Understood, thanks.
(I yield to the combined power of "out of scope" and "future extension".)
On Wed, Sep 22, 2021 at 11:14 PM wrote:
> Hi Erik,
>
> Thank you for the comments.
>
> Please see inline.
>
> Cheers,
> Med
>
> > -Message d'origine-
> > De : Erik Kline via Datatracker
Thanks Med for addressing the discuss points. I have now balloted NO OBJECTION.
BR
Zahed
On 2021-09-23, 15:10, "mohamed.boucad...@orange.com"
wrote:
Hi Zahed,
FWIW, a new version that resolves your DISCUSS is available online:
Hi Zahed,
FWIW, a new version that resolves your DISCUSS is available online:
https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-vpn-common-11.
Cheers,
Med
> -Message d'origine-
> De : OPSAWG [mailto:opsawg-boun...@ietf.org] De la part de
> mohamed.boucad...@orange.com
> Envoyé :
> -Original Message-
> From: Qin Wu
> Sent: Thursday, September 23, 2021 1:25 PM
> To: Scharf, Michael ;
> mohamed.boucad...@orange.com; Martin Duke
> ; The IESG
> Cc: draft-ietf-opsawg-l3sm-l...@ietf.org; opsawg@ietf.org; opsawg-
> cha...@ietf.org
> Subject: RE: Martin Duke's Discuss on
Hi Rob, all,
This version integrates the comments received from the IESG review.
Cheers,
Med
> -Message d'origine-
> De : OPSAWG [mailto:opsawg-boun...@ietf.org] De la part de internet-
> dra...@ietf.org
> Envoyé : jeudi 23 septembre 2021 14:15
> À : i-d-annou...@ietf.org
> Cc :
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Operations and Management Area Working Group
WG of the IETF.
Title : A Layer 2/3 VPN Common YANG Model
Authors : Samier Barguil
I assume many of us don't understand the difference between device model and
network model, how network model is mapped down to device level models.
See figure 5 of RFC8969, In order to deliver L3VPN service, the L3NM defined
configuration or abstraction should be further decomposed into a set
Hi Qin,
I believe that in the specific case of "send-id" and "recv-id", the actual
issue is that L3NM references to the RFC 8177 model that could theoretically
include the required information. But RFC 8177 may have a gap there.
And since these values must be set consistently with the router a
Hi, Michael, Med and all:
I tend to agree with Med we should have a clear distinction between device
level configuration and network level abstraction.
Device level configuration will provide complete set of TCP AO properties
configuration to make TCP AO functionality work while network level
Benjamin Kaduk has entered the following ballot position for
draft-ietf-opsawg-l3sm-l3nm-11: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
Hi Erik,
Thank you for the comments.
Please see inline.
Cheers,
Med
> -Message d'origine-
> De : Erik Kline via Datatracker [mailto:nore...@ietf.org]
> Envoyé : mercredi 22 septembre 2021 22:36
> À : The IESG
> Cc : draft-ietf-opsawg-l3sm-l...@ietf.org; opsawg-cha...@ietf.org;
>
11 matches
Mail list logo
