idnits 2.17.1 draft-ietf-v6ops-ipv4survey-apps-01.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: ---------------------------------------------------------------------------- ** 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. ** 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. == There are 14 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** 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-RFC2606-compliant FQDNs in the document. == There is 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There is 2 instances of lines with multicast IPv4 addresses in the document. If these are generic example addresses, they should be changed to use the 233.252.0.x range defined in RFC 5771 == There is 3 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 897: '... in URLs SHOULD be avoided whenever p...' RFC 2119 keyword, line 1688: '... The property MUST be specified in ...' RFC 2119 keyword, line 1691: '...: The UID itself MUST be a globally un...' RFC 2119 keyword, line 1692: '...f the identifier MUST guarantee that t...' RFC 2119 keyword, line 1694: '...he identifier is RECOMMENDED to be the...' (15 more instances...) 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 (February 2003) is 7733 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: '24' is mentioned on line 898, but not defined == Missing Reference: '13' is mentioned on line 1081, but not defined -- Looks like a reference, but probably isn't: 'RFC-1738' on line 1431 -- Looks like a reference, but probably isn't: 'RFC 822' on line 1695 == Missing Reference: '0' is mentioned on line 2069, but not defined -- Looks like a reference, but probably isn't: 'RFC1884' on line 2323 -- Looks like a reference, but probably isn't: 'RFC 2104' on line 2389 -- Possible downref: Non-RFC (?) normative reference: ref. '1' ** Downref: Normative reference to an Historic RFC: RFC 2874 (ref. '2') ** Obsolete normative reference: RFC 2732 (ref. '4') (Obsoleted by RFC 3986) Summary: 12 errors (**), 0 flaws (~~), 10 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force Rute Sofia 2 Internet Draft Philip J. Nesser II 3 Expiration Date: August 2003 Nesser & Nesser Consulting 4 February 2003 6 Survey of IPv4 Addresses in Currently Deployed 7 IETF Application Area Standards 8 draft-ietf-v6ops-ipv4survey-apps-01.txt 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that other 16 groups may also distribute working documents as Internet- Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six 18 months and may be updated, replaced, or obsoleted by other 19 documents at any time. It is inappropriate to use Internet-Drafts as 20 reference material or to cite them other than as "work in progress." 21 The list of current Internet-Drafts can be accessed at 22 http://www.ietf.org/ietf/1id-abstracts.txt. 23 To view the list Internet-Draft Shadow Directories, see 24 http://www.ietf.org/shadow.html. 26 Abstract 28 The transition from an all IPv4 network to an all IPv6 network 29 requires several interim steps, being one of them the evolution of 30 current IPv4 dependent protocols to protocols that are independent 31 of the type of IP addresses used. Hence, it is hoped that protocols 32 will be redesigned and re-implemented to become network address 33 independent, or at least to dually support IPv4 and IPv6. 34 To achieve that step, it is necessary to survey and document all IPv4 35 dependencies experienced by current standards - Full, Draft, and 36 Proposed - and Experimental RFCs. Hence, this document describes 37 IPv4 addressing dependencies that deployed IETF Application Area 38 documented Standards may experience. 40 Contents 42 1 Introduction 15 44 2 Document Organization 15 46 3 Full Standards 15 47 3.1 RFC821, RFC1869: SMTP Service Extensions . . . . . . . . . . 16 48 3.1.1 RFC 821 . . . . . . . . . . . . . . . . . . . . 16 49 3.1.2 RFC 1869 . . . . . . . . . . . . . . . . . . . . 16 50 3.2 RFC 822: Standard for the format of ARPA Internet 51 text messages . . . . . . . . . . . . . . . . . . . . 16 52 3.3 RFC854, RFC855: Telnet Protocol . . . . . . . . . . . . . . 17 53 3.3.1 RFC 854 . . . . . . . . . . . . . . . . . . . . 17 54 3.3.2 RFC 855 . . . . . . . . . . . . . . . . . . . . 17 55 3.4 RFC 856: Binary Transmission Telnet Option . . . . . . . . . 17 56 3.5 RFC 857: Echo Telnet Option . . . . . . . . . . . . . . . . 17 57 3.6 RFC 858: Suppress Go Ahead Telnet Option . . . . . . . . . . 17 58 3.7 RFC 859: Status Telnet Option . . . . . . . . . . . . . . . 17 59 3.8 RFC 860: Timing Mark Telnet Option . . . . . . . . . . . . . 17 60 3.9 RFC 861: Extended Options List Telnet Option . . . . . . . . 18 61 3.10 RFC 862: Echo Protocol . . . . . . . . . . . . . . . . . . 18 62 3.11 RFC 863: Discard Protocol . . . . . . . . . . . . . . . . . 18 63 3.12 RFC 864: Character Generator Protocol . . . . . . . . . . . 18 64 3.13 RFC 865: Quote of the Day Protocol . . . . . . . . . . . . 18 65 3.14 RFC 866: Active Users Protocol . . . . . . . . . . . . . . 18 66 3.15 RFC 867: Daytime Protocol . . . . . . . . . . . . . . . . . 18 67 3.16 RFC 868: Time Server Protocol . . . . . . . . . . . . . . . 18 68 3.17 RFC 959: File Transfer Protocol (FTP) . . . . . . . . . . . 18 69 3.18 RFC 974: Mail Routing and the Domain System . . . . . . . . 19 70 3.19 RFC 1350: Trivial File Transfer Protocol (TFTP) . . . . . . 19 71 3.20 RFC 1939: Post Office Protocol - Version 3 (POP3) . . . . . 19 72 3.21 RFC 2920: SMTP Service Extension for Command 73 Pipelining (SMTP-pipe) . . . . . . . . . . . . . . . . 19 75 4 Draft Standards 19 76 4.1 RFC 954: NICNAME/WHOIS (NICNAME) . . . . . . . . . . . . . 20 77 4.2 RFC 1184: Telnet Linemode Option (TOPT-LINE) . . . . . . . . 20 78 4.3 RFC 1288: The Finger User Information Protocol 79 (FINGER) . . . . . . . . . . . . . . . . . . . . . . . 20 80 4.4 RFC 1305: Network Time Protocol (Version 3) 81 Specification, Implementation . . . . . . . . . . . . 20 82 4.5 RFC 1575: An Echo Function for CLNP (ISO 8473) 83 (ISO-TS-ECH) . . . . . . . . . . . . . . . . . . . . . 21 84 4.6 RFC 1652: SMTP Service Extension for 8bit-MIME 85 Transport . . . . . . . . . . . . . . . . . . . . . . 22 86 4.7 RFC 1777: Lightweight Directory Access Protocol 87 (LDAP) . . . . . . . . . . . . . . . . . . . . . . . . 22 88 4.8 RFC 1778: The String Representation of Standard 89 Attribute Syntaxes . . . . . . . . . . . . . . . . . . 22 90 4.9 RFC 1832: eXternal Data Representation Standard 91 (XDR) . . . . . . . . . . . . . . . . . . . . . . . . 22 92 4.10 RFC 2045: Multipurpose Internet Mail Extensions 93 (MIME), Part One: Format of Internet Message 94 Bodies (MIME) . . . . . . . . . . . . . . . . . . . . 22 95 4.11 RFC 2046 MIME, Part Two: Media Types (MIME- 96 MEDIA) . . . . . . . . . . . . . . . . . . . . . . . . 22 97 4.12 RFC 2047: MIME, Part Three: Message Header 98 Extensions for Non-ASCII Text (MIME-MSG) . . . . . . . 22 99 4.13 RFC 2049: MIME Part Five: Conformance Criteria 100 and Examples (MIME-CONF) . . . . . . . . . . . . . . . 22 101 4.14 RFC 2279: UTF-8, a transformation format of ISO 102 10646 (UTF-8) . . . . . . . . . . . . . . . . . . . . 23 103 4.15 RFC 2347: TFTP Option Extension (TFTP-Ext) . . . . . . . . 23 104 4.16 RFC 2348: TFTP Blocksize Option (TFTP-Blk) . . . . . . . . 23 105 4.17 RFC 2349: TFTP Timeout Interval and Transfer Size 106 Options (TFTP-Opt) . . . . . . . . . . . . . . . . . . 23 107 4.18 RFC 2355: TN3270 Enhancements (TN3270E) . . . . . . . . . . 23 108 4.19 RFC 2396: Uniform Resource Identifiers (URI): 109 Generic Syntax (URI-GEN) . . . . . . . . . . . . . . . 23 110 4.20 RFC 2616: Hypertext Transfer Protocol � HTTP/1.1 111 (HTTP) . . . . . . . . . . . . . . . . . . . . . . . . 24 113 5 Proposed Standards 24 114 5.1 RFC 698: Telnet extended ASCII option (TOPT-EXT) . . . . . 25 115 5.2 RFC 726: Remote Controlled Transmission and 116 Echoing Telnet option (TOPT-REM) . . . . . . . . . . . 25 117 5.3 RFC 727: Telnet logout option (TOPT-LOGO) . . . . . . . . . 25 118 5.4 RFC 735: Revised Telnet byte macro option (TOPT- 119 BYTE) . . . . . . . . . . . . . . . . . . . . . . . . 25 120 5.5 RFC 736: Telnet SUPDUP option (TOPT-SUP) . . . . . . . . . . 25 121 5.6 RFC 749: Telnet SUPDUP-Output option (TOPT- 122 SUPO) . . . . . . . . . . . . . . . . . . . . . . . . 25 123 5.7 RFC 779: Telnet send-location option (TOPT-SNDL) . . . . . . 25 124 5.8 RFC 885: Telnet end of record option (TOPT-EOR) . . . . . . 25 125 5.9 RFC 927: TACACS user identification Telnet option 126 (TOPT-TACAC) . . . . . . . . . . . . . . . . . . . . . 25 127 5.10 RFC 933: Output marking Telnet option (TOPT-OM) . . . . . . 26 128 5.11 RFC 946: Telnet terminal location number option 129 (TOPT-TLN) . . . . . . . . . . . . . . . . . . . . . . 26 130 5.12 RFC 977: Network News Transfer Protocol (NNTP) 26 131 5.13 RFC 1041: Telnet 3270 regime option (TOPT-3270) . . . . . . 26 132 5.14 RFC 1043: Telnet Data Entry Terminal option: 133 DODIIS implementation (TOPT-DATA) . . . . . . . . . . 26 134 5.15 RFC 1053: Telnet X.3 PAD option (TOPT-X.3) . . . . . . . . 26 135 5.16 RFC 1073: Telnet window size option (TOPT-NAWS) . . . . . . 27 136 5.17 RFC 1079: Telnet terminal speed option (TOPT-TS) . . . . . 27 137 5.18 RFC 1091: Telnet terminal-type option (TOPT-TERM) . . . . . 27 138 5.19 RFC 1096: Telnet X display location option (TOPT- 139 XDL) . . . . . . . . . . . . . . . . . . . . . . . . . 27 140 5.20 RFC 1274: The COSINE and Internet X.500 Schema . . . . . . 27 141 5.21 RFC 1276: Replication and Distributed Operationsi extensions 142 to provide an Internet Directory using X.500 . . . . . 27 143 5.22 RFC 1314: A File Format for the Exchange of 144 Images in the Internet (NETFAX) . . . . . . . . . . . 27 145 5.23 RFC 1328: X.400 1988 to 1984 downgrading . . . . . . . . . 27 146 5.24 RFC 1372: Telnet Remote Flow Control Option 147 (TOPT-RFC) . . . . . . . . . . . . . . . . . . . . . . 27 149 5.25 RFC 1415: FTP-FTAM Gateway Specification 150 (FTP-FTAM) . . . . . . . . . . . . . . . . . . . . . . 28 151 5.26 RFC 1494: Equivalences between 1988 X.400 and 152 RFC-822 Message Bodies (Equiv) . . . . . . . . . . . . 28 153 5.27 RFC 1496: Rules for downgrading messages from 154 X.400/88 to X.400/84 when MIME content-types are 155 present in the messages (HARPOON) . . . . . . . . . . 28 156 5.28 RFC 1502: X.400 Use of Extended Character Sets . . . . . . 28 157 5.29 RFC 1572: Telnet Environment Option (TOPT- 158 ENVIR) . . . . . . . . . . . . . . . . . . . . . . . . 28 159 5.30 RFC 1648: Postmaster Convention for X.400 160 Operations . . . . . . . . . . . . . . . . . . . . . . 28 161 5.31 RFC 1738: Uniform Resource Locators (URL) (URL) 28 162 5.32 RFC 1740: MIME Encapsulation of Macintosh Files 163 - MacMIME (MacMIME) . . . . . . . . . . . . . . . . . 29 164 5.33 RFC 1767: MIME Encapsulation of EDI Objects 165 (MIME-EDI) . . . . . . . . . . . . . . . . . . . . . . 29 166 5.34 RFC 1781: Using the OSI Directory to Achieve User 167 Friendly Naming (OSI-Dir) . . . . . . . . . . . . . . 29 168 5.35 RFC 1798: Connection-less Lightweight X.500 169 Directory Access Protocol (CLDAP) . . . . . . . . . . 29 170 5.36 RFC 1808: Relative Uniform Resource Locators (URL) 30 171 5.37 RFC 1835: Architecture of the WHOIS++ service 172 (WHOIS++) . . . . . . . . . . . . . . . . . . . . . . 30 173 5.38 RFC 1891: SMTP Service Extension for Delivery 174 Status Notifications (SMTP-DSN) . . . . . . . . . . . 30 175 5.39 RFC 1892: The Multipart/Report Content Type 176 for the Reporting of Mail System Administrative 177 Messages (MIME-RPT) . . . . . . . . . . . . . . . . . 30 178 5.40 RFC 1893: Enhanced Mail System Status Codes 179 (EMS-CODE) . . . . . . . . . . . . . . . . . . . . . . 30 180 5.41 RFC 1894: An Extensible Message Format for 181 Delivery Status Notifications (DSN) . . . . . . . . . 30 182 5.42 RFC 1913: Architecture of the Whois++ Index 183 Service,WHOIS++A . . . . . . . . . . . . . . . . . . . 31 184 5.43 RFC 1914: How to Interact with a Whois++ Mesh 185 (WHOIS++) . . . . . . . . . . . . . . . . . . . . . . 31 187 5.44 RFC 1985: SMTP Service Extension for Remote 188 Message Queue Starting (SMTP-ETRN) . . . . . . . . . 32 189 5.45 RFC 2017: Definition of the URL MIME External- 190 Body Access-Type (URL-ACC) . . . . . . . . . . . . . 32 191 5.46 RFC 2034: SMTP Service Extension for Returning 192 Enhanced Error Codes (SMTP-ENH) . . . . . . . . . . . 33 193 5.47 RFC 2056: Uniform Resource Locators for Z39.50 194 (URLZ39.50) . . . . . . . . . . . . . . . . . . . . . 33 195 5.48 RFC 2060: Internet Message Access Protocol - 196 Version 4rev1 (IMAPV4) . . . . . . . . . . . . . . . 33 197 5.49 RFC 2077: The Model Primary Content Type 198 for Multipurpose Internet Mail Extensions (MIME- 199 MODEL) . . . . . . . . . . . . . . . . . . . . . . . 33 200 5.50 RFC 2079: Definition of an X.500 Attribute Type 201 and an Object Class to Hold Uniform Resource 202 Identifiers (URIs) (URI-ATT) . . . . . . . . . . . . 33 203 5.51 RFC 2086: IMAP4 ACL extension (IMAP4-ACL) . . . . . . . . 33 204 5.52 RFC 2087: IMAP4 QUOTA extension (IMAP4-QUO) . . . . . . . 33 205 5.53 RFC 2088: IMAP4 non-synchronizing literals 206 (IMAP4-LIT) . . . . . . . . . . . . . . . . . . . . . 33 207 5.54 RFC 2122: VEMMI URL Specification (VEMMI- 208 URL) . . . . . . . . . . . . . . . . . . . . . . . . 34 209 5.55 RFC 2141: URN Syntax (URN-SYNTAX) . . . . . . . . . . . . 34 210 5.56 RFC 2142 "Mailbox Names for Common Services, 211 Roles and Functions" (MAIL-SERV) . . . . . . . . . . 34 212 5.57 RFC 2156: MIXER (Mime Internet X.400 213 Enhanced Relay): Mapping between X.400 and 214 RFC 822/MIME (MIXER) . . . . . . . . . . . . . . . . 34 215 5.58 RFC 2157: Mapping between X.400 and RFC- 216 822/MIME Message Bodies . . . . . . . . . . . . . . . 34 217 5.59 RFC 2158: X.400 Image Body Parts . . . . . . . . . . . . . 35 218 5.60 RFC 2159: A MIME Body Part for FAX . . . . . . . . . . . . 35 219 5.61 RFC 2160: Carrying PostScript in X.400 and MIME 35 220 5.62 RFC 2163: Using the Internet DNS to Distribute 221 MIXER Conformant Global Address Mapping 222 (MCGAM) (DNS-MCGAM) . . . . . . . . . . . . . . . . . 35 223 5.63 RFC 2164: Use of an X.500/LDAP directory to 224 support MIXER address mapping . . . . . . . . . . . . 35 226 5.64 RFC 2165: Service Location Protocol (SLP) . . . . . . . . 35 227 5.65 RFC 2177: IMAP4 IDLE command (IMAP4-IDLE) 37 228 5.66 RFC 2183: Communicating Presentation 229 Information in Internet Messages: The Content- 230 Disposition Header Field . . . . . . . . . . . . . . . 37 231 5.67 RFC 2192: IMAP URL Scheme (IMAP-URL) . . . . . . . . . . . 37 232 5.68 RFC 2193: IMAP4 Mailbox Referrals (IMAP4MAIL) . . . . . . . 37 233 5.69 RFC 2218: A Common Schema for the Internet 234 White Pages Service . . . . . . . . . . . . . . . . . 38 235 5.70 RFC 2221: IMAP4 Login Referrals (IMAP4LOGIN) . . . . . . . 38 236 5.71 RFC 2227: Simple Hit-Metering and Usage- 237 Limiting for HTTP . . . . . . . . . . . . . . . . . . 38 238 5.72 RFC 2231: MIME Parameter Value and Encoded 239 Word Extensions: Character Sets, Languages, and 240 Continuations (MIME-EXT) . . . . . . . . . . . . . . . 38 241 5.73 RFC 2234: Augmented BNF for Syntax 242 Specifications: ABNF (ABNF) . . . . . . . . . . . . . 38 243 5.74 RFC 2244: Application Configuration Access 244 Protocol (ACAP) . . . . . . . . . . . . . . . . . . . 38 245 5.75 RFC 2254 The String Representation of LDAP 246 Search Filters (STR-LDAP) . . . . . . . . . . . . . . 39 247 5.76 RFC 2255: The LDAP URL Format (LDAP-URL) . . . . . . . . . 39 248 5.77 RFC 2247 Using Domains in LDAP/X.500 249 Distinguished Names . . . . . . . . . . . . . . . . . 39 250 5.78 RFC 2251 Lightweight Directory Access Protocol 251 (v3) (LDAPV3) . . . . . . . . . . . . . . . . . . . . 39 252 5.79 RFC 2252: Lightweight Directory Access Protocol 253 (v3): Attribute Syntax Definitions (LDAP3-ATD) . . . . 39 254 5.80 RFC 2253: Lightweight Directory Access Protocol 255 (v3): UTF-8 String Representation of Distinguished 256 Names (LDAP3-UTF8) . . . . . . . . . . . . . . . . . . 39 257 5.81 RFC 2256: A Summary of the X.500(96) User 258 Schema for use with LDAPv3 . . . . . . . . . . . . . . 40 259 5.82 RFC 2293: Representing Tables and Subtrees in the 260 X.500 Directory (SUBTABLE) . . . . . . . . . . . . . . 40 261 5.83 RFC 2294: Representing the O/R Address hierarchy 262 in the X.500 Directory Information Tree (OR-ADD) . . . 40 264 5.84 RFC 2298: An Extensible Message Format for 265 Message Disposition Notifications (EMF-MDN) . . . . . 40 266 5.85 RFC 2301: File Format for Internet Fax (FFIF) . . . . . . . 40 267 5.86 RFC 2302: Tag Image File Format (TIFF) - 268 image/tiff MIME Sub-type Registration (TIFF) . . . . . 40 269 5.87 RFC 2303: Minimal PSTN address format in Internet 270 Mail (MIN-PSTN) . . . . . . . . . . . . . . . . . . . 40 271 5.88 RFC 2304: Minimal FAX address format in Internet 272 Mail (MINFAX-IM) . . . . . . . . . . . . . . . . . . . 40 273 5.89 RFC 2305: A Simple Mode of Facsimile Using 274 Internet Mail (SMFAX-IM) . . . . . . . . . . . . . . . 41 275 5.90 RFC 2334: Server Cache Synchronization Protocol 276 (SCSP) (SCSP) . . . . . . . . . . . . . . . . . . . . 41 277 5.91 RFC 2342: IMAP4 Namespace (IMAP4NAME) . . . . . . . . . . . 41 278 5.92 RFC 2359: IMAP4 UIDPLUS extension 279 (IMAP4UIDPL) . . . . . . . . . . . . . . . . . . . . . 41 280 5.93 RFC 2368: The mailto URL scheme (URLMAILTO) 41 281 5.94 RFC 2369: The Use of URLs as Meta-Syntax 282 for Core Mail List Commands and their Transport 283 through Message Header Fields . . . . . . . . . . . . 41 284 5.95 RFC 2384: POP URL Scheme (POP-URL) . . . . . . . . . . . . 42 285 5.96 RFC 2387: The MIME Multipart/Related Content- 286 type (MIME-RELAT) . . . . . . . . . . . . . . . . . . 42 287 5.97 RFC 2388: Returning Values from Forms: 288 multipart/form-data . . . . . . . . . . . . . . . . . 42 289 5.98 RFC 2389: Feature negotiation mechanism for the 290 File Transfer Protocol . . . . . . . . . . . . . . . . 42 291 5.99 RFC 2392: Content-ID and Message-ID Uniform 292 Resource Locators (CIDMID-URL) . . . . . . . . . . . . 42 293 5.100 RFC 2397: The "data" URL scheme (DATA-URL) . . . . . . . . 42 294 5.101 RFC 2421: Voice Profile for Internet Mail - version 295 2 (MIME-VP2) . . . . . . . . . . . . . . . . . . . . 43 296 5.102 RFC 2422: Toll Quality Voice - 32 kbit/s ADPCM 297 MIME Sub-type Registration (MIME-ADPCM) . . . . . . . 43 298 5.103 RFC 2423 VPIM Voice Message MIME Sub-type 299 Registration (MIME-VPIM) . . . . . . . . . . . . . . . 43 301 5.104 RFC 2424: Content Duration MIME Header 302 Definition (CONT-DUR) . . . . . . . . . . . . . . . . 43 303 5.105 RFC 2425: A MIME Content-Type for Directory 304 Information (TXT-DIR) . . . . . . . . . . . . . . . . 43 305 5.106 RFC 2426: vCard MIME Directory Profile (MIME- 306 VCARD) . . . . . . . . . . . . . . . . . . . . . . . . 43 307 5.107 RFC 2428: FTP Extensions for IPv6 and NATs . . . . . . . . 43 308 5.108 RFC 2445: Internet Calendaring and Scheduling 309 Core Object Specification (iCalendar) (ICALENDAR) . . 43 310 5.109 RFC 2446: iCalendar Transport-Independent 311 Interoperability Protocol (iTIP) Scheduling Events, 312 BusyTime, To-dos and Journal Entries (ITIP) . . . . . 44 313 5.110 RFC 2447: iCalendar Message-Based 314 Interoperability Protocol (iMIP) (IMIP) . . . . . . . 45 315 5.111 RFC 2449: POP3 Extension Mechanism (POP3-EXT) . . . . . . 45 316 5.112 RFC 2476: Message Submission . . . . . . . . . . . . . . . 45 317 5.113 RFC 2480: Gateways and MIME Security Multiparts . . . . . 45 318 5.114 RFC 2518: HTTP Extensions for Distributed 319 Authoring � WEBDAV (WEBDAV) . . . . . . . . . . . . . 45 320 5.115 RFC 2530: Indicating Supported Media Features 321 Using Extensions to DSN and MDN . . . . . . . . . . . 45 322 5.116 RFC 2532: Extended Facsimile Using Internet Mail . . . . . 45 323 5.117 RFC 2533: A Syntax for Describing Media Feature 324 Sets . . . . . . . . . . . . . . . . . . . . . . . . . 45 325 5.118 RFC 2534: Media Features for Display, Print, and Fax . . . 46 326 5.119 RFC 2554: SMTP Service Extension for 327 Authentication . . . . . . . . . . . . . . . . . . . . 46 328 5.120 RFC 2557: MIME Encapsulation of Aggregate 329 Documents, such as HTML (MHTML) (MHTML) . . . . . . . 46 330 5.121 RFC 2589: Lightweight Directory Access Protocol 331 (v3): Extensions for Dynamic Directory Services 332 (LDAPv3) . . . . . . . . . . . . . . . . . . . . . . . 46 333 5.122 RFC 2595: Using TLS with IMAP, POP3 and ACAP . . . . . . . 46 334 5.123 RFC 2596 Use of Language Codes in LDAP . . . . . . . . . . 46 335 5.124 RFC 2608: Service Location Protocol, Version 2 (SLP) . . . 47 336 5.125 RFC 2609: Service Templates and Service: Schemes . . . . . 48 337 5.126 RFC 2640: Internationalization of the File Transfer 338 Protocol . . . . . . . . . . . . . . . . . . . . . . . 48 339 5.127 RFC 2645: ON-DEMAND MAIL RELAY (ODMR) 340 SMTP with Dynamic IP Addresses (ODMR-SMTP) . . . . . . 48 341 5.128 RFC 2646: The Text/Plain Format Parameter . . . . . . . . 48 342 5.129 RFC 2651: The Architecture of the Common 343 Indexing Protocol (CIP) (CIP) . . . . . . . . . . . . 48 344 5.130 RFC 2652: MIME Object Definitions for the 345 Common Indexing Protocol (CIP) . . . . . . . . . . . . 48 346 5.131 RFC 2653: CIP Transport Protocols . . . . . . . . . . . . 49 347 5.132 RFC 2732: Format for Literal IPv6 Addresses in URL's . . . 49 348 5.133 RFC 2738: Corrections to "A Syntax for Describing 349 Media Feature Sets" . . . . . . . . . . . . . . . . . 49 350 5.134 RFC 2739: Calendar Attributes for vCard and LDAP 49 351 5.135 RFC 2806: URLs for Telephone Calls . . . . . . . . . . . 49 352 5.136 RFC 2846: GSTN Address Element Extensions in 353 E-mail Services . . . . . . . . . . . . . . . . . . . 49 354 5.137 RFC 2849: The LDAP Data Interchange Format 355 (LDIF) - Technical Specification (LDIF) . . . . . . . 49 356 5.138 RFC 2852: Deliver By SMTP Service Extension . . . . . . . 49 357 5.139 RFC 2879: Content Feature Schema for Internet Fax 358 (V2) . . . . . . . . . . . . . . . . . . . . . . . . . 49 359 5.140 RFC 2891: LDAP Control Extension for Server Side 360 Sorting of Search Results . . . . . . . . . . . . . . 50 361 5.141 RFC 2910: Internet Printing Protocol/1.1: Encoding 362 and Transport (IPP-E-T) . . . . . . . . . . . . . . . 50 363 5.142 RFC 2911: Internet Printing Protocol/1.1: Model 364 and Semantics (IPP-M-S) . . . . . . . . . . . . . . . 50 365 5.143 RFC 2912: Indicating Media Features for MIME 366 Content . . . . . . . . . . . . . . . . . . . . . . . 50 367 5.144 RFC 2913: MIME Content Types in Media Feature 368 Expressions . . . . . . . . . . . . . . . . . . . . . 50 369 5.145 RFC 2919: List-Id: A Structured Field and 370 Namespace for the Identification of Mailing Lists . . 50 371 5.146 RFC 2938: Identifying Composite Media Features . . . . . . 50 372 5.147 RFC 2965: HTTP State Management Mechanism . . . . . . . . 50 373 5.148 RFC 2971: IMAP4 ID extension . . . . . . . . . . . . . . . 51 374 5.149 RFC 2987: Registration of Charset and Languages 375 Media Features Tags . . . . . . . . . . . . . . . . . 51 376 5.150 RFC 3009: Registration of parityfec MIME types . . . . . . 51 377 5.151 RFC 3017: XML DTD for Roaming Access Phone 378 Book . . . . . . . . . . . . . . . . . . . . . . . . . 51 379 5.152 RFC 3023: XML Media Types . . . . . . . . . . . . . . . . 52 380 5.153 RFC 3028: Sieve: A Mail Filtering Language . . . . . . . . 52 381 5.154 RFC 3030: SMTP Service Extensions for 382 Transmission of Large and Binary MIME Messages . . . . 52 383 5.155 RFC 3049: TN3270E Service Location and Session 384 Balancing . . . . . . . . . . . . . . . . . . . . . . 52 385 5.156 RFC 3059: Attribute List Extension for the Service 386 Location Protocol (SLPv2) . . . . . . . . . . . . . . 52 387 5.157 RFC 3080: The Blocks Extensible Exchange 388 Protocol Core (BEEP) . . . . . . . . . . . . . . . . . 52 389 5.158 RFC 3081: Mapping the BEEP Core onto TCP . . . . . . . . . 52 390 5.159 RFC 3111: Service Location Protocol Modifications 391 for IPv6 . . . . . . . . . . . . . . . . . . . . . . . 52 393 6 Experimental RFCs 53 394 6.1 RFC 909: Loader Debugger Protocol (LDP) . . . . . . . . . . 53 395 6.2 RFC 1143: The Q Method of Implementing 396 TELNET Option Negotiation . . . . . . . . . . . . . . 53 397 6.3 RFC 1153: Digest message format (DMF-MAIL) . . . . . . . . . 53 398 6.4 RFC 1159: Message Send Protocol . . . . . . . . . . . . . . 53 399 6.5 RFC 1165: Network Time Protocol (NTP) over the 400 OSI Remote Operations Service (NTP-OSI) . . . . . . . 53 401 6.6 RFC 1176: Interactive Mail Access Protocol: 402 Version 2 (IMAP2) . . . . . . . . . . . . . . . . . . 54 403 6.7 RFC 1204: Message Posting Protocol (MPP) (MPP) . . . . . . . 54 404 6.8 RFC 1235: Coherent File Distribution Protocol (CFDP) . . . . 54 405 6.9 RFC 1279: X.500 and Domains . . . . . . . . . . . . . . . . 55 406 6.10 RFC 1312: Message Send Protocol 2 (MSP2) . . . . . . . . . 55 407 6.11 RFC 1339: Remote Mail Checking Protocol (RMCP) . . . . . . 55 408 6.12 RFC 1440: SIFT/UFT: Sender-Initiated/Unsolicited 409 File Transfer (SIFT) . . . . . . . . . . . . . . . . . 55 410 6.13 RFC 1459: Internet Relay Chat Protocol (IRCP) . . . . . . . 55 411 6.14 RFC 1465: Routing Coordination for X.400 MHS 412 Services Within a Multi Protocol / Multi Network 413 Environment Table Format V3 for Static Routing . . . . 56 414 6.15 RFC 1505: Encoding Header Field for Internet 415 Messages (EHF-MAIL) . . . . . . . . . . . . . . . . . 56 416 6.16 RFC 1528: Principles of Operation for the TPC.INT 417 Subdomain: Remote Printing � Technical Procedures 418 (REM-PRINT) . . . . . . . . . . . . . . . . . . . . . 56 419 6.17 RFC 1608: Representing IP Information in the X.500 420 Directory (X500-DIR) . . . . . . . . . . . . . . . . . 56 421 6.18 RFC 1609: Charting Networks in the X.500 422 Directory (X500-CHART) . . . . . . . . . . . . . . . . 56 423 6.19 RFC 1639: FTP Operation Over Big Address 424 Records (FOOBAR) . . . . . . . . . . . . . . . . . . . 56 425 6.20 RFC 1641 Using Unicode with MIME (MIME-UNI) . . . . . . . . 56 426 6.21 RFC 1756: Remote Write Protocol - Version 1.0 (RWP) . . . . 56 427 6.22 RFC 1801: MHS use of the X.500 Directory to 428 support MHS Routing . . . . . . . . . . . . . . . . . 57 429 6.23 RFC 1804: Schema Publishing in X.500 Directory . . . . . . 57 430 6.24 RFC 1806: Communicating Presentation 431 Information in Internet Messages: The Content- 432 Disposition Header . . . . . . . . . . . . . . . . . . 57 433 6.25 RFC 1845: SMTP Service Extension for 434 Checkpoint/Restart . . . . . . . . . . . . . . . . . . 57 435 6.26 RFC 1846: SMTP 521 Reply Code . . . . . . . . . . . . . . . 57 436 6.27 RFC 1873: Message/External-Body Content-ID 437 Access Type (CONT-MT) . . . . . . . . . . . . . . . . 57 438 6.28 RFC 1874: SGML Media Types (SGML-MT) . . . . . . . . . . . 57 439 6.29 RFC 1986: Experiments with a Simple File Transfer 440 Protocol for Radio Links using Enhanced Trivial File 441 Transfer Protocol (ETFTP) . . . . . . . . . . . . . . 57 442 6.30 RFC 2016: Uniform Resource Agents (URAs) (URAS) 58 443 6.31 RFC 2066: TELNET CHARSET Option (TOPT- 444 CHARS) . . . . . . . . . . . . . . . . . . . . . . . . 58 446 6.32 RFC 2075: IP Echo Host Service (IP-Echo) . . . . . . . . . 58 447 6.33 RFC 2090: TFTP Multicast Option (TFTP-MULTI) . . . . . . . 58 448 6.34 RFC 2120: Managing the X.500 Root Naming 449 Context (X.500-NAME) . . . . . . . . . . . . . . . . . 58 450 6.35 RFC 2161: A MIME Body Part for ODA (MIME- 451 ODA) . . . . . . . . . . . . . . . . . . . . . . . . . 58 452 6.36 RFC 2162: MaXIM-11 - Mapping between X.400 / 453 Internet mail and Mail-11 mail (MAP-MAIL) . . . . . . 59 454 6.37 RFC 2168: Resolution of Uniform Resource 455 Identifiers using the Domain Name System . . . . . . . 59 456 6.38 RFC 2169: A Trivial Convention for using HTTP in 457 URN Resolution . . . . . . . . . . . . . . . . . . . . 59 458 6.39 RFC 2217: Telnet Com Port Control Option (TOPT- 459 COMPO) . . . . . . . . . . . . . . . . . . . . . . . . 59 460 6.40 RFC 2295: Transparent Content Negotiation in 461 HTTP (TCN-HTTP) . . . . . . . . . . . . . . . . . . . 59 462 6.41 RFC 2296: HTTP Remote Variant Selection 463 Algorithm � RVSA/1.0 (HTTP-RVSA) . . . . . . . . . . . 59 464 6.42 RFC 2307: An Approach for Using LDAP as a 465 Network Information Service (LDAP-NIS) . . . . . . . . 59 466 6.43 RFC 2310: The Safe Response Header Field . . . . . . . . . 60 467 6.44 RFC 2483: URI Resolution Services Necessary for 468 URN Resolution . . . . . . . . . . . . . . . . . . . . 60 469 6.45 RFC 2567: Design Goals for an Internet Printing 470 Protocol (IPP-DG) . . . . . . . . . . . . . . . . . . 60 471 6.46 RFC 2568: Rationale for the Structure of the Model 472 and Protocol for the Internet Printing Protocol (IPP- 473 RAT) . . . . . . . . . . . . . . . . . . . . . . . . . 61 474 6.47 RFC 2569: Mapping between LPD and IPP Protocols . . . . . . 61 475 6.48 RFC 2649: An LDAP Control and Schema for 476 Holding Operation Signatures . . . . . . . . . . . . 61 477 6.49 RFC 2654: A Tagged Index Object for use in the 478 Common Indexing Protocol . . . . . . . . . . . . . . . 61 479 6.50 RFC 2655: CIP Index Object Format for SOIF Objects 61 480 6.51 RFC 2656: Registration Procedures for SOIF 481 Template Types . . . . . . . . . . . . . . . . . . . . 61 482 6.52 RFC 2657: LDAPv2 Client vs. the Index Mesh . . . . . . . . 61 483 6.53 RFC 2756: Hyper Text Caching Protocol 484 (HTCP/0.0) (HTCP) . . . . . . . . . . . . . . . . . . 61 485 6.54 RFC 2774: An HTTP Extension Framework . . . . . . . . . . . 62 486 6.55 RFC 2974: Session Announcement Protocol (SAP) . . . . . . . 62 487 6.56 RFC 3018: Unified Memory Space Protocol 488 Specification . . . . . . . . . . . . . . . . . . . . 62 489 6.57 RFC 3082: Notification and Subscription for SLP . . . . . . 62 490 6.58 RFC 3088: OpenLDAP Root Service An 491 experimental LDAP referral service . . . . . . . . . . 63 493 7 Summary of Results 63 494 7.1 Full Standards . . . . . . . . . . . . . . . . . . . . . . . 63 495 7.1.1 RFC 959: STD 9 File Transfer Protocol . . . . . 63 496 7.1.2 RFC 821: STD 10 Simple Mail Transfer 497 Protocol . . . . . . . . . . . . . . . . . . . 64 498 7.1.3 RFC 822: STD 11 Standard for the format of 499 ARPA Internet Text Messages . . . . . . . . . . 64 500 7.1.4 RFC 1305: STD 12 Network Time Protocol . . . . . 64 501 7.2 Draft Standards . . . . . . . . . . . . . . . . . . . . . . 64 502 7.2.1 RFC 1305: Network Time Protocol (NTP) . . . . . 64 503 7.2.2 RFC 2396: Uniform Resource Identifiers 504 (URI) Syntax . . . . . . . . . . . . . . . . . 64 505 7.2.3 RFC 2616: HTTP . . . . . . . . . . . . . . . . . 64 506 7.3 Proposed Standards . . . . . . . . . . . . . . . . . . . . . 64 507 7.3.1 RFC 946: Telnet Terminal LOC . . . . . . . . . . 64 508 7.3.2 RFC 1738: Uniform Resource Locators (URL) . . . 65 509 7.3.3 RFC 2384: POP3 URL Scheme . . . . . . . . . . . 65 510 7.3.4 RFC 2608:SLP v2 . . . . . . . . . . . . . . . . 65 511 7.3.5 RFC 3017: XML DTP For Roaming Access 512 Phone Books . . . . . . . . . . . . . . . . . . 65 513 7.4 Experimental RFCs . . . . . . . . . . . . . . . . . . . . . 65 514 7.4.1 RFC 1235:The Coherent File Distribution 515 Protocol . . . . . . . . . . . . . . . . . . . 65 516 7.4.2 RFC 1459: IRC Protocol . . . . . . . . . . . . . 65 517 7.4.3 RFC 1986: Simple File Transfer Using 518 Enhanced TFTP . . . . . . . . . . . . . . . . . 65 519 7.4.4 RFC 2090: TFTP Multicast Option . . . . . . . . 65 520 7.4.5 RFC 2307: Using LDAP as a NIS (RFC 2307) . . . 66 522 8 Acknowledgements 66 524 9 Security Considerations 66 526 1 Introduction 528 The exhaustive documentation of IPv4 addresses usage in currently 529 deployed IETF documented standards has now been broken 530 into seven documents conforming to current IETF main areas - 531 Applications, Internet, Operations and Management, Routing, Sub- 532 IP, and Transport. A general overview of the documentation, as well 533 as followed methodology and historical perspective can be found in 534 [1]. 535 This document represents one of the seven blocks, and its scope 536 is limited to the use of IPv4 addresses in IETF Application Area 537 documented Standards. 539 2 Document Organization 541 The remainder sections are organized as follows. Sections 3, 4, 5, and 542 6 describe, respectively, the raw analysis of Internet Standards [3]: 543 Full, Draft and Proposed Standards, and Experimental RFCs. For 544 each section, standards are analysed by their RFC sequential order, 545 i.e., from RFC 1 to RFC 3247. Also, the comments presented for 546 each RFC are raw in their nature, i.e., each RFC is simply analysed 547 in terms of possible IPv4 addressing dependencies. Finally, Section 548 7 presents a global overview of the data described in the previous 549 sections, and suggests possible future steps. 551 3 Full Standards 553 Internet Full Standards attain the highest level of maturity on 554 the standards track process. They are commonly referred to as 555 "Standards", and represent fully technical mature specifications, 556 widely implemented and used throughout the Internet. 558 3.1 RFC821, RFC1869: SMTP Service Extensions 560 3.1.1 RFC 821 562 Section 4.1.2 "Command Syntax" contains the following clear IPv4 563 reference: 565 " ::= "." "." "." " 567 Also, the following paragraph needs to be re-written, to eliminate 568 the explicit reference to a 32-bit ARPA Internet Address in four 569 8-bit fields: 571 "Sometimes a host is not known to the translation function and 572 communication is blocked. To bypass this barrier two numeric forms 573 are also allowed for host 'names'. One form is a decimal integer 574 prefixed by a pound sign, "#", which indicates the number is the 575 address of the host. Another form is four small decimal integers 576 separated by dots and enclosed by brackets, e.g., "[123.255.37.2]". 578 3.1.2 RFC 1869 580 There are no IPv4 dependencies in RFC 1869. 582 3.2 RFC 822: Standard for the format of ARPA Internet 583 text messages 585 There are some IPv4 dependencies in RFC 822, which needs to be 586 re-written. Section 6.2.3. (Domain Terms) contains the following 587 text: 589 "A domain-ref must be THE official name of a registry, network, 590 or host. It is a symbolic reference, within a name sub-domain. At 591 times, it is necessary to bypass standard mechanisms for resolving 592 such references, using more primitive information, such as a network 593 host address rather than its associated host name. 594 To permit such references, this standard provides the domain-literal 595 construct. Its contents must conform with the needs of the sub- 596 domain in which it is interpreted. 597 Domain-literals which refer to domains within the ARPA Internet 598 specify 32-bit Internet addresses, in four 8-bit fields noted in 599 decimal, as described in Request for Comments #820,"Assigned Numbers." 600 For example: 601 [10.0.3.19] 602 Note: THE USE OF DOMAIN-LITERALS IS STRONGLY 603 DISCOURAGED. 604 It is permitted only as a means of bypassing temporary system 605 limitations, 606 such as name tables which are not complete." 608 3.3 RFC854, RFC855: Telnet Protocol 610 3.3.1 RFC 854 612 There are no IPv4 dependencies in RFC 854. 614 3.3.2 RFC 855 616 There are no IPv4 dependencies in RFC 855. 618 3.4 RFC 856: Binary Transmission Telnet Option 620 There are no IPv4 dependencies in this protocol. 622 3.5 RFC 857: Echo Telnet Option 624 There are no IPv4 dependencies in this protocol. 626 3.6 RFC 858: Suppress Go Ahead Telnet Option 628 There are no IPv4 dependencies in this protocol. 630 3.7 RFC 859: Status Telnet Option 632 There are no IPv4 dependencies in this protocol. 634 3.8 RFC 860: Timing Mark Telnet Option 636 There are no IPv4 dependencies in this protocol. 638 3.9 RFC 861: Extended Options List Telnet Option 640 There are no IPv4 dependencies in this protocol. 642 3.10 RFC 862: Echo Protocol 644 There are no IPv4 dependencies in this protocol. 646 3.11 RFC 863: Discard Protocol 648 There are no IPv4 dependencies in this protocol. 650 3.12 RFC 864: Character Generator Protocol 652 There are no IPv4 dependencies in this protocol. 654 3.13 RFC 865: Quote of the Day Protocol 656 There are no IPv4 dependencies in this protocol. 658 3.14 RFC 866: Active Users Protocol 660 There are no IPv4 dependencies in this protocol. 662 3.15 RFC 867: Daytime Protocol 664 There are no IPv4 dependencies in this protocol. 666 3.16 RFC 868: Time Server Protocol 668 There are no IPv4 dependencies in this protocol. 670 3.17 RFC 959: File Transfer Protocol (FTP) 672 Section 4.1.2 (TRANSFER PARAMETER COMMANDS) describes 673 the port command using the following format: 675 "A port command would be: 676 PORT h1,h2,h3,h4,p1,p2 677 where h1 is the high order 8 bits of the internet host address." 679 This is a clear reference to an IPv4 address. In sections 4.2.1 and 680 4.2.2, on reply codes, the code: 682 "227 Entering Passive Mode (h1,h2,h3,h4,p1,p2)" 684 also needs to be reworked for IPv6 addressing. Also, Section 5.3.2 685 (FTP COMMAND ARGUMENTS) contains: 687 " ::= ,,, 688 ::= , ::= any decimal 689 integer 1 through 255" 691 This needs to be solved to transition to IPv6. 693 3.18 RFC 974: Mail Routing and the Domain System 695 Section Examples uses the well established A records, whose clear 696 IPv4 dependency has already been investigated in [2]. 698 3.19 RFC 1350: Trivial File Transfer Protocol (TFTP) 700 There are no IPv4 dependencies in this protocol. 702 3.20 RFC 1939: Post Office Protocol - Version 3 (POP3) 704 There are no IPv4 dependencies in this protocol. 706 3.21 RFC 2920: SMTP Service Extension for Command 707 Pipelining (SMTP-pipe) 709 There are no IPv4 dependencies in this protocol. 711 4 Draft Standards 713 Draft Standards is the nomenclature given to specifications that are 714 on the penultimate maturity level of the IETF standards track process. 715 They are considered to be final specifications, which may only 716 experience changes to solve specific problems found. A specification 717 is only considered to be a Draft Standard if there are at least two 718 known independent and interoperable implementations. Hence, Draft 719 Standards are usually quite mature and widely used. 721 4.1 RFC 954: NICNAME/WHOIS (NICNAME) 723 There are no IPv4 dependencies in this protocol. 725 4.2 RFC 1184: Telnet Linemode Option (TOPT-LINE) 727 There are no IPv4 dependencies in this protocol. 729 4.3 RFC 1288: The Finger User Information Protocol 730 (FINGER) 732 There are no IPv4 dependencies in this protocol. 734 4.4 RFC 1305: Network Time Protocol (Version 3) 735 Specification, Implementation 737 Section 3.2.1 (Common Variables) provides the following variable 738 definitions: 740 "Peer Address (peer.peeraddr, pkt.peeraddr), Peer Port 741 (peer.peerport,pkt.peerport). These are the 32-bit Internet address 742 and 16-bit port number of the peer. 743 Host Address (peer.hostaddr, pkt.hostaddr), Host Port (peer.hostport, 744 pkt.hostport). These are the 32-bit Internet address and 16-bit port 745 number of the host. They are included among the state variables to 746 support multi-homing." 748 Section 3.4.3 (Receive Procedure) defines the following procedure: 750 "The source and destination Internet addresses and ports in the IP 751 and UDP headers are matched to the correct peer. If there is no 752 match a new instantiation of the protocol machine is created and the 753 association mobilized." 754 Section 3.6 (Access Control Issues) proposes a simple authentication 755 scheme in the following way: 757 "If a more comprehensive trust model is required, the design can 758 be based on an access-control list with each entry consisting of 759 a 32-bit Internet address, 32-bit mask and three-bit mode. If the 760 logical AND of the source address (pkt.peeraddr) and the mask in an 761 entry matches the corresponding address in the entry and the mode 762 (pkt.mode) matches the mode in the entry, the access is allowed; 763 otherwise an ICMP error message is returned to the requestor. Through 764 appropriate choice of mask, it is possible to restrict requests 765 by mode to individual addresses, a particular subnet or net addresses, 766 or have no restriction at all. The access-control list would then 767 serve as a filter controlling which peers could create associations." 769 Appendix B Section 3 (B.3 Commands) defines the following 770 command: 772 "Set Trap Address/Port (6): The command association identifier, 773 status and data fields are ignored. The address and port number for 774 subsequent trap messages are taken from the source address and 775 port of the control message itself. The initial trap counter for trap 776 response messages is taken from the sequence field of the command. 777 The response association identifier, status and data fields are not 778 significant. Implementations should include sanity timeouts which 779 prevent trap transmissions if the monitoring program does not renew 780 this information after a lengthy interval." 782 The address clearly assumes an IPv4 address. Also, there are 783 numerous places in sample code and in algorithms that use the above 784 mentioned variables. It seems that there is no reason to modify the 785 actual protocol. A small number of text changes and an update 786 to implementations, so they can understand both IPv4 and IPv6 787 addresses, will suffice to have a NTP version that works on both 788 network layer protocols. 790 4.5 RFC 1575: An Echo Function for CLNP (ISO 8473) 791 (ISO-TS-ECH) 793 There are no IPv4 dependencies in this protocol. 795 4.6 RFC 1652: SMTP Service Extension for 8bit-MIME 796 Transport 798 There are no IPv4 dependencies in this protocol. 800 4.7 RFC 1777: Lightweight Directory Access Protocol 801 (LDAP) 803 There are no IPv4 dependencies in this protocol. 805 4.8 RFC 1778: The String Representation of Standard 806 Attribute Syntaxes 808 There are no IPv4 dependencies in this protocol. 810 4.9 RFC 1832: eXternal Data Representation Standard 811 (XDR) 813 There are no IPv4 dependencies in this protocol. 815 4.10 RFC 2045: Multipurpose Internet Mail Extensions 816 (MIME), Part One: Format of Internet Message 817 Bodies (MIME) 819 There are no IPv4 dependencies in this protocol. 821 4.11 RFC 2046 MIME, Part Two: Media Types (MIME- 822 MEDIA) 824 There are no IPv4 dependencies in this protocol. 826 4.12 RFC 2047: MIME, Part Three: Message Header 827 Extensions for Non-ASCII Text (MIME-MSG) 829 There are no IPv4 dependencies in this protocol. 831 4.13 RFC 2049: MIME Part Five: Conformance Criteria 832 and Examples (MIME-CONF) 834 There are no IPv4 dependencies in this protocol. 836 4.14 RFC 2279: UTF-8, a transformation format of ISO 837 10646 (UTF-8) 839 There are no IPv4 dependencies in this protocol. 841 4.15 RFC 2347: TFTP Option Extension (TFTP-Ext) 843 There are no IPv4 dependencies in this protocol. 845 4.16 RFC 2348: TFTP Blocksize Option (TFTP-Blk) 847 Section "Blocksize Option Specification" gives the following 848 example: 850 "For example: 851 +---+--�+-+--�+-+--�+-+--�+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 852 | 1 | foobar | 0 | octet | 0 | blksize| 0 | 1428 | 0 | 853 +---+--�+-+--�+-+--�+-+--�+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 854 is a Read Request, for the file named "foobar", in octet (binary) 855 transfer mode, with a block size of 1428 octets (Ethernet MTU, less 856 the TFTP, UDP and IP header lengths)." 858 Clearly, the given blocksize example would not work with IPv6 859 header sizes, but it has no practical implications, since larger 860 blocksizes are also available. 862 4.17 RFC 2349: TFTP Timeout Interval and Transfer 863 Size Options (TFTP-Opt) 865 There are no IPv4 dependencies in this protocol. 867 4.18 RFC 2355: TN3270 Enhancements (TN3270E) 869 There are no IPv4 dependencies in this protocol. 871 4.19 RFC 2396: Uniform Resource Identifiers (URI): 872 Generic Syntax (URI-GEN) 874 Section 3.2.2. (Server-based Naming Authority) states: 876 "The host is a domain name of a network host, or its IPv4 address 877 as a set of four decimal digit groups separated by ".". Literal IPv6 878 addresses are not supported. 879 ... 880 Note: A suitable representation for including a literal IPv6 address 881 as the host part of a URL is desired, but has not yet been determined 882 or implemented in practice." 884 4.20 RFC 2616: Hypertext Transfer Protocol � HTTP/1.1 885 (HTTP) 887 Section 3.2.2 (http URL) states: 889 "The "http" scheme is used to locate network resources via the 890 HTTP protocol. This section defines the scheme-specific syntax and 891 semantics for http URLs. 892 http_URL = "http:" "//" host [ ":" port ] [ abs_path [ "?" query ]] 893 If the port is empty or not given, port 80 is assumed. The semantics 894 are that the identified resource is located at the server listening 895 for TCP connections on that port of that host, and the Request-URI for 896 the resource is abs_path (section 5.1.2). The use of IP addresses 897 in URLs SHOULD be avoided whenever possible (see RFC 1900 898 [24]). " 900 The text is version neutral, but it is unclear whether individual 901 implementations will support IPv6 addresses. In fact, the use 902 of the ":"separator in IPv6 addresses will cause misinterpretation 903 when parsing URI's. There are other discussions regarding a 904 server recognizing its own IP addresses, spoofing DNS/IP address 905 combinations, as well as issues regarding multiple HTTP servers 906 running on a single IP interface. Again, the text is version neutral, 907 but clearly, such statements represent implementation issues. 909 5 Proposed Standards 911 Proposed Standards represent initial level documents in the IETF 912 standards track. They are stable in terms of design, but do not 913 require the existence of implementations. In several cases, these 914 specifications are simply proposed as solid technical ideas, to be 915 analysed by the Internet community, but are never implemented or 916 advanced in the IETF standards' process. 918 5.1 RFC 698: Telnet extended ASCII option (TOPT-EXT) 920 There are no IPv4 dependencies in this protocol. 922 5.2 RFC 726: Remote Controlled Transmission and 923 Echoing Telnet option (TOPT-REM) 925 There are no IPv4 dependencies in this protocol. 927 5.3 RFC 727: Telnet logout option (TOPT-LOGO) 929 There are no IPv4 dependencies in this protocol. 931 5.4 RFC 735: Revised Telnet byte macro option (TOPT- 932 BYTE) 934 There are no IPv4 dependencies in this protocol. 936 5.5 RFC 736: Telnet SUPDUP option (TOPT-SUP) 938 There are no IPv4 dependencies in this protocol. 940 5.6 RFC 749: Telnet SUPDUP-Output option (TOPT- 941 SUPO) 943 There are no IPv4 dependencies in this protocol. 945 5.7 RFC 779: Telnet send-location option (TOPT-SNDL) 947 There are no IPv4 dependencies in this protocol. 949 5.8 RFC 885: Telnet end of record option (TOPT-EOR) 951 There are no IPv4 dependencies in this protocol. 953 5.9 RFC 927: TACACS user identification Telnet option 954 (TOPT-TACAC) 956 There are no IPv4 dependencies in this protocol. 958 5.10 RFC 933: Output marking Telnet option (TOPT-OM) 960 There are no IPv4 dependencies in this protocol. 962 5.11 RFC 946: Telnet terminal location number option 963 (TOPT-TLN) 965 Section "TTYLOC Number" states: 967 "The TTYLOC number is a 64-bit number composed of two (2) 968 32-bit numbers: The 32-bit official ARPA Internet host address (may 969 be any one of the addresses for multi-homed hosts) and a 32-bit 970 number representing the terminal on the specified host. The host 971 address of [0.0.0.0] is defined to be "unknown", the terminal number 972 of FFFFFFFF (hex, r or-1 in decimal) is defined to be "unknown" 973 and the terminal number of FFFFFFFE (hex, or -2 in decimal) is 974 defined to be "detached" for processes that are not attached to a 975 terminal." 977 Although there is a dependency here, it is unlikely to be of any major 978 significance. 980 5.12 RFC 977: Network News Transfer Protocol (NNTP) 982 There are no IPv4 dependencies in this protocol. 984 5.13 RFC 1041: Telnet 3270 regime option (TOPT-3270) 986 There are no IPv4 dependencies in this protocol. 988 5.14 RFC 1043: Telnet Data Entry Terminal option: 989 DODIIS implementation (TOPT-DATA) 991 There are no IPv4 dependencies in this protocol. 993 5.15 RFC 1053: Telnet X.3 PAD option (TOPT-X.3) 995 There are no IPv4 dependencies in this protocol. 997 5.16 RFC 1073: Telnet window size option (TOPT- 998 NAWS) 1000 There are no IPv4 dependencies in this protocol. 1002 5.17 RFC 1079: Telnet terminal speed option (TOPT-TS) 1004 There are no IPv4 dependencies in this protocol. 1006 5.18 RFC 1091: Telnet terminal-type option (TOPT- 1007 TERM) 1009 There are no IPv4 dependencies in this protocol. 1011 5.19 RFC 1096: Telnet X display location option (TOPT- 1012 XDL) 1014 There are no IPv4 dependencies in this protocol. 1016 5.20 RFC 1274: The COSINE and Internet X.500 Schema 1018 There are no IPv4 dependencies in this protocol. 1020 5.21 RFC 1276: Replication and Distributed Operations 1021 extensions to provide an Internet Directory using 1022 X.500 1024 There are no IPv4 dependencies in this protocol. 1026 5.22 RFC 1314: A File Format for the Exchange of 1027 Images in the Internet (NETFAX) 1029 There are no IPv4 dependencies in this protocol. 1031 5.23 RFC 1328: X.400 1988 to 1984 downgrading 1033 There are no IPv4 dependencies in this protocol. 1035 5.24 RFC 1372: Telnet Remote Flow Control Option 1036 (TOPT-RFC) 1038 There are no IPv4 dependencies in this protocol. 1040 5.25 RFC 1415: FTP-FTAM Gateway Specification 1041 (FTP-FTAM) 1043 Since this document defines a gateway for interaction between FTAM 1044 and FTP, the only possible IPv4 dependencies are associated with 1045 FTP, which has already been investigated above, in section 3.2. 1047 5.26 RFC 1494: Equivalences between 1988 X.400 and 1048 RFC-822 Message Bodies (Equiv) 1050 There are no IPv4 dependencies in this protocol. 1052 5.27 RFC 1496: Rules for downgrading messages from 1053 X.400/88 to X.400/84 when MIME content-types are 1054 present in the messages (HARPOON) 1056 There are no IPv4 dependencies in this protocol. 1058 5.28 RFC 1502: X.400 Use of Extended Character Sets 1060 There are no IPv4 dependencies in this protocol. 1062 5.29 RFC 1572: Telnet Environment Option (TOPT- 1063 ENVIR) 1065 There are no IPv4 dependencies in this protocol. 1067 5.30 RFC 1648: Postmaster Convention for X.400 1068 Operations 1070 There are no IPv4 dependencies in this protocol. 1072 5.31 RFC 1738: Uniform Resource Locators (URL) 1073 (URL) 1075 Section 3.1. (Common Internet Scheme Syntax) states: 1077 "host 1078 The fully qualified domain name of a network host, or its IP address 1079 as a set of four decimal digit groups separated by ".". Fully qualified 1080 domain names take the form as described in Section 3.5 of RFC 1081 1034 [13] and Section 2.1 of RFC 1123 [5]: a sequence of domain 1082 labels separated by ".", each domain label starting and ending 1083 with an alphanumerical character and possibly also containing "-" 1084 characters. The rightmost domain label will never start with a digit, 1085 though, which syntactically distinguishes all domain names from the 1086 IP addresses." 1088 Clearly, this is only valid when using IPv4 addresses. Later in 1089 Section 5. (BNF for specific URL schemes), there is the following 1090 text: 1092 "; URL schemeparts for ip based protocols: 1093 ip-schemepart = "//" login [ "/" urlpath ] 1094 login = [ user [ ":" password ] "@" ] hostport 1095 hostport = host [ ":" port ] 1096 host = hostname | hostnumber" 1098 Again, this has also implications in terms of network neutrality. 1100 5.32 RFC 1740: MIME Encapsulation of Macintosh Files 1101 - MacMIME (MacMIME) 1103 There are no IPv4 dependencies in this protocol. 1105 5.33 RFC 1767: MIME Encapsulation of EDI Objects 1106 (MIME-EDI) 1108 There are no IPv4 dependencies in this protocol. 1110 5.34 RFC 1781: Using the OSI Directory to Achieve User 1111 Friendly Naming (OSI-Dir) 1113 There are no IPv4 dependencies in this protocol. 1115 5.35 RFC 1798: Connection-less Lightweight X.500 1116 Directory Access Protocol (CLDAP) 1118 Section 5.2. (Client Implementations) presents the following 1119 observation, which needs to be re-written: 1121 "For simple lookup applications, use of a retry algorithm with 1122 multiple servers similar to that commonly used in DNS stub resolver 1123 implementations is recommended. The location of a CLDAP server 1124 or servers may be better specified using IP addresses (simple or 1125 broadcast) rather than names that must first be looked up in another 1126 directory such as DNS." 1128 5.36 RFC 1808: Relative Uniform Resource Locators 1129 (URL) 1131 There are no IPv4 dependencies in this protocol. 1133 5.37 RFC 1835: Architecture of the WHOIS++ service 1134 (WHOIS++) 1136 There are no IPv4 dependencies in this protocol. 1138 5.38 RFC 1891: SMTP Service Extension for Delivery 1139 Status Notifications (SMTP-DSN) 1141 There are no IPv4 dependencies in this protocol. 1143 5.39 RFC 1892: The Multipart/Report Content Type 1144 for the Reporting of Mail System Administrative 1145 Messages (MIME-RPT) 1147 There are no IPv4 dependencies in this protocol. 1149 5.40 RFC 1893: Enhanced Mail System Status Codes 1150 (EMS-CODE) 1152 There are no IPv4 dependencies in this protocol. 1154 5.41 RFC 1894: An Extensible Message Format for 1155 Delivery Status Notifications (DSN) 1157 There are no IPv4 dependencies in this protocol. 1159 5.42 RFC 1913: Architecture of the Whois++ Index 1160 Service,WHOIS++A 1162 Section 6.5. (Query referral) makes the following statement: 1164 "When referrals are included in the body of a response to a query, 1165 each referral is listed in a separate SERVER-TO-ASK block as shown 1166 below. 1167 # SERVER-TO-ASK 1168 Version-number: // version number of index software, used to insure 1169 compatibility 1170 Body-of-Query: // the original query goes here 1171 Server-Handle: // WHOIS++ handle of the referred server 1172 Host-Name: // DNS name or IP address of the referred server 1173 Port-Number: // Port number to which to connect, if different from 1174 the 1175 // WHOIS++ port number" 1177 The syntax used does not present specific IPv4 dependencies, but 1178 implementations should be modified to check, in incoming packets, 1179 which IP version was used by the original request, so they can 1180 determine whether or not to to return an IPv6 address. 1182 5.43 RFC 1914: How to Interact with a Whois++ Mesh 1183 (WHOIS++) 1185 Section 4 (Caching) states the following: 1187 "A client can cache all information it gets from a server for some 1188 time. For example records, IP-addresses of Whois++ servers, the 1189 Directory of Services server etc. 1190 A client can itself choose for how long it should cache the 1191 information. The IP-address of the Directory of Services server 1192 might not change for a day or two, and neither might any other 1193 information." 1195 Also, subsection 4.1. (Caching a Whois++ servers hostname) 1196 contains: 1198 "An example of cached information that might change is the cached 1199 hostname, IP-address and portnumber which a client gets back 1200 in a servers-to-ask response. That information is cached in the 1201 server since the last poll, which might occurred several weeks ago. 1202 Therefore, when such a connection fails, the client should fall back 1203 to use the serverhandle instead, which means that it contacts the 1204 Directory of Services server and queries for a server with that 1205 serverhandle. By doing this, the client should always get the last 1206 known hostname. An algorithm for this might be: 1207 response := servers-to-ask response from server A 1208 IP-address := find ip-address for response.hostname in DNS 1209 connect to ip-address at port response.portnumber 1210 if connection fails { 1211 connect to Directory of Services server 1212 query for host with serverhandle response.serverhandle 1213 response := response from Directory of Services server 1214 IP-address := find ip-address for response.hostname in DNS 1215 connect to ip-address at port response.portnumber 1216 if connection fails { 1217 exit with error message 1218 } 1219 } 1220 Query this new server" 1222 The paragraph does not contain IPv4 specific syntax. Hence, IPv6 1223 compliance will be implementation dependent. 1225 5.44 RFC 1985: SMTP Service Extension for Remote 1226 Message Queue Starting (SMTP-ETRN) 1228 There are no IPv4 dependencies in this protocol. 1230 5.45 RFC 2017: Definition of the URL MIME External- 1231 Body Access-Type (URL-ACC) 1233 There are no IPv4 dependencies in this protocol. 1235 5.46 RFC 2034: SMTP Service Extension for Returning 1236 Enhanced Error Codes (SMTP-ENH) 1238 There are no IPv4 dependencies in this protocol. 1240 5.47 RFC 2056: Uniform Resource Locators for Z39.50 1241 (URLZ39.50) 1243 There are no IPv4 dependencies in this protocol. 1245 5.48 RFC 2060: Internet Message Access Protocol - 1246 Version 4rev1 (IMAPV4) 1248 There are no IPv4 dependencies in this protocol. 1250 5.49 RFC 2077: The Model Primary Content Type 1251 for Multipurpose Internet Mail Extensions (MIME- 1252 MODEL) 1254 There are no IPv4 dependencies in this protocol. 1256 5.50 RFC 2079: Definition of an X.500 Attribute Type 1257 and an Object Class to Hold Uniform Resource 1258 Identifiers (URIs) (URI-ATT) 1260 There are no IPv4 dependencies in this protocol. 1262 5.51 RFC 2086: IMAP4 ACL extension (IMAP4-ACL) 1264 There are no IPv4 dependencies in this protocol. 1266 5.52 RFC 2087: IMAP4 QUOTA extension (IMAP4- 1267 QUO) 1269 There are no IPv4 dependencies in this protocol. 1271 5.53 RFC 2088: IMAP4 non-synchronizing literals 1272 (IMAP4-LIT) 1274 There are no IPv4 dependencies in this protocol. 1276 5.54 RFC 2122: VEMMI URL Specification (VEMMI- 1277 URL) 1279 Section 3 (Description of the VEMMI scheme) states: 1281 "The VEMMI URL scheme is used to designate multimedia 1282 interactive services conforming to the VEMMI standard (ITU/T 1283 T.107 and ETS 300 709). 1284 A VEMMI URL takes the form: 1285 vemmi://:/; 1286 = 1287 as specified in Section 3.1. of RFC 1738. If : is omitted, 1288 the port defaults to 575 (client software may choose to ignore 1289 the optional port number in order to increase security). The 1290 part is optional and may be omitted." 1292 IPv4 dependencies may relate to the possibility of the portion 1293 to contain an IPv4 address, as defined in RFC 1738 (see section 5.31. 1294 above). Once the problem is solved in the context of RFC 1738, this 1295 issue will be automatically solved. 1297 5.55 RFC 2141: URN Syntax (URN-SYNTAX) 1299 There are no IPv4 dependencies in this protocol. 1301 5.56 RFC 2142 "Mailbox Names for Common Services, 1302 Roles and Functions" (MAIL-SERV) 1304 There are no IPv4 dependencies in this protocol. 1306 5.57 RFC 2156: MIXER (Mime Internet X.400 1307 Enhanced Relay): Mapping between X.400 and 1308 RFC 822/MIME (MIXER) 1310 There are no IPv4 dependencies in this protocol. 1312 5.58 RFC 2157: Mapping between X.400 and RFC- 1313 822/MIME Message Bodies 1315 There are no IPv4 dependencies in this protocol. 1317 5.59 RFC 2158: X.400 Image Body Parts 1319 There are no IPv4 dependencies in this protocol. 1321 5.60 RFC 2159: A MIME Body Part for FAX 1323 There are no IPv4 dependencies in this protocol. 1325 5.61 RFC 2160: Carrying PostScript in X.400 and MIME 1327 There are no IPv4 dependencies in this protocol. 1329 5.62 RFC 2163: Using the Internet DNS to Distribute 1330 MIXER Conformant Global Address Mapping 1331 (MCGAM) (DNS-MCGAM) 1333 There are no IPv4 dependencies in this protocol. 1335 5.63 RFC 2164: Use of an X.500/LDAP directory to 1336 support MIXER address mapping 1338 There are no IPv4 dependencies in this protocol. 1340 5.64 RFC 2165: Service Location Protocol (SLP) 1342 Section 7. (Service Type Request Message Format) and Section 9. 1343 (Service Registration Message Format) have an 80 bit field from 1344 addr-spec (see below) which cannot not support IPv6 addresses. 1345 Also, Section 20.1. (Previous Responders' Address Specification) 1346 states: 1348 "The previous responders' Address Specification is specified as: 1349 ::= 1350 |, 1351 i.e., a list separated 1352 by commas with no intervening white space. The Address 1353 Specification is the address of the Directory Agent or Service Agent 1354 which supplied the previous response. The format for Address 1355 Specifications in Service Location is defined in section 20.4. The 1356 comma delimiter is required between each . The use 1357 of dotted decimal IP address notation should only be used in 1358 environments which have no Domain Name Service. 1359 Example: 1360 RESOLVO.NEATO.ORG,128.127.203.63" 1362 Later, in Section 20.4. (Address Specification in Service Location) 1363 there is also the following reference to addr-spec: 1365 "The address specification used in Service Location is: 1366 ::= [:@][:] 1367 ::= Fully qualified domain name | dotted decimal IP address 1368 notation 1369 When no Domain Name Server is available, SAs and DAs must 1370 use dotted decimal conventions for IP addresses. Otherwise, it is 1371 preferable to use a fully qualified domain name wherever possible as 1372 renumbering of host addresses will make IP addresses invalid over 1373 time." 1375 The whole Section 21. (Protocol Requirements) defines the 1376 requirements for each of the elements of this protocol. Several IPv4 1377 statements are made, but the syntax used is sufficiently neutral to 1378 apply to the use of IPv6. 1379 Section 22. (Configurable Parameters and Default Values) states: 1381 "There are several configuration parameters for Service Location. 1382 Default values are chosen to allow protocol operation without the 1383 need for selection of these configuration parameters, but other 1384 values may be selected by the site administrator. The configurable 1385 parameters will allow an implementation of Service Location to be 1386 more useful in a variety of scenarios. 1387 Multicast vs. Broadcast 1388 All Service Location entities must use multicast by default. The 1389 ability to use broadcast messages must be configurable for UAs and 1390 SAs. Broadcast messages are to be used in environments where 1391 not all Service Location entities have hardware or software which 1392 supports multicast. 1393 Multicast Radius 1394 Multicast requests should be sent to all subnets in a site. The 1395 default multicast radius for a site is 32. This value must be 1396 configurable. The value for the site's multicast TTL may be obtained 1397 DHCP using an option which is currently unassigned." 1398 Once again, nothing here precludes IPv6. Section 23. (Non- 1399 configurable Parameters) states: 1400 "IP Port number for unicast requests to Directory Agents: 1401 UDP and TCP Port Number: 427 1402 Multicast Addresses 1403 Service Location General Multicast Address: 224.0.1.22 1404 Directory Agent Discovery Multicast Address: 224.0.1.35 1405 A range of 1024 contiguous multicast addresses for use as Service 1406 Specific Discovery Multicast Addresses will be assigned by IANA." 1408 Clearly, the statements above require specifications related to the 1409 use of IPv6 multicast addresses with equivalent functionality. 1411 5.65 RFC 2177: IMAP4 IDLE command (IMAP4-IDLE) 1413 There are no IPv4 dependencies in this protocol. 1415 5.66 RFC 2183: Communicating Presentation 1416 Information in Internet Messages: The Content- 1417 Disposition Header Field 1419 There are no IPv4 dependencies in this protocol. 1421 5.67 RFC 2192: IMAP URL Scheme (IMAP-URL) 1423 There are no IPv4 dependencies in this protocol. 1425 5.68 RFC 2193: IMAP4 Mailbox Referrals 1426 (IMAP4MAIL) 1428 Section 6. (Formal Syntax) presents the following statement: 1430 "referral_response_code = "[" "REFERRAL" 1*(SPACE ) "]"; 1431 See [RFC-1738] for definition" 1433 The above presents dependencies on RFC 1738 URL definitions, 1434 which have already been mentioned in this document, section 5.31. 1436 5.69 RFC 2218: A Common Schema for the Internet 1437 White Pages Service 1439 There are no IPv4 dependencies in this protocol. 1441 5.70 RFC 2221: IMAP4 Login Referrals 1442 (IMAP4LOGIN) 1444 Section 4.1. (LOGIN and AUTHENTICATE Referrals) provides the 1445 following example: 1447 "Example: C: A001 LOGIN MIKE PASSWORD 1448 S: A001 NO [REFERRAL IMAP://MIKE@SERVER2/] Specified 1449 user is invalid on this server. Try SERVER2." 1451 Even though the syntax "user@SERVER2" is presented often, there 1452 are no specifications related to the format of "SERVER2". Hence, it 1453 is up to individual implementations to decide acceptable values for 1454 the hostname. This may or not include explicit IPv6 addresses. 1456 5.71 RFC 2227: Simple Hit-Metering and Usage- 1457 Limiting for HTTP 1459 There are no IPv4 dependencies in this protocol. 1461 5.72 RFC 2231: MIME Parameter Value and Encoded 1462 Word Extensions: Character Sets, Languages, and 1463 Continuations (MIME-EXT) 1465 There are no IPv4 dependencies in this protocol. 1467 5.73 RFC 2234: Augmented BNF for Syntax 1468 Specifications: ABNF (ABNF) 1470 There are no IPv4 dependencies in this protocol. 1472 5.74 RFC 2244: Application Configuration Access 1473 Protocol (ACAP) 1475 There are no IPv4 dependencies in this protocol. 1477 5.75 RFC 2254 The String Representation of LDAP 1478 Search Filters (STR-LDAP) 1480 There are no IPv4 dependencies in this protocol. 1482 5.76 RFC 2255: The LDAP URL Format (LDAP-URL) 1484 There are no IPv4 dependencies in this protocol. 1486 5.77 RFC 2247 Using Domains in LDAP/X.500 1487 Distinguished Names 1489 There are no IPv4 dependencies in this protocol. 1491 5.78 RFC 2251: Lightweight Directory Access Protocol (v3) 1492 (LDAPV3) 1494 There are no IPv4 dependencies in this protocol. 1496 5.79 RFC 2252: Lightweight Directory Access Protocol (v3): 1497 Attribute Syntax Definitions (LDAP3-ATD) 1499 There are no IPv4 dependencies in this protocol. 1501 5.80 RFC 2253: Lightweight Directory Access Protocol (v3): 1502 UTF-8 String Representation of Distinguished 1503 Names (LDAP3-UTF8) 1505 Section 7.1. (Disclosure) states: 1507 "Distinguished Names typically consist of descriptive information 1508 about the entries they name, which can be people, organizations, 1509 devices or other real-world objects. This frequently includes some 1510 of the following kinds of information: 1512 - the common name of the object (i.e. a person's full name) 1513 - an email or TCP/IP address 1514 - its physical location (country, locality, city, street address) 1515 - organizational attributes (such as department name or affiliation)" 1517 If the caveat "Without putting any limitations on the version of the 1518 IP address.", then are no IPv4 dependencies in this protocol. 1520 5.81 RFC 2256: A Summary of the X.500(96) User 1521 Schema for use with LDAPv3 1523 There are no IPv4 dependencies in this protocol. 1525 5.82 RFC 2293: Representing Tables and Subtrees in the 1526 X.500 Directory (SUBTABLE) 1528 There are no IPv4 dependencies in this protocol. 1530 5.83 RFC 2294: Representing the O/R Address hierarchy 1531 in the X.500 Directory Information Tree (OR-ADD) 1533 There are no IPv4 dependencies in this protocol. 1535 5.84 RFC 2298: An Extensible Message Format for 1536 Message Disposition Notifications (EMF-MDN) 1538 There are no IPv4 dependencies in this protocol. 1540 5.85 RFC 2301: File Format for Internet Fax (FFIF) 1542 There are no IPv4 dependencies in this protocol. 1544 5.86 RFC 2302: Tag Image File Format (TIFF) - 1545 image/tiff MIME Sub-type Registration (TIFF) 1547 There are no IPv4 dependencies in this protocol. 1549 5.87 RFC 2303: Minimal PSTN address format in 1550 Internet Mail (MIN-PSTN) 1552 There are no IPv4 dependencies in this protocol. 1554 5.88 RFC 2304: Minimal FAX address format in Internet 1555 Mail (MINFAX-IM) 1557 There are no IPv4 dependencies in this protocol. 1559 5.89 RFC 2305: A Simple Mode of Facsimile Using 1560 Internet Mail (SMFAX-IM) 1562 There are no IPv4 dependencies in this protocol. 1564 5.90 RFC 2334: Server Cache Synchronization Protocol 1565 (SCSP) (SCSP) 1567 Appendix B, part 2.0.1 (Mandatory Common Part) states: 1569 "Cache Key 1570 This is a database lookup key that uniquely identifies a piece of 1571 data which the originator of a CSA Record wishes to synchronize 1572 with its peers for a given "Protocol ID/Server Group ID" pair. This 1573 key will generally be a small opaque byte string which SCSP will 1574 associate with a given piece of data in a cache. Thus, for example, 1575 an originator might assign a particular 4 byte string to the binding 1576 of an IP address with that of an ATM address. Generally speaking, the 1577 originating server of a CSA record is responsible for generating a 1578 Cache Key for every element of data that the given server originates 1579 and which the server wishes to synchronize with its peers in the SG." 1581 The statemente above is simply meant as an example. Hence, any 1582 IPv4 possible dependency of this protocol is an implementation issue. 1584 5.91 RFC 2342: IMAP4 Namespace (IMAP4NAME) 1586 There are no IPv4 dependencies in this protocol. 1588 5.92 RFC 2359: IMAP4 UIDPLUS extension 1589 (IMAP4UIDPL) 1591 There are no IPv4 dependencies in this protocol. 1593 5.93 RFC 2368: The mailto URL scheme (URLMAILTO) 1595 There are no IPv4 dependencies in this protocol. 1597 5.94 RFC 2369: The Use of URLs as Meta-Syntax for 1598 Core Mail List Commands and their Transport 1599 through Message Header Fields 1601 There are no IPv4 dependencies in this protocol. 1603 5.95 RFC 2384: POP URL Scheme (POP-URL) 1605 Section 3. (POP Scheme) states: 1607 "A POP URL is of the general form: 1608 pop://;auth=@: 1609 Where , , and are as defined in RFC 1738, and 1610 some or all of the elements, except "pop://" and , may be 1611 omitted." 1613 RFC 1738 (please refer to section 5.31) has a potential IPv4 1614 limitation.Hence, RFC2384 will only be IPv6 compliant when RFC 1615 1738 becomes properly updated. 1617 5.96 RFC 2387: The MIME Multipart/Related Content- 1618 type (MIME-RELAT) 1620 There are no IPv4 dependencies in this protocol. 1622 5.97 RFC 2388: Returning Values from Forms: 1623 multipart/form-data 1625 There are no IPv4 dependencies in this protocol. 1627 5.98 RFC 2389: Feature negotiation mechanism for the 1628 File Transfer Protocol 1630 There are no IPv4 dependencies in this protocol. 1632 5.99 RFC 2392: Content-ID and Message-ID Uniform 1633 Resource Locators (CIDMID-URL) 1635 There are no IPv4 dependencies in this protocol. 1637 5.100 RFC 2397: The "data" URL scheme (DATA-URL) 1639 There are no IPv4 dependencies in this protocol. 1641 5.101 RFC 2421: Voice Profile for Internet Mail - version 1642 2 (MIME-VP2) 1644 There are no IPv4 dependencies in this protocol. 1646 5.102 RFC 2422: Toll Quality Voice - 32 kbit/s ADPCM 1647 MIME Sub-type Registration (MIME-ADPCM) 1649 There are no IPv4 dependencies in this protocol. 1651 5.103 RFC 2423 VPIM Voice Message MIME Sub-type 1652 Registration (MIME-VPIM) 1654 There are no IPv4 dependencies in this protocol. 1656 5.104 RFC 2424: Content Duration MIME Header 1657 Definition (CONT-DUR) 1659 There are no IPv4 dependencies in this protocol. 1661 5.105 RFC 2425: A MIME Content-Type for Directory 1662 Information (TXT-DIR) 1664 There are no IPv4 dependencies in this protocol. 1666 5.106 RFC 2426: vCard MIME Directory Profile 1667 (MIME-VCARD) 1669 There are no IPv4 dependencies in this protocol. 1671 5.107 RFC 2428: FTP Extensions for IPv6 and NATs 1673 This RFC documents an IPv6 extension and hence, it is not 1674 considered in the context of the current discussion. 1676 5.108 RFC 2445: Internet Calendaring and 1677 Scheduling Core Object Specification (iCalendar) 1678 (ICALENDAR) 1680 Section 4.8.4.7 (Unique Identifier) states: 1682 "Property Name: UID 1683 Purpose: This property defines the persistent, globally unique 1684 identifier for the calendar component. 1685 Value Type: TEXT 1686 Property Parameters: Non-standard property parameters can be 1687 specified on this property. 1688 Conformance: The property MUST be specified in the 1689 "VEVENT", "VTODO", "VJOURNAL" or "VFREEBUSY" 1690 calendar components. 1691 Description: The UID itself MUST be a globally unique identifier. 1692 The generator of the identifier MUST guarantee that the identifier is 1693 unique. There are several algorithms that can be used to accomplish 1694 this. The identifier is RECOMMENDED to be the identical syntax 1695 to the [RFC 822] addr-spec. A good method to assure uniqueness 1696 is to put the domain name or a domain literal IP address of the host 1697 on which the identifier was created on the right hand side of the 1698 "@", and on the left hand side, put a combination of the current 1699 calendar date and time of day (i.e., formatted in as a DATE-TIME 1700 value) along with some other currently unique (perhaps sequential) 1701 identifier available on the system (for example, a process id number). 1702 Using a date/time value on the left hand side and a domain name or 1703 domain literal on the right hand side makes it possible to guarantee 1704 uniqueness since no two hosts should be using the same domain 1705 name or IP address at the same time. Though other algorithms will 1706 work, it is RECOMMENDED that the right hand side contain some 1707 domain identifier (either of the host itself or otherwise) such that 1708 the generator of the message identifier can guarantee the uniqueness 1709 of the left hand side within the scope of that domain." 1711 Although the above does not explicitly state the use of IPv4 1712 addresses, it addresses the explicit use of RFC 822, which is IPv4 1713 dependent, as already described in section 3.4. To be IPv6 compliant 1714 it should instead explicitly disallow the use of IPv4 addresses. 1716 5.109 RFC 2446: iCalendar Transport-Independent 1717 Interoperability Protocol (iTIP) Scheduling Events, 1718 BusyTime, To-dos and Journal Entries (ITIP) 1720 There are no IPv4 dependencies in this protocol. 1722 5.110 RFC 2447: iCalendar Message-Based 1723 Interoperability Protocol (iMIP) (IMIP) 1725 There are no IPv4 dependencies in this protocol. 1727 5.111 RFC 2449: POP3 Extension Mechanism (POP3- 1728 EXT) 1730 There are no IPv4 dependencies in this protocol. 1732 5.112 RFC 2476: Message Submission 1734 This RFC contains several discussions on the usage of IP Address 1735 authorization schemes, but it does not limit those addresses to IPv4. 1737 5.113 RFC 2480: Gateways and MIME Security 1738 Multiparts 1740 There are no IPv4 dependencies in this protocol. 1742 5.114 RFC 2518: HTTP Extensions for Distributed 1743 Authoring � WEBDAV (WEBDAV) 1745 There are no IPv4 dependencies in this protocol. 1747 5.115 RFC 2530: Indicating Supported Media Features 1748 Using Extensions to DSN and MDN 1750 There are no IPv4 dependencies in this protocol. 1752 5.116 RFC 2532: Extended Facsimile Using Internet 1753 Mail 1755 There are no IPv4 dependencies in this protocol. 1757 5.117 RFC 2533: A Syntax for Describing Media Feature 1758 Sets 1760 There are no IPv4 dependencies in this protocol. 1762 5.118 RFC 2534: Media Features for Display, Print, and 1763 Fax 1765 There are no IPv4 dependencies in this protocol. 1767 5.119 RFC 2554: SMTP Service Extension for 1768 Authentication 1770 There are no IPv4 dependencies in this protocol. 1772 5.120 RFC 2557: MIME Encapsulation of Aggregate 1773 Documents, such as HTML (MHTML) (MHTML) 1775 There are no IPv4 dependencies in this protocol. 1777 5.121 RFC 2589: Lightweight Directory Access Protocol 1778 (v3): Extensions for Dynamic Directory Services 1779 (LDAPv3) 1781 There are no IPv4 dependencies in this protocol. 1783 5.122 RFC 2595: Using TLS with IMAP, POP3 and 1784 ACAP 1786 There are no IPv4 dependencies in this protocol. 1788 5.123 RFC 2596 Use of Language Codes in LDAP 1790 There are no IPv4 dependencies in this protocol. 1792 5.124 RFC 2608: Service Location Protocol, Version 2 1793 (SLP) 1795 Section 8.1. (Service Request) contains the following: 1797 "0 1 2 3 1798 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1799 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1800 | Service Location header (function = SrvRqst = 1) | 1801 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1802 | length of | String \ 1803 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1804 | length of | String \ 1805 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1806 | length of | String \ 1807 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1808 | length of predicate string | Service Request \ 1809 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1810 | length of string | String \ 1811 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1813 is the Previous Responder List. This contains 1814 dotted decimal notation IP (v4) addresses, and is iteratively 1815 multicast to obtain all possible results (see Section 6.3). UAs SHOULD 1816 implement this discovery algorithm. SAs MUST use this to discover 1817 all available DAs in their scope, if they are not already configured 1818 with DA addresses by some other means." 1819 And later: 1821 "A SA silently drops all requests which include the SA's address in 1822 the . An SA which has multiple network interfaces MUST 1823 check if any of the entries in the equal any of its 1824 interfaces. An entry in the PRList which does not conform to an 1825 IPv4 dotted decimal address is ignored: The rest of the 1826 is processed normally and an error is not returned." 1828 To become IPv6 compliant, this protocol requires a new version. 1830 5.125 RFC 2609: Service Templates and Service: 1831 Schemes 1833 Section 2.1. (Service URL Syntax) defines: 1834 "The ABNF for a service: URL is: 1835 hostnumber = ipv4-number 1836 ipv4-number = 1*3DIGIT 3("." 1*3DIGIT)" 1837 This document presents many other references to hostnumber, which 1838 requires an update to support IPv6. 1840 5.126 RFC 2640: Internationalization of the File 1841 Transfer Protocol 1843 There are no IPv4 dependencies in this protocol. 1845 5.127 RFC 2645: ON-DEMAND MAIL RELAY 1846 (ODMR) SMTP with Dynamic IP Addresses 1847 (ODMR-SMTP) 1849 There are no IPv4 dependencies in this protocol. 1851 5.128 RFC 2646: The Text/Plain Format Parameter 1853 There are no IPv4 dependencies in this protocol. 1855 5.129 RFC 2651: The Architecture of the Common 1856 Indexing Protocol (CIP) (CIP) 1858 There are no IPv4 dependencies in this protocol. 1860 5.130 RFC 2652: MIME Object Definitions for the 1861 Common Indexing Protocol (CIP) 1863 There are no IPv4 dependencies in this protocol. 1865 5.131 RFC 2653: CIP Transport Protocols 1867 There are no IPv4 dependencies in this protocol. 1869 5.132 RFC 2732: Format for Literal IPv6 Addresses in 1870 URL's 1872 This document defines an IPv6 specific protocol and hence, it is not 1873 discussed in this document. 1875 5.133 RFC 2738: Corrections to "A Syntax for 1876 Describing Media Feature Sets" 1878 There are no IPv4 dependencies in this protocol. 1880 5.134 RFC 2739: Calendar Attributes for vCard and 1881 LDAP 1883 There are no IPv4 dependencies in this protocol. 1885 5.135 RFC 2806: URLs for Telephone Calls 1887 There are no IPv4 dependencies in this protocol. 1889 5.136 RFC 2846: GSTN Address Element Extensions in 1890 E-mail Services 1892 There are no IPv4 dependencies in this protocol. 1894 5.137 RFC 2849: The LDAP Data Interchange Format 1895 (LDIF) - Technical Specification (LDIF) 1897 There are no IPv4 dependencies in this protocol. 1899 5.138 RFC 2852: Deliver By SMTP Service Extension 1901 There are no IPv4 dependencies in this protocol. 1903 5.139 RFC 2879: Content Feature Schema for Internet 1904 Fax (V2) 1906 There are no IPv4 dependencies in this protocol. 1908 5.140 RFC 2891: LDAP Control Extension for Server 1909 Side Sorting of Search Results 1911 There are no IPv4 dependencies in this protocol. 1913 5.141 RFC 2910: Internet Printing Protocol/1.1: 1914 Encoding and Transport (IPP-E-T) 1916 There are no IPv4 dependencies in this protocol. 1918 5.142 RFC 2911: Internet Printing Protocol/1.1: Model 1919 and Semantics (IPP-M-S) 1921 There are no IPv4 dependencies in this protocol. 1923 5.143 RFC 2912: Indicating Media Features for MIME 1924 Content 1926 There are no IPv4 dependencies in this protocol. 1928 5.144 RFC 2913: MIME Content Types in Media Feature 1929 Expressions 1931 There are no IPv4 dependencies in this protocol. 1933 5.145 RFC 2919: List-Id: A Structured Field and 1934 Namespace for the Identification of Mailing Lists 1936 There are no IPv4 dependencies in this protocol. 1938 5.146 RFC 2938: Identifying Composite Media Features 1940 There are no IPv4 dependencies in this protocol. 1942 5.147 RFC 2965: HTTP State Management Mechanism 1944 This document includes several references to host IP addresses. 1945 However, there is no explicit mention to a particular protocol 1946 version. A caveat similar to "Without putting any limitations on 1947 the version of the IP address." should be added, so that there will 1948 remain no doubts about possible IPv4 dependencies. 1950 5.148 RFC 2971: IMAP4 ID extension 1952 There are no IPv4 dependencies in this protocol. 1954 5.149 RFC 2987: Registration of Charset and Languages 1955 Media Features Tags 1957 There are no IPv4 dependencies in this protocol. 1959 5.150 RFC 3009: Registration of parityfec MIME types 1961 There are no IPv4 dependencies in this protocol. 1963 5.151 RFC 3017: XML DTD for Roaming Access Phone 1964 Book 1966 Section 6.21. (DNS Server Address) states: 1968 "The dnsServerAddress element represents the IP address of the 1969 Domain Name Service (DNS) server which should be used when 1970 connected to this POP. The address is represented in the form of a 1971 string in dotted-decimal notation (e.g., 192.168.101.1). 1972 Syntax: 1973 1974 1975 " 1978 Additionally, it is stated in Section 6.2.9. (Default Gateway 1979 Address): 1980 "The defaulttGatewayAddress element represents the address of the 1981 default gateway which should be used when connected to this POP. 1982 The address is represented in the form of a string in dotted-decimal 1983 notation (e.g., 192.168.101.1). 1984 Syntax: 1985 1986 1987 " 1990 It should be straightforward to implement elements that are IPv6 1991 aware. 1993 5.152 RFC 3023: XML Media Types 1995 There are no IPv4 dependencies in this protocol. 1997 5.153 RFC 3028: Sieve: A Mail Filtering Language 1999 There are no IPv4 dependencies in this protocol. 2001 5.154 RFC 3030: SMTP Service Extensions for 2002 Transmission of Large and Binary MIME Messages 2004 There are no IPv4 dependencies in this protocol. 2006 5.155 RFC 3049: TN3270E Service Location and Session 2007 Balancing 2009 There are no IPv4 dependencies in this protocol. 2011 5.156 RFC 3059: Attribute List Extension for the Service 2012 Location Protocol (SLPv2) 2014 There are no IPv4 dependencies in this protocol. 2016 5.157 RFC 3080: The Blocks Extensible Exchange 2017 Protocol Core (BEEP) 2019 There are no IPv4 dependencies in this protocol. 2021 5.158 RFC 3081: Mapping the BEEP Core onto TCP 2023 There are no IPv4 dependencies in this protocol. 2025 5.159 RFC 3111: Service Location Protocol 2026 Modifications for IPv6 2028 This is an IPv6 related document and is not discussed in this 2029 document. 2031 6 Experimental RFCs 2033 Experimental RFCs belong to the category of "non-standard" 2034 specifications. This group involves specifications considered "off- 2035 track", e.g., specifications that haven't yet reach an adequate 2036 standardization level, or that have been superseded by more recent 2037 specifications. 2038 Experimental RFCs represent specifications that are currently part of 2039 some research effort, and that are often propriety in nature, or used 2040 in limited arenas. They are documented to the Internet community 2041 in order to allow potential interoperability or some other potential 2042 useful scenario. In a few cases, they are presented as alternatives to 2043 the mainstream solution of an acknowledged problem. 2045 6.1 RFC 909: Loader Debugger Protocol (LDP) 2047 There are no IPv4 dependencies in this protocol. 2049 6.2 RFC 1143: The Q Method of Implementing TELNET 2050 Option Negotiation 2052 There are no IPv4 dependencies in this protocol. 2054 6.3 RFC 1153: Digest message format (DMF-MAIL) 2056 There are no IPv4 dependencies in this protocol. 2058 6.4 RFC 1159: Message Send Protocol 2060 There are no IPv4 dependencies in this protocol. 2062 6.5 RFC 1165: Network Time Protocol (NTP) over the 2063 OSI Remote Operations Service (NTP-OSI) 2065 The only dependency this protocol presents is included in Appendix 2066 A (ROS Header Format): 2068 "ClockIdentifier ::= CHOICE { 2069 referenceClock[0] PrintableString, 2070 inetaddr[1] OCTET STRING, 2071 psapaddr[2] OCTET STRING 2072 }" 2074 6.6 RFC 1176: Interactive Mail Access Protocol: Version 2075 2 (IMAP2) 2077 There are no IPv4 dependencies in this protocol. 2079 6.7 RFC 1204: Message Posting Protocol (MPP) (MPP) 2081 There are no IPv4 dependencies in this protocol. 2083 6.8 RFC 1235: Coherent File Distribution Protocol 2084 (CFDP) 2086 Section "Protocol Specification" provides the following example, 2087 for the Initial Handshake: 2089 "The ticket server replies with a "This is Your Ticket" (TIYT) packet 2090 containing the ticket. Figure 2 shows the format of this packet. 2091 0 1 2 3 2092 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2093 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2094 | 'T' | 'I' | 'Y' | 'T' | 2095 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2096 | "ticket" | 2097 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2098 | BLKSZ (by default 512) | 2099 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2100 | FILSZ | 2101 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2102 | IP address of CFDP server (network order) | 2103 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2104 | client UDP port# (cfdpcln) | server UDP port# (cfdpsrv) | 2105 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2107 Fig. 2: "This Is Your Ticket" packet." 2109 This protocol assumes IPv4 multicast, but could be converted to IPv6 2110 multicast with a little effort. 2112 6.9 RFC 1279: X.500 and Domains 2114 This protocol specifies a protocol that assumes IPv4 but does not 2115 actually have any limitations which would limit its operation in an 2116 IPv6 environment. 2118 6.10 RFC 1312: Message Send Protocol 2 (MSP2) 2120 There are no IPv4 dependencies in this protocol. 2122 6.11 RFC 1339: Remote Mail Checking Protocol (RMCP) 2124 There are no IPv4 dependencies in this protocol. 2126 6.12 RFC 1440: SIFT/UFT: Sender-Initiated/Unsolicited 2127 File Transfer (SIFT) 2129 There are no IPv4 dependencies in this protocol. 2131 6.13 RFC 1459: Internet Relay Chat Protocol (IRCP) 2133 There are only two specific IPv4 addressing references. The first is 2134 presented in Section 6.2. (Command Response): 2136 "203 RPL_TRACEUNKNOWN 2137 "???? []"" 2139 The second appears in Section 8.12 (Configuration File): 2141 "In specifying hostnames, both domain names and use of the 'dot' 2142 notation (127.0.0.1) should both be accepted." 2144 After correcting the above, IPv6 support can be straightforward 2145 added. 2147 6.14 RFC 1465: Routing Coordination for X.400 MHS 2148 Services Within a Multi Protocol / Multi Network 2149 Environment Table Format V3 for Static Routing 2151 There are no IPv4 dependencies in this protocol. 2153 6.15 RFC 1505: Encoding Header Field for Internet 2154 Messages (EHF-MAIL) 2156 There are no IPv4 dependencies in this protocol. 2158 6.16 RFC 1528: Principles of Operation for the 2159 TPC.INT Subdomain: Remote Printing � Technical 2160 Procedures (REM-PRINT) 2162 There are no IPv4 dependencies in this protocol. 2164 6.17 RFC 1608: Representing IP Information in the 2165 X.500 Directory (X500-DIR) 2167 There are no IPv4 dependencies in this protocol. 2169 6.18 RFC 1609: Charting Networks in the X.500 2170 Directory (X500-CHART) 2172 There are no IPv4 dependencies in this protocol. 2174 6.19 RFC 1639: FTP Operation Over Big Address 2175 Records (FOOBAR) 2177 This document defines a method for overcoming FTP IPv4 2178 limitations and is therefore both IPv4 and IPv6 aware. 2180 6.20 RFC 1641 Using Unicode with MIME (MIME-UNI) 2182 There are no IPv4 dependencies in this protocol. 2184 6.21 RFC 1756: Remote Write Protocol - Version 1.0 2185 (RWP) 2187 There are no IPv4 dependencies in this protocol. 2189 6.22 RFC 1801: MHS use of the X.500 Directory to 2190 support MHS Routing 2192 There are no IPv4 dependencies in this protocol. 2194 6.23 RFC 1804: Schema Publishing in X.500 Directory 2196 There are no IPv4 dependencies in this protocol. 2198 6.24 RFC 1806: Communicating Presentation 2199 Information in Internet Messages: The Content- 2200 Disposition Header 2202 There are no IPv4 dependencies in this protocol. 2204 6.25 RFC 1845: SMTP Service Extension for 2205 Checkpoint/Restart 2207 There are no IPv4 dependencies in this protocol. 2209 6.26 RFC 1846: SMTP 521 Reply Code 2211 There are no IPv4 dependencies in this protocol. 2213 6.27 RFC 1873: Message/External-Body Content-ID 2214 Access Type (CONT-MT) 2216 There are no IPv4 dependencies in this protocol. 2218 6.28 RFC 1874: SGML Media Types (SGML-MT) 2220 There are no IPv4 dependencies in this protocol. 2222 6.29 RFC 1986: Experiments with a Simple File Transfer 2223 Protocol for Radio Links using Enhanced Trivial File 2224 Transfer Protocol (ETFTP) 2226 This protocol is IPv4 dependent, as can be seen from the segment 2227 presented bellow, and taken from Section 2. (PROTOCOL 2228 DESCRIPTION): 2230 "Table 3: ETFTP Data Encapsulation 2231 +------------+------------+------------+------------+---�--------+ 2232 |Ethernet(14)| | |ETFTP/ | | 2233 |SLIP(2) |IP(20) |UDP(8) |NETBLT(24) |DATA(1448) | 2234 |AX.25(20) | | | | | 2235 +------------+------------+------------+------------+---�--------+ 2236 " 2238 6.30 RFC 2016: Uniform Resource Agents (URAs) 2239 (URAS) 2241 There are no IPv4 dependencies in this protocol. 2243 6.31 RFC 2066: TELNET CHARSET Option (TOPT- 2244 CHARS) 2246 There are no IPv4 dependencies in this protocol. 2248 6.32 RFC 2075: IP Echo Host Service (IP-Echo) 2250 There are no IPv4 dependencies in this protocol. 2252 6.33 RFC 2090: TFTP Multicast Option (TFTP-MULTI) 2254 This protocol is limited to IPv4 multicast. It is expected that a 2255 similar functionality could be implemented on top of IPv6 multicast. 2257 6.34 RFC 2120: Managing the X.500 Root Naming 2258 Context (X.500-NAME) 2260 There are no IPv4 dependencies in this protocol. 2262 6.35 RFC 2161: A MIME Body Part for ODA (MIME- 2263 ODA) 2265 There are no IPv4 dependencies in this protocol. 2267 6.36 RFC 2162: MaXIM-11 - Mapping between X.400 / 2268 Internet mail and Mail-11 mail (MAP-MAIL) 2270 There are no IPv4 dependencies in this protocol. 2272 6.37 RFC 2168: Resolution of Uniform Resource 2273 Identifiers using the Domain Name System 2275 There are no IPv4 dependencies in this protocol. 2277 6.38 RFC 2169: A Trivial Convention for using HTTP in 2278 URN Resolution 2280 There are no IPv4 dependencies in this protocol. 2282 6.39 RFC 2217: Telnet Com Port Control Option (TOPT- 2283 COMPO) 2285 There are no IPv4 dependencies in this protocol. 2287 6.40 RFC 2295: Transparent Content Negotiation in 2288 HTTP (TCN-HTTP) 2290 There are no IPv4 dependencies in this protocol. 2292 6.41 RFC 2296: HTTP Remote Variant Selection 2293 Algorithm � RVSA/1.0 (HTTP-RVSA) 2295 There are no IPv4 dependencies in this protocol. 2297 6.42 RFC 2307: An Approach for Using LDAP as a 2298 Network Information Service (LDAP-NIS) 2300 This protocol assumes IPv4 addressing in its schema, as shown in 2301 Section 3. (Attribute definitions): 2303 "( nisSchema.1.19 NAME 'ipHostNumber' 2304 DESC 'IP address as a dotted decimal, eg. 192.168.1.1, 2305 omitting leading zeros' 2306 EQUALITY caseIgnoreIA5Match 2307 SYNTAX 'IA5String{128}' ) 2308 ( nisSchema.1.20 NAME 'ipNetworkNumber' 2309 DESC 'IP network as a dotted decimal, eg. 192.168, 2310 omitting leading zeros' 2311 EQUALITY caseIgnoreIA5Match 2312 SYNTAX 'IA5String{128}' SINGLE-VALUE ) 2313 ( nisSchema.1.21 NAME 'ipNetmaskNumber' 2314 DESC 'IP netmask as a dotted decimal, eg. 255.255.255.0, 2315 omitting leading zeros' 2316 EQUALITY caseIgnoreIA5Match 2317 SYNTAX 'IA5String{128}' SINGLE-VALUE )" 2319 The document does try to provide some IPv6 support as in Section 2320 5.4. (Interpreting Hosts and Networks): 2322 "Hosts with IPv6 addresses MUST be written in their "preferred" 2323 form as defined in section 2.2.1 of [RFC1884], such that all 2324 components of the address are indicated and leading zeros are 2325 omitted. This provides a consistent means of resolving ipHosts by 2326 address." 2328 However, the defined format mentioned above has been replaced, 2329 hence it is no longer valid. 2331 6.43 RFC 2310: The Safe Response Header Field 2333 There are no IPv4 dependencies in this protocol. 2335 6.44 RFC 2483: URI Resolution Services Necessary for 2336 URN Resolution 2338 There are no IPv4 dependencies in this protocol. 2340 6.45 RFC 2567: Design Goals for an Internet Printing 2341 Protocol (IPP-DG) 2343 There are no IPv4 dependencies in this protocol. 2345 6.46 RFC 2568: Rationale for the Structure of the Model 2346 and Protocol for the Internet Printing Protocol (IPP- 2347 RAT) 2349 There are no IPv4 dependencies in this protocol. 2351 6.47 RFC 2569: Mapping between LPD and IPP 2352 Protocols 2354 There are no IPv4 dependencies in this protocol. 2356 6.48 RFC 2649: An LDAP Control and Schema for 2357 Holding Operation Signatures 2359 There are no IPv4 dependencies in this protocol. 2361 6.49 RFC 2654: A Tagged Index Object for use in the 2362 Common Indexing Protocol 2364 There are no IPv4 dependencies in this protocol. 2366 6.50 RFC 2655: CIP Index Object Format for SOIF 2367 Objects 2369 There are no IPv4 dependencies in this protocol. 2371 6.51 RFC 2656: Registration Procedures for SOIF 2372 Template Types 2374 There are no IPv4 dependencies in this protocol. 2376 6.52 RFC 2657: LDAPv2 Client vs. the Index Mesh 2378 There are no IPv4 dependencies in this protocol. 2380 6.53 RFC 2756: Hyper Text Caching Protocol 2381 (HTCP/0.0) (HTCP) 2383 This protocol claims to be both IPv4 and IPv6 aware, but in Section 2384 2.8. (An HTCP/0.0 AUTH has the following structure), it does make 2385 the following statement: 2387 "SIGNATURE is a COUNTSTR [3.1] which holds the HMAC-MD5 2388 digest (see 2389 [RFC 2104]), with a B value of 64, of the following elements, each 2390 of which is digested in its "on the wire" format, including 2391 transmitted padding if any is covered by a field's associated LENGTH: 2392 IP SRC ADDR [4 octets] 2393 IP SRC PORT [2 octets] 2394 IP DST ADDR [4 octets] 2395 IP DST PORT [2 octets] 2396 HTCP MAJOR version number [1 octet] 2397 HTCP MINOR version number [1 octet] 2398 SIG-TIME [4 octets] 2399 SIG-EXPIRE [4 octets] 2400 HTCP DATA [variable] 2401 KEY-NAME (the whole COUNTSTR [3.1]) [variable]" 2403 The given SIGNATURE calculation should be expanded to support 2404 IPv6 16 byte addresses. 2406 6.54 RFC 2774: An HTTP Extension Framework 2408 There are no IPv4 dependencies in this protocol. 2410 6.55 RFC 2974: Session Announcement Protocol (SAP) 2412 This protocol is both IPv4 and IPv6 aware and needs no changes. 2414 6.56 RFC 3018: Unified Memory Space Protocol 2415 Specification 2417 This protocol seems to support IPv6 but, however, the specification 2418 has definitions for IPv4 addresses. 2420 6.57 RFC 3082: Notification and Subscription for SLP 2422 This protocol is both IPv4 and IPv6 aware, and thus, it requires no 2423 changes. 2425 6.58 RFC 3088: OpenLDAP Root Service An 2426 experimental LDAP referral service 2428 Section 5. (Using the Service) states: 2429 "The service supports LDAPv3 and LDAPv2+ [LDAPv2+] clients 2430 over 2431 TCP/IPv4. Future incarnations of this service may support TCP/IPv6 2432 or other transport/internet protocols." 2434 7 Summary of Results 2436 From the initial survey of 262 RFCs, 17 were identified as having 2437 some form of IPv4 dependency. Results are broken down as follows: 2438 Standards: 4 of 24, or 16.67% 2439 Draft Standards: 3 of 20, or 15.00% 2440 Proposed Standards: 5 of 160, or 3.13% 2441 Experimental RFCs: 5 of 58, or 8.62% 2442 Of the 17 identified, several require no action, either because they 2443 document outdated and unused protocols, or because they document 2444 protocols that are still being updated by the appropriate working 2445 groups. Additionally, there are many instances of standards that 2446 should be updated, but do not cause any operational impact if 2447 they are not. The remaining instances are documented below. 2448 The author has attempted to organize the results in a format 2449 that allows easy reference to other protocol designers. The 2450 following recommendations uses the documented terms "MUST", 2451 "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 2452 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 2453 "OPTIONAL" described in RFC 2119. They should only be 2454 interpreted in the context of RFC 2119 when they appear in all 2455 caps. That is, the word "should" in the previous SHOULD NOT be 2456 interpreted as in RFC 2119. The assignment of these terms has been 2457 based entirely on the authors perceived needs for updates and should 2458 not be taken as an official statement. 2460 7.1 Full Standards 2462 7.1.1 RFC 959: STD 9 File Transfer Protocol 2464 Problems have already been fixed in [6]. 2466 7.1.2 RFC 821: STD 10 Simple Mail Transfer Protocol 2468 The use of literal IP addresses as part of email addresses, 2469 i.e., phil@10.10.10.10, is depreciated and therefore additional 2470 specifications for using literal IPv6 addresses SHOULD NOT be 2471 defined. 2473 7.1.3 RFC 822: STD 11 Standard for the format of ARPA 2474 Internet Text Messages 2476 See section 3.2. 2478 7.1.4 RFC 1305: STD 12 Network Time Protocol 2480 As documented in Section 3.19. above, there are too many 2481 specific references to the use of 32-bit IPv4 addresses. An updated 2482 specification to support NTP over IPv6 packets MUST be created. 2484 7.2 Draft Standards 2486 7.2.1 RFC 1305: Network Time Protocol (NTP) 2488 See Section 7.1.4. 2490 7.2.2 RFC 2396: Uniform Resource Identifiers (URI) Syntax 2492 URI's allow the literal use of IPv4 addresses but have no specific 2493 recommendations on how to represent literal IPv6 addresses. This 2494 problem has already been addressed in [4]. 2496 7.2.3 RFC 2616: HTTP 2498 HTTP allows the literal use of IPv4 addresses, but has no specific 2499 recommendations on how to represent literal IPv6 addresses. This 2500 problem has already been addressed in [4]. 2502 7.3 Proposed Standards 2504 7.3.1 RFC 946: Telnet Terminal LOC 2506 There is a dependency in the definition of the TTYLOC Number 2507 which would require an updated version of the protocol. However, 2508 since this functionality is of marginal value today, a newer version 2509 MAY be created. 2511 7.3.2 RFC 1738: Uniform Resource Locators (URL) 2513 URL's IPv4 dependencies have already been addressed in [4]. 2515 7.3.3 RFC 2384: POP3 URL Scheme 2517 POP URL IPv4 dependencies have already been addressed in [4]. 2519 7.3.4 RFC 2608:SLP v2 2521 The problems of this specification have already been addressed in 2522 [5]. 2524 7.3.5 RFC 3017: XML DTP For Roaming Access Phone Books 2526 Extensions SHOULD be defined to support IPv6 addresses. 2528 7.4 Experimental RFCs 2530 7.4.1 RFC 1235:The Coherent File Distribution Protocol 2532 This protocol relies on IPv4 and a new protocol standard SHOULD 2533 NOT be produced. 2535 7.4.2 RFC 1459: IRC Protocol 2537 This protocol relies on IPv4 and a new protocol standard SHOULD 2538 be produced. 2540 7.4.3 RFC 1986: Simple File Transfer Using Enhanced TFTP 2542 This protocol relies on IPv4 and a new protocol standard MAY be 2543 produced. 2545 7.4.4 RFC 2090: TFTP Multicast Option 2547 This protocol relies on IPv4 IGMP Multicast and a new protocol 2548 standard MAY be produced. 2550 7.4.5 RFC 2307: Using LDAP as a NIS (RFC 2307) 2552 This document tries to provide IPv6 support but it relies on an 2553 outdated format for IPv6 addresses. A new specification MAY be 2554 produced. 2556 8 Acknowledgements 2558 The author would like to acknowledge the support of the 2559 Internet Society in the research and production of this document. 2560 Additionally, the author would like to thanks his partner in all ways, 2561 Wendy M. Nesser. 2563 9 Security Considerations 2565 This document provides an exhaustive documentation of current 2566 IETF documented standards IPv4 address dependencies. Such 2567 process does not have security implications in itself. 2569 References 2571 [1] P. Nesser II, "Introduction to the Survey of IPv4 Addresses in 2572 Currently Deployed IETF Standards", Internet Draft (Work in 2573 Progress), February 2003. 2575 [2] Crawford, C. and C. Huitema, "DNS Extensions to Support IPv6 2576 Address Aggregation and Renumbering", RFC 2874, July 2000. 2578 [3] Bradner, S., "The Internet Standards Process - version 3", RFC 2579 2026, October 1996. 2581 [4] Hinden., R., Carpenter, B., L. Masinter, "Format For Literal 2582 Addresses in URL's", RFC 2732, December 1999. 2584 [5] E. Guttman, "Service Location Protocol Modifications for IPv6", 2585 RFC 3111, May 2001. 2587 [6] Allman, M., Ostermann, S., Metz C., "FTP Extensions for IPv6 2588 and NATs", RFC 2428, September 1998. 2590 Authors' Addresses 2592 Editor: Rute Sofia 2593 FCCN 2594 Av. Brasil, 101 2595 1700 Lisboa 2596 Portugal 2597 Email: rsofia@fccn.pt 2598 Phone: +351 91 2507273 2600 Philip J. Nesser II 2601 Principal 2602 Nesser & Nesser Consulting 2603 13501 100th Ave NE, #5202 2604 Kirkland, WA 98034 2605 Email: phil@nesser.com 2606 Phone: +1 425 481 4303 2607 Fax: +1 425 482 9721 2608 This draft expires in August 2003. 2610 Intellectual Property Statement 2612 The IETF takes no position regarding the validity or scope of any 2613 intellectual property or other rights that might be claimed to 2614 pertain to the implementation or use of the technology described in 2615 this document or the extent to which any license under such rights 2616 might or might not be available; neither does it represent that it 2617 has made any effort to identify any such rights. Information on the 2618 IETF's procedures with respect to rights in standards-track and 2619 standards-related documentation can be found in BCP-11. Copies of 2620 claims of rights made available for publication and any assurances of 2621 licenses to be made available, or the result of an attempt made to 2622 obtain a general license or permission for the use of such 2623 proprietary rights by implementors or users of this specification can 2624 be obtained from the IETF Secretariat. 2625 The IETF invites any interested party to bring to its attention any 2626 copyrights, patents or patent applications, or other proprietary 2627 rights which may cover technology that may be required to practice 2628 this standard. Please address the information to the IETF Executive 2629 Director. 2631 Full Copyright Statement 2633 Copyright (C) The Internet Society (2003). All Rights Reserved. 2635 This document and translations of it may be copied and furnished to 2636 others, and derivative works that comment on or otherwise explain it 2637 or assist in its implementation may be prepared, copied, published 2638 and distributed, in whole or in part, without restriction of any 2639 kind, provided that the above copyright notice and this paragraph are 2640 included on all such copies and derivative works. However, this 2641 document itself may not be modified in any way, such as by removing 2642 the copyright notice or references to the Internet Society or other 2643 Internet organizations, except as needed for the purpose of 2644 developing Internet standards in which case the procedures for 2645 copyrights defined in the Internet Standards process must be 2646 followed, or as required to translate it into languages other than 2647 English. 2648 The limited permissions granted above are perpetual and will not be 2649 revoked by the Internet Society or its successors or assignees. 2650 This document and the information contained herein is provided on 2651 an 2652 "AS IS" basis and THE INTERNET SOCIETY AND THE 2653 INTERNET ENGINEERING 2654 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 2655 IMPLIED, INCLUDING 2656 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2657 THE INFORMATION 2658 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 2659 IMPLIED WARRANTIES OF 2660 MERCHANTABILITY OR FITNESS FOR A PARTICULAR 2661 PURPOSE.