On 20/10/2009, at 5:23 AM, Ron Broersma wrote:
On Oct 12, 2009, at 6:01 AM, Tim Chown wrote:
Every so often you stumble into another missing IPv6 feature in
MacOSX.
I discovered recently that while I can happily print from Windows to
my HP Laserjet P2055dn via IPv6, I can't do so from my Mac.
Kudos to
HP though.
Concur with "Kudos to HP". We like their IPv6 support in newer
printers, and in the new jetdirect cards.
But we had the same problem with getting MacOSX talking to our IPv6-
enabled HP printers. When configuring the new printer in MacOSX,
it will not take an IPv6 address. We filed a bug report with Apple
and their response was that this was not a bug, and was by design.
You can only configure a NAME of the printer, not the IPv6
address. So, you need to register it in DNS with a AAAA record,
then configure the printer using the name instead of the address,
and MacOSX will then happily talk to it.
That's interesting. My understanding is that a link-local address
should NOT have a DNS record, so if the printer only has a link-
local address, then there should not be a DNS entry for it. So what
is one to do? Of course, there SHOULD be a mDNS entry---the correct
way to handle local names. Does the HP printer not support mDNS? I
thought the newer ones did.
The second thing is that surely any sane name resolver is NOT hard
coded to parse names or IP addresses, but calls standard systems
calls that Do The Right Thing---as per RFC 2133 of April 1977. In C:
getaddrinfo. In Cocoa: NSURL, which understands RFC 2732 (so the
Class documentation says).
The NSURL class provides a way to manipulate URLs and the resources
they reference. NSURL objects understand URLs as specified in RFCs
1808, 1738, and 2732.
And per RFC 2732
2. Literal IPv6 Address Format in URL's Syntax
To use a literal IPv6 address in a URL, the literal address
should be
enclosed in "[" and "]" characters. For example the following
literal IPv6 addresses:
FEDC:BA98:7654:3210:FEDC:BA98:7654:3210
1080:0:0:0:8:800:200C:4171
3ffe:2a00:100:7031::1
1080::8:800:200C:417A
::192.9.5.5
::FFFF:129.144.52.38
2010:836B:4179::836B:4179
would be represented as in the following example URLs:
http://[FEDC:BA98:7654:3210:FEDC:BA98:7654:3210]:80/index.html
http://[1080:0:0:0:8:800:200C:417A]/index.html
http://[3ffe:2a00:100:7031::1]
http://[1080::8:800:200C:417A]/foo
http://[::192.9.5.5]/ipng
http://[::FFFF:129.144.52.38]:80/index.html
http://[2010:836B:4179::836B:4179]
so if it doesn't accept that as a name, I'd class it as a genuine bug.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Ipv6-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
