Subject: Re: I-D Action: draft-ietf-6man-ug-03.txt]

From: t.petch <[email-masked]>
Date: Thu, 5 Sep 2013 18:21:12 +0100

Brian

Good stuff - I like it as is.

I notice that the references has
   [IEEE802]  , "IEEE Standard for Local and Metropolitan Area Networks:

I wonder if the XML requires a reference to have an author and is going
to put in that first comma regardless; doubtless the RFC editor knows
how to fix it:-)

Tom Petch

----- Original Message -----
From: "Brian E Carpenter" <[email-masked]>
To: "6man" <[email-masked]>
Sent: Monday, August 26, 2013 9:15 PM
Subject: [Fwd: I-D Action: draft-ietf-6man-ug-03.txt]

> Hi,
>
> This version responds to Fernando's review, as discussed in
> http://www.ietf.org/mail-archive/web/ipv6/current/msg18789.html
>
> We did not delete the paragraph in Section 5 as Fernando
> suggested, because we think it's a necessary clarification.
>
>    Brian + Sheng
>
>
> -------- Original Message --------
> Subject: I-D Action: draft-ietf-6man-ug-03.txt
> Date: Mon, 26 Aug 2013 13:03:52 -0700
> From: [email-masked]
> Reply-To: [email-masked]
> To: [email-masked]
> CC: [email-masked]
>
>
> 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           : Significance of IPv6 Interface Identifiers
> Author(s)       : Brian Carpenter
>                           Sheng Jiang
> Filename        : draft-ietf-6man-ug-03.txt
> Pages           : 11
> Date            : 2013-08-26
>
> Abstract:
>    The IPv6 addressing architecture includes a unicast interface
>    identifier that is used in the creation of many IPv6 addresses.
>    Interface identifiers are formed by a variety of methods.  This
>    document clarifies that the bits in an interface identifier have no
>    generic meaning and that the identifier should be treated as an
>    opaque value.  In particular, RFC 4291 defines a method by which
the
>    Universal and Group bits of an IEEE link-layer address are mapped
>    into an IPv6 unicast interface identifier.  This document clarifies
>    that those two bits are significant only in interface identifiers
>    that are derived from an IEEE link-layer address, and updates RFC
>    4291 accordingly.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-ug
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6man-ug-03
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-ug-03
>
>
> Please note that it may take a couple of minutes from the time of
submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [email-masked]
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>