Re: [Dime] AD review of draft-ietf-dime-rfc4005bis-09.txt

[Benoit Claise <[e-mail]>]

Hi Lionel,
>
> Hi,
>
> Benoit, it is true that there is in the RFC4005 an implicit reference 
> to the RFC3588 when describing the new command (AAR/AAA). It could be 
> useful to explicitly state that the definition of the new command 
> follows the rules described in RFC3588(bis).
>
That would work for me

Regards, Benoit.
>
> About Dieter's comment, the CCF specification of a command is clearly 
> defined in RFC3588(bis) with an explicit reference to RFC5234 for 
> further details, so I don't think that it is needed to provide again 
> the description in this specification and in any other diameter 
> specification referencing the RFC3588(bis).
>
> Regards,
>
> Lionel
>
> *De :*[e-mail] [mailto:[e-mail]]
> *Envoyé :* mercredi 11 juillet 2012 09:29
> *À :* [e-mail]; MORAND Lionel RD-CORE
> *Cc :* [e-mail]
> *Objet :* AW: [Dime] AD review of draft-ietf-dime-rfc4005bis-09.txt
>
> Hello Benoit and Lionel
>
> as a reader of the Diameter specifications I would support a proposal 
> to define the notification within the document. Clearly "somewhere" it 
> is stated but for a simple reader it would be very helpful to have 
> such an description of the notification in the same document as it is 
> used.
>
> Best regards
>
> Dieter Jacobsohn
>
> Deutsche Telekom AG
> Group Technology
> Dieter Jacobsohn
> Landgrabenweg 151, 53227 Bonn
> [phone] (Tel.)
> [phone] (Fax)
> [phone] (Mobil)
> E-Mail: [e-mail] <mailto:[e-mail]>
> www.telekom.com <http://www.telekom.com/>
>
> Erleben, was verbindet.
>
> Deutsche Telekom AG
> Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender)
> Vorstand: René Obermann (Vorsitzender),
> Dr. Manfred Balz, Reinhard Clemens, Niek Jan van Damme,
> Timotheus Höttges, Claudia Nemat,  Prof. Dr. Marion Schick
> Handelsregister: Amtsgericht Bonn HRB 6794
> Sitz der Gesellschaft Bonn
> USt-IdNr. DE 123475223
>
> *Große Veränderungen fangen klein an****--**Ressourcen schonen und 
> nicht jede E-Mail drucken.*
>
> ------------------------------------------------------------------------
>
> *Von:*[e-mail] [mailto:[e-mail]] *Im Auftrag 
> von *Benoit Claise
> *Gesendet:* Mittwoch, 11. Juli 2012 09:09
> *An:* [e-mail]
> *Cc:* dime mailing list
> *Betreff:* Re: [Dime] AD review of draft-ietf-dime-rfc4005bis-09.txt
>
> Hi Lionel,
>
>     Hi Benoit,
>
>       
>
>     - I could not find the meaning of * in, for example,
>
>       
>
>                                [ CHAP-Auth ]
>
>                                [ CHAP-Challenge ]
>
>                              * [ Framed-Compression ]
>
>                                [ Framed-Interface-Id ]
>
>                                [ Framed-IP-Address ]
>
>                              * [ Framed-IPv6-Prefix ]
>
>                                [ Framed-IP-Netmask ]
>
>                                [ Framed-MTU ]
>
>                                [ Framed-Protocol ]
>
>                                [ ARAP-Password ]
>
>                                [ ARAP-Security ]
>
>                              * [ ARAP-Security-Data ]
>
>                              * [ Login-IP-Host ]
>
>                              * [ Login-IPv6-Host ]
>
>                                [ Login-LAT-Group ]
>
>                                [ Login-LAT-Node ]
>
>                                [ Login-LAT-Port ]
>
>                                [ Login-LAT-Service ]
>
>                              * [ Tunneling ]
>
>                              * [ Proxy-Info ]
>
>                              * [ Route-Record ]
>
>                              * [ AVP ]
>
>     */[[LM]]/*the « * » in front the AVP means that 0, 1 or more AVP scan be present in the request (or in a Grouped AVP). It follows rules used in RFC3588 and defined in RFC 5234 (http://tools.ietf.org/html/rfc5234#section-3.6).
>
>       
>
> BC> Thanks for the education.
> Is this so obvious to the Diameter readers, including the newcomers, 
> that we don't need to mention it?
> In other words, am I the only one NOT knowing this? ;-)
>
> Regards, Benoit.
>
>
> Regards,
>   
> Lionel
> _________________________________________________________________________________________________________________________
>   
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>   
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.