Re: [mif] Default Route with DHCPv6 on a single-egress-interfaced Mobile Router

[Alexandru Petrescu <[e-mail]>]

Le 13/09/2010 16:31, Hui Deng a écrit :
> Hello Alex,
> Before discussion, just wondering whether you have read the draft before
> http://tools.ietf.org/html/draft-dec-dhcpv6-route-option-03
> Whether this draft solve your issue or not?

In a sense, yes, it does solve in a way the issue: I need a default 
route on a Mobile Router at home and that draft could deliver it.  I may 
have comments on it.

> People from different drafts are working on the merged solution recently,

Hmm... which solution and how recent?  Do you mean that authors of
draft-dec-dhcpv6-route-option-03 and of
draft-droms-dhc-dhcpv6-default-router-00 are about to write a common 
draft?  I am not aware of it.  If and when that happens I am interested 
to comment on it.

Alex

> thanks
> -Hui
>
> 2010/9/11 Alexandru Petrescu <[e-mail]
> <mailto:[e-mail]>>
>
>     Hello MIF,
>
>     I have a particular interest in MIF for simultaneous use of multiple
>     egress interfaces for bandwidth augmentation on a Mobile Router.
>       But it is not for this reason I post now.  I post now to ask about
>     Default Route delivered to a single-egress-interfaced Mobile Router.
>       This discussion was originated in the MEXT WG upon IESG LC of the
>     DHCPv6-PD-NEMO draft, then redirected to DHC WG then MIF WG was
>     mentioned too.
>
>     Le 31/08/2010 04:56, Hui Deng a écrit :
>     [...]
>
>         2) DHCPv6 routing configuration: a specification of DHCPv6 options
>         allowing client nodes to perform route table configuration.
>
>
>     Would this item allow for a draft describing the way in which
>     DHCPv6(/-PD) assigns a Default Route to a single-egress-interfaced
>     Mobile Router?
>
>     My problem is a Mobile Router connected on the home link.  It acquires a
>     prefix (the Mobile Network Prefix) using DHCPv6-PD.  Being a Router it
>     doesn't configure a default route from SLAAC (if I want it to I have to
>     switch it from Router to Host - burdensome).  DHCPv6 doesn't deliver it
>     a Default Route either.  So I am left with a nice machine without a
>     default route - I have to manually configure it.
>
>     I could write a draft telling that DHCPv6 option is delivered to a
>     single-egress-interfaced Mobile Router and allows it to configure a
>     default route.  Would this draft fit within this potential Charter item?
>
>     Any comments appreciated: is this kind of work appropriate here?  Is
>     another alternative work (like DHCPv6 tells Router to acquire this from
>     SLAAC, and modify SLAAC)?  Could this be adapted to MIF by saying there
>     _could_ be multiple such egress interfaces each with its own default
>     route (hard, there should be only one default - the last resort)?
>
>     Any comments appreciated about how to set a default route on a Mobile
>     Router single-egress interface.
>
>     Alex
>
>         3) MIF API: While no changes are needed for applications to run on
>         multiple interface hosts, this API could provide additional services
>         to applications running on hosts attached to multiple provisioning
>         domains. For instance, these services could help in solving
>         first-hop, source address and/or DNS selection issues. Goals and
>         Milestones Nov 2010: Initial WG draft on Split-DNS solution Nov
>         2010:
>         Initial WG draft on DHCPv6 option for routing configuration Nov
>         2010:
>         Initial WG draft on MIF API extension. Nov 2011: Submit Split-DNS
>         solution to IESG for publication as a Proposed Standard RFC Nov
>         2011:
>         Submit DHCPv6 routing configuration option to IESG for
>         publication as
>         a Proposed Standard RFC Nov 2011: Submit MIF API extension solution
>         to IESG for publication as an Informational RFC
>
>
>
>         _______________________________________________ mif mailing list
>         [e-mail] <mailto:[e-mail]>
>         https://www.ietf.org/mailman/listinfo/mif
>
>
>