Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home Information Discovery inMIPv6
Vijay Devarapalli <vijay.devarapalli@azairenet.com> Thu, 22 June 2006 18:17 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtTjg-0005f1-AO; Thu, 22 Jun 2006 14:17:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtAvK-0007T7-CJ; Wed, 21 Jun 2006 18:11:46 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtAvJ-0003aW-RC; Wed, 21 Jun 2006 18:11:46 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Jun 2006 15:11:44 -0700
Message-ID: <4499C3AE.1030903@azairenet.com>
Date: Wed, 21 Jun 2006 15:09:50 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Debian Thunderbird 1.0.2 (X11/20060423)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@yegin.org>
Subject: Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home Information Discovery inMIPv6
References: <0MKoyl-1FtAYX2m3k-0000p1@mrelay.perfora.net>
In-Reply-To: <0MKoyl-1FtAYX2m3k-0000p1@mrelay.perfora.net>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Jun 2006 22:11:44.0930 (UTC) FILETIME=[AE993820:01C6957F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b8f3559805f7873076212d6f63ee803e
X-Mailman-Approved-At: Thu, 22 Jun 2006 14:16:13 -0400
Cc: mip6@ietf.org, 'Heejin Jang' <heejin.jang@samsung.com>, dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org
Alper Yegin wrote: > Gerardo, > > I think it helps to understand the components of the full picture. > > [a] Delivery of the info from home AAA to the NAS > [b] Delivery of the info from the NAS (DHCP relay) to the DHCP server. > [c] Delivery of the info from the DHCP server to the DHCP client > [d] Plumbing of all these components > > > [a], [b], and [c] are all protocol work. [d] is just informational. > > The document draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt covers [b] > and [d]. section 3.6 and 3.7 of draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt seem to describe [c]. Vijay > > WiMAX does not use [b]. For that there is no need to have a normative > reference to draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt. It could > have an informative reference to it, but it does not have to. > > Alper > > > > > > > >>-----Original Message----- >>From: Gerardo Giaretta [mailto:gerardo.giaretta@gmail.com] >>Sent: Wednesday, June 21, 2006 1:18 AM >>To: Alper Yegin >>Cc: Vijay Devarapalli; mip6@ietf.org; Heejin Jang; dhcwg@ietf.org >>Subject: Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home Information >>Discovery inMIPv6 >> >>Alper, >> >>just one question below in order to understand if there is a real >>technical reason to keep the docs separated.. >> >> >>>>>But I hope this data point helps: WiMAX Forum NWG architecture is >> >>using >> >>>>>draft-jang. >>>> >>>>in what context and how are they planning to use it? >>> >>>The MIP info is brought to the DHCP server via RADIUS and delivered to >> >>the >> >>>MN via DHCP. >>> >> >>Can you please explain which are the technical differences between the >>solution in the DT draft for integrated scenario and the solution >>developped in WiMAX? >> >>I guess in WiMAX MIP info are brought to DHCP relay (i.e. NAS) and >>then draft-jang is applied. Is this really different from what is >>described in the DT draft? >> >>--Gerardo >> >> >>>>the >>>>WiMAX forum NWG can still use the DHCP options wherever >>>>they are defined. >>> >>>Yes. And WiMAX Forum could also use it even if IETF had concatenated all >> >>of >> >>>the RFCs and I-Ds under a single document too.... This I-D being >> >>referenced >> >>>whereas the draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt wasn't >> >>is a >> >>>solid proof that the former I-D is useful without having to be >> >>integrated >> >>>into the latter. >>> >>> >>> >>>>>>the only other mechanism is to manually >>>>>>configure the DHCP servers in the visited link with >>>>>>information like home agent address, home address and home >>>>>>prefix. this is a bad idea. >>> >>> >>>You know that one does not have to put DHCP servers on every subnet, >> >>instead >> >>>one can rely on DHCP relays. And that's the used technique for many >>>enterprise networks. So, I don't see why this is a bad idea. >>> >>>Alper >>> >>> >>> >>> >>> >>>>Vijay >>>> >>>> >>>>>Alper >>>>> >>>>> >>>>> >>>>> >>>>>>-----Original Message----- >>>>>>From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com] >>>>>>Sent: Monday, June 19, 2006 6:17 PM >>>>>>To: Heejin Jang >>>>>>Cc: mip6@ietf.org; dhcwg@ietf.org >>>>>>Subject: Re: [Mip6] [Updated] DHCP Option for Home Information >> >>Discovery >> >>>>>>inMIPv6 >>>>>> >>>>>>Heejin Jang wrote: >>>>>> >>>>>> >>>>>>>Hello folks, >>>>>>>We posted an I-D that proposes new DHCP Options for Home >> >>Information >> >>>>>>>Discovery in MIPv6. >>>>>>> >>>>>>>Kindly note that the previous version of this draft is >>>>>>>"draft-jang-dhc-haopt-02.txt" but the name is slightly changed into >>>>>>>"draft-jang-mip6-hiopt-00.txt" while keeping almost the same >> >>contents. >> >>>>>>>The drafts referencing this draft such as >>>>>>>draft-ietf-mip6-bootstrapping-split-02.txt and >>>>>>>draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt need to be >> >>revised >> >>>>>>>accordingly. >>>>>>> >>>>>>>We would appreciate to hear your comments. >>>>>> >>>>>>when this draft was discussed in the MIP6 bootstrapping >>>>>>design team, many people wanted to integrate the two DHCP >>>>>>options into >>>>>>draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt. >>>>>>this was mainly because the options defined in the document >>>>>>have limited applicability beyond the integrated scenario >>>>>>solution document. the only other mechanism is to manually >>>>>>configure the DHCP servers in the visited link with >>>>>>information like home agent address, home address and home >>>>>>prefix. this is a bad idea. >>>>>> >>>>>>there was some opposition and we never reached an agreement. >>>>>> >>>>>>so I suggest including these options into the integrated >>>>>>scenario solution document for these options to get >>>>>>standardized quickly. >>>>>> >>>>>>Vijay >>>>>> >>>>>>_______________________________________________ >>>>>>Mip6 mailing list >>>>>>Mip6@ietf.org >>>>>>https://www1.ietf.org/mailman/listinfo/mip6 >>>>> >>>>> >>> >>> >>>_______________________________________________ >>>dhcwg mailing list >>>dhcwg@ietf.org >>>https://www1.ietf.org/mailman/listinfo/dhcwg >>> > > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] [Updated] DHCP Option for Home Informatio… Heejin Jang
- [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home… Alper Yegin
- [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home… Alper Yegin
- [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home… Alper Yegin
- Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for … Gerardo Giaretta
- RE: [dhcwg] RE: [Mip6] [Updated] DHCP Option for … Alper Yegin
- RE: [dhcwg] RE: [Mip6] [Updated] DHCP Option for … Alper Yegin
- [dhcwg] Re: [Mip6] [Updated] DHCP Option for Home… Vijay Devarapalli
- [dhcwg] Re: [Mip6] [Updated] DHCP Option for Home… Vijay Devarapalli
- Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for … Vijay Devarapalli
- Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for … Vijay Devarapalli
- [dhcwg] Re: [Mip6] [Updated] DHCP Option for Home… Vijay Devarapalli
- Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for … James Kempf