IETF Logo Mail Archive

Re: [savi] WGLC: draft-ietf-savi-dhcp-22

Ted Lemon <mellon@fugue.com> Tue, 22 April 2014 11:41 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: savi@ietfa.amsl.com
Delivered-To: savi@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A67A01A03B4 for <savi@ietfa.amsl.com>; Tue, 22 Apr 2014 04:41:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level:
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S5dFPcHTVLeN for <savi@ietfa.amsl.com>; Tue, 22 Apr 2014 04:41:47 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 1D8631A03A3 for <savi@ietf.org>; Tue, 22 Apr 2014 04:41:47 -0700 (PDT)
Received: from [10.0.10.40] (c-174-62-147-182.hsd1.nh.comcast.net [174.62.147.182]) by toccata.fugue.com (Postfix) with ESMTPSA id 97B612380424; Tue, 22 Apr 2014 07:41:40 -0400 (EDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CF7BFCD2.38EA7%elevyabe@cisco.com>
Date: Tue, 22 Apr 2014 07:41:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <52D2BDC7-9E55-43BC-8248-23C43DCDEF96@fugue.com>
References: <CF7BFCD2.38EA7%elevyabe@cisco.com>
To: "Eric Levy- Abegnoli (elevyabe)" <elevyabe@cisco.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/savi/znbLpQWTNncX8Iv97iCBtV5ULr4
X-Mailman-Approved-At: Wed, 23 Apr 2014 03:30:34 -0700
Cc: "draft-ietf-savi-dhcp@tools.ietf.org" <draft-ietf-savi-dhcp@tools.ietf.org>, Jean-Michel Combes <jeanmichel.combes@gmail.com>, SAVI Mailing List <savi@ietf.org>, Guang Yao <yaoguang@cernet.edu.cn>
Subject: Re: [savi] WGLC: draft-ietf-savi-dhcp-22
X-BeenThere: savi@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mailing list for the SAVI working group at IETF <savi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/savi>, <mailto:savi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/savi/>
List-Post: <mailto:savi@ietf.org>
List-Help: <mailto:savi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/savi>, <mailto:savi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 11:41:51 -0000

On Apr 22, 2014, at 5:21 AM, Eric Levy- Abegnoli (elevyabe) <elevyabe@cisco.com> wrote:
> The one thing we cannot impose is to have a
> layer-3 stack/address in every subnet a switch is operating on.

IOW the switch can't have a link-local address per subnet?

> For LeaseQuery, it's a slightly different issue (should not require one
> layer-3 per vlan). It drives quite an operational provisioning complexity:
> configuration, security, etc wise.

Again, if it's a managed switch, it doesn't make sense that you wouldn't want it to have a routable L3 address.   You might want to constrain what L3 address it has, and yes, there are operational ramifications to this.   But are you saying that you aren't managing the switch?

> . It is currently not very common to
> deploy DHCP on access switches when the L2/L3 boundary is one layer up (on
> aggregation/distribution). And I am not talking about the one you have at
> home.

Of course not.   Mine doesn't do leasequery or SAVI.   I was using it as an example of the minimum functionality one might expect in a switch that _does_ do SAVI.

v2.23.0 | Report a Bug | By Email