On 22/07/2013 23:41, Bernie Volz (volz) wrote:
> Perhaps you've argued this before, but per rfc 4291, u=1, g=0 is what an IID
> that was formed from a MAC address uses, not u=0. The IEEE mac bits are u=0,
> g=0. In the context below, perhaps best to be clear ... Use IEEE "u" = "g" =
> 0? Or IID "u" = 1 and "g" = 0. (It is also a bit odd that 2nd sentence talks
> about IID into MAC and 4th sentence switches this to MAC into IID, especially
> given last sentence.)
Bernie, you are correct, the phrasing is slightly confused there.
We can correct it.
Brian
>
> 3<http://tools.ietf.org/html/draft-ietf-6man-ug-01#section-3>. Usefulness of
> the U and G Bits
>
>
> Given that the "u" and "g" bits do not have a reliable meaning in an
> IID, it is relevant to consider what usefulness they do have.
>
> If an IID is known or guessed to have been created according to
> RFC<http://tools.ietf.org/html/rfc4291>
> 4291<http://tools.ietf.org/html/rfc4291>, it could be transformed back
> into a MAC address. This can be
> very helpful during operational fault diagnosis. For that reason,
> mapping the IEEE "u" and "g" bits into the IID has operational
> usefulness. However, it should be stressed that "u" = "g" = 0 does
> not prove that an IID was formed from a MAC address; on the contrary,
> it might equally result from another method. With other methods,
> there is no reverse transformation available.
>
>
>
> - Bernie (from iPad)
>
> On Jul 22, 2013, at 6:01 AM, "Liubing (Leo)"
> <[email protected]<mailto:[email protected]>> wrote:
>
> Hi, WG
>
> Support for advancing.
>
> Best regards,
> Bing
>
> -----Original Message-----
> From: [email protected]<mailto:[email protected]>
> [mailto:[email protected]] On Behalf Of
> Bob Hinden
> Sent: Friday, July 19, 2013 6:11 AM
> To: IPv6 IPv6 List
> Cc: Bob Hinden
> Subject: 6MAN WG Last Call: <draft-ietf-6man-ug-01.txt>
>
> All,
>
> This message starts a two week 6MAN Working Group on advancing:
>
> Title : Significance of IPv6 Interface Identifiers
> Author(s) : Brian Carpenter
> Sheng Jiang
> Filename : draft-ietf-6man-ug-01.txt
> Pages : 11
> Date : 2013-05-24
>
> http://tools.ietf.org/html/draft-ietf-6man-ug-01
>
> as a Proposed Standard. Substantive comments and statements of support
> for advancing this document should be directed to the mailing list. Editorial
> suggestions can be sent to the author. This last call will end on 1 August
> 2013.
>
> The chairs would also like to solicit a few people to do a detailed review of
> this document. Please contact the chairs directly.
>
> Regards,
>
> Bob Hinden & Ole Trøan
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [email protected]<mailto:[email protected]>
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [email protected]<mailto:[email protected]>
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>
>
> ------------------------------------------------------------------------
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [email protected]
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
