[IPP] Support for IPv6 addresses with Scope ID's and what ?was? IPvFuture addresses?

[Christopher Rizzo]

Not sure if this is out of the scope of IPP PWG, but Apple AirPrint has requirements for support of IPv6 addressing that does not appear to be in any standards.

For example, the following is an ?IPvFuture? IPv6 address (note the "v1." on the front):


ipps://[v1.fd3f:7b2c:b134:364b::abcd]:443/.

Only reference I can find about this: https://datatracker.ietf.org/doc/draft-sweet-uri-zoneid/

Does it make sense that this format IPv6 address be required to be supported by a printer as this does not appear to be any part of an approved standard?

Also, there is the issue of Scope (or Zone?) ID's: the addition of "%X" on the end of an IPv6 address where X is a reference to the local client interface.  According to what I read, the scope id is only relevant for the local machine and helps identify which interface the client request goes out on, and it should be removed by the client before communicating on the network, so why would there be a requirement that a printer IPP or HTTP daemon/server comprehend IPv6 addresses with a scope id appended?

References:
RFC 6874<https://datatracker.ietf.org/doc/html/rfc6874> obsoleted by RFC 9844<https://datatracker.ietf.org/doc/rfc9844/>

"It should be noted that zone identifiers have
   purely local meaning within the node in which they are defined,
   usually being the same as IPv6 interface names.  They are completely
   meaningless for any other node."


Thanks,
Chris

Christopher Rizzo
Engineer II, Software Engineering
Design & Development Engineering

[signature_3469743175]<http://www.xerox.com/>

Xerox Corporation
Virtual Office Employee
26600 SW Parkway Ave
Wilsonville, OR 97070

[signature_3903628068]<https://www.linkedin.com/company/xerox/>   [signature_410573172] <https://www.youtube.com/user/XeroxCorp>    [signature_3697375908] <https://twitter.com/Xerox>    [signature_12220815] <https://www.instagram.com/xerox/>    [signature_231343901] <https://www.facebook.com/XeroxCorp>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20251104/c3b92b16/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 9065 bytes
Desc: image001.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20251104/c3b92b16/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1409 bytes
Desc: image002.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20251104/c3b92b16/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1427 bytes
Desc: image003.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20251104/c3b92b16/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1528 bytes
Desc: image004.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20251104/c3b92b16/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 1648 bytes
Desc: image005.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20251104/c3b92b16/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 1456 bytes
Desc: image006.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20251104/c3b92b16/attachment-0005.png>