Hi Jeff, Actually, except local-multiplier that we call detection-multiplier, the same names are used in both drafts. We can fix that one.
Please note that we are not using the interval-config-type choice given that the single case can be covered by setting desired-min-tx-interval and required-min-rx-interval to the same value. It is then straightforward to map it the device module depending whether single-minimum-interval feature is supported or not. We don't want to complicate the network view of the service with such device-level features. Thank you. Cheers, Med > -----Message d'origine----- > De : Jeffrey Haas [mailto:jh...@pfrc.org] > Envoyé : mardi 31 août 2021 23:31 > À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com> > Cc : Greg Mirsky <gregimir...@gmail.com>; draft-ietf-opsawg-l3sm- > l...@ietf.org; opsawg <ops...@ietf.org>; rtg-bfd WG <rtg- > b...@ietf.org> > Objet : Re: A question on OAM section in draft-ietf-opsawg-l3sm-l3nm > > Med, > > On Mon, Aug 30, 2021 at 12:19:23PM +0000, > mohamed.boucad...@orange.com wrote: > > Hi Greg, > > > > Thank you for checking the OAM part and for sharing this comment. > > > > As you can read in both sections 4 and 5, this model is ** not a > device configuration model **. The focus is on aspects that can be > triggered by service requests and managed by the network controller. > This network view of the service will be then enriched (with other > sources such as local templates/profiles/defaults) to derive the > exhaustive configuration that will be enforced in involved devices > to deliver the requested service. > > > > With that rationale in mind, you can understand why we don’t > import device models but point to the authoritative RFCs for aspects > that we think make sense to be tweaked at the network-level. > > Greg's suggestion is not to import a device specific model. His > suggestion is to leverage groupings defined in the BFD yang model > that have the configuration semantics typical of most BFD > implementations. > > Put a different way, if you're defining BFD parameters, why would > you have different names or structures for BFD configuration > elements in your module than everyone else? > > -- Jeff _________________________________________________________________________________________________________________________ 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.
