
From curtis@occnc.com  Wed Mar  2 11:05:37 2011
Return-Path: <curtis@occnc.com>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F06CB3A6844 for <rtgwg@core3.amsl.com>; Wed,  2 Mar 2011 11:05:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8gEShfSt0ri0 for <rtgwg@core3.amsl.com>; Wed,  2 Mar 2011 11:05:37 -0800 (PST)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 0993D3A6840 for <rtgwg@ietf.org>; Wed,  2 Mar 2011 11:05:36 -0800 (PST)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id p22J6RAv046496; Wed, 2 Mar 2011 14:06:27 -0500 (EST) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201103021906.p22J6RAv046496@harbor.orleans.occnc.com>
To: Tony Li <tony.li@tony.li>
From: Curtis Villamizar <curtis@occnc.com>
Subject: Re: WGLC completed on draft-ietf-rtgwg-cl-requirement-03 
In-reply-to: Your message of "Thu, 24 Feb 2011 15:30:37 PST." <ABA87097-B0BA-40C6-BEDB-288E84BE9C17@tony.li> 
Date: Wed, 02 Mar 2011 14:06:27 -0500
Sender: curtis@occnc.com
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 19:05:38 -0000

In message <ABA87097-B0BA-40C6-BEDB-288E84BE9C17@tony.li>
Tony Li writes:
>  
>  
> On Feb 24, 2011, at 3:24 PM, Curtis Villamizar wrote:
>  
> > If there are a large number of components with identical properties,
> > then the IGP needs to indicate that how many components exist with a
> > given set of properties.  In some cases, it may not be necessary to
> > enumberate each component.
>  
> Hi Curtis,
>  
> I'm perfectly happy with any encoding tricks that folks may propose
> that will allow further aggregation in the cases where doing do does
> not lose significant information.
>  
> I look forward to concrete proposals.
>  
> Regards,
> Tony


Tony,

Thanks.

For now I just want to be sure that we don't prohibit those concrete
proposals in the requirements and/or architecture.  I put some wording
into the requirements to that effect but it was removed.

I think you would agree that it is too early to try to define the TLVs
to do this.

Curtis

From tony.li@tony.li  Wed Mar  2 11:12:18 2011
Return-Path: <tony.li@tony.li>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 06E463A6857 for <rtgwg@core3.amsl.com>; Wed,  2 Mar 2011 11:12:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.552
X-Spam-Level: 
X-Spam-Status: No, score=-102.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iuax+QGyp3vO for <rtgwg@core3.amsl.com>; Wed,  2 Mar 2011 11:12:17 -0800 (PST)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by core3.amsl.com (Postfix) with ESMTP id 3C8983A6840 for <rtgwg@ietf.org>; Wed,  2 Mar 2011 11:12:17 -0800 (PST)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta12.westchester.pa.mail.comcast.net with comcast id EK8j1g0091c6gX85CKDPc7; Wed, 02 Mar 2011 19:13:24 +0000
Received: from dhcp-171-70-245-114.cisco.com ([171.70.245.114]) by omta23.westchester.pa.mail.comcast.net with comcast id EKD21g0012Up3dF3jKD856; Wed, 02 Mar 2011 19:13:18 +0000
Subject: Re: WGLC completed on draft-ietf-rtgwg-cl-requirement-03 
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Tony Li <tony.li@tony.li>
In-Reply-To: <201103021906.p22J6RAv046496@harbor.orleans.occnc.com>
Date: Wed, 2 Mar 2011 11:13:00 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <6A4EC8BF-32E6-45D8-A924-B3D35E62009B@tony.li>
References: <201103021906.p22J6RAv046496@harbor.orleans.occnc.com>
To: curtis@occnc.com
X-Mailer: Apple Mail (2.1082)
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 19:12:18 -0000

On Mar 2, 2011, at 11:06 AM, Curtis Villamizar wrote:

> I think you would agree that it is too early to try to define the TLVs
> to do this.


I agree that the solutions should not make it into the requirements.  

Tony


From curtis@occnc.com  Wed Mar  2 11:17:10 2011
Return-Path: <curtis@occnc.com>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0022E3A6831 for <rtgwg@core3.amsl.com>; Wed,  2 Mar 2011 11:17:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NbJeSBUjuI+B for <rtgwg@core3.amsl.com>; Wed,  2 Mar 2011 11:17:09 -0800 (PST)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 7FFE73A6800 for <rtgwg@ietf.org>; Wed,  2 Mar 2011 11:17:08 -0800 (PST)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id p22JIC5g046621; Wed, 2 Mar 2011 14:18:12 -0500 (EST) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201103021918.p22JIC5g046621@harbor.orleans.occnc.com>
To: Lucy yong <lucy.yong@huawei.com>
From: Curtis Villamizar <curtis@occnc.com>
Subject: Re: WGLC completed on draft-ietf-rtgwg-cl-requirement-03 
In-reply-to: Your message of "Fri, 25 Feb 2011 00:34:22 GMT." <2691CE0099834E4A9C5044EEC662BB9D2ABE9F@DFWEML501-MBX.china.huawei.com>
Date: Wed, 02 Mar 2011 14:18:12 -0500
Sender: curtis@occnc.com
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 19:17:10 -0000

In message <2691CE0099834E4A9C5044EEC662BB9D2ABE9F@DFWEML501-MBX.china.huawei.com>
Lucy yong writes:
>  
>  
> Hi Curtis,
>  
>  
> > I suggest that we go down a path which allows the following options:
> > 
> >   1.  list existing min-bw, max-bw summary with attached extended
> >       attributes per aggregate, with no other information.
>  
> [LY] Does "min-bw" mean the largest LSP that composite link can take?
> If yes, I agree this is the right direction. 


We do need to extend the semantics on min-bw and I had indicated that.
The existing min-bw applies to LSP that must take only one component.

With existing hash based multipath techniques a larger LSP can be
accommodated as long as no microflow within the LSP is larger than
min-bw.

Currently there is no way to determine which case applies.  Both cases
should be supported (must be?) with the LSR indicating which flavor it
supports.


> >   2.  add to #1, for all or a subset of components a sub-aggregation
> >       that is characterized by min-bw, max-bw and attached extended
> >       attributes,
>  
> [LY] Yes, we had this in mind. In addition, it is valuable to allow a
> composite link containing some component links that just use recovery
> purpose so their BW does not need to be advertised. A good example is
> that when a composite link contains a 10G component link with 30ms
> transmission delay and 1G component link with 500ms transmission
> delay. The composite link can just advertise 10BW with 30ms. 1G link
> can be used for recovery purpose. This gives operator flexibility to
> use the composite link. This does not require protocol changes, just
> need to describe the usage.

Yes and this too would have the semantics of min-bw listed above with
a needed extension to disambiguate the current "standard" meansing of
min-bw and a common interpretation or not force deployments that need
the "all ones" behaviour to configure min-bw to be equal to max-bw
regardless of component sizes (to get the desired ingress behaviour).

The sub-aggregation must be in addition rather than a replacement for
backwards compatibility.

> >   3.  add to #1 or #1 plus #2, advertisements for individual
> >       components.
> > 
> > #1 is just extended attributes added to link bundle.  #2 and #3 are
> >  sub-tlvs added to the link bundle.

Yes.

> [LY] Agree. 
>  
> Lucy

Regards,

Curtis


From akatlas@gmail.com  Tue Mar  8 06:01:08 2011
Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C36A3A6843 for <rtgwg@core3.amsl.com>; Tue,  8 Mar 2011 06:01:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vLlrRRkxitRK for <rtgwg@core3.amsl.com>; Tue,  8 Mar 2011 06:01:07 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 6DE6D3A63CB for <rtgwg@ietf.org>; Tue,  8 Mar 2011 06:01:06 -0800 (PST)
Received: by iwl42 with SMTP id 42so6137764iwl.31 for <rtgwg@ietf.org>; Tue, 08 Mar 2011 06:02:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=09S/gbmzgxZU6S5DwAuYpHefGejXaz5uBZiK1q34DSQ=; b=Q59xQ+MSYjhurcX9a52fq2iivP3HkimWE5rK/+PfpKm4p6gP/yU4r4XXpcvqBeC7Z4 WYs9DafHuxlYU5aNh7CsNOgcFgFmBhh8Bma9IfygER65/zuXTLeHeGoEY2T7t0aWnJx+ 4mgGNylbnWTPGRJJAGnGrYE5+G5ZlBl59U41k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=jYc88p14z3LZFDw8LSAkAuwlbsM1heHhw0avXN6uWwfpDfcU0rUJub9XHnoq5bxJ1F hwkDAkG+jFFlQfHlh/NEDG7U751MUw9Dcnttph6BaPlVRlHiRCBI/aaORHJGMpb/sA1v QEcsRr1CAKTyIJvb3A1hlO9tnUVdMzD+gYqys=
MIME-Version: 1.0
Received: by 10.43.70.20 with SMTP id ye20mr4593169icb.156.1299592941803; Tue, 08 Mar 2011 06:02:21 -0800 (PST)
Received: by 10.42.8.208 with HTTP; Tue, 8 Mar 2011 06:02:21 -0800 (PST)
Date: Tue, 8 Mar 2011 09:02:21 -0500
Message-ID: <AANLkTikcp_YpsjD6Rrzmqdj-ftP6_s5g=A5+afXWR=mT@mail.gmail.com>
Subject: agenda requests for Praque
From: Alia Atlas <akatlas@gmail.com>
To: rtgwg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2011 14:01:08 -0000

Please send us your agenda requests this week so that we can
get a preliminary agenda ready.  We are meeting on Monday afternoon.

Thanks,
Alia

From akatlas@gmail.com  Fri Mar 11 08:48:44 2011
Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82A783A6B0B for <rtgwg@core3.amsl.com>; Fri, 11 Mar 2011 08:48:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6xON45d9Ez5t for <rtgwg@core3.amsl.com>; Fri, 11 Mar 2011 08:48:43 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id 9982F3A6A38 for <rtgwg@ietf.org>; Fri, 11 Mar 2011 08:48:43 -0800 (PST)
Received: by iyj8 with SMTP id 8so3443803iyj.31 for <rtgwg@ietf.org>; Fri, 11 Mar 2011 08:50:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=27NhCkFXGLnWYyISmWbRA+6hbtytjEulXER6KRcLDyY=; b=Dv5GAZKdwD9pbKvqvOtf0Ylal+QwLZ/84jceuKQFN5GCLRHkpQzZYbAUMSck4p9Bnk LRKEKYrwH5I/oI1z7XbjfjlS7hTECGV0IdVgWfk+2oRGDVvI39SKC5CgLI9L/KsHeBXS QYYNnO4WqxkK6biVTXeS0mzsg6eoQg3eABCws=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=kGD3zsar5+6jaOLaJfdwp+R8nhdwWrC7cFAuVOlzZ8v00M6zZD3MptgYZKhH6oDm/6 WCi42IvdhoYDHkv2nd8d/hHu932ZWRJFCUGUMkluyQ35dWAdn1ZeHJre1ktkebbYpXRQ sRvOPhRdA+xBLElao4ZixEK4Dpkydqt0W+klw=
MIME-Version: 1.0
Received: by 10.42.246.70 with SMTP id lx6mr1141187icb.223.1299862203011; Fri, 11 Mar 2011 08:50:03 -0800 (PST)
Received: by 10.42.8.208 with HTTP; Fri, 11 Mar 2011 08:50:02 -0800 (PST)
Date: Fri, 11 Mar 2011 11:50:02 -0500
Message-ID: <AANLkTik8D71qvSkxY=wzQdhA7JGLa5BmP9fsw=6iVZFs@mail.gmail.com>
Subject: preliminary agenda for IETF80 available
From: Alia Atlas <akatlas@gmail.com>
To: rtgwg@ietf.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 16:48:44 -0000

IETF 80   Routing Area WG Agenda
Monday, March 28   13:00 =96 15:00

Topic	Draft	Presenter	Time Allotted
Agenda Bashing & Current Draft Statuses		Alia Atlas	10 mins
LFA Applicability	draft-ietf-rtgwg-lfa-applicability
Clarence Filsfils
15 mins
Multicast Only Fast Reroute	draft-karan-mofrr
Clarence Filsfils
15 mins
Composite Link Framework	draft-so-yong-rtgwg-cl-framework-03
Ning So
10 mins
Composite Link Discussion			10 mins
OSPF TE Express Path	draft-giacalone-ospf-te-express-path
Spencer Giacolone
15 mins
Fast Notification Framework	draft-lu-fast-notification-framework
Wenhu Lu
5 mins
IP Fast-Reroute with Fast Notification	draft-csaszar-ipfrr-fn-00
	Andras Csaszar
15 mins
Transport of Fast Notification Messages	draft-lu-fn-transport-00
Wenhu Lu
20 mins

From Internet-Drafts@ietf.org  Sat Mar 12 05:00:03 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 47BF83A6A31; Sat, 12 Mar 2011 05:00:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.563
X-Spam-Level: 
X-Spam-Status: No, score=-102.563 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QJt1iL1aQ8c6; Sat, 12 Mar 2011 05:00:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ACFAE3A6959; Sat, 12 Mar 2011 05:00:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-rtgwg-lfa-applicability-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110312130001.24508.77518.idtracker@localhost>
Date: Sat, 12 Mar 2011 05:00:01 -0800
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Mar 2011 13:00:03 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Routing Area Working Group Working Group of the IETF.


	Title           : LFA applicability in SP networks
	Author(s)       : C. Filsfils, et al.
	Filename        : draft-ietf-rtgwg-lfa-applicability-01.txt
	Pages           : 32
	Date            : 2011-03-12

In this draft, we analyze the applicability of LoopFree Alternates in
both core and access parts of Service Provider networks.  We provide
design guides to favor their applicability where relevant, typically
in the access part of the network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-lfa-applicability-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-rtgwg-lfa-applicability-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-12044538.I-D@ietf.org>


--NextPart--

From Internet-Drafts@ietf.org  Mon Mar 14 05:45:06 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D09823A6AF5; Mon, 14 Mar 2011 05:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FiA1KEBdCPrO; Mon, 14 Mar 2011 05:45:05 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F3303A6C5C; Mon, 14 Mar 2011 05:45:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-rtgwg-cl-requirement-04.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110314124502.31755.81408.idtracker@localhost>
Date: Mon, 14 Mar 2011 05:45:02 -0700
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 12:45:06 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Routing Area Working Group Working Group of the IETF.


	Title           : Requirements for MPLS Over a Composite Link
	Author(s)       : C. Villamizar, et al.
	Filename        : draft-ietf-rtgwg-cl-requirement-04.txt
	Pages           : 20
	Date            : 2011-03-14

There is often a need to provide large aggregates of bandwidth that
are best provided using parallel links between routers or MPLS LSR.
In core networks there is often no alternative since the aggregate
capacities of core networks today far exceed the capacity of a single
physical link or single packet processing element.

The presence of parallel links, with each link potentially comprised
of multiple layers has resulted in additional requirements.  Certain
services may benefit from being restricted to a subset of the
component links or a specific component link, where component link
characteristics, such as latency, differ.  Certain services require
that an LSP be treated as atomic and avoid reordering.  Other
services will continue to require only that reordering not occur
within a microflow as is current practice.

Current practice related to multipath is described briefly in an
appendix.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-cl-requirement-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-rtgwg-cl-requirement-04.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-14053159.I-D@ietf.org>


--NextPart--

From bashandy@cisco.com  Wed Mar 23 09:45:46 2011
Return-Path: <bashandy@cisco.com>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 590CA3A6844 for <rtgwg@core3.amsl.com>; Wed, 23 Mar 2011 09:45:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VxGjNceQpX7A for <rtgwg@core3.amsl.com>; Wed, 23 Mar 2011 09:45:43 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 92BBE3A67AF for <rtgwg@ietf.org>; Wed, 23 Mar 2011 09:45:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=bashandy@cisco.com; l=30137; q=dns/txt; s=iport; t=1300898837; x=1302108437; h=message-id:date:from:reply-to:mime-version:to:cc:subject; bh=EU7ziMlFK3MsAgZrrvCK8TfUKJyYOP4PMPRHQwpFh0k=; b=BSxo5D0Gb/cLCZnwAzJv+3G60OyZskxjQLZ4xLhXfhYN7vTPV5o9toro /Bt80jA4htsCFZVe/IiL1JvFopVYf3ECimj3cZMF3pybCTZFYncs3KIgP VUBF+y8HCdHmPMc1QLd8P7Jfaw2qiATf8+FbuH8UJTZkMSWqeM8HcpG8q U=;
X-Files: draft-bashandy-idr-bgp-repair-label-01.txt, signature.asc : 27296, 251
X-IronPort-AV: E=Sophos;i="4.63,232,1299456000";  d="asc'?txt'?scan'208";a="323565980"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-2.cisco.com with ESMTP; 23 Mar 2011 16:47:13 +0000
Received: from [10.21.121.36] (sjc-vpn6-292.cisco.com [10.21.121.36]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2NGl616022796; Wed, 23 Mar 2011 16:47:08 GMT
Message-ID: <4D8A2406.3070109@cisco.com>
Date: Wed, 23 Mar 2011 18:47:02 +0200
From: Ahmed Bashandy <bashandy@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: rtgwg@ietf.org
Subject: draft-bashandy-idr-bgp-repair-label-01
X-Enigmail-Version: 1.1.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1305CA9DF1005F8C5A60ACA5"
Cc: "Burjiz Pithawala \(bpithaw\)" <bpithaw@cisco.com>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bashandy@cisco.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2011 16:45:46 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig1305CA9DF1005F8C5A60ACA5
Content-Type: multipart/mixed;
 boundary="------------000001010907030906010808"

This is a multi-part message in MIME format.
--------------000001010907030906010808
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

This is a draft that proposes rerouting traffic, without waiting for BGP =
to re-converge, to another PE in a BGP-free core when a PE detects that t=
he NH is no longer reachable. Because traffic coming from the core is red=
irected back to the core, we propose using a specially advertised label t=
o make sure that the traffic does not get re-routed multiple times into t=
he core, thus avoiding loops.

The draft was sent to IDR. But of course RTGWG has historically been the =
FRR discussion arena. Unfortunately, non of the authors will be able to a=
ttend the next RTGWG meeting in Prague. But I am planning to present the =
draft during the IDR meeting.

I am attaching a newer version of the draft based on the comments that I =
got so far. I'll upload it to the ID database once ID submission is re-op=
ened

All comments now or during the IDR meeting are highly appreciated.

Ahmed


--------------000001010907030906010808
Content-Type: text/plain;
 name="draft-bashandy-idr-bgp-repair-label-01.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="draft-bashandy-idr-bgp-repair-label-01.txt"

Network Working Group                                       A. Bashandy
Internet Draft                                             B. Pithawala
Intended status: Standards Track                          Cisco Systems
Expires: September 2011                                  March 23, 2011

              Scalable, Loop-Free BGP FRR using Repair Label
                draft-bashandy-idr-bgp-repair-label-01.txt


Abstract

Consider a BGP free core scenario. Suppose the provider edge BGP
speaker PE1, PE2,..., PEn know about a prefix P/p via the external
routers CE1, CE2,..., CEm.  If the PE router PEi loses connectivity to
the primary path, whether it is another PE router or a CE router, it
desirable to immediately restore traffic by rerouting packets arriving
to PEi and destined to the prefix P/p to one of the other PE routers
that advertised P/p, say PEj, until BGP re-converges. However if the
loss of connectivity of PEi to the primary path also resulted in the
loss of connectivity between PEj and CEj, rerouting a packet before
the control plane converges may result in a loop. In this document, we
propose using a repair label for traffic restoration while avoiding
loops. We propose advertising the "repair" label through BGP.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008. The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s)
   controlling the copyright in such materials, this document may not
   be modified outside the IETF Standards Process, and derivative
   works of it may not be created outside the IETF Standards Process,
   except to format it for publication as an RFC or to translate it
   into languages other than English.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six
   months and may be updated, replaced, or obsoleted by other



Bashandy              Expires September 23, 2011               [Page 1]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   documents at any time.  It is inappropriate to use Internet-Drafts
   as reference material or to cite them other than as "work in
   progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on September 23, 2011.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with
   respect to this document. Code Components extracted from this
   document must include Simplified BSD License text as described in
   Section 4.e of the Trust Legal Provisions and are provided without
   warranty as described in the Simplified BSD License.



Table of Contents

   1. Introduction...................................................3
      1.1. Conventions used in this document.........................4
      1.2. Terminology...............................................4
   2. Protocol Operation.............................................5
      2.1. Control plane Operation...................................5
         2.1.1. Additional Rules for allocating and advertising a Repair
         label.......................................................6
      2.2. Forwarding Plane Operation on Losing Primary path
      Reachability...................................................6
      2.3. Example...................................................7
   3. How to Disseminate Repair Label Information....................9
         3.1.1. Structure of the Repair Label Path Attribute.........9
         3.1.2. Semantics of the Repair Label Attribute.............10
         3.1.3. Additional Rule when Forwarding Advertisements
         Containing the Repair Path Attribute.......................11
   4. Security Considerations.......................................11
   5. IANA Considerations...........................................11
   6. Conclusions...................................................12

Bashandy              Expires September 23, 2011               [Page 2]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   7. References....................................................12
      7.1. Normative References.....................................12
      7.2. Informative References...................................12
   8. Acknowledgments...............................................13

1. Introduction

   In a BGP free core, where traffic is tunneled between edge routers
   and edge routers assign labels to prefixes, BGP speakers advertise
   reachability information about prefixes and associate a local label
   with each prefix such as L3VPN [9], 6PE [10], and Softwire [8].
   Suppose that a given edge router is chosen as the best next-hop for
   a prefix P/p. An ingress router that receives a packet from an
   external router and destined for the prefix P/p pushes the label
   advertised by the egress edge router and then "tunnels" the packet
   across the core to that egress router. Upon receiving the labeled
   packet from the core, the egress router uses the label on the
   packet to take the appropriate forwarding decision.

   In modern networks, it is not uncommon to have a prefix reachable
   via multiple edge routers. One example is the best external path
   [7]. Another more common and widely deployed scenario is L3VPN [9]
   with multi-homed VPN sites. As an example, consider the L3VPN
   topology depicted in Figure 1.

         +--------------------------+
         |                          |
         |      BGP free Core       |
         |                          |
         |      +------------------PE1----+
         |     /                    |      \
         |    /                     |       \
         |   /                      |        \
         |  /                       |         \
         | /                        |          *
        PE3                         |          CE....... VPN prefix
         | \                        |          *          (P/p)
         |  \                       |         /
         |   \                      |        /
         |    \                     |       /
         |     \                    |      /
         |      +------------------PE2----+
         |                          |
         |                          |
         +--------------------------+

             Figure 1 VPN prefix reachable via multiple PEs



Bashandy              Expires September 23, 2011               [Page 3]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   PE3 is the ingress PE. PE1 and PE2 are both egress PEs connected to
   CE. CE advertises one or more VPN prefixes, denoted by P/p. PE1 and
   PE2 advertise P/p as VPNv4 or VPNv6 routes to all ingress PEs,
   including PE3, and associates a label with each route.

   Suppose that the ingress PE, PE3, chooses PE1 as the next-hop for
   the prefix P/p. In order to minimize traffic loss, it is highly
   desirable for PE1 to reroute all traffic destined to P/p to PE2 as
   soon as the connectivity to CE is lost and without waiting for the
   control plane (whether it is IGP or BGP) to re-converge and
   computes new the best path. In doing so, PE1 pushes the label
   advertised by PE2 for the prefix P/p, and then "tunnels" the packet
   to PE2. However if the loss of PE1-CE connectivity was due to CE
   crash, then PE2 will also reroute the traffic back to PE1,
   resulting in loop. Due to ultra scalability requirements, where
   there is a need to support thousands of peers and hundreds of
   thousands of prefixes, there is a need to support quick traffic
   restoration without waiting for the control plane to converge and
   without risking loops.

   1.1. Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
   this document are to be interpreted as described in RFC-2119 [1].

   In this document, these words will appear with that interpretation
   only when in ALL CAPS. Lower case uses of these words are not to be
   interpreted as carrying RFC-2119 significance.

   1.2. Terminology

   This section outlines the terms used in this document. For ease of
   use, we will use terms similar to those used by L3VPN [9]

   o  Protected prefix: It is a prefix P/p (of any AFI) that a BGP
      speaker has an external path to. The BGP speaker may learn about
      the prefix from an external peer through BGP, some other
      protocol, or manual configuration. The protected prefix is
      advertised to some or all the internal peers.

   o  Primary egress PE: It is an IBGP peer that can reach the
      protected prefix P/p through an external path and advertised the
      prefix to the other IBGP peers. The primary egress PE was chosen
      as the best path by one or more internal peers. In other words,
      the primary egress PE is an egress PE that will normally be used
      when there is no failure. Referring to Figure 1, PE1 is a
      primary egress PE.


Bashandy              Expires September 23, 2011               [Page 4]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   o  CE: It is an external router through which an egress PE can
      reach a prefix P/p. The router "CE" in Figure 1 is an example of
      such CE

   o  Ingress PE: It is a BGP speaker that learns about a prefix
      through another IBGP peer and chooses that IBGP peer as the
      next-hop for the prefix. PE3 in Figure 1 is an example of an
      ingress PE

   o  Repairing PE: It is the PE that attempts to restore traffic when
      the primary path is no longer reachable "without" waiting for
      BGP to re-converge. The repairing PE restores the traffic by
      rerouting the traffic (through a tunnel) towards the pre-
      calculated repair PE when it detects that the primary path
      longer reachable. The primary path may be a CE or another egress
      PE. Referring to Figure 1, if PE3 chooses PE1 as the primary
      egress PE and PE1 decides to reroute traffic to PE2 on losing
      reachability with CE, then PE1 is a repairing PE. If PE3 chooses
      PE1 as a primary path and PE3 decides to use PE2 as a repair
      path when it loses reachability to PE2, then PE3 is a repairing
      PE.

   o  Primary label: It is the label advertised by the primary egress
      PE to be used for normal traffic forwarding.

   o  Repair egress PE: It is an egress PE other than the primary
      egress PE that can reach the protected prefix P/p through an
      external neighbor. The repair PE is pre-calculated via other PEs
      prior to any failure

   o  Repair label: It is the label that will be pushed on the packet
      when the repairing PE reroutes the traffic (through a tunnel)
      towards the repair egress PE. Section 2. discusses how the
      repair label is used. Section 3. discusses semantics of and the
      method for disseminating repair label information.

   o  Repair path: It is the repair egress PE and the repair label.

2. Protocol Operation

   This section explains the operation of the control and forwarding
   planes of routers participating BGP-free core traffic restoration.

   2.1. Control plane Operation

   1. As usual, each PE allocates a local label for each prefix it can
      reach through an external neighbor CE. This is the primary label
      used for normal traffic forwarding.


Bashandy              Expires September 23, 2011               [Page 5]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   2. To provide repair path information to all PEs, the PE also
      allocates a repair label to the prefix if it can reach that
      prefix via an external neighbor. Different repair label
      allocation schemes are proposed in Section 3.

   3. The PE advertises both the primary and repair labels to all IBGP
      peers.

   4. When a PE receives the label advertisement from egress PEs, it
      calculates a primary egress PE and a repair egress PE based on
      its internal path selection criteria. Note that the method of
      choosing the repair path is beyond the scope of this document.

   5. In the end, for some of the prefix advertised by more than one
      PE, a PE will have

       o a primary path

       o a repair path consisting of a repair PE and a repair label
          advertised by the chosen repair PE.

   6. A PE "never" protects a repair label. Hence on any PE, a repair
      label only has paths towards the CE. However a primary label may
      have a repair path towards a chosen repair PE

2.1.1. Additional Rules for allocating and advertising a Repair label

   o  A repairing PE MUST NOT advertise a repair for a prefix if it does
      NOT have an external path to the prefix

   o  A repairing PE MUST NOT associate an internal path with a repair
      label

   o  Repair labels SHOULD be advertised with labeled address families
      only. That is AFI/SAFI 1/4, 2/4, 1/128, and 2/128.



   2.2. Forwarding Plane Operation on Losing Primary path
      Reachability

   As soon as a PE loses reachability to the primary path of the
   protected prefix P/p, the forwarding plane processes arriving
   traffic as follows:






Bashandy              Expires September 23, 2011               [Page 6]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   1. If the repairing PE is an egress PE, the packet arrives at the
      repairing PE with the primary label at the top because the packet
      is "tunneled" from the ingress PE(s). In that case, the repairing
      PE swaps the incoming label stack with the "repair label stack"
      advertised by the repair egress PE. Section 3.1.2. specifies all
      the details

   2. If the repairing PE is an ingress PE, it pushes the "repair label
      stack" advertised by the repair egress PE. Section 3.1.2.
      specifies all the details

   3. The repairing PE tunnels the packet to the repair PE

   4. At the repair PE, the packet arrives with the repair label at
      the top. The repair PE uses the incoming label stack to take
      forwarding decisions

   5. If the repair egress PE can reach the CE, the repair PE forwards
      the packet towards the CE.

   6. If the repair PE cannot reach the CE, the traffic will be
      dropped because a PE never protects a repair label

   2.3. Example

   Consider the L3VPN [9] topology depicted in Figure 2 where two PEs
   are connected to the same PE. Assume that the core is LDP. We will
   be using an advertised repair label.

                                  PE1
                                     \
                                      \
                                       \
                                        \
               LDP core                 CE....... VPN prefix
                                        /        (10.0.0.0/8)
                                       /
                                      /
                                     /
                                   PE2

                        Figure 2 : L3VPN Example



   PE1: Repairing egress PE
   PE2: repair PE
   Primary VPN label advertised by PE1 to all PEs 4000
   Repair VPN label advertised by PE1 to all PEs 5000

Bashandy              Expires September 23, 2011               [Page 7]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   Primary VPN label advertised by PE2 to all PEs: 2000
   Repair VPN label advertised by PE2 all PEs: 3000

   LDP label for PE2 on PE1 is 1234
   LDP label for PE1 on PE2 is 4567

   Before failure
   '''''''''''''''
   PE1 has the following FIB entries

   4000 -----> CE (unlabeled)
        -----> PE2, swap 4000 with 3000 and then push 1234
   5000 -----> CE (unlabeled)

   PE2 has the following
   2000 -----> CE (unlabeled)
        -----> PE1, swap 2000 with 5000 and then push 4567
   3000 ------> CE (unlabeled)

   After the CE crashes
   ''''''''''''''''''''
   PE1 has the following entry:
   4000 -----> PE2, swap 4000 with 3000 and then push 1234
   5000 -----> Drop


   PE2 has the following
   2000 -----> PE1, swap 2000 with 5000 and then push 4567
   3000 ------> Drop


   Because of the above routing entries, any traffic arriving from the
   core at PE1 and destined for 10.0.0/8,  is rerouted towards PE2
   using the repair VPN label 3000. PE2 will just drop it instead of
   looping it back towards PE1.

   After the link between PE and CE fails (CE did not crash)
   '''''''''''''''''''''''''''''''''''''''''''''''''''''''''
   PE1 has the following entry:
   4000 -----> PE2, swap 4000 with 3000 and then push 1234
   5000 -----> Drop

   PE2 has the following
   2000 -----> CE (unlabeled)
        -----> PE1, swap 2000 with 5000 and then push 4567
   3000 ------> CE


   Because of the above routing entries, any traffic arriving from the

Bashandy              Expires September 23, 2011               [Page 8]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   core at PE1 and destined for 10.0.0/8 is rerouted towards PE2 using
   the repair VPN label 3000. PE2 will forward the traffic towards CE.

3. How to Disseminate Repair Label Information

   We propose advertise the repair label as an optional path
   attribute. Advertising the repair label as an optional path
   attributes has some advantages:

   o  An egress PE can benefits from a scalable repair label
      allocation schemes such as per-CE repair label allocation

   o  Allows the repairing PE to share the same repair path among
      multiple protected prefixes. Since the repair path is shared by
      all labels sharing the path attribute, the repairing PE can
      optimize its RIB and FIB by sharing the same repair path data
      structure among a large number of protected prefixes.

   o  Reduces the BGP update message size. Instead of having to send
      additional labels per prefix, multiple prefixes can share the
      same repair label

   o  The number of labels used for traffic restoration does not
      depend on the number of protected prefixes

   o  Allows for incremental deployment because the attribute is
      optional

   The main disadvantage of sharing the same repair path among
   multiple primary paths is loss of fine grain control. It is not
   possible to manage, control, or provide differentiated handling to
   traffic on per prefix basis until the network re-converges. The
   loss of fine grain control is limited to the BGP re-convergence
   period.

   It is noteworthy to mention that per-CE repair label allocation has
   some advantages over per-prefix repair label allocation. First it
   results in using fewer labels. Second it allows for better packing
   in BGP messages. Third it does not require special handling in the
   forwarding plane at the repair PE. Fourth it simplifies the
   forwarding plane while maximizing the packet switching performance
   because the egress PE can take a forwarding decision with a single
   FIB lookup.

3.1.1. Structure of the Repair Label Path Attribute

   This document defines the repair label attribute as an optional
   non-transitive path attribute [2] as follows:


Bashandy              Expires September 23, 2011               [Page 9]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

      Attribute name: REPAIR_LABEL

      Type code: TBD

      Attribute Flags:

         Optional bit: 1

         Transitive bit: 0

         Partial bit: 0

         Extended Length bit: 0

      Length of the attribute: It indicates the length in octets of
      the attribute

      Attribute Value: The attribute value contains a stack of one or
      more labels. The encoding of the labels is identical to encoding
      of the "label" field in [4]. The value of the bottom of stack
      (BOS) bit is determined at traffic restoration time as specified
      in Section 3.1.2.

3.1.2. Semantics of the Repair Label Attribute

   This document specifies the semantics of the repair label attribute
   when the attribute carries one repair label only. The semantics of
   more than one repair label is beyond the scope of this document.

   Suppose a BGP speaker PE1 receives an update message with a repair
   label attribute containing the label "Lr2" from the IBGP peer PE2.
   Suppose the NLRI in the MP_REACH_NLRI attribute [3] contains the
   prefixes R1, R2,. . . , Rn each bound to a label L21, L22,. . . ,
   L2n, respectively. This means the following:

   1. PE2 will never attempt to repair a packet arriving with the
      label "Lr". Hence PE2 will either forward the packet to an
      external CE or drop the packet

   2. PE2 expects the following from PE1:

       a. Case a: The route Ri on PE1 is bound to a local label "L1i".
          Suppose PE1 receives a packet with the label "L1i" at the
          top of the stack. If the PE1 loses the primary path for a
          prefix Ri and PE1 decides that PE2 is the repair PE for the
          prefix Ri, then PE1 has to swap the label "L1i" on the
          packet with the repair label "Lr2" and then tunnel the
          packet to PE2. The bottom of stack (BOS) bit MUST be copied
          from the label arriving on the packet to the label "Lr2"

Bashandy              Expires September 23, 2011              [Page 10]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

       b. Case b: The router Ri on PE1 is not bound to any local
          label. If the PE1 loses the primary path for a prefix Ri and
          PE1 decides that PE2 is the repair PE for the prefix Ri,
          then PE1 MUST push the label "Lr2" and then tunnel the
          packet to PE2. The bottom of stack (BOS) bit in "Lr2" MUST
          be set as specified in [5].

3.1.3. Additional Rule when Forwarding Advertisements Containing the
   Repair Path Attribute

   As specified in Section 3.1.1. the repair label attribute is a non-
   transitive attribute. However there may be cases, such as inter-AS
   option (b)[9], route reflectors [11], or confederation [12], where
   a router may replace the advertised next-hop with its own before
   forwarding an advertisement. If a BGP speaker replaces the next-hop
   attribute with its own and the advertisement contains a repair
   label attribute with label stack "Sr", there are two options

   o  Option 1: The BGP speaker MUST NOT advertise the repair label
      attribute

   o  Option 2: The BGP speaker MUST replace the repair label stack
      "Sr" with a locally allocated label stack "Sr1" before
      advertising the route and then advertise the stack "Sr1" in the
      repair label attribute. For the forwarding plane, the BGP
      speaker MUST install a swap forwarding entry such that if the
      BGP speaker receives a packet with the label stack "Sr1", it
      swaps "Sr1" with the stack "Sr".

   Note that advertising the repair label attribute by the router
   depends on whether the router understands the semantics of and
   supports the repair label attribute at the time of receiving an
   advertisement containing the repair label attribute.

4. Security Considerations

   No additional security risk is introduced by using the mechanisms
   proposed in this document

5. IANA Considerations

   This document defines a new BGP path attribute. IANA maintains a
   list of the current BGP attribute typecodes in [6]. This document
   proposes defining a new typecode value of "TBD" for the
   REPAIR_LABEL path attribute





Bashandy              Expires September 23, 2011              [Page 11]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

6. Conclusions

   This document proposes using a repair label to allow restoring
   traffic prior to BGP convergence while avoiding loops

7. References

   7.1. Normative References

   [1]   Bradner, S., "Key words for use in RFCs to Indicate
         Requirement Levels", BCP 14, RFC 2119, March 1997.

   [2]   Rekhter, Y., Li, T., and S. Hares, "A Border Gateway Protocol
         4 (BGP-4), RFC 4271, January 2006

   [3]   Bates, T., Chandra, R., Katz, D., and Rekhter Y.,
         "Multiprotocol Extensions for BGP", RFC 4760, January 2007

   [4]   Rosen, E., Rekhter, Y., "Carrying Label Information in BGP-
         4", RFC 3107, May 2001

   [5]   Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci,
         D., Li, T. and A. Conta, "MPLS Label Stack Encoding", RFC
         3032, January 2001.

   7.2. Informative References

   [6]   BGP Parameters, http://www.iana.org/assignments/bgp-
         parameters/bgp-parameters.xhtml

   [7]   Marques,P., Fernando, R., Chen, E, Mohapatra, P.,
         "Advertisement of the best external route in BGP", draft-
         ietf-idr-best-external-02.txt, April 2004.

   [8]   Wu, J., Cui, Y., Metz, C., and E. Rosen, "Softwire Mesh
         Framework", RFC 5565, June 2009.

   [9]   Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
         Networks (VPNs)", RFC 4364, February 2006.

   [10]  De Clercq, J. , Ooms, D., Prevost, S., Le Faucheur, F.,
         Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider
         Edge Routers (6PE)", RFC 4798, February 2007

   [11]  Bates, T., Chen, E., and Chandra, R., "BGP Route Reflection:
         An Alternative to Full Mesh Internal BGP (IBGP)", RFC 4456,
         April 2006



Bashandy              Expires September 23, 2011              [Page 12]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   [12]  Traina, P., McPherson, P., and Scudder, J., "Autonomous
         System Confederations for BGP", RFC 5065, August 2007

8. Acknowledgments

   Special thanks to Keyur Patel, Robert Raszuk, and Eric Rosen for
   the valuable comments

   This document was prepared using 2-Word-v2.0.template.dot.

Authors' Addresses

   Ahmed Bashandy
   Cisco Systems
   170 West Tasman Dr, San Jose, CA 95134
   Email: bashandy@cisco.com

   Burjiz Pithawala
   Cisco Systems
   170 West Tasman Dr, San Jose, CA 95134
   Email: bpithaw@cisco.com





























Bashandy              Expires September 23, 2011              [Page 13]
=0C

--------------000001010907030906010808--

--------------enig1305CA9DF1005F8C5A60ACA5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFNiiQG+G19kFA5zIYRAoQ7AJ9KM4Rqm+HvLplMyRzmdjbhYWNFAACeO7Pu
ikeNMYG+0DPqKAJzxHznS+Q=
=1anw
-----END PGP SIGNATURE-----

--------------enig1305CA9DF1005F8C5A60ACA5--

From wim.henderickx@alcatel-lucent.com  Wed Mar 23 11:47:50 2011
Return-Path: <wim.henderickx@alcatel-lucent.com>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 084193A68C7 for <rtgwg@core3.amsl.com>; Wed, 23 Mar 2011 11:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.136
X-Spam-Level: 
X-Spam-Status: No, score=-4.136 tagged_above=-999 required=5 tests=[AWL=-1.887, BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lpy-aR5JI552 for <rtgwg@core3.amsl.com>; Wed, 23 Mar 2011 11:47:47 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by core3.amsl.com (Postfix) with ESMTP id E7B403A6941 for <rtgwg@ietf.org>; Wed, 23 Mar 2011 11:47:46 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p2NInCiY030042 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 23 Mar 2011 19:49:14 +0100
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.43]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Wed, 23 Mar 2011 19:49:13 +0100
From: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
To: "bashandy@cisco.com" <bashandy@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Wed, 23 Mar 2011 19:49:10 +0100
Subject: RE: draft-bashandy-idr-bgp-repair-label-01
Thread-Topic: draft-bashandy-idr-bgp-repair-label-01
Thread-Index: AcvpegFmeq+6tdNjQBGZjmZcv1h6AAAEOyJQ
Message-ID: <14C7F4F06DB5814AB0DE29716C4F6D67181A8A83@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
References: <4D8A2406.3070109@cisco.com>
In-Reply-To: <4D8A2406.3070109@cisco.com>
Accept-Language: nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: nl-NL, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.84
Cc: "Burjiz Pithawala \(bpithaw\)" <bpithaw@cisco.com>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2011 18:47:50 -0000

Ahmed, do you believe this should also work for LBL per NH and LBL per serv=
ice in a VRF ?

-----Original Message-----
From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of A=
hmed Bashandy
Sent: woensdag 23 maart 2011 17:47
To: rtgwg@ietf.org
Cc: Burjiz Pithawala (bpithaw)
Subject: draft-bashandy-idr-bgp-repair-label-01

Hi,

This is a draft that proposes rerouting traffic, without waiting for BGP to=
 re-converge, to another PE in a BGP-free core when a PE detects that the N=
H is no longer reachable. Because traffic coming from the core is redirecte=
d back to the core, we propose using a specially advertised label to make s=
ure that the traffic does not get re-routed multiple times into the core, t=
hus avoiding loops.

The draft was sent to IDR. But of course RTGWG has historically been the FR=
R discussion arena. Unfortunately, non of the authors will be able to atten=
d the next RTGWG meeting in Prague. But I am planning to present the draft =
during the IDR meeting.

I am attaching a newer version of the draft based on the comments that I go=
t so far. I'll upload it to the ID database once ID submission is re-opened

All comments now or during the IDR meeting are highly appreciated.

Ahmed


From bashandy@cisco.com  Thu Mar 24 02:22:43 2011
Return-Path: <bashandy@cisco.com>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D57AB3A6836 for <rtgwg@core3.amsl.com>; Thu, 24 Mar 2011 02:22:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.449
X-Spam-Level: 
X-Spam-Status: No, score=-10.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6vc5rlvXuY0O for <rtgwg@core3.amsl.com>; Thu, 24 Mar 2011 02:22:42 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id A6DDD3A6847 for <rtgwg@ietf.org>; Thu, 24 Mar 2011 02:22:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=bashandy@cisco.com; l=2390; q=dns/txt; s=iport; t=1300958657; x=1302168257; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=Jx6JgK5glDvUZspPdRL8D8NQoiyKKOhjiD1ojR458NQ=; b=Rnab0mCQnwZSMSriM6MEqniXPXwfGK02R9nVtVvV1orQ0/Mp32Uzd+P6 rXdvjJN/PZOSxi30bxkxH7NYMUMJ0+4QgJoatIkAFia6oJy8uIOg7RqrI /jftrHtnRaxQ8JIp37iZqXolteMQtAa/rM1qXSFdKQ47iAfBOfJBQ35Rg 4=;
X-Files: signature.asc : 251
X-IronPort-AV: E=Sophos;i="4.63,236,1299456000";  d="asc'?scan'208";a="351620605"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-5.cisco.com with ESMTP; 24 Mar 2011 09:24:17 +0000
Received: from [10.21.77.126] ([10.21.77.126]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2O9ODxh013831; Thu, 24 Mar 2011 09:24:15 GMT
Message-ID: <4D8B0DB7.7030300@cisco.com>
Date: Thu, 24 Mar 2011 11:24:07 +0200
From: Ahmed Bashandy <bashandy@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
Subject: Re: draft-bashandy-idr-bgp-repair-label-01
References: <4D8A2406.3070109@cisco.com> <14C7F4F06DB5814AB0DE29716C4F6D67181A8A83@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
In-Reply-To: <14C7F4F06DB5814AB0DE29716C4F6D67181A8A83@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig2DBB626E754FA7DBB72A6BCC"
Cc: "Burjiz Pithawala \(bpithaw\)" <bpithaw@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bashandy@cisco.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2011 09:22:44 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig2DBB626E754FA7DBB72A6BCC
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Both the primary and repair label allocation can be anything (at least th=
is is our intention). However, as pointed out near the end of page 9, per=
 NH (we call it per-CE) repair label allocation is preferred in the sense=
 that optimizes both control and forwarding planes.

Thanks

Ahmed


On 3/23/2011 8:49 PM, Henderickx, Wim (Wim) wrote:
> Ahmed, do you believe this should also work for LBL per NH and LBL per =
service in a VRF ?
>
> -----Original Message-----
> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf =
Of Ahmed Bashandy
> Sent: woensdag 23 maart 2011 17:47
> To: rtgwg@ietf.org
> Cc: Burjiz Pithawala (bpithaw)
> Subject: draft-bashandy-idr-bgp-repair-label-01
>
> Hi,
>
> This is a draft that proposes rerouting traffic, without waiting for BG=
P to re-converge, to another PE in a BGP-free core when a PE detects that=
 the NH is no longer reachable. Because traffic coming from the core is r=
edirected back to the core, we propose using a specially advertised label=
 to make sure that the traffic does not get re-routed multiple times into=
 the core, thus avoiding loops.
>
> The draft was sent to IDR. But of course RTGWG has historically been th=
e FRR discussion arena. Unfortunately, non of the authors will be able to=
 attend the next RTGWG meeting in Prague. But I am planning to present th=
e draft during the IDR meeting.
>
> I am attaching a newer version of the draft based on the comments that =
I got so far. I'll upload it to the ID database once ID submission is re-=
opened
>
> All comments now or during the IDR meeting are highly appreciated.
>
> Ahmed
>


--------------enig2DBB626E754FA7DBB72A6BCC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFNiw29+G19kFA5zIYRAuppAJ9Ps7WQbNbGIK8cL3QaPBr/S40fOwCeJhlL
h8XX58vfl9+jcHKIwUQ87X8=
=jpxV
-----END PGP SIGNATURE-----

--------------enig2DBB626E754FA7DBB72A6BCC--

From wim.henderickx@alcatel-lucent.com  Thu Mar 24 04:33:36 2011
Return-Path: <wim.henderickx@alcatel-lucent.com>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 89A273A687A for <rtgwg@core3.amsl.com>; Thu, 24 Mar 2011 04:33:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.192
X-Spam-Level: 
X-Spam-Status: No, score=-5.192 tagged_above=-999 required=5 tests=[AWL=1.057,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EXvNgL-9htwY for <rtgwg@core3.amsl.com>; Thu, 24 Mar 2011 04:33:35 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id 6C6D63A6806 for <rtgwg@ietf.org>; Thu, 24 Mar 2011 04:33:35 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p2OBZ5Hr010768 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 24 Mar 2011 12:35:06 +0100
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.43]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Thu, 24 Mar 2011 12:34:49 +0100
From: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
To: "bashandy@cisco.com" <bashandy@cisco.com>
Date: Thu, 24 Mar 2011 12:34:50 +0100
Subject: RE: draft-bashandy-idr-bgp-repair-label-01
Thread-Topic: draft-bashandy-idr-bgp-repair-label-01
Thread-Index: AcvqBUQrD2wtdZz4RMedTuvbtgZLOwAEUsGA
Message-ID: <14C7F4F06DB5814AB0DE29716C4F6D67181A8CA4@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
References: <4D8A2406.3070109@cisco.com> <14C7F4F06DB5814AB0DE29716C4F6D67181A8A83@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <4D8B0DB7.7030300@cisco.com>
In-Reply-To: <4D8B0DB7.7030300@cisco.com>
Accept-Language: nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: nl-NL, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Cc: "Burjiz Pithawala \(bpithaw\)" <bpithaw@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2011 11:33:36 -0000

Ahmed, in case of LBL per VRF when an IP lookup is done, how are you going =
to deal with this when also a repair LBL is used. In this case when a CE li=
nk fails you have to do a NH re-write for the prefix using either the repai=
r LBL or a different NH advertized by BGP with a different RD.

You should clarify this case I believe.

-----Original Message-----
From: Ahmed Bashandy [mailto:bashandy@cisco.com]=20
Sent: donderdag 24 maart 2011 10:24
To: Henderickx, Wim (Wim)
Cc: rtgwg@ietf.org; Burjiz Pithawala (bpithaw)
Subject: Re: draft-bashandy-idr-bgp-repair-label-01

Both the primary and repair label allocation can be anything (at least this=
 is our intention). However, as pointed out near the end of page 9, per NH =
(we call it per-CE) repair label allocation is preferred in the sense that =
optimizes both control and forwarding planes.

Thanks

Ahmed


On 3/23/2011 8:49 PM, Henderickx, Wim (Wim) wrote:
> Ahmed, do you believe this should also work for LBL per NH and LBL per se=
rvice in a VRF ?
>
> -----Original Message-----
> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of=
 Ahmed Bashandy
> Sent: woensdag 23 maart 2011 17:47
> To: rtgwg@ietf.org
> Cc: Burjiz Pithawala (bpithaw)
> Subject: draft-bashandy-idr-bgp-repair-label-01
>
> Hi,
>
> This is a draft that proposes rerouting traffic, without waiting for BGP =
to re-converge, to another PE in a BGP-free core when a PE detects that the=
 NH is no longer reachable. Because traffic coming from the core is redirec=
ted back to the core, we propose using a specially advertised label to make=
 sure that the traffic does not get re-routed multiple times into the core,=
 thus avoiding loops.
>
> The draft was sent to IDR. But of course RTGWG has historically been the =
FRR discussion arena. Unfortunately, non of the authors will be able to att=
end the next RTGWG meeting in Prague. But I am planning to present the draf=
t during the IDR meeting.
>
> I am attaching a newer version of the draft based on the comments that I =
got so far. I'll upload it to the ID database once ID submission is re-open=
ed
>
> All comments now or during the IDR meeting are highly appreciated.
>
> Ahmed
>


From bashandy@cisco.com  Thu Mar 24 07:20:09 2011
Return-Path: <bashandy@cisco.com>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B624E28C102 for <rtgwg@core3.amsl.com>; Thu, 24 Mar 2011 07:20:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.198
X-Spam-Level: 
X-Spam-Status: No, score=-10.198 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EHZIyCsiBtYG for <rtgwg@core3.amsl.com>; Thu, 24 Mar 2011 07:20:06 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 7127328C115 for <rtgwg@ietf.org>; Thu, 24 Mar 2011 07:20:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=bashandy@cisco.com; l=38438; q=dns/txt; s=iport; t=1300976500; x=1302186100; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=L/0I38Qmeal/svF0aH4Eeu11VyExocwe5mfrKlOA4BA=; b=EWrbnolpQ2xg+BRfmt3RNiZk4RpqAeFPakYWFW/UX9VdgqQJBacyrF1H 4zfEOZKx9x+kW5eM2Y0nXHvbGdo0AQEnwHGbrd6rJd4zO2uJ/m4XQjSfO iepra3fKTgrprFHI+udsdnanWqbXjsKrcFHmdY8d1w57n5WQUaL63SV+K A=;
X-Files: draft-bashandy-idr-bgp-repair-label-01.txt, signature.asc : 27918, 251
X-IronPort-AV: E=Sophos;i="4.63,237,1299456000";  d="asc'?txt'?scan'208,217";a="417798624"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-1.cisco.com with ESMTP; 24 Mar 2011 14:21:40 +0000
Received: from [10.21.148.142] (sjc-vpn7-1166.cisco.com [10.21.148.142]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2OELYws030174; Thu, 24 Mar 2011 14:21:35 GMT
Message-ID: <4D8B5372.6040307@cisco.com>
Date: Thu, 24 Mar 2011 16:21:38 +0200
From: Ahmed Bashandy <bashandy@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
Subject: Re: draft-bashandy-idr-bgp-repair-label-01
References: <4D8A2406.3070109@cisco.com> <14C7F4F06DB5814AB0DE29716C4F6D67181A8A83@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <4D8B0DB7.7030300@cisco.com> <14C7F4F06DB5814AB0DE29716C4F6D67181A8CA4@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
In-Reply-To: <14C7F4F06DB5814AB0DE29716C4F6D67181A8CA4@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0C8BA67CB742A078473FDB71"
Cc: "Burjiz Pithawala \(bpithaw\)" <bpithaw@cisco.com>, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bashandy@cisco.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2011 14:20:09 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig0C8BA67CB742A078473FDB71
Content-Type: multipart/mixed;
 boundary="------------080008060403030804010107"

This is a multi-part message in MIME format.
--------------080008060403030804010107
Content-Type: multipart/alternative;
 boundary="------------040704020902060407080002"


--------------040704020902060407080002
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I agree that this part is not clear in the draft.

Multiple lookups are needed to decide the primary NH for any aggregate la=
bel (e.g. per-VRF). Eventually there will either be a label lookup or an =
IP lookup that points to the primary NH.
If it is a label, then item 2.a in section 3.1.2 specifies how to handle =
the case of loosing the primary NH
If it is an IP lookup, then it is similar to the case where the repairing=
 PE is an ingress PE. Item 2.b in Section 3.1.2 describes how to deal wit=
h loosing the primary NH in this case

Thanks for catching it :-) . I added item (2.c) in Section 3.1.2 to cover=
 this case. The modified draft is attached

Thanks

Ahmed




On 3/24/2011 1:34 PM, Henderickx, Wim (Wim) wrote:
>
> Ahmed, in case of LBL per VRF when an IP lookup is done, how are you go=
ing to deal with this when also a repair LBL is used. In this case when a=
 CE link fails you have to do a NH re-write for the prefix using either t=
he repair LBL or a different NH advertized by BGP with a different RD.
>
> You should clarify this case I believe.
>
> -----Original Message-----
> From: Ahmed Bashandy [mailto:bashandy@cisco.com]
> Sent: donderdag 24 maart 2011 10:24
> To: Henderickx, Wim (Wim)
> Cc: rtgwg@ietf.org; Burjiz Pithawala (bpithaw)
> Subject: Re: draft-bashandy-idr-bgp-repair-label-01
>
> Both the primary and repair label allocation can be anything (at least =
this is our intention). However, as pointed out near the end of page 9, p=
er NH (we call it per-CE) repair label allocation is preferred in the sen=
se that optimizes both control and forwarding planes.
>
> Thanks
>
> Ahmed
>
>
> On 3/23/2011 8:49 PM, Henderickx, Wim (Wim) wrote:
> > Ahmed, do you believe this should also work for LBL per NH and LBL pe=
r service in a VRF ?
> >
> > -----Original Message-----
> > From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behal=
f Of Ahmed Bashandy
> > Sent: woensdag 23 maart 2011 17:47
> > To: rtgwg@ietf.org
> > Cc: Burjiz Pithawala (bpithaw)
> > Subject: draft-bashandy-idr-bgp-repair-label-01
> >
> > Hi,
> >
> > This is a draft that proposes rerouting traffic, without waiting for =
BGP to re-converge, to another PE in a BGP-free core when a PE detects th=
at the NH is no longer reachable. Because traffic coming from the core is=
 redirected back to the core, we propose using a specially advertised lab=
el to make sure that the traffic does not get re-routed multiple times in=
to the core, thus avoiding loops.
> >
> > The draft was sent to IDR. But of course RTGWG has historically been =
the FRR discussion arena. Unfortunately, non of the authors will be able =
to attend the next RTGWG meeting in Prague. But I am planning to present =
the draft during the IDR meeting.
> >
> > I am attaching a newer version of the draft based on the comments tha=
t I got so far. I'll upload it to the ID database once ID submission is r=
e-opened
> >
> > All comments now or during the IDR meeting are highly appreciated.
> >
> > Ahmed
> >
>

--------------040704020902060407080002
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content=3D"text/html; charset=3DISO-8859-1"
      http-equiv=3D"Content-Type">
  </head>
  <body text=3D"#000000" bgcolor=3D"#ffffff">
    I agree that this part is not clear in the draft.<br>
    <br>
    Multiple lookups are needed to decide the primary NH for any
    aggregate label (e.g. per-VRF). Eventually there will either be a
    label lookup or an IP lookup that points to the primary NH. <br>
    If it is a label, then item 2.a in section 3.1.2 specifies how to
    handle the case of loosing the primary NH<br>
    If it is an IP lookup, then it is similar to the case where the
    repairing PE is an ingress PE. Item 2.b in Section 3.1.2 describes
    how to deal with loosing the primary NH in this case<br>
    <br>
    Thanks for catching it <span class=3D"moz-smiley-s1"><span> :-) </spa=
n></span>.
    I added item (2.c) in Section 3.1.2 to cover this case. The modified
    draft is attached<br>
    <br>
    Thanks<br>
    <br>
    Ahmed<br>
    <br>
    <br>
    <br>
    <br>
    On 3/24/2011 1:34 PM, Henderickx, Wim (Wim) wrote:
    <blockquote
cite=3D"mid:14C7F4F06DB5814AB0DE29716C4F6D67181A8CA4@FRMRSSXCHMBSB1.dc-m.=
alcatel-lucent.com"
      type=3D"cite">
      <meta http-equiv=3D"Content-Type" content=3D"text/html;
        charset=3DISO-8859-1">
      <meta name=3D"Generator" content=3D"MS Exchange Server version
        6.5.7655.10">
      <title>RE: draft-bashandy-idr-bgp-repair-label-01</title>
      <!-- Converted from text/plain format -->
      <p><font size=3D"2">Ahmed, in case of LBL per VRF when an IP lookup=

          is done, how are you going to deal with this when also a
          repair LBL is used. In this case when a CE link fails you have
          to do a NH re-write for the prefix using either the repair LBL
          or a different NH advertized by BGP with a different RD.<br>
          <br>
          You should clarify this case I believe.<br>
          <br>
          -----Original Message-----<br>
          From: Ahmed Bashandy [<a moz-do-not-send=3D"true"
            href=3D"mailto:bashandy@cisco.com">mailto:bashandy@cisco.com<=
/a>]<br>
          Sent: donderdag 24 maart 2011 10:24<br>
          To: Henderickx, Wim (Wim)<br>
          Cc: <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:rtgwg@=
ietf.org">rtgwg@ietf.org</a>; Burjiz Pithawala (bpithaw)<br>
          Subject: Re: draft-bashandy-idr-bgp-repair-label-01<br>
          <br>
          Both the primary and repair label allocation can be anything
          (at least this is our intention). However, as pointed out near
          the end of page 9, per NH (we call it per-CE) repair label
          allocation is preferred in the sense that optimizes both
          control and forwarding planes.<br>
          <br>
          Thanks<br>
          <br>
          Ahmed<br>
          <br>
          <br>
          On 3/23/2011 8:49 PM, Henderickx, Wim (Wim) wrote:<br>
          &gt; Ahmed, do you believe this should also work for LBL per
          NH and LBL per service in a VRF ?<br>
          &gt;<br>
          &gt; -----Original Message-----<br>
          &gt; From: <a class=3D"moz-txt-link-abbreviated" href=3D"mailto=
:rtgwg-bounces@ietf.org">rtgwg-bounces@ietf.org</a> [<a moz-do-not-send=3D=
"true"
            href=3D"mailto:rtgwg-bounces@ietf.org">mailto:rtgwg-bounces@i=
etf.org</a>]
          On Behalf Of Ahmed Bashandy<br>
          &gt; Sent: woensdag 23 maart 2011 17:47<br>
          &gt; To: <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:r=
tgwg@ietf.org">rtgwg@ietf.org</a><br>
          &gt; Cc: Burjiz Pithawala (bpithaw)<br>
          &gt; Subject: draft-bashandy-idr-bgp-repair-label-01<br>
          &gt;<br>
          &gt; Hi,<br>
          &gt;<br>
          &gt; This is a draft that proposes rerouting traffic, without
          waiting for BGP to re-converge, to another PE in a BGP-free
          core when a PE detects that the NH is no longer reachable.
          Because traffic coming from the core is redirected back to the
          core, we propose using a specially advertised label to make
          sure that the traffic does not get re-routed multiple times
          into the core, thus avoiding loops.<br>
          &gt;<br>
          &gt; The draft was sent to IDR. But of course RTGWG has
          historically been the FRR discussion arena. Unfortunately, non
          of the authors will be able to attend the next RTGWG meeting
          in Prague. But I am planning to present the draft during the
          IDR meeting.<br>
          &gt;<br>
          &gt; I am attaching a newer version of the draft based on the
          comments that I got so far. I'll upload it to the ID database
          once ID submission is re-opened<br>
          &gt;<br>
          &gt; All comments now or during the IDR meeting are highly
          appreciated.<br>
          &gt;<br>
          &gt; Ahmed<br>
          &gt;<br>
          <br>
        </font>
      </p>
    </blockquote>
  </body>
</html>

--------------040704020902060407080002--

--------------080008060403030804010107
Content-Type: text/plain;
 name="draft-bashandy-idr-bgp-repair-label-01.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="draft-bashandy-idr-bgp-repair-label-01.txt"

Network Working Group                                       A. Bashandy
Internet Draft                                             B. Pithawala
Intended status: Standards Track                          Cisco Systems
Expires: September 2011                                  March 24, 2011

              Scalable, Loop-Free BGP FRR using Repair Label
                draft-bashandy-idr-bgp-repair-label-01.txt


Abstract

Consider a BGP free core scenario. Suppose the provider edge BGP
speaker PE1, PE2,..., PEn know about a prefix P/p via the external
routers CE1, CE2,..., CEm.  If the PE router PEi loses connectivity to
the primary path, whether it is another PE router or a CE router, it
desirable to immediately restore traffic by rerouting packets arriving
to PEi and destined to the prefix P/p to one of the other PE routers
that advertised P/p, say PEj, until BGP re-converges. However if the
loss of connectivity of PEi to the primary path also resulted in the
loss of connectivity between PEj and CEj, rerouting a packet before
the control plane converges may result in a loop. In this document, we
propose using a repair label for traffic restoration while avoiding
loops. We propose advertising the "repair" label through BGP.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008. The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s)
   controlling the copyright in such materials, this document may not
   be modified outside the IETF Standards Process, and derivative
   works of it may not be created outside the IETF Standards Process,
   except to format it for publication as an RFC or to translate it
   into languages other than English.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six
   months and may be updated, replaced, or obsoleted by other



Bashandy              Expires September 24, 2011               [Page 1]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   documents at any time.  It is inappropriate to use Internet-Drafts
   as reference material or to cite them other than as "work in
   progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on September 24, 2011.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with
   respect to this document. Code Components extracted from this
   document must include Simplified BSD License text as described in
   Section 4.e of the Trust Legal Provisions and are provided without
   warranty as described in the Simplified BSD License.



Table of Contents

   1. Introduction...................................................3
      1.1. Conventions used in this document.........................4
      1.2. Terminology...............................................4
   2. Protocol Operation.............................................5
      2.1. Control plane Operation...................................5
         2.1.1. Additional Rules for allocating and advertising a Repair
         label.......................................................6
      2.2. Forwarding Plane Operation on Losing Primary path
      Reachability...................................................6
      2.3. Example...................................................7
   3. How to Disseminate Repair Label Information....................9
         3.1.1. Structure of the Repair Label Path Attribute.........9
         3.1.2. Semantics of the Repair Label Attribute.............10
         3.1.3. Additional Rule when Forwarding Advertisements
         Containing the Repair Path Attribute.......................11
   4. Security Considerations.......................................12
   5. IANA Considerations...........................................12
   6. Conclusions...................................................12

Bashandy              Expires September 24, 2011               [Page 2]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   7. References....................................................12
      7.1. Normative References.....................................12
      7.2. Informative References...................................12
   8. Acknowledgments...............................................13

1. Introduction

   In a BGP free core, where traffic is tunneled between edge routers
   and edge routers assign labels to prefixes, BGP speakers advertise
   reachability information about prefixes and associate a local label
   with each prefix such as L3VPN [9], 6PE [10], and Softwire [8].
   Suppose that a given edge router is chosen as the best next-hop for
   a prefix P/p. An ingress router that receives a packet from an
   external router and destined for the prefix P/p pushes the label
   advertised by the egress edge router and then "tunnels" the packet
   across the core to that egress router. Upon receiving the labeled
   packet from the core, the egress router uses the label on the
   packet to take the appropriate forwarding decision.

   In modern networks, it is not uncommon to have a prefix reachable
   via multiple edge routers. One example is the best external path
   [7]. Another more common and widely deployed scenario is L3VPN [9]
   with multi-homed VPN sites. As an example, consider the L3VPN
   topology depicted in Figure 1.

         +--------------------------+
         |                          |
         |      BGP free Core       |
         |                          |
         |      +------------------PE1----+
         |     /                    |      \
         |    /                     |       \
         |   /                      |        \
         |  /                       |         \
         | /                        |          *
        PE3                         |          CE....... VPN prefix
         | \                        |          *          (P/p)
         |  \                       |         /
         |   \                      |        /
         |    \                     |       /
         |     \                    |      /
         |      +------------------PE2----+
         |                          |
         |                          |
         +--------------------------+

             Figure 1 VPN prefix reachable via multiple PEs



Bashandy              Expires September 24, 2011               [Page 3]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   PE3 is the ingress PE. PE1 and PE2 are both egress PEs connected to
   CE. CE advertises one or more VPN prefixes, denoted by P/p. PE1 and
   PE2 advertise P/p as VPNv4 or VPNv6 routes to all ingress PEs,
   including PE3, and associates a label with each route.

   Suppose that the ingress PE, PE3, chooses PE1 as the next-hop for
   the prefix P/p. In order to minimize traffic loss, it is highly
   desirable for PE1 to reroute all traffic destined to P/p to PE2 as
   soon as the connectivity to CE is lost and without waiting for the
   control plane (whether it is IGP or BGP) to re-converge and
   computes new the best path. In doing so, PE1 pushes the label
   advertised by PE2 for the prefix P/p, and then "tunnels" the packet
   to PE2. However if the loss of PE1-CE connectivity was due to CE
   crash, then PE2 will also reroute the traffic back to PE1,
   resulting in loop. Due to ultra scalability requirements, where
   there is a need to support thousands of peers and hundreds of
   thousands of prefixes, there is a need to support quick traffic
   restoration without waiting for the control plane to converge and
   without risking loops.

   1.1. Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
   this document are to be interpreted as described in RFC-2119 [1].

   In this document, these words will appear with that interpretation
   only when in ALL CAPS. Lower case uses of these words are not to be
   interpreted as carrying RFC-2119 significance.

   1.2. Terminology

   This section outlines the terms used in this document. For ease of
   use, we will use terms similar to those used by L3VPN [9]

   o  Protected prefix: It is a prefix P/p (of any AFI) that a BGP
      speaker has an external path to. The BGP speaker may learn about
      the prefix from an external peer through BGP, some other
      protocol, or manual configuration. The protected prefix is
      advertised to some or all the internal peers.

   o  Primary egress PE: It is an IBGP peer that can reach the
      protected prefix P/p through an external path and advertised the
      prefix to the other IBGP peers. The primary egress PE was chosen
      as the best path by one or more internal peers. In other words,
      the primary egress PE is an egress PE that will normally be used
      when there is no failure. Referring to Figure 1, PE1 is a
      primary egress PE.


Bashandy              Expires September 24, 2011               [Page 4]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   o  CE: It is an external router through which an egress PE can
      reach a prefix P/p. The router "CE" in Figure 1 is an example of
      such CE

   o  Ingress PE: It is a BGP speaker that learns about a prefix
      through another IBGP peer and chooses that IBGP peer as the
      next-hop for the prefix. PE3 in Figure 1 is an example of an
      ingress PE

   o  Repairing PE: It is the PE that attempts to restore traffic when
      the primary path is no longer reachable "without" waiting for
      BGP to re-converge. The repairing PE restores the traffic by
      rerouting the traffic (through a tunnel) towards the pre-
      calculated repair PE when it detects that the primary path
      longer reachable. The primary path may be a CE or another egress
      PE. Referring to Figure 1, if PE3 chooses PE1 as the primary
      egress PE and PE1 decides to reroute traffic to PE2 on losing
      reachability with CE, then PE1 is a repairing PE. If PE3 chooses
      PE1 as a primary path and PE3 decides to use PE2 as a repair
      path when it loses reachability to PE2, then PE3 is a repairing
      PE.

   o  Primary label: It is the label advertised by the primary egress
      PE to be used for normal traffic forwarding.

   o  Repair egress PE: It is an egress PE other than the primary
      egress PE that can reach the protected prefix P/p through an
      external neighbor. The repair PE is pre-calculated via other PEs
      prior to any failure

   o  Repair label: It is the label that will be pushed on the packet
      when the repairing PE reroutes the traffic (through a tunnel)
      towards the repair egress PE. Section 2. discusses how the
      repair label is used. Section 3. discusses semantics of and the
      method for disseminating repair label information.

   o  Repair path: It is the repair egress PE and the repair label.

2. Protocol Operation

   This section explains the operation of the control and forwarding
   planes of routers participating BGP-free core traffic restoration.

   2.1. Control plane Operation

   1. As usual, each PE allocates a local label for each prefix it can
      reach through an external neighbor CE. This is the primary label
      used for normal traffic forwarding.


Bashandy              Expires September 24, 2011               [Page 5]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   2. To provide repair path information to all PEs, the PE also
      allocates a repair label to the prefix if it can reach that
      prefix via an external neighbor. Different repair label
      allocation schemes are proposed in Section 3.

   3. The PE advertises both the primary and repair labels to all IBGP
      peers.

   4. When a PE receives the label advertisement from egress PEs, it
      calculates a primary egress PE and a repair egress PE based on
      its internal path selection criteria. Note that the method of
      choosing the repair path is beyond the scope of this document.

   5. In the end, for some of the prefix advertised by more than one
      PE, a PE will have

       o a primary path

       o a repair path consisting of a repair PE and a repair label
          advertised by the chosen repair PE.

   6. A PE "never" protects a repair label. Hence on any PE, a repair
      label only has paths towards the CE. However a primary label may
      have a repair path towards a chosen repair PE

2.1.1. Additional Rules for allocating and advertising a Repair label

   o  A repairing PE MUST NOT advertise a repair for a prefix if it does
      NOT have an external path to the prefix

   o  A repairing PE MUST NOT associate an internal path with a repair
      label

   o  Repair labels SHOULD be advertised with labeled address families
      only. That is AFI/SAFI 1/4, 2/4, 1/128, and 2/128.



   2.2. Forwarding Plane Operation on Losing Primary path
      Reachability

   As soon as a PE loses reachability to the primary path of the
   protected prefix P/p, the forwarding plane processes arriving
   traffic as follows:






Bashandy              Expires September 24, 2011               [Page 6]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   1. If the repairing PE is an egress PE, the packet arrives at the
      repairing PE with the primary label at the top because the packet
      is "tunneled" from the ingress PE(s). In that case, the repairing
      PE swaps the incoming label stack with the "repair label stack"
      advertised by the repair egress PE. Section 3.1.2. specifies all
      the details

   2. If the repairing PE is an ingress PE, it pushes the "repair label
      stack" advertised by the repair egress PE. Section 3.1.2.
      specifies all the details

   3. The repairing PE tunnels the packet to the repair PE

   4. At the repair PE, the packet arrives with the repair label at
      the top. The repair PE uses the incoming label stack to take
      forwarding decisions

   5. If the repair egress PE can reach the CE, the repair PE forwards
      the packet towards the CE.

   6. If the repair PE cannot reach the CE, the traffic will be
      dropped because a PE never protects a repair label

   2.3. Example

   Consider the L3VPN [9] topology depicted in Figure 2 where two PEs
   are connected to the same PE. Assume that the core is LDP. We will
   be using an advertised repair label.

                                  PE1
                                     \
                                      \
                                       \
                                        \
               LDP core                 CE....... VPN prefix
                                        /        (10.0.0.0/8)
                                       /
                                      /
                                     /
                                   PE2

                        Figure 2 : L3VPN Example



   PE1: Repairing egress PE
   PE2: repair PE
   Primary VPN label advertised by PE1 to all PEs 4000
   Repair VPN label advertised by PE1 to all PEs 5000

Bashandy              Expires September 24, 2011               [Page 7]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   Primary VPN label advertised by PE2 to all PEs: 2000
   Repair VPN label advertised by PE2 all PEs: 3000

   LDP label for PE2 on PE1 is 1234
   LDP label for PE1 on PE2 is 4567

   Before failure
   '''''''''''''''
   PE1 has the following FIB entries

   4000 -----> CE (unlabeled)
        -----> PE2, swap 4000 with 3000 and then push 1234
   5000 -----> CE (unlabeled)

   PE2 has the following
   2000 -----> CE (unlabeled)
        -----> PE1, swap 2000 with 5000 and then push 4567
   3000 ------> CE (unlabeled)

   After the CE crashes
   ''''''''''''''''''''
   PE1 has the following entry:
   4000 -----> PE2, swap 4000 with 3000 and then push 1234
   5000 -----> Drop


   PE2 has the following
   2000 -----> PE1, swap 2000 with 5000 and then push 4567
   3000 ------> Drop


   Because of the above routing entries, any traffic arriving from the
   core at PE1 and destined for 10.0.0/8,  is rerouted towards PE2
   using the repair VPN label 3000. PE2 will just drop it instead of
   looping it back towards PE1.

   After the link between PE and CE fails (CE did not crash)
   '''''''''''''''''''''''''''''''''''''''''''''''''''''''''
   PE1 has the following entry:
   4000 -----> PE2, swap 4000 with 3000 and then push 1234
   5000 -----> Drop

   PE2 has the following
   2000 -----> CE (unlabeled)
        -----> PE1, swap 2000 with 5000 and then push 4567
   3000 ------> CE


   Because of the above routing entries, any traffic arriving from the

Bashandy              Expires September 24, 2011               [Page 8]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   core at PE1 and destined for 10.0.0/8 is rerouted towards PE2 using
   the repair VPN label 3000. PE2 will forward the traffic towards CE.

3. How to Disseminate Repair Label Information

   We propose advertise the repair label as an optional path
   attribute. Advertising the repair label as an optional path
   attributes has some advantages:

   o  An egress PE can benefits from a scalable repair label
      allocation schemes such as per-CE repair label allocation

   o  Allows the repairing PE to share the same repair path among
      multiple protected prefixes. Since the repair path is shared by
      all labels sharing the path attribute, the repairing PE can
      optimize its RIB and FIB by sharing the same repair path data
      structure among a large number of protected prefixes.

   o  Reduces the BGP update message size. Instead of having to send
      additional labels per prefix, multiple prefixes can share the
      same repair label

   o  The number of labels used for traffic restoration does not
      depend on the number of protected prefixes

   o  Allows for incremental deployment because the attribute is
      optional

   The main disadvantage of sharing the same repair path among
   multiple primary paths is loss of fine grain control. It is not
   possible to manage, control, or provide differentiated handling to
   traffic on per prefix basis until the network re-converges. The
   loss of fine grain control is limited to the BGP re-convergence
   period.

   It is noteworthy to mention that per-CE repair label allocation has
   some advantages over per-prefix repair label allocation. First it
   results in using fewer labels. Second it allows for better packing
   in BGP messages. Third it does not require special handling in the
   forwarding plane at the repair PE. Fourth it simplifies the
   forwarding plane while maximizing the packet switching performance
   because the egress PE can take a forwarding decision with a single
   FIB lookup.

3.1.1. Structure of the Repair Label Path Attribute

   This document defines the repair label attribute as an optional
   non-transitive path attribute [2] as follows:


Bashandy              Expires September 24, 2011               [Page 9]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

      Attribute name: REPAIR_LABEL

      Type code: TBD

      Attribute Flags:

         Optional bit: 1

         Transitive bit: 0

         Partial bit: 0

         Extended Length bit: 0

      Length of the attribute: It indicates the length in octets of
      the attribute

      Attribute Value: The attribute value contains a stack of one or
      more labels. The encoding of the labels is identical to encoding
      of the "label" field in [4]. The value of the bottom of stack
      (BOS) bit is determined at traffic restoration time as specified
      in Section 3.1.2.

3.1.2. Semantics of the Repair Label Attribute

   This document specifies the semantics of the repair label attribute
   when the attribute carries one repair label only. The semantics of
   more than one repair label is beyond the scope of this document.

   Suppose a BGP speaker PE1 receives an update message with a repair
   label attribute containing the label "Lr2" from the IBGP peer PE2.
   Suppose the NLRI in the MP_REACH_NLRI attribute [3] contains the
   prefixes R1, R2,. . . , Rn each bound to a label L21, L22,. . . ,
   L2n, respectively. This means the following:

   1. PE2 will never attempt to repair a packet arriving with the
      label "Lr". Hence PE2 will either forward the packet to an
      external CE or drop the packet

   2. PE2 expects the following from PE1:

       a. Case a: The route Ri on PE1 is bound to a local label "L1i".
          Suppose PE1 receives a packet with the label "L1i" at the
          top of the stack. If the PE1 loses the primary path for a
          prefix Ri and PE1 decides that PE2 is the repair PE for the
          prefix Ri, then PE1 has to swap the label "L1i" on the
          packet with the repair label "Lr2" and then tunnel the
          packet to PE2. The bottom of stack (BOS) bit MUST be copied
          from the label arriving on the packet to the label "Lr2"

Bashandy              Expires September 24, 2011              [Page 10]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

       b. Case b: The route Ri on PE1 is not bound to any local label.
          If the PE1 loses the primary path for a prefix Ri and PE1
          decides that PE2 is the repair PE for the prefix Ri, then
          PE1 MUST push the label "Lr2" and then tunnel the packet to
          PE2. The bottom of stack (BOS) bit in "Lr2" MUST be set as
          specified in [5].

       c. Case c: The route Ri on PE1 is bound to an aggregate label
          (e.g. per-vrf label). In that case, PE1 has to perform more
          than one route lookup to determine the primary path.
          Eventually, there will either be an IP lookup or a label
          lookup that points to the primary path:

           i. A label lookup points to the primary path: In that
               case, PE1 handles the packet as described in item 2.a
               above.

          ii. An IP lookup points to the primary path: In that case,
               PE1 handles the packet similar described in item 2.b
               above.

3.1.3. Additional Rule when Forwarding Advertisements Containing the
   Repair Path Attribute

   As specified in Section 3.1.1. the repair label attribute is a non-
   transitive attribute. However there may be cases, such as inter-AS
   option (b)[9], route reflectors [11], or confederation [12], where
   a router may replace the advertised next-hop with its own before
   forwarding an advertisement. If a BGP speaker replaces the next-hop
   attribute with its own and the advertisement contains a repair
   label attribute with label stack "Sr", there are two options

   o  Option 1: The BGP speaker MUST NOT advertise the repair label
      attribute

   o  Option 2: The BGP speaker MUST replace the repair label stack
      "Sr" with a locally allocated label stack "Sr1" before
      advertising the route and then advertise the stack "Sr1" in the
      repair label attribute. For the forwarding plane, the BGP
      speaker MUST install a swap forwarding entry such that if the
      BGP speaker receives a packet with the label stack "Sr1", it
      swaps "Sr1" with the stack "Sr".

   Note that advertising the repair label attribute by the router
   depends on whether the router understands the semantics of and
   supports the repair label attribute at the time of receiving an
   advertisement containing the repair label attribute.



Bashandy              Expires September 24, 2011              [Page 11]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

4. Security Considerations

   No additional security risk is introduced by using the mechanisms
   proposed in this document

5. IANA Considerations

   This document defines a new BGP path attribute. IANA maintains a
   list of the current BGP attribute typecodes in [6]. This document
   proposes defining a new typecode value of "TBD" for the
   REPAIR_LABEL path attribute

6. Conclusions

   This document proposes using a repair label to allow restoring
   traffic prior to BGP convergence while avoiding loops

7. References

   7.1. Normative References

   [1]   Bradner, S., "Key words for use in RFCs to Indicate
         Requirement Levels", BCP 14, RFC 2119, March 1997.

   [2]   Rekhter, Y., Li, T., and S. Hares, "A Border Gateway Protocol
         4 (BGP-4), RFC 4271, January 2006

   [3]   Bates, T., Chandra, R., Katz, D., and Rekhter Y.,
         "Multiprotocol Extensions for BGP", RFC 4760, January 2007

   [4]   Rosen, E., Rekhter, Y., "Carrying Label Information in BGP-
         4", RFC 3107, May 2001

   [5]   Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci,
         D., Li, T. and A. Conta, "MPLS Label Stack Encoding", RFC
         3032, January 2001.

   7.2. Informative References

   [6]   BGP Parameters, http://www.iana.org/assignments/bgp-
         parameters/bgp-parameters.xhtml

   [7]   Marques,P., Fernando, R., Chen, E, Mohapatra, P.,
         "Advertisement of the best external route in BGP", draft-
         ietf-idr-best-external-02.txt, April 2004.

   [8]   Wu, J., Cui, Y., Metz, C., and E. Rosen, "Softwire Mesh
         Framework", RFC 5565, June 2009.


Bashandy              Expires September 24, 2011              [Page 12]
=0C
Internet-Draft        BGP FRR using Repair Label             March 2011

   [9]   Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
         Networks (VPNs)", RFC 4364, February 2006.

   [10]  De Clercq, J. , Ooms, D., Prevost, S., Le Faucheur, F.,
         Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider
         Edge Routers (6PE)", RFC 4798, February 2007

   [11]  Bates, T., Chen, E., and Chandra, R., "BGP Route Reflection:
         An Alternative to Full Mesh Internal BGP (IBGP)", RFC 4456,
         April 2006

   [12]  Traina, P., McPherson, P., and Scudder, J., "Autonomous
         System Confederations for BGP", RFC 5065, August 2007

8. Acknowledgments

   Special thanks to Keyur Patel, Robert Raszuk, and Eric Rosen for
   the valuable comments

   This document was prepared using 2-Word-v2.0.template.dot.

Authors' Addresses

   Ahmed Bashandy
   Cisco Systems
   170 West Tasman Dr, San Jose, CA 95134
   Email: bashandy@cisco.com

   Burjiz Pithawala
   Cisco Systems
   170 West Tasman Dr, San Jose, CA 95134
   Email: bpithaw@cisco.com


















Bashandy              Expires September 24, 2011              [Page 13]
=0C

--------------080008060403030804010107--

--------------enig0C8BA67CB742A078473FDB71
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFNi1Ny+G19kFA5zIYRAl6jAJ0ZsaasXM/NdNDbQvZbttJJ8MrrCwCfZ8C/
OqpVUkorFRqGYJC+6Gtix+E=
=eidk
-----END PGP SIGNATURE-----

--------------enig0C8BA67CB742A078473FDB71--

From bashandy@cisco.com  Mon Mar 28 21:16:12 2011
Return-Path: <bashandy@cisco.com>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A968F3A67E1; Mon, 28 Mar 2011 21:16:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.448
X-Spam-Level: 
X-Spam-Status: No, score=-10.448 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ABTb+gYHhEPF; Mon, 28 Mar 2011 21:16:11 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 9B7243A67AF; Mon, 28 Mar 2011 21:16:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=bashandy@cisco.com; l=8719; q=dns/txt; s=iport; t=1301372269; x=1302581869; h=message-id:date:from:reply-to:mime-version:to:cc:subject; bh=vH4BZliYI67x9K2yB1v6hjILLewaJkVYaSWpKegxTtw=; b=TC/l65pQ0gTwGRSnss1JLKG+r6JRPY+VurpsVhDkwxDDqT+eTXsNDgvD IVNZ0t90/tMRq6MrpRQkBV0+jfrwaEBh+mWdUDYnZbxb3brrYX5L5LE3M 2ORKiQ76I9zgyiHPkL3nf9Cgiw5BUn+i4MAbtcv1YSVPNcfIRP8HiMHQc Y=;
X-Files: signature.asc : 251
X-IronPort-AV: E=Sophos;i="4.63,259,1299456000";  d="asc'?scan'208,217";a="419931510"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-1.cisco.com with ESMTP; 29 Mar 2011 04:17:49 +0000
Received: from [10.21.77.47] ([10.21.77.47]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2T4Hi4C008960; Tue, 29 Mar 2011 04:17:45 GMT
Message-ID: <4D915D5D.8030706@cisco.com>
Date: Tue, 29 Mar 2011 06:17:33 +0200
From: Ahmed Bashandy <bashandy@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: idr@ietf.org, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Fwd: New Version Notification for draft-bashandy-idr-bgp-repair-label-01
X-Enigmail-Version: 1.1.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig296740EB73B0282820BB0F98"
Cc: "Burjiz Pithawala \(bpithaw\)" <bpithaw@cisco.com>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bashandy@cisco.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2011 04:16:12 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig296740EB73B0282820BB0F98
Content-Type: multipart/alternative;
 boundary="------------000801050304090007040807"

This is a multi-part message in MIME format.
--------------000801050304090007040807
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

This is a new version of the draft with some corrections based on the fee=
dback given so far

This is a draft that proposes rerouting traffic, without waiting for BGP =
to re-converge, to another PE in a BGP-free core when a PE detects that t=
he NH is no longer reachable. Because traffic coming from the core is red=
irected back to the core, we propose using a specially advertised label t=
o make sure that the traffic does not get re-routed multiple times into t=
he core, thus avoiding loops.

The draft will be presented during the IDR meeting on Thursday Mar/31/11

All comments now or during the meeting are most welcomed

Thanks

Ahmed




-------- Original Message --------
Subject: 	New Version Notification for draft-bashandy-idr-bgp-repair-labe=
l-01
Date: 	Mon, 28 Mar 2011 21:11:45 -0700
From: 	IETF I-D Submission Tool <idsubmission@ietf.org>
To: 	Ahmed Bashandy (bashandy) <bashandy@cisco.com>
CC: 	Burjiz Pithawala (bpithaw) <bpithaw@cisco.com>




A new version of I-D, draft-bashandy-idr-bgp-repair-label-01.txt has been=
 successfully submitted by Ahmed Bashandy and posted to the IETF reposito=
ry.

Filename:        draft-bashandy-idr-bgp-repair-label
Revision:        01
Title:           Scalable, Loop-Free BGP FRR using Repair Label
Creation_date:   2011-03-29
WG ID:           Independent Submission
Number_of_pages: 13

Abstract:
Consider a BGP free core scenario. Suppose the provider edge BGP
speaker PE1, PE2,..., PEn know about a prefix P/p via the external
routers CE1, CE2,..., CEm.  If the PE router PEi loses connectivity to
the primary path, whether it is another PE router or a CE router, it
desirable to immediately restore traffic by rerouting packets arriving
to PEi and destined to the prefix P/p to one of the other PE routers
that advertised P/p, say PEj, until BGP re-converges. However if the
loss of connectivity of PEi to the primary path also resulted in the
loss of connectivity between PEj and CEj, rerouting a packet before
the control plane converges may result in a loop. In this document, we
propose using a repair label for traffic restoration while avoiding
loops. We propose advertising the "repair" label through BGP.
                                                                         =
       =20


The IETF Secretariat.



--------------000801050304090007040807
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF=
-8">
    <meta name=3D"Generator" content=3D"MS Exchange Server version
      6.5.7655.10">
    <title>New Version Notification for
      draft-bashandy-idr-bgp-repair-label-01 </title>
  </head>
  <body text=3D"#000000" bgcolor=3D"#ffffff">
    <pre wrap=3D"">Hi,

This is a new version of the draft with some corrections based on the fee=
dback given so far

This is a draft that proposes rerouting traffic, without waiting for BGP =
to re-converge, to another PE in a BGP-free core when a PE detects that t=
he NH is no longer reachable. Because traffic coming from the core is red=
irected back to the core, we propose using a specially advertised label t=
o make sure that the traffic does not get re-routed multiple times into t=
he core, thus avoiding loops.

The draft will be presented during the IDR meeting on Thursday Mar/31/11

All comments now or during the meeting are most welcomed

Thanks

Ahmed

</pre>
    <br>
    <br>
    -------- Original Message --------
    <table class=3D"moz-email-headers-table" border=3D"0" cellpadding=3D"=
0"
      cellspacing=3D"0">
      <tbody>
        <tr>
          <th valign=3D"BASELINE" align=3D"RIGHT" nowrap=3D"nowrap">Subje=
ct: </th>
          <td>New Version Notification for
            draft-bashandy-idr-bgp-repair-label-01</td>
        </tr>
        <tr>
          <th valign=3D"BASELINE" align=3D"RIGHT" nowrap=3D"nowrap">Date:=
 </th>
          <td>Mon, 28 Mar 2011 21:11:45 -0700</td>
        </tr>
        <tr>
          <th valign=3D"BASELINE" align=3D"RIGHT" nowrap=3D"nowrap">From:=
 </th>
          <td>IETF I-D Submission Tool <a class=3D"moz-txt-link-rfc2396E"=
 href=3D"mailto:idsubmission@ietf.org">&lt;idsubmission@ietf.org&gt;</a><=
/td>
        </tr>
        <tr>
          <th valign=3D"BASELINE" align=3D"RIGHT" nowrap=3D"nowrap">To: <=
/th>
          <td>Ahmed Bashandy (bashandy) <a class=3D"moz-txt-link-rfc2396E=
" href=3D"mailto:bashandy@cisco.com">&lt;bashandy@cisco.com&gt;</a></td>
        </tr>
        <tr>
          <th valign=3D"BASELINE" align=3D"RIGHT" nowrap=3D"nowrap">CC: <=
/th>
          <td>Burjiz Pithawala (bpithaw) <a class=3D"moz-txt-link-rfc2396=
E" href=3D"mailto:bpithaw@cisco.com">&lt;bpithaw@cisco.com&gt;</a></td>
        </tr>
      </tbody>
    </table>
    <br>
    <br>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF=
-8">
    <meta name=3D"Generator" content=3D"MS Exchange Server version
      6.5.7655.10">
    <title>New Version Notification for
      draft-bashandy-idr-bgp-repair-label-01 </title>
    <!-- Converted from text/plain format -->
    <br>
    <p><font size=3D"2">A new version of I-D,
        draft-bashandy-idr-bgp-repair-label-01.txt has been successfully
        submitted by Ahmed Bashandy and posted to the IETF repository.<br=
>
        <br>
        Filename:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 draft-bashand=
y-idr-bgp-repair-label<br>
        Revision:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 01<br>
        Title:=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Sca=
lable, Loop-Free BGP FRR using Repair Label<br>
        Creation_date:=C2=A0=C2=A0 2011-03-29<br>
        WG ID:=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Ind=
ependent Submission<br>
        Number_of_pages: 13<br>
        <br>
        Abstract:<br>
        Consider a BGP free core scenario. Suppose the provider edge BGP<=
br>
        speaker PE1, PE2,..., PEn know about a prefix P/p via the
        external<br>
        routers CE1, CE2,..., CEm.=C2=A0 If the PE router PEi loses
        connectivity to<br>
        the primary path, whether it is another PE router or a CE
        router, it<br>
        desirable to immediately restore traffic by rerouting packets
        arriving<br>
        to PEi and destined to the prefix P/p to one of the other PE
        routers<br>
        that advertised P/p, say PEj, until BGP re-converges. However if
        the<br>
        loss of connectivity of PEi to the primary path also resulted in
        the<br>
        loss of connectivity between PEj and CEj, rerouting a packet
        before<br>
        the control plane converges may result in a loop. In this
        document, we<br>
        propose using a repair label for traffic restoration while
        avoiding<br>
        loops. We propose advertising the "repair" label through BGP.<br>=

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<br>
        <br>
        <br>
        The IETF Secretariat.<br>
        <br>
        <br>
      </font>
    </p>
  </body>
</html>

--------------000801050304090007040807--

--------------enig296740EB73B0282820BB0F98
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFNkV1o+G19kFA5zIYRAlOfAJ0RA7ktxlLmJ284e2nrUMhQkZTaEACdE4gB
bSnxJBHZ44uheEoEFm0Sq3k=
=t3Mh
-----END PGP SIGNATURE-----

--------------enig296740EB73B0282820BB0F98--

From jeff.tantsura@ericsson.com  Tue Mar 29 05:56:47 2011
Return-Path: <jeff.tantsura@ericsson.com>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C09FB3A683A for <rtgwg@core3.amsl.com>; Tue, 29 Mar 2011 05:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.37
X-Spam-Level: 
X-Spam-Status: No, score=-5.37 tagged_above=-999 required=5 tests=[AWL=1.229,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nDDwG7smtn9M for <rtgwg@core3.amsl.com>; Tue, 29 Mar 2011 05:56:47 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id 017AE3A6801 for <rtgwg@ietf.org>; Tue, 29 Mar 2011 05:56:46 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p2TCwOG7028102 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtgwg@ietf.org>; Tue, 29 Mar 2011 07:58:24 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.2.141]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Tue, 29 Mar 2011 08:58:24 -0400
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Tue, 29 Mar 2011 08:58:20 -0400
Subject: fn-transport/ipfrr drafts
Thread-Topic: fn-transport/ipfrr drafts
Thread-Index: AcvuEPsMZcHWm7VeSfqbDajC5qgxFg==
Message-ID: <0ED867EB33AB2B45AAB470D5A64CDBF60CAB204D66@EUSAACMS0701.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2011 12:56:47 -0000

Hi rtgwg,

The authors would like to solicit comments from the workgroup.

draft-lu-fn-transport-00
draft-csaszar-ipfrr-fn-00

Thank you in advance!

Regards,
Jeff =20


From Fred.L.Templin@boeing.com  Tue Mar 29 15:43:03 2011
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 064553A6ACC for <rtgwg@core3.amsl.com>; Tue, 29 Mar 2011 15:43:03 -0700 (PDT)
X-Quarantine-ID: <SKSJe0uMIBv4>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, MIME error: error: illegal encoding [base64] for MIME type message/external-body
X-Spam-Flag: NO
X-Spam-Score: -6.312
X-Spam-Level: 
X-Spam-Status: No, score=-6.312 tagged_above=-999 required=5 tests=[AWL=0.287,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SKSJe0uMIBv4 for <rtgwg@core3.amsl.com>; Tue, 29 Mar 2011 15:43:01 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 9BD433A6AC5 for <rtgwg@ietf.org>; Tue, 29 Mar 2011 15:43:01 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by slb-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p2TMidI3020135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <rtgwg@ietf.org>; Tue, 29 Mar 2011 15:44:40 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p2TMidEB024308 for <rtgwg@ietf.org>; Tue, 29 Mar 2011 15:44:39 -0700 (PDT)
Received: from XCH-NWHT-01.nw.nos.boeing.com (xch-nwht-01.nw.nos.boeing.com [130.247.70.222]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p2TMidFT024298 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for <rtgwg@ietf.org>; Tue, 29 Mar 2011 15:44:39 -0700 (PDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.97]) by XCH-NWHT-01.nw.nos.boeing.com ([130.247.70.222]) with mapi; Tue, 29 Mar 2011 15:44:38 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Tue, 29 Mar 2011 15:44:35 -0700
Subject: Asymmetric Extended Route Optimization (AERO)
Thread-Topic: Asymmetric Extended Route Optimization (AERO)
Thread-Index: AcvuXwwoAJpjxGYnQTSBsmybyrT48wAABGUwAACmb7A=
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C691813C0@XCH-NW-01V.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/mixed; boundary="_004_E1829B60731D1740BB7A0626B4FAF0A65C691813C0XCHNW01Vnwnos_"
MIME-Version: 1.0
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2011 22:43:03 -0000

--_004_E1829B60731D1740BB7A0626B4FAF0A65C691813C0XCHNW01Vnwnos_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Please see below for a new draft entitled: "Asymmetric Extended
Route Optimization (AERO). This document was derived from the
Section 5.14 text of 'draft-templin-intarea-vet-24', which I
briefed during the Monday rtgwg session under the (cryptic)
title of: "On-demand dynamic route optimizations between tunnel
endpoints".

AERO is based on ordinary ICMP Redirect messages, but it is
different from classical redirection in that the gateway first
sends a "Predirect" forward to the egress link node. The egress
establishes RPF filtering entries, then sends a "Redirect"
messsage back to the ingress link node via the gateway. The
ingress then can know that the egress is ready to accept its
tunneled packets directly without involving the gateway.

This work is a bit of a "crossover" technology, in that
it is using intarea constructs (i.e., ICMP redirects) to
produce rtgarea results. However, I would like to get
discussion on the document on this list to determine if
it can be considered as a rtgwg working item.

Thanks - Fred
fred.l.templin@boeing.com

-----Original Message-----
From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] =
On Behalf Of Internet-Drafts@ietf.org
Sent: Tuesday, March 29, 2011 3:15 PM
To: i-d-announce@ietf.org
Subject: I-D Action:draft-templin-aero-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.

	Title           : Asymmetric Extended Route Optimization (AERO)
	Author(s)       : F. Templin
	Filename        : draft-templin-aero-00.txt
	Pages           : 20
	Date            : 2011-03-29

Nodes (i.e., gateways, routers and hosts) attached to link types such
as multicast-capable, shared media and non-broadcast multiple access
(NBMA), etc. can exchange packets as neighbors on the link.  Each
node should therefore be able to discover a neighboring gateway that
can provide default routing services to reach off-link destinations,
and should also accept redirection messages from the gateway
informing it of a neighbor that is closer to the final destination.
This redirect function can provide a useful route optimization, since
the triangular path from the ingress link neighbor, to the gateway,
and finally to the egress link neighbor may be considerably longer
than the direct path between the neighbors.  However, ordinary
redirection may lead to operational issues on certain link types
and/or in certain deployment scenarios.  This document therefore
introduces an Asymmetric Extended Route Optimization (AERO)
capability that addresses the issues.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-templin-aero-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--_004_E1829B60731D1740BB7A0626B4FAF0A65C691813C0XCHNW01Vnwnos_
Content-Type: message/external-body; name="draft-templin-aero-00.url"
Content-Description: draft-templin-aero-00.url
Content-Disposition: attachment; filename="draft-templin-aero-00.url";
	size=460; creation-date="Tue, 29 Mar 2011 08:17:10 GMT";
	modification-date="Tue, 29 Mar 2011 08:17:10 GMT"
Content-Transfer-Encoding: base64


Q29udGVudC1UeXBlOiBtZXNzYWdlL2V4dGVybmFsLWJvZHk7IG5hbWU9ImRyYWZ0LXRlbXBsaW4t
YWVyby0wMC51cmwiDQpDb250ZW50LURlc2NyaXB0aW9uOiBkcmFmdC10ZW1wbGluLWFlcm8tMDAu
dXJsDQpDb250ZW50LURpc3Bvc2l0aW9uOiBhdHRhY2htZW50OyBmaWxlbmFtZT0iZHJhZnQtdGVt
cGxpbi1hZXJvLTAwLnVybCI7DQoJc2l6ZT04NjsgY3JlYXRpb24tZGF0ZT0iVHVlLCAyOSBNYXIg
MjAxMSAxNToxNzoxMCBHTVQiOw0KCW1vZGlmaWNhdGlvbi1kYXRlPSJUdWUsIDI5IE1hciAyMDEx
IDE1OjE3OjEwIEdNVCINCkNvbnRlbnQtVHJhbnNmZXItRW5jb2Rpbmc6IGJhc2U2NA0KDQoNClcw
bHVkR1Z5Ym1WMFUyaHZjblJqZFhSZERRcFZVa3c5Wm5Sd09pOHZablJ3TG1sbGRHWXViM0puTDJs
dWRHVnlibVYwTFdSeVlXWjANCmN5OWtjbUZtZEMxMFpXMXdiR2x1TFdGbGNtOHRNREF1ZEhoMERR
bz0NCg==

--_004_E1829B60731D1740BB7A0626B4FAF0A65C691813C0XCHNW01Vnwnos_
Content-Type: text/plain; name="ATT00001..txt"
Content-Description: ATT00001..txt
Content-Disposition: attachment; filename="ATT00001..txt"; size=258;
	creation-date="Tue, 29 Mar 2011 08:17:10 GMT";
	modification-date="Tue, 29 Mar 2011 08:17:10 GMT"
Content-Transfer-Encoding: base64

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5v
dW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pLWQtYW5ub3VuY2UNCkludGVybmV0LURyYWZ0IGRpcmVj
dG9yaWVzOiBodHRwOi8vd3d3LmlldGYub3JnL3NoYWRvdy5odG1sDQpvciBmdHA6Ly9mdHAuaWV0
Zi5vcmcvaWV0Zi8xc2hhZG93LXNpdGVzLnR4dA0K

--_004_E1829B60731D1740BB7A0626B4FAF0A65C691813C0XCHNW01Vnwnos_
Content-Type: text/plain; name="ATT00001..txt"
Content-Description: ATT00001..txt
Content-Disposition: attachment; filename="ATT00001..txt"; size=139;
	creation-date="Tue, 29 Mar 2011 15:31:47 GMT";
	modification-date="Tue, 29 Mar 2011 15:31:47 GMT"
Content-Transfer-Encoding: base64

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkludC1hcmVh
IG1haWxpbmcgbGlzdA0KSW50LWFyZWFAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vaW50LWFyZWENCg==

--_004_E1829B60731D1740BB7A0626B4FAF0A65C691813C0XCHNW01Vnwnos_--

From jgs@juniper.net  Wed Mar 30 02:12:18 2011
Return-Path: <jgs@juniper.net>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0532028C117 for <rtgwg@core3.amsl.com>; Wed, 30 Mar 2011 02:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.582
X-Spam-Level: 
X-Spam-Status: No, score=-6.582 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y0-wwSU4BO8J for <rtgwg@core3.amsl.com>; Wed, 30 Mar 2011 02:12:17 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by core3.amsl.com (Postfix) with ESMTP id AE85928C116 for <rtgwg@ietf.org>; Wed, 30 Mar 2011 02:12:17 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKTZL0VJAm+OGSlIvapPrh9ccyFG4fQ4JJ@postini.com; Wed, 30 Mar 2011 02:13:56 PDT
Received: from EMBX02-HQ.jnpr.net ([fe80::18fe:d666:b43e:f97e]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Wed, 30 Mar 2011 02:11:35 -0700
From: John Scudder <jgs@juniper.net>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Wed, 30 Mar 2011 02:13:03 -0700
Subject: Fwd: Routing Area Open Meeting room change
Thread-Topic: Routing Area Open Meeting room change
Thread-Index: AcvuunfeDx8MV6K/Rja933ulGMU5YQ==
Message-ID: <46E6EA63-D065-4E6F-99AC-206376D882C6@juniper.net>
References: <0bb501cbeeac$e6a72390$b3f56ab0$@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 09:12:18 -0000

FYI.

--John

Begin forwarded message:

From: Adrian Farrel <Adrian.Farrel@huawei.com<mailto:Adrian.Farrel@huawei.c=
om>>
Date: March 30, 2011 9:34:25 AM GMT+02:00
To: "routing-discussion@ietf.org<mailto:routing-discussion@ietf.org>" <rout=
ing-discussion@ietf.org<mailto:routing-discussion@ietf.org>>
Cc: "rtg-chairs@ietf.org<mailto:rtg-chairs@ietf.org>" <rtg-chairs@ietf.org<=
mailto:rtg-chairs@ietf.org>>
Subject: Routing Area Open Meeting room change
Reply-To: "Adrian.Farrel@huawei.com<mailto:Adrian.Farrel@huawei.com>" <Adri=
an.Farrel@huawei.com<mailto:Adrian.Farrel@huawei.com>>

Fortunately, this is only a change to the next-door room.

Chairs: Notifying your WGs might be good.


From: 80all-bounces@ietf.org<mailto:80all-bounces@ietf.org> [mailto:80all-b=
ounces@ietf.org] On Behalf Of Wanda Lo
Sent: 30 March 2011 09:01
To: 80all@ietf.org<mailto:80all@ietf.org>
Subject: [80all] Wednesday 3-30-2011 Agenda Change

Hi Everyone,

There's a room change in today's afternoon session I (13:00-15:00).

RTGAREA has moved to Congress Hall II.

CLUE has moved to Congress Hall I.


Please note it in on your pocket agenda to reflect the change.  Of course, =
the agenda on the IETF website (https://datatracker.ietf.org/meeting/80/age=
nda.html) always has the most up-to-date information.



Thanks,
Wanda




=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
Wanda Lo
Internet Engi neering span style=3D'mso-fareast-font-family:"Times New Roma=
n";color:black'>
48377 Fremont Blvd., Ste. 117
Fremont, California 94538 / USA
+1-510-492-4082
+1-510-492-4001 (fax)
www.ietf.org<http://www.ietf.org/>

--
Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com<http://www.amsl.com/>






