Re: draft-baker-6man-multiprefix-default-route-00.txt is a newdraft
marcelo bagnulo braun <marcelo@it.uc3m.es> Mon, 12 November 2007 15:10 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 1IravV-0005Rc-Ia; Mon, 12 Nov 2007 10:10:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IravU-0005Na-GL for ipv6@ietf.org; Mon, 12 Nov 2007 10:10:12 -0500
Received: from smtp02.uc3m.es ([163.117.176.132] helo=smtp.uc3m.es) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IravQ-0007SP-OJ for ipv6@ietf.org; Mon, 12 Nov 2007 10:10:12 -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 8BD41209FF6;Mon, 12 Nov 2007 16:05:55 +0100 (CET)
In-Reply-To: <A4AE6069-5936-4C7E-AFD6-6100FB66A8EE@cisco.com>
References: <200711081001.lA8A14C00375@ftpeng-update.cisco.com> <6A990F09-F0D4-43AA-BA1F-D81AB94628D6@cisco.com> <55C1E39E-7FE1-4912-B730-017C1C5CAC09@it.uc3m.es> <A4AE6069-5936-4C7E-AFD6-6100FB66A8EE@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="ISO-8859-1"; delsp="yes"; format="flowed"
Message-Id: <6E855E77-A8FB-401E-AC72-4A3F8D4A1686@it.uc3m.es>
Content-Transfer-Encoding: quoted-printable
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
Date: Mon, 12 Nov 2007 16:05:59 +0100
To: Fred Baker <fred@cisco.com>
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:-10.4945 TC:04 TRN:41 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: -1.9 (-)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
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 Fred, El 12/11/2007, a las 14:39, Fred Baker escribió: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Nov 12, 2007, at 12:27 PM, marcelo bagnulo braun wrote: > >> 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. i understand that it is done when the destination is off site and there are multiple routes to the external destination. So in a regular multihomed site that accept default routes from each ot its ISPs, basically, source address dependent routing is performed for all packets with an external destination, right? > 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. > agree, that is why i normally use Source address dependent routing instead of source routing > 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. right > > Is there something wrong with that? i don't know.... I have proposed a very similar thing in http://tools.ietf.org/id/ draft-ietf-shim6-ingress-filtering-00.txt but it got quite some push back and we finally dropped it from the shim6 wg. I would be interested to continue working on this, regards, marcelo > Would you prefer it be dropped as it leaves the site? Would you > prefer that the matter be indeterminate? > -----BEGIN PGP SIGNATURE----- > > iD8DBQFHOFerbjEdbHIsm0MRAh89AKDO1FiDeHknTEpXSwl0SP30BXSxXwCgj389 > ovysRXKu7Rr1wrO93DvioZQ= > =u6Oy > -----END PGP SIGNATURE----- -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- Fwd: draft-baker-6man-multiprefix-default-route-0… Fred Baker
- Re: draft-baker-6man-multiprefix-default-route-00… marcelo bagnulo braun
- Re: draft-baker-6man-multiprefix-default-route-00… Fred Baker
- Re: draft-baker-6man-multiprefix-default-route-00… marcelo bagnulo braun
- Re: draft-baker-6man-multiprefix-default-route-00… Havard Eidnes
- Re: draft-baker-6man-multiprefix-default-route-00… marcelo bagnulo braun
- RE: draft-baker-6man-multiprefix-default-route-00… Manfredi, Albert E
- Re: draft-baker-6man-multiprefix-default-route-00… Fred Baker
- Re: draft-baker-6man-multiprefix-default-route-00… Pekka Savola
- Re: draft-baker-6man-multiprefix-default-route-00… marcelo bagnulo braun
- RE: draft-baker-6man-multiprefix-default-route-00… James Carlson
- RE: draft-baker-6man-multiprefix-default-route-00… Manfredi, Albert E
- RE: draft-baker-6man-multiprefix-default-route-00… James Carlson
- Re: draft-baker-6man-multiprefix-default-route-00… Iljitsch van Beijnum
- Re: draft-baker-6man-multiprefix-default-route-00… James Carlson
- Re: Fwd: draft-baker-6man-multiprefix-default-rou… Brian E Carpenter