Magnus, Lars, Tom,
Your text makes sense.
As long as we are going formal, I think the following would have to
be:
Ports in the well known and registered ranges SHOULD NOT be used
without
registration.
SHOULD NOT -> MUST NOT
Might as well state what we mean. It's hard to make sense
of the intermediate rule.
If the group likes this or something evolving from this, my
advice to Tom and Lars is that it will need to get a WGLC to make
sure that everyone is fine with the change to the spec.
Then the AD (me), who has been giving parallel AD review here,
will have to get IESG review, before we can be sure it's ok
to make a Post-Approval change.
But I'd classify this a big catch, that justifies the Post-Approval
change, so I think this should proceed.
Allison
Hi,
I am supporting that we start from scratch. However I think the
language
should be a bit more explicit. I am fine with first come first served
rules. However a statement on intention on different parts of the
number
space should be clearly stated. The proposed text is to loosely
defined
and using implicit references. I think DCCP should write their
rules to
be completely stand alone.
My initial proposal for this would be:
19.9 DCCP Ports
19.9.1 Registration Rules
DCCP connections may make use of well known port numbers, as in
TCP and
UDP, although the Service Code may lessen this requirement somewhat.
IANA is requested to create and maintain a port registry using the
rules
below. The ports are combined with the service code to explicitly
indicate the application and usage of the DCCP connection.
The ports registry is divided into three ranges. The Well Known ports
are all ports in the range 0 to 1023. The Registered Ports in the
range
1024 to 49151. The Dynamic ports are ports in the range 49152 to
65535.
The well known ports are intended for services that on most
systems is
run by the system (or root) processes or by programs executed by
privileged users.
The registered ports are intended for any application desiring a
fixed
contact point on a system. This range of ports can on most systems be
used by ordinary user processes or programs executed by ordinary
users.
Ports in the well known and registered ranges SHOULD NOT be used
without
registration.
Dynamic ports are intended for DCCP connections intended for
temporary
use. This includes out-of-band negotiated ports and service codes,
application testing prior to registration of a dedicated port and
service codes in the well known or registered range. Dynamic ports
SHALL
NOT be registered.
All registrations allowed by the rules are done using the first come,
first served rules as defined by [RFC2434]. Each port registration
SHALL
include the following information:
- Port number that is requested to be registered.
- Service code(s) that combined with the port definitely identify the
service or application.
- Short name for Service/Application
- Description on purpose for port. Either a short description or a
reference to document describing the intended usage of the port
and
service code. The minimal required description is an
application name.
- Name and contact information of person/entity doing the
registration.
Registrations coming from IETF WGs needs only to indicate which WG
that performed the registration but is recommend to also
indicate a
contact person.
19.9.2 Registration Template
Port number requested:
Service Code(s):
Short name for port:
Description:
Contact Person
Name:
Organization:
email:
19.9.3 Initial Registrations
Port number requested: 9
Service code: All
Short name for port: Discard Port
Description: The discard ports shall discard all incoming DCCP
packets
without sending any response.
Contact Person
Name: Eddie Kohler
Organization: IETF DCCP WG
email: dccp at ietf.org, kohler at CS.UCLA.EDU