[dhcwg] Re: [Mip6] [Updated] DHCP Option for Home Information Discovery inMIPv6
Vijay Devarapalli <vijay.devarapalli@azairenet.com> Thu, 22 June 2006 18:16 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtTjf-0005er-T0; Thu, 22 Jun 2006 14:16:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FskNA-00037Q-Ae; Tue, 20 Jun 2006 13:50:44 -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 1FskN8-0005Wd-VM; Tue, 20 Jun 2006 13:50:44 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 Jun 2006 10:50:42 -0700
Message-ID: <44983503.6050703@azairenet.com>
Date: Tue, 20 Jun 2006 10:48:51 -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>
References: <0MKp2t-1FsYuU3mc1-0007WT@mrelay.perfora.net>
In-Reply-To: <0MKp2t-1FsYuU3mc1-0007WT@mrelay.perfora.net>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Jun 2006 17:50:42.0079 (UTC) FILETIME=[0C6612F0:01C69492]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
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
Subject: [dhcwg] Re: [Mip6] [Updated] DHCP Option for Home Information Discovery inMIPv6
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: > Vijay, > > As far as I remember you were the only one who didn't give up on pushing for > integration. I think you remember wrong. It'd only be a circular discussion if I had repeated the > reasons for not bundling a bunch of protocol extensions in a single > document. let the MIP6 WG hear the arguments again, since we couldn't reach a conclusion in the design team. > 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 WiMAX forum NWG can still use the DHCP options wherever they are defined. 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] [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