Hi Benoît,

You got it.

We may use the identity from RFC9181... but that will add a dependency on other 
modules (e.g., ietf-routing-types) not needed for the IM. We went with 
simplicity approach here.

Cheers,
Med (as author)

PS: Most of your other comments are addressed in 
https://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-opsawg-discardmodel&url_2=https://o-pylypenko.github.io/draft-ietf-opsawg-discardmodel/draft-ietf-opsawg-discardmodel.txt.
 We will follow-up with more context once we are ready.

De : [email protected] <[email protected]>
Envoyé : jeudi 30 octobre 2025 21:58
À : [email protected]; [email protected]
Objet : Re: [OPSAWG]Review of draft-ietf-opsawg-discardmodel-09 - part 1


Dear authors,

I have been thinking some more about this (and also I read the YANG data model, 
which helped me), so replying one of my point. Hopefully, answering it





- in the IM YANG model, I am surprised that you had to define those identities

     identity address-family {

       description

         "Defines a type for the address family.";

     }



     identity ipv4 {

       base address-family;

       description

         "Identity for an IPv4 address family.";

     }



     identity ipv6 {

       base address-family;

       description

         "Identity for an IPv6 address family.";

     }



     identity all {

       base address-family;

       description

         "Identity for all address families.";

     }



I would have been expecting that it was defined already in an existing IETF 
YANG modules.

The YANG doctors will tell.


New identities or reused identities, I guess it doesn't matter too much for the 
YANG information model, right?
The point being to be able to understand the concepts.  And this is the reason 
why you only imported ietf-yang-types and ietf-yang-structure-ext, which were 
absolutely required for the YANG definitions.

Is my understanding correct?

Regards, Benoit
____________________________________________________________________________________________________________
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.
_______________________________________________
OPSAWG mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to