Format for Literal IPv6 Addresses in URL's URI 中の
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.
Copyright (C) The Internet Society (1999). All Rights Reserved.
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.
この文書は、
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 で定義された[ 及び ]
の使用を陽に認めます。
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] で定義された: 及び文字 . を区切子として使用します。
この文書は、
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 を含む広く用いられている幾つかの
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.
.
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 中で[ 及び文字 ]
で囲む
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:4179would 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]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
で定義された[ 及び ]
を使用することを陽に認めます。
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) 非終端 host を変更して IPv6 選択肢を加えます。
host = hostname | IPv4address | IPv6reference
ipv6reference = "[" IPv6address "]"where IPv6address is defined as in 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)
(3) Add "[" and "]" to the set of 'reserved' characters:
[
及び ] を加えます。
reserved = ";" | "/" | "?" | ":" | "@" | "&" | "=" | "+" |
"$" | "," | "[" | "]"and remove them from the 'unwise' set:
そして
unwise = "{" | "}" | "|" | "\" | "^" | "`"The use of this approach to represent literal IPv6 addresses in URL's does not introduce any known new security concerns.
URL で
None.
特になし。
Robert M. Hinden Nokia 313 Fairchild Drive Mountain View, CA 94043 USA
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
EMail: brian@icair.org
Larry Masinter AT&T Labs 75 Willow Road Menlo Park, CA 94025
EMail: LMM@acm.org Web: http://larry.masinter.net
[ARCH] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture IP 第6版 [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
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.
Funding for the RFC Editor function is currently provided by the Internet Society.