--- 1/draft-ietf-6man-uri-zoneid-03.txt 2012-09-21 16:14:30.429342934 +0200 +++ 2/draft-ietf-6man-uri-zoneid-04.txt 2012-09-21 16:14:30.449342243 +0200 @@ -1,20 +1,22 @@ 6MAN B. Carpenter Internet-Draft Univ. of Auckland -Updates: 3986 (if approved) R. Hinden -Intended status: Standards Track Check Point -Expires: March 14, 2013 September 10, 2012 +Updates: 3986 (if approved) S. Cheshire +Intended status: Standards Track Apple Inc. +Expires: March 25, 2013 R. Hinden + Check Point + September 21, 2012 Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers - draft-ietf-6man-uri-zoneid-03 + draft-ietf-6man-uri-zoneid-04 Abstract This document describes how the Zone Identifier of an IPv6 scoped address can be represented in a literal IPv6 address and in a Uniform Resource Identifier that includes such a literal address. It updates RFC 3986 accordingly. Status of this Memo @@ -24,21 +26,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on March 14, 2013. + This Internet-Draft will expire on March 25, 2013. Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -58,33 +60,34 @@ 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 7. Change log [RFC Editor: Please remove] . . . . . . . . . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 8.1. Normative References . . . . . . . . . . . . . . . . . . . 7 8.2. Informative References . . . . . . . . . . . . . . . . . . 7 Appendix A. Alternatives Considered . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 1. Introduction - [RFC3986] defined how a literal IPv6 address can be represented in - the "host" part of a Uniform Resource Identifier (URI). - Subsequently, [RFC4007] extended the text representation of limited- - scope IPv6 addresses such that a zone identifier may be concatenated - to a literal address, for purposes described in that RFC. Zone - identifiers are especially useful in contexts where literal addresses - are typically used, for example during fault diagnosis, when it may - be essential to specify which interface is used for sending to a link - local address. It should be noted that zone identifiers have purely - local meaning within the host where they are defined, and they are - completely meaningless for any other host. Today, they are only - meaningful when attached to addresses with less than global scope, - but it is possible that other uses might be defined in the future. + The Uniform Resource Identifier (URI) syntax [RFC3986] defined how a + literal IPv6 address can be represented in the "host" part of a URI. + A subsequent specification [RFC4007] extended the text representation + of limited-scope IPv6 addresses such that a zone identifier may be + concatenated to a literal address, for purposes described in that + RFC. Zone identifiers are especially useful in contexts where + literal addresses are typically used, for example during fault + diagnosis, when it may be essential to specify which interface is + used for sending to a link local address. It should be noted that + zone identifiers have purely local meaning within the host where they + are defined, and they are completely meaningless for any other host. + Today, they are only meaningful when attached to addresses with less + than global scope, but it is possible that other uses might be + defined in the future. RFC 4007 does not specify how zone identifiers are to be represented in URIs. Practical experience has shown that this feature is useful, in particular when using a web browser for debugging with link local addresses, but as it is undefined, it is not implemented consistently in URI parsers or in browsers. Some versions of some browsers accept the RFC 4007 syntax for scoped IPv6 addresses embedded in URIs, i.e., they have been coded to interpret the "%" sign according to RFC 4007 instead of RFC 3986. @@ -221,30 +223,29 @@ The lack of this format was first pointed out by Margaret Wasserman some years ago, and more recently by Kerry Lynn. A previous draft document by Martin Duerst and Bill Fenner [I-D.fenner-literal-zone] discussed this topic but was not finalised. Valuable comments and contributions were made by Karl Auer, Carsten Bormann, Brian Haberman, Tatuya Jinmei, Tom Petch, Tomoyuki Sahara, Juergen Schoenwaelder, Dave Thaler, and Ole Troan. - Stuart Cheshire suggested the current approach taken by this - document. - Brian Carpenter was a visitor at the Computer Laboratory, Cambridge University during part of this work. This document was produced using the xml2rfc tool [RFC2629]. 7. Change log [RFC Editor: Please remove] + draft-ietf-6man-uri-zoneid-03: additional author, 2012-21-10. + draft-ietf-6man-uri-zoneid-03: reverted to percent-encoded model following WGLC, 2012-09-10. draft-ietf-6man-uri-zoneid-02: additional WG comments, 2012-07-11. draft-ietf-6man-uri-zoneid-01: use "-" instead of %25, listed alternatives in Appendix, according to WG debate, added suggestion for browser developers, 2012-05-29. draft-ietf-6man-uri-zoneid-00: adopted by WG, fixed syntax to allow @@ -365,17 +365,25 @@ Brian Carpenter Department of Computer Science University of Auckland PB 92019 Auckland, 1142 New Zealand Email: brian.e.carpenter@gmail.com + Stuart Cheshire + Apple Inc. + 1 Infinite Loop + Cupertino, CA 95014 + US + + Email: cheshire@apple.com + Robert M. Hinden Check Point Software Technologies, Inc. 800 Bridge Parkway Redwood City, CA 94065 US Email: bob.hinden@gmail.com