IETF Logo Mail Archive

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

Mrinmoy Das <mrinmoy.ietf@gmail.com> Tue, 22 February 2022 11:50 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 35EC23A0E77 for <pce@ietfa.amsl.com>; Tue, 22 Feb 2022 03:50:04 -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 0rOjwSV7J0mq for <pce@ietfa.amsl.com>; Tue, 22 Feb 2022 03:50:01 -0800 (PST)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 16CE33A0E6D for <pce@ietf.org>; Tue, 22 Feb 2022 03:50:01 -0800 (PST)
Received: by mail-ed1-x532.google.com with SMTP id s24so29830751edr.5 for <pce@ietf.org>; Tue, 22 Feb 2022 03:50:00 -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=iwYF+3CiF9QA4uvmy2jKemyk4QHqOWfYV6Co/RXM2AI=; b=k8UUs1m3fyGRmuLNsMxTZ2XaCKMINHXlI3SGtomCmY75aqiEFgt7BYLDpf57ltN1S8 mAof607YUe2rbB0PQlDXWXFqSddP/tAq7d0JxnAPpi9DVdjfZdf9iMILA8oFBJy6AiO6 hilwiy55gtUB+KdqvxGZ/6B04zoy0BWP7H5etaczyIJWPvRHkuW1uCghYVtc5Ix7zuyx ImvmJtgQ35U9RyN3kynMzBsu+ADNtW46a9hWH07tFnRvmcYGl5yvtcYtXkiHUPtjyTIq FQcMxALo0SnLQ/d2cvzRsf/iUhAwpX4Ckd2dxxuS56UjgxoaQSqqko1v4sk8ppPVs3Nz qp/A==
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=iwYF+3CiF9QA4uvmy2jKemyk4QHqOWfYV6Co/RXM2AI=; b=ouVAWZcFpJffs00yz/hsbnsT9xyyGjCLLtpN/B/EdjNx5gUwVwueWRPYcFHCNiuJPM RTcKmFaNrjgmXTWCQC9v8RK12AivPod9XiFp7HzfdXxU0AkzA9ZgGTjxZLh++zChIDmi FP4GqvYM5KhbjnIBvMltWn7h3bHBK3y4jVm9c17SGqNnshvG3siT124G5ZeLgkt792jL kS3JV61taWaq1WVU3umaVrMApxUcI+0z5TbZXaWruN2RCiIhce9Wc+3I867YJj3aHeX7 /lyMvc/QYQWST6NjVb3Zt3yHHipa78TfGsy4KEGGoYzzeweB5SP6kWONPq+9gKEhjPQb XuzQ==
X-Gm-Message-State: AOAM532igtECkkfXGXN50FabMyUUGX+cfsl0mceRPsTg0Qq8MyWnbKU+ aaHFPbQ2VdnvZ+psd9WBOPeihgo2NCJ/S0QTfcmEi1AK
X-Google-Smtp-Source: ABdhPJw3a4iquaeE6EvcJqG4WZvz1LhWZ90T6frXyMySv6A9FQGDSM7BGGHLxEVLjuz306BNLtazq3rPf67kNHnEddk=
X-Received: by 2002:a05:6402:1a55:b0:410:a4b4:2a9d with SMTP id bf21-20020a0564021a5500b00410a4b42a9dmr26270576edb.45.1645530597495; Tue, 22 Feb 2022 03:49:57 -0800 (PST)
MIME-Version: 1.0
References: <CANVfNKqZztkOsfYwmcZGucHn3oZetHyv+8W9x67i8tgVstw8Eg@mail.gmail.com> <CAB75xn7cf_Kzik0as6EWPDcK9WCSzSbZHTcC-r7bZgxtoiO+xw@mail.gmail.com>
In-Reply-To: <CAB75xn7cf_Kzik0as6EWPDcK9WCSzSbZHTcC-r7bZgxtoiO+xw@mail.gmail.com>
From: Mrinmoy Das <mrinmoy.ietf@gmail.com>
Date: Tue, 22 Feb 2022 17:19:46 +0530
Message-ID: <CANVfNKqW8=sRPkm1ERqooNumq6MUtc6CxNSUr93cWRmd0kUxyQ@mail.gmail.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: pce@ietf.org
Content-Type: multipart/alternative; boundary="000000000000bb180005d899f28b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/V7B_dd-tBvTuyF89m3kpO3PfeTo>
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:50:04 -0000

Thanks Dhruv for the clarification.

On Tue, Feb 22, 2022 at 5:17 PM Dhruv Dhody <dhruv.ietf@gmail.com> wrote:

> 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