Re: [mpls] A comment on the TTL in draft-dong-mpls-mna-encaps-00

bruno.decraene@orange.com Thu, 04 August 2022 13:34 UTC

Return-Path: <bruno.decraene@orange.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E7A8C13C536; Thu, 4 Aug 2022 06:34:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eermaUEGDtcM; Thu, 4 Aug 2022 06:34:05 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28ABDC13C51A; Thu, 4 Aug 2022 06:33:45 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr26.francetelecom.fr (ESMTP service) with ESMTPS id 4Lz8nf65Zgz10Zf; Thu, 4 Aug 2022 15:33:42 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1659620022; bh=0XJbPii28Qq7T/eNLS35p5ul7Zu/nmf4ySXzvk8kJ/c=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=mWq8AD3uq6Kz66cWqix8LYnM6n7kHYxBBWGFmL+sQrO+5tbNEwTcoIizh1oIBHNlb 6Tl/frDaKks1ybbx/co/ACz4tPf0eBPFd4vvv5Ehdc7TKZgiMe+xQajQodIJdbGlMh fqsvi1DSVofeqGvd2H2tGSBSHu/IgCGYTScX+Jqr0liXE1TyN4hnyu8PuDOCN+brZ4 vcI2E/0WtosZJBqStDmszeRFpxWZyjh4Zg0sUcm1t6egv1tZ8TWcLn7PTOuno5RS3u oORrlLcnz8Rzc59r8WiWH6LmksJUY+TFUbtGRWOW1PLjVjpgst19CQLhdfw1UNPWEv 85JRI3R/vVzLw==
From: bruno.decraene@orange.com
To: Stewart Bryant <stewart.bryant@gmail.com>, mpls <mpls@ietf.org>
CC: "draft-dong-mpls-mna-encaps@ietf.org" <draft-dong-mpls-mna-encaps@ietf.org>
Thread-Topic: [mpls] A comment on the TTL in draft-dong-mpls-mna-encaps-00
Thread-Index: AQHYqASvapMPjxZUY0W/B/9OwGt6C62euwSw
Date: Thu, 04 Aug 2022 13:33:42 +0000
Message-ID: <21300_1659620022_62EBCAB6_21300_243_3_7737e1098fd84f8899e0804c1e77b75a@orange.com>
References: <39A83D4E-61DC-4750-AE62-1724B93D0400@gmail.com>
In-Reply-To: <39A83D4E-61DC-4750-AE62-1724B93D0400@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Enabled=true; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_SetDate=2022-08-04T13:33:40Z; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Method=Standard; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Name=Orange_restricted_external.2; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_ActionId=6f3e589f-dd88-4ae1-b1b5-8f1f0feb610f; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_ContentBits=2
x-originating-ip: [10.115.26.52]
Content-Type: multipart/alternative; boundary="_000_7737e1098fd84f8899e0804c1e77b75aorangecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/k2Z9SvVS0P8SLjsoRwQNf5lFSfM>
Subject: Re: [mpls] A comment on the TTL in draft-dong-mpls-mna-encaps-00
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2022 13:34:09 -0000




Orange Restricted
From: mpls <mpls-bounces@ietf.org> On Behalf Of Stewart Bryant
Sent: Thursday, August 4, 2022 3:18 PM
To: mpls <mpls@ietf.org>
Cc: draft-dong-mpls-mna-encaps@ietf.org
Subject: [mpls] A comment on the TTL in draft-dong-mpls-mna-encaps-00








3<https://datatracker.ietf.org/doc/html/draft-dong-mpls-mna-encaps#section-3>.  MNA Indicator



   The MNA Indicator is introduced to indicate the presence of any MNA

   information in the packet.  It can be used to indicate the existence

   of MNA actions and the optional associated data in the ISD, or the

   PSD or both.  Since this indicator is generic for all types of MPLS

   network actions, it is reasonable to allocate a basic Special Purpose

   MPLS label (bSPL) for it.  The TC and TTL fields of the MNA Indicator

   are redefined as flags.



   The format of the MNA Indicator is shown as below:



       0                   1                   2                   3

       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      |       MNA Indicator=SPL (TBA)         |H|I|P|S|ISF|    RSV    |

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                  Figure 1. The format of MNA Indicator



   Where:



<snip>





   *  RSV: The rest 6 bits in the original TTL field are reserved for

      future use.  They MUST be set to 0 on transmit and MUST be ignored

      on receipt.

SB> There might be some merit in setting the RSV to 0b111111

SB> Then if some router receiving the SPL predecremented the TTL (not unknown in hardware) the upper bits of the TTL and hence the indicators would be unchanged

[Bruno] May be that would call for setting aside the last bit and always send it to 1. (hence reducing RSV to 5 bits)

[Bruno] Also if PHP is used, the penultimate node may recopy the TTL value from the top label to the SPL, which would erase fields.

[Bruno]  Another comment regarding the TC. If PHP is used, the egress would receive the MNA as top label and may select its CoS treatment based on the TC. So there might be some merit in not overloading this TC field.

[Bruno] In https://www.ietf.org/archive/id/draft-jags-mpls-mna-hdr-01.html#name-overview we intentionally did not repurpose those two fields and explained why.

--Bruno

- Stewart

_________________________________________________________________________________________________________________________

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.