[Pce] Clarification regarding SR-ERO Validation Error
Mrinmoy Das <mrinmoy.ietf@gmail.com> Tue, 22 February 2022 11:22 UTC
Return-Path: <mrinmoy.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 352683A0E06
for <pce@ietfa.amsl.com>; Tue, 22 Feb 2022 03:22:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.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_HI=-5, 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 8MCwXMy-xofh for <pce@ietfa.amsl.com>;
Tue, 22 Feb 2022 03:22:28 -0800 (PST)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com
[IPv6:2a00:1450:4864:20::536])
(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 8EC9F3A0E0B
for <pce@ietf.org>; Tue, 22 Feb 2022 03:22:19 -0800 (PST)
Received: by mail-ed1-x536.google.com with SMTP id s24so29657187edr.5
for <pce@ietf.org>; Tue, 22 Feb 2022 03:22:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
h=mime-version:from:date:message-id:subject:to;
bh=XGHXzEDkpQ+TZNy6c8nQ25cLZ/8T1q+IMo9j5nDTgzo=;
b=XcrQWEVVl7vcvsuoCb8PRuWmRUnK86cXZdCv2JxDVg4Aa4nqPrhaIyrSK5RS/fUSJv
keDXEpo/D3sgId4CUIlWKhw0p6m1BRkSJBiEnHEO15gUch2KPrvMuePq4VXCz1egzWX4
vGTLgCoyS2MS8ZPgioQSNfepWe2IcJx2UQn91N9/LI+0qRaUCkRxt3czD6g3D14pzT5J
xWQGZgK++2BG++xR6x5kkB62Eed4wNXLgvtJGGM2dPeappBkJG4U0ALJUdAz7I9q9dLA
FMMPv/RTHGWCegbxZKouiWlGF0jykUPNVNBmmFPIw8NbnsV6t55YAdTJUP+CHVJdJB9p
Ubwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=XGHXzEDkpQ+TZNy6c8nQ25cLZ/8T1q+IMo9j5nDTgzo=;
b=MCvBJgMe5EpsE3at4b9iKPnJ25QP5FsFthgnLjAD0ZITOv45J1ByhjEfJg9GEvb5TP
m2gHriKbbUzV5GC+jcFX+5XF67R40X8wdfihNYvuQdOjSXiwQxJ66pSyCvOjxBh8SHWE
bQB50uik7OqmO/3YOEe5QPLhuZKU5tN1umnaNgnQ5oX7vf/quYIxXuQ5+dVnh1JUKPzt
eelK7zp2vjPKZyWa4ahqYd9YxkTkg4XjVJL3R/rOij/r21FKa9c8w2KzUrwMA4UTHZQa
deHLFCdOQl+VeFUBs8H+hd//AM50K2MN3VNcv6kYak7aiqv4ii8njIQPJT7tGOL6oPN3
ZEjg==
X-Gm-Message-State: AOAM532wYmzZZchmV4+icp9EogN2/0PiDaQh3g9qEVf35PTJ0B2kYiTi
MfkwbKRBVGym5cY7PG9YJAa+sICdbFmTq60OmUO19xHNnVw=
X-Google-Smtp-Source: ABdhPJxPHfqGGY8kL9HHSnnljRX6243gIBCPSbYE9Ke6jIho1HA8vmGjIYJ6YFCqr2pGFtieylpr1yAF+b6XmwxNyFE=
X-Received: by 2002:a05:6402:278b:b0:408:e865:45af with SMTP id
b11-20020a056402278b00b00408e86545afmr25968942ede.44.1645528936796; Tue, 22
Feb 2022 03:22:16 -0800 (PST)
MIME-Version: 1.0
From: Mrinmoy Das <mrinmoy.ietf@gmail.com>
Date: Tue, 22 Feb 2022 16:52:05 +0530
Message-ID: <CANVfNKqZztkOsfYwmcZGucHn3oZetHyv+8W9x67i8tgVstw8Eg@mail.gmail.com>
To: pce@ietf.org
Content-Type: multipart/alternative; boundary="000000000000bed4eb05d8998f4f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/umEoxzHTsa0t3bAEok0RU6FWGRo>
Subject: [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:22:30 -0000
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.
Thanks,
Mrinmoy
- [Pce] Clarification regarding SR-ERO Validation E… Mrinmoy Das
- Re: [Pce] Clarification regarding SR-ERO Validati… Dhruv Dhody
- Re: [Pce] Clarification regarding SR-ERO Validati… Mrinmoy Das