Re: [dhcwg] [netlmm] Request for review ofdraft-xia-netlmm-lma-discovery-01.txt

[Frank Xia <[e-mail]>]

Hi Ted

Let me get another shot.

Please read these text from
http://tools.ietf.org/id/draft-ietf-mip6-hiopt-17.txt

" There can be several ways that the DHCP
server knows the requested home network
information.  For instance, as described in
[I-D.ietf-mip6-radius] and [I-D.ietf-dime-mip6-integrated],
a NAS can learn the information via
RADIUS or Diameter, respectively, during
network access authentication, and the
DHCP relay co-located with the NAS can
transfer it to the DHCP server by using the
DHCP option specified in Section 3.2 and
Section 3.3.  Or the home information
may have been configured statically in
the DHCP server by the  administrator.  "

BR
Frank


----- Original Message ----- 
From: "Ted Lemon" <[e-mail]>
To: "Frank Xia" <[e-mail]>
Cc: "Behcet Sarikaya" <[e-mail]>; "Behcet Sarikaya" 
<[e-mail]>; "dhc WG" <[e-mail]>; <[e-mail]>
Sent: Wednesday, May 06, 2009 6:09 PM
Subject: Re: [dhcwg] [netlmm] Request for review 
ofdraft-xia-netlmm-lma-discovery-01.txt


> On May 6, 2009, at 5:30 PM, Frank Xia wrote:
>> draft-ietf-mip6-hiopt-17.txt defines DHCP options
>> for a mobile node to fetch available HA information
>> from a DHCP server. The information stored in DHCP
>> server is independent from  any AAA facility.
>
> Yes, I know what this draft does, and have some questions about its 
> requirement that the DHCP server store information on behalf of the  relay 
> agent in certain cases.   This seems unnecessarily stateful  given that 
> the relay agent knows the information and could easily send  it along 
> every time rather than relying on the DHCPv6 server to store  it.   But 
> that wasn't my question.   :')
>