1 / 9

Joe Touch and Michelle Cotton touch@isi michelle.cotton@icann

IETF-72 TSVAREA Working Group Update on draft-ietf-tsvwg-iana-ports and other ports related work items. Joe Touch and Michelle Cotton touch@isi.edu michelle.cotton@icann.org. Update since IETF-71. TSVAREA WG has taken this I-D as a working group document draft-ietf-tsvwg-iana-ports-00

kmoses
Download Presentation

Joe Touch and Michelle Cotton touch@isi michelle.cotton@icann

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. IETF-72TSVAREA Working GroupUpdate on draft-ietf-tsvwg-iana-portsand other ports related work items Joe Touch and Michelle Cotton touch@isi.edu michelle.cotton@icann.org Dublin, IETF

  2. Update since IETF-71 TSVAREA WG has taken this I-D as a working group document draft-ietf-tsvwg-iana-ports-00 Changes since draft-cotton-tsvwg-iana-ports • Clarity of language and more detail • Port range descriptions (system, user, dynamic) • Title change • Section for IANA procedures (incl. revoke, xfer, etc.) • Port use recommendations (hints at IANA process) • Added DCCP updates to the appendix Dublin, IETF

  3. New IANA procedures • User requests • Deregister, revoke, transfer • Allocation only requested transport • Others reserved but not allocated • Defines registration info. • Some required, some optional • Requires service name uniqueness • Cleanup and unify various of service names lists • Variants of “RESERVED” Dublin, IETF

  4. Port use (IANA decision hints) • One port per service (see open issues) • One port for all versions of a service • One port for all devices supporting a service • Do NOT use multiple ports for load balancing • Suggests use of nonce on experimental ports Dublin, IETF

  5. Open Issues • Should services sharing a port require the same protocol? • e.g., DNS on TCP/UDP vs. TCP data / UDP sync • i.e., is a service a single app protocol or set? • Service name requirements • Syntax, “owned” by DNSSRV, TCPMUX, etc. • Need for a common discovery protocol? • vs. allocating UDP for every service? • akin to Apple's Bonjour (maybe simplified?) Dublin, IETF

  6. Next Steps • Feedback on current version • Resolution of open issues • Socialization with other IETF Areas • Begin development of companion document • History of ports • How, when, to use ports • Is an assigned port really needed? • Other options Dublin, IETF

  7. Port Experts • IESG officially designated experts • Port process slow due to learning curve • We need more experts • Volunteer • IESG officially designates • Review 3-5 applications per month • On AVERAGE review time = 10 minutes Dublin, IETF

  8. Other related work items • Review and Re-formatting of the port numbers registry • Will be seeking input from the working group on new format • XML Conversion • Revised application form for port-numbers Dublin, IETF

  9. Thank you! Special thanks to the “Ports Group”! Please send questions to Joe Touch or Michelle Cotton touch@isi.edu michelle.cotton@icann.org Dublin, IETF

More Related