draft-ietf-tsvwg-iana-ports-07.txt   draft-ietf-tsvwg-iana-ports-08.txt 
Transport Area Working Group M. Cotton Transport Area Working Group M. Cotton
Internet-Draft ICANN Internet-Draft ICANN
Updates: 2780, 2782, 3828, 4340, L. Eggert Updates: 2780, 2782, 3828, 4340, L. Eggert
4960 (if approved) Nokia 4960 (if approved) Nokia
Intended status: BCP J. Touch Intended status: BCP J. Touch
Expires: April 15, 2011 USC/ISI Expires: April 28, 2011 USC/ISI
M. Westerlund M. Westerlund
Ericsson Ericsson
S. Cheshire S. Cheshire
Apple Apple
October 12, 2010 October 25, 2010
Internet Assigned Numbers Authority (IANA) Procedures for the Management Internet Assigned Numbers Authority (IANA) Procedures for the Management
of the Service Name and Transport Protocol Port Number Registry of the Service Name and Transport Protocol Port Number Registry
draft-ietf-tsvwg-iana-ports-07 draft-ietf-tsvwg-iana-ports-08
Abstract Abstract
This document defines the procedures that the Internet Assigned This document defines the procedures that the Internet Assigned
Numbers Authority (IANA) uses when handling registration and other Numbers Authority (IANA) uses when handling registration and other
requests related to the Service Name and Transport Protocol Port requests related to the Service Name and Transport Protocol Port
Number Registry. It also discusses the rationale and principles Number Registry. It also discusses the rationale and principles
behind these procedures and how they facilitate the long-term behind these procedures and how they facilitate the long-term
sustainability of the registry. sustainability of the registry.
skipping to change at page 1, line 49 skipping to change at page 1, line 49
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 15, 2011. This Internet-Draft will expire on April 28, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 22 skipping to change at page 3, line 22
5.1. Service Name Syntax . . . . . . . . . . . . . . . . . . . 9 5.1. Service Name Syntax . . . . . . . . . . . . . . . . . . . 9
5.2. Service Name Usage in DNS SRV Records . . . . . . . . . . 10 5.2. Service Name Usage in DNS SRV Records . . . . . . . . . . 10
6. Port Number Ranges . . . . . . . . . . . . . . . . . . . . . . 10 6. Port Number Ranges . . . . . . . . . . . . . . . . . . . . . . 10
6.1. Service names and Port Numbers for Experimentation . . . . 11 6.1. Service names and Port Numbers for Experimentation . . . . 11
7. Principles for Service Name and Transport Protocol Port 7. Principles for Service Name and Transport Protocol Port
Number Registry Management . . . . . . . . . . . . . . . . . . 12 Number Registry Management . . . . . . . . . . . . . . . . . . 12
7.1. Past Principles . . . . . . . . . . . . . . . . . . . . . 12 7.1. Past Principles . . . . . . . . . . . . . . . . . . . . . 12
7.2. Updated Principles . . . . . . . . . . . . . . . . . . . . 13 7.2. Updated Principles . . . . . . . . . . . . . . . . . . . . 13
8. IANA Procedures for Managing the Service Name and 8. IANA Procedures for Managing the Service Name and
Transport Protocol Port Number Registry . . . . . . . . . . . 15 Transport Protocol Port Number Registry . . . . . . . . . . . 15
8.1. Service Name and Port Number Registration . . . . . . . . 15 8.1. Service Name and Port Number Registration . . . . . . . . 16
8.2. Service Name and Port Number De-Registration . . . . . . . 20 8.2. Service Name and Port Number De-Registration . . . . . . . 20
8.3. Service Name and Port Number Re-Use . . . . . . . . . . . 20 8.3. Service Name and Port Number Re-Use . . . . . . . . . . . 20
8.4. Service Name and Port Number Revocation . . . . . . . . . 21 8.4. Service Name and Port Number Revocation . . . . . . . . . 21
8.5. Service Name and Port Number Transfers . . . . . . . . . . 21 8.5. Service Name and Port Number Transfers . . . . . . . . . . 21
8.6. Maintenance Issues . . . . . . . . . . . . . . . . . . . . 22 8.6. Maintenance Issues . . . . . . . . . . . . . . . . . . . . 22
8.7. Disagreements . . . . . . . . . . . . . . . . . . . . . . 22 8.7. Disagreements . . . . . . . . . . . . . . . . . . . . . . 22
9. Security Considerations . . . . . . . . . . . . . . . . . . . 22 9. Security Considerations . . . . . . . . . . . . . . . . . . . 22
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
10.1. Service Name Consistency . . . . . . . . . . . . . . . . . 23 10.1. Service Name Consistency . . . . . . . . . . . . . . . . . 23
10.2. Port Numbers for SCTP and DCCP Experimentation . . . . . . 25 10.2. Port Numbers for SCTP and DCCP Experimentation . . . . . . 25
skipping to change at page 10, line 16 skipping to change at page 10, line 16
In approximately 98% of cases, the new "service name" is exactly the In approximately 98% of cases, the new "service name" is exactly the
same as the old historic "short name" from the IANA web forms same as the old historic "short name" from the IANA web forms
[SYSFORM] [USRFORM]. In approximately 2% of cases, the new "service [SYSFORM] [USRFORM]. In approximately 2% of cases, the new "service
name" is derived from the old historic "short name" as described name" is derived from the old historic "short name" as described
below in Section 10.1. below in Section 10.1.
The rules for valid service names, excepting the limit of 15 The rules for valid service names, excepting the limit of 15
characters maximum, are also expressed below (as a non-normative characters maximum, are also expressed below (as a non-normative
convenience) using ABNF [RFC5234]. convenience) using ABNF [RFC5234].
SRVNAME = (ALPHA / (1*DIGIT [HYPHEN] ALPHA)) *([HYPHEN] ALNUM) SRVNAME = *(1*DIGIT [HYPHEN]) ALPHA *([HYPHEN] ALNUM)
ALNUM = ALPHA / DIGIT ; A-Z, a-z, 0-9 ALNUM = ALPHA / DIGIT ; A-Z, a-z, 0-9
HYPHEN = %x2d ; "-" HYPHEN = %x2d ; "-"
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z [RFC5234] ALPHA = %x41-5A / %x61-7A ; A-Z / a-z [RFC5234]
DIGIT = %x30-39 ; 0-9 [RFC5234] DIGIT = %x30-39 ; 0-9 [RFC5234]
5.2. Service Name Usage in DNS SRV Records 5.2. Service Name Usage in DNS SRV Records
The DNS SRV specification [RFC2782] states that the Service Label The DNS SRV specification [RFC2782] states that the Service Label
part of the owner name of a DNS SRV record includes a "Service" part of the owner name of a DNS SRV record includes a "Service"
element, described as "the symbolic name of the desired service", but element, described as "the symbolic name of the desired service", but
 End of changes. 6 change blocks. 
6 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/