wanting  a little light relief from the e-mail DoS attacks that surround an 
IETF meeting :-(
________________________________________
From: GROW <[email protected]> on behalf of Martin Pels <[email protected]>
Sent: 06 November 2023 10:07

Hi all,

Based on various discussions since my presentation in London, I have
submitted a draft for a YANG module to describe BGP communities:

   https://datatracker.ietf.org/doc/draft-pels-grow-yang-bgp-communities/

<tp>
I think that the Abstract is misleading.  I see this as a data model defining 
the structures to be used to specify a BGP community which happens to use YANG 
as a DDL but could use all sorts of languages.  It might (should?) have 
appeared as an Information Model first.  This becomes clearer from the 
Introduction but that Abstract needs to lead into that.  And the Introduction 
needs to come before the Terminology.

Technically, I find it flawed because it makes extensive use of strings with no 
constraints.  In several, cases, RFC have defined data types that could be used 
for such fields - IMHO strings are not a suitable alternative.

Where there is no data type, then string allows a length of  
18446744073709551615.  I have argued for a restriction thereon, as we had in 
SMI, but YANG Doctors always resist. The type t also allows the full range of 
pictogram languages which I find a hindrance; I note that recent I-D have 
imposed restrictions thereon, typically A-Z 0-9  and  a selection of 
punctuation varying according to the need.

Reference clauses I find helpful - in some places they are required in a YANG 
module.

Tom Petch.

There is also a github repository with some example JSON community
definitions following the model, as well as a working demo parser
written in Python:

   https://github.com/rodecker/draft-yang-bgp-communities

I'm looking forward to your feedback.

Kind regards,
Martin

_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow

_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow

Reply via email to