Re: [dhcwg] draft-ietf-dhc-subnet-alloc-09.txt finished with WGLC

"Templin, Fred L" <Fred.L.Templin@boeing.com> Wed, 25 March 2009 19:58 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D129B3A6D85 for <dhcwg@core3.amsl.com>; Wed, 25 Mar 2009 12:58:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.341
X-Spam-Level:
X-Spam-Status: No, score=-6.341 tagged_above=-999 required=5 tests=[AWL=0.258, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zXGQVLvTqpfQ for <dhcwg@core3.amsl.com>; Wed, 25 Mar 2009 12:58:39 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id D57153A68AB for <dhcwg@ietf.org>; Wed, 25 Mar 2009 12:58:39 -0700 (PDT)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n2PJxMSD007991 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 25 Mar 2009 12:59:23 -0700 (PDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n2PJxMj5025094; Wed, 25 Mar 2009 12:59:22 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n2PJxL0r025080; Wed, 25 Mar 2009 12:59:22 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 25 Mar 2009 12:59:20 -0700
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
Date: Wed, 25 Mar 2009 12:59:18 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A105BB4F5E@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <6BB83B63-CC55-47A8-9204-3AF4072F2D4F@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dhcwg] draft-ietf-dhc-subnet-alloc-09.txt finished with WGLC
Thread-Index: Acmtfe7juaKjOReZScW7V0SAZC91kwABgo4A
References: <20090311204501.D0D4B28C158@core3.amsl.com> <FDE67292-AC3F-49C2-BBB4-12F67E085D6B@cisco.com> <39C363776A4E8C4A94691D2BD9D1C9A105BB4E0F@XCH-NW-7V2.nw.nos.boeing.com> <6BB83B63-CC55-47A8-9204-3AF4072F2D4F@cisco.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Richard Johnson <raj@cisco.com>
X-OriginalArrivalTime: 25 Mar 2009 19:59:20.0868 (UTC) FILETIME=[2FF58E40:01C9AD84]
Cc: dhcwg@ietf.org, dhc Chairs <dhc-chairs@tools.ietf.org>, draft-ietf-dhc-subnet-alloc@tools.ietf.org
Subject: Re: [dhcwg] draft-ietf-dhc-subnet-alloc-09.txt finished with WGLC
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Mar 2009 19:58:40 -0000

Richard,

I like the spirit of what you are saying; if the lawyers
agreed, that would make me feel even better. But, I don't
think any of this should hold up publication - any other
opinions?

Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Richard Johnson [mailto:raj@cisco.com]
> Sent: Wednesday, March 25, 2009 12:14 PM
> To: Templin, Fred L
> Cc: dhcwg@ietf.org; dhc Chairs;
draft-ietf-dhc-subnet-alloc@tools.ietf.org
> Subject: Re: [dhcwg] draft-ietf-dhc-subnet-alloc-09.txt finished with
WGLC
> 
> The IPR for this is the same as the standard Cisco IPR; basically,
> "don't sue us and we won't sue you" is my understanding, and it's
> always been that way.  I could contact our Cisco lawyers and have then
> try to clarify it more, if that would help.
> 
> /raj
> 
> 
> On Mar 25, 2009, at 10:32 AM, Templin, Fred L wrote:
> 
> > AFAICT, the IPR will still be there whether/not this
> > document actually publishes as an RFC. I would still
> > appreciate clarification on the IPR, but I cannot see
> > that holding up publication - does anyone else see it
> > differently?
> >
> > Fred
> > fred.l.templin@boeing.com
> >
> >> -----Original Message-----
> >> From: Richard Johnson [mailto:raj@cisco.com]
> >> Sent: Tuesday, March 24, 2009 3:38 PM
> >> To: dhcwg@ietf.org WG
> >> Cc: dhc Chairs; draft-ietf-dhc-subnet-alloc@tools.ietf.org
> >> Subject: [dhcwg] draft-ietf-dhc-subnet-alloc-09.txt finished with
> >> WGLC
> >>
> >> Unless I'm missing something, the Subnet Allocation draft has been
> >> through WG LC at least 3 times and with this last revision, this
last
> >> time actually received sufficient reviews that I think we can call
it
> >> done and *finally* move on?
> >>
> >> /raj
> >>
> >>
> >> Begin forwarded message:
> >>
> >>> From: Internet-Drafts@ietf.org
> >>> Date: March 11, 2009 1:45:01 PM PDT
> >>> To: i-d-announce@ietf.org
> >>> Cc: dhcwg@ietf.org
> >>> Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-subnet-alloc-09.txt
> >>> Sender: dhcwg-bounces@ietf.org
> >>>
> >>> A New Internet-Draft is available from the on-line Internet-Drafts
> >>> directories.
> >>> This draft is a work item of the Dynamic Host Configuration
Working
> >>> Group of the IETF.
> >>>
> >>> 	Title		: Subnet Allocation Option
> >>> 	Author(s)	: R. Johnson, J. Kumarasamy, K. Kinnear, M.
> > Stapp
> >>> 	Filename	: draft-ietf-dhc-subnet-alloc-09.txt
> >>> 	Pages		: 32
> >>> 	Date		: 2009-3-11
> >>>
> >>> This document defines a new DHCP option which is passed between
the
> >>>  DHCP Client and the DHCP Server to request dynamic allocation of
a
> >>>  subnet, give specifications of subnet(s) allocated, and report
> > usage
> >>>  statistics.  This memo documents the current usage of the option
> > in
> >>>  agreement with [RFC3942], which declares that any pre-existing
> >>> usages
> >>>  of option numbers in the range 128 - 223 should be documented and
> >>> the
> >>>  working group will try to officially assign those numbers to
those
> >>>  options.
> >>>
> >>> A URL for this Internet-Draft is:
> >>>
> >
http://www.ietf.org/internet-drafts/draft-ietf-dhc-subnet-alloc-09.txt
> >>>
> >>> Internet-Drafts are also available by anonymous FTP at:
> >>> ftp://ftp.ietf.org/internet-drafts/
> >>>
> >>> Below is the data which will enable a MIME compliant mail reader
> >>> implementation to automatically retrieve the ASCII version of the
> >>> Internet-Draft.