ular exercise so it
> is important to get it right first time..
>
> Tom Petch
>
>
>
> My 2 cents
>
> Italo
>
> > -Original Message-----
> > From: Joe Clarke (jclarke) [mailto:jcla...@cisco.com]
> > Sent: giovedì 13 agosto 2020 14:49
> > To: opsa
that end, the chairs would like a call for adoption of
> draft-bgbw-opsawg-vpn-common. Additionally, comments on the approach and the
> choice of common attributes are welcome, especially from those that were
> unable to attend the IETF 108 virtual meeting.
>
> This serves as a two week
,
Adrian
-Original Message-
From: OPSAWG On Behalf Of Joe Clarke (jclarke)
Sent: 13 August 2020 13:49
To: opsawg
Subject: [OPSAWG] CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common
Hello, WG members. On the IETF 108 virtual meeting, Oscar presented the status
of the L3NM, L2NM, and the VPN
e interesting rules, so this is not
> > conclusive, but seems to favor that this common module work should exist as
> > its own, standalone document that both L2NM and L3NM will consume. In this
> > manner, one would not need to import either L2NM or L3NM to make use
> > of/ex
onclusive,
> but seems to favor that this common module work should exist as its own,
> standalone document that both L2NM and L3NM will consume. In this manner,
> one would not need to import either L2NM or L3NM to make use of/extend these
> common attributes.
>
> To th
need to import either L2NM or L3NM to make use of/extend these
> common attributes.
>
> To that end, the chairs would like a call for adoption of
> draft-bgbw-opsawg-vpn-common. Additionally, comments on the approach and the
> choice of common attributes are welcome, especiall
Hi,
I support adoption as expressed in the list already.
Roque
From: OPSAWG on behalf of SAMIER BARGUIL GIRALDO
Date: Friday, 14 August 2020 at 09:42
To: "Joe Clarke (jclarke)" , opsawg
Subject: Re: [OPSAWG] CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common
Hello WG,
> Sent: giovedì 13 agosto 2020 14:49
> To: opsawg
> Subject: [OPSAWG] CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common
>
> Hello, WG members. On the IETF 108 virtual meeting, Oscar presented the
> status of the L3NM, L2NM, and the VPN common work. While this VPN
>
de Joe Clarke (jclarke)
Enviado: jueves, 13 de agosto de 2020 7:49
Para: opsawg
Asunto: [OPSAWG] CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common
Hello, WG members. On the IETF 108 virtual meeting, Oscar presented the status
of the L3NM, L2NM, and the VPN common work. While this VPN common YANG
; Joe
Clarke (jclarke) ; opsawg
Asunto: Re: CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common
From: OPSAWG on behalf of SAMIER BARGUIL GIRALDO
Sent: 14 August 2020 08:41
Hello WG,
I Support the adoption of this draft using the "Forte" approach. It is
necessary to decouple the module
9
Para: opsawg
Asunto: [OPSAWG] CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common
Hello, WG members. On the IETF 108 virtual meeting, Oscar presented the status
of the L3NM, L2NM, and the VPN common work. While this VPN common YANG module
started as an individual document (per the chairs’ requ
n,
standalone document that both L2NM and L3NM will consume. In this manner, one
would not need to import either L2NM or L3NM to make use of/extend these common
attributes.
To that end, the chairs would like a call for adoption of
draft-bgbw-opsawg-vpn-common. Additionally, comments o
L2NM and L3NM will consume. In this manner, one
would not need to import either L2NM or L3NM to make use of/extend these common
attributes.
To that end, the chairs would like a call for adoption of
draft-bgbw-opsawg-vpn-common. Additionally, comments on the approach and the
choice of common
13 matches
Mail list logo
