Re: [mpls] Comments about draft-xiong-mpls-path-segment-sr-mpls-interworking and difference between Path Segment and BSID

Dhruv Dhody <dhruv.ietf@gmail.com> Thu, 12 September 2019 10:18 UTC

Return-Path: <dhruv.ietf@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 2F7C312010E; Thu, 12 Sep 2019 03:18:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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_HELO_NONE=0.001, SPF_PASS=-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=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 B9eton7jQ7M1; Thu, 12 Sep 2019 03:18:00 -0700 (PDT)
Received: from mail-io1-xd44.google.com (mail-io1-xd44.google.com [IPv6:2607:f8b0:4864:20::d44]) (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 1522D120077; Thu, 12 Sep 2019 03:18:00 -0700 (PDT)
Received: by mail-io1-xd44.google.com with SMTP id d25so53237840iob.6; Thu, 12 Sep 2019 03:18:00 -0700 (PDT)
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=OxnJ1vKsvMXyH1qWum1Uw/eFEOG6sR37phBoj59XyAg=; b=UGbb8wFmdsFoAlthOx2iYpLflIimTEbT3ZRwDQpFRgd7xdash0BjynIE3oGA8N9Vz5 v8FoJ+wRNkPU2SlHjY5IuvLwTrYPGxBMSZXzhjBVTTe7KPmKc80E0ct2NruhAQAq2HrK k8LhLLc1lXuXT5bbSF41KXm0hUcIjVXMElNehK93+wQ2ccnItvt3Sm2i/R/cRiKIRkJh JfCbg3+mMZmz2S2SvZ7vtf4sltXz2sNK+n8OccMlgdKdCIlzmYcRbVyFJOkULeKFGC+x 2emxXmv3G65X/Mm3G7uAQx3NzJdkkmSjJ8keRPo+Bki2ZFY2dahBoK/gwXbpiHC+sH4D CqAA==
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=OxnJ1vKsvMXyH1qWum1Uw/eFEOG6sR37phBoj59XyAg=; b=PJz/4rJWAnI25DctRaTWPfn0Zy/wwuG9kQivBApBoaD/ghWHhmb+jyd2Z7hI3O2/IV //d9VKtv62wz0cOQx04/N70Qj2KfFNX9IAVRd+L52BrnstAWx/qfp+pGw3xXSPTkfDfa z30d7A8nwB0PFJIH93VmkIplwXeuNwRt9l8/ZymQjRKd6lwnSDEzTebfuBIz+i0CrQGf G33Mu8IlHZ8qfrOQUUvLEK5QAb+9j+fpiq6dysMUYOLZsF0e5dKJVAcbFfGdlDez2D8R lbquqs9xfK3pHwkiOFPytZwG0qfFRMo2pCya9s/sKfaI8Cj1VD33S0chvxgmhiF0FFgt DBlw==
X-Gm-Message-State: APjAAAVYJD2o2+mOdWYaJXxAjZP2MmcEKmf5B7TxaGL9qrzZz1ru/E9r lTnwtDrwDnhv79vbofdEswMbMjW1ZX3eyToIw74=
X-Google-Smtp-Source: APXvYqyyaHf6dVMJxoBsisX3RHsA2praXYUT+2O1A10ioxoP8BBfvunw2CpZEzVcFVh8XDStVckBfTdmA7iqg/V9H0A=
X-Received: by 2002:a6b:e318:: with SMTP id u24mr3443393ioc.279.1568283479259; Thu, 12 Sep 2019 03:17:59 -0700 (PDT)
MIME-Version: 1.0
References: <201909121505032731162@zte.com.cn>
In-Reply-To: <201909121505032731162@zte.com.cn>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Thu, 12 Sep 2019 15:47:23 +0530
Message-ID: <CAB75xn68Ex0TUVQAWKw8K+yfWDV4TG==+WUy4ojF4rB7Oa=Xhg@mail.gmail.com>
To: xiong.quan@zte.com.cn
Cc: Loa Andersson <loa@pi.nu>, Tarek Saad <tsaad.net@gmail.com>, mpls@ietf.org, draft-xiong-mpls-path-segment-sr-mpls-interworking@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b0423f05925873f3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/Z-K4migSyPc0934PbaYatVhUehY>
Subject: Re: [mpls] Comments about draft-xiong-mpls-path-segment-sr-mpls-interworking and difference between Path Segment and BSID
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 12 Sep 2019 10:18:02 -0000

Hi Quan,

Thanks for your mail and further discussion.

It is not about Path SID v/s Binding SID, both are needed and each serve a
specific purpose.

The comment I made during 105 was that you are using Path SID to do the
function of Binding SID!

See
https://tools.ietf.org/html/draft-xiong-spring-path-segment-sr-inter-domain-00#section-3.1,
where you say -

  The border nodes should
  install the following MPLS data entries for Path segments:

    incoming label: i-Path
       outgoing label: the SID list of the next domain or link + next i-Path

Here you are not using Path SID for OAM/PM but for the functionality of
Binding SID! That seems like a wrong thing to do!

Thanks!
Dhruv

On Thu, Sep 12, 2019 at 12:35 PM <xiong.quan@zte.com.cn>; wrote:

> Hi  all,
>
>
> I noticed you proposed comments at the IETF#105 MPLS meeting to the draft
> "draft-xiong-mpls-path-segment-sr-mpls-interworking". Your comment and
> review is very appreciated!
>
>
> The Path Segment defined in draft-ietf-spring-mpls-path-segment has been
> proposed and adopted in Spring WG.
>
> The Path Segment is a path identification for Performance measurement and
> Bidirectional path correlation and End-to-end Path Protection.
>
> The draft "draft-xiong-mpls-path-segment-sr-mpls-interworking" mainly
> focus on the SR and MPLS Interworking with Path Segment to provide
>
> end-to-end bidirectional VPN service in inter-domain scenario.
>
>
> I noticed the Binding SID is also used in inter-domain scenario. I think
> the main difference is as follows:
>
> Binding SID indicates a SID List. Selected path by replace the Binding SID
> to a SID List. Path Segment indicates a path, it can realize
> OAM,PM,protection. Selected path by path segment correlation.
>
> Binding SID can not replace path segment in bidirectional path, OAM, PM
> and protection etc. If we use Binding SID, the per-segment or per-domain
> OAM/PM/protection can not be achieved.
>
>
> I just start the discussion and comments and suggestions are very welcome!
>
>
> Best Regards,
>
> Quan
>