Skip to main content

IETF Last Call Review of draft-ietf-mboned-amt-yang-06
review-ietf-mboned-amt-yang-06-dnsdir-lc-blacka-2026-04-02-00

Request Review of draft-ietf-mboned-amt-yang
Requested revision No specific revision (document currently at 09)
Type IETF Last Call Review
Team DNS Directorate (dnsdir)
Deadline 2026-04-08
Requested 2026-03-25
Authors Yisong Liu , Changwang Lin , Zheng Zhang , Xuesong Geng , Vinod Kumar Nagaraj
I-D last updated 2026-05-08 (Latest revision 2026-04-17)
Completed reviews Yangdoctors Early review of -04 by Robert Wills (diff)
Opsdir IETF Last Call review of -06 by Michael P (diff)
Yangdoctors IETF Last Call review of -06 by Robert Wills (diff)
Genart IETF Last Call review of -07 by Behcet Sarikaya (diff)
Secdir IETF Last Call review of -06 by Mike Ounsworth (diff)
Dnsdir IETF Last Call review of -06 by David Blacka (diff)
Assignment Reviewer David Blacka
State Completed
Request IETF Last Call review on draft-ietf-mboned-amt-yang by DNS Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/dnsdir/HiDVZ6kbNGWZlJdxUTReC2R0hF4
Reviewed revision 06 (document currently at 09)
Result Ready
Completed 2026-04-02
review-ietf-mboned-amt-yang-06-dnsdir-lc-blacka-2026-04-02-00
I'm not able to comment as to whether or not this draft is ready from a YANG
perspective. The amount I don't know about YANG or Automatic Multicast Tunnels
is large.  However, from a DNS perspective, this draft is fine.

This document does mention "DNS" a few times, but this only in reference to the
mechanism defined in RFC 8777 (DNS Reverse IP AMT Discovery.)  The only
relationship to DNS that *this* I-D has is that it has a spot for putting
AMTRELAY resource records into the model.  The representation in the model does
match the resource record description in RFC 8777.

If there is a concern with the use of DNS in AMT discovery, that issue would be
with RFC 8777, not this draft.  Note, that I don't have any concerns with 8777
either.