IETF Logo Mail Archive

[mpls] [Technical Errata Reported] RFC8663 (8855)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 25 March 2026 12:51 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D11B6D12CFA5; Wed, 25 Mar 2026 05:51:25 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id B7AD5C0004D7; Wed, 25 Mar 2026 05:51:25 -0700 (PDT)
To: xiaohu.xxh@alibaba-inc.com, stewart.bryant@gmail.com, adrian@olddog.co.uk, shassan@cisco.com, wim.henderickx@nokia.com, lizhenbin@huawei.com, james.n.guichard@futurewei.com, ketant.ietf@gmail.com, gunter.van_de_velde@nokia.com, tsaad.net@gmail.com, tony.li@tony.li, adrian@olddog.co.uk
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20260325125125.B7AD5C0004D7@rfcpa.rfc-editor.org>
Date: Wed, 25 Mar 2026 05:51:25 -0700
Message-ID-Hash: NLRSWTW4YRH7KXG3PMAIATJXQ3LTTM5U
X-Message-ID-Hash: NLRSWTW4YRH7KXG3PMAIATJXQ3LTTM5U
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mpls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: technotaz2004@gmail.com, mpls@ietf.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [mpls] [Technical Errata Reported] RFC8663 (8855)
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/5KP8G872xHAJ6gE78VB41e2K454>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Owner: <mailto:mpls-owner@ietf.org>
List-Post: <mailto:mpls@ietf.org>
List-Subscribe: <mailto:mpls-join@ietf.org>
List-Unsubscribe: <mailto:mpls-leave@ietf.org>

The following errata report has been submitted for RFC8663,
"MPLS Segment Routing over IP".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid8855

--------------------------------------
Type: Technical
Reported by: Imtiyaz Mohammad <technotaz2004@gmail.com>

Section: 3.1.1

Original Text
-------------
If the No-PHP (NP) Flag in OSPF or the Persistent (P) 
Flag in IS-IS is clear:

pop the top label
If the No-PHP (NP) Flag in OSPF or the Persistent (P)
Flag in IS-IS is set:




Corrected Text
--------------
If the No-PHP Flag in OSPF (NP) or in IS-IS (P) is clear:

pop the top label
If the No-PHP Flag in OSPF (NP) or in IS-IS (P) is set:



Notes
-----
The original text mentions Persistent flag in the context of IS-IS but persistent flag has nothing to do with PHP operation of the labels. Refer sec 2.1.1. in https://www.rfc-editor.org/rfc/rfc8667.html#name-flags

Instructions:
-------------
This erratum is currently posted as "Reported". (If it is spam, it 
will be removed shortly by the RFC Production Center.) Please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
will log in to change the status and edit the report, if necessary.

--------------------------------------
RFC8663 (draft-ietf-mpls-sr-over-ip-07)
--------------------------------------
Title               : MPLS Segment Routing over IP
Publication Date    : December 2019
Author(s)           : X. Xu, S. Bryant, A. Farrel, S. Hassan, W. Henderickx, Z. Li
Category            : PROPOSED STANDARD
Source              : Multiprotocol Label Switching
Stream              : IETF
Verifying Party     : IESG

v2.46.0 | Report a Bug | By Email | System Status