80 likes | 198 Views
IPv4 Dependencies in Applications Area Specifications. Margaret Wasserman mrw@windriver.com draft-ietf-v6ops-ipv4survey-apps-01.txt. IPv4 Survey Effort. Extensive survey of IETF standards-track and experimental RFCs for IPv4 dependencies
E N D
IPv4 Dependencies in Applications Area Specifications Margaret Wasserman mrw@windriver.com draft-ietf-v6ops-ipv4survey-apps-01.txt
IPv4 Survey Effort • Extensive survey of IETF standards-track and experimental RFCs for IPv4 dependencies • Conducted by Phil Nesser for the ngtrans WG, transferred to the v6ops WG • Ready for wider review and ACTION!!
Extent of the Problem • Identified 9 Applications area RFCs that have IPv4 dependencies • Some are higher priority than others
Full Standards • RFC 821/2821: SMTP • Literal IP addresses in mail addresses • RFC 822/2822: Internet Message Format • Domain literals • RFC 1119/1305: NTP • Many IPv4 dependencies and references
Draft Standards • RFC 946: Telnet Terminal LOC • Definition of TTYLOC number • RFC 3017: XML DTP For Roaming Access Phone Books • Doesn't support IPv6
Experimental RFCs • RFC 1235: Coherent File Distribution • 32-bit IP addresses in TIYT packets • RFC 1459: IRC • IP address "dot format" used in error messages and hostnames • RFC 2090: TFTP Multicast Option • No support for IPv6 • RFC 2307: Using LDAP as a NIS • Uses outdated IPv6 address format
What Can You Do? • Review the document and determine if it is correct • Review the recommendations • Determine an action plan to correct the problems that have been identified • What should we do with this document?
One more thing… • v6ops WG is working on guidelines for writers of IPv6 applications and application protocols • draft-shin-v6ops-application-transition-01.txt • Your review and input would be helpful