Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt

"Gaurav Halwasia (ghalwasi)" <> Fri, 21 September 2012 14:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8221721F885C for <>; Fri, 21 Sep 2012 07:16:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.08
X-Spam-Status: No, score=-10.08 tagged_above=-999 required=5 tests=[AWL=0.519, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id BM1fNLTAhRBm for <>; Fri, 21 Sep 2012 07:16:53 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id E174621F8849 for <>; Fri, 21 Sep 2012 07:16:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=2075; q=dns/txt; s=iport; t=1348237013; x=1349446613; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=BIpARngfM27V63P0uzyiWyTvsT2KwiYH9a6aI1uXp84=; b=HvqgDzNoKOlsK/oVelofess+Bah/S6kKujfkYumCmwU4BdL/7zIqd6Xi Xl6su0FSQG0bGt3E3Adz52ZVNatNiNnqsV7ZCAk5eWGsEzt5v3wRwGy5K ZM18oWj0eCnMtoxTF9aNla31a63fEkS24hXxYAn2khyZ3xrqb71onRt2X 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.80,463,1344211200"; d="scan'208";a="123964187"
Received: from ([]) by with ESMTP; 21 Sep 2012 14:16:42 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id q8LEGg2W023013 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 21 Sep 2012 14:16:42 GMT
Received: from ([]) by ([]) with mapi id 14.02.0298.004; Fri, 21 Sep 2012 09:16:41 -0500
From: "Gaurav Halwasia (ghalwasi)" <>
To: Tim Chown <>, dhc WG <>
Thread-Topic: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt
Thread-Index: Ac2X8ddMOw/OIH/tQHCVi0DiBXN4ZAANXS2AAAD+9gAACmhikA==
Date: Fri, 21 Sep 2012 14:16:41 +0000
Message-ID: <>
References: <> <> <> <EMEW3|54cdd79b989cbc48ef75bbf93b6c9609o8KExs03tjc||>
In-Reply-To: <EMEW3|54cdd79b989cbc48ef75bbf93b6c9609o8KExs03tjc||>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
x-tm-as-product-ver: SMEX-
x-tm-as-result: No--41.511100-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 21 Sep 2012 14:16:53 -0000

Hi Tim,

Thanks for supporting the document.

I think the first text which you referred is mentioned in the "Problem Statement" where in we really don't have a way to find out the link-layer address form the "DHCPv6 message header/options." 

Whereas the next text (section 5) is talking about server extracting it from DHCPv6 message L2 header. Not from the DHCPv6 message/options.

Please let me know if you still find it confusing.


-----Original Message-----
From: [] On Behalf Of Tim Chown
Sent: Friday, September 21, 2012 7:30 PM
To: dhc WG
Subject: Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt


This also has my support.  It would be something we would use in our deployment.

A little nit though...  

The text says:
"Similarly DHCPv6 Relay or Server cannot glean client link-layer address from the contents of DHCPv6 message received."

and then later in Section 5 the text that's been added in the latest version says:
"This specification does not specify the mechanism for DHCPv6 Server to find out link-layer address of the directly connected clients as a DHCP option as it can obtain it directly from the received message."

This seems a bit contradictory - should the first text say "Similarly DHCPv6 Relay or DHCPv6 Server receiving a relayed message cannot glean"...?


On 21 Sep 2012, at 14:31, Simon Hobson <> wrote:

> Looks good to me. Has my support.
> --
> Simon Hobson
> Visit for books by acclaimed 
> author Gladys Hobson. Novels - poetry - short stories - ideal as 
> Christmas stocking fillers. Some available as e-books.
> _______________________________________________
> dhcwg mailing list

dhcwg mailing list