idnits 2.17.1 draft-masinter-url-ipv6-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 166 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. ** There is 1 instance of lines with control characters in the document. == There is 1 instance of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 12, 1998) is 9514 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-03) exists of draft-fielding-uri-syntax-02 Summary: 10 errors (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT L. Masinter, J. Gettys, B. Carpenter 2 draft-masinter-url-ipv6-00 3 Expires six months after publication date March 12, 1998 5 Using IPv6 Addresses in URLs 7 Status of this Memo 9 This document is an Internet-Draft. Internet-Drafts are working 10 documents of the Internet Engineering Task Force (IETF), its areas, 11 and its working groups. Note that other groups may also distribute 12 working documents as Internet-Drafts. 14 Internet-Drafts are draft documents valid for a maximum of six 15 months and may be updated, replaced, or obsoleted by other 16 documents at any time. It is inappropriate to use Internet-Drafts 17 as reference material or to cite them other than as ``work in 18 progress.'' 20 To learn the current status of any Internet-Draft, please check the 21 ``1id-abstracts.txt'' listing contained in the Internet-Drafts 22 Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net 23 (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East 24 Coast), or ftp.isi.edu (US West Coast). 26 Copyright Notice 28 Copyright (C) The Internet Society (1997). All Rights Reserved. 30 Abstract 32 The normal textual representation for IPv6 addresses as a set 33 of colon-separated hexadecimal numbers does not work well with 34 most deployed URL-parsing software. This document describes an 35 alternate format which will pass unharmed through most URL-parsing 36 software. 38 1. Introduction 40 The normal textual representation for IPv6 addresses as a set of 41 colon-separated hexadecimal numbers does not work well with most 42 deployed URL-parsing software. This document describes an alternate 43 format which will pass unharmed through most URL-parsing software. 45 2. Background 47 The standard representation for IPv6 addresses in text [IPV6ADDR] 48 uses embedded colons ":"; in addition, it has been suggested that 49 square brackets "[]" be used isolate the address from any 50 additional text. Thus, an IPv6 address might be written 51 "[ABCD:EF01::2345:10.9.8.7]". 53 Unfortunately, using this IPv6 syntax within URLs [URISYNTAX] would 54 be disruptive of many applications. The colon is used normally to 55 separate the host name or address from an (optional) port number; 56 in some addresses, a colon followed by a decimal number could 57 ambiguously be interpreted as a port designator or part of the IPv6 58 address. Square brackets are not normally allowed in URLs, and may 59 be used as a delimiter around the entire URL. 61 Even if there were no ambiguity, this syntax is incompatible with a 62 very large number of deployed applications that parse (but do not 63 resolve) URLs, including many CGI scripts, robots, search engines, 64 and so forth. 66 In addition, common operating system scripting languages have a 67 special interpretation for square brackets. While it is believed 68 that the use of IPv6 addresses instead of host names will be much 69 rarer than the use of IPv4 addresses, the use is envisioned in 70 emergency situations, e.g., when the domain name system is not 71 functioning: having the syntax be incompatible with operating 72 system command syntax would deny access to network operators just 73 in times when it is needed the most. 75 One of the most important characteristics of Uniform Resource 76 Locators is that they are Uniform: the same syntax is used by all 77 applications. Having different representations for different 78 applications would be confusing and counter-productive. 80 3. Syntax 82 The safest way to embed IPv6 addresses in URLs is to use a syntax 83 which will look like a domain name to otherwise unaware software. 85 The syntax is best described as a transformation of the 86 normal IPv6 syntax: 88 a) replace every colon ":" with a "-" 89 b) append ".ipv6" to the end. 91 Thus, an HTTP service available at port 70 of IPv6 address 92 "ABCD:EF01::2345:10.9.8.7" could be written as 94 http://ABCD-EF01--2345-10.9.8.7.ipv6:70/ 96 This syntax should always be used. Internet software that resolves 97 host names and addresses in URLs should be modified to recognize 98 the "ipv6" pseudo-domain. 100 4. IANA considerations 102 The Internet Assigned Names Authority is requested to reserve 103 the "ipv6" pseudo-domain for the purpose outlined in this memo. 105 5. References 107 [URISYNTAX] R. Fielding, L. Masinter, T. Berners-Lee, "Uniform 108 Resource Identifiers: Generic Syntax", draft-fielding-uri-syntax-02.txt, 109 March, 1998. 111 [IPV6ADDR] R. Hinden, S. Deering. "IP Version 6 Addressing Architecture", 112 draft-ietf-ipngwg-addr-arch-v2-06.txt, January, 1998. 114 6. Authors' Addresses 116 Larry Masinter 117 Xerox Palo Alto Research Center 118 3333 Coyote Hill Road 119 Palo Alto, CA 94034, USA 120 Fax: +1 650 812 4365 121 EMail: masinter@parc.xerox.com 123 James Gettys 124 MIT Laboratory for Computer Science 125 545 Technology Square 126 Cambridge, MA 02139, USA 127 Fax: +1 617 258 8682 128 Email: jg@w3.org 130 Brian Carpenter 131 IBM United Kingdom Laboratories 132 MP 185, Hursley Park 133 Winchester, Hampshire SO21 2JN, UK 134 Email: brian@hursley.ibm.com 136 7. Full Copyright Statement 138 Copyright (C) The Internet Society (1997). All Rights Reserved. 140 This document and translations of it may be copied and furnished to 141 others, and derivative works that comment on or otherwise explain 142 it or assist in its implementation may be prepared, copied, 143 published and distributed, in whole or in part, without restriction 144 of any kind, provided that the above copyright notice and this 145 paragraph are included on all such copies and derivative works. 146 However, this document itself may not be modified in any way, such 147 as by removing the copyright notice or references to the Internet 148 Society or other Internet organizations, except as needed for the 149 purpose of developing Internet standards in which case the 150 procedures for copyrights defined in the Internet Standards process 151 must be followed, or as required to translate it into languages 152 other than English. 154 The limited permissions granted above are perpetual and will not be 155 revoked by the Internet Society or its successors or assigns. 157 This document and the information contained herein is provided on 158 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 159 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 160 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 161 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 162 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.