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]