Last Call Review of draft-ietf-lsr-ospf-admin-tags-17
review-ietf-lsr-ospf-admin-tags-17-rtgdir-lc-white-2024-04-29-00

Adding RTG-DIR.

Russ' review below.

Internal All Employees

________________________________
From: last-call <last-call-bounces@ietf.org> on behalf of russ@riw.us
<russ@riw.us> Sent: 29 April 2024 16:23 To: rtg-ads@ietf.org <rtg-ads@ietf.org>
Cc: draft-ietf-lsr-ospf-admin-tags.all@ietf.org
<draft-ietf-lsr-ospf-admin-tags.all@ietf.org>; lsr@ietf.org <lsr@ietf.org>;
last-call@ietf.org <last-call@ietf.org> Subject: [Last-Call] RtgDir Last Call
review: draft-ietf-lsr-ospf-admin-tags-17

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://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.ietf.org%2Fen%2Fgroup%2Frtg%2FRtgDir&data=05%7C02%7Cdaniam.henriques%40liquid.tech%7C7b863a75e4fa464cb52808dc6858257d%7C687926120f0e46cbb16afcb82fd80cb1%7C0%7C0%7C638499974997469821%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=%2FhGyeL%2FLJutHA%2BiMzuV7xDVUkHS%2FWBxY7nmdXBTLJXo%3D&reserved=0<https://wiki.ietf.org/en/group/rtg/RtgDir>

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-ietf-lsr-ospf-admin-tags-17
Reviewer: Russ White
Review Date: 29 April 2024
IETF LC End Date:
Intended Status: Standards Track

Summary:

No issues found. This document is ready for publication.

Comments:

This draft is readable, and describes a useful addition to the OSPF
protocol.

Major Issues:

No major issues found.

Minor Issues:

No minor issues found.

--
last-call mailing list
last-call@ietf.org
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Flast-call&data=05%7C02%7Cdaniam.henriques%40liquid.tech%7C7b863a75e4fa464cb52808dc6858257d%7C687926120f0e46cbb16afcb82fd80cb1%7C0%7C0%7C638499974997485931%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=9g%2FPobL9YeTNPv5L7nsWoyZlm4hY3xWCsCIb7qcDLKk%3D&reserved=0<https://www.ietf.org/mailman/listinfo/last-call>
This email disclaimer applies to the original email, all attachments and any
subsequent emails sent by Liquid Telecom. This email contains valuable business
information that is privileged, confidential and/or otherwise protected from
disclosure, intended only for the named person or entity to which it is
addressed. If you are not the intended recipient of this email and you received
this e-mail in error, any review, use, dissemination, distribution, printing or
copying of this e-mail is strictly prohibited and may be unlawful and/or an
infringement of copyright. Please notify us immediately of the error and
permanently delete the email from your system, retaining no copies in any
media. No employee or agent is authorized to conclude any binding agreement on
behalf of Liquid Telecom with another party or give any warranty by email
without the express written confirmation by an authorized representative or a
director of Liquid Telecom. Nothing in this email shall be construed as a
legally binding agreement or warranty or an offer to contract. Liquid Telecom
will not be responsible for any damages suffered by the recipient as a result
of the recipient not taking cognizance of this principle. Liquid Telecom
accepts no liability of whatever nature for any loss, liability, damage or
expense resulting directly or indirectly from the access of any files which are
attached to this message. Any email addressed to Liquid Telecom shall only be
deemed to have been received once receipt is confirmed by Liquid Telecom orally
or in writing. An automated acknowledgment of receipt will not suffice as proof
of receipt by the Liquid Telecom. This email disclaimer shall be governed by
the laws of South Africa.