/Documentation/rfc2732.txt

http://eeframework.googlecode.com/ · Plain Text · 283 lines · 157 code · 126 blank · 0 comment · 0 complexity · ed75fc9f92ea51f31bac43c31ace0df3 MD5 · raw file

  1. Network Working Group R. Hinden
  2. Request for Comments: 2732 Nokia
  3. Category: Standards Track B. Carpenter
  4. IBM
  5. L. Masinter
  6. AT&T
  7. December 1999
  8. Format for Literal IPv6 Addresses in URL's
  9. Status of this Memo
  10. This document specifies an Internet standards track protocol for the
  11. Internet community, and requests discussion and suggestions for
  12. improvements. Please refer to the current edition of the "Internet
  13. Official Protocol Standards" (STD 1) for the standardization state
  14. and status of this protocol. Distribution of this memo is unlimited.
  15. Copyright Notice
  16. Copyright (C) The Internet Society (1999). All Rights Reserved.
  17. Abstract
  18. This document defines the format for literal IPv6 Addresses in URL's
  19. for implementation in World Wide Web browsers. This format has been
  20. implemented in the IPv6 versions of several widely deployed browsers
  21. including Microsoft Internet Explorer, Mozilla, and Lynx. It is also
  22. intended to be used in the IPv6 version of the service location
  23. protocol.
  24. This document incudes an update to the generic syntax for Uniform
  25. Resource Identifiers defined in RFC 2396 [URL]. It defines a syntax
  26. for IPv6 addresses and allows the use of "[" and "]" within a URI
  27. explicitly for this reserved purpose.
  28. 1. Introduction
  29. The textual representation defined for literal IPv6 addresses in
  30. [ARCH] is not directly compatible with URL's. Both use ":" and "."
  31. characters as delimiters. This document defines the format for
  32. literal IPv6 Addresses in URL's for implementation in World Wide Web
  33. browsers. The goal is to have a format that allows easy "cut" and
  34. "paste" operations with a minimum of editing of the literal address.
  35. Hinden, et al. Standards Track [Page 1]
  36. RFC 2732 IPv6 Literal Addresses in URL's December 1999
  37. The format defined in this document has been implemented in the IPv6
  38. versions of several widely deployed browsers including Microsoft
  39. Internet Explorer, Mozilla, and Lynx. It is also intended to be used
  40. in the IPv6 version of the service location protocol.
  41. 1.1 Requirements
  42. The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
  43. SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, if and where they appear
  44. in this document, are to be interpreted as described in [KEYWORDS].
  45. World Wide Web browsers SHOULD implement the format of IPv6 literals
  46. in URL's defined in this document. Other types of applications and
  47. protocols that use URL's MAY use this format.
  48. 2. Literal IPv6 Address Format in URL's Syntax
  49. To use a literal IPv6 address in a URL, the literal address should be
  50. enclosed in "[" and "]" characters. For example the following
  51. literal IPv6 addresses:
  52. FEDC:BA98:7654:3210:FEDC:BA98:7654:3210
  53. 1080:0:0:0:8:800:200C:4171
  54. 3ffe:2a00:100:7031::1
  55. 1080::8:800:200C:417A
  56. ::192.9.5.5
  57. ::FFFF:129.144.52.38
  58. 2010:836B:4179::836B:4179
  59. would be represented as in the following example URLs:
  60. http://[FEDC:BA98:7654:3210:FEDC:BA98:7654:3210]:80/index.html
  61. http://[1080:0:0:0:8:800:200C:417A]/index.html
  62. http://[3ffe:2a00:100:7031::1]
  63. http://[1080::8:800:200C:417A]/foo
  64. http://[::192.9.5.5]/ipng
  65. http://[::FFFF:129.144.52.38]:80/index.html
  66. http://[2010:836B:4179::836B:4179]
  67. 3. Changes to RFC 2396
  68. This document updates the generic syntax for Uniform Resource
  69. Identifiers defined in RFC 2396 [URL]. It defines a syntax for IPv6
  70. addresses and allows the use of "[" and "]" within a URI explicitly
  71. for this reserved purpose.
  72. Hinden, et al. Standards Track [Page 2]
  73. RFC 2732 IPv6 Literal Addresses in URL's December 1999
  74. The following changes to the syntax in RFC 2396 are made:
  75. (1) change the 'host' non-terminal to add an IPv6 option:
  76. host = hostname | IPv4address | IPv6reference
  77. ipv6reference = "[" IPv6address "]"
  78. where IPv6address is defined as in RFC2373 [ARCH].
  79. (2) Replace the definition of 'IPv4address' with that of RFC 2373, as
  80. it correctly defines an IPv4address as consisting of at most three
  81. decimal digits per segment.
  82. (3) Add "[" and "]" to the set of 'reserved' characters:
  83. reserved = ";" | "/" | "?" | ":" | "@" | "&" | "=" | "+" |
  84. "$" | "," | "[" | "]"
  85. and remove them from the 'unwise' set:
  86. unwise = "{" | "}" | "|" | "\" | "^" | "`"
  87. 4. Security Considerations
  88. The use of this approach to represent literal IPv6 addresses in URL's
  89. does not introduce any known new security concerns.
  90. 5. IANA Considerations
  91. None.
  92. Hinden, et al. Standards Track [Page 3]
  93. RFC 2732 IPv6 Literal Addresses in URL's December 1999
  94. 6. Authors' Addresses
  95. Robert M. Hinden
  96. Nokia
  97. 313 Fairchild Drive
  98. Mountain View, CA 94043
  99. USA
  100. Phone: +1 650 625 2004
  101. EMail: hinden@iprg.nokia.com
  102. Web: http://www.iprg.nokia.com/~hinden
  103. Brian E. Carpenter
  104. IBM
  105. iCAIR, Suite 150
  106. 1890 Maple Avenue
  107. Evanston IL 60201
  108. USA
  109. EMail: brian@icair.org
  110. Larry Masinter
  111. AT&T Labs
  112. 75 Willow Road
  113. Menlo Park, CA 94025
  114. EMail: LMM@acm.org
  115. Web: http://larry.masinter.net
  116. 7. References
  117. [ARCH] Hinden, R. and S. Deering, "IP Version 6 Addressing
  118. Architecture", RFC 2373, July 1998.
  119. [STD-PROC] Bradner, S., The Internet Standards Process -- Revision 3,
  120. BCP 9, RFC 2026, October 1996.
  121. [URL] Fielding, R., Masinter, L. and T. Berners-Lee, "Uniform
  122. Resource Identifiers: Generic Syntax", RFC 2396, August
  123. 1998.
  124. Hinden, et al. Standards Track [Page 4]
  125. RFC 2732 IPv6 Literal Addresses in URL's December 1999
  126. 8. Full Copyright Statement
  127. Copyright (C) The Internet Society (1999). All Rights Reserved.
  128. This document and translations of it may be copied and furnished to
  129. others, and derivative works that comment on or otherwise explain it
  130. or assist in its implementation may be prepared, copied, published
  131. and distributed, in whole or in part, without restriction of any
  132. kind, provided that the above copyright notice and this paragraph are
  133. included on all such copies and derivative works. However, this
  134. document itself may not be modified in any way, such as by removing
  135. the copyright notice or references to the Internet Society or other
  136. Internet organizations, except as needed for the purpose of
  137. developing Internet standards in which case the procedures for
  138. copyrights defined in the Internet Standards process must be
  139. followed, or as required to translate it into languages other than
  140. English.
  141. The limited permissions granted above are perpetual and will not be
  142. revoked by the Internet Society or its successors or assigns.
  143. This document and the information contained herein is provided on an
  144. "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
  145. TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
  146. BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
  147. HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
  148. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
  149. Acknowledgement
  150. Funding for the RFC Editor function is currently provided by the
  151. Internet Society.
  152. Hinden, et al. Standards Track [Page 5]