Re: [OPSAWG] Last Call: <draft-ietf-opsawg-l2nm-15.txt> (A YANG Network Data Model for Layer 2 VPNs) to Proposed Standard BGP L2

[tom petch <[e-mail]>]

I find some lack of clarity with regard of the BGP Layer 2 Encapsulation 
Types module.

I see no description of the module in the body of the document, only the 
module itself and the IANA Considerations (S.10.2).

S.10.2 says ' add this note to both modules'.  I only see one module.

It gives the name of the registry but not what Group it is part of i.e. 
'Border Gateway Protocol(BGP) Parameters'.  Admittedly this is one of 
the better chosen Group names but it is always good practice IMO to 
specify Group name and Registry name when referencing IANA entries.

It also says that the name of the 'identity' is the lower case of the 
encapsulation name provided in the description.  This is not what 
happens here, in the module, in many if not most cases.  The identity 
name is based on the Description in the IANA Registry but heavily 
abbreviated.  Who will decide on an acceptable abbreviation, meaningful, 
unique, for future additions?

'Unassigned or reserved values..' worth spelling out that those are the 
values in the BGP Layer 2 Encapsulation Types registry.

And what about the Experimental Use values? They are not in the IANA 
module but why not?

'unique revision date' well yes but the current date would seem more useful.

Section 8.1 describes the module as 'YANG data types defined by IANA' 
which seems odd.  The underlying data types are defined by the IDR WG; 
perhaps 'maintained by'.

I note that Section 8.2 which contains the other IANA module, 
IANA-pseudowire-types, has a section title of 'IANA Encapsulation Types' 
which seems odd in the absence of any explanation.


Tom Petch

On 29/04/2022 15:40, The IESG wrote:
>
> The IESG has received a request from the Operations and Management Area
> Working Group WG (opsawg) to consider the following document: - 'A YANG
> Network Data Model for Layer 2 VPNs'
>    <draft-ietf-opsawg-l2nm-15.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> [e-mail] mailing lists by 2022-05-13. Exceptionally, comments may
> be sent to [e-mail] instead. In either case, please retain the beginning
> of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document defines an L2VPN Network YANG Model (L2NM) which can be
>     used to manage the provisioning of Layer 2 Virtual Private Network
>     services within a network (e.g., service provider network).  The L2NM
>     complements the Layer 2 Service Model (L2SM) by providing a network-
>     centric view of the service that is internal to a service provider.
>     The L2NM is particularly meant to be used by a network controller to
>     derive the configuration information that will be sent to relevant
>     network devices.
>
>     Also, this document defines a YANG module to manage Ethernet segments
>     and the initial versions of two IANA-maintained modules that defines
>     a set of identities of BGP Layer 2 encapsulation types and pseudowire
>     types.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-opsawg-l2nm/
>
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>
>
> _______________________________________________
> IETF-Announce mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/ietf-announce
> .
>