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

"Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> Wed, 29 August 2001 18:10 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 OAA04875; Wed, 29 Aug 2001 14:10:30 -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 OAA11223; Wed, 29 Aug 2001 14:09:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA11201 for <dhcwg@ns.ietf.org>; Wed, 29 Aug 2001 14:09:30 -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 OAA04786 for <dhcwg@ietf.org>; Wed, 29 Aug 2001 14:08:09 -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 f7TI9Sp29409 for <dhcwg@ietf.org>; Wed, 29 Aug 2001 13:09:28 -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 f7TI9S711383 for <dhcwg@ietf.org>; Wed, 29 Aug 2001 13:09:28 -0500 (CDT)
Received: FROM eamrcnt761.exu.ericsson.se BY eamrcnt747.exu.ericsson.se ; Wed Aug 29 13:09:27 2001 -0500
Received: by eamrcnt761.exu.ericsson.se with Internet Mail Service (5.5.2653.19) id <P4M9PD1A>; Wed, 29 Aug 2001 13:09:27 -0500
Message-ID: <66F66129A77AD411B76200508B65AC697B34C3@eambunt705.ena-east.ericsson.se>
From: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: "'Ralph Droms'" <rdroms@cisco.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] Changes to remove "client-link-local-address" from th e DHCPv6 header
Date: Wed, 29 Aug 2001 13:09:27 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C130B5.BDA49BE0"
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

Please see my other message just sent a few moments ago before making this change.

To answer your specific question, correct. In many cases this probably won't be an issue (at least if you consider the IPv4 case as all we have there is giaddr). Sure, there are some cases where this would be a problem (relay has no global address or address of sufficient scope for the interface) and in those the relay uses the option to carry this information.

But, again, we need to look at the RETURN path and that's why I now think making this an option is a bad idea.

- Bernie

-----Original Message-----
From: Ralph Droms [mailto:rdroms@cisco.com]
Sent: Wednesday, August 29, 2001 1:23 PM
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Changes to remove "client-link-local-address" from
the DHCPv6 header 


Before I make the change, let me make sure I understand your proposal.  If the relay agent does not include the relay-address, the relay agent has to cause the forwarded message to have a source address - an address with the widest scope possible; e.g., a link-local address isn't useful - that is assigned to the interface on which the message was received by the agent from the client.

- Ralph

At 11:49 AM 8/29/2001 -0400, Ted Lemon wrote:

>How about making relay-address an option?   I don't think it will be
>useful in most cases, so it seems like a drag to have it part of the
>fixed header.
>
>                               _MelloN_
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>http://www1.ietf.org/mailman/listinfo/dhcwg


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
http://www1.ietf.org/mailman/listinfo/dhcwg