Re: [mpls] A comment on the TTL in draft-dong-mpls-mna-encaps-00
"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 04 August 2022 14:54 UTC
Return-Path: <jie.dong@huawei.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 87D96C157B5A; Thu, 4 Aug 2022 07:54:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 TJFd89qc58vi; Thu, 4 Aug 2022 07:54:04 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1626C14CF01; Thu, 4 Aug 2022 07:54:03 -0700 (PDT)
Received: from fraeml738-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4LzBTQ2ZnSz67PJt; Thu, 4 Aug 2022 22:49:46 +0800 (CST)
Received: from kwepemi500017.china.huawei.com (7.221.188.110) by fraeml738-chm.china.huawei.com (10.206.15.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 4 Aug 2022 16:53:59 +0200
Received: from kwepemi500017.china.huawei.com (7.221.188.110) by kwepemi500017.china.huawei.com (7.221.188.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 4 Aug 2022 22:53:57 +0800
Received: from kwepemi500017.china.huawei.com ([7.221.188.110]) by kwepemi500017.china.huawei.com ([7.221.188.110]) with mapi id 15.01.2375.024; Thu, 4 Aug 2022 22:53:57 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.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: A comment on the TTL in draft-dong-mpls-mna-encaps-00
Thread-Index: AQHYqASqFxFEb1NBUUKKqLrlCPpjoK2ez7mA
Date: Thu, 04 Aug 2022 14:53:57 +0000
Message-ID: <e5f4323f4a1940fc9f020d98cafd1cd3@huawei.com>
References: <39A83D4E-61DC-4750-AE62-1724B93D0400@gmail.com>
In-Reply-To: <39A83D4E-61DC-4750-AE62-1724B93D0400@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.85.131.99]
Content-Type: multipart/alternative; boundary="_000_e5f4323f4a1940fc9f020d98cafd1cd3huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/9ZjIQJtqrM_NAGwJSJLXKJEdVOA>
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 14:54:08 -0000
Hi Stewart, Thanks a lot for your review and comment. I agree the design about the TTL field in the uniform model with PHP needs further consideration, and what you suggested can be one possible approach. While I noticed that in RFC 6790 section 4.4, it says: "a PHP LSR that recognizes the ELI MAY choose to pop the ELI and following label (which should be an entropy label) in addition to popping the tunnel label a PHP LSR "MAY choose to pop the ELI and following label (which should be an entropy label) in addition to popping the tunnel label, provided that doing so doesn't diminish its ability to load balance on the next hop." Maybe some description about the behavior of the PHP LSR on the MNA Indicator could also be considered. Best regards, Jie From: Stewart Bryant [mailto:stewart.bryant@gmail.com] Sent: Thursday, August 4, 2022 9:18 PM To: mpls <mpls@ietf.org> Cc: Stewart Bryant <stewart.bryant@gmail.com>; draft-dong-mpls-mna-encaps@ietf.org Subject: 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 - Stewart
- [mpls] A comment on the TTL in draft-dong-mpls-mn… Stewart Bryant
- Re: [mpls] A comment on the TTL in draft-dong-mpl… bruno.decraene
- Re: [mpls] [EXTERNAL] A comment on the TTL in dra… Alexander Vainshtein
- Re: [mpls] A comment on the TTL in draft-dong-mpl… Dongjie (Jimmy)
- Re: [mpls] A comment on the TTL in draft-dong-mpl… bruno.decraene
- Re: [mpls] [EXTERNAL] A comment on the TTL in dra… Alexander Vainshtein
- Re: [mpls] [EXTERNAL] A comment on the TTL in dra… Alexander Vainshtein