IETF Logo Mail Archive

Re: [dhcwg] I-D Action: draft-ietf-dhc-conn-status-00.txt

Ted Lemon <ted.lemon@nominum.com> Tue, 04 February 2014 14:14 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE3481A00E9 for <dhcwg@ietfa.amsl.com>; Tue, 4 Feb 2014 06:14:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 2Gp1Tzmh8Eab for <dhcwg@ietfa.amsl.com>; Tue, 4 Feb 2014 06:14:50 -0800 (PST)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id 70A291A00EC for <dhcwg@ietf.org>; Tue, 4 Feb 2014 06:14:50 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUvD12uEEQRj9dFP0/yLCVrCB3jWPvCzX@postini.com; Tue, 04 Feb 2014 06:14:50 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id EB8601B831A for <dhcwg@ietf.org>; Tue, 4 Feb 2014 06:14:49 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id D1EB6190052; Tue, 4 Feb 2014 06:14:49 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 4 Feb 2014 06:14:49 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <52F0F3C2.20807@viagenie.ca>
Date: Tue, 04 Feb 2014 09:14:46 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <4B094E1A-431F-4F2B-9004-37D6D12BE8F8@nominum.com>
References: <20140204093611.4914.51694.idtracker@ietfa.amsl.com> <52F0F3C2.20807@viagenie.ca>
To: Simon Perreault <simon.perreault@viagenie.ca>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-conn-status-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 04 Feb 2014 14:14:51 -0000

On Feb 4, 2014, at 9:05 AM, Simon Perreault <simon.perreault@viagenie.ca> wrote:
> This is getting better!

It is, but I still don't understand why this is the right architectural solution.   We already have the DHCPv6 link-layer address relay option.   This allows a DHCPv4/DHCPv6 server to track clients and make allocations centrally in the same way that this proposal allows it to happen on relays.   From a management perspective, and from a relay complexity perspective, doing it on the server seems like a win.

Can you guys speak to this question?

v2.23.0 | Report a Bug | By Email