Re: [Pce] Clarification Regarding Binding SID in SR-ERO/SRv6-ERO

Dhruv Dhody <dd@dhruvdhody.com> Wed, 24 May 2023 05:01 UTC

Return-Path: <dd@dhruvdhody.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 246D7C14CF13 for <pce@ietfa.amsl.com>; Tue, 23 May 2023 22:01:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level:
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dhruvdhody-com.20221208.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B8gTJ2citgxD for <pce@ietfa.amsl.com>; Tue, 23 May 2023 22:01:46 -0700 (PDT)
Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64843C14CE52 for <pce@ietf.org>; Tue, 23 May 2023 22:01:46 -0700 (PDT)
Received: by mail-vs1-xe2a.google.com with SMTP id ada2fe7eead31-438a5069d58so171239137.0 for <pce@ietf.org>; Tue, 23 May 2023 22:01:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dhruvdhody-com.20221208.gappssmtp.com; s=20221208; t=1684904505; x=1687496505; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=iAG9YEW+ZEp6yDx3iTuTcwVfPB8RSglrObePmFuf3Ak=; b=q1MPD4YqpE7Zzxr94YCzodKwa1T7hFaEkkl9ewpTxLzL2k84KF/t//SO/QaslXYLka kN/yHDdmAK2Gu4CVtb7Pjed8zAJWzw5DTl0iwUD09vkohFSQnhXO2PXGaFpcjj8KF+NV dR0mg1PQKGx20Rqx08Dckefaj4ReEWriLOZV0w1nQ9vPUQKSEXDoK1P5YWgOdEOg30Sd jVgGUPgVlFhKDObBNbTjVj8HR/3Ze1uQGSW8KV6eo39omZ3mSwFWqyqILgN6a7yh+xAP zM80oK/XGwrpTAa3PmA8+bqnHHy9KTHge4rLl6ijZL8S9iGa4UBFepyfug0yZCV7APid 2SAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684904505; x=1687496505; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=iAG9YEW+ZEp6yDx3iTuTcwVfPB8RSglrObePmFuf3Ak=; b=X3FWQ8jgjDmX/5aszGIwaw4oTJPENd99ObydRstwTQMj+TVSDV/xxw/kD6WiYZ4MZ9 EQYKSDWaqOi/Km41x+wSUBs5bBwO8EOatgjM9izCEpdTu0v32SartQfuiIqqMwZIEY90 Vwo8sCQH1pM6NDp3tnD8WweKJdRfbt1sUqu4jnKNMLz+LYWqlFN98yrkccgNDp5sn3mj y58q2GYav+IesSQYxd9/WZnyWuXWrxAzInpwiffCMts10sIr/sAO9Kd7fXeghkSmyyxG C6eHv9gviU116nPcYEXDBht2KeieLEc921zt1QbmWUqn3mPt6q0Nx+znWDsRNWOkhBp7 5wiA==
X-Gm-Message-State: AC+VfDxiCmUFDF95e8LIkxrB3Vsdk/4tSkwZNESq34nasG7nGx7a+D0W MVCjpsh6+Ooj9ojqZ/T6JNLnkwkFyrI/coAcU5umyw==
X-Google-Smtp-Source: ACHHUZ7m0xlb6jiylNVGJUDNFIDdp5xZcK9Wq4qtMqR2PQICAG9Rp0z+KWQ5LgCWD+C2e93YaRThDpFarLPAX6NQ+Ic=
X-Received: by 2002:a67:d013:0:b0:434:8401:beb5 with SMTP id r19-20020a67d013000000b004348401beb5mr4298794vsi.35.1684904505266; Tue, 23 May 2023 22:01:45 -0700 (PDT)
MIME-Version: 1.0
References: <CANVfNKp3m0ByOCW9+Hmir72H1HRtA=g4xOWxgjUEAYeUyy7S-w@mail.gmail.com>
In-Reply-To: <CANVfNKp3m0ByOCW9+Hmir72H1HRtA=g4xOWxgjUEAYeUyy7S-w@mail.gmail.com>
From: Dhruv Dhody <dd@dhruvdhody.com>
Date: Wed, 24 May 2023 10:31:09 +0530
Message-ID: <CAP7zK5Y901JFT+qOfipR+s=0o1szhXoLrxSS-=NrrKG9rmSRaQ@mail.gmail.com>
To: Mrinmoy Das <mrinmoy.ietf@gmail.com>
Cc: pce@ietf.org
Content-Type: multipart/alternative; boundary="00000000000084684005fc69660b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/KKmI_W-6U9tqc49iFo2CqyrRWR8>
Subject: Re: [Pce] Clarification Regarding Binding SID in SR-ERO/SRv6-ERO
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 May 2023 05:01:48 -0000

Hi,

Just to close this on the list as well -- Mrinmoy and I discussed this
offline and the confusion with the BSID in the TLV and the BSID as part of
the SR-ERO subobject is cleared! No further action is needed!

Thanks!
Dhruv

On Wed, May 17, 2023 at 1:02 PM Mrinmoy Das <mrinmoy.ietf@gmail.com> wrote:

> Hello Team,
>
> I was reading
> https://datatracker.ietf.org/doc/draft-ietf-pce-binding-label-sid/16/ and
> find below sections:
>
> 6.  Binding SID in SR-ERO
>
>    In PCEP messages, LSP route information is carried in the Explicit
>    Route Object (ERO), which consists of a sequence of subobjects.
>    [RFC8664] defines the "SR-ERO subobject" capable of carrying a SID as
>    well as the identity of the node/adjacency (NAI) represented by the
>    SID.  The NAI Type (NT) field indicates the type and format of the
>    NAI contained in the SR-ERO.  In case of binding SID, the NAI MUST
>    NOT be included and NT MUST be set to zero.  [RFC8664] Section 5.2.1
>    specifies bit settings and error handling in the case when NT=0.
>
> 7.  Binding SID in SRv6-ERO
>
>    [I-D.ietf-pce-segment-routing-ipv6] defines the "SRv6-ERO subobject"
>    for an SRv6 SID.  Similarly to SR-ERO (Section 6), the NAI MUST NOT
>    be included and the NT MUST be set to zero.  [RFC8664] Section 5.2.1
>    specifies bit settings and error handling in the case when NT=0.
>
>
> Suppose in a SR LSP, there is an ERO object with 3 ero-subobjects, having
> MPLS labels 20, 50, 80.
> Now, this LSP also has 3 binding TLV, having MPLS labels 10, 50, 75.
>
> Now, my questions are:
> 1. Is the restriction mentioned in section 6 means only ERO sub-object
> having MPLS label 50 will not have any NAI as the same label is present as
> Binding value? Other ERO sub-objects having label 20 and 80 can have NAI as
> there is no binding value same to it?
> 2. How does the SID/Label stack look for this LSP in example?
>
> Thanks & Regards,
> Mrinmoy
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>