RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt

"Wes Beebee (wbeebee)" <> Thu, 29 October 2009 13:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3F5E03A6964 for <>; Thu, 29 Oct 2009 06:23:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dVU-xxVTSMGJ for <>; Thu, 29 Oct 2009 06:23:48 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 09E0B3A67D6 for <>; Thu, 29 Oct 2009 06:23:47 -0700 (PDT)
Authentication-Results:; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEABM06UpAZnwN/2dsb2JhbADFCZgUhD0EgWI
X-IronPort-AV: E=Sophos;i="4.44,646,1249257600"; d="scan'208";a="65521179"
Received: from ([]) by with ESMTP; 29 Oct 2009 13:24:03 +0000
Received: from ( []) by (8.13.8/8.14.3) with ESMTP id n9TDO3Zh000570; Thu, 29 Oct 2009 13:24:03 GMT
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.3959); Thu, 29 Oct 2009 09:24:03 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt
Date: Thu, 29 Oct 2009 09:24:02 -0400
Message-ID: <>
In-Reply-To: <>
Thread-Topic: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt
Thread-Index: AcpYGZqOPa4LhbfwRqyZ8jL0QnAK2AAfmXSQ
References: <> <>
From: "Wes Beebee (wbeebee)" <>
To: "Brian E Carpenter" <>, "Brian Haberman" <>
X-OriginalArrivalTime: 29 Oct 2009 13:24:03.0762 (UTC) FILETIME=[1583E120:01CA589B]
Cc:, Bob Hinden <>
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 29 Oct 2009 13:23:49 -0000

> Supported.


> Two comments, however.

> 1. An Updates: 4861 header is required


> 2. Why does it contain the "pre-5378" disclaimer ("This document may
contain material...")?

> If the only issue is that material conributed by Thomas Narten is
included, Thomas could give
> us the OK to use standard boilerplate without the annoying disclaimer.

> Regards
>   Brian Carpenter

To be on the safe side, to clear our employers from potential liability,
we would probably need to get everyone on the contributor and
acknowledgement list (or, more importantly, their employers at the time
of contribution) to agree with the new terms of 5378 in writing before
we could get rid of the pre-5378 disclaimer.

8.  Contributors

   Thomas Narten contributed significant text and provided substantial
   guidance to the production of this document.

9.  Acknowledgements

   Thanks (in alphabetical order) to Adeel Ahmed, Jari Arkko, Ralph
   Droms, Alun Evans, Dave Forster, Prashanth Krishnamurthy, Suresh
   Krishnan, Josh Littlefield, Bert Manfredi, David Miles, Madhu Sudan,
   Jinmei Tatuya, Dave Thaler, Bernie Volz, and Vlad Yasevich for their
   consistent input, ideas and review during the production of this
   document.  The security problem related to an NS message that
   provides one reason for invalidating a part of the on-link definition
   was found by David Miles.  Jinmei Tatuya found the security problem
   to also exist with an RS message.

If we really want to get rid of the pre-5378 disclaimer, the authors can
make an attempt to get all of the appropriate rights from all of the 
people above to give to the Trustees.  Fortunately, many of these people

were employed by Cisco at the time this work was done.  Do you remember
the website of employer/author waivers of 5378 is located?  That would
us a good head start...

- Wes