Re: [Dime] Review of draft-jones-3gpp-eps-command-codes-00

["Tschofenig, Hannes (NSN - FI/Espoo)" <[e-mail]>]

I will do the shepherd. 
 

>-----Original Message-----
>From: [e-mail] [mailto:[e-mail]] On 
>Behalf Of ext Mark Jones
>Sent: 09 December, 2008 16:16
>To: Romascanu, Dan (Dan); Victor Fajardo; [e-mail]
>Subject: Re: [Dime] Review of draft-jones-3gpp-eps-command-codes-00
>
>> -----Original Message-----
>> From: [e-mail] [mailto:[e-mail]] On Behalf 
>> Of Romascanu, Dan (Dan)
>> Sent: December 8, 2008 14:19
>> To: Mark Jones; Victor Fajardo; [e-mail]
>> Subject: Re: [Dime] Review of draft-jones-3gpp-eps-command-codes-00
>>
>> Mark,
>>
>> Do not forget that in order to complete the submission process you 
>> need to find a proto-shepherd, and the shepherd needs to submit a 
>> proto write-up.
>>
>
>Understood, Dan. A draft PROTO write-up is being prepared by 
>the authors while we continue the search for a doc shepherd.
>
>Thanks
>Mark
>
>
>
>> Thanks and Regards,
>>
>> Dan
>>
>>
>> > -----Original Message-----
>> > From: [e-mail] [mailto:[e-mail]] 
>On Behalf 
>> > Of Mark Jones
>> > Sent: Monday, December 08, 2008 7:06 PM
>> > To: Victor Fajardo; [e-mail]
>> > Subject: Re: [Dime] Review of draft-jones-3gpp-eps-command-codes-00
>> >
>> > Thanks for the review, Victor.
>> >
>> > Responses/Comments inline. I'll incorporate your changes into the 
>> > -01 version and publish shortly.
>> >
>> >
>> > > -----Original Message-----
>> > > From: Victor Fajardo [mailto:[e-mail]]
>> > > Sent: December 4, 2008 15:56
>> > > To: [e-mail]; Mark Jones; MORAND Lionel RD-CORE-ISS
>> > > Subject: Review of draft-jones-3gpp-eps-command-codes-00
>> > >
>> > > Hi Mark/Lionel,
>> > >
>> > > Comments on draft-jones-3gpp-eps-command-codes-00:
>> > >
>> > > * Maybe add the following sentence to the introduction to
>> > clarify the
>> > > purpose of the doc:
>> > >
>> > > "This document defines the assigned values of the command
>> > codes used
>> > > in these applications."
>> > >
>> >
>> > Ok.
>> >
>> > >
>> > > * Change 1st paragraph of Sec 3 from:
>> > >
>> > > "As described in [TS29.272], the 3GPP S6a application
>> specifies the
>> > >  following command pairs:"
>> > >
>> > > to:
>> > >
>> > > "3GPP S6a application in [TS29.272] requires the definition
>> > of command
>> > > code values for
>> > >  the following command pairs:"
>> > >
>> >
>> > Ok
>> >
>> > >
>> > > * Change 2nd paragraph of Sec 3 from:
>> > >
>> > > "Also described in [TS29.272], the 3GPP S13 application
>> > specifies the
>> > >  following command pair:"
>> > >
>> > > to:
>> > >
>> > > "3GPP S13 application in [TS29.272] requires the 
>definition of the 
>> > > command code values for  the following command pairs:"
>> > >
>> >
>> > Ok
>> >
>> > >
>> > > * Change 2nd paragraph of the IANA considerations from:
>> > >
>> > > "This document defines values in the namespaces that have
>> > been created
>> > >   and defined in the Diameter Base [RFC3588]. The IANA
>> > Considerations
>> > >  section of that document details the assignment criteria.
>> > Values ..."
>> > >
>> > > to:
>> > >
>> > > "This document defines values in the namespaces that have
>> > been created
>> > >  and defined in Sec 11.2.1 of the Diameter Base
>> [RFC3588].  Sec 11,
>> > >  IANA Considerations of [RFC3588] details the assignment 
>criteria.
>> > >  Values ..."
>> > >
>> >
>> > Ok but would prefer "Section" instead of "Sec".
>> >
>> > >
>> > > * Are the values intended to forward compatible with bis ?
>> > If so, does
>> > > it need to
>> > >   fall in the 0x800000 - 0xfffffd range ? If so, do we need
>> > to mention
>> > >   that in the IANA actions (since this is absent in 3588) ?
>> > >
>> > > As it is, the document complies with the 3588 command code
>> > allocation
>> > > process.
>> > >
>> >
>> > My understanding is that IANA must follow the rules in 3588 until 
>> > 3588bis is ratified. That unfortunately means that the 
>3GPP S6a/S13 
>> > values will be taken from the IETF range as proposed in 
>3588bis but 
>> > I see no means to give any alternative guidance to IANA.
>> >
>> > Thanks
>> > Mark
>> > _______________________________________________
>> > DiME mailing list
>> > [e-mail]
>> > https://www.ietf.org/mailman/listinfo/dime
>> >
>> _______________________________________________
>> DiME mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/dime
>>
>_______________________________________________
>DiME mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/dime
>
_______________________________________________
DiME mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/dime