RE: [Mip6] [Updated] DHCP Option for Home Information Discovery inMIPv6

> > 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.

Can we hear from someone else who insists we shall bundle up the I-Ds?

> 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.

You really want us to circle around, don't you :-)

> > 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.

> 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
> >
> >

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