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
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
Precedence: list

--_000_B96405CE655B4A9F9A9322CE3D9FD13Anominumcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

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 D=
HCP server either has to give it an entire IP address, or not configure it =
at all.

I agree with your other comments=97thanks for the thorough review!


--_000_B96405CE655B4A9F9A9322CE3D9FD13Anominumcom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <F861EC5990DFF141857FD81C8A8B81C2@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Jul 30, 2012, at 7:39 AM, Tomek Mrugalski wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">I
 like the idea of setting yiaddr to 0.0.0.0 mentioned in draft-bajko.<br>
Draft-wu does not not have this behavior. If the client does not<br>
understand received port set options, it will simply use the whole port<br>
range for a given address. Other A&#43;P clients will suffer.</span></block=
quote>
</div>
<br>
<div>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 configur=
e it at all.</div>
<div><br>
</div>
<div>I agree with your other comments=97thanks for the thorough review!</di=
v>
<div><br>
</div>
</body>
</html>

--_000_B96405CE655B4A9F9A9322CE3D9FD13Anominumcom_--