RFC2732原文链接
RFC2732参考译文链接
参考译文版权信息：
组织：中国互动出版网（http://www.china-pub.com/）
RFC文档中文翻译计划（http://www.china-pub.com/compters/emook/aboutemook.htm）
E-mail：[email protected]
译者：王治恒（cata_xu [email protected]）
译文发布时间：2001-6-10
版权：本中文翻译文档版权归中国互动出版网所有。可以用于非商业用途自由转载，但必须
保留本文档的翻译及版权信息。
目录
1. 介
绍
1.1 要求
2. URL语法中的IPv6地址文本格式
3. 对RFC 2396的修改
4. 安全考虑
5. IANA的考虑
参考
作者的地址
版权声明
致谢
Network Working Group
Request for Comments: 2732
Category: Standards Track
R. Hinden
Nokia
B. Carpenter
IBM
L. Masinter
AT&
TDecember 1999
Format for Literal IPv6 Addresses in URL’s
文本IPv6地址在URL上的格式
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.
本文档讲述了一种Internet社区的Internet标准跟踪协议，它需要进一步进行讨论和建
议以得到改进。请参考最新版的“Internet正式协议标准” (STD1)来获得本协议的标
准化程度和状态。本备忘录的发布不受任何限制。
Copyright Notice –版权声明
Copyright (C) The Internet Society (1999). All Rights Reserved.
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.
本文档定义了在WWW浏览器的URL中执行的文本IPv6地址的格式。在包括Microsoft的
IE，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地址的语法规则并允许在统一资源
标识符中使用“[”和“]”符号。
Introduction –介绍
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的表述方法相适应。尽管
两者都使用符号“：”和“.”作为分隔符。本文档定义了在WWW浏览器的URL中执行
的文本IPv6地址的格式。其目的就是为了得到一种格式，能够很容易的使用剪切和
粘贴操作以使文本地址编辑操作达到最少。
Hinden, et al. Standards Track [Page 1]
RFC 2732 IPv6 Literal Addresses in URL’s December 1999
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的IE，Mozilla和Lynx等几个已经被广泛安装使用的浏览器的IPv6
版本中，这种格式已经被使用。并且这种格式也将被应用于服务定位协议的IPv6版本
中。
1.1 Requirements 要求
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.
如果本文档中任何地方出现关键词 MUST，MUST NOT，REQUIRED，SHALL， SHALL
NOT， SHOULD， SHOULD NOT， RECOMMENDED， MAY，以及OPTIONAL，都将和它们
在[KEYWORDS]中的定义一致。
WWW浏览器‘SHOULD’（应当）在URL中使用本文档定义的IPv6文本格式。其它一些
使用URL的应用和协议‘MAY’（可以）用这种格式。Literal IPv6 Address Format in URL’s Syntax – 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
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]Changes to RFC 2396 —对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地址的语法规则并允许在统一资源
标识符中使用“[”和“]”符号。
Hinden, et al. Standards Track [Page 2]
RFC 2732 IPv6 Literal Addresses in URL’s December 1999
The following changes to the syntax in RFC 2396 are made:
对RFC 2396中语法的一些改变如下：
(1) change the ’host’ non-terminal to add an IPv6 option:
在‘主机（host）’末端增加一节IPv6项 ：
host = hostname | 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.
由于RFC 2373中“IPv4地址”的定义更清晰的说明了IPv4地址是由每节最多三个
十进制数组成的，所以用这个定义来替换RFC 2396中的定义。
(3) Add “[” and “]” to the set of ’reserved’ characters:
在’设定‘符号组中增加“[”和“]”：
reserved = “;” | “/” | “?” | “:” | “@” | “&” | “=” | “+” |
“$” | “,” | “[” | “]”
and remove them from the ’unwise’ set:
并且把它们从’非合理‘符号组中去掉：
unwise = “{” | “}” | “|” | “\” | “^” | “‘”Security Considerations 安全考虑
The use of this approach to represent literal IPv6 addresses in URL’s
does not introduce any known new security concerns.
这种在URL中使用文本IPv6地址的表述方法的应用不会引起任何新的已知安全问题。IANA Considerations
None.
Hinden, et al. Standards Track [Page 3]
RFC 2732 IPv6 Literal Addresses in URL’s December 1999- Authors’ Addresses
Robert M. Hinden
Nokia
313 Fairchild Drive
Mountain View, CA 94043
USA
Phone: +1 650 625 2004
EMail: [email protected]
Web: http://www.iprg.nokia.com/ ̃hinden
Brian E. Carpenter
IBM
iCAIR, Suite 150
1890 Maple Avenue
Evanston IL 60201
USA
EMail: [email protected]
Larry Masinter
AT&T Labs
75 Willow Road
Menlo Park, CA 94025
EMail: [email protected]
Web: http://larry.masinter.net - References
[ARCH] Hinden, R. and S. Deering, “IP Version 6 Addressing
Architecture”, RFC 2373, July 1998.
[STD-PROC] Bradner, S., The Internet Standards Process – Revision 3,
BCP 9, RFC 2026, October 1996.
[URL] Fielding, R., Masinter, L. and T. Berners-Lee, “Uniform
Resource Identifiers: Generic Syntax”, RFC 2396, August
1998.
Hinden, et al. Standards Track [Page 4]
RFC 2732 IPv6 Literal Addresses in URL’s December 1999 - Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved.
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.
Hinden, et al. Standards Track [Page 5]