Re: [port-srv-reg] ACTION ITEMS - final updates - ports doc

[Joe Touch <[e-mail]>]

Hi, Lars,

Lars Eggert wrote:
> Hi,
> 
> On 2010-5-19, at 4:01, Joe Touch wrote:
>>>> The current list of registration information is listed in Section 8.1:
>>>>
>>>>     Registration Administrative Contact (REQUIRED)
>>>>     Registration Technical Contact (REQUIRED)
>>>>     Service Name (REQUIRED)
>>>>     Port Number (OPTIONAL)
>>>>     Transport Protocol(s) (REQUIRED if port number requested)
>> I think we agreed to make this "(REQUIRED)" in all cases.
> 
> a port number isn't required for when only a service name is requested, no?

Correct. Port number remains OPTIONAL (see a few lines up).

The transport protocol is not, as per our discussion on the list (TCP,
UDP, SCTP, etc.). I.e., even if an applicant requests a service name
without a port number, they still need to indicate at least one
transport protocol for that service, and only those indicated are
registered.

I.e., here are the specific changes:

<orig>
	Transport Protocol(s) (REQUIRED if port number requested)
<new>
	Transport Protocol(s) (REQUIRED)

<orig>
   o  Transport Protocol(s): If assignment of a port number is desired,
      the transport protocol(s) for which the allocation is requested
      MUST be provided.  This field is currently limited to one or more
      of TCP, UDP, SCTP, and DCCP.
<new>
   o  Transport Protocol(s): The transport protocol(s) for which the
      allocation is requested MUST be provided.  This field is currently
      limited to one or more of TCP, UDP, SCTP, and DCCP. This field is
      required even for services with no port number.

>>>>     Service Code (only REQUIRED for DCCP)
>>>>     Description (REQUIRED)
>>>>     Reference (REQUIRED)
>> It might be useful to move the service name and transport protocol to
>> the top of the list, and indicate that the pair are the "key", i.e.,
>> they define the service.
>>
>> I would suggest adding the following two OPTIONAL fields to the set
>> above, which are NOT provided by the applicant:
>>
>> 	Known Unauthorized Uses
>> 	Assignment comments (de-registration, owner/name change, etc.)
> 
> Can you provide text for those two, so we understand a little better what they'd be about?

<new - insert after Reference (REQUIRED)>
	Known Unauthorized Uses (OPTIONAL)
	Assignment Notes (OPTIONAL)

<new - insert after full description of Reference>

o Known Unauthorized Uses: A list of uses by applications or
organizations who are not the assignee. This list may be augmented by
IANA after assignment when unauthorized uses are reported.

o Assignment Notes: Indications of owner/name change, or any other
assignment process issue. This list may be updated by IANA after
assignment to help track changes to an assignment, e.g.,
de-registration, owner/name changes, etc.

------