An IPvFuture Syntax for IPv6 Link-Local Addresses
draft-sweet-uri-zoneid-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Michael Sweet | ||
| Last updated | 2014-05-26 (Latest revision 2013-11-22) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
xml
pdf
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-sweet-uri-zoneid-01.txt
Abstract
This document describes how the zone identifier of an IPv6 scoped address, defined as <zone_id> in the IPv6 Scoped Address Architecture (RFC 4007), can be represented in a literal IPv6 address and in a Uniform Resource Identifier that includes such a literal address. It documents a long-standing usage of the IPvFuture extension point provided in the Uniform Resource Identifier (URI) syntax specification [RFC3986]. [ Editor's note: This draft documents the IPvFuture format originally defined in [LITERAL-ZONE] and used by CUPS since 2005. A separate, incompatible format was defined and published in RFC 6874. ]
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)