Re: [Dime] Peter Saint-Andre's Discuss on draft-ietf-dime-rfc3588bis-29: (withDISCUSS and COMMENT)

[jouni korhonen <[e-mail]>]

On Mar 11, 2012, at 9:07 AM, Glen Zorn wrote:

> On 3/9/2012 10:50 PM, Peter Saint-Andre wrote:
> 
> ...
> 
>>>>> My secondary concern was this:
>>>>> 
>>>>>  Furthermore, this specification does not register the 'diameter'
>>>>>  SRV Service value in accordance with RFC 6335. 
> 
> And yet, "diameter" already is shown in the IANA registry with SCTP, TCP
> and UDP as protocols.
> 
>>>>>  Because these values
>>>>>  were not defined or registered by draft-ietf-dime-extended-naptr, I
>>>>>  think they need to be defined here.
>>>>> 
>>>>> Please see Section 8.1 of RFC 6335 for the registration procedure:
>>>>> 
>>>>> http://tools.ietf.org/html/rfc6335#section-8.1
>>>>> 
>>>>> I think you can add this quite easily in a revised I-D before the
>>>>> deadline on Monday, or your AD can add an RFC Editor note.
>>>> 
>>>> OK, what to do about the port number, etc.?  Jouni, since you
>>>> volunteered that we would do this, how about writing the section?
>>> 
>>> That's ok.
> 
> Can this be done before the deadline Monday?

I try to get this done tonight.

- Jouni


> 
>> 
>> Thanks, Jouni. I think it should be easy, because RFC 6335 asks for:
>> 
>>      Service Name (REQUIRED)
>>      Transport Protocol(s) (REQUIRED)
>>      Assignee (REQUIRED)
>>      Contact (REQUIRED)
>>      Description (REQUIRED)
>>      Reference (REQUIRED)
>>      Port Number (OPTIONAL)
>>      Service Code (REQUIRED for DCCP only)
>>      Known Unauthorized Uses (OPTIONAL)
>>      Assignment Notes (OPTIONAL)
>> 
>