Thus spake Job Snijders (job=40fastly....@dmarc.ietf.org) on Wed, Dec 06, 2023 at 04:42:05PM +0100: > Dear GROW, > > The author of draft-pels-grow-yang-bgp-communities asked whether the > GROW working group could consider adoption of their internet-draft. > > This message is a request to the group for feedback on whether this > internet-draft should be adopted. > > Title: YANG Module for BGP Communities > Abstract: > This document provides a YANG module for describing BGP communities. > > The Internet-Draft can be found here: > https://www.ietf.org/archive/id/draft-pels-grow-yang-bgp-communities-00.html > > Please share with the mailing list if you would like this work to be > adopted by GROW, are willing to review and/or otherwise contribute to > this draft! > > WG Adoption call ends January 6th, 2024.
I think it is an interesting approach to a real problem, and worthy of group adoption. An overall question I have is with so many nominally unstructured string fields, does that just push the problem out further? For example, in the presentation at IETF, it was mentioned some communities are informational and some are actions. Should there be enumerated fields in the model denoting this? Things in my mind to consider are not just throwing semi-structured data out there for use cases like annotating looking glasses, but could this also help with having a defined format that could help the discoverability of actions for automation systems to use without a human having to read through arbitrary string fields? I realize this could be daunting and potentially delay progress, but there are probably enough usual suspects (like do-not-send-to-xxx and prepend-x-times, etc) that they could be enumerated? Having done some yang stuff on the provisioning end of things, I would emphasize Tom Petch's note to consider typedef's already defined whenever reasonable. For example, RFC 6991 defines 'uri', 'email-address', 'as-number' (of course this will be 4-byte...). There may be more instances like this. >From an ecosystem perspective, we should be thinking about where these would get (linted and) published. Or do we just settle on yang-o-rama.sobornost.net now. ;-) Dale _______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
