RE: [dhcwg] Changes to remove "client-link-local-address" from th e DHCPv6 header

"Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> Thu, 30 August 2001 16:57 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21786; Thu, 30 Aug 2001 12:57:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA03645; Thu, 30 Aug 2001 12:56:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA03626 for <dhcwg@ns.ietf.org>; Thu, 30 Aug 2001 12:56:08 -0400 (EDT)
Received: from imr1.ericy.com (imr1.ericy.com [208.237.135.240]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21751 for <dhcwg@ietf.org>; Thu, 30 Aug 2001 12:54:49 -0400 (EDT)
Received: from mr6.exu.ericsson.se (mr6u3.ericy.com [208.237.135.123]) by imr1.ericy.com (8.11.3/8.11.3) with ESMTP id f7UGu9p08449 for <dhcwg@ietf.org>; Thu, 30 Aug 2001 11:56:09 -0500 (CDT)
Received: from eamrcnt747.exu.ericsson.se (eamrcnt747.exu.ericsson.se [138.85.133.37]) by mr6.exu.ericsson.se (8.11.3/8.11.3) with SMTP id f7UGu9O14804 for <dhcwg@ietf.org>; Thu, 30 Aug 2001 11:56:09 -0500 (CDT)
Received: FROM eamrcnt760.exu.ericsson.se BY eamrcnt747.exu.ericsson.se ; Thu Aug 30 11:56:08 2001 -0500
Received: by eamrcnt760.exu.ericsson.se with Internet Mail Service (5.5.2653.19) id <P4MQA2LJ>; Thu, 30 Aug 2001 11:56:08 -0500
Message-ID: <66F66129A77AD411B76200508B65AC697B34DA@eambunt705.ena-east.ericsson.se>
From: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: "'Ted Lemon'" <mellon@nominum.com>
Cc: "'Ralph Droms'" <rdroms@cisco.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] Changes to remove "client-link-local-address" from th e DHCPv6 header
Date: Thu, 30 Aug 2001 11:56:07 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C13174.A99339D0"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org

It does seem to me, based on the DHCPv4 RFC3046 description, that a circuit ID
option would work just fine.

- Bernie

-----Original Message-----
From: Ted Lemon [mailto:mellon@nominum.com]
Sent: Thursday, August 30, 2001 12:22 PM
To: Bernie Volz (EUD)
Cc: 'Ralph Droms'; dhcwg@ietf.org
Subject: Re: [dhcwg] Changes to remove "client-link-local-address" from
th e DHCPv6 header 



> For 2, the relay can either use 3 or provide some other means of
> identifying this information. It may not be an address - it could
> just be an interface id or some other opaque info. So, I suggest
> that for 2, we simply have an "Interface-ID" option which is
> whatever the relay wants it to be. The server should treat it as
> opaque and simply echo it back to the relay. If the relay doesn't
> need it (because the info in (3) is sufficient), it need not provide
> this option.

We've already got two options that handle this - the circuit ID and
the remote ID.   Do we need a third, or is the circuit ID already
serving this purpose?

			       _MelloN_