Hi Erik,
Thank you for the review.
Some quick comments on this part:
> ### S4.1
>
> * "IPv4-converted IPv6 addresses"
>
> As Geoff Huston pointed out, this is not a formal term.
Med: It is defined in RFC6052 and widely used:
IPv4-converted IPv6 addresses: IPv6 addresses used to represent IPv4
nodes in an IPv6 network. They are a variant of IPv4-embedded
IPv6 addresses and follow the format described in Section 2.2.
I
> recommend
> adopting his suggested alternative:
>
> "Authoritative DNS servers SHOULD NOT use IPv4-Compatible IPv6
> Addresses
> and IPv4-Mapped IPv6 Address [RFC4291]".
Med: The authors adopted a variant of this as you can see at
https://github.com/ietf-wg-dnsop/draft-ietf-dnsop-3901bis/pull/66/files.
IPv4-compatible or IPv4-mapped are specific variants of embedded addresses. The
initial guidance is a call to prefer native connectivity and avoid any
translation, including NAT64, etc. NAT64 does not use compatible/mapped
addresses.
NEW:
To avoid reachability issues, authoritative DNS servers SHOULD NOT use
IPv4-embedded addresses [RFC6052] (including IPv4-Mapped IPv6 addresses and
deprecated IPv4-Compatible addresses [RFC4291]) for receiving queries.
Cheers,
Med
> -----Message d'origine-----
> De : Erik Kline via Datatracker <[email protected]>
> Envoyé : mercredi 21 janvier 2026 02:06
> À : The IESG <[email protected]>
> Cc : [email protected]; [email protected]; draft-ietf-dnsop-
> [email protected]; [email protected]
> Objet : Erik Kline's No Objection on draft-ietf-dnsop-3901bis-10:
> (with COMMENT)
>
>
> Erik Kline has entered the following ballot position for
> draft-ietf-dnsop-3901bis-10: No Objection
>
> When responding, please keep the subject line intact and reply to
> all email addresses included in the To and CC lines. (Feel free to
> cut this introductory paragraph, however.)
>
>
> ------------------------------------------------------------------
> COMMENT:
> ------------------------------------------------------------------
>
> # Internet AD comments for draft-ietf-dnsop-3901bis-10
> CC @ekline
>
>
> ## Comments
>
> ### S4.1
>
> * "IPv4-converted IPv6 addresses"
>
> As Geoff Huston pointed out, this is not a formal term. I
> recommend
> adopting his suggested alternative:
>
> "Authoritative DNS servers SHOULD NOT use IPv4-Compatible IPv6
> Addresses
> and IPv4-Mapped IPv6 Address [RFC4291]".
>
> ### S4.2
>
> * Geoff highlights some concerns with recurser forwarding and the
> lack of
> a protocol-based mechanism for loop avoidance or loop
> termination.
>
> One possibility here might be to say that recursers SHOULD NOT
> forward
> to other recursers in the manner described unless the operator
> can be
> sure that no loops can ever formed (the means by which this is
> to be
> done would, of course, be outside the scope of this document).
> Operators
> choosing to employ this kind of recurser forwarding may open
> their
> infrastructure to denial of resource attacks.
>
> ## Nits
>
> ### S1
>
> * If you're going to reach for an early IPv6 RFC then 2460 itself
> was
> replacing 1883 (1998 vs 1995).
>
>
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
