Re: [mpls] Shepherd review of draft-ietf-mpls-lspping-norao
Adrian Farrel <adrian@olddog.co.uk> Mon, 06 November 2023 12:35 UTC
Return-Path: <adrian@olddog.co.uk>
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 F3AABC18E183; Mon, 6 Nov 2023 04:35:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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_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=olddog.co.uk
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 w0OJjnZZgY5p; Mon, 6 Nov 2023 04:35:17 -0800 (PST)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 016F2C09BB56; Mon, 6 Nov 2023 04:34:42 -0800 (PST)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta6.iomartmail.com (8.14.7/8.14.7) with ESMTP id 3A6CYecp003176; Mon, 6 Nov 2023 12:34:40 GMT
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id B510B4604B; Mon, 6 Nov 2023 12:34:40 +0000 (GMT)
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 9F7DF4604A; Mon, 6 Nov 2023 12:34:40 +0000 (GMT)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs3.iomartmail.com (Postfix) with ESMTPS; Mon, 6 Nov 2023 12:34:40 +0000 (GMT)
Received: from LAPTOPK7AS653V (dhcp-8a07.meeting.ietf.org [31.133.138.7]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.7/8.14.7) with ESMTP id 3A6CYd4x021172 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 6 Nov 2023 12:34:40 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Greg Mirsky' <gregimirsky@gmail.com>
Cc: mpls@ietf.org, draft-ietf-mpls-lspping-norao.all@ietf.org
References: <019401da0b7b$3a640f90$af2c2eb0$@olddog.co.uk> <CA+RyBmU0-Xe-t6PfUGMwqxUoSMOFmbE+HKG=JMM4WcSaZgKyJQ@mail.gmail.com>
In-Reply-To: <CA+RyBmU0-Xe-t6PfUGMwqxUoSMOFmbE+HKG=JMM4WcSaZgKyJQ@mail.gmail.com>
Date: Mon, 06 Nov 2023 12:34:39 -0000
Organization: Old Dog Consulting
Message-ID: <014f01da10ad$9c9db9e0$d5d92da0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQH0IfmuHgH8jR5HJh4zpiTFpzjd6gIOT872sCiisOA=
X-Originating-IP: 31.133.138.7
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding; s= 20221128; bh=EYkWJsPip14CKOlyt8zOQuayLNpws+eLsSS/FXpTAzM=; b=Xt9 wvJI8IxsRxRJy4Ji48eKIHeNXm/7L51SUnN4vBRx+/sJgzkughWj/2vYI3JLMH2K W9zS4Eueuh42O3gL7K9mtqZ34yyUhGae9hna1t24MoDDydmb12BuHVG4MmybGvmH Y9PTkOvddVnIf7axuanSbk+9JpkCUvAD6FS/gVFyXspcUNKtTwrEFT3QIoefGk81 JJWatOC/jNaIqluPokIk3rcKMCteKxxFxf69c0LYcvsUffB/hZFW0FkzyQk8K8qF keydtl4EQKiV6CYFScWl5EmsksUSiE0mYm4iWCxvinc9CCIoAL8+4q/X/v2nfr6P K9mv3fU85c48sFrqvhg==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-27980.006
X-TM-AS-Result: No--34.861-10.0-31-10
X-imss-scan-details: No--34.861-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-27980.006
X-TMASE-Result: 10--34.861400-10.000000
X-TMASE-MatchedRID: 8HTFlOrbAtHxIbpQ8BhdbC/T1r68E/jWkYC3rjkUXRIvfU/riSJXkZXw t1rkqwjUrCCXG3Lpn8TFmuzTavPkFiUub0G/po3cvHKClHGjjr1rd3Vy8kQ7lW4lvELvVn+GZng ixNorteDuNQDtj0/CtK9odUR5cJBx0uQOgHtFIKp85pjA/x1xfoxYco4GgrCRksXB/WVsecg7d4 F04dq2HP62xyNpn8FQUKQk+0pZpo1aSb0pBpxm6H1JIA4rhsZ/sk61leL8Ml/IgofMgahPra1ip mt4cI0W7z0rdc8Z7avPmMb/Rhk0Ugx5TL3qCTgEyn0GCvk40qESrxWnE1VUicOo7r/xHr1AHYZc jAnJmTj5CjTtz8/YyM+3OUWsTdgWbqtTkpIo69QNmz8qCap2S7TrV2IG143XYjNWMNi9SZqrKtp Yte1evVtu1YqzHJeIpLAJnNiNmxrHQ6AkMehNoRfqkKQlk1I5WmOfr3aLpwjZy7cO2aY0Q/mern eLrf1/YBA+EGmViA4e/zLOc+2C2h2P280ZiGmR9k5nZzZVBSD6DHtjrOvoOTnZfxjBVQRb3kUs9 G0YRzFNSvMUvTZEo0OLAa6uLyZA1ZganTi7yViz8d6zvo5NkBhBgVDb4fBgMZC3ZFuwuaptzRhG hF5pwMRavgnETVO2zpKgTpsbDRMIR4rOO9eFEzLRY601LrakWaKvOaBFthQr8ogo/U2yX+BwlzW EEXt27uyigFv229rXvaPmtupi+juZPz8QQL7+C8FMH3T6F77OhLimqQauQ4g/y3JYxGR5oBk/WX 7bU8ck5K3+y8iskqdM0oFOSmNnXHEPHmpuRH2DGx/OQ1GV8is3zPQeiEbe+gtHj7OwNO2FR9Hau 8GO7qfDnZdVcKQklExlQIQeRG0=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/tEvNdOGVI1-TT52lpjAMZ2W-2V8>
Subject: Re: [mpls] Shepherd review of draft-ietf-mpls-lspping-norao
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: Mon, 06 Nov 2023 12:35:25 -0000
Greg, This is all looking good. Thanks for the work. In section 4, You are missing an “END” to delimit the change from OLD to NEW (i.e., OLD—NEW—END). I think that comes before “Additionally, this specification updates Section 2.2 of [RFC8029]” Please post the update and I will start on the shepherd write-up. Best, Adrian From: Greg Mirsky <gregimirsky@gmail.com> Sent: Monday, November 6, 2023 9:29 AM To: adrian@olddog.co.uk Cc: mpls@ietf.org; draft-ietf-mpls-lspping-norao.all@ietf.org Subject: Re: Shepherd review of draft-ietf-mpls-lspping-norao Hi Adrian, I've got to really appreciate the thoroughness of your review and clear and constructive suggestions. Attached, please find the working version (all your suggestions were accepted with a few minor editorial nits). A bit frustrating that gmail finds a virus in the diff and thus I am not attaching it this time. Please let me know if I've got the updates right, and will gladly upload the new version of the document. Also, I've noticed that idnits reports the following concern: -- The abstract seems to indicate that this document updates RFC6398, but the header doesn't have an 'Updates:' line to match this. I've checked it, and it looks like some misunderstanding of the tool. WDYT? Regards, Greg On Mon, Oct 30, 2023 at 10:51 PM Adrian Farrel <mailto:adrian@olddog.co.uk> wrote: Hi, Here is my review as document shepherd. Sorry that this is me doing yet another review, but this time there is a whole new layer of pedantry as we get the document ready for publication. All of my changes are editorial - no technical comments. Let me know if there are any concerns. Cheers, Adrian === Abstract OLD Therefore, this document removes the RAO from LSP ping message encapsulations. It updates RFCs 7506 and 8029. NEW Therefore, this document retires the Router Alert Option for MPLS Operations, Administration, and Maintenance (OAM). It reclassifies RFC 7506 as Historic and updates RFC 8029 to remove the RAO from LSP ping message encapsulations. END --- Abstract This document also recommends the use of an IPv6 loopback address (::1/128) and discourages the use of an IPv4 loopback address mapped to IPv6. I think that "discourages" may be underplaying what is going on. Don't you actually update 8029 to describe new rules for selecting an IPv6 address? So, perhaps, This document also recommends the use of an IPv6 loopback address (::1/128) and not the use of an IPv4 loopback address mapped to IPv6. --- Need to expand FEC on first use. --- Introduction I'm a little worried that the text that describes how 8029 uses RAO is too strong. In particular, the Introduction says "must include an RAO" which will be confusing for the reader. So, a suggestion... OLD The IP header that encapsulates an MPLS echo request message must include a Router Alert Option (RAO), while the IP header that encapsulates an MPLS echo reply message must include an RAO if the value of the Reply Mode in the corresponding MPLS echo request message is "Reply via an IPv4/IPv6 UDP packet with Router Alert". NEW According to RFC 8029, the IP header that encapsulates an MPLS echo request message must include a Router Alert Option (RAO), while RFC 8029 also says that the IP header that encapsulates an MPLS echo reply message must include an RAO if the value of the Reply Mode in the corresponding MPLS echo request message is "Reply via an IPv4/IPv6 UDP packet with Router Alert". END --- Introduction OLD Therefore, this document removes the RAO from both LSP ping message encapsulations. It updates RFCs 7506 [RFC7506] and 8029 [RFC8029]. NEW Therefore, this document updates RFC 8026 to retire the RAO from both LSP ping message encapsulations and reclassifies RFC 7506 as Historic. END --- You don't need section 1.2 as all three abbreviations are already expanded in the introduction. --- 2.1 s/(LSR).To/(LSR). To/ --- 2.1 The authors are not aware of any implementation that relies on the RAO to prevent packets from being forwarded beyond the egress LSR. I don't think we can have WG consensus on what the authors are or are not aware of. How about changing this to: No implementation that rely on the RAO to prevent packets from being forwarded beyond the egress LSR have been reported to the MPLS working group. Similarly in 2.2 OLD The authors are not aware of any implementations of mode 3. NEW No implementations of mode 3 have been reported to the MPLS working group. END --- 2.2 s/mode 3 are removed/mode 3 is removed/ --- 4. This needs a little more clarity on exactly what change is made to RFC 8029. So, maybe... OLD Considering that this specification updates Section 2.1 of [RFC8029] regarding the selection of an IPv6 destination address for an MPLS echo request message: * For IPv6, the IPv6 loopback address ::1/128 SHOULD be used. * The sender of an MPLS echo request MAY select the IPv6 destination address from the 0:0:0:0:0:FFFF:7F00/104 range. * To exercise all paths in an ECMP environment, the entropy other than the IP destination address SHOULD be used. NEW Considering that, this specification updates Section 2.1 of [RFC8029] regarding the selection of an IPv6 destination address for an MPLS echo request message as follows: OLD The 127/8 range for IPv4 and that same range embedded in an IPv4-mapped IPv6 address for IPv6 was chosen for a number of reasons. RFC 1122 allocates the 127/8 as the "Internal host loopback address" and states: "Addresses of this form MUST NOT appear outside a host." Thus, the default behavior of hosts is to discard such packets. This helps to ensure that if a diagnostic packet is misdirected to a host, it will be silently discarded. RFC 1812 [RFC1812] states: A router SHOULD NOT forward, except over a loopback interface, any packet that has a destination address on network 127. A router MAY have a switch that allows the network manager to disable these checks. If such a switch is provided, it MUST default to performing the checks. This helps to ensure that diagnostic packets are never IP forwarded. The 127/8 address range provides 16M addresses allowing wide flexibility in varying addresses to exercise ECMP paths. Finally, as an implementation optimization, the 127/8 range provides an easy means of identifying possible LSP packets. NEW The 127/8 range for IPv4 was chosen for a number of reasons. RFC 1122 allocates the 127/8 as the "Internal host loopback address" and states: "Addresses of this form MUST NOT appear outside a host." Thus, the default behavior of hosts is to discard such packets. This helps to ensure that if a diagnostic packet is misdirected to a host, it will be silently discarded. RFC 1812 [RFC1812] states: A router SHOULD NOT forward, except over a loopback interface, any packet that has a destination address on network 127. A router MAY have a switch that allows the network manager to disable these checks. If such a switch is provided, it MUST default to performing the checks. This helps to ensure that diagnostic packets are never IP forwarded. The 127/8 address range provides 16M addresses allowing wide flexibility in varying addresses to exercise ECMP paths. Finally, as an implementation optimization, the 127/8 range provides an easy means of identifying possible LSP packets. The IPv6 destination address for an MPLS echo request message is selected as follows: * For IPv6, the IPv6 loopback address ::1/128 SHOULD be used. * The sender of an MPLS echo request MAY select the IPv6 destination address from the 0:0:0:0:0:FFFF:7F00/104 range. * To exercise all paths in an ECMP environment, the entropy other than the IP destination address SHOULD be used. END END ...and further... OLD LSP Ping implementations SHOULD ignore RAO options when they arrive on incoming MPLS echo request and MPLS echo reply messages. NEW Additionally, this specification updates Section 2.2 of [RFC8029] to replace the whole of the section with the following text: LSP Ping implementations SHOULD ignore RAO options when they arrive on incoming MPLS echo request and MPLS echo reply messages. END --- 5. OLD LSP Ping implementations SHOULD ignore RAO options when they arrive on incoming MPLS echo request and MPLS echo reply messages. This document requests that the IPv6 RAO value for MPLS OAM (69) in [IANA-IPV6-RAO] is marked as "Deprecated". It also requests that the Reply Mode 3 ("Reply via an IPv4/IPv6 UDP packet with Router Alert") in [IANA-LSP-PING] is marked as "Deprecated". We interpret "DEPRECATED" in this context to mean that the deprecated values should not be used in new implementations, and that deployed implementations that use these values continue to work seamlessly. NEW LSP Ping implementations that conform to this specification SHOULD ignore RAO options when they arrive on incoming MPLS echo request and MPLS echo reply messages. However, this will not harm backwards compatibility because other mechanisms will also be in use by all legacy implementations in the messages they send and receive. Section 6 of this document deprecates the IPv6 RAO value for MPLS OAM (69) in [IANA-IPV6-RAO] and the Reply Mode 3 ("Reply via an IPv4/IPv6 UDP packet with Router Alert") in [IANA-LSP-PING]. [RFC8126] offers a formal description of the word "Deprecated". In this context, "Deprecated" means that the deprecated values SHOULD NOT be used in new implementations, and that deployed implementations that already use these values continue to work seamlessly. END --- 6. OLD If this document is approved, mark the IPv6 RAO value of MPLS OAM (69) in [IANA-IPV6-RAO] as "Deprecated". [RFC8126] offers a formal description of the word "Deprecated". Also, mark Reply Mode 3 ("Reply via an IPv4/IPv6 UDP packet with Router Alert") in [IANA-LSP-PING] as "Deprecated". NEW IANA is requested to mark the IPv6 RAO value of MPLS OAM (69) in [IANA-IPV6-RAO] as "Deprecated". IANA is Also requested to mark Reply Mode 3 ("Reply via an IPv4/IPv6 UDP packet with Router Alert") in [IANA-LSP-PING] as "Deprecated". END
- [mpls] Shepherd review of draft-ietf-mpls-lspping… Adrian Farrel
- Re: [mpls] Shepherd review of draft-ietf-mpls-lsp… Greg Mirsky
- Re: [mpls] Shepherd review of draft-ietf-mpls-lsp… Greg Mirsky
- Re: [mpls] Shepherd review of draft-ietf-mpls-lsp… Adrian Farrel
- Re: [mpls] Shepherd review of draft-ietf-mpls-lsp… Adrian Farrel
- Re: [mpls] Shepherd review of draft-ietf-mpls-lsp… Adrian Farrel
- Re: [mpls] Shepherd review of draft-ietf-mpls-lsp… Greg Mirsky