Thank You! :) Regards, Christer > -----Original Message----- > From: Shraddha Hegde <shraddha@xxxxxxxxxxx> > Sent: Monday, 20 January 2025 6.39 > To: Christer Holmberg <christer.holmberg@xxxxxxxxxxxx>; gen-art@xxxxxxxx > Cc: draft-ietf-lsr-flex-algo-bw-con.all@xxxxxxxx; last-call@xxxxxxxx; lsr@xxxxxxxx > Subject: RE: Genart last call review of draft-ietf-lsr-flex-algo-bw-con-17 > > [You don't often get email from shraddha@xxxxxxxxxxx. Learn why this is > important at https://aka.ms/LearnAboutSenderIdentification ] > > Hi Christer, > > Thanks for the review and comments. > Var -18 will address your comments. > > Pls see inline for replies <SH>... > > Rgds > Shraddha > > > Juniper Business Use Only > -----Original Message----- > From: Christer Holmberg via Datatracker <noreply@xxxxxxxx> > Sent: 19 December 2024 19:02 > To: gen-art@xxxxxxxx > Cc: draft-ietf-lsr-flex-algo-bw-con.all@xxxxxxxx; last-call@xxxxxxxx; lsr@xxxxxxxx > Subject: Genart last call review of draft-ietf-lsr-flex-algo-bw-con-17 > > [External Email. Be cautious of content] > > > Reviewer: Christer Holmberg > Review result: Ready with Nits > > I am the assigned Gen-ART reviewer for this draft. The General Area Review > Team (Gen-ART) reviews all IETF documents being processed by the IESG for > the IETF Chair. Please treat these comments just like any other last call > comments. > > For more information, please see the FAQ at > > <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furld > efense.com%2Fv3%2F__https%3A%2F%2Fwiki.ietf.org%2Fen%2Fgroup%2Fg > en%2FGenArtFAQ__%3B!!NEt6yMaO- > gk!Bqlfnq4vKcUN3IbvJA47a5kqceLvU6B6ivItGjRvk9QH6W0SYEAXSh7erf8lN > 1r9w0xaE0aoBy4OK_OM%24&data=05%7C02%7Cchrister.holmberg%40eric > sson.com%7Cbdc450fbc74f41798abf08dd390c6e24%7C92e84cebfbfd47ab > be52080c6b87953f%7C0%7C0%7C638729447750175963%7CUnknown%7 > CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOi > JXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata= > %2BzcSm6iS5tdGIG621HRZwOA1U%2BOQQNNCOXYUFksrNRE%3D&reserve > d=0 >. > > Document: draft-ietf-lsr-flex-algo-bw-con-17 > Reviewer: Christer Holmberg > Review Date: 2024-12-19 > IETF LC End Date: 2024-12-17 > IESG Telechat date: 2025-02-06 > > Summary: I have no technical comments or questions. However, I do have one > editorial question/comment that I'd like the authors to address. > > Major issues: N/A > > Minor issues: N/A > > Nits/editorial comments: > > The "Flex-Algorithm" is used throughout the document, and Section 1 > contains the following sentence: > > "A Flex-Algorithm [RFC9350] is defined as a > set of parameters consisting of calculation-type, metric-type, and a > set of constraints to allow operators to have more control over the > network path computation." > > Is this correct? Isn't that the definition for FAD? Flex-Algorithm is just a > numeric identifier. > > "In this document, we define further > extensions to Flex-Algorithm that will allow operators additional > control over their traffic flows, especially with respect to > bandwidth constraints." > > Similar to the previous comment, in what way is Flex-Algorithm extended, > assuming it is just an identifier? > > <SH> Updating the text as below. > > > Flex-Algorithm [RFC9350] > provides a mechanism to create constrained paths by defining > a set of parameters consisting of > calculation-type, metric-type, and a set of constraints. In > this document, we define further extensions to Flex-Algorithm Definition > (FAD) that > will allow operators additional control over their traffic flows, > especially with respect to bandwidth constraints. > > -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
