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

Richard Johnson <raj@cisco.com> Wed, 25 March 2009 19:13 UTC

Return-Path: <raj@cisco.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 CF7FE3A68D6 for <dhcwg@core3.amsl.com>; Wed, 25 Mar 2009 12:13:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 aQtkSyowh9NM for <dhcwg@core3.amsl.com>; Wed, 25 Mar 2009 12:13:37 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id C6BDB3A68C1 for <dhcwg@ietf.org>; Wed, 25 Mar 2009 12:13:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.38,420,1233532800"; d="scan'208";a="146712215"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-3.cisco.com with ESMTP; 25 Mar 2009 19:14:30 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n2PJEUnb003309; Wed, 25 Mar 2009 12:14:30 -0700
Received: from dhcp-51d5.meeting.ietf.org (sjc-vpn2-337.cisco.com [10.21.113.81]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n2PJEUEf022534; Wed, 25 Mar 2009 19:14:30 GMT
References: <20090311204501.D0D4B28C158@core3.amsl.com> <FDE67292-AC3F-49C2-BBB4-12F67E085D6B@cisco.com> <39C363776A4E8C4A94691D2BD9D1C9A105BB4E0F@XCH-NW-7V2.nw.nos.boeing.com>
Message-Id: <6BB83B63-CC55-47A8-9204-3AF4072F2D4F@cisco.com>
From: Richard Johnson <raj@cisco.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A105BB4E0F@XCH-NW-7V2.nw.nos.boeing.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 25 Mar 2009 12:14:28 -0700
X-Mailer: Apple Mail (2.930.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2801; t=1238008470; x=1238872470; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=raj@cisco.com; z=From:=20Richard=20Johnson=20<raj@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20draft-ietf-dhc-subnet-alloc-0 9.txt=20finished=20with=20WGLC |Sender:=20; bh=Q8XAWFFSOpHyiBymUtMYDNh/30H3ryaNytTvdLjfWpY=; b=hqTYe9dLQROGDguZ+IjYLs2t/uuUKNA3C31JeH4Q7rTRP+SH1FumU61XK5 6YeJXSbx/lc7DESwpOmHyIvb13IRI9LvgfPTWdwo/YK+n+K+5DQOZ9zZMCF7 cc8FTkv+i4;
Authentication-Results: sj-dkim-2; header.From=raj@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
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:13:38 -0000

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.