Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home Information Discovery inMIPv6
Behcet Sarikaya <behcetsarikaya@yahoo.com> Thu, 22 June 2006 00:04 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtCgF-0006bb-67; Wed, 21 Jun 2006 20:04:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtCgD-0006bM-4R for mip6@ietf.org; Wed, 21 Jun 2006 20:04:17 -0400
Received: from web60320.mail.yahoo.com ([209.73.178.128]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FtCgC-0000vr-Gv for mip6@ietf.org; Wed, 21 Jun 2006 20:04:17 -0400
Received: (qmail 13982 invoked by uid 60001); 22 Jun 2006 00:04:16 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=L/fPfQRTyd3Lq17ss1ExFtFO+IYpCizpsq0HodvteFEjGLoV5KNNPkgut5+lstrwiljGG6hw//oYPqPU7P4cznN6cHhwBd9Fj5poL+cNgILPm+j/ArQJcVQxrcE2SNO8hF1eh15mjYrQxKbj4bB11ZE2lmd2/5KKtl0A0p6QszM= ;
Message-ID: <20060622000416.13980.qmail@web60320.mail.yahoo.com>
Received: from [12.129.211.52] by web60320.mail.yahoo.com via HTTP; Wed, 21 Jun 2006 17:04:16 PDT
Date: Wed, 21 Jun 2006 17:04:16 -0700
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home Information Discovery inMIPv6
To: Alper Yegin <alper.yegin@yegin.org>, Gerardo Giaretta <gerardo.giaretta@gmail.com>
In-Reply-To: <0MKoyl-1FtAYX2m3k-0000p1@mrelay.perfora.net>
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: cdb443e3957ca9b4c5b55e78cfcf4b26
Cc: mip6@ietf.org, Heejin Jang <heejin.jang@samsung.com>, dhcwg@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1756776807=="
Errors-To: mip6-bounces@ietf.org
Hi Vijay, The idea in the present WiMAX document is quite simple: it uses EAP-PKMv2 (which is like 802.11i) authentication and during EAP transaction, they assume that AAA server determines that the MS is a CMIPv6 authorized user based on the AAA profile and it will include all the so-called bootstrapping info in the Access-Accept. Then MS can use RFC 3736 to make a DHCP Information Request to DHCP Relay colocated with NAS and use draft-jang (extended now with HoA) and receive all the info to configure MIP6. No DHCP server is involved. In this setup can you make a case for draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt? Regards, --behcet ----- Original Message ---- From: Alper Yegin <alper.yegin@yegin.org> To: Gerardo Giaretta <gerardo.giaretta@gmail.com> Cc: mip6@ietf.org; dhcwg@ietf.org; Heejin Jang <heejin.jang@samsung.com> Sent: Wednesday, June 21, 2006 4:48:10 PM Subject: RE: [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home Information Discovery inMIPv6 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]. 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 > > _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www1.ietf.org/mailman/listinfo/mip6
_______________________________________________ Mip6 mailing list Mip6@ietf.org https://www1.ietf.org/mailman/listinfo/mip6
- [Mip6] [Updated] DHCP Option for Home Information… Heejin Jang
- Re: [Mip6] [Updated] DHCP Option for Home Informa… Vijay Devarapalli
- RE: [Mip6] [Updated] DHCP Option for Home Informa… Alper Yegin
- Re: [Mip6] [Updated] DHCP Option for Home Informa… Vijay Devarapalli
- RE: [Mip6] [Updated] DHCP Option for Home Informa… Alper Yegin
- Re: [Mip6] [Updated] DHCP Option for Home Informa… Vijay Devarapalli
- RE: [Mip6] [Updated] DHCP Option for Home Informa… Alper Yegin
- Re: [Mip6] [Updated] DHCP Option for Home Informa… Behcet Sarikaya
- Re: [Mip6] [Updated] DHCP Option for Home Informa… Vijay Devarapalli
- 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 … Vijay Devarapalli
- Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for … James Kempf
- Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for … Vijay Devarapalli
- Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for … Behcet Sarikaya
- RE: [dhcwg] RE: [Mip6] [Updated] DHCP Option for … Alper Yegin
- Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for … Vijay Devarapalli
- Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for … Behcet Sarikaya
- Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for … Vijay Devarapalli