IETF Logo Mail Archive

Re: [sfc] The SFC WG has placed draft-eastlake-sfc-nsh-ecn-support in state "Candidate for WG Adoption"

<mohamed.boucadair@orange.com> Thu, 17 January 2019 14:12 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 461BB128CB7; Thu, 17 Jan 2019 06:12:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 bqtSWSAmKBjG; Thu, 17 Jan 2019 06:12:40 -0800 (PST)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 671B7130EA3; Thu, 17 Jan 2019 06:12:40 -0800 (PST)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr27.francetelecom.fr (ESMTP service) with ESMTP id 43gQyG75fKz4wFK; Thu, 17 Jan 2019 15:12:38 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.32]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id 43gQyG5vxBzDq78; Thu, 17 Jan 2019 15:12:38 +0100 (CET)
Received: from OPEXCAUBM8F.corporate.adroot.infra.ftgroup (10.114.13.107) by OPEXCLILM32.corporate.adroot.infra.ftgroup (10.114.31.32) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 17 Jan 2019 15:12:38 +0100
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM8F.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0415.000; Thu, 17 Jan 2019 15:12:38 +0100
From: mohamed.boucadair@orange.com
To: IETF Secretariat <ietf-secretariat-reply@ietf.org>, "sfc-chairs@ietf.org" <sfc-chairs@ietf.org>, "draft-eastlake-sfc-nsh-ecn-support@ietf.org" <draft-eastlake-sfc-nsh-ecn-support@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] The SFC WG has placed draft-eastlake-sfc-nsh-ecn-support in state "Candidate for WG Adoption"
Thread-Index: AQHUoyK7AP7W2v1e202zdcW0+LgwT6WzknSw
Date: Thu, 17 Jan 2019 14:12:38 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EA09352@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <154649225579.32607.12231566034033496144.idtracker@ietfa.amsl.com>
In-Reply-To: <154649225579.32607.12231566034033496144.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
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/dvuHEoDvXNSDHk_AbQYLNqR9hoE>
Subject: Re: [sfc] The SFC WG has placed draft-eastlake-sfc-nsh-ecn-support in state "Candidate for WG Adoption"
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: Thu, 17 Jan 2019 14:12:42 -0000

Hi all, 

I do think that ECN is naturally better handled at the transport encapsulation instead of the NSH itself. 

Requiring the functionality to be handled at the transport encap (draft-ietf-tsvwg-rfc6040update-shim) and NSH is redundant, IMO.

I like the approach we set in the SFC architecture in which we separated service matters from transport ones. I'd vote for maintaining that separation cleaner as it was set in the arch RFC.

Thank you.  

Cheers,
Med

> -----Message d'origine-----
> De : sfc [mailto:sfc-bounces@ietf.org] De la part de IETF Secretariat
> Envoyé : jeudi 3 janvier 2019 06:11
> À : sfc-chairs@ietf.org; draft-eastlake-sfc-nsh-ecn-support@ietf.org;
> sfc@ietf.org
> Objet : [sfc] The SFC WG has placed draft-eastlake-sfc-nsh-ecn-support in
> state "Candidate for WG Adoption"
> 
> 
> The SFC WG has placed draft-eastlake-sfc-nsh-ecn-support in state
> Candidate for WG Adoption (entered by Joel Halpern)
> 
> The document is available at
> https://datatracker.ietf.org/doc/draft-eastlake-sfc-nsh-ecn-support/
> 
> Comment:
> This starts the WG call for adoption of this draft.
> Please respond to the list, indicating support for this as a work item of the
> working group with this document as the basis for the work, or objection to
> the working group adopting this item as a working group draft.
> 
> The authors should confirm to the chairs and WG secretary that all IPR known
> to them relevant to this draft has been disclosed.
> 
> The working group adoption call will last 2 weeks, ending at the end of the
> day on Thursday, January 17 2019 COB somewhere.
> 
> Thank you,
> Joel
> 
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc

v2.23.0 | Report a Bug | By Email