#1168 closed request (pending)

ietf-nat64 and IPv4 literals

Reported by: brian.e.carpenter@… Owned by: llynch@…
Priority: tbd Milestone: ietf-100
Component: incoming Keywords: ietf-nat64
Cc: My Current Location: Padang
My MAC Address: 88-53-2E-B9-56-22 My OS: Windows 7

Description

This is for the record as it is an expected failure case:

http://[64:ff9b::4206:65ab]/ works well
http://66.6.101.171/ fails utterly (Firefox can’t establish a connection to the server at 66.6.101.171)

See also
https://mailarchive.ietf.org/arch/msg/ipv6/MQH3sNZ9QKHSW0Ipcfvvzp943k0

Change history (1)

comment:1 Changed 11 months ago by panda@…

Resolution: pending
Status: newclosed

Thanks for trying the NAT64 network (SSID ietf-nat64) and reporting your experience. That is an expected behavior but it is worth to file the issue. We’re collecting all the issues that come up and will pass the reports back to the vendor at the end of the week. Hopefully this will lead to better implementations and greater functionality for the next meeting. If you’re curious about other known issues, please see https://tickets.meeting.ietf.org/wiki/nat64

I think this draft(*) is also related, although it is expired.
(*) https://datatracker.ietf.org/doc/draft-osamu-v6ops-ipv4-literal-in-url/

If you have additional input on this issue please update the ticket, if you see new issues please open additional tickets.

Thanks -

Note: See TracTickets for help on using tickets.