Re: [dhcwg] Comments on draft-bajko-pripaddrassign-04 and draft-wu-dhc-port-set-option-00

Ted Lemon <Ted.Lemon@nominum.com> Mon, 30 July 2012 15:47 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9BCB21F863C for <dhcwg@ietfa.amsl.com>; Mon, 30 Jul 2012 08:47:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.55
X-Spam-Level:
X-Spam-Status: No, score=-106.55 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r1WvpP8KG5pu for <dhcwg@ietfa.amsl.com>; Mon, 30 Jul 2012 08:47:47 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id 7A85921F8639 for <dhcwg@ietf.org>; Mon, 30 Jul 2012 08:47:45 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKUBasnI2uffSZVzEmECDBiXixMZaUilwG@postini.com; Mon, 30 Jul 2012 08:47:45 PDT
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 F108B1B8301 for <dhcwg@ietf.org>; Mon, 30 Jul 2012 08:47:39 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id E398919005D; Mon, 30 Jul 2012 08:47:39 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0247.003; Mon, 30 Jul 2012 08:47:39 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Thread-Topic: [dhcwg] Comments on draft-bajko-pripaddrassign-04 and draft-wu-dhc-port-set-option-00
Thread-Index: AQHNbmEm0zGmCzseGkOriWCkNqFILZdCbeGA
Date: Mon, 30 Jul 2012 15:47:39 +0000
Message-ID: <B96405CE-655B-4A9F-9A93-22CE3D9FD13A@nominum.com>
References: <50169CA0.7090500@gmail.com>
In-Reply-To: <50169CA0.7090500@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_B96405CE655B4A9F9A9322CE3D9FD13Anominumcom_"
MIME-Version: 1.0
Cc: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Comments on draft-bajko-pripaddrassign-04 and draft-wu-dhc-port-set-option-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 30 Jul 2012 15:47:47 -0000

On Jul 30, 2012, at 7:39 AM, Tomek Mrugalski wrote:
I like the idea of setting yiaddr to 0.0.0.0 mentioned in draft-bajko.
Draft-wu does not not have this behavior. If the client does not
understand received port set options, it will simply use the whole port
range for a given address. Other A+P clients will suffer.

I think that in the case that the client doesn't support this option, the DHCP server either has to give it an entire IP address, or not configure it at all.

I agree with your other comments—thanks for the thorough review!