Re: [mif] #5: only one default route? (there should be multiple, as for MIF WG)

#5: only one default route?  (there should be multiple, as for MIF WG)

Comment (by alexandru.petrescu@…):

 On 2012-03-28 04:30, Erik Kline wrote:
 > On 27 March 2012 15:26, Ted Lemon <Ted.Lemon@nominum.com> wrote:
 >>> Is also the following configuration out of scope for this group?
 >>> - a home network with TWO ISP's providing connection
 >>> - both without knowledge of each other
 >>> - both send default and specific route(s) (RA or DHCP)
 >>> IMHO, my home desktop should really be able to handle
 >>> this too (router selection needs to consider which source
 >>> address was picked from which router).
 >> Yes, this seems to be in scope to me.   I think you should submit a
 draft, since you've described both the problem and the solution quite
 well.   You are describing the "two provisioning domains" scenario, FWIW.

 The phrase "more than one default route" on its own makes my head hurt,
 given the normal meaning in computer science of the word "default".

 One default route per source prefix in use makes perfect sense, in view
 of the need for address pair selection and ingress-filtering avoidance.
 (When I think about it, a default route even makes sense for a ULA
 prefix.)

 > Submit to 6man, I think.

 Clearly - the customers for this include MIF, homenet and shim6 to name
 only three.

     Brian

     Brian
 _______________________________________________
 mif mailing list
 mif@ietf.org
 https://www.ietf.org/mailman/listinfo/mif

-- 
-------------------------------------+---------------------------------
 Reporter:  alexandru.petrescu@…     |       Owner:  Alexandru Petrescu
     Type:  enhancement              |      Status:  new
 Priority:  minor                    |   Milestone:  milestone1
Component:  dhcpv6-route-option      |     Version:
 Severity:  In WG Last Call          |  Resolution:
 Keywords:  multiple default routes  |
-------------------------------------+---------------------------------

Ticket URL: <https://trac.tools.ietf.org/wg/mif/trac/ticket/5#comment:7>
mif <http://tools.ietf.org/mif/>