[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipng
Subject:    RE: I-D Action: draft-ietf-6man-ug-00.txt
From:       Christian Huitema <huitema () microsoft ! com>
Date:       2013-03-31 19:31:19
Message-ID: C91E67751B1EFF41B857DE2FE1F68ABA0BFF9C51 () tk5ex14mbxc272 ! redmond ! corp ! microsoft ! com
[Download RAW message or body]

The draft would be a bit easier to read if it announced its purpose immediately, both in the abstract and in the introduction. For example, in the abstract, instead of just stating:

                                                                              This document clarifies
   the status of those bits for interface identifiers that are not
   derived from an IEEE link-layer address, and updates RFC 4291
   accordingly.

You could have written:

                                                                             This document clarifies
  that these  bits only apply to interface identifiers that are explicitly
   derived from an IEEE link-layer address, and updates RFC 4291
   accordingly. 



-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: Friday, March 29, 2013 8:56 AM
To: i-d-announce@ietf.org
Cc: ipv6@ietf.org
Subject: I-D Action: draft-ietf-6man-ug-00.txt


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           : The U and G bits in IPv6 Interface Identifiers
	Author(s)       : Brian Carpenter
                          Sheng Jiang
	Filename        : draft-ietf-6man-ug-00.txt
	Pages           : 9
	Date            : 2013-03-29

Abstract:
   The IPv6 addressing architecture 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
   the status of those bits for interface identifiers that are not
   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-00


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
[prev in list] [next in list] [prev in thread] [next in thread]