Re: [dhcwg] Question: in RFC3046 why did Agent Subnet Mask Sub-optiondie

Ralph Droms <rdroms@cisco.com> Mon, 19 March 2007 08:10 UTC

Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTCwc-0001ty-PW; Mon, 19 Mar 2007 04:10:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTCwc-0001ti-BA for dhcwg@ietf.org; Mon, 19 Mar 2007 04:10:18 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTCwa-0006YP-0h for dhcwg@ietf.org; Mon, 19 Mar 2007 04:10:18 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 19 Mar 2007 04:10:17 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l2J8AFMc018591; Mon, 19 Mar 2007 04:10:15 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l2J8AFGd012890; Mon, 19 Mar 2007 08:10:15 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 19 Mar 2007 04:10:15 -0400
Received: from 10.86.242.109 ([10.86.242.109]) by xmb-rtp-211.amer.cisco.com ([64.102.31.118]) via Exchange Front-End Server email.cisco.com ([64.102.31.38]) with Microsoft Exchange Server HTTP-DAV ; Mon, 19 Mar 2007 08:10:15 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Sun, 18 Mar 2007 14:20:46 -0400
Subject: Re: [dhcwg] Question: in RFC3046 why did Agent Subnet Mask Sub-optiondie
From: Ralph Droms <rdroms@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Simon Kelley <simon@thekelleys.org.uk>
Message-ID: <C222FB3E.3DDDC%rdroms@cisco.com>
Thread-Topic: [dhcwg] Question: in RFC3046 why did Agent Subnet Mask Sub-optiondie
Thread-Index: AcdpiiWQY/223NV9Edu0YgARJOT6eg==
In-Reply-To: <498F953B-6422-42A8-9EE2-8ED00F64D1AB@nominum.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 19 Mar 2007 08:10:15.0405 (UTC) FILETIME=[067159D0:01C769FE]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1717; t=1174291815; x=1175155815; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdroms@cisco.com; z=From:=20Ralph=20Droms=20<rdroms@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Question=3A=20in=20RFC3046=20why=20did=20Ag ent=20Subnet=20Mask=0A=20Sub-optiondie |Sender:=20 |To:=20Ted=20Lemon=20<Ted.Lemon@nominum.com>, =20Simon=20Kelley=20<simon@t hekelleys.org.uk>; bh=Hu4dw0i1X3cpo/1jB25k0zOEhPKjEqJUM/Kbe3ah2zs=; b=ZnhtgaDVAHfOivR2MFgvsVXZ5Iummaq5SVFm6q90xKIUuZsrtvsaTEFanQzH5Cl/L4QljjfT GQLOHorupACFHFcvoZQcGEp7UqIC+DCRpqEaJ4m0nyrnBrbIELptaG/o;
Authentication-Results: rtp-dkim-2; header.From=rdroms@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: DHC WG <dhcwg@ietf.org>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Expanding on Ted's theme a little - if we're going to consider extensions to
DHCP that can automate the process of configuring the DHCP server, we ought
to take a little time to consider other, similar extensions and define them
all at once rather than one at a time...

- Ralph


On 3/9/07 2:38 PM, "Ted Lemon" <Ted.Lemon@nominum.com> wrote:

> On Mar 9, 2007, at 4:50 AM, Simon Kelley wrote:
>> This is a very valid question: reading back though the archives, it
>> looks like it's one of the things which was worying Ted Lemon about
>> the
>> netmask sub-option. (I think: Ted can, of course, correct me if I've
>> second-guessed him wrong here.)
> 
> My personal feeling on the relay agent subnet mask issue is that I
> don't see any reason why we shouldn't just specify a list of subnets
> that are valid on the client's link, in the same format as the
> classless static routes option, rather than doing the incomplete
> solution of simply providing a subnet mask that implies a prefix
> based on the relay agent's IP address.   I think that that solution
> has limited utility, and in the single-subnet case providing a CSR-
> like option to specify the one prefix that's valid on the link isn't
> going to add more than three or four bytes as compared to sending
> just the subnet mask.
> 
> I have minimal recollection of the debate over the subnet mask option
> way back when - that's been a very long time ago now.   I don't think
> we could meaningfully use any recollections I have to inform this
> discussion... :'}
> 
> 
> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg