REVISED Port Number Procedures DRAFT
4
REVISED Port Number Procedures DRAFT TSVAREA WG Meeting Vancouver, IETF-70 Presented by: Michelle Cotton, IANA
description
REVISED Port Number Procedures DRAFT. TSVAREA WG Meeting Vancouver, IETF-70 Presented by: Michelle Cotton, IANA. Current Guidelines. Currently defined in RFC 2780 but not clear Ports assigned via IANA paid ‘expert’ reviewer (no other registry has this) - PowerPoint PPT Presentation
Transcript of REVISED Port Number Procedures DRAFT
REVISED Port Number Procedures
DRAFT
TSVAREA WG Meeting
Vancouver, IETF-70
Presented by: Michelle Cotton, IANA
Current Guidelines
Currently defined in RFC 2780 but not clearPorts assigned via IANA paid ‘expert’
reviewer (no other registry has this)Currently allow NDA - This causes issues
when having an official expert designatedAssign both the TCP and UDPGuidelines for SCTP and DCCP are different
Proposed Guidelines
IANA requesting official designation of expert(s) by the IESG
NO NDA’sPort number space conservation and clarity
Only assign what the requester is asking (example UDP only) and reserve the others
Approximately 15-20 ports assigned in November October
Not retroactive
Remaining issues
A discussion distinct from the port registry update document will need to define how port number allocation interacts with service namesRequests for service names without numberRenaming existing ports(eg. Reusing port number for new protocol)
Well known (0-1023) vs. Registered (1024+)
XML’izing the port numbers registry
