IETF Logo Mail Archive

Re: [Pce] Clarification regarding SR-ERO Validation Error

Dhruv Dhody <dhruv.ietf@gmail.com> Tue, 22 February 2022 11:47 UTC

Return-Path: <dhruv.ietf@gmail.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 CA2B93A0E6E for <pce@ietfa.amsl.com>; Tue, 22 Feb 2022 03:47:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-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 6B_nZEihRk74 for <pce@ietfa.amsl.com>; Tue, 22 Feb 2022 03:47:54 -0800 (PST)
Received: from mail-il1-x130.google.com (mail-il1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (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 4E1E23A0E6D for <pce@ietf.org>; Tue, 22 Feb 2022 03:47:54 -0800 (PST)
Received: by mail-il1-x130.google.com with SMTP id q4so5539715ilt.0 for <pce@ietf.org>; Tue, 22 Feb 2022 03:47:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3In0zOHaiy/KWESjkNLMHmBwnBvzT590fXCNbhx8jMM=; b=NMFvOLgD8IPKKWqxQ/Fv7onDdzSIOV4LuBu+QY3T1A0vEPLbnW8qdbtEPz6p6Cazig +xauHfqU9hZbYmzl7QjPHepMj45Tf9aDL9J0qoqIvp0tAWGPGIZqY79IRhMFOmgrFfc6 nYPa9k+xW63t3wfBzfoD4iBE954U4F/SP9a/Iz6dDIIq88aXu/YS6JBG0ln8pVFhUxMg JrNc7Ry6STVQTAEhTmufjN4ZdNQoGVz1R4I9PL+mpNJLriTuooq41oFzX96n2lhwoM6V xtULp7LoGhe9s1CDg9oSke26WLwcZk9nXXCSUwrYNGfxpRxZiTtwSDDPd4mcCl8JFMJr 2kEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3In0zOHaiy/KWESjkNLMHmBwnBvzT590fXCNbhx8jMM=; b=gXbuBi0/6zCLV5PkT9lWbvsmlTdzdGXMXnSivUWtJgRrSM4qn+IYOjZvjn5FWWDghf ndNQV3IwpFDOlg9YvKfgHHNgRsWOH3GWlCSxE8vT9QN2g6H/C8O9zcbwlJhIHoh95cop 08GmVRWU6wAlQHhpkobYB+JG59HLZkaCAOy7RfxmQhRWuTb4A3r5WHd88IBIq+fCRMQw mqdp91LYTSUUmLOHUDbbBf5cKZHOSvMJ0vDrk4xrnVTuLYWzUyTcA29E47M03iheL1fF E+h0ArJ0gm0EpNpovN6I7NQ/527DoWPsUSnpgQqVLd0BwuSVKbIBnMdwGCDdgcVIyOA4 Ocig==
X-Gm-Message-State: AOAM5304mOcmirxKAjGB7hOtqZ1Lci8kpAYyPkZjOGM5pMzOBF59vp7P RiN1IeoSdcNkSJrtQWDwBEs1RX4UUvUwEn3P1Iw=
X-Google-Smtp-Source: ABdhPJyb2Tolho5DRCV/7ihI/F1q1Q4zKF/y0SsTaO1SEqdb5d6WmujW3wLPCYtjiTRR2W3FZJkTGHkcMfplp7UfJcg=
X-Received: by 2002:a92:6907:0:b0:2bc:4b18:e671 with SMTP id e7-20020a926907000000b002bc4b18e671mr18930381ilc.299.1645530473086; Tue, 22 Feb 2022 03:47:53 -0800 (PST)
MIME-Version: 1.0
References: <CANVfNKqZztkOsfYwmcZGucHn3oZetHyv+8W9x67i8tgVstw8Eg@mail.gmail.com>
In-Reply-To: <CANVfNKqZztkOsfYwmcZGucHn3oZetHyv+8W9x67i8tgVstw8Eg@mail.gmail.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Tue, 22 Feb 2022 17:17:16 +0530
Message-ID: <CAB75xn7cf_Kzik0as6EWPDcK9WCSzSbZHTcC-r7bZgxtoiO+xw@mail.gmail.com>
To: Mrinmoy Das <mrinmoy.ietf@gmail.com>
Cc: pce@ietf.org
Content-Type: multipart/alternative; boundary="00000000000050c20905d899eb09"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/WRMiVqZDb91V1rnSyG54DgkJqDQ>
Subject: Re: [Pce] Clarification regarding SR-ERO Validation Error
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 22 Feb 2022 11:47:56 -0000

Hi Mrinmoy,

On Tue, Feb 22, 2022 at 4:52 PM Mrinmoy Das <mrinmoy.ietf@gmail.com> wrote:

> Hello Team,
>
> I found below SR-ERO validation in RFC 8664, 5.2.1
> <https://datatracker.ietf.org/doc/html/rfc8664#section-5.2.1>. SR-ERO
> Validation
>
>    The SR-ERO subobjects can be classified according to whether they
>    contain a SID representing an MPLS label value or an index value, or
>    no SID.  If a PCC detects that the SR-ERO subobjects are a mixture of
>    more than one of these types, then it MUST send a PCErr message with
>    Error-Type = 10 ("Reception of an invalid object") and Error-value =
>    20 ("Inconsistent SIDs in SR-ERO/SR-RRO subobjects").
>
>
> As per my understanding of the above text, there could be three types of
> SIDs:
>
> 1. *SID index: *S-bit = 0, M = 0,C = 0
> 2. *SID as MPLS label:* S-bit = 0, M = 1, C = 0/1
> 3. *Null:* S-bit = 1
>
> Now, if a LSP contains 3 SR-ERO subobjects then all those three should
> have the same SID type, e.g. all may be type 1, or type 2 or type 3 and
> there shouldn't be any combination of these 3 types.
>
> Is this understanding correct? Please let me know.
>
>
Yes! Your understanding is correct.

Thanks!
Dhruv



> Thanks,
> Mrinmoy
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>

v2.8.7 | Report a Bug | By Email