Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
draft-ietf-6man-uri-zoneid-02

The information below is for an old version of the document
Document Type Active Internet-Draft (6man WG)
Last updated 2012-07-11
Replaces draft-carpenter-6man-uri-zoneid
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
6MAN                                                        B. Carpenter
Internet-Draft                                         Univ. of Auckland
Updates: 3986, 4007 (if approved)                              R. Hinden
Intended status: Standards Track                             Check Point
Expires: January 12, 2013                                  July 11, 2012

   Representing IPv6 Zone Identifiers in Address Literals and Uniform
                          Resource Identifiers
                     draft-ietf-6man-uri-zoneid-02

Abstract

   This document describes how the Zone Identifier of an IPv6 scoped
   address can be represented in a a literal IPv6 address and in a
   Uniform Resource Identifier that includes such a literal address.  It
   updates RFC 3986 and RFC 4007 accordingly.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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 January 12, 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
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as

Carpenter & Hinden      Expires January 12, 2013                [Page 1]
Internet-Draft             IPv6 Zone ID in URI                 July 2012

   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Specification . . . . . . . . . . . . . . . . . . . . . . . . . 4
   3.  Web Browsers  . . . . . . . . . . . . . . . . . . . . . . . . . 5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 6
   7.  Change log [RFC Editor: Please remove]  . . . . . . . . . . . . 7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . . . 7
     8.2.  Informative References  . . . . . . . . . . . . . . . . . . 8
   Appendix A.  Alternatives Considered  . . . . . . . . . . . . . . . 8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 9

Carpenter & Hinden      Expires January 12, 2013                [Page 2]
Internet-Draft             IPv6 Zone ID in URI                 July 2012

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.

   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.
   Clearly this approach is very convenient for users, although it
   formally breaches the syntax rules of RFC 3986.  The present document
Show full document text