draft-ietf-6man-uri-zoneid-04.txt | draft-ietf-6man-uri-zoneid-05.txt | |||
---|---|---|---|---|
6MAN B. Carpenter | 6MAN B. Carpenter | |||
Internet-Draft Univ. of Auckland | Internet-Draft Univ. of Auckland | |||
Updates: 3986 (if approved) S. Cheshire | Updates: 3986 (if approved) S. Cheshire | |||
Intended status: Standards Track Apple Inc. | Intended status: Standards Track Apple Inc. | |||
Expires: March 25, 2013 R. Hinden | Expires: May 10, 2013 R. Hinden | |||
Check Point | Check Point | |||
September 21, 2012 | November 6, 2012 | |||
Representing IPv6 Zone Identifiers in Address Literals and Uniform | Representing IPv6 Zone Identifiers in Address Literals and Uniform | |||
Resource Identifiers | Resource Identifiers | |||
draft-ietf-6man-uri-zoneid-04 | draft-ietf-6man-uri-zoneid-05 | |||
Abstract | Abstract | |||
This document describes how the Zone Identifier of an IPv6 scoped | This document describes how the Zone Identifier of an IPv6 scoped | |||
address can be represented in a literal IPv6 address and in a Uniform | address can be represented in a literal IPv6 address and in a Uniform | |||
Resource Identifier that includes such a literal address. It updates | Resource Identifier that includes such a literal address. It updates | |||
RFC 3986 accordingly. | RFC 3986 accordingly. | |||
Status of this Memo | Status of this Memo | |||
skipping to change at page 1, line 37 | skipping to change at page 1, line 37 | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
This Internet-Draft will expire on March 25, 2013. | This Internet-Draft will expire on May 10, 2013. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2012 IETF Trust and the persons identified as the | Copyright (c) 2012 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
skipping to change at page 4, line 48 | skipping to change at page 4, line 48 | |||
[RFC5234] by the following rule: | [RFC5234] by the following rule: | |||
IP-literal = "[" ( IPv6address / IPvFuture ) "]" | IP-literal = "[" ( IPv6address / IPvFuture ) "]" | |||
To provide support for a zone identifier, the existing syntax of | To provide support for a zone identifier, the existing syntax of | |||
IPv6address is retained, and a zone identifier may be added | IPv6address is retained, and a zone identifier may be added | |||
optionally to any literal address. This allows flexibility for | optionally to any literal address. This allows flexibility for | |||
unknown future uses. The rule quoted above from RFC 3986 is replaced | unknown future uses. The rule quoted above from RFC 3986 is replaced | |||
by three rules: | by three rules: | |||
IP-literal = "[" ( IPv6addrz / IPvFuture ) "]" | IP-literal = "[" ( IPv6address / IPv6addrz / IPvFuture ) "]" | |||
ZoneID = 1*( unreserved / pct-encoded ) | ZoneID = 1*( unreserved / pct-encoded ) | |||
IPv6addrz = IPv6address [ "%" ZoneID ] | IPv6addrz = IPv6address "%25" ZoneID | |||
This syntax fills the gap that is described at the end of Section | ||||
11.7 of RFC 4007. | ||||
The rules in [RFC5952] SHOULD be applied in producing URIs. | The rules in [RFC5952] SHOULD be applied in producing URIs. | |||
RFC 3986 states that URIs have a global scope, but that in some cases | RFC 3986 states that URIs have a global scope, but that in some cases | |||
their interpretation depends on the end-user's context. URIs | their interpretation depends on the end-user's context. URIs | |||
including a ZoneID are to be interpreted only in the context of the | including a ZoneID are to be interpreted only in the context of the | |||
host where they originate, since the ZoneID is of local signifance | host where they originate, since the ZoneID is of local signifance | |||
only. | only. | |||
The 6man WG discussed and rejected an alternative in which the | The 6man WG discussed and rejected an alternative in which the | |||
skipping to change at page 6, line 26 | skipping to change at page 6, line 29 | |||
This document requests no action by IANA. | This document requests no action by IANA. | |||
6. Acknowledgements | 6. Acknowledgements | |||
The lack of this format was first pointed out by Margaret Wasserman | The lack of this format was first pointed out by Margaret Wasserman | |||
some years ago, and more recently by Kerry Lynn. A previous draft | some years ago, and more recently by Kerry Lynn. A previous draft | |||
document by Martin Duerst and Bill Fenner [I-D.fenner-literal-zone] | document by Martin Duerst and Bill Fenner [I-D.fenner-literal-zone] | |||
discussed this topic but was not finalised. | discussed this topic but was not finalised. | |||
Valuable comments and contributions were made by Karl Auer, Carsten | Valuable comments and contributions were made by Karl Auer, Carsten | |||
Bormann, Brian Haberman, Tatuya Jinmei, Tom Petch, Tomoyuki Sahara, | Bormann, Brian Haberman, Ted Hardie, Tatuya Jinmei, Tom Petch, | |||
Juergen Schoenwaelder, Dave Thaler, and Ole Troan. | Tomoyuki Sahara, Juergen Schoenwaelder, Dave Thaler, and Ole Troan. | |||
Brian Carpenter was a visitor at the Computer Laboratory, Cambridge | Brian Carpenter was a visitor at the Computer Laboratory, Cambridge | |||
University during part of this work. | University during part of this work. | |||
This document was produced using the xml2rfc tool [RFC2629]. | This document was produced using the xml2rfc tool [RFC2629]. | |||
7. Change log [RFC Editor: Please remove] | 7. Change log [RFC Editor: Please remove] | |||
draft-ietf-6man-uri-zoneid-03: additional author, 2012-21-10. | draft-ietf-6man-uri-zoneid-05: tuned ABNF, clarified RFC 4007 text, | |||
2012-11-06. | ||||
draft-ietf-6man-uri-zoneid-04: additional author, 2012-09-21. | ||||
draft-ietf-6man-uri-zoneid-03: reverted to percent-encoded model | draft-ietf-6man-uri-zoneid-03: reverted to percent-encoded model | |||
following WGLC, 2012-09-10. | following WGLC, 2012-09-10. | |||
draft-ietf-6man-uri-zoneid-02: additional WG comments, 2012-07-11. | draft-ietf-6man-uri-zoneid-02: additional WG comments, 2012-07-11. | |||
draft-ietf-6man-uri-zoneid-01: use "-" instead of %25, listed | draft-ietf-6man-uri-zoneid-01: use "-" instead of %25, listed | |||
alternatives in Appendix, according to WG debate, added suggestion | alternatives in Appendix, according to WG debate, added suggestion | |||
for browser developers, 2012-05-29. | for browser developers, 2012-05-29. | |||
End of changes. 8 change blocks. | ||||
9 lines changed or deleted | 15 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |