Re: [mpls] I-D Action: draft-ietf-mpls-sfl-framework-01.txt

Stewart Bryant <stewart.bryant@gmail.com> Mon, 29 January 2018 16:38 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1B1D12EC94 for <mpls@ietfa.amsl.com>; Mon, 29 Jan 2018 08:38:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, 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 Bcx0rMzvcX6U for <mpls@ietfa.amsl.com>; Mon, 29 Jan 2018 08:38:52 -0800 (PST)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (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 AD24812D87C for <mpls@ietf.org>; Mon, 29 Jan 2018 08:38:51 -0800 (PST)
Received: by mail-wm0-x234.google.com with SMTP id t74so15600703wme.3 for <mpls@ietf.org>; Mon, 29 Jan 2018 08:38:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=pTCveIfvvc4Ptsh6eGtTTXu/uvaTmt2DpeYQBLPX8ik=; b=BlfD4LiH42lMQs8LZBbRv0f3wkWYNfGEhNloOaDzlxA/JHiYsDbvzyV4KSKXs1swtW cFC+izYwQNxkyjKus8e1ijJ1XvDKxx++bXWNb+xw1SkeeVq4ajguHflBPapt2S7MjMHq K1JH//mKVKW678K84bXp8iF9bzFKhJNsFz1wkA6/JC8khYYD1RfuXK4j2VzFjoFkB6Yc ACtO9qqL9Z0zd1kj1zwcDsn/arsOAQoPXt6JbfP3PWwn4MWEYoBb/I+BwidBspmcK9SZ pdhy5jcmdZhzAyiexF8O+/LccPqHOo0jPuXFMROtA/+Jvy03y8MQpITOV3ZDwGwEDctu hg0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=pTCveIfvvc4Ptsh6eGtTTXu/uvaTmt2DpeYQBLPX8ik=; b=CIcg0eKLUJ+/EjEDss7+zmjViAdkL49LPmoKemCOBY0Hsm9TriieUAETRs7UZauM5s KXr2wV63slkdxIR9lhO26P2v4QAaAyxIosZc2dV1QzEjshGhHSIPeph10eieOyQRleiD 3S3lOqxLGGWmnsQigNvuXqfpAt0A1ASsRGe/L98tNasc1ESEBdppXLhIheEDKtLINygq +T37rZdM5/LI/AqhpwwhQGhjcnhygEX+JevulrzellbZFFt9rXksUhwmQonSapdBBT8p gayUGY4Gs3rpyl9y1xoIH2S2JNQ/W643nrDIS0TkTAATeEvgdGYfzwfSQLuX9nftyzaG vFsg==
X-Gm-Message-State: AKwxytcORjvOlrXAByPPTszxnCioaCM0Apx2kOfYaQZ/nVA3wCnorLn2 9M45Yb0YbbmPeq3+uW9p3USxLkFD
X-Google-Smtp-Source: AH8x2254JmPflkCz1xV2UPIQszmpTRVa7GL5W1Dw0tL6uk6INj2LS9wuyUrw2uhs+XToO2Ucn7JagQ==
X-Received: by 10.28.148.214 with SMTP id w205mr18222814wmd.67.1517243929974; Mon, 29 Jan 2018 08:38:49 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id v75sm15047736wrc.45.2018.01.29.08.38.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Jan 2018 08:38:49 -0800 (PST)
To: Balaji venkat Venkataswami <balajivenkat299@gmail.com>, mach.chen@huawei.com, mpls@ietf.org
References: <CAHF4apONg86UYSK9qJN_-bkcw0TcdFXMjgad+gSoxwDmsFbOmA@mail.gmail.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <88650e7a-5fbb-1a99-dbc0-19650db99146@gmail.com>
Date: Mon, 29 Jan 2018 16:38:47 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <CAHF4apONg86UYSK9qJN_-bkcw0TcdFXMjgad+gSoxwDmsFbOmA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------AA00DAE19062554D1451C964"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/vMDSJvTNYvSqQybQvbvwSbQ55WQ>
Subject: Re: [mpls] I-D Action: draft-ietf-mpls-sfl-framework-01.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jan 2018 16:38:59 -0000


On 29/01/2018 14:50, Balaji venkat Venkataswami wrote:
> Hi Authors,
>
> In the current version of the draft, this follows in section 5.
>
>
>
>     The introduction to an SFL to an existing flow may cause that flow to
>     take a different path through the network under conditions of Equal
>     Cost Multipath (ECMP).  This is turn may invalidate the certain use
>     of the SFL such as performance measurement applications.  Where this
>     is a problem there are two solutions worthy of consideration:
>
>     1.  The operator can elect to always run with the SFL in place in the
>         MPLS label stack.

What this is saying is that you could set up monitoring at for example 
PW or VPN
creation and always run with that extra label. This is not ideal but the
ECMP issue goes away. In other words always run with the SFL in place.



>
>     2.  The operator can elect to use [RFC6790] Entropy Labels in a
>         network that fully supports this type of ECMP.  If this approach
>         is adopted, the intervening MPLS network MUST NOT load balance on
>         any packet field other than the entropy label.  Note that this is
>         stricter than the text in Section 4.2 of [RFC6790].  In networks
>
> Bryant, et al. Expires August 2, 2018 [Page 7]
> Internet-Draft MPLS FI January 2018
>
>         in which the ECMP decision is independent of both the value of
>         any other label in the label stack, and the MPLS payload, the
>         path of the flow with the SFL will be congruent with the path
>         without the SFL.
>

This is an alternative to point 1. Use the EL system (always) and 
require a strict implementation
of it in which the only packet characteristic taken into account when 
selecting the ECMP path
is the value of the EL.

The text seems clear, but if you have any changes in mind please let me 
know.

Best Regards

- Stewart

> Question ?
>
> You dont seem to be considering the consequences of point 1 in the 
> explanation given.
> Or are you trying to say that if point 1 is what is followed, the ECMP 
> decision should be
> independent of the SFL label in place and the MPLS payload, so that 
> the path of the
> flow with the SFL in place will be congruent with the path without the 
> SFL ?
>
> Are you specifying something in point 2 that also applies to point 1 ?
>
> Please clarify.
>
> thanks and regards,
> balaji venkat