draft-ietf-6man-uri-zoneid-03.txt   draft-ietf-6man-uri-zoneid-04.txt 
6MAN B. Carpenter 6MAN B. Carpenter
Internet-Draft Univ. of Auckland Internet-Draft Univ. of Auckland
Updates: 3986 (if approved) R. Hinden Updates: 3986 (if approved) S. Cheshire
Intended status: Standards Track Check Point Intended status: Standards Track Apple Inc.
Expires: March 14, 2013 September 10, 2012 Expires: March 25, 2013 R. Hinden
Check Point
September 21, 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-03 draft-ietf-6man-uri-zoneid-04
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 35 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 14, 2013. This Internet-Draft will expire on March 25, 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 3, line 7 skipping to change at page 3, line 7
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
7. Change log [RFC Editor: Please remove] . . . . . . . . . . . . 6 7. Change log [RFC Editor: Please remove] . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . . 7 8.1. Normative References . . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . . 7 8.2. Informative References . . . . . . . . . . . . . . . . . . 7
Appendix A. Alternatives Considered . . . . . . . . . . . . . . . 8 Appendix A. Alternatives Considered . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
[RFC3986] defined how a literal IPv6 address can be represented in The Uniform Resource Identifier (URI) syntax [RFC3986] defined how a
the "host" part of a Uniform Resource Identifier (URI). literal IPv6 address can be represented in the "host" part of a URI.
Subsequently, [RFC4007] extended the text representation of limited- A subsequent specification [RFC4007] extended the text representation
scope IPv6 addresses such that a zone identifier may be concatenated of limited-scope IPv6 addresses such that a zone identifier may be
to a literal address, for purposes described in that RFC. Zone concatenated to a literal address, for purposes described in that
identifiers are especially useful in contexts where literal addresses RFC. Zone identifiers are especially useful in contexts where
are typically used, for example during fault diagnosis, when it may literal addresses are typically used, for example during fault
be essential to specify which interface is used for sending to a link diagnosis, when it may be essential to specify which interface is
local address. It should be noted that zone identifiers have purely used for sending to a link local address. It should be noted that
local meaning within the host where they are defined, and they are zone identifiers have purely local meaning within the host where they
completely meaningless for any other host. Today, they are only are defined, and they are completely meaningless for any other host.
meaningful when attached to addresses with less than global scope, Today, they are only meaningful when attached to addresses with less
but it is possible that other uses might be defined in the future. 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 RFC 4007 does not specify how zone identifiers are to be represented
in URIs. Practical experience has shown that this feature is useful, in URIs. Practical experience has shown that this feature is useful,
in particular when using a web browser for debugging with link local in particular when using a web browser for debugging with link local
addresses, but as it is undefined, it is not implemented consistently addresses, but as it is undefined, it is not implemented consistently
in URI parsers or in browsers. in URI parsers or in browsers.
Some versions of some browsers accept the RFC 4007 syntax for scoped Some versions of some browsers accept the RFC 4007 syntax for scoped
IPv6 addresses embedded in URIs, i.e., they have been coded to IPv6 addresses embedded in URIs, i.e., they have been coded to
interpret the "%" sign according to RFC 4007 instead of RFC 3986. interpret the "%" sign according to RFC 4007 instead of RFC 3986.
skipping to change at page 6, line 27 skipping to change at page 6, line 29
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, Tatuya Jinmei, Tom Petch, Tomoyuki Sahara,
Juergen Schoenwaelder, Dave Thaler, and Ole Troan. 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 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-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.
draft-ietf-6man-uri-zoneid-00: adopted by WG, fixed syntax to allow draft-ietf-6man-uri-zoneid-00: adopted by WG, fixed syntax to allow
skipping to change at page 9, line 30 skipping to change at page 9, line 31
Brian Carpenter Brian Carpenter
Department of Computer Science Department of Computer Science
University of Auckland University of Auckland
PB 92019 PB 92019
Auckland, 1142 Auckland, 1142
New Zealand New Zealand
Email: brian.e.carpenter@gmail.com Email: brian.e.carpenter@gmail.com
Stuart Cheshire
Apple Inc.
1 Infinite Loop
Cupertino, CA 95014
US
Email: cheshire@apple.com
Robert M. Hinden Robert M. Hinden
Check Point Software Technologies, Inc. Check Point Software Technologies, Inc.
800 Bridge Parkway 800 Bridge Parkway
Redwood City, CA 94065 Redwood City, CA 94065
US US
Email: bob.hinden@gmail.com Email: bob.hinden@gmail.com
 End of changes. 7 change blocks. 
21 lines changed or deleted 31 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/