I support the progression of these documents. They fill an important gap by
modelling attachment circuits in more detail than had been done in the past,
and therefore have high value.
thanks
Julian
Juniper Business Use Only
From: OPSAWG on behalf of "Joe Clarke (jclarke)"
Date: Friday, 1
I support the set of drafts – standardization of attachment circuits is very
valuable
thanks
Julian
Juniper Business Use Only
From: OPSAWG on behalf of "Joe Clarke (jclarke)"
Date: Monday, 2 October 2023 at 14:22
To: "opsawg@ietf.org"
Subject: [OPSAWG] CALL FOR ADOPTION: Attachment circu
nge is now implemented in -10.
Thank you for raising this.
Cheers,
Med
> -Message d'origine-
> De : Julian Lucek
> Envoyé : vendredi 29 octobre 2021 13:08
> À : Joe Clarke (jclarke) ; tom petch
> ; Joe Clarke (jclarke)
&
> “But I would urge you to change the terminology to "PE-to-CE-bandwidth"
/"CE-to-PE-bandwidth" to make it super-explicit, the current terminology has
been causing endless confusion to implementers (I realise it's inherited from
the service models, but changing the terminology in LXNM woul
I have a comment on the MVPN treatment in the draft. It would be valuable if
the model would allow the nature of the P-tunnel to be specified (e.g. PIM,
mLDP, RSVP) for inclusive and selective trees. Furthermore, it would be
valuable if the model would allow selective tree specifics to be listed
A couple of comments:
1/ "evpn-type" seems redundant, as the allowed types are already covered by
"vpn-type". But if there is a reason to have it, also need "mpls-evpn" as an
allowed evpn-type.
2/ There is a container called "status" (imported from vpn-common). "Status" is
a yang keyword, so i
tf.org] De la part de
> mohamed.boucad...@orange.com
> Envoyé : mardi 7 septembre 2021 14:35
> À : 'Julian Lucek' ; last-
> c...@ietf.org; opsawg@ietf.org
> Objet : Re: [Last-Call] [OPSAWG] Last Call: l3nm-10.txt> (A Layer 3 VPN Network YANG
I have the following comments:
1/ In the BFD section, the ability to invoke a profile should be moved up a
level, i.e. provide a choice between (i) specifying values for the parameters
listed and (ii) invoking a profile
| +--rw bfd {vpn-common:bfd}?
| +--rw desired-min-tx-interval?
