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

"Andrew G. Malis" <agmalis@gmail.com> Thu, 17 January 2019 14:49 UTC

Return-Path: <agmalis@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 7B46D1277CC; Thu, 17 Jan 2019 06:49:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 WK3z2cecKmtf; Thu, 17 Jan 2019 06:49:45 -0800 (PST)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (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 AAC181276D0; Thu, 17 Jan 2019 06:49:45 -0800 (PST)
Received: by mail-qt1-x830.google.com with SMTP id t13so11567831qtn.3; Thu, 17 Jan 2019 06:49:45 -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=eL9nwV6LGCisEe2P3E756kDzKMNeLN15m3n5VIXTI0A=; b=ep2UO49DVQlvJO+bv2CafrandefMAwjmPMfASlfVegrLIniK0xL2F7KYtGB2J0eksV vhC/sCycHJkndlPjCPbUFtiK6lAb3J6coCKdQhG5GZc1p0fCV4DvzjW5VseeNcTFEQ3C sldcKuNOQ4Llks4bpYEH62/T4xTbyCbsOM2j8NinseKCMuHqDEhYsqAil1aM1MVESU0z mM6eFVRbxAldePTiVm85ELozMrqXTCaPBAzIQGKdogHvTlm5j+E3C/IkHE7mk2l+6DXO qxE9qnPto/mEMquMT6KBrv9JKOBINuEnbW1xkuTqKqCvFbZSXKiZrUUrsfBNrQzys7QP VLcA==
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=eL9nwV6LGCisEe2P3E756kDzKMNeLN15m3n5VIXTI0A=; b=c47zLJfyNNxGOukyqLuvRN94WIgkOKE63jtz2pHBilwl3Md7aRPL1sfta0heE2a8jr DptD16F0ql36B3ZAgM4AnQf08IZ8xedu8m7gltMAy7nGWxwP1YtGSHTBvbILwSGb6AOB ZuFH3o7b62gMwEug9/hDpZWw7M7fMHLRJCmkwIq/DLZ370vo5AwaLQPA9F96Qr4DkaUH HPrEpvPP1UWsr+35YQ91aO+c7rcgxUGVy6p2QhZrsVohbiawl3kmuN7pPvPUgRxRJKlv AYKu6auV7Y9qJS+wJUBMaFLCNhJVsCaoGUQG/AKtwqfKYGaDFP0oVqlgGYE4zaeBi5UK I5wQ==
X-Gm-Message-State: AJcUukcQShjjob9/oWQoFT3Y+WQ064NpA3wFiumUEmncevEzviER8awQ 0XOQgnPxpFvZBbYBfMw/Jrswlr0ik5dZY5n6HxY=
X-Google-Smtp-Source: ALg8bN4QnKsxSYbVs9Mbk0sJBZLJLXkAerD0+th82gFYhPulay1urEkIo+IcIrnlID1PV6y9Gto+vGUNSjlZcK5rNpA=
X-Received: by 2002:a0c:878d:: with SMTP id 13mr11476674qvj.8.1547736584671; Thu, 17 Jan 2019 06:49:44 -0800 (PST)
MIME-Version: 1.0
References: <154649225579.32607.12231566034033496144.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B93302EA09352@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93302EA09352@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 17 Jan 2019 09:49:33 -0500
Message-ID: <CAA=duU2DOKXFH6GTDsVxN__OcfEUc5D-2tszGd2Z7QYBmyCv0w@mail.gmail.com>
To: BOUCADAIR Mohamed IMT/OLN <mohamed.boucadair@orange.com>
Cc: 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>
Content-Type: multipart/alternative; boundary="00000000000055d691057fa881e6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/wu_FCmiuYC8MQjc2B59CCClrMJQ>
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:49:49 -0000

Med,

Not all transports support ECN marking, for example NSH over MPLS.

And even where the transport supports ECN marking, note the example in
Figure 1 in the draft where the outer encapsulation can be stripped during
SFF processing. In that case, the scope of the ECN marking is limited to
individual SFF-SFF links. rather than end-to-end.

Cheers,
Andy


On Thu, Jan 17, 2019 at 9:12 AM <mohamed.boucadair@orange.com> wrote:

> 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
>