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

Dhruv Dhody <dhruv.ietf@gmail.com> Tue, 09 February 2021 09:50 UTC

Return-Path: <dhruv.ietf@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 652773A1399 for <sfc@ietfa.amsl.com>; Tue, 9 Feb 2021 01:50:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 FI-hOhtwZo65 for <sfc@ietfa.amsl.com>; Tue, 9 Feb 2021 01:50:15 -0800 (PST)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 EA41B3A1398 for <sfc@ietf.org>; Tue, 9 Feb 2021 01:50:14 -0800 (PST)
Received: by mail-io1-xd32.google.com with SMTP id p132so861077iod.11 for <sfc@ietf.org>; Tue, 09 Feb 2021 01:50:14 -0800 (PST)
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=h0bnKQeNnYV6UIGC2oOZrSbn3QdzKzsH6BhJzND0EOA=; b=ubY+yRMxFyZmJpYdmsGpCX97K2LxsIojlrhy0v9TaW9WNeHxZeKlVet6W9LKB/tsXY VHV2HX4Vq0iIFi9AMUaudgTE/aRpVoS7du6yOOe4UJjGmf2VH+GTp5MqLQAdth2V2x8R vIC4Qt4GcH80xY53i18hzwUriphxWZptlmsCR5KqaTjAeuOL7UbSNGMUl0I0SiVeHDuk SAtTZM7RPFbL1nwnjrDnL0wBz0Zy6vo1SwzN7vAAwTf4/KmbnIdMyUfnN5N3f3UApG8X XeS5oBmlO8shf3lD/YHDCgodDIWRy2AvnXMM3Ao1e1ap7WgU5z5aVp691KKYF+g0QqUW ahMA==
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=h0bnKQeNnYV6UIGC2oOZrSbn3QdzKzsH6BhJzND0EOA=; b=bwNfq3eAlAdeHDKUc0aLzwPt5Qd8dzA7VZxGyMgBZs80B5TAKu5342jP5gSYP99VnB YsYUITzXW7gAAKKnYhvAlr6HeTOR5/Bms2G/qsumkSOoZaDATuSBHjofekL52kFZmNnH x1lrD7Qb7spLbWhFqRzXr1gkf9ZskZKl0kPJMXUQqKP9wOd/Mjddl3k19X1D0RQCMvMG o9Agz7AF3Cr29U6zWtTTbyaZR99h42kC91Qc+o0FsmP93lczdrcGOUGmsXbgvjYZlfAv ixusQJiqmkIaojv+cWvblJGJl3EKESB6kR2QgZOiV3bBK1hg5pY7DebG7t5+DOpnXpiU 68gA==
X-Gm-Message-State: AOAM530CfqgsTvJOQrzCteakVJosvK/4PnjQaeL0s6rzCj+fDxWWfBGe NrI+fKoCpdwteh8ZA0fR5qmvR+adgY6dMQMZYmiUOFWjyWAfwA==
X-Google-Smtp-Source: ABdhPJwZ81fig5OeESVo9VSRO92bkkDmC4ySJdQvIUOUEAJkqv3c06GLUlZe2d3lG5X4q+BDk8W31ntJAOpfHQowifM=
X-Received: by 2002:a05:6638:14d5:: with SMTP id l21mr21548763jak.54.1612864213802; Tue, 09 Feb 2021 01:50:13 -0800 (PST)
MIME-Version: 1.0
References: <161184769798.6893.13499187160157088449@ietfa.amsl.com> <48b9f1db-38cb-7703-3c1e-7d2e75f93d19@joelhalpern.com>
In-Reply-To: <48b9f1db-38cb-7703-3c1e-7d2e75f93d19@joelhalpern.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Tue, 09 Feb 2021 15:19:37 +0530
Message-ID: <CAB75xn7TyVumBUkJN322W4doaukcdgObsvOAdFeEP4_x04-PMQ@mail.gmail.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/W6BT91V6gcS8X9lk9HRBuAuyNGU>
Subject: Re: [sfc] Fwd: 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: Tue, 09 Feb 2021 09:50:16 -0000

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