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

[[e-mail]]

Hi Med,
thanks for quick clarification!
Best Regards
Dirk 

-----Original Message-----
From: [e-mail] <[e-mail]> 
Sent: Donnerstag, 4. Februar 2021 14:19
To: von Hugo, Dirk <[e-mail]>; [e-mail]; [e-mail]
Subject: RE: [sfc] Fwd: IETF WG state changed for draft-ietf-sfc-nsh-integrity

Dirk, 

A version that integrates almost all your inputs is now available at: https://tinyurl.com/nsh-integrity-latest. Please check.   

For this one: 

==
Base Header: Provides information about the service header/ Base and Service Headers 
> Is it rather Service Path Header(s) what is meant here - or what is difference between Service Header and NSH??
==

we are actually echoing Section 2.1 of 8300. That text is correct as it is basically referring to the role of "MD type" and "next protocol". The service header covers both the "service path header" and context headers.

Cheers,
Med

> -----Message d'origine-----
> De : sfc [mailto:[e-mail]] De la part de 
> [e-mail] Envoyé : jeudi 4 février 2021 07:27 À : 
> [e-mail]; [e-mail]; [e-mail] Objet : 
> Re: [sfc] Fwd: IETF WG state changed for draft-ietf-sfc-nsh- integrity
> 
> Hi Dirk,
> 
> Thank you.
> 
> FWIW, your comments are recorded at
> https://github.com/boucadair/draft-ietf-sfc-nsh-integrity/issues/4.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : sfc [mailto:[e-mail]] De la part de Dirk.von- 
> > [e-mail] Envoyé : mercredi 3 février 2021 21:53 À :
> > [e-mail]; [e-mail] Objet : Re: [sfc] Fwd: IETF WG
> state
> > changed for draft-ietf-sfc-nsh- integrity
> >
> > Dear all,
> > I agree that the doc should move forward.
> > I have sent a list of nits detected and questions for minor 
> > clarifications to the authors in parallel.
> > Thanks for the good work!
> >  Best Regards
> > Dirk
> >
> > -----Original Message-----
> > From: sfc <[e-mail]> On Behalf Of Joel M. Halpern
> > Sent: Donnerstag, 28. Januar 2021 16:33
> > To: [e-mail]
> > Subject: [sfc] Fwd: IETF WG state changed for draft-ietf-sfc-nsh- 
> > integrity
> >
> > 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
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/sfc
> >
> > _______________________________________________
> > sfc mailing list
> > [e-mail]
> > 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.
> 
> _______________________________________________
> sfc mailing list
> [e-mail]
> 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.