Hi Ben,
Thank you for the follow-up.
Please see inline.
Cheers,
Med
> -Message d'origine-
> De : Benjamin Kaduk
> Envoyé : lundi 27 septembre 2021 23:39
> À : BOUCADAIR Mohamed INNOV/NET
> Cc : The IESG ; draft-ietf-opsawg-vpn-com...@ietf.org;
> opsawg-cha...@ietf.org; opsawg@ietf.
Hi Med,
Continuing inline...
On Fri, Sep 24, 2021 at 02:35:25PM +, mohamed.boucad...@orange.com wrote:
> Hi Ben,
>
> Focusing on the COMMENT part. All good points. Many thanks for the time and
> the effort put into looking this.
>
> Please see inline.
>
> Cheers,
> Med
>
> > -Mes
Hi Med,
Sorry for not getting back to you last week -- I had to shift gears
immediately after the telechat to another project.
Also inline...
On Fri, Sep 24, 2021 at 08:52:30AM +, mohamed.boucad...@orange.com wrote:
> Hi Ben,
>
> (focusing on the DISCUSS part)
>
> Many thanks for the revi
Hi Med,
On Wed, Sep 22, 2021 at 09:40:17AM +, mohamed.boucad...@orange.com wrote:
> Hi Ben,
>
> Thank you for the review. The changes to address your review can be tracked
> at:
> https://github.com/IETF-OPSAWG-WG/lxnm/commit/108707e8b2aea6590b0a9695756c7546887c9614
>
Thanks. Also inli
Martin Duke has entered the following ballot position for
draft-ietf-opsawg-l3sm-l3nm-13: No Objection
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 h
> > > We can add a note about it you think this helps. Thank you.
> >
> > If the document assumes additions to RFC 8177, this must be noted, IMHO.
>
> [[Med]] Added this NEW text:
>
> This version of the L3NM assumes that TCP-AO specific parameters
> are preconfigured as part of the k
Many thanks Shwetha for getting back on the draft.
To answer your points:
1. Yes! Software application, hosted in cloud, also responses to a form of
Asset as part of the draft.
2. It will be good to hear more on your proposal, lifecycle in SaaS is part
of our scope.
3. Yes, we are ope
Re-,
Great. Thanks.
The change is now implemented in the draft as you can see in this diff:
https://www.ietf.org/rfcdiff?url1=draft-ietf-opsawg-l3sm-l3nm-12&url2=draft-ietf-opsawg-l3sm-l3nm-13
Cheers,
Med
> -Message d'origine-
> De : Julian Lucek [mailto:jlu...@juniper.net]
> Envoyé :
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 3 VPN Network YANG Model
Authors : Samier Barguil
Hi Mohamed
Yes, that would be perfect
Cheers
Julian
On 27/09/2021, 14:16, "mohamed.boucad...@orange.com"
wrote:
[External Email. Be cautious of content]
Hi Julian,
Following-up on the LAG point.
The current model supports managing the LAG outside of the L3NM (as other
i
Hi Julian,
Following-up on the LAG point.
The current model supports managing the LAG outside of the L3NM (as other
interface management). In this approach, a pointer to a LAG interface can be
provided under interface-id of vpn-network-access.
However, I understand that you would like one
I get you point, Med.
Thanks for addressing my comments, I will clear my discuss.
BR
Zahed
On 2021-09-27, 13:23, "mohamed.boucad...@orange.com"
wrote:
Re-,
Great, thanks.
For this one:
> This might be fine, however, I was talking about the case where the
> configura
Re-,
Great, thanks.
For this one:
> This might be fine, however, I was talking about the case where the
> configuration is correct but due to ambiguity the classification is
> wrong. The end result might be same i.e. SLA violation, but reason could
> be different.
I agree that the reason is di
Hi Roman,
A new version that echo the replies already provided in this this thread is
available:
URL:
https://www.ietf.org/archive/id/draft-ietf-opsawg-l3sm-l3nm-12.txt
Status: https://datatracker.ietf.org/doc/draft-ietf-opsawg-l3sm-l3nm/
Htmlized:
https://datatrack
Hi Med,
This looks good to me.
I think I forgot to reply to your response to one of my earlier comments.
Copying that here for convenience -
> > Additional comment(s)-
> >
> > * I think if would be good if this specification also discusses the
> > implication of wrong classifi
Hi Martin ,
The proposed changes to echo the clarification provided below and the
discussion with Michael (thanks) are now implemented in a new revision:
URL:
https://www.ietf.org/archive/id/draft-ietf-opsawg-l3sm-l3nm-12.txt
Status: https://datatracker.ietf.org/doc/draft-ie
Hi Zahed,
The proposed changes to address your DISCUSS are now implemented in a new
revision:
URL:
https://www.ietf.org/archive/id/draft-ietf-opsawg-l3sm-l3nm-12.txt
Status: https://datatracker.ietf.org/doc/draft-ietf-opsawg-l3sm-l3nm/
Htmlized:
https://datatracker.
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 3 VPN Network YANG Model
Authors : Samier Barguil
18 matches
Mail list logo
