Network Working Group                                        R. Hinden
Request for Comments: 2732                                       Nokia
Category: Standards Track                                 B. Carpenter
                                                                   IBM
                                                           L. Masinter
                                                                  AT&T
                                                         December 1999
        
Network Working Group                                        R. Hinden
Request for Comments: 2732                                       Nokia
Category: Standards Track                                 B. Carpenter
                                                                   IBM
                                                           L. Masinter
                                                                  AT&T
                                                         December 1999
        

Format for Literal IPv6 Addresses in URL's

URL中文本IPv6地址的格式

Status of this Memo

本备忘录的状况

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

本文件规定了互联网社区的互联网标准跟踪协议,并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态,请参考当前版本的“互联网官方协议标准”(STD 1)。本备忘录的分发不受限制。

Copyright Notice

版权公告

Copyright (C) The Internet Society (1999). All Rights Reserved.

版权所有(C)互联网协会(1999年)。版权所有。

Abstract

摘要

This document defines the format for literal IPv6 Addresses in URL's for implementation in World Wide Web browsers. This format has been implemented in the IPv6 versions of several widely deployed browsers including Microsoft Internet Explorer, Mozilla, and Lynx. It is also intended to be used in the IPv6 version of the service location protocol.

本文档定义了URL中文字IPv6地址的格式,以便在万维网浏览器中实现。这种格式已经在几种广泛部署的浏览器(包括Microsoft Internet Explorer、Mozilla和Lynx)的IPv6版本中实现。它还打算用于IPv6版本的服务位置协议。

This document incudes an update to the generic syntax for Uniform Resource Identifiers defined in RFC 2396 [URL]. It defines a syntax for IPv6 addresses and allows the use of "[" and "]" within a URI explicitly for this reserved purpose.

本文档包括对RFC 2396[URL]中定义的统一资源标识符的通用语法的更新。它定义了IPv6地址的语法,并允许在URI中显式地使用“[”和“]”用于此保留目的。

1. Introduction
1. 介绍

The textual representation defined for literal IPv6 addresses in [ARCH] is not directly compatible with URL's. Both use ":" and "." characters as delimiters. This document defines the format for literal IPv6 Addresses in URL's for implementation in World Wide Web browsers. The goal is to have a format that allows easy "cut" and "paste" operations with a minimum of editing of the literal address.

[ARCH]中为文字IPv6地址定义的文本表示形式与URL不直接兼容。两者都使用“:”和“.”字符作为分隔符。本文档定义了URL中文字IPv6地址的格式,以便在万维网浏览器中实现。我们的目标是要有一种格式,允许简单的“剪切”和“粘贴”操作,并对文本地址进行最少的编辑。

The format defined in this document has been implemented in the IPv6 versions of several widely deployed browsers including Microsoft Internet Explorer, Mozilla, and Lynx. It is also intended to be used in the IPv6 version of the service location protocol.

本文档中定义的格式已在几种广泛部署的浏览器(包括Microsoft Internet Explorer、Mozilla和Lynx)的IPv6版本中实现。它还打算用于IPv6版本的服务位置协议。

1.1 Requirements
1.1 要求

The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, if and where they appear in this document, are to be interpreted as described in [KEYWORDS].

关键词必须、不得、必需、应、不应、应、不应、建议、可能和可选,如果出现在本文件中,则应按照[关键词]中的说明进行解释。

World Wide Web browsers SHOULD implement the format of IPv6 literals in URL's defined in this document. Other types of applications and protocols that use URL's MAY use this format.

万维网浏览器应在本文档中定义的URL中实现IPv6文本格式。使用URL的其他类型的应用程序和协议可能使用此格式。

2. Literal IPv6 Address Format in URL's Syntax
2. URL语法中的文字IPv6地址格式

To use a literal IPv6 address in a URL, the literal address should be enclosed in "[" and "]" characters. For example the following literal IPv6 addresses:

要在URL中使用文字IPv6地址,文字地址应包含在“[”和“]”字符中。例如,以下文字IPv6地址:

      FEDC:BA98:7654:3210:FEDC:BA98:7654:3210
      1080:0:0:0:8:800:200C:4171
      3ffe:2a00:100:7031::1
      1080::8:800:200C:417A
      ::192.9.5.5
      ::FFFF:129.144.52.38
      2010:836B:4179::836B:4179
        
      FEDC:BA98:7654:3210:FEDC:BA98:7654:3210
      1080:0:0:0:8:800:200C:4171
      3ffe:2a00:100:7031::1
      1080::8:800:200C:417A
      ::192.9.5.5
      ::FFFF:129.144.52.38
      2010:836B:4179::836B:4179
        

would be represented as in the following example URLs:

将表示为以下示例URL:

      http://[FEDC:BA98:7654:3210:FEDC:BA98:7654:3210]:80/index.html
      http://[1080:0:0:0:8:800:200C:417A]/index.html
      http://[3ffe:2a00:100:7031::1]
      http://[1080::8:800:200C:417A]/foo
      http://[::192.9.5.5]/ipng
      http://[::FFFF:129.144.52.38]:80/index.html
      http://[2010:836B:4179::836B:4179]
        
      http://[FEDC:BA98:7654:3210:FEDC:BA98:7654:3210]:80/index.html
      http://[1080:0:0:0:8:800:200C:417A]/index.html
      http://[3ffe:2a00:100:7031::1]
      http://[1080::8:800:200C:417A]/foo
      http://[::192.9.5.5]/ipng
      http://[::FFFF:129.144.52.38]:80/index.html
      http://[2010:836B:4179::836B:4179]
        
3. Changes to RFC 2396
3. 对RFC 2396的更改

This document updates the generic syntax for Uniform Resource Identifiers defined in RFC 2396 [URL]. It defines a syntax for IPv6 addresses and allows the use of "[" and "]" within a URI explicitly for this reserved purpose.

本文档更新了RFC 2396[URL]中定义的统一资源标识符的通用语法。它定义了IPv6地址的语法,并允许在URI中显式地使用“[”和“]”用于此保留目的。

The following changes to the syntax in RFC 2396 are made: (1) change the 'host' non-terminal to add an IPv6 option:

对RFC 2396中的语法进行了以下更改:(1)更改“主机”非终端以添加IPv6选项:

host = hostname | IPv4address | IPv6reference ipv6reference = "[" IPv6address "]"

主机名=主机名| IPv4address | IPv6reference IPv6reference=“[“IPv6address”]”

where IPv6address is defined as in RFC2373 [ARCH].

其中,IPV6地址的定义如RFC2373[ARCH]中所述。

(2) Replace the definition of 'IPv4address' with that of RFC 2373, as it correctly defines an IPv4address as consisting of at most three decimal digits per segment.

(2) 将“IPv4address”的定义替换为RFC 2373的定义,因为它正确地将IPv4address定义为每个段最多包含三个十进制数字。

(3) Add "[" and "]" to the set of 'reserved' characters:

(3) 将“[”和“]”添加到“保留”字符集:

      reserved    = ";" | "/" | "?" | ":" | "@" | "&" | "=" | "+" |
                    "$" | "," | "[" | "]"
        
      reserved    = ";" | "/" | "?" | ":" | "@" | "&" | "=" | "+" |
                    "$" | "," | "[" | "]"
        

and remove them from the 'unwise' set:

并将其从“不明智”集合中删除:

      unwise      = "{" | "}" | "|" | "\" | "^" | "`"
        
      unwise      = "{" | "}" | "|" | "\" | "^" | "`"
        
4. Security Considerations
4. 安全考虑

The use of this approach to represent literal IPv6 addresses in URL's does not introduce any known new security concerns.

使用此方法在URL中表示文字IPv6地址不会引入任何已知的新安全问题。

5. IANA Considerations
5. IANA考虑

None.

没有一个

6. Authors' Addresses
6. 作者地址

Robert M. Hinden Nokia 313 Fairchild Drive Mountain View, CA 94043 USA

Robert M.Hinden诺基亚313飞兆半导体山景大道,加利福尼亚州94043

   Phone: +1 650 625 2004
   EMail: hinden@iprg.nokia.com
   Web: http://www.iprg.nokia.com/~hinden
        
   Phone: +1 650 625 2004
   EMail: hinden@iprg.nokia.com
   Web: http://www.iprg.nokia.com/~hinden
        

Brian E. Carpenter IBM iCAIR, Suite 150 1890 Maple Avenue Evanston IL 60201 USA

Brian E.Carpenter IBM iCAIR,美国伊利诺伊州埃文斯顿枫叶大道1890号150室,邮编60201

   EMail: brian@icair.org
        
   EMail: brian@icair.org
        

Larry Masinter AT&T Labs 75 Willow Road Menlo Park, CA 94025

加利福尼亚州门罗公园柳树路75号Larry Masinter AT&T实验室,邮编94025

   EMail: LMM@acm.org
   Web: http://larry.masinter.net
        
   EMail: LMM@acm.org
   Web: http://larry.masinter.net
        
7. References
7. 工具书类

[ARCH] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 2373, July 1998.

[ARCH]Hinden,R.和S.Deering,“IP版本6寻址体系结构”,RFC 23731998年7月。

[STD-PROC] Bradner, S., The Internet Standards Process -- Revision 3, BCP 9, RFC 2026, October 1996.

[STD-PROC]Bradner,S.,互联网标准过程——修订版3,BCP 9,RFC 2026,1996年10月。

[URL] Fielding, R., Masinter, L. and T. Berners-Lee, "Uniform Resource Identifiers: Generic Syntax", RFC 2396, August 1998.

[URL]Fielding,R.,Masinter,L.和T.Berners Lee,“统一资源标识符:通用语法”,RFC 2396,1998年8月。

8. Full Copyright Statement
8. 完整版权声明

Copyright (C) The Internet Society (1999). All Rights Reserved.

版权所有(C)互联网协会(1999年)。版权所有。

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.

本文件及其译本可复制并提供给他人,对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发,不受任何限制,前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是,不得以任何方式修改本文件本身,例如删除版权通知或对互联网协会或其他互联网组织的引用,除非出于制定互联网标准的需要,在这种情况下,必须遵循互联网标准过程中定义的版权程序,或根据需要将其翻译成英语以外的其他语言。

The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.

上述授予的有限许可是永久性的,互联网协会或其继承人或受让人不会撤销。

This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

本文件和其中包含的信息是按“原样”提供的,互联网协会和互联网工程任务组否认所有明示或暗示的保证,包括但不限于任何保证,即使用本文中的信息不会侵犯任何权利,或对适销性或特定用途适用性的任何默示保证。

Acknowledgement

确认

Funding for the RFC Editor function is currently provided by the Internet Society.

RFC编辑功能的资金目前由互联网协会提供。