1 / 13

IANA Port Number and Service Name Procedures

IANA Port Number and Service Name Procedures. draft-ietf-tsvwg-iana-ports-03 Joe Touch, USC/ISI For the IANA Port Procedures team. Outline. Document Goals Unifying Registries Allocation Principles Procedure Updates Other Issues. Doc. Goals. Update registration procedures

knox-abbott
Download Presentation

IANA Port Number and Service Name Procedures

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. IANA Port Number and Service Name Procedures draft-ietf-tsvwg-iana-ports-03 Joe Touch, USC/ISI For the IANA Port Procedures team

  2. Outline • Document Goals • Unifying Registries • Allocation Principles • Procedure Updates • Other Issues

  3. Doc. Goals • Update registration procedures • Unify registries • What this doc is not: • Guidance to registrants/app designers • Specification of port/name spaces

  4. Current Registries • Port numbers (IANA; /etc/services) • TCP, UDP • Number and short name • Service names (DNS; SRV) • DNS SRV • Name only • Other transports (IANA) • SCTP, DCCP • Includes DCCP service codes

  5. Registry Concerns • Confusion over name-only registrations • Do port name owners (in /etc/services) need to register again with DNS SRV? • Lack of IANA coordination • Different managers • IANA, individuals • Lack of unified info. • Ports table, SRV table, DCCP service codes

  6. Unified Registry • One table for all • Transports – TCP, UDP, DCCP, SCTP, future • DNS SRV • Indexed by name • One name space across all registries • Info. can be used by any discovery mechanism • What this doc does not do: • Specify how IANA expresses the details

  7. Syntax Changes • US ASCII a-z, 0-9, ‘-’ (hyphen), case insensitive • No hyphen start or end • Not all numbers • 1-15 characters • Current name changes • Included as legacy • New name replaces special chars with ‘-’ • One exception – whois++ becomes whoisplusplus

  8. Prev. Allocation Princ. • TCP and UDP assigned together • Port numbers as primary • Service names informative only • No well-defined syntax • Informal/inconsistent conservation • SCTP, DCCP separate from TCP/UDP • Couldn’t assign name w/o number

  9. New Alloc. Princ. • One port per service • One port for all versions (incl. secure) • One port for all of device types w/in a svc. • Port only for transports requested • IANA may recover/reuse/transfer ports • IANA handles names • FCFS w/o numbers, expert review otherwise

  10. Procedures • Current • Register • New • De-Register – owner initiated recovery • Re-Use – same owner, diff. meaning • Revoke – IANA initiated recovery • Transfer – change owners

  11. Proc. Details • Separate assignee roles • Owner • IETF for RFC-specified items • Determines who can transfer • Can be an organization • Tech Contact • Must be an individual

  12. Other Issues • Extends experimental (1021, 1022) for DCCP and SCTP • All new transport registries will include these. • DCCP • Expert review for more than 5 service codes • Avoid 0-1024 range • Service code to at most one port

  13. Other Work • Format of unified information • XML table • Name as index • *Lots* of other information • IANA managed, but not RFC mandated since not used by a protocol • User Guidelines • Lots of advice from IANA Port Experts Review Team, community input

More Related