[sfc] WG LC for draft-ietf-sfc-ioam-nsh

Joel Halpern <jmh@joelhalpern.com> Thu, 02 June 2022 18:52 UTC

Return-Path: <jmh@joelhalpern.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 2FE6FC14F745 for <sfc@ietfa.amsl.com>; Thu, 2 Jun 2022 11:52:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SsLOd8Uu_QYd for <sfc@ietfa.amsl.com>; Thu, 2 Jun 2022 11:52:13 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58751C14F738 for <sfc@ietf.org>; Thu, 2 Jun 2022 11:52:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4LDZrF05b6z6G9Mg for <sfc@ietf.org>; Thu, 2 Jun 2022 11:52:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1654195933; bh=1YMdK6v6STY5d2nN3V+7qz62PPn4k9i7WDXj982Xvyc=; h=Date:To:From:Subject:From; b=iZzyqIKwe+yGd5pSh6OkuCQkr7CZ+E7goRdJcwb3FZybZ+0RcVwrOyBNIaoDCy+Ix GbzS3iXwdKBB7/sUi56sbH5wbRPUNIRnZr3GcgGJU5w5cvnTiJr+0umKoFS1rBef/i A9HOvyBG1oRMjjR7fwXMORUKbguMJW20+Yi1gM6k=
X-Quarantine-ID: <tgfgzjW2rQJx>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.23.181] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4LDZrD3ts6z6G9K8 for <sfc@ietf.org>; Thu, 2 Jun 2022 11:52:12 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------wQUYUOswD0n7nz3sULK5gyRW"
Message-ID: <72a06b36-7765-a512-edc4-9b48185950f9@joelhalpern.com>
Date: Thu, 02 Jun 2022 14:52:10 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1
Content-Language: en-US
To: "sfc@ietf.org" <sfc@ietf.org>
From: Joel Halpern <jmh@joelhalpern.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/NOU1hEJyxehclnBzJvOrLZZxryg>
Subject: [sfc] WG LC for draft-ietf-sfc-ioam-nsh
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 02 Jun 2022 18:52:17 -0000

Technically, the draft is still in last call from quite some time ago.

For clarity, and as there have been clarifications in relate 
terminology, the chairs have decided to consider that we are restarting 
the last call today.

This Working Group Last call will run for 2 weeks (and a day) until CoB 
on June 17, 2022.

Please respond positively or negatively to this call.  Note that if we 
do not get enough responses we will likely be unable to advance the 
document before the WG closes.

When responding, please provide clear motivation either for or against 
publication as an RFC.  Substantive comments are MUCH more helpful than 
"yes" or "no".


Thank you,

Joel and Jim