html5-img
1 / 8

IPv4 Dependencies in Applications Area Specifications

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

joy-short
Télécharger la présentation

IPv4 Dependencies in Applications Area Specifications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IPv4 Dependencies in Applications Area Specifications Margaret Wasserman mrw@windriver.com draft-ietf-v6ops-ipv4survey-apps-01.txt

  2. 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!!

  3. Extent of the Problem • Identified 9 Applications area RFCs that have IPv4 dependencies • Some are higher priority than others

  4. 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

  5. Draft Standards • RFC 946: Telnet Terminal LOC • Definition of TTYLOC number • RFC 3017: XML DTP For Roaming Access Phone Books • Doesn't support IPv6

  6. 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

  7. 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?

  8. 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

More Related