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

[Greg Mirsky <[e-mail]>]

Hi Med,
thank you for the helpful detail on the start of the draft and the reminder
about reviews by the SecDir. I've updated my write-up. Please let me know
if it captures your suggestions.

Regards,
Greg

On Wed, Mar 24, 2021 at 6:37 AM <[e-mail]> wrote:

> Hi Greg,
>
>
>
> Thank you for the write-up.
>
>
>
> I wonder whether you can update it with the following details for more
> context:
>
>
>
> ·         The document was edited as a follow up to the discussion in
> IETF#104:
> https://datatracker.ietf.org/meeting/104/materials/slides-104-sfc-sfc-chair-slides-01
> (slide 7).
>
> ·         Two early secdir reviews were requested for the document. All
> raised issues were resolved.
>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* sfc [mailto:[e-mail]] *De la part de* Greg Mirsky
> *Envoyé :* mercredi 24 mars 2021 14:26
> *À :* Konda, Tirumaleswar Reddy <[e-mail]>
> *Cc :* Dan Wing <[e-mail]>om>; Joel M. Halpern <[e-mail]>om>;
> [e-mail]
> *Objet :* Re: [sfc] IETF WG state changed for draft-ietf-sfc-nsh-integrity
>
>
>
> Dear Authors,
>
> thank you for your timely responses to the IPR inquiry regarding
> draft-ietf-sfc-nsh-integrity.
>
> As the Shepherd, I've submitted my review. Please let me know if there are
> any questions.
>
>
>
> Regards,
>
> Greg
>
>
>
> On Tue, Mar 23, 2021 at 11:04 PM Konda, Tirumaleswar Reddy <
> [e-mail]> wrote:
>
> I confirm that I am not aware of any IPR related to
> draft-ietf-sfc-nsh-integrity.
>
> -TIru
>
> > -----Original Message-----
> > From: Dan Wing <[e-mail]>
> > Sent: Tuesday, March 16, 2021 8:08 PM
> > To: Greg Mirsky <[e-mail]>
> > Cc: [e-mail]; Konda, Tirumaleswar Reddy
> > <[e-mail]>om>; Joel M. Halpern
> > <[e-mail]>
> > Subject: Re: [sfc] IETF WG state changed for draft-ietf-sfc-nsh-integrity
> >
> > CAUTION: External email. Do not click links or open attachments unless
> you
> > recognize the sender and know the content is safe.
> >
> > I am not aware of IPR related to draft-ietf-sfc-nsh-integrity.
> >
> > -d
> >
> >
> > > On Mar 14, 2021, at 11:06 PM, [e-mail] wrote:
> > >
> > > Hi Greg,
> > >
> > > As an input to the write-up, I confirm that I have no IPR nor I’m
> aware of
> > any.
> > >
> > > I let Dan and Tiru answer to the IPR check.
> > >
> > > Cheers,
> > > Med
> > >
> > > De : sfc [mailto:[e-mail]] De la part de Greg Mirsky
> > > Envoyé : jeudi 18 février 2021 16:05 À : Joel M. Halpern
> > > <[e-mail]> Cc : [e-mail] Objet : Re: [sfc] Fwd: IETF WG
> > > state changed for draft-ietf-sfc-nsh-integrity
> > >
> > > Hi Joel and Jim,
> > > I'll be happy to shepherd this document.
> > >
> > > Regards,
> > > Greg
> > >
> > > On Thu, Feb 18, 2021 at 6:25 AM Joel M. Halpern <[e-mail]>
> > wrote:
> > > The WG Last Call for draft-ietf-sfc-nsh-integrity has completed
> > > successfully as noted below.
> > >
> > > We now need a document shepherd.
> > > It would be good for someone other than the chairs to do this.
> > > If you are willing, please let us know.  We will pick someone with a
> > > few days.
> > >
> > > Thank you,
> > > Joel
> > >
> > >
> > > -------- Forwarded Message --------
> > > Subject: IETF WG state changed for draft-ietf-sfc-nsh-integrity
> > > Resent-Date: Thu, 18 Feb 2021 06:15:12 -0800 (PST)
> > > Resent-From: [e-mail]
> > > Resent-To: [e-mail], [e-mail],
> > > [e-mail]
> > > Date: Thu, 18 Feb 2021 06:15:12 -0800
> > > From: IETF Secretariat <[e-mail]>
> > > To: [e-mail], [e-mail]
> > >
> > >
> > > The IETF WG state of draft-ietf-sfc-nsh-integrity has been changed to
> > > "WG
> > > Consensus: Waiting for Write-Up" from "In WG Last Call" by Joel
> Halpern:
> > >
> > > https://datatracker.ietf.org/doc/draft-ietf-sfc-nsh-integrity/
> > >
> > > Comment:
> > > Thank you.  This document has completed WG Last Call successfully.
> > > Thanks to the authors for promptly addressing comments raised during
> > > that last call. We will now pick a document shepherd, and in parallel
> > > ask for an updated security review.
> > >
> > > _______________________________________________
> > > 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.
> > >
>
> _________________________________________________________________________________________________________________________
>
> 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.
>
>