Re: [sfc] Fwd: IETF WG state changed for draft-ietf-sfc-nsh-integrity

Hi Dhruv, all, 

Thank you for the feedback. 

We added a note to remind that NSH-aware control plane solution is out of the scope. 

As some may be confused that the control plane is out of the scope but it is still mentioned in the text, we went with an update that "softens" (rather than groups) the use of "control plane".

The edits can be seen at: https://tinyurl.com/nsh-integrity-latest. 

Hope this is better. 

Cheers,
Med

> -----Message d'origine-----
> De : sfc [mailto:sfc-bounces@ietf.org] De la part de Dhruv Dhody
> Envoyé : mardi 9 février 2021 10:50
> À : Joel M. Halpern <jmh@joelhalpern.com>
> Cc : sfc@ietf.org
> Objet : Re: [sfc] Fwd: IETF WG state changed for draft-ietf-sfc-nsh-
> integrity
> 
> Hi Joel,
> 
> I have read the I-D and I feel that the document is ready for
> publication. Authors have done a good job in clearly describing the
> need and mechanism for integrity protection in NSH.
> 
> I see some control plane aspects scattered across the I-D (while
> mostly out of scope), wondering if it is a good idea to consolidate
> them in a section.
> 
> Thanks!
> Dhruv
> 
> On Thu, Jan 28, 2021 at 9:03 PM Joel M. Halpern <jmh@joelhalpern.com>
> wrote:
> >
> > As you can see below, the SFC Chairs have started the WG last Call
> for
> > the nsh-integrity draft.  Please respond.
> > Thank you,
> > Joel
> >
> >
> > -------- Forwarded Message -------
> >
> >
> > The IETF WG state of draft-ietf-sfc-nsh-integrity has been changed
> to
> > "In WG Last Call" from "WG Document" by Joel Halpern:
> >
> > https://datatracker.ietf.org/doc/draft-ietf-sfc-nsh-integrity/
> >
> > Comment:
> > This starts the SFC Working Group last call for the NSH integrity
> > protection document.  This will run through the end of the day
> February 11, 2021.
> > (Don't worry about time zone.  If it is still Feb 11 2021 somewhere
> in
> > the world, you can send in comments.)  Please respond.  Silence is
> not
> > consent, and when (if, but we hope when) we send this to the AD, we
> > need to be able to describe meaningful WG support for the
> publication.
> > And if possible, more than just +1.
> >
> > Thank you,
> > Joel (and Jim)
> >
> > _______________________________________________
> > sfc mailing list
> > sfc@ietf.org
> > https://www.ietf.org/mailman/listinfo/sfc
> 
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.