Well, if you want the line ID field to hold a string, to do the right
thing, one probably needs to:
1) make the field be a UTF-8 string
2) have the string contain normalized unicode, so that the "string"
entered on one device correctly matches the "string" entered on the
server (which won't alway
Support, and agreed very useful to avoid conflicts for users.
-Original Message-
From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On Behalf Of Shishio
Tsuchiya
Sent: Wednesday, November 30, 2011 11:22 AM
To: br...@innovationslab.net
Cc: 6man-cha...@tools.ietf.org; ipv6@ietf.or
Sorry for jump to this discussion thread late.
The route policy shall be well considered by the operator/network. If we
discuss confliction, it is more like to be the network configuration that
may appear for MIF host rather than the mechanism of DHCPv6 or RA. Even we
only use RIO, the confliction
Support!
Thank you for this document.
This is understandable/useful guide line to avoid conflict for users.
Regards,
-Shishio
(2011/11/30 0:51), Brian Haberman wrote:
> All,
> This message starts a two week 6MAN Working Group on advancing:
>
> Title : RFC3627 to Historic status
> Author(s) : Wes
Brian Haberman wrote
> This message starts a two week 6MAN Working Group on advancing:
>
> Title : RFC3627 to Historic status
:
> as Informational. Substantive comments and statements of support for
> advancing this document should be directed to the mailing list.
Support.
-
Matsu
Support.
-as
On 29 Nov 2011, at 13:51, Brian Haberman wrote:
> All,
> This message starts a two week 6MAN Working Group on advancing:
>
> Title : RFC3627 to Historic status
> Author(s) : Wesley George
> Filename : draft-ietf-6man-3627-historic-00.txt
> Pages : 4
> Date
* Brian Haberman
> This message starts a two week 6MAN Working Group on advancing:
>
> Title : RFC3627 to Historic status
> Author(s) : Wesley George
> Filename : draft-ietf-6man-3627-historic-00.txt
> Pages : 4
> Date : 2011-11-28
>
> as Informational. Substantive comments a
