[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#992503: [RFC] [meta][WiP] URL specification with IPv6 zone identifiers



Package: general
Severity: minor
Tags: upstream ipv6
Forwarded: https://github.com/whatwg/url/issues/392

Dear all,

They are some push to change the RFC in order to support browsing to IPV6
address with zone identifier.

It will help some of us to get configuration of industrial appliance.

Link Local addresses (fe80::/10) are used for addressing devices in your local
subnet. They can be automatically generated and using the IPv6 multicast
address ff02::1, all hosts on the local subnet can easily be located.

However browsers like Chrome or Firefox do not support entering link local
addresses inside a URL, which prevents accessing devices locally with a
browser, for instance for configuring them.

Link local addresses need zone identifiers to specify which network device to
use as an outgoing interface. This is because you have link local addresses on
every interface and your network stack does not know on its own, which
interface to use. So typically a link local address is something on the line of
fe80::fae4:e3ff:fee2:37a4%eth0, where eth0 is the zone identifier.

However, I do not know if debian is ready for this for next release so, open a
bug in order to track issue. I suppose we will need also a user tag

Rational and workarround for the time being here
https://ungleich.ch/u/blog/ipv6-link-local-support-in-browsers/

Last draft here
https://www.ietf.org/archive/id/draft-carpenter-6man-rfc6874bis-02.html

Bastien


Reply to: