Stuart,
On 09/08/2012 22:31, Stuart Cheshire wrote:
At the meeting in Vancouver, Dave Thaler made a point that I found
convincing:
Where is the character set for IPv6 zone IDs specified?
RFC 4007 doesn't do so, but can be read to imply ASCII.
draft-ietf-6man-uri-zoneid-02 is explicit that
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 Maintenance Working Group of the IETF.
Title : Processing of IPv6 atomic fragments
Author(s) : Fernando Gont
Filename:
Stuart == Stuart Cheshire chesh...@apple.com writes:
Stuart This argues in support of what Microsoft already did: Encode
Stuart '%' as % 25.
okay.
May a browser process the %-escaped UTF-8 in the interface name for the
purpose of display them?
If it does that, and a user then
(this is just supporting that you say that the parse must be tolerant of
a bare %)
First please solve the mystery of how such a parser can tell whether %251 is
an escaped %1 or an unescaped %251.
IETF IPv6 working group
Call this making sure I'm on the same page as anyone else…
RFC 4941 describes privacy addresses, and RFC 4291 describes an EID based on a
MAC Address. RFC 4862 describes stateless address autoconfiguration, and uses
RFC 4861's duplicate address detection mechanism.
My question is: what happens
On Aug 10, 2012, at 6:17 PM, Fred Baker (fred) wrote:
Is it fair to assume that implementations do DAD and follow (2)?
This is the logical thing that I personally would do..
- Jared
IETF IPv6 working group mailing list
Hi, Fred,
On 08/10/2012 07:17 PM, Fred Baker (fred) wrote:
Call this making sure I'm on the same page as anyone else…
RFC 4941 describes privacy addresses, and RFC 4291 describes an EID
based on a MAC Address. RFC 4862 describes stateless address
autoconfiguration, and uses RFC 4861's
Brian Carpenter writes:
On 09/08/2012 22:31, Stuart Cheshire wrote:
At the meeting in Vancouver, Dave Thaler made a point that I found
convincing:
Where is the character set for IPv6 zone IDs specified?
RFC 4007 doesn't do so, but can be read to imply ASCII.
How? RFC 4007 says:
An
