IETF Logo Mail Archive

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

mohamed.boucadair@orange.com Fri, 03 June 2022 08:31 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 1209DC157B34 for <sfc@ietfa.amsl.com>; Fri, 3 Jun 2022 01:31:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id seTof6NELwmn for <sfc@ietfa.amsl.com>; Fri, 3 Jun 2022 01:31:52 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E445C14CF17 for <sfc@ietf.org>; Fri, 3 Jun 2022 01:31:52 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) (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 opfedar26.francetelecom.fr (ESMTP service) with ESMTPS id 4LDx1x4M61zFq2m; Fri, 3 Jun 2022 10:31:49 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1654245109; bh=MqpXy7tMziQdHHxMhnNgiM6uBcMGmFSJRymdQamlXCY=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=ihbDZ2pf5K7iKHwbB+d69Pj8+FY34L3yo+VvRCSanxsICSyg9H+oGPRyGWTkEQ7Ra 7KwOEXGTtjCCF8IBhx5vGpBPgu2BF4l4jjazTyPF3AeFUOKntnUag34TtaslxzhLZz 4iIcCcz9V8yWb4rrYBeRYVTGNl94eSo9E4+V8DqiCJvLwaCUljl9doQjsYIo0PIgwD PROzl1f2e4xO7ZC2dZVmIm9208Zq0pF5hGN4CGZRZ55e8y7O4kgoCBBlVj8ytC3H25 0qeZHzBc2IRJb5BJu7S1Ij+jkYTOLIEJ/zhST+4kYabI1NS61w2qf+DuGrYyWKkWDw knQR8CmSDMXKg==
From: mohamed.boucadair@orange.com
To: Joel Halpern <jmh@joelhalpern.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] WG LC for draft-ietf-sfc-ioam-nsh
Thread-Index: AQHYdrHm3vn0thUb3EGx4p/Z2y1Kla09WP2Q
Content-Class:
Date: Fri, 03 Jun 2022 08:31:49 +0000
Message-ID: <25115_1654245109_6299C6F5_25115_331_1_a8adf3a66f784c8886c3463fe42ffa9f@orange.com>
References: <72a06b36-7765-a512-edc4-9b48185950f9@joelhalpern.com>
In-Reply-To: <72a06b36-7765-a512-edc4-9b48185950f9@joelhalpern.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-06-03T08:28:27Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=42558ec7-c2df-453b-91b9-26ae079a54bd; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.26.52]
Content-Type: multipart/alternative; boundary="_000_a8adf3a66f784c8886c3463fe42ffa9forangecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/Y-CrHO0Tsjr96AiwrdMNRatjQxI>
Subject: Re: [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: Fri, 03 Jun 2022 08:31:57 -0000

Hi Joel, all,

I support progressing this document to the IESG.

FWIW, I do have some easy to fix points that you can find at:


  *   pdf: https://raw.githubusercontent.com/boucadair/IETF-Drafts-Reviews/master/draft-ietf-sfc-ioam-nsh-10-rev%20Med.pdf
  *   doc: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-sfc-ioam-nsh-10-rev%20Med.doc

Joel, if you are looking for a Shepherd for this doc, I will be more than pleased to help.

Cheers,
Med

De : sfc <sfc-bounces@ietf.org> De la part de Joel Halpern
Envoyé : jeudi 2 juin 2022 20:52
À : sfc@ietf.org
Objet : [sfc] WG LC for draft-ietf-sfc-ioam-nsh

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

_________________________________________________________________________________________________________________________

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.23.0 | Report a Bug | By Email