Re: [OPSAWG] WG LC: L2NM document: draft-ietf-opsawg-l2nm

2021-10-04 Thread Joe Clarke (jclarke)
WG LC has closed on this document. There have been a few comments by both opsawg members and others (after the extended sweep of RTG). The authors have not yet addressed the comments in a published draft but have proposed changes. Adrian Farrel has graciously agreed to act as shepherd of this

Re: [OPSAWG] WG LC: L2NM document: draft-ietf-opsawg-l2nm

2021-10-01 Thread mohamed.boucadair
Hi Julian, Thank you for the comments. Please see inline. Cheers, Med > -Message d'origine- > De : OPSAWG De la part de Julian Lucek > Envoyé : jeudi 30 septembre 2021 17:00 > À : opsawg@ietf.org > Objet : Re: [OPSAWG] WG LC: L2NM document: draft-ietf-opsawg-l2n

Re: [OPSAWG] WG LC: L2NM document: draft-ietf-opsawg-l2nm

2021-09-30 Thread Julian Lucek
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

Re: [OPSAWG] WG LC: L2NM document: draft-ietf-opsawg-l2nm

2021-09-30 Thread mohamed.boucadair
/IETF-OPSAWG-WG/lxnm/tree/master/I-D-L2NM, fwiw. Comments are still more than welcome. Cheers, Med > -Message d'origine- > De : OPSAWG De la part de Joe Clarke (jclarke) > Envoyé : jeudi 16 septembre 2021 17:59 > À : opsawg@ietf.org > Objet : [OPSAWG] WG LC: L2NM docum

Re: [OPSAWG] WG LC: L2NM document: draft-ietf-opsawg-l2nm

2021-09-28 Thread mohamed.boucadair
? Cheers, Med > -Message d'origine- > De : OPSAWG De la part de Joe Clarke (jclarke) > Envoyé : jeudi 16 septembre 2021 17:59 > À : opsawg@ietf.org > Objet : [OPSAWG] WG LC: L2NM document: draft-ietf-opsawg-l2nm > > Hello, WG. We would like to kick off a WG LC for

Re: [OPSAWG] WG LC: L2NM document: draft-ietf-opsawg-l2nm

2021-09-18 Thread tom petch
From: Joe Clarke (jclarke) Sent: 17 September 2021 18:17 On 9/17/21 04:34, tom petch wrote: > From: OPSAWG on behalf of Joe Clarke (jclarke) > > Sent: 16 September 2021 16:59 > > Hello, WG. We would like to kick off a WG LC for the > draft-ietf-opsawg-l2nm draft. As you review it, I would

Re: [OPSAWG] WG LC: L2NM document: draft-ietf-opsawg-l2nm

2021-09-17 Thread Joe Clarke (jclarke)
On 9/17/21 04:34, tom petch wrote: > From: OPSAWG on behalf of Joe Clarke (jclarke) > > Sent: 16 September 2021 16:59 > > Hello, WG. We would like to kick off a WG LC for the > draft-ietf-opsawg-l2nm draft. As you review it, I would encourage > looking back at draft-ietf-opsawg-vpn-common to

Re: [OPSAWG] WG LC: L2NM document: draft-ietf-opsawg-l2nm

2021-09-17 Thread tom petch
From: OPSAWG on behalf of Joe Clarke (jclarke) Sent: 16 September 2021 16:59 Hello, WG. We would like to kick off a WG LC for the draft-ietf-opsawg-l2nm draft. As you review it, I would encourage looking back at draft-ietf-opsawg-vpn-common to make sure everything lines up well. We'd like

[OPSAWG] WG LC: L2NM document: draft-ietf-opsawg-l2nm

2021-09-16 Thread Joe Clarke (jclarke)
Hello, WG. We would like to kick off a WG LC for the draft-ietf-opsawg-l2nm draft. As you review it, I would encourage looking back at draft-ietf-opsawg-vpn-common to make sure everything lines up well. We'd like to give two weeks for review, with LC closing on October 1. @Adrian Farrel you