Re: [PCN] RSVP and ECMP
Bruce Davie <bdavie@cisco.com> Tue, 23 October 2007 17:51 UTC
Return-path: <pcn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkNum-0007Qd-Uh; Tue, 23 Oct 2007 13:51:40 -0400
Received: from pcn by megatron.ietf.org with local (Exim 4.43) id 1IkNul-0007Pc-HN for pcn-confirm+ok@megatron.ietf.org; Tue, 23 Oct 2007 13:51:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkNuk-0007PO-OT for pcn@ietf.org; Tue, 23 Oct 2007 13:51:38 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkNu3-0004bd-SV for pcn@ietf.org; Tue, 23 Oct 2007 13:51:38 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-2.cisco.com with ESMTP; 23 Oct 2007 10:50:55 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l9NHotJq017320; Tue, 23 Oct 2007 10:50:55 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l9NHojxJ022611; Tue, 23 Oct 2007 17:50:55 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 23 Oct 2007 10:50:51 -0700
Received: from [10.32.241.67] ([10.32.241.67]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 23 Oct 2007 10:50:50 -0700
In-Reply-To: <471E1C5C.5020502@informatik.uni-wuerzburg.de>
References: <471E1C5C.5020502@informatik.uni-wuerzburg.de>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <6C20D78B-36AE-4D88-8F7A-20F4D4A512A4@cisco.com>
Content-Transfer-Encoding: 7bit
From: Bruce Davie <bdavie@cisco.com>
Subject: Re: [PCN] RSVP and ECMP
Date: Tue, 23 Oct 2007 13:50:42 -0400
To: menth@informatik.uni-wuerzburg.de
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 23 Oct 2007 17:50:50.0928 (UTC) FILETIME=[4015D300:01C8159D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2197; t=1193161855; x=1194025855; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=bdavie@cisco.com; z=From:=20Bruce=20Davie=20<bdavie@cisco.com> |Subject:=20Re=3A=20[PCN]=20RSVP=20and=20ECMP |Sender:=20; bh=F9r1LQj/EYtzF3uzrMqinG2xS1HAxkh806HqwcyBoIY=; b=r+Ik+/PNx9OnaSi+pGBohObN5MDXzpjUybsuHIb6FJErRcbBudTzjiGxqBWyDwF5ovAhUTBQ 8F2OeqrwclDl+wiXEdeVZ1oYD6q4psxMlRUm6IjC3tv/EwhQ5JiHS4fk;
Authentication-Results: sj-dkim-2; header.From=bdavie@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: pcn@ietf.org
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
Errors-To: pcn-bounces@ietf.org
Michael, RSVP tries to forward the Path exactly the same way that it would forward the data. Since Path messages are processed outside of the fast path, it is possible for the router to look at anything that is in the path message, including source addr, dest addr, and port numbers, and figure out where a data packet that had those values in its IP header would get forwarded. It sends the Path message out that interface. In practice, this takes care of the vast majority of ECMP algorithms. This approach is implemented today. If ECMP was using something from the IP or higher layer header that was not in the Path message, then a problem would arise. So, practically speaking, if the probe messages have the same addresses and ports as the data, they should get correct ECMP treatment. Or at least, fare no worse than RSVP. Bruce On Oct 23, 2007, at 12:07 PM, Michael Menth wrote: > Hi, > > I've got a question regarding RSVP. PATH messages need to be > carried over the same path as subsequent data packets. How is this > achieved in the presence of ECMP routing? In theory, PATH messages > can take a different route than data packets if the load balancer > takes arbitrary parts of the header(s) to calculate a suitable hash > value, which decides which route the packet will take. > > This issue seems to be related to the problem of how to make sure > that PCN probe messages take the same path as subsequent PCN data > packets, provided that they have the same source and destination > ports and addresses. > > I am interested in how this problem is solved in practice or > whether it is intentionally avoided. > > Regards, > > Michael > > -- > Dr. Michael Menth, Assistant Professor > University of Wuerzburg, Institute of Computer Science > Am Hubland, D-97074 Wuerzburg, Germany, room B206 > phone: (+49)-931/888-6644, fax: (+49)-931/888-6632 > mailto:menth@informatik.uni-wuerzburg.de > http://www3.informatik.uni-wuerzburg.de/research/ngn > > > > _______________________________________________ > PCN mailing list > PCN@ietf.org > https://www1.ietf.org/mailman/listinfo/pcn _______________________________________________ PCN mailing list PCN@ietf.org https://www1.ietf.org/mailman/listinfo/pcn
- [PCN] RSVP and ECMP Michael Menth
- Re: [PCN] RSVP and ECMP Martin Karsten
- Re: [PCN] RSVP and ECMP Michael Menth
- Re: [PCN] RSVP and ECMP Bruce Davie
- RE: [PCN] RSVP and ECMP Anna Charny (acharny)
- RE: [PCN] RSVP and ECMP Jozef Babiarz
- Re: [PCN] RSVP and ECMP Georgios Karagiannis
- Re: [PCN] RSVP and ECMP Hannes Tschofenig
- RE: [PCN] RSVP and ECMP Anna Charny (acharny)
- Re: [PCN] RSVP and ECMP Hannes Tschofenig
- Re: [PCN] RSVP and ECMP Tina TSOU