Thanks Med, that looks great.

David, I approve the -10.

P.


On 22/05/24 07:42, mohamed.boucad...@orange.com wrote:

Hi Paul,

-10 fixes all these, including the ToC level.

Thank you.

Cheers,

Med

*De :* Aitken, Paul <pait...@ciena.com>
*Envoyé :* mardi 21 mai 2024 22:58
*À :* BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com>; drafts-expert-review-comm...@iana.org
*Cc :* ie-doct...@ietf.org; opsawg <opsawg@ietf.org>
*Objet :* Re: [Ie-doctors] [IANA #1363822] Expert review for draft-ietf-opsawg-ipfix-fixes (ipfix)


Med,



    * In the TOC, all the OLD / NEW section names are distracting. It
    would be much more readable if the TOC was limited to just two levels:

        1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4

        2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   5

        3.  Why An RFC is Needed for These Updates? . . . . . . . . . . .   6

        4.  Update the Description  . . . . . . . . . . . . . . . . . . .   6

          4.1.  sourceTransportPort . . . . . . . . . . . . . . . . . . .   6

          4.2.  destinationTransportPort  . . . . . . . . . . . . . . . .   7

          4.3.  forwardingStatus  . . . . . . . . . . . . . . . . . . . .   8


Is this not possible?



    * 6.11.2 NEW


    Please append [RFC5102 [iana.org]
    
<https://urldefense.com/v3/__https://www.iana.org/go/rfc5102__;!!OSsGDw!JNH0CYLK4vjkABu-cFwUmkIE5CBNlemiA4NBseRFoWxSRTTB9y5yUwj2nT9VV_EvrAwtuqT3ANY2CkyFV-zmjrvn$>]
    here.

        For the methods parameters, Information Elements are defined
        in the information model document *[RFC5102]*.

    */[Med] OK as that was the intent at the time. However, given that
    5102 is obsoleted, should we simply point to the registry itself
    instead of 5102?/*


Yes please, that seems good.


6.22.2. NEW

Typo: remove "at" in the registry name:

        SeemibCaptureTimeSemanticsat  registry at

P.

____________________________________________________________________________________________________________
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,
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, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

_______________________________________________
ie-doctors mailing list --ie-doct...@ietf.org
To unsubscribe send an email toie-doctors-le...@ietf.org
_______________________________________________
OPSAWG mailing list -- opsawg@ietf.org
To unsubscribe send an email to opsawg-le...@ietf.org

Reply via email to