Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home Information Discovery inMIPv6
"Gerardo Giaretta" <gerardo.giaretta@gmail.com> Wed, 21 June 2006 08:17 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fsxu7-0005Eh-35; Wed, 21 Jun 2006 04:17:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fsxu5-0005EX-Gk for dhcwg@ietf.org; Wed, 21 Jun 2006 04:17:37 -0400
Received: from nf-out-0910.google.com ([64.233.182.187]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fsxu4-0006F0-4q for dhcwg@ietf.org; Wed, 21 Jun 2006 04:17:37 -0400
Received: by nf-out-0910.google.com with SMTP id c29so60520nfb for <dhcwg@ietf.org>; Wed, 21 Jun 2006 01:17:35 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=A3gOD1Kz89SkJ4QNqNHn4FpLNjr6vwuWm8h/JeDHPFld1YYUCqFYmex5UGxF7OP9CxY7j5viAXG1EpRwd0+lgv/YhYkRiy1lYRwy4OLPFua1KkwefBAbvQVSkKzjGQswgD0vzXi2jabjIXIx71lfxmGsgViUCIiCIKsH4MA55HE=
Received: by 10.49.58.3 with SMTP id l3mr318517nfk; Wed, 21 Jun 2006 01:17:35 -0700 (PDT)
Received: by 10.49.40.17 with HTTP; Wed, 21 Jun 2006 01:17:34 -0700 (PDT)
Message-ID: <eaa74a7e0606210117s4ec19b57h584e33828c083126@mail.gmail.com>
Date: Wed, 21 Jun 2006 10:17:35 +0200
From: Gerardo Giaretta <gerardo.giaretta@gmail.com>
To: Alper Yegin <alper.yegin@yegin.org>
Subject: Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home Information Discovery inMIPv6
In-Reply-To: <0MKoyl-1Fskwf2rab-0000pr@mrelay.perfora.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <44983503.6050703@azairenet.com> <0MKoyl-1Fskwf2rab-0000pr@mrelay.perfora.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Cc: mip6@ietf.org, Vijay Devarapalli <vijay.devarapalli@azairenet.com>, dhcwg@ietf.org, Heejin Jang <heejin.jang@samsung.com>
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, 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