[L3sm] Comments on draft-ietf-l3sm-l3vpn-service-model

[Kireeti Kompella <[e-mail]>]

Hi,

Very happy to see this WG, and to see the l3vpn _service_ YANG model.  Wish I’d been paying attention earlier :)

Some comments:

1) At a high level, I would like to see services as compositions (mash-ups) of service elements.  This is a generalization of the comments that Aijun made.  Here’s why.  As we (either the IETF or other bodies, or SPs on their own) define other services, it would be very convenient to be able to reuse these service elements.  Example: suppose an L2SM module is needed.

Elements to consider:
	availability
	QoS
	access-control-list
	OAM (liveness)
	customer-specific-info

I don’t know how one defines a mash-up of modules in YANG, maybe as simple as “import”.

(Note: this has nothing to do with service chaining!)

2) I think it would be convenient to have certain stanzas directly under vpn-svc, and again under vpn-svc/sites — essentially, a default for the entire service, and overrides for each site.

3) not sure why “bfd” is under “routing protocols”.  You may be better off having a stanza called OAM/Hello/liveness, where one can choose bfd among other mechanisms.

4) might be hard, but define defaults for as many YANG leaves as possible.

5) From comments on the mailing list, it seems OTT VPNs (customer-provisioned) are out of scope; however, doing such a model will help clarify common elements, and might help organize the L3VPN SM better.

6) Philosophical comment: should scrutinize service models to ensure we’re making them as abstract as possible.  E.g., I’m very happy that RDs and RTs are not in the SM.  Question: what else can be trimmed?

Finally, should YANG models (in general) have guidance as to where to place augments?  The theory is, you start with an SM (or data model in general) that everyone agrees on — lowest common denominator.  Then, as people augment a DM, if a certain augmentation appears in several such models, that might be promoted to being a part of the standard DM.  Or maybe I’m a dreamer :)

Kireeti.