Re: draft-baker-6man-multiprefix-default-route-00.txt is a newdraft

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Nov 12, 2007, at 4:27 PM, Havard Eidnes wrote:

> Instead, my inclination would be to "solve" this problem in a much  
> simpler manner, simply by declaring it a configuration error.  A  
> site which receives prefixes from more than a single provider is  
> clearly multihomed, and needs to have its providers make  
> appropriate exceptions to a strict "I will only accept packets with  
> source addresses from within the prefix I delegate" rule.  Either  
> that, or the domain in question needs to ensure via a combination  
> of address selection and routing policy that one avoids being  
> subjected to (presumably unwanted) RPF failures.

You have read RFC 3704, right? You're aware of the routing issues here?

I think the provisions in that are quite a bit for the SOHO, and  
residential broadband providers tend to be reticent to do anything  
like what you suggest. Hence the comment. I would like to see a  
better solution than the one you are proposing.
-----BEGIN PGP SIGNATURE-----

iD8DBQFHONkqbjEdbHIsm0MRAnjUAKDoOE5uvo+nW8HhF6cMQBkytyWjWwCglacy
GaTOvghlEm8uVeWPC6gc904=
=O1cA
-----END PGP SIGNATURE-----

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------