Re: [sfc] WG Adoption calls: two MD-1 drafts
<mohamed.boucadair@orange.com> Thu, 30 November 2017 09:36 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 ED740127337 for <sfc@ietfa.amsl.com>; Thu, 30 Nov 2017 01:36:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.398
X-Spam-Level:
X-Spam-Status: No, score=-5.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Oz1gua27Qq5D for <sfc@ietfa.amsl.com>; Thu, 30 Nov 2017 01:36:15 -0800 (PST)
Received: from orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E76F127601 for <sfc@ietf.org>; Thu, 30 Nov 2017 01:36:15 -0800 (PST)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) by opfednr26.francetelecom.fr (ESMTP service) with ESMTP id B46BE20E85; Thu, 30 Nov 2017 10:36:13 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.58]) by opfednr02.francetelecom.fr (ESMTP service) with ESMTP id 9620B12022E; Thu, 30 Nov 2017 10:36:13 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM33.corporate.adroot.infra.ftgroup ([fe80::3881:fc15:b4b2:9017%19]) with mapi id 14.03.0361.001; Thu, 30 Nov 2017 10:36:13 +0100
From: mohamed.boucadair@orange.com
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] WG Adoption calls: two MD-1 drafts
Thread-Index: AQHTaVe6313Mvadxp0yankAfX0uRmqMsoiog
Date: Thu, 30 Nov 2017 09:36:13 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300A083FA6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <a4824833-03da-16e4-2d5e-b88757454d9c@joelhalpern.com>
In-Reply-To: <a4824833-03da-16e4-2d5e-b88757454d9c@joelhalpern.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/vBSmISdF0W-ViT0_pz-Jo_M45ow>
Subject: Re: [sfc] WG Adoption calls: two MD-1 drafts
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.22
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, 30 Nov 2017 09:36:18 -0000
Joel, all, (1) draft-guichard-sfc-nsh-dc-allocation-07 addressed the comments I had on -06 (https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-guichard-sfc-nsh-dc-allocation-06-rev%20Med.doc). Many thanks to the authors. I'm happy with this document to be adopted. In order to remove the dependency on draft-penno, the authors may consider adding a pointer to the format of the Opaque Service Class when F=02. For example, the text can indicate that the format is the one depicted in Figure 2 of RFC6759: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Class. Eng. ID |zero-valued upper-bits ... Selector ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 2: Selector ID Encoding The text should also warrant that some defined selector IDs are encoded in 5 bytes. Evidently, those cannot be inserted in this MD-1 format. The text should call those explicitly (See Section 4.2 of RFC6759). (2) I do also support draft-napper-sfc-nsh-broadband-allocation. Cheers, Med > -----Message d'origine----- > De : sfc [mailto:sfc-bounces@ietf.org] De la part de Joel M. Halpern > Envoyé : mercredi 29 novembre 2017 22:19 > À : sfc@ietf.org > Objet : [sfc] WG Adoption calls: two MD-1 drafts > > The WG chairs have been asked to issue calls for adoption for two of the > MD-1 related drafts: > > https://datatracker.ietf.org/doc/draft-napper-sfc-nsh-broadband- > allocation/ > > and > > https://datatracker.ietf.org/doc/draft-guichard-sfc-nsh-dc-allocation/ > > These documents aim for publication as Informational RFCs. > > As Jim is the coauthor on one of these two, I will be overseeing both > adoption calls. > > Given that there are two last calls an two calls for working group > adoption (see following emails) we are allowing 3 weeks for these calls. > > Please respond with either support or objection to the WG adopting > either or both of these documents. > > We need to see feedback. Silence does not imply consent. > We would prefer feedback with content. > > Thank you, > Joel > > _______________________________________________ > sfc mailing list > sfc@ietf.org > https://www.ietf.org/mailman/listinfo/sfc
- [sfc] WG Adoption calls: two MD-1 drafts Joel M. Halpern
- Re: [sfc] WG Adoption calls: two MD-1 drafts Sumandra Majee
- Re: [sfc] WG Adoption calls: two MD-1 drafts Andrew G. Malis
- Re: [sfc] WG Adoption calls: two MD-1 drafts mohamed.boucadair
- Re: [sfc] WG Adoption calls: two MD-1 drafts Carlos Pignataro (cpignata)
- Re: [sfc] WG Adoption calls: two MD-1 drafts Joel M. Halpern
- Re: [sfc] WG Adoption calls: two MD-1 drafts Paul Quinn (paulq)
- Re: [sfc] WG Adoption calls: two MD-1 drafts Muley, Praveen (Nokia - US/Mountain View)
- Re: [sfc] WG Adoption calls: two MD-1 drafts Joel M. Halpern