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

Greg Mirsky <gregimirsky@gmail.com> Wed, 24 March 2021 13:26 UTC

Return-Path: <gregimirsky@gmail.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 CAF3F3A2C7C for <sfc@ietfa.amsl.com>; Wed, 24 Mar 2021 06:26:10 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=gmail.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 511F-P6EfaSE for <sfc@ietfa.amsl.com>; Wed, 24 Mar 2021 06:26:06 -0700 (PDT)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 F0C803A2C7A for <sfc@ietf.org>; Wed, 24 Mar 2021 06:26:05 -0700 (PDT)
Received: by mail-lf1-x129.google.com with SMTP id b4so8018231lfi.6 for <sfc@ietf.org>; Wed, 24 Mar 2021 06:26:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RjYHwiQYnnrnlcvFcAUrqgbM6oidxlkKUYC4RoNF8Tk=; b=XtKgpn3eN2BKqwckJb5llIkUJLoWxSrz6DUYyoHBmWXx6bGzCu5c5xaYAcqsZC67vd VcfeU2uy2wg65qt4cQ7g0CB4JX9EQlrkz+drWW34YNM/41DhMiTlX0EM0UfnHiGa0b0N lZfMzXrhuMpHji9hXTc9iomtirjUiqEjFqLShdLOP15WI4aMEC1UBAesORayGJ8kUvIs dqKj9cw15WRwFBrH4ik4XS8nMwGur9jsZ2ZmniYUwlid/D1k5U6PaAhJMxc+ZYlqgwtQ r25sHRaPWIKm4P2EwKOU/tVupFchGOR/cvfMEMp0sysyz8YQGqjC/EqpZ+A9mR96p2V8 F/Fw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RjYHwiQYnnrnlcvFcAUrqgbM6oidxlkKUYC4RoNF8Tk=; b=ToM4X/nkbQoBfx03jxIN+H1XLB2A6YfdWbDoZ0FDGoZCrC0hjqvajkRkG7YRLUI5kt YG8Tp9hUBeQF/woQsM+MBC9H3FDVBz2hWWOiLWx4sNsC457aixpEUlNsO/fXp+dqYwJH Bi0GrP9isbZT9AYIFtb0TQDWj4dU/cc0NvSBHXQA0fma67ArdGkO6zODJ0YEVu7J4SUu /LdNyrSyh0P+OytNPzxBaZlFWvAVp+7Q4qq9fuCGyoCQjyw8pjMYq59s2+tFquuRMBpv rZ527W0GnkGi/LYmz6qpJkKz3yjc5duXSnfIFl1ocPER/RwgyN4LWtQXXJFy66gtRyDT L4Pg==
X-Gm-Message-State: AOAM531m5rpABa+na1vunnM8aVbw3xKGa08WcCdqARahmv/IWj+DhNCV 0LXxoo+/9WOez+wCXPyFwDGYV3F4z5FyRCY/pJw=
X-Google-Smtp-Source: ABdhPJyEn8K1RaD4Aqe2Zo+DlktYcCkjHIaqD7EbzaB7zSv37bMW7nn54SKDmmOrm1wB2ME9dwCKAdO8Z6jslgRUDao=
X-Received: by 2002:ac2:5f56:: with SMTP id 22mr1997396lfz.35.1616592358826; Wed, 24 Mar 2021 06:25:58 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <PH0PR16MB41182D95D37B0422F276160EEA639@PH0PR16MB4118.namprd16.prod.outlook.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 24 Mar 2021 06:25:47 -0700
Message-ID: <CA+RyBmXXBSZNd8NFjURJxpO+71OfBPVKG_pCgEXe0Pn2yrca0g@mail.gmail.com>
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@mcafee.com>
Cc: Dan Wing <danwing@gmail.com>, "sfc@ietf.org" <sfc@ietf.org>, "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary="0000000000004b676805be483dbc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/G_ziKYcQ-nOSDA2OYKirIF03k6Y>
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 13:26:11 -0000

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