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

"Manfredi, Albert E" <albert.e.manfredi@boeing.com> Mon, 12 November 2007 18:28 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 1Ire1O-00058t-Qq; Mon, 12 Nov 2007 13:28:30 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ire1N-00055V-80 for ipv6@ietf.org; Mon, 12 Nov 2007 13:28:29 -0500
Received: from slb-smtpout-01.boeing.com ([130.76.64.48]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ire1M-0004Fr-Qu for ipv6@ietf.org; Mon, 12 Nov 2007 13:28:29 -0500
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id lACISRkw025877 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Nov 2007 10:28:27 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id lACISRGv004343; Mon, 12 Nov 2007 10:28:27 -0800 (PST)
Received: from XCH-NEBH-11.ne.nos.boeing.com (xch-nebh-11.ne.nos.boeing.com [128.225.80.27]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id lACIS7A3003707; Mon, 12 Nov 2007 10:28:11 -0800 (PST)
Received: from XCH-NE-1V2.ne.nos.boeing.com ([128.225.80.43]) by XCH-NEBH-11.ne.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 12 Nov 2007 13:28:07 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 12 Nov 2007 13:28:05 -0500
Message-ID: <CA7D9B4A761066448304A6AFC09ABDA90331BD01@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <A4AE6069-5936-4C7E-AFD6-6100FB66A8EE@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: draft-baker-6man-multiprefix-default-route-00.txt is a newdraft
Thread-Index: AcglMazAQT0Rxwk9Tw+0OYSA35KCBgAJ0smA
References: <55C1E39E-7FE1-4912-B730-017C1C5CAC09@it.uc3m.es> <A4AE6069-5936-4C7E-AFD6-6100FB66A8EE@cisco.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Fred Baker <fred@cisco.com>
X-OriginalArrivalTime: 12 Nov 2007 18:28:07.0512 (UTC) FILETIME=[C5747580:01C82559]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
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

> -----Original Message-----
> From: Fred Baker [mailto:fred@cisco.com] 
> Sent: Monday, November 12, 2007 8:40 AM
> To: marcelo bagnulo braun
> Cc: IETF IPv6 Mailing List
> Subject: Re: 
> draft-baker-6man-multiprefix-default-route-00.txt is a newdraft
> 
> 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. 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.
> 
> Is there something wrong with that? Would you prefer it be 
> dropped as  
> it leaves the site? Would you prefer that the matter be indeterminate?

I found nothing objectionable at all in the draft.

Matter of fact, it seems to address something that also occurs with
IPv4, with multihomed hosts. And that apparently, some OSs screw up
royally. Which is, if a multi-homed IPv4 host, connected to two
different IP subnets, transmits an IP packet over Subnet A, it often is
found to use as source address the address assigned to its Subnet B
interface.

Whether or not this behavior results in total comm failure does not
preclude that is seems just plain wrong.

I agree that calling this "source routing." or anything similar, would
be misleading.

Bert

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