Re: [mpls] Codepoint for OSPFv3 protocol in SPRING LSP-Ping and LSP-Trace

<> Mon, 09 September 2019 12:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 236DD120047; Mon, 9 Sep 2019 05:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZRJxlexah_QJ; Mon, 9 Sep 2019 05:53:22 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B79C7120154; Mon, 9 Sep 2019 05:53:18 -0700 (PDT)
Received: from (unknown [xx.xx.xx.70]) by (ESMTP service) with ESMTP id 46Rp4F0PGwz10Tn; Mon, 9 Sep 2019 14:53:17 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.92]) by (ESMTP service) with ESMTP id 46Rp4D6c2zzDqZY; Mon, 9 Sep 2019 14:53:16 +0200 (CEST)
Received: from OPEXCAUBM43.corporate.adroot.infra.ftgroup ([fe80::b846:2467:1591:5d9d]) by OPEXCAUBM34.corporate.adroot.infra.ftgroup ([fe80::7873:1668:636f:52c%21]) with mapi id 14.03.0468.000; Mon, 9 Sep 2019 14:53:16 +0200
From: <>
To: "Aissaoui, Mustapha (Nokia - CA/Ottawa)" <>, "" <>, "" <>
CC: "" <>
Thread-Topic: Codepoint for OSPFv3 protocol in SPRING LSP-Ping and LSP-Trace
Thread-Index: AdVIuAQ8AdZ/IKoeQP2RJFvbMTxY5QeVSCgA
Date: Mon, 9 Sep 2019 12:53:16 +0000
Message-ID: <27031_1568033596_5D764B3C_27031_258_1_53C29892C857584299CBF5D05346208A48C03799@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
References: <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A48C03799OPEXCAUBM43corp_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [mpls] Codepoint for OSPFv3 protocol in SPRING LSP-Ping and LSP-Trace
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 09 Sep 2019 12:53:24 -0000

RFC 8287 is a product of the MPLS WG so in the absence of answer on the SPRING mailing list, I'm redirecting the question to the MPLS WG.


From: spring [] On Behalf Of Aissaoui, Mustapha (Nokia - CA/Ottawa)
Sent: Friday, August 2, 2019 12:29 AM
Subject: [spring] Codepoint for OSPFv3 protocol in SPRING LSP-Ping and LSP-Trace

Dear all,
I am not sure if this was discussed during the development of RFC 8287 - "Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs)                         with MPLS Data Planes", but I could not find anything in the SPRING mail archive.

Prefix SID and adjacency SID which are originated in an OSPFv3 instance (IPv4 or IPv6 instance) do not have a protocol ID assigned to them in the Segment ID Sub-TLV, as well as in the Label Stack Sub-TLV of the Downstream Detailed Mapping TLV.

Should we assign the next available IANA codepoint values or was there a rationale for omitting them?



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.