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 19:15 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 PAA25921; Thu, 30 Aug 2001 15:15:37 -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 PAA08109; Thu, 30 Aug 2001 15:10:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08073 for <dhcwg@ns.ietf.org>; Thu, 30 Aug 2001 15:10:44 -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 PAA25774 for <dhcwg@ietf.org>; Thu, 30 Aug 2001 15:09:24 -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 f7UJAjp01569 for <dhcwg@ietf.org>; Thu, 30 Aug 2001 14:10:45 -0500 (CDT)
Received: from eamrcnt749 (eamrcnt749.exu.ericsson.se [138.85.133.47]) by mr6.exu.ericsson.se (8.11.3/8.11.3) with SMTP id f7UJAjZ14294 for <dhcwg@ietf.org>; Thu, 30 Aug 2001 14:10:45 -0500 (CDT)
Received: FROM eamrcnt761.exu.ericsson.se BY eamrcnt749 ; Thu Aug 30 14:10:45 2001 -0500
Received: by eamrcnt761.exu.ericsson.se with Internet Mail Service (5.5.2653.19) id <P4M9RNF0>; Thu, 30 Aug 2001 14:10:44 -0500
Message-ID: <66F66129A77AD411B76200508B65AC697B34DE@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: Thu, 30 Aug 2001 14:10:42 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C13187.76FEA370"
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

Yeah, in thinking some more about this, perhaps it is better that the relay
doesn't know about prefix lengths (it doesn't really need to) - though it
likely will anyway (because of Router Advertisements, etc).

It also is one more thing that could get misconfigured in some way between
the relay and server, so perhaps best to just let the server deal with it.

Therefore, I would suggest it can either be the prefix (with 0's in the interface
id) or just an address. Since the server knows the prefix lengths, it can find
the appropriate "network" by doing the checks only against the prefix-length
bits. Essentially, only the prefix bits are significant and the remaining bits
are don't care. But, I have no major issue if we want to force it to be just
the prefix (with 0's in the other bits).

- Bernie

-----Original Message-----
From: Ralph Droms [mailto:rdroms@cisco.com]
Sent: Thursday, August 30, 2001 2:05 PM
To: dhcwg@ietf.org
Subject: RE: [dhcwg] Changes to remove "client-link-local-address" from
the DHCPv6 header 


Bernie opined:

>Just to be clear, there are three pieces of information: 
>
>1. The address used to communicate with the relay. 
>2. The link on which the client's packet was received. 
>3. The prefix to be used for address assignment for the client. 
>
>I think 1 is easy and it should just be the IPv6 source address of the Relay-Forw. 
>
>In many cases 2 and 3 are the same but they need not be. I would suggest we solve 
>this by doing the following: 
>
>For 3, the relay should send a prefix and prefix-length. 


For 3, we can either do a variable length length+prefix field or send
a prefix with 0's in the interface-id or just send an address
from the appropriate link and let the server deduce the
prefix (which is what we do in DHCPv4, right?).  I've written up
the third alternative, which is as easy as any.  I'll rewrite
it as soon as someone expresses a preference for one of the
other alternatives or comes up with a different plan.

- Ralph

=====
9.1. Relay-forward message

      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |    msg-type   |                                               |
     +-+-+-+-+-+-+-+-+                                               |
     |                          link-prefix                          |
     |                                                               |
     |                                                               |
     |               |-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
     +-+-+-+-+-+-+-+-+                                               |
     |                                                               |
     |                     client-return-address                     |
     |                                                               |
     |               |-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
     +-+-+-+-+-+-+-+-+                                               |
     .                                                               .
     .            options (variable number and length)   ....        .
     |                                                               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


      msg-type                    RELAY-FORW

      link-prefix                 An address with a prefix that is
                                  assigned to the link from
                                  which the client should be assigned
                                  an address.

      client-return-address       The source address from the IP
                                  datagram in which the message from the
                                  client was received by the relay agent

      options                     MUST include a "Client message
                                  option"; see section 18.7.  The relay
                                  MUST include a "circuit-ID option" if
                                  it needs to explicitly identify the
                                  link on which the client message should
                                  be forwarded to the client


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