IETF Logo Mail Archive

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

mohamed.boucadair@orange.com Wed, 24 March 2021 14:08 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B4733A2D27 for <sfc@ietfa.amsl.com>; Wed, 24 Mar 2021 07:08:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4C0a3kDJbbkU for <sfc@ietfa.amsl.com>; Wed, 24 Mar 2021 07:08:11 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D3AD3A2D22 for <sfc@ietf.org>; Wed, 24 Mar 2021 07:08:11 -0700 (PDT)
Received: from opfedar04.francetelecom.fr (unknown [xx.xx.xx.6]) by opfedar25.francetelecom.fr (ESMTP service) with ESMTP id 4F597B2Hlcz8ttg; Wed, 24 Mar 2021 15:08:06 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1616594886; bh=YCiX3yXE/GYo80yV1u1BqWBCMMLebx0Gdmsm1RdkAeI=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=qMfSsIawuESMVZwwGtz14+JbqQYd6VlYZfAswrvgAFqWgSaecTKWqKWkG46xi6S6x 4DYQDl/s0ohVB+0MkxdboD2sSCEmwa9/c2DpXOg/aFBF0Enyabw+2hPuBma2+N4hVv eB3uNtNBbH2OixCiIp5VCSxR+96Dq30e+WfZ6ppDu2LwALKgGRZIrlZql6DN0upYd9 XGbwa/v/AoELBelGhRsaA1QGHbIVCMfj++4TAprov/S475ZdPeO1YWi4iSOyPCO21E oGL/mP6KXXWDe05wiCpLO9m78IKnTEGVoFikHNFzPQOGi1uQvs4E039xkrMf2S+JoM llYJ/MmFgP5yw==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.29]) by opfedar04.francetelecom.fr (ESMTP service) with ESMTP id 4F597B0qTJz1xp3; Wed, 24 Mar 2021 15:08:06 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Greg Mirsky <gregimirsky@gmail.com>
CC: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@mcafee.com>, Dan Wing <danwing@gmail.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] IETF WG state changed for draft-ietf-sfc-nsh-integrity
Thread-Index: AQHXILbc/h/UHKVYcUS2C83Sh0a+EKqTLIMw
Date: Wed, 24 Mar 2021 14:08:04 +0000
Message-ID: <27248_1616594886_605B47C6_27248_231_1_787AE7BB302AE849A7480A190F8B93303535B52E@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <161365771236.8570.11348497959366101106@ietfa.amsl.com> <2b68064f-4dd0-d7db-ae78-2971bc572e93@joelhalpern.com> <CA+RyBmV--OA8C0KAZdQdtONndO2_C3HMKXeVKOEYo=nXoYD5HQ@mail.gmail.com> <9155_1615788407_604EF977_9155_339_1_787AE7BB302AE849A7480A190F8B9330353534D6@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <1D9D1294-448F-4608-AA4E-919443A7EE22@gmail.com> <PH0PR16MB41182D95D37B0422F276160EEA639@PH0PR16MB4118.namprd16.prod.outlook.com> <CA+RyBmXXBSZNd8NFjURJxpO+71OfBPVKG_pCgEXe0Pn2yrca0g@mail.gmail.com> <30749_1616593062_605B40A6_30749_181_1_787AE7BB302AE849A7480A190F8B93303535B458@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CA+RyBmWN2dmCHgf6W7LQOe9Y2j4PS5eRNDK6ZGwOTT2f_O-Pyg@mail.gmail.com>
In-Reply-To: <CA+RyBmWN2dmCHgf6W7LQOe9Y2j4PS5eRNDK6ZGwOTT2f_O-Pyg@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93303535B52EOPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/AqpjMkbrmHIBXRdYMkP8npzsKuI>
Subject: Re: [sfc] IETF WG state changed for draft-ietf-sfc-nsh-integrity
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2021 14:08:17 -0000

Re-,

Looks good to me.

Thank you, Greg.

Cheers,
Med

De : Greg Mirsky [mailto:gregimirsky@gmail.com]
Envoyé : mercredi 24 mars 2021 15:06
À : BOUCADAIR Mohamed TGI/OLN <mohamed.boucadair@orange.com>
Cc : Konda, Tirumaleswar Reddy <TirumaleswarReddy_Konda@mcafee.com>om>; Dan Wing <danwing@gmail.com>om>; Joel M. Halpern <jmh@joelhalpern.com>om>; sfc@ietf.org
Objet : Re: [sfc] IETF WG state changed for draft-ietf-sfc-nsh-integrity

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 <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> 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:sfc-bounces@ietf.org<mailto:sfc-bounces@ietf.org>] De la part de Greg Mirsky
Envoyé : mercredi 24 mars 2021 14:26
À : Konda, Tirumaleswar Reddy <TirumaleswarReddy_Konda@mcafee.com<mailto:TirumaleswarReddy_Konda@mcafee.com>>
Cc : Dan Wing <danwing@gmail.com<mailto:danwing@gmail.com>>; Joel M. Halpern <jmh@joelhalpern.com<mailto:jmh@joelhalpern.com>>; sfc@ietf.org<mailto:sfc@ietf.org>
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 <TirumaleswarReddy_Konda@mcafee.com<mailto:TirumaleswarReddy_Konda@mcafee.com>> wrote:
I confirm that I am not aware of any IPR related to draft-ietf-sfc-nsh-integrity.

-TIru

> -----Original Message-----
> From: Dan Wing <danwing@gmail.com<mailto:danwing@gmail.com>>
> Sent: Tuesday, March 16, 2021 8:08 PM
> To: Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>>
> Cc: sfc@ietf.org<mailto:sfc@ietf.org>; Konda, Tirumaleswar Reddy
> <TirumaleswarReddy_Konda@McAfee.com<mailto:TirumaleswarReddy_Konda@McAfee.com>>; Joel M. Halpern
> <jmh@joelhalpern.com<mailto:jmh@joelhalpern.com>>
> 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, mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> 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:sfc-bounces@ietf.org<mailto:sfc-bounces@ietf.org>] De la part de Greg Mirsky
> > Envoyé : jeudi 18 février 2021 16:05 À : Joel M. Halpern
> > <jmh@joelhalpern.com<mailto:jmh@joelhalpern.com>> Cc : sfc@ietf.org<mailto:sfc@ietf.org> 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 <jmh@joelhalpern.com<mailto:jmh@joelhalpern.com>>
> 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: alias-bounces@ietf.org<mailto:alias-bounces@ietf.org>
> > Resent-To: tal.mizrahi.phd@gmail.com<mailto:tal.mizrahi.phd@gmail.com>, james.n.guichard@futurewei.com<mailto:james.n.guichard@futurewei.com>,
> > jmh@joelhalpern.com<mailto:jmh@joelhalpern.com>
> > Date: Thu, 18 Feb 2021 06:15:12 -0800
> > From: IETF Secretariat <ietf-secretariat-reply@ietf.org<mailto:ietf-secretariat-reply@ietf.org>>
> > To: draft-ietf-sfc-nsh-integrity@ietf.org<mailto:draft-ietf-sfc-nsh-integrity@ietf.org>, sfc-chairs@ietf.org<mailto:sfc-chairs@ietf.org>
> >
> >
> > 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
> > sfc@ietf.org<mailto: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.
> >

_________________________________________________________________________________________________________________________



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.

v2.8.7 | Report a Bug | By Email