[RTG-DIR]Re: Rtgdir last call review of draft-ietf-mpls-sr-epe-oam-15
Joel Halpern <jmh.direct@joelhalpern.com> Fri, 14 June 2024 14:28 UTC
Return-Path: <jmh.direct@joelhalpern.com>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2844C14CF0C; Fri, 14 Jun 2024 07:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_ZEN_BLOCKED_OPENDNS=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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 iVyrlbtgQn71; Fri, 14 Jun 2024 07:28:15 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 D65FEC14F71D; Fri, 14 Jun 2024 07:28:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4W11pk1m2nz6G99K; Fri, 14 Jun 2024 07:28:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1718375294; bh=456woSoX35jv3bTuu5aIn9TN//V5RM1F9i9cXfWhHrA=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=G3Ki4GkaEc3qFRdtl7xflvi5wMLhAPWwMf/9gqgAsuhEu96mzJN6QwL4gmQa0jCN3 G4dPPiZ1ryDD9MaedsFO6+X6i9yjMuH3DPJLsDAEfz1neNywResFDbs0v/1UQ49pZa 0hU+Kmc0mgEYlYNvhSy/ZhKnq/fV5hDcX9B38ZSo=
X-Quarantine-ID: <Vn14_M0UIGqe>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.22.41] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4W11ph5NBXz6G7yS; Fri, 14 Jun 2024 07:28:12 -0700 (PDT)
Message-ID: <ac06bedf-4284-482d-a9e7-8a0de3157015@joelhalpern.com>
Date: Fri, 14 Jun 2024 10:28:11 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Shraddha Hegde <shraddha@juniper.net>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>
References: <171510159186.29535.18251469067423385129@ietfa.amsl.com> <CO1PR05MB83147CDA79376C32E27EC80CD5E52@CO1PR05MB8314.namprd05.prod.outlook.com> <d10a5274-dc8d-47c3-88e5-bd0b33bf9af2@joelhalpern.com> <CO1PR05MB83144A6EAB0A463D622E372ED5C12@CO1PR05MB8314.namprd05.prod.outlook.com>
Content-Language: en-US
From: Joel Halpern <jmh.direct@joelhalpern.com>
In-Reply-To: <CO1PR05MB83144A6EAB0A463D622E372ED5C12@CO1PR05MB8314.namprd05.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: 35ZMIJKZIO6W6XA6J5N6IJEMLHGM43NT
X-Message-ID-Hash: 35ZMIJKZIO6W6XA6J5N6IJEMLHGM43NT
X-MailFrom: jmh.direct@joelhalpern.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rtg-dir.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "last-call@ietf.org" <last-call@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, James Guichard <james.n.guichard@futurewei.com>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [RTG-DIR]Re: Rtgdir last call review of draft-ietf-mpls-sr-epe-oam-15
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/HefGL2jxB3Rnu1wUJLl-5ZfAHE0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Owner: <mailto:rtg-dir-owner@ietf.org>
List-Post: <mailto:rtg-dir@ietf.org>
List-Subscribe: <mailto:rtg-dir-join@ietf.org>
List-Unsubscribe: <mailto:rtg-dir-leave@ietf.org>
Thank you. I can live with the change as you have made it. It suffices. Yours, Joel On 6/13/2024 5:24 AM, Shraddha Hegde wrote: > Hi Joel, > > I have updated ver -17 and added adj-type field to the peerAdjSID FEC. > Pls review ver -17. > > Rgds > Shraddha > > > Juniper Business Use Only > -----Original Message----- > From: Joel Halpern <jmh@joelhalpern.com> > Sent: Friday, May 10, 2024 1:27 AM > To: Shraddha Hegde <shraddha@juniper.net>; rtg-dir@ietf.org > Cc: draft-ietf-mpls-sr-epe-oam.all@ietf.org; last-call@ietf.org; mpls@ietf.org > Subject: Re: Rtgdir last call review of draft-ietf-mpls-sr-epe-oam-15 > > [External Email. Be cautious of content] > > > [Resending in case this got lost in the email problems.] > > Thank you Shraddha. In line, marked <jmh></jmh> > > > Yours, > > Joel > > On 5/8/2024 4:54 AM, Shraddha Hegde wrote: >> Hi Joel, >> >> Thank you for the careful review and comments. >> Pls see inline <SH> for responses. >> >> >> Rgds >> Shraddha >> >> >> Juniper Business Use Only >> -----Original Message----- >> From: Joel Halpern via Datatracker <noreply@ietf.org> >> Sent: Tuesday, May 7, 2024 10:37 PM >> To: rtg-dir@ietf.org >> Cc: draft-ietf-mpls-sr-epe-oam.all@ietf.org; last-call@ietf.org; >> mpls@ietf.org >> Subject: Rtgdir last call review of draft-ietf-mpls-sr-epe-oam-15 >> >> [External Email. Be cautious of content] >> >> >> Reviewer: Joel Halpern >> Review result: Not Ready >> >> Hello, >> >> I have been selected as the Routing Directorate reviewer for this >> draft. The Routing Directorate seeks to review all routing or >> routing-related drafts as they pass through IETF last call and IESG >> review, and sometimes on special request. The purpose of the review is >> to provide assistance to the Routing ADs. >> For more information about the Routing Directorate, please see >> https://urldefense.com/v3/__https://wiki.ietf.org/en/group/rtg/RtgDir_ >> _;!!NEt6yMaO-gk!AhctNGPPaKLQ_H79A9RESTF3a29btJzh4iO8NHGpWZzqq9EuPQTv9j >> m2O_41fO-qR1mCgCzII3RUBXYp$ >> >> Although these comments are primarily for the use of the Routing ADs, >> it would be helpful if you could consider them along with any other >> IETF Last Call comments that you receive, and strive to resolve them >> through discussion or by updating the draft. >> >> Document: draft-name-version >> Reviewer: your-name >> Review Date: date >> IETF LC End Date: date-if-known >> Intended Status: copy-from-I-D >> >> Summary: >> I have significant concerns about this document and recommend that the >> Routing ADs discuss these issues further with the authors. >> >> Comments: >> >> I was very pleased with the clarity and readability of the document. >> It lays out the space it is working in, and explains what it does and >> how very well. >> >> Major Issues: >> I have significant concern with the structure of the TLVs in two regards. >> First, the PeerAdj SID Sub-TLV (assigned tbd1 in section 4, defined in >> section 4.1) uses a single code point for IPv4 and IPv6 and >> differentiates by length. Other sub-TLVs for MPLS ping and traceroute >> use different code points for IPv4 and IPv6. Second, all of the >> sub-TLVs defined in section 4 have length codes. Looking at RFC 8029, >> sub-TLVs are defined with fixed lengths and do not have length codes >> embedded in them. While one can argue that this is a bad practice, it >> is the practice, and RFC 8287 follows that practice. It would seem this document should do so as well. >> <SH> The definition of PeerAdjSID was referenced from IGP Adj SID FEC >> definition from Sec 5.3 of RFC 8287. This uses sigle code point for >> IPv4/IPv6 addresses. Similar approach is Used in PeerAdjSID definition >> to keep it consistent. Let me know what you think. > <jmh>From where I sit, given that these sub-TLVs are part of the MPLS PING and Traceroute protocol, alignment with that protocol is more important than aligning with the wire encoding BGP uses. After all, the comparison process inside the router can easily convert between the two representations. In the end whether to leave this as is or align with the rest of the MPLS traceroute and ping protocol is up to the MPLS WG chairs and the responsible AD. > > If the WG already discussed this, pointers to that discussion would seem helpful to those responsible for deciding. > > </jmh> > >> Minor Issues: >> It would be helpful if the document directly referenced RFC 8029 and >> said that 8029 is where the TLVs that can carry these sub-TLVs is >> defined. That should be a normative reference. >> <SH> RFC 8029 is already under normative reference. I'll add text >> explaining RFC 8029 defines main TLVs where these sub-TLVs are >> carried. Thanks for pointing out. > <jmh>Thank you.</jmh> >> >>
- [RTG-DIR]Rtgdir last call review of draft-ietf-mp… Joel Halpern via Datatracker
- [RTG-DIR]Re: Rtgdir last call review of draft-iet… Shraddha Hegde
- [RTG-DIR]Re: Rtgdir last call review of draft-iet… Joel Halpern
- [RTG-DIR]Re: Rtgdir last call review of draft-iet… Shraddha Hegde
- [RTG-DIR]Re: Rtgdir last call review of draft-iet… Joel Halpern