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

marcelo bagnulo braun <marcelo@it.uc3m.es> Mon, 12 November 2007 16:33 UTC

Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrcEO-0001Y9-01; Mon, 12 Nov 2007 11:33:48 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrcEM-0001V3-Lw for ipv6@ietf.org; Mon, 12 Nov 2007 11:33:46 -0500
Received: from smtp01.uc3m.es ([163.117.176.131] helo=smtp.uc3m.es) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IrcEM-0007Ob-1w for ipv6@ietf.org; Mon, 12 Nov 2007 11:33:46 -0500
Received: from [163.117.139.225] (chelo-it-uc3m-es.it.uc3m.es [163.117.139.225])(using TLSv1 with cipher AES128-SHA (128/128 bits))(No client certificate requested)by smtp.uc3m.es (Postfix) with ESMTP id 8A9101DBDBF;Mon, 12 Nov 2007 17:33:44 +0100 (CET)
In-Reply-To: <20071112.172700.95023288.he@uninett.no>
References: <6A990F09-F0D4-43AA-BA1F-D81AB94628D6@cisco.com><55C1E39E-7FE1-4 912-B730-017C1C5CAC09@it.uc3m.es><A4AE6069-5936-4C7E-AFD6-6100FB66A8EE@cis co.com> <20071112.172700.95023288.he@uninett.no>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="ISO-8859-1"; delsp="yes"; format="flowed"
Message-Id: <18ADD814-6EC5-467D-907E-A83265529B78@it.uc3m.es>
Content-Transfer-Encoding: quoted-printable
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
Date: Mon, 12 Nov 2007 17:33:48 +0100
To: Havard Eidnes <he@uninett.no>
X-Mailer: Apple Mail (2.752.3)
X-imss-version: 2.049
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-5.7554 TC:04 TRN:48 TV:5.0.1023(15542.000)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
X-Spam-Score: 2.1 (++)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: ipv6@ietf.org, fred@cisco.com
Subject: Re: draft-baker-6man-multiprefix-default-route-00.txt is a newdraft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Havard,

El 12/11/2007, a las 17:27, Havard Eidnes escribió:

>>> AFAIU, you are essentially proposing to perform source address
>>> based routing by the hosts and by the routers in a multiprefix
>>> site, is that correct?
>>
>> I don't like the term, because I first do a destination lookup and
>> only look up the source address in certain cases. Kind of like the
>> previous comment on source routing, which in IEEE 802.5, DSR, and RFC
>> 791 IP means that the source specifies all or part of the routing
>> path. I think the term mis-states the case.
>>
>> But yes, in certain cases where there is a multipath route, the point
>> is that if the datagram is handed to the wrong ISP and the ISP is
>> doing ingress filtering, the datagram will be dropped, and hence I
>> suggest that we direct it toward the right ISP.
>
> But still, you appear to propose to fundamentally change the
> forwarding process by inserting a relatively complex lookup
> operation into per-packet forwarding, and I think such a change
> needs quite a bit more in terms of justification.
>
> 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.
>

but which type of sites do you think will have such configuration? I  
mean, i would expect that very small multihomed sites may end up with  
this configuration, e.g. a home network with dsl and CATV access.
So in this case, i am not sure if the trust needed to release the  
ingress filters will exist, so i am not sure the isp will agree to  
release them

Regards, marcelo


> Regards,
>
> - Håvard
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


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