Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
draft-carpenter-6man-rfc6874bis-03
| Document | Type |
Replaced Internet-Draft
(6man WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Brian E. Carpenter , Stuart Cheshire , Bob Hinden | ||
| Last updated | 2022-03-16 (Latest revision 2022-02-08) | ||
| Replaced by | draft-ietf-6man-rfc6874bis | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-6man-rfc6874bis | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 updates the URI Generic Syntax and Internationalized Resource Identifier specifications (RFC 3986, RFC 3987) accordingly, and obsoletes RFC 6874.
Authors
Brian E. Carpenter
Stuart Cheshire
Bob Hinden
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)