RE: [dhcwg] RE: [Mip6] [Updated] DHCP Option for HomeInformationDiscovery inMIPv6

Hi Kuntal and Vijay.

See my posting, "Generalizing draft-jang-dhc-haopt for MIPv6 support in
DHCP", back on Jan 4, 2006 on this topic.  I proposed to keep the 2
drafts separate, one for defining DHCPv6 opcodes for MIPv6 parameters
and a bootstrap draft that references the DHCP options needed to achieve
its function.

I agree there's no need to drag in references other to say that there's
value for the DHCP MIPv6 options.  3GPP2/WiMAX specs can reference the
DHCPv6 opcodes for MIPv6 draft/RFC, much like what MIPv6 bootstrap would
have done.

As for what Vijay said about the WiMAX scheme, definitely true that it
doesn't conform to DHCP RFC 3315.  But we should keep the issues
separate.  I haven't read all the emails on the thread.  Just jumping in
to say the following:

 - Keep 2 separate self contained drafts
 - IETF MIPv6 bootstrap draft references DHCP for MIPv6 draft
 - WiMAX and 3GPP2 can also reference DHCP for MIPv6 draft for their
bootstrapping schemes

Just some explanatory comments:
 - 3GPP2 conforms to DHCPv6 in its bootstrapping scheme
 - WiMAX does not conform to DHCPv6 when using proxy DHCP server scheme

But *ALL* of the above bootstrapping schemes use the same DHCP options
for MIPv6 parameters.  That's what justifies an independent DHCP for
MIPv6 draft, IMHO.

Kent

> -----Original Message-----
> From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com] 
> Sent: Thursday, June 22, 2006 7:19 PM
> To: Vijay Devarapalli; Behcet Sarikaya
> Cc: mip6@ietf.org; Heejin Jang; dhcwg@ietf.org
> Subject: RE: [dhcwg] RE: [Mip6] [Updated] DHCP Option for 
> HomeInformationDiscovery inMIPv6
> 
> Sorry, I am not getting this. Why are we dragging WiMAX and 
> 3GPP2 references to justify the need for basic DHCP op-codes 
> for HoA/HL/HA infcrosoft SMTPSVC(6.0.3790.211);
	Mon, 26 Jun 2006 14:42:02 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] RE: [Mip6] [Updated] DHCP Option for
	HomeInformationDiscovery inMIPv6
Date: Mon, 26 Jun 2006 14:42:00 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC52020C8E13@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] RE: [Mip6] [Updated] DHCP Option for
	HomeInformationDiscovery inMIPv6
Thread-Index: AcaWJ1At3e9b1E8eTceNcRUoaUj47wAQ6ahAAL8Y9OAFrom: "Kent Leung \(kleung\)" <kleung@cisco.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"Behcet Sarikaya" <sarikaya@ieee.org>
X-OriginalArrivalTime: 26 Jun 2006 21:42:02.0927 (UTC)
	FILETIME=[5C81E3F0:01C69969]
DKIM-Signature: a=rsa-sha1; q=dns; l982; t51358133; x52222133;
	c=relaxed/simple; s=sjdkim5001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:"Kent Leung \(kleung\)" <kleung@cisco.com>
	|Subject:RE: [dhcwg] RE: [Mip6] [Updated] DHCP Option for Hom
	eInformationDiscovery inMIPv6;
	X=v=cisco.com; h=JYf6MBNa8mTiQH9SoxmdmxHW/20=;
	b
3J99ySXVUrGIAsJcpHZ4VoS0kLhNkU3hlTNwx71+UWsfFaUH8hlWrfWepioWyi4du4jztU
	r5l4Ln1bNNrthDLmyz+gnzGMD/vd91PFo2y1v2EMtKsfghBKgFfzv4DE;
Authentication-Results: sj-dkim-5.cisco.com; header.From=kleung@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
X-Mailman-Approved-At: Wed, 27 Sep 2006 22:14:58 -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

Hi Kuntal and Vijay.

See my posting, "Generalizing draft-jang-dhc-haopt for MIPv6 support in
DHCP", back on Jan 4, 2006 on this topic.  I proposed to keep the 2
drafts separate, one for defining DHCPv6 opcodes for MIPv6 parameters
and a bootstrap draft that references the DHCP options needed to achieve
its function.

I agree there's no need to drag in references other to say that there's
value for the DHCP MIPv6 options.  3GPP2/WiMAX specs can reference the
DHCPv6 opcodes for MIPv6 draft/RFC, much like what MIPv6 bootstrap would
have done.

As for what Vijay said about the WiMAX scheme, definitely true that it
doesn't conform to DHCP RFC 3315.  But we should keep the issues
separate.  I haven't read all the emails on the thread.  Just jumping in
to say the following:

 - Keep 2 separate self contained drafts
 - IETF MIPv6 bootstrap draft references DHCP for MIPv6 draft
 - WiMAX and 3GPP2 can also reference DHCP for MIPv6 draft for their
bootstrapping schemes

Just some explanatory comments:
 - 3GPP2 conforms to DHCPv6 in its bootstrapping scheme
 - WiMAX does not conform to DHCPv6 when using proxy DHCP server scheme

But *ALL* of the above bootstrapping schemes use the same DHCP options
for MIPv6 parameters.  That's what justifies an independent DHCP for
MIPv6 draft, IMHO.

Kent

> -----Original Message-----
> From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com] 
> Sent: Thursday, June 22, 2006 7:19 PM
> To: Vijay Devarapalli; Behcet Sarikaya
> Cc: mip6@ietf.org; Heejin Jang; dhcwg@ietf.org
> Subject: RE: [dhcwg] RE: [Mip6] [Updated] DHCP Option for 
> HomeInformationDiscovery inMIPv6
> 
> Sorry, I am not getting this. Why are we dragging WiMAX and 
> 3GPP2 references to justify the need for basic DHCP op-codes 
> for HoA/HL/HA info?
> 
> draft-jang-mip6-hiopt-00.txt defines the DHCPv6 op-codes for 
> HA, HoA and HL info.
> 
> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt is the 
> MIP6 bootstrapping solution that leverages DHCPv6 for HA/HL 
> bootstrapping. 
> 
> There are tons of I-Ds and solutions in IETF that leverage other I-Ds.
> So, what is so special here? The decision to NOT merge these 
> I-Ds was taken in the bootstrap DT. Why are we wasting 
> people's time here to revisit basic decisions?
> 
> -Kuntal
> 
> 
> > -----Original Message-----
> > From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > Sent: Thursday, June 22, 2006 12:55 PM
> > To: Behcet Sarikaya
> > Cc: mip6@ietf.org; Heejin Jang; dhcwg@ietf.org
> > Subject: Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home 
> > InformationDiscovery inMIPv6
> > 
> > Behcet Sarikaya wrote:
> > > 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.
> > 
> > the DHCP Relay replies to the MN without relaying the DHCP request 
> > from the MN to a DHCP server? this is not allowed with the current 
> > IETF specs.
> > 
> > >   In this setup can you make a case for 
> > > draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt?
> > 
> > as far as I am concerned,
> > draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
> > is the document that describes how to use DHCPv6 for MIPv6 
> > bootstrapping. as for the setup in the WiMAX NWG, it is 
> something that 
> > doesn't conform to the IETF DHCP specs.
> > 
> > Vijay
> > <snip>
> 

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

o?
> 
> draft-jang-mip6-hiopt-00.txt defines the DHCPv6 op-codes for 
> HA, HoA and HL info.
> 
> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt is the 
> MIP6 bootstrapping solution that leverages DHCPv6 for HA/HL 
> bootstrapping. 
> 
> There are tons of I-Ds and solutions in IETF that leverage other I-Ds.
> So, what is so special here? The decision to NOT merge these 
> I-Ds was taken in the bootstrap DT. Why are we wasting 
> people's time here to revisit basic decisions?
> 
> -Kuntal
> 
> 
> > -----Original Message-----
> > From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > Sent: Thursday, June 22, 2006 12:55 PM
> > To: Behcet Sarikaya
> > Cc: mip6@ietf.org; Heejin Jang; dhcwg@ietf.org
> > Subject: Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home 
> > InformationDiscovery inMIPv6
> > 
> > Behcet Sarikaya wrote:
> > > 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.
> > 
> > the DHCP Relay replies to the MN without relaying the DHCP request 
> > from the MN to a DHCP server? this is not allowed with the current 
> > IETF specs.
> > 
> > >   In this setup can you make a case for 
> > > draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt?
> > 
> > as far as I am concerned,
> > draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
> > is the document that describes how to use DHCPv6 for MIPv6 
> > bootstrapping. as for the setup in the WiMAX NWG, it is 
> something that 
> > doesn't conform to the IETF DHCP specs.
> > 
> > Vijay
> > <snip>
> 

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg