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

[Glen Zorn <[e-mail]>]

On 3/8/2012 10:48 PM, Peter Saint-Andre wrote:
> On 3/8/12 8:27 AM, Jouni Korhonen wrote:
>> Peter,
>>
>> The text in recently submitted -30 Section 5.2 (
>> http://tools.ietf.org/html/draft-ietf-dime-rfc3588bis-30#section-5.2) should
>> also address your DISCUSS.
> 
> Thanks for the pointer to a specific section.
> 
> That change does address my primary concern, which was:
> 
>    RFC 3588 used DNS SRV Proto values of 'tcp' and 'sctp' for the SRV
>    Service of 'diameter'. 3588bis seems to add two more Proto values:
>    'tls' and 'dtls'.  However, RFC 6335, which defines updated rules
>    for the ports and services registry, allows only TCP, UDP, SCTP,
>    and DCCP as transport protocols.
> 
> My secondary concern was this:
> 
>    Furthermore, this specification does not register the 'diameter'
>    SRV Service value in accordance with RFC 6335. 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?

> 
> Thanks!
> 
> Peter
>