Re: [IPv6] [Last-Call] Artart last call review of draft-ietf-6man-rfc6874bis-02
Michael Sweet <[email protected]>
| Newsgroups | gmane.ietf.apps-discuss,gmane.ietf.ipv6 |
|---|---|
| Message-ID | <[email protected]> |
Brian, > On Mar 26, 2023, at 10:33 PM, Brian E Carpenter <[email protected]> wrote: > ... >> https://datatracker.ietf.org/doc/html/draft-ietf-6man-rfc6874bis#appendix-A <https://datatracker.ietf.org/doc/html/draft-ietf-6man-rfc6874bis#appendix-A> >> It says "Simply use the 'IPvFuture' syntax left open in RFC 3986". >> You could do that, right? But maybe we have an accidental production here. That's fine too. Just say it, if that's the case. > > CUPS, I believe, does use IPvFuture internally, but that has no impact except on CUPS participants. Actually, it isn't just CUPS, it is all AirPrint printers... In practice this isn't an issue since mDNS hostnames are normally used and the backup (but numeric IP addresses) can likewise usually rely on IPv4 addresses assigned via DHCP. But on the off chance that you have an IPv6-only network and mDNS doesn't work, you have a situation where you aren't able to access the printer's web interface (for configuration) because browsers don't support it... :/ ________________________ Michael Sweet