From rtgwg-bounces@ietf.org Thu Jul 05 14:38:51 2007
Return-path: <rtgwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6WE4-0004md-2W; Thu, 05 Jul 2007 14:38:48 -0400
Received: from rtgwg by megatron.ietf.org with local (Exim 4.43)
	id 1I6WE2-0004mP-TY
	for rtgwg-confirm+ok@megatron.ietf.org; Thu, 05 Jul 2007 14:38:46 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6WE2-0004m8-I6
	for rtgwg@ietf.org; Thu, 05 Jul 2007 14:38:46 -0400
Received: from dnsmx1pya.telcordia.com ([128.96.20.31])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6WE2-0003kn-9I
	for rtgwg@ietf.org; Thu, 05 Jul 2007 14:38:46 -0400
Received: from pya-dte-ieg01.cc.telcordia.com (pya-dte-ieg01.cc.telcordia.com
	[128.96.20.21])
	by dnsmx1pya.telcordia.com (8.11.7+Sun/8.9.3) with SMTP id l65IcJX06166
	for <rtgwg@ietf.org>; Thu, 5 Jul 2007 14:38:19 -0400 (EDT)
Received: from rrc-dte-exbh02.dte.telcordia.com ([128.96.109.16])
	by pya-dte-ieg01.cc.telcordia.com (SMSSMTP 4.1.9.35) with SMTP id
	M2007070514381715585
	for <rtgwg@ietf.org>; Thu, 05 Jul 2007 14:38:17 -0400
Received: from rrc-dte-exs01.dte.telcordia.com ([128.96.150.34]) by
	rrc-dte-exbh02.dte.telcordia.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 5 Jul 2007 14:38:17 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 5 Jul 2007 14:38:17 -0400
Message-ID: <A09345776B6C7A4985573569C0F3004314F21850@rrc-dte-exs01.dte.telcordia.com>
In-Reply-To: <34B3EAA5B3066A42914D28C5ECF5FEA40BF4B92D@zrtphxm2.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: A new I-D: remote LFAPs
Thread-Index: AccJmEhAi5u0lNNISPmbgf9tEF29VwA176WgLTB4I3A=
References: <34B3EAA5B3066A42914D28C5ECF5FEA40BF4B92D@zrtphxm2.corp.nortel.com>
From: "Hokelek, Ibrahim" <ihokelek@telcordia.com>
To: <rtgwg@ietf.org>
X-OriginalArrivalTime: 05 Jul 2007 18:38:17.0515 (UTC)
	FILETIME=[A75807B0:01C7BF33]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: A new I-D: remote LFAPs
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Errors-To: rtgwg-bounces@ietf.org

Hi all,

We have just submitted the following draft in which we describe a new=20
loop-free IP fast reroute mechanism by introducing the concept of=20
pre-computed remote Loop-Free Alternate Paths (rLFAPs). Our new draft
completely prevents micro-loops for single link failures and quickly=20
converges to a loop-free path in case of multiple link failures.

We would very much appreciate if you could review our draft and provide=20
your comments and suggestions. We are going to make a presentation of
our=20
ideas in the 69th IETF meeting in Chicago.

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

Regards,
Ibrahim Hokelek

|---------------------------------|
|  Ibrahim Hokelek                |=20
|  Telcordia Technologies, Inc.   |
|  Piscataway, NJ                 |
|  Phone: 732-699-3905            |
|  Fax:   732-336-7013            |
|---------------------------------|


_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Thu Jul 05 16:15:16 2007
Return-path: <rtgwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6XjP-0006A7-NF; Thu, 05 Jul 2007 16:15:15 -0400
Received: from rtgwg by megatron.ietf.org with local (Exim 4.43)
	id 1I6XjD-0005yZ-VI
	for rtgwg-confirm+ok@megatron.ietf.org; Thu, 05 Jul 2007 16:15:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6XjD-0005yR-IW; Thu, 05 Jul 2007 16:15:03 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I6XjD-00033U-8Q; Thu, 05 Jul 2007 16:15:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id D587A26EA0;
	Thu,  5 Jul 2007 20:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I6XjC-0002bZ-BK; Thu, 05 Jul 2007 16:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I6XjC-0002bZ-BK@stiedprstage1.ietf.org>
Date: Thu, 05 Jul 2007 16:15:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: rtgwg@ietf.org
Subject: I-D ACTION:draft-ietf-rtgwg-ipfrr-framework-07.txt 
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Errors-To: rtgwg-bounces@ietf.org

--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		: IP Fast Reroute Framework
	Author(s)	: M. Shand, S. Bryant
	Filename	: draft-ietf-rtgwg-ipfrr-framework-07.txt
	Pages		: 15
	Date		: 2007-7-5
	
This document provides a framework for the development of IP 
   fast-reroute mechanisms which provide protection against link or 
   router failure by invoking locally determined repair paths. Unlike 
   MPLS Fast-reroute, the mechanisms are applicable to a network 
   employing conventional IP routing and forwarding. An essential part 
   of such mechanisms is the prevention of packet loss caused by the 
   loops which normally occur during the re-convergence of the network 
   following a failure.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-ipfrr-framework-07.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-rtgwg-ipfrr-framework-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rtgwg-ipfrr-framework-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-5153418.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rtgwg-ipfrr-framework-07.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rtgwg-ipfrr-framework-07.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-5153418.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg

--NextPart--






From rtgwg-bounces@ietf.org Thu Jul 05 16:15:24 2007
Return-path: <rtgwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6XjY-0006La-4Q; Thu, 05 Jul 2007 16:15:24 -0400
Received: from rtgwg by megatron.ietf.org with local (Exim 4.43)
	id 1I6XjF-0005zC-9l
	for rtgwg-confirm+ok@megatron.ietf.org; Thu, 05 Jul 2007 16:15:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6XjE-0005yh-F2; Thu, 05 Jul 2007 16:15:04 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I6XjE-00033s-1t; Thu, 05 Jul 2007 16:15:04 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id D7C7E26EA1;
	Thu,  5 Jul 2007 20:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I6XjC-0002bS-9t; Thu, 05 Jul 2007 16:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I6XjC-0002bS-9t@stiedprstage1.ietf.org>
Date: Thu, 05 Jul 2007 16:15:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: rtgwg@ietf.org
Subject: I-D ACTION:draft-ietf-rtgwg-lf-conv-frmwk-01.txt 
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Errors-To: rtgwg-bounces@ietf.org

--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		: A Framework for Loop-free Convergence
	Author(s)	: S. Bryant, M. Shand
	Filename	: draft-ietf-rtgwg-lf-conv-frmwk-01.txt
	Pages		: 23
	Date		: 2007-7-5
	
This draft describes mechanisms that may be used to prevent or to    
   suppress the formation of micro-loops when an IP or MPLS network    
   undergoes topology change due to failure, repair or management    
   action.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-rtgwg-lf-conv-frmwk-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rtgwg-lf-conv-frmwk-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-5152927.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rtgwg-lf-conv-frmwk-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rtgwg-lf-conv-frmwk-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-5152927.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg

--NextPart--






From rtgwg-bounces@ietf.org Thu Jul 05 16:15:36 2007
Return-path: <rtgwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6Xjk-0006ez-57; Thu, 05 Jul 2007 16:15:36 -0400
Received: from rtgwg by megatron.ietf.org with local (Exim 4.43)
	id 1I6XjG-00061E-9h
	for rtgwg-confirm+ok@megatron.ietf.org; Thu, 05 Jul 2007 16:15:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6XjE-0005yr-LA; Thu, 05 Jul 2007 16:15:04 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I6XjE-00033q-1u; Thu, 05 Jul 2007 16:15:04 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id E024626EA5;
	Thu,  5 Jul 2007 20:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I6XjC-0002bf-CW; Thu, 05 Jul 2007 16:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I6XjC-0002bf-CW@stiedprstage1.ietf.org>
Date: Thu, 05 Jul 2007 16:15:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: rtgwg@ietf.org
Subject: I-D ACTION:draft-ietf-rtgwg-ipfrr-notvia-addresses-01.txt 
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Errors-To: rtgwg-bounces@ietf.org

--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		: IP Fast Reroute Using Not-via Addresses
	Author(s)	: S. Bryant, et al.
	Filename	: draft-ietf-rtgwg-ipfrr-notvia-addresses-01.txt
	Pages		: 23
	Date		: 2007-7-5
	
This draft describes a mechanism that provides fast reroute in an IP 
   network through encapsulation to "not-via" addresses. A single level 
   of encapsulation is used. The mechanism protects unicast, multicast 
   and LDP traffic against link, router and shared risk group failure, 
   regardless of network topology and metrics.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-rtgwg-ipfrr-notvia-addresses-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rtgwg-ipfrr-notvia-addresses-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-5153808.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rtgwg-ipfrr-notvia-addresses-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rtgwg-ipfrr-notvia-addresses-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-5153808.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg

--NextPart--





From rtgwg-bounces@ietf.org Mon Jul 09 01:12:55 2007
Return-path: <rtgwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7lYL-0001gz-2o; Mon, 09 Jul 2007 01:12:53 -0400
Received: from rtgwg by megatron.ietf.org with local (Exim 4.43)
	id 1I7lYJ-0001gl-FV
	for rtgwg-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 01:12:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7lYH-0001gb-21
	for rtgwg@ietf.org; Mon, 09 Jul 2007 01:12:49 -0400
Received: from wa-out-1112.google.com ([209.85.146.182])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7lYD-0003Re-N8
	for rtgwg@ietf.org; Mon, 09 Jul 2007 01:12:49 -0400
Received: by wa-out-1112.google.com with SMTP id k17so1370219waf
	for <rtgwg@ietf.org>; Sun, 08 Jul 2007 22:12:45 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=m7l3+31Br/0lgZehlMmrWVQFV9nLIKseEO6gO0VDopm6T6j+RFJN+8Xdf8jNRKjBp8iABIJKkp7dI2sRTa6opcqUoEUlj+PiGgWbNZmciMBZ/pukujJzFQjACfaKJqChhOmbluPV7hSkfLeiTWQrMMGiWCOWP2BsbnieY9lFefc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=J9zh0ITZ5gT7EvqX9gqRI9CXGwOf5dK7jGpH3uyAlErt5LCusAnqXrBnzdjd5cSGHc+cFxPCUMAmY02bPYlsZncurX6DX3DlyrCfoYFpRkIfY3Usqm+QIHyhr4EYMCAl4NabfydyTJDIMrYsLjFM8Hum4oV9sm1LJI51qSEGcRQ=
Received: by 10.115.94.1 with SMTP id w1mr2769476wal.1183957965138;
	Sun, 08 Jul 2007 22:12:45 -0700 (PDT)
Received: by 10.114.108.5 with HTTP; Sun, 8 Jul 2007 22:12:45 -0700 (PDT)
Message-ID: <100ba11b0707082212q517460cuf0aee97a215c5100@mail.gmail.com>
Date: Mon, 9 Jul 2007 10:42:45 +0530
From: "janardhan kulkarni" <janardhan.kulkarni@gmail.com>
To: rtgwg@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: Kindly review our new draft. Thanks.
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1779282488=="
Errors-To: rtgwg-bounces@ietf.org

--===============1779282488==
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: base64
Content-Disposition: inline

SGksCgpLaW5kbHkgcmV2aWV3IG91ciBuZXcgZHJhZnQgb24gUklQL1JJUE5HIHRvIHN1cHBvcnQg
ZXF1YWwgY29zdCByb3V0ZXMKYW5kIHNwbGl0IGhvcm96b24gYW5kIHBvaXNvbiBjaGVja3MgZm9y
IHN1Y2ggcm91dGVzLiBPdXIgYWltIGlzCmRvY3VtZW50IHJ1bGVzIGRvaW5nIHNwbGl0IGFuZCBw
b2lzb24gY2hlY2tzIGZvciB0aGVzZSByb3V0ZXMgYW5kIHdlCmFpbSB0byBtYWtlIGl0IGFuIGlu
Zm9ybWF0aW9uYWwgZHJhZnQuCgpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvd2cvcnRnd2cvZHJhZnQt
amFuYXJkaGFuLW5hdmVlbi1ydGd3Zy1lcXVhbGNvc3Ryb3V0ZXMtcmlwLTAwLnR4dAoKQnJpZWYg
aW50cm9kdWN0aW9uIGZyb20gb3VyIHdvcms6LQpSSVAgdjIgYXMgZGVzY3JpYmVkIGluIFJGQyAy
NDUzIGFuZCBSSVBORyBhcyBkZXNjcmliZWQgaW4gUkZDIDIwODAsCmRvIG5vdCBzdXBwb3J0IGxl
YXJuaW5nIG11bHRpcGxlIGVxdWFsIGNvc3Qgcm91dGVzIHRvIGEgZGVzdGluYXRpb24KdGhyb3Vn
aCBkaWZmZXJlbnQgbmVpZ2hib3JzLkJ1dCBpbiB0b2Rhee+/vXMgaW50ZXJuZXQgaXQgaXMgdmVy
eQpjb21tb24gdG8gaGF2ZSB0b3BvbG9naWVzIHdoZXJlIHRoZXJlIGFyZSBtb3JlIHRoYW4gb25l
IHJvdXRlIHRvIGEKZGVzdGluYXRpb24uIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIHRoZSBtb2Rp
ZmljYXRpb25zIHRvIHRoZQpSSVAvUklQTkcgcHJvdG9jb2xzIHRvIGhhbmRsZSB0aGlzIHNjZW5h
cmlvIGFuZCBkZXNjcmliZXMgaG93IHRvCmFwcGx5IHRoZSBzcGxpdCBob3Jpem9uIGFuZCBwb2lz
b24gcmV2ZXJzZSBmb3Igc3VjaCByb3V0ZXMuIEl0IGlzCnNpbXBsZSwgbGlnaHQgYW5kIGlzIGNv
bXBhdGlibGUgd2l0aCB0aGUgaW1wbGVtZW50YXRpb25zIHdoaWNoIGRvIG5vdApzdXBwb3J0IHRo
aXMgZmVhdHVyZS4KVGhlIG1haW4gbW90aXZhdGlvbiBiZWhpbmQgdGhpcyBkcmFmdCBpcyB0byBk
b2N1bWVudCBydWxlcyBmb3IgUklQLwpSSVBORyB0byBoYW5kbGUgZXF1YWwgY29zdCByb3V0ZXMg
dG8gYSBkZXN0aW5hdGlvbiwgc2luY2UgbW9zdCBvZiB0aGUKdmVuZG9ycyBhbHJlYWR5IHN1cHBv
cnQgdGhpcyBmZWF0dXJlLiBCdXQgdGhlcmUgaXMgbm8gY29uY29yZCBvbiBob3cKdG8gYXBwbHkg
dGhlIHNwbGl0IGhvcml6b24vcG9pc29uIGNoZWNrcyBmb3Igc3VjaCByb3V0ZXMuIEluIGZhY3Qs
Cm1vc3Qgb2YgdGhlIHBvcHVsYXIgdmVuZG9ycyBhcHBseSB0aGUgc3BsaXQvcG9pc29uIGNoZWNr
cyBpbiBhIHdyb25nCndheS4gVGhpcyBkcmFmdCBleHBsaWNhdGVzIHRoZSBwcm9wZXIgaW1wbGVt
ZW50YXRpb24gb2YgdGhlIGFib3ZlCmZlYXR1cmVzLiBBbHNvLCBzaW5jZSBSSVBORyBpcyBnZXR0
aW5nIGRlcGxveWVkLHRoZXNlIGZlYXR1cmVzIGNhbiBiZQppbmNsdWRlZCB3aGlsZSBkZXZlbG9w
aW5nIFJJUE5HLgoKLS0KQnllLApKYW5hcmRoYW4uCiJJIGhhdmUgbmV2ZXIgYmVlbiBodXJ0IGJ5
IHdoYXQgSSBoYXZlIG5vdCBzYWlkLiIKICAtQ2FsdmluIENvb2xpZGdlCgoKLS0gCkJ5ZSwKSmFu
YXJkaGFuLgoiSSBoYXZlIG5ldmVyIGJlZW4gaHVydCBieSB3aGF0IEkgaGF2ZSBub3Qgc2FpZC4i
CiAgLUNhbHZpbiBDb29saWRnZQo=



--===============1779282488==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg

--===============1779282488==--



From rtgwg-bounces@ietf.org Mon Jul 09 13:15:42 2007
Return-path: <rtgwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7wpp-0007Yz-ER; Mon, 09 Jul 2007 13:15:41 -0400
Received: from rtgwg by megatron.ietf.org with local (Exim 4.43)
	id 1I7wpl-0007SJ-1L
	for rtgwg-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 13:15:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7wpj-0007Px-Oo; Mon, 09 Jul 2007 13:15:35 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I7wpj-00062N-FP; Mon, 09 Jul 2007 13:15:35 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 6F816328EF;
	Mon,  9 Jul 2007 17:15:05 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I7wpE-00047e-Vk; Mon, 09 Jul 2007 13:15:05 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I7wpE-00047e-Vk@stiedprstage1.ietf.org>
Date: Mon, 09 Jul 2007 13:15:04 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: rtgwg@ietf.org
Subject: I-D ACTION:draft-ietf-rtgwg-ordered-fib-01.txt 
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Errors-To: rtgwg-bounces@ietf.org

--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		: Loop-free convergence using oFIB
	Author(s)	: P. Francois, et al.
	Filename	: draft-ietf-rtgwg-ordered-fib-01.txt
	Pages		: 15
	Date		: 2007-7-9
	
This draft describes a mechanism for use in conjunction with link
   state routing protocols which prevents the transient loops which
   would otherwise occur during topology changes.  It does this by
   correctly sequencing the FIB updates on the routers.

   This mechanism can be used in the case of non-urgent link or node
   shutdowns and restarts or link metric changes.  It can also be used
   in conjunction with a FRR mechanism which converts a sudden link or
   node failure into a non-urgent topology change.  This is possible
   where a complete repair path is provided for all affected
   destinations.

   After a non-urgent topology change, each router computes a rank that
   defines the time at which it can safely update its FIB.  A method for
   accelerating this loop-free convergence process by the use of
   completion messages is also described.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-rtgwg-ordered-fib-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rtgwg-ordered-fib-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-9123133.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rtgwg-ordered-fib-01.txt

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

Content-Type: text/plain
Content-ID: <2007-7-9123133.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg

--NextPart--





From rtgwg-bounces@ietf.org Mon Jul 09 14:15:52 2007
Return-path: <rtgwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7xm3-0004rf-VP; Mon, 09 Jul 2007 14:15:51 -0400
Received: from rtgwg by megatron.ietf.org with local (Exim 4.43)
	id 1I7xll-0004Gv-9t
	for rtgwg-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 14:15:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7xlk-0004DX-IS; Mon, 09 Jul 2007 14:15:32 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I7xlk-00085x-Am; Mon, 09 Jul 2007 14:15:32 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 4D1AB328BD;
	Mon,  9 Jul 2007 18:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I7xlG-0006dg-6e; Mon, 09 Jul 2007 14:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I7xlG-0006dg-6e@stiedprstage1.ietf.org>
Date: Mon, 09 Jul 2007 14:15:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: rtgwg@ietf.org
Subject: I-D ACTION:draft-ietf-rtgwg-ipfrr-spec-base-07.txt 
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Errors-To: rtgwg-bounces@ietf.org

--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		: Basic Specification for IP Fast-Reroute: Loop-free Alternates
	Author(s)	: A. Atlas, A. Zinin
	Filename	: draft-ietf-rtgwg-ipfrr-spec-base-07.txt
	Pages		: 29
	Date		: 2007-7-9
	
This document describes the use of loop-free alternates to provide
  local protection for unicast traffic in pure IP and MPLS/LDP networks
  in the event of a single failure, whether link, node or shared risk
  link group (SRLG).  The goal of this technology is to reduce the
  micro-looping and packet loss that happens while routers converge
  after a topology change due to a failure.  Rapid failure repair is
  achieved through use of precalculated backup next-hops that are loop-
  free and safe to use until the distributed network convergence
  process completes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-ipfrr-spec-base-07.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-rtgwg-ipfrr-spec-base-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rtgwg-ipfrr-spec-base-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-9132122.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rtgwg-ipfrr-spec-base-07.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rtgwg-ipfrr-spec-base-07.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-9132122.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg

--NextPart--






From rtgwg-bounces@ietf.org Tue Jul 10 15:20:24 2007
Return-path: <rtgwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8LFx-0005hJ-6v; Tue, 10 Jul 2007 15:20:17 -0400
Received: from rtgwg by megatron.ietf.org with local (Exim 4.43)
	id 1I8LFw-0005gT-7Y
	for rtgwg-confirm+ok@megatron.ietf.org; Tue, 10 Jul 2007 15:20:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8LFv-0005fN-Sl; Tue, 10 Jul 2007 15:20:15 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I8LEz-0000FA-JW; Tue, 10 Jul 2007 15:20:15 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 7D78426EBB;
	Tue, 10 Jul 2007 19:19:17 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I8LEz-0004fV-DU; Tue, 10 Jul 2007 15:19:17 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1I8LEz-0004fV-DU@stiedprstage1.ietf.org>
Date: Tue, 10 Jul 2007 15:19:17 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: rtgwg mailing list <rtgwg@ietf.org>,
	Internet Architecture Board <iab@iab.org>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'The Generalized TTL Security 
 Mechanism (GTSM)' to Proposed Standard 
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Errors-To: rtgwg-bounces@ietf.org

The IESG has approved the following document:

- 'The Generalized TTL Security Mechanism (GTSM) '
   <draft-ietf-rtgwg-rfc3682bis-10.txt> as a Proposed Standard

This document is the product of the Routing Area Working Group. 

The IESG contact persons are Ross Callon and David Ward.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-rfc3682bis-10.txt

Technical Summary
 
  The use of a packet's Time to Live (TTL) (IPv4) or Hop Limit (IPv6)
  to verify whether the packet was originated by an adjacent node on a
  connected link has been used in many recent protocols.  This document
  generalizes this technique.  This document obsoletes RFC 3682.

Working Group Summary
 
  No dissent reported. This document defines an easy-to-deploy 
  (ie easy to configure) and computationally simple / efficient 
  mechanism which might be considered to be less robust than 
  cryptographic authentication techniques, and as such there is 
  inevitably some difference of opinion regarding how valuable 
  this is. On many platforms this technique is computationally 
  significantly more efficient than cryptographic authentication 
  methods, and therefore may be more effective against DOS attacks. 
 
Protocol Quality
 
  Ross Callon has reviewed this spec for the IESG. This document 
  updates an experimental RFC that is implemented and widely deployed.



_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Wed Jul 18 14:07:18 2007
Return-path: <rtgwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBDvc-0004BM-M1; Wed, 18 Jul 2007 14:07:12 -0400
Received: from rtgwg by megatron.ietf.org with local (Exim 4.43)
	id 1IBDvb-00049r-3Z
	for rtgwg-confirm+ok@megatron.ietf.org; Wed, 18 Jul 2007 14:07:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBDva-00049j-Pr
	for rtgwg@ietf.org; Wed, 18 Jul 2007 14:07:10 -0400
Received: from szxga01-in.huawei.com ([61.144.161.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBDvX-0000PS-TF
	for rtgwg@ietf.org; Wed, 18 Jul 2007 14:07:10 -0400
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JLD00C3PZMV71@szxga01-in.huawei.com> for
	rtgwg@ietf.org; Thu, 19 Jul 2007 02:06:32 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JLD0000PZMQAW@szxga01-in.huawei.com> for
	rtgwg@ietf.org; Thu, 19 Jul 2007 02:06:31 +0800 (CST)
Received: from [127.0.0.1] ([10.18.4.187])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JLD00FY5ZMO5Y@szxml04-in.huawei.com> for
	rtgwg@ietf.org; Thu, 19 Jul 2007 02:06:26 +0800 (CST)
Date: Wed, 18 Jul 2007 23:36:22 +0530
From: Saravana K <saravanak@huawei.com>
To: rtgwg@ietf.org
Message-id: <469E569E.8070909@huawei.com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_XA3hSnf/wOY14mcuWGGl/g)"
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 826b8da4948b827b02e4b599895c9e48
Cc: Janardhan Kulkarni <Janardhan.Kulkarni@citrix.com>
Subject: draft-kumar-kulkarni-riprestart-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Errors-To: rtgwg-bounces@ietf.org

This is a multi-part message in MIME format.

--Boundary_(ID_XA3hSnf/wOY14mcuWGGl/g)
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT

Hi All,

We have written a new draft proposing a set of restart signaling 
extensions for the RIP protocol. Currently we discovered some issues 
related to route path flapping when a RIP router undergoes a restart and 
came up with a mechanism to avoid it. I request you all to please go 
through the draft and give us your comments. I will be presenting the 
idea behind the same in the upcoming IETF-69 meeting.

The draft is attached in this mail as i had missed the ID submission 
cutoff date.

Thanks,
Saravana


--Boundary_(ID_XA3hSnf/wOY14mcuWGGl/g)
Content-type: text/plain; name=draft-kumar-kulkarni-riprestart-00.txt
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=draft-kumar-kulkarni-riprestart-00.txt

Network Working Group                                    Saravana Kumar 
Internet Draft                                      Huawei Technologies 
Intended status: Standard                            Janardhan Kulkarni 
Expires: January 2008                                            Citrix 
                                                          July 18, 2007 
                                    
 
                                      
                          RIP Restart Extensions 
                draft-kumar-kulkarni-riprestart-00.txt 


Status of this Memo 

   By submitting this Internet-Draft, each author represents that       
   any applicable patent or other IPR claims of which he or she is       
   aware have been or will be disclosed, and any of which he or she       
   becomes aware will be disclosed, in accordance with Section 6 of       
   BCP 79. 

   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 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 January 18, 2007. 

Copyright Notice 

   Copyright (C) The IETF Trust (2007). 

 

 

 

 
 
 
<Kumar-Kulkarni>       Expires January 18, 2008                [Page 1] 

Internet-Draft          RIP Restart Signaling                 July 2007 
    

Abstract 

   This draft proposes a restart signaling mechanism for the RIP 
   protocol to effectively eliminate the routing disturbances in the 
   network when a RIP router is restarted. The basic idea is for the 
   restarting RIP router to not update its routing tables and not 
   advertise any route information before it receives the routing 
   information from all its peers. In addition to the base restart 
   signaling mechanism this document also describes a mechanism for 
   deterministically selecting equal cost routes and a security 
   enhancement to recover the cryptographic sequence number after a 
   restart. These enhancements will help the RIP router to continue 
   functioning in the same way after a restart as if nothing happened to 
   it. 

    

1. Introduction 

   By its very nature the RIP protocol ([RIP], [RIP2]) is to an extent 
   resilient to protocol and system restarts. There is no stateful 
   neighbor relationship maintained and the routes have a relatively 
   comfortable ageing time of (typical) 180 seconds. So the base RIP 
   protocol does not have many of the issues faced by the other link 
   state protocols like ISIS and OSPF during a restart (the term 
   'restart' applies equally to both the protocol level restart and a 
   control plane restart). But its behavior is not perfect either and 
   could cause some routing disturbances in the network as described 
   below. 

   When the RIP router comes up after a restart (either a protocol level 
   or a system level restart) it will send out a full table request over 
   all its enabled interfaces and start receiving the route updates from 
   its peers. As and when the new route updates are received the router 
   will update its forwarding table and propagate these routes to its 
   peers. This premature behavior will disrupt the packet forwarding in 
   the network, mainly resulting in a switch in the packet flow to a low 
   preference path and back again to the preferred path. If equal cost 
   paths are present in the network then there might be a permanent 
   switch to a different set of paths after a router restart. This kind 
   of disturbance to the network can be eliminated using a simple 
   restart signaling mechanism described in this document. The mechanism 
   also provides certain additional benefits like preventing aging out 
   of routes in the peers during a restart, detecting topology changes, 
   protecting against replay attacks in the network etc. 

    

 
 
<Kumar-Kulkarni>       Expires January 18, 2008                [Page 2] 

Internet-Draft          RIP Restart Signaling                 July 2007 
    

   The basic idea behind the restart signaling mechanism is similar to 
   the ones used in other protocols. The entire restart mechanism works 
   in three different phases. In the first Helper Solicitation Phase the 
   restarting router requests its peers to help by sending a full 
   routing table update and notifying the restarting route when the 
   update is over. Next during the Route Update Phase the restarting 
   router tracks the route update progress of all its peers and builds 
   its routing database. Finally during the Restart Complete phase the 
   restarting router updates its forwarding tables with the route 
   information and begins sending route updates to its peers. 

    

2. RIP Extension Message format 

   In order to support the restart extensions and any other extensions 
   in the future a new message has been introduced. This message can 
   carry different types of notifications, acknowledgements along with 
   multiple options. The format of this new RIP extension message is: 

    

    0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |    Command    |     Version   |     Type      |  Option Num   | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |             0xFFFF            |    Authentication Type        | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   ~                     Authentication Data(16)                   ~ 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |         Option Type           |         Option Length         | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |                                                               | 
   ~                           Option Data                         ~ 
   |                                                               | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   ~                     Authentication Trailer                    ~ 
   +---------------------------------------------------------------+ 

    
   Command: 
   A new command type 7 has been introduced to denote the Extension 
   Message 

   Version: 
   The version field is not modified. 
 
 
<Kumar-Kulkarni>       Expires January 18, 2008                [Page 3] 

Internet-Draft          RIP Restart Signaling                 July 2007 
    

   Type: 
   This field indicates the type of the extension message. Currently 
   there are 8 different message types. 

      1 - Restart Notification (RN) 
      2 - Restart Acknowledgment (RA) 
      3 - Update Complete Notification (UCN) 
      4 - Update Complete Acknowledgement (UCA) 
      5 - Restart Abort Notification (RAN) 
      6 - Restart Abort Acknowledgement (RAA) 
      7 - Restart Complete Notification (RCN) 
      8 - Restart Complete Acknowledgement (RCA) 
      9 - Sequence Number Request 
     10 - Sequence Number Reply 
    
   Option Num: 
   Some extension messages may carry some additional information in 
   options. This field indicates how many such options are present in 
   the message. 

   Options: 
   All the options are encoded in a Type, Length and Value format. The 
   2-byte type field identifies the option, the 2-byte length field 
   indicates the length of the value field in bytes and the Value field 
   can be of zero or more bytes as denoted by the length field.  

    
   The values of different Option Types are listed below: 
    
      1 - Neighbor-List Option 
      2 - Delayed-Restart Option 
      3 - Sequence Number Option 
    

   If the option type field carries a value of 0xFFFF then it denotes 
   authentication information as defined in [RFC-2082] and [RFC-4822]. 
    

3. Planned and Unplanned restarts 

   A router can undergo a restart due to two reasons, a planned restart 
   or an unplanned restart. An unplanned restart happens when there is 
   some failure in the control plane of a router and it immediately 
   switches over to a standby board. This event cannot be predicted 
   beforehand and the RIP protocol should start its restart processing 
   when it comes up after the unplanned restart. On the other hand a 
   planned restart is a controlled event initiated by a network 
   administrator, typically to upgrade the hardware/software in the 
 
 
<Kumar-Kulkarni>       Expires January 18, 2008                [Page 4] 

Internet-Draft          RIP Restart Signaling                 July 2007 
    

   router. RIP can take some advantage of this event to pre-notify its 
   peers about the pending failure and enable them to play a better 
   supporting role. 

   When a router is scheduled to undergo a planned restart it SHOULD 
   inform its peers about this by sending out a Restart Notification 
   message with a Delayed-Restart Option. The time interval for which 
   the restarting router is expected to be down is also mentioned in the 
   Restart-Time field in the Delayed-Restart Option. This will ensure 
   that the peers do not let the routes from the restarting router to be 
   aged out while it is being restarted. Another advantage to informing 
   the peer early is that the helper can track topology changes from the 
   moment the restarting router goes down. 

    

4. Helper Solicitation Phase 

4.1. Actions of the Restarting router 

   When the restarting router comes up after a Planned or an Un-planned 
   restart it MUST immediately notify all its peers about its state by 
   sending out a Restart Notification (RN) message without the 'Delayed-
   Restart' option. Along with the Restart Notification a Full Table 
   Request message MUST also be sent over all the interfaces. This will 
   ensure that the restart incapable routers on the link start sending 
   their route updates to the restarting router. If no processing to 
   recover the sequence number (see Section 8) is carried out then both 
   the RN and the Full Table Request messages MUST be generated with a 
   sequence number of zero (even when they are being retransmitted). 

   The Restart Notification (RN) message SHOULD be retransmitted for a 
   predetermined number of times to ensure its reliable receipt over the 
   link. On a point-to-point link the retransmission SHOULD be stopped 
   once a valid Restart Acknowledgement message is received. On a multi-
   access link however the RN message SHOULD be re-transmitted for the 
   predetermined number of times irrespective of whether a RA was 
   received over the link or not. Each RN message sent on a link MUST 
   have a 'Neighbor-List' option containing the list of neighbors from 
   whom a RA message was received already. This will help prevent the 
   peer router from sending the RA multiple times. 







 
 
<Kumar-Kulkarni>       Expires January 18, 2008                [Page 5] 

Internet-Draft          RIP Restart Signaling                 July 2007 
    

   Once a RA is received from a peer, the restarting router SHOULD mark 
   that peer as 'Restart-Capable'. If no RA is received from a peer even 
   after resending the RN message for the pre-determined number of 
   times, then the restarting router SHOULD mark that peer as 'Restart-
   Incapable'. A static-update-timer MUST be started for each of the 
   'Restart-Incapable' peers to statically track their route update 
   progress. 

4.2. Actions of the Helper router 

   On receiving the Restart Notification message from the restarting 
   router, a Restart-Capable router SHOULD check if its interface 
   address is present in the Neighbor-List option of the RN message. If 
   so then the peer router MUST ignore the (retransmitted) RN message. 
   Otherwise the peer should do some checks to decide if it can act as a 
   helper to the restarting router or not. 

   o  If the peer router has an existing neighbor relationship with the 
      restarting router then it SHOULD act as a helper for the 
      restarting router. 

   o  If the peer router is also undergoing the restart process then it 
      SHOULD NOT act as a helper for the restarting router. 

   The peer router decides not to act as a helper it indicates a 
   topology change event and the peer MAY send a Restart Abort 
   Notification message to tell the restarting router to stop its 
   restart processing. Otherwise the peer SHOULD mark itself as the 
   'Helper' for the restarting router and send a Restart Acknowledgement 
   (RA) message. Once the peer enters the 'Helper' mode it should do the 
   following additional processing. 

   o  If the 'Delayed-Restart' Option is present in the RN message then 
      Helper router SHOULD set the status of the restarting router as 
      RESTART_INACTIVE and SHOULD reset the age time for all the routes 
      learnt from the restarting router to the 'Restart-Time' value 
      specified in the RN message. It SHOULD NOT send its full table 
      route updates to the restarting router. 

   o  If the 'Delayed-Restart' Option is NOT present in the RN message 
      then Helper router SHOULD set the status of the restarting router 
      as RESTART_ACTIVE and SHOULD refresh the age time for all the 
      routes learnt from the restarting router. And it SHOULD start 
      sending its full table route updates to the restarting router. 




 
 
<Kumar-Kulkarni>       Expires January 18, 2008                [Page 6] 

Internet-Draft          RIP Restart Signaling                 July 2007 
    

   If a Helper router receives a Full Table Request from the restarting 
   router while it is still in the helper mode it SHOULD ignore the 
   message.  
    

5. Route Update Phase 

5.1. Actions of the Restarting router 

   On entering the Restart mode, the main job of the restarting router 
   is to build its route database and determine when it has finished 
   receiving route updates from all its peers. During this time the 
   restarting router MUST NOT update its forwarding table with the 
   learnt routes and it MUST NOT send out any route updates (neither 
   periodic nor triggered) to any of its peers.  

   The route update progress of each peer is tracked separately by the 
   restarting router. As an added safety mechanism the restarting router 
   should start a RESTART_CUTOFF_TIMER (300s), which will forcefully end 
   the route update phase. For a 'Restart-Capable' peer the route update 
   is considered to be over upon receiving a Update Complete 
   Notification (UCN) message from that peer. For a 'Restart-Incapable' 
   peer its route update is considered to be over when its static-
   update-timer expired. The route update phase is considered to be over 
   in the following cases. 

   o  Route update is completed for all its peers. 

   o  A Restart Abort Notification message is received from any of its 
      peers. 

   o  The restarting router detects a topology change locally. 

   o  The RESTART_CUTOFF_TIMER expires. 

    

5.2. Actions of the Helper router 

   Once the helper router has completed sending all its route updates to 
   the restarting router it SHOULD send a Update Complete Notification 
   (UCN) message directly to the restarting router. This message must be 
   retransmitted for a pre-determined number of times until an Update 
   Complete Acknowledgement (UCA) message is received from the 
   restarting router. 



 
 
<Kumar-Kulkarni>       Expires January 18, 2008                [Page 7] 

Internet-Draft          RIP Restart Signaling                 July 2007 
    

6. Restart Complete Phase 

6.1. Actions of the Restarting Router 

   On exiting the Restart mode, the restarting router SHOULD perform the 
   following actions: 

   o  Update all the learnt routes to the forwarding table and flush out 
      any stale route entries that might've been added before the 
      restart happened. 

   o  Start the processing to send out periodic updates over all 
      interfaces. 

   o  Send a Restart Complete Notification (RCN) message over all its 
      interfaces. The RCN message is re-transmitted till the Restart 
      Complete Acknowledgement (RCA) is received from all the 'Restart-
      Capable' peers on an interface. Each time the RCN message is re-
      transmitted it SHOULD include the list of routers from which a RCA 
      has already been received. 

 

6.2. Actions of the Helper router 

   A Helper router SHOULD reset its Helper mode status for a restarting 
   neighbor once it receives the Restart Complete Notification (RCN) 
   from that neighbor or when the neighbor is deleted. On receiving the 
   RCN message that needs to be acknowledged it SHOULD immediately send 
   a Restart Complete Acknowledgement (RCA) back and reset the Helper 
   status for that neighbor. 

    

7. ECMP routes selection 

   ECMP support for RIP is widely implemented by many of the vendors 
   today and [RIP-ECMP] provides some recommendations for the same. One 
   of the aspects of ECMP that needs to be considered for un-interrupted 
   forwarding is the selection procedure for the equal cost paths. 
   Typically when RIP (or any protocol) has a set of ECMP routes to 
   choose from for a particular destination, depending on the system 
   configuration, it will choose a subset of these routes and discard 
   the rest. If the selection of these routes is in a first come first 
   serve basis, then the set of ECMP routes selected by a RIP router 
   before and after a restart would be different. This will affect the 
   forwarding in the network. 

 
 
<Kumar-Kulkarni>       Expires January 18, 2008                [Page 8] 

Internet-Draft          RIP Restart Signaling                 July 2007 
    

   This problem can be avoided if RIP chooses its equal cost paths in a 
   deterministic manner. The paths MAY chosen based on the neighbor and 
   nexthop IP address information associated with the routes, giving 
   preference to the routes with smaller neighbor and nexthop addresses. 
   One of the disadvantages with this method is that if the 'preferred' 
   neighbor is unstable, then still its routes will be learnt instead of 
   the more stable routes from a different neighbor. Implementers must 
   consider this issue carefully before going for a deterministic ECMP 
   selection mechanism. 

    

8. Handling topology changes 

   If during the restart processing there is any change in the topology 
   then it is RECOMMENDED that the restarting router exit the Restart 
   mode immediately. Topology change can be detected by either the 
   restarting router or the helper. A couple of recommended topology 
   change detection mechanisms are described below, however the 
   implementations are free to choose their own mechanism. 

   o  If a Helper router needs to send some triggered updates to the 
      restarting router, then it indicates a topology change.  

   o  Any local configuration change in the restarting router or the 
      helper router that would change their route advertisements. 

   If the Helper router detects any topology change it SHOULD send a 
   Restart Abort Notification (RAN) message to the restarting router. 
   This message is sent only if the restarting router's state is 
   RESTART_ACTIVE. Otherwise the helper SHOULD wait until the status 
   changes to RESTART_ACTIVE and then send the RAN message. The RAN 
   message SHOULD be retransmitted for a predetermined number of times 
   until the Restart Abort Acknowledgement message is received from the 
   restarting router. 

    

9. Security Considerations 

9.1. Sequence number re-acquisition during restart. 

   [RIPMD5] allows a RIP router to accept a cryptographically protected 
   packet with sequence number of zero. This opens up the RIP protocol 
   to replay attacks as documented in [CRYPT]. The Restart Notification 
   message will usually be the first RIP packet sent out of an interface 
   after a restart and will have a sequence number of zero and is 
   vulnerable to such replay attacks. This section describes how a 
 
 
<Kumar-Kulkarni>       Expires January 18, 2008                [Page 9] 

Internet-Draft          RIP Restart Signaling                 July 2007 
    

   restarting router can re-acquire its sequence number from its helper, 
   using the sequence number request and reply messages. It is assumed 
   in this section that all the routers involved are using sequence 
   number based cryptographic authentication mechanisms. 

   When RIP is enabled on any interface it SHOULD first try to recover 
   its sequence number before sending any other packets. This is 
   achieved by sending out a Sequence-Number-Request message containing 
   a Sequence Number option. For a request message the sequence number 
   field is set to zero and the Session ID field SHOULD be set to a 
   random number that will be used for the rest of the sequence number 
   re-acquisition processing.  

    

   0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |       Option Type (3)         |       Option Length (8)       | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |                           Session ID                          | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |                         Sequence Number                       | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
    

   On receiving a Sequence-Number-Request message over an interface, a 
   RIP router SHOULD reply with a Sequence-Number-Response message. The 
   Session ID value MUST be the same as the one on the Request message. 
   The Sequence Number field SHOULD be set to the last received sequence 
   number from the originating router or if there is no neighbor 
   relationship with the originating router then the value SHOULD be set 
   to zero. 

   When the originator of the request messages gets the Sequence Number 
   Response message it SHOULD first check the Session ID field to ensure 
   that the Session ID value is the same as the one it generated. If the 
   Session ID value is different (possible replayed packet) then the 
   response message MUST be dropped. Otherwise the router SHOULD use the 
   sequence number mentioned in the response message to generate its 
   other messages. The Sequence Number Request message must be re-
   transmitted a pre-determined number of times till a response is 
   received over the interface If no response is received then it should 
   generate its packets starting with a sequence number of zero. 

   This sequence number re-acquisition capability can be optionally 
   enabled by the administrator on an interface. If this capability is 
   enabled then the router SHOULD NOT accept any messages with sequence 

 
 
<Kumar-Kulkarni>       Expires January 18, 2008               [Page 10] 

Internet-Draft          RIP Restart Signaling                 July 2007 
    

   number zero from a router with which it already has a neighbor 
   relationship. 

    

10. IANA Considerations 

   IANA is requested to update the RIP message types   
   (http://www.iana.org/assignments/rip-types) so that the message type 
   7 refers to this document's RFC number. 

    

11. Acknowledgments 

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

    






























 
 
<Kumar-Kulkarni>       Expires January 18, 2008               [Page 11] 

Internet-Draft          RIP Restart Signaling                 July 2007 
    

APPENDIX A: Message Format 

A.1. Restart Notification/Acknowledgement (RN/RA): 

   The Restart Notification (RN) message is sent by the restarting 
   router to all the RIP routers on a particular link. The neighbor list 
   option MUST be included in the RN message only if the restarting 
   router has received acknowledgement from any routers on the link. The 
   neighbor list option contains a list of 4-byte IP addresses of the 
   acknowledging RIP routers.  

   The Restart Acknowledgment (RA) message is sent by the Helper 
   directly to the restarting router. The neighbor list option SHOULD 
   NOT be included in the RA message.  

    0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |   Command(7)  |   Version(2)  |   Type(1/2)   | Option Num(1) | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |       Option Type(1)          |        Option Length(8)       | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |                         NBR IP Address                        | 
   +-------------------------------+-------------------------------+ 
   |                         NBR IP Address                        | 
   +-------------------------------+-------------------------------+ 
    

A.2. Update Complete Notification/Acknowledgement (UCN/UCA): 

   The Update Complete Notification (UCN) message is sent by the Helper 
   to the restarting router. The 'option num' field is set to zero. 

   The Update Complete Acknowledgement (UCA) message is sent by the 
   restarting router to the Helper that had sent it the Update Complete 
   Notification message. The 'option num' field is set to zero. 

    0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |   Command(7)  |   Version(2)  |   Type(3/4)   | Option Num(0) | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 

A.3. Restart Abort Notification/Acknowledgement (RAN/RAA): 

   The Restart Abort Notification (RAN) message is sent by the Helper to 
   the restarting router. The 'option num' field is set to zero.  



 
 
<Kumar-Kulkarni>       Expires January 18, 2008               [Page 12] 

Internet-Draft          RIP Restart Signaling                 July 2007 
    

   The Restart Abort Acknowledgement (RAA) message is sent by the 
   restarting router to the Helper that had sent it the Restart Abort 
   Notification message. The 'option num' field is set to zero. 

    0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |   Command(7)  |   Version(2)  |   Type(5/6)   | Option Num(0) | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 

A.4. Restart Complete Notification/Acknowledgement (RCN/RCA): 

   The Restart Complete Notification (RCN) message is sent by the 
   restarting router to all the RIP routers on a particular link. The 
   neighbor list option MUST be included once in the RCN message. The 
   neighbor list option SHOULD contain the 4-byte IP address of the RIP 
   routers on the link which have already sent the Restart Complete 
   Acknowledgement. If no such neighbors are present on the link then 
   the option length field SHOULD be set to zero. 

    0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |   Command(7)  |   Version(2)  |    Type(7)    | Option Num(1) | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |       Option Type(1)          |        Option Length(8)       | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |                         NBR IP Address                        | 
   +-------------------------------+-------------------------------+ 
   |                         NBR IP Address                        | 
   +-------------------------------+-------------------------------+ 

   The Restart Complete Acknowledgment (RCA) message is sent by the 
   Helper to the restarting router. The neighbor list option is NOT 
   included in the RCA message. The 'option num' field is set to zero. 

    0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |   Command(7)  |   Version(2)  |    Type 8   |  Option Num(0)  | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 

    

    

12. References 

   [RIP]  C. Hedrick, "RIP Routing Information Protocol", RFC 1058, June 
             1988. 

 
 
<Kumar-Kulkarni>       Expires January 18, 2008               [Page 13] 

Internet-Draft          RIP Restart Signaling                 July 2007 
    

    

   [RIP2]  G. Malkin, "RIP Version 2", RFC 2453, January 1998. 

   [OSPFGR]  J. Moy, P. Pillay-Esnault, A. Lindem, "Graceful OSPF 
             Restart", RFC 3623, November 2003.  

   [RFC-2082]  F. Baker, R. Atkinson, "RIP-2 MD5 Authentication", RFC 
               2082, January 1997. 

   [RFC-4822]  R. Atkinson, M. Fanto, "RIPv2 Cryptographic 
               Authentication", RFC 4822, February 2007.  

   [CRYPT]  V. Manral, R.White, M.Bhatia, G., "Issues with existing 
             Cryptographic Protection Methods for Routing Protocols",         
             draft-manral-rpsec-existing-crypto-04.txt, May 2007. 

   [RIP-ECMP]  J. Kulkarni, N. Anand, "Equal cost routes support for 
             RIP/RIPNG", draft-janardhan-naveen-rtgwg-equalcostroutes-
             rip-00, June 2007.  

    

Author's Addresses 

   Saravana Kumar 
   Huawei Technologies 
   Level-3, Leela Galleria. Airport Road 
   Bangalore, 
   India - 560008 
   Email: saravanak@huawei.com 

    

   Janardhan Kulkarni 
   Citrix 
   Email: Janardhan.Kulkarni@citrix.com 

 

Intellectual Property Statement 

   The IETF takes no position regarding the validity or scope of any 
   Intellectual Property Rights or other rights that might be claimed to 
   pertain to the implementation or use of the technology described in 
   this document or the extent to which any license under such rights 
   might or might not be available; nor does it represent that it has 
   made any independent effort to identify any such rights.  Information 
 
 
<Kumar-Kulkarni>       Expires January 18, 2008               [Page 14] 

Internet-Draft          RIP Restart Signaling                 July 2007 
    

   on the procedures with respect to rights in RFC documents can be 
   found in BCP 78 and BCP 79. 

   Copies of IPR disclosures made to the IETF Secretariat and any 
   assurances of licenses to be made available, or the result of an 
   attempt made to obtain a general license or permission for the use of 
   such proprietary rights by implementers or users of this 
   specification can be obtained from the IETF on-line IPR repository at 
   http://www.ietf.org/ipr. 

   The IETF invites any interested party to bring to its attention any 
   copyrights, patents or patent applications, or other proprietary 
   rights that may cover technology that may be required to implement 
   this standard.  Please address the information to the IETF at 
   ietf-ipr@ietf.org. 

Disclaimer of Validity 

   This document and the information contained herein are provided on an 
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 

Copyright Statement 

   Copyright (C) The IETF Trust (2007). 

   This document is subject to the rights, licenses and restrictions 
   contained in BCP 78, and except as set forth therein, the authors 
   retain all their rights. 

Acknowledgment 

   Funding for the RFC Editor function is currently provided by the 
   Internet Society. 

    








 
 
<Kumar-Kulkarni>       Expires January 18, 2008               [Page 15] 


--Boundary_(ID_XA3hSnf/wOY14mcuWGGl/g)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg

--Boundary_(ID_XA3hSnf/wOY14mcuWGGl/g)--





From rtgwg-bounces@ietf.org Fri Jul 20 15:59:33 2007
Return-path: <rtgwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IByd8-0002Xb-0K; Fri, 20 Jul 2007 15:59:14 -0400
Received: from rtgwg by megatron.ietf.org with local (Exim 4.43)
	id 1I7lU4-0006do-Pc
	for rtgwg-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 01:08:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7lU4-0006dg-CN
	for rtgwg@ietf.org; Mon, 09 Jul 2007 01:08:28 -0400
Received: from wa-out-1112.google.com ([209.85.146.180])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7lU4-0004Oj-3S
	for rtgwg@ietf.org; Mon, 09 Jul 2007 01:08:28 -0400
Received: by wa-out-1112.google.com with SMTP id k17so1368711waf
	for <rtgwg@ietf.org>; Sun, 08 Jul 2007 22:08:19 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=CPoA1yRsp3v87cNCRpRudzLJQYFKaYg+Gqtja4qVAVGoIRM7ob9WJlq5DPzjqQHRaWQLQaDVMiWDuD5uCj2Ixcv5JomZfrFlO1sdAcUKJvaEuk2FBgSnkciiPj/dpYINB2lSa2jsGP5joTRdq9Y8r1fx54uS2zYdX1Hb0ZSkMpU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=t3cvww8j6Y3S9YPuYHbKLds4nWl9VImz7FzZ/UfxKU4lNGYltTp3HSM7sP57KKlXTGrVcBY6h+suZ7Ksnih+VkzTA9kHB7jRJhTi9Lgjooa5hY3tpLrj2TWkMLmLY3EUcLH+v5H7lOaA7AQVeM6wEikEnydGU35YYX4l1ItK7uA=
Received: by 10.114.107.19 with SMTP id f19mr2758991wac.1183957699461;
	Sun, 08 Jul 2007 22:08:19 -0700 (PDT)
Received: by 10.114.108.5 with HTTP; Sun, 8 Jul 2007 22:08:19 -0700 (PDT)
Message-ID: <100ba11b0707082208t3de943eer68a15ef8d306c7bc@mail.gmail.com>
Date: Mon, 9 Jul 2007 10:38:19 +0530
From: "janardhan kulkarni" <janardhan.kulkarni@gmail.com>
To: rtgwg@ietf.org, rcallon@juniper.net, dward@cisco.com, zinin@psg.com, 
	jgs@bgp.nu
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
X-Mailman-Approved-At: Fri, 20 Jul 2007 15:59:12 -0400
Cc: naveenanand@huawei.com, naveen.anand@gmail.com
Subject: Please review our new draft. Thanks.
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2133066648=="
Errors-To: rtgwg-bounces@ietf.org

--===============2133066648==
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: base64
Content-Disposition: inline

SGksCgpLaW5kbHkgcmV2aWV3IG91ciBuZXcgZHJhZnQgb24gUklQL1JJUE5HIHRvIHN1cHBvcnQg
ZXF1YWwgY29zdCByb3V0ZXMKYW5kIHNwbGl0IGhvcm96b24gYW5kIHBvaXNvbiBjaGVja3MgZm9y
IHN1Y2ggcm91dGVzLiBPdXIgYWltIGlzCmRvY3VtZW50IHJ1bGVzIGRvaW5nIHNwbGl0IGFuZCBw
b2lzb24gY2hlY2tzIGZvciB0aGVzZSByb3V0ZXMgYW5kIHdlCmFpbSB0byBtYWtlIGl0IGFuIGlu
Zm9ybWF0aW9uYWwgZHJhZnQuCgpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvd2cvcnRnd2cvZHJhZnQt
amFuYXJkaGFuLW5hdmVlbi1ydGd3Zy1lcXVhbGNvc3Ryb3V0ZXMtcmlwLTAwLnR4dAoKQnJpZWYg
aW50cm9kdWN0aW9uIGZyb20gb3VyIHdvcms6LQpSSVAgdjIgYXMgZGVzY3JpYmVkIGluIFJGQyAy
NDUzIGFuZCBSSVBORyBhcyBkZXNjcmliZWQgaW4gUkZDIDIwODAsCmRvIG5vdCBzdXBwb3J0IGxl
YXJuaW5nIG11bHRpcGxlIGVxdWFsIGNvc3Qgcm91dGVzIHRvIGEgZGVzdGluYXRpb24KdGhyb3Vn
aCBkaWZmZXJlbnQgbmVpZ2hib3JzLkJ1dCBpbiB0b2Rhee+/vXMgaW50ZXJuZXQgaXQgaXMgdmVy
eQpjb21tb24gdG8gaGF2ZSB0b3BvbG9naWVzIHdoZXJlIHRoZXJlIGFyZSBtb3JlIHRoYW4gb25l
IHJvdXRlIHRvIGEKZGVzdGluYXRpb24uIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIHRoZSBtb2Rp
ZmljYXRpb25zIHRvIHRoZQpSSVAvUklQTkcgcHJvdG9jb2xzIHRvIGhhbmRsZSB0aGlzIHNjZW5h
cmlvIGFuZCBkZXNjcmliZXMgaG93IHRvCmFwcGx5IHRoZSBzcGxpdCBob3Jpem9uIGFuZCBwb2lz
b24gcmV2ZXJzZSBmb3IgFrom rtgwg-bounces@ietf.org Fri Jul 20 15:59:33 2007
Return-path: <rtgwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IByd8-0002Xb-0K; Fri, 20 Jul 2007 15:59:14 -0400
Received: from rtgwg by megatron.ietf.org with local (Exim 4.43)
	id 1I7lU4-0006do-Pc
	for rtgwg-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 01:08:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7lU4-0006dg-CN
	for rtgwg@ietf.org; Mon, 09 Jul 2007 01:08:28 -0400
Received: from wa-out-1112.google.com ([209.85.146.180])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7lU4-0004Oj-3S
	for rtgwg@ietf.org; Mon, 09 Jul 2007 01:08:28 -0400
Received: by wa-out-1112.google.com with SMTP id k17so1368711waf
	for <rtgwg@ietf.org>; Sun, 08 Jul 2007 22:08:19 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=CPoA1yRsp3v87cNCRpRudzLJQYFKaYg+Gqtja4qVAVGoIRM7ob9WJlq5DPzjqQHRaWQLQaDVMiWDuD5uCj2Ixcv5JomZfrFlO1sdAcUKJvaEuk2FBgSnkciiPj/dpYINB2lSa2jsGP5joTRdq9Y8r1fx54uS2zYdX1Hb0ZSkMpU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=t3cvww8j6Y3S9YPuYHbKLds4nWl9VImz7FzZ/UfxKU4lNGYltTp3HSM7sP57KKlXTGrVcBY6h+suZ7Ksnih+VkzTA9kHB7jRJhTi9Lgjooa5hY3tpLrj2TWkMLmLY3EUcLH+v5H7lOaA7AQVeM6wEikEnydGU35YYX4l1ItK7uA=
Received: by 10.114.107.19 with SMTP id f19mr2758991wac.1183957699461;
	Sun, 08 Jul 2007 22:08:19 -0700 (PDT)
Received: by 10.114.108.5 with HTTP; Sun, 8 Jul 2007 22:08:19 -0700 (PDT)
Message-ID: <100ba11b0707082208t3de943eer68a15ef8d306c7bc@mail.gmail.com>
Date: Mon, 9 Jul 2007 10:38:19 +0530
From: "janardhan kulkarni" <janardhan.kulkarni@gmail.com>
To: rtgwg@ietf.org, rcallon@juniper.net, dward@cisco.com, zinin@psg.com, 
	jgs@bgp.nu
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
X-Mailman-Approved-At: Fri, 20 Jul 2007 15:59:12 -0400
Cc: naveenanand@huawei.com, naveen.anand@gmail.com
Subject: Please review our new draft. Thanks.
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2133066648=="
Errors-To: rtgwg-bounces@ietf.org

--===============2133066648==
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: base64
Content-Disposition: inline

SGksCgpLaW5kbHkgcmV2aWV3IG91ciBuZXcgZHJhZnQgb24gUklQL1JJUE5HIHRvIHN1cHBvcnQg
ZXF1YWwgY29zdCByb3V0ZXMKYW5kIHNwbGl0IGhvcm96b24gYW5kIHBvaXNvbiBjaGVja3MgZm9y
IHN1Y2ggcm91dGVzLiBPdXIgYWltIGlzCmRvY3VtZW50IHJ1bGVzIGRvaW5nIHNwbGl0IGFuZCBw
b2lzb24gY2hlY2tzIGZvciB0aGVzZSByb3V0ZXMgYW5kIHdlCmFpbSB0byBtYWtlIGl0IGFuIGlu
Zm9ybWF0aW9uYWwgZHJhZnQuCgpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvd2cvcnRnd2cvZHJhZnQt
amFuYXJkaGFuLW5hdmVlbi1ydGd3Zy1lcXVhbGNvc3Ryb3V0ZXMtcmlwLTAwLnR4dAoKQnJpZWYg
aW50cm9kdWN0aW9uIGZyb20gb3VyIHdvcms6LQpSSVAgdjIgYXMgZGVzY3JpYmVkIGluIFJGQyAy
NDUzIGFuZCBSSVBORyBhcyBkZXNjcmliZWQgaW4gUkZDIDIwODAsCmRvIG5vdCBzdXBwb3J0IGxl
YXJuaW5nIG11bHRpcGxlIGVxdWFsIGNvc3Qgcm91dGVzIHRvIGEgZGVzdGluYXRpb24KdGhyb3Vn
aCBkaWZmZXJlbnQgbmVpZ2hib3JzLkJ1dCBpbiB0b2Rhee+/vXMgaW50ZXJuZXQgaXQgaXMgdmVy
eQpjb21tb24gdG8gaGF2ZSB0b3BvbG9naWVzIHdoZXJlIHRoZXJlIGFyZSBtb3JlIHRoYW4gb25l
IHJvdXRlIHRvIGEKZGVzdGluYXRpb24uIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIHRoZSBtb2Rp
ZmljYXRpb25zIHRvIHRoZQpSSVAvUklQTkcgcHJvdG9jb2xzIHRvIGhhbmRsZSB0aGlzIHNjZW5h
cmlvIGFuZCBkZXNjcmliZXMgaG93IHRvCmFwcGx5IHRoZSBzcGxpdCBob3Jpem9uIGFuZCBwb2lz
b24gcmV2ZXJzZSBmb3Igc3VjaCByb3V0ZXMuIEl0IGlzCnNpbXBsZSwgbGlnaHQgYW5kIGlzIGNv
bXBhdGlibGUgd2l0aCB0aGUgaW1wbGVtZW50YXRpb25zIHdoaWNoIGRvIG5vdApzdXBwb3J0IHRo
aXMgZmVhdHVyZS4KVGhlIG1haW4gbW90aXZhdGlvbiBiZWhpbmQgdGhpcyBkcmFmdCBpcyB0byBk
b2N1bWVudCBydWxlcyBmb3IgUklQLwpSSVBORyB0byBoYW5kbGUgZXF1YWwgY29zdCByb3V0ZXMg
dG8gYSBkZXN0aW5hdGlvbiwgc2luY2UgbW9zdCBvZiB0aGUKdmVuZG9ycyBhbHJlYWR5IHN1cHBv
cnQgdGhpcyBmZWF0dXJlLiBCdXQgdGhlcmUgaXMgbm8gY29uY29yZCBvbiBob3cKdG8gYXBwbHkg
dGhlIHNwbGl0IGhvcml6b24vcG9pc29uIGNoZWNrcyBmb3Igc3VjaCByb3V0ZXMuIEluIGZhY3Qs
Cm1vc3Qgb2YgdGhlIHBvcHVsYXIgdmVuZG9ycyBhcHBseSB0aGUgc3BsaXQvcG9pc29uIGNoZWNr
cyBpbiBhIHdyb25nCndheS4gVGhpcyBkcmFmdCBleHBsaWNhdGVzIHRoZSBwcm9wZXIgaW1wbGVt
ZW50YXRpb24gb2YgdGhlIGFib3ZlCmZlYXR1cmVzLiBBbHNvLCBzaW5jZSBSSVBORyBpcyBnZXR0
aW5nIGRlcGxveWVkLHRoZXNlIGZlYXR1cmVzIGNhbiBiZQppbmNsdWRlZCB3aGlsZSBkZXZlbG9w
aW5nIFJJUE5HLgoKLS0gCkJ5ZSwKSmFuYXJkaGFuLgoiSSBoYXZlIG5ldmVyIGJlZW4gaHVydCBi
eSB3aGF0IEkgaGF2ZSBub3Qgc2FpZC4iCiAgLUNhbHZpbiBDb29saWRnZQo=



--===============2133066648==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg

--===============2133066648==--

From rtgwg-bounces@ietf.org Fri Jul 20 15:59:33 2007
Return-path: <rtgwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IByd8-0002ZK-9d; Fri, 20 Jul 2007 15:59:14 -0400
Received: from rtgwg by megatron.ietf.org with local (Exim 4.43)
	id 1IByaB-0000jA-Rg
	for rtgwg-confirm+ok@megatron.ietf.org; Fri, 20 Jul 2007 15:56:11 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IByaB-0000j2-Hb
	for rtgwg@ietf.org; Fri, 20 Jul 2007 15:56:11 -0400
Received: from smtpa.juniper.net ([207.17.137.120])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IByaB-0000V6-8B
	for rtgwg@ietf.org; Fri, 20 Jul 2007 15:56:11 -0400
Received: from unknown (HELO merlot.juniper.net) ([172.17.27.10])
	by smtpa.juniper.net with ESMTP/TLS/DES-CBC3-SHA;
	20 Jul 2007 12:56:09 -0700
X-IronPort-AV: i="4.16,563,1175497200"; 
	d="scan'208"; a="40783675:sNHT30349056"
Received: from [172.16.13.202] ([172.16.13.202])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id l6KJu7O38905
	for <rtgwg@ietf.org>; Fri, 20 Jul 2007 12:56:07 -0700 (PDT)
	(envelope-from jgs@juniper.net)
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <5660C206-20B1-4366-B964-29E550A6A6C7@juniper.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: rtgwg@ietf.org
From: "John G. Scudder" <jgs@juniper.net>
Date: Fri, 20 Jul 2007 15:56:05 -0400
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
X-Mailman-Approved-At: Fri, 20 Jul 2007 15:59:12 -0400
Subject: rtgwg meeting at IETF-69
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Errors-To: rtgwg-bounces@ietf.org

Folks,

We will meet on Tuesday from 1740 until 1840.  We have a short slot  
and a full agenda so please make an effort to be on time if you plan  
to attend.  Thanks!

Our agenda is:

- Administrivia
    John Scudder
    5 min
- Applicability of not-via to distance vector and routing vector  
protocols
    Stewart Bryant
    10 min
- draft-ietf-rtgwg-ordered-fib update
    Pierre Francois
    10 min
- Graceful Restart extensions for RIP
    Saravana K
    15 min
- draft-hokelek-rLFAP-00
    Ibrahim Hokelek
    20 min

--John


_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfoc3VjaCByb3V0ZXMuIEl0IGlzCnNpbXBsZSwgbGlnaHQgYW5kIGlzIGNv
bXBhdGlibGUgd2l0aCB0aGUgaW1wbGVtZW50YXRpb25zIHdoaWNoIGRvIG5vdApzdXBwb3J0IHRo
aXMgZmVhdHVyZS4KVGhlIG1haW4gbW90aXZhdGlvbiBiZWhpbmQgdGhpcyBkcmFmdCBpcyB0byBk
b2N1bWVudCBydWxlcyBmb3IgUklQLwpSSVBORyB0byBoYW5kbGUgZXF1YWwgY29zdCByb3V0ZXMg
dG8gYSBkZXN0aW5hdGlvbiwgc2luY2UgbW9zdCBvZiB0aGUKdmVuZG9ycyBhbHJlYWR5IHN1cHBv
cnQgdGhpcyBmZWF0dXJlLiBCdXQgdGhlcmUgaXMgbm8gY29uY29yZCBvbiBob3cKdG8gYXBwbHkg
dGhlIHNwbGl0IGhvcml6b24vcG9pc29uIGNoZWNrcyBmb3Igc3VjaCByb3V0ZXMuIEluIGZhY3Qs
Cm1vc3Qgb2YgdGhlIHBvcHVsYXIgdmVuZG9ycyBhcHBseSB0aGUgc3BsaXQvcG9pc29uIGNoZWNr
cyBpbiBhIHdyb25nCndheS4gVGhpcyBkcmFmdCBleHBsaWNhdGVzIHRoZSBwcm9wZXIgaW1wbGVt
ZW50YXRpb24gb2YgdGhlIGFib3ZlCmZlYXR1cmVzLiBBbHNvLCBzaW5jZSBSSVBORyBpcyBnZXR0
aW5nIGRlcGxveWVkLHRoZXNlIGZlYXR1cmVzIGNhbiBiZQppbmNsdWRlZCB3aGlsZSBkZXZlbG9w
aW5nIFJJUE5HLgoKLS0gCkJ5ZSwKSmFuYXJkaGFuLgoiSSBoYXZlIG5ldmVyIGJlZW4gaHVydCBi
eSB3aGF0IEkgaGF2ZSBub3Qgc2FpZC4iCiAgLUNhbHZpbiBDb29saWRnZQo=



--===============2133066648==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg

--===============2133066648==--

From rtgwg-bounces@ietf.org Fri Jul 20 15:59:33 2007
Return-path: <rtgwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IByd8-0002ZK-9d; Fri, 20 Jul 2007 15:59:14 -0400
Received: from rtgwg by megatron.ietf.org with local (Exim 4.43)
	id 1IByaB-0000jA-Rg
	for rtgwg-confirm+ok@megatron.ietf.org; Fri, 20 Jul 2007 15:56:11 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IByaB-0000j2-Hb
	for rtgwg@ietf.org; Fri, 20 Jul 2007 15:56:11 -0400
Received: from smtpa.juniper.net ([207.17.137.120])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IByaB-0000V6-8B
	for rtgwg@ietf.org; Fri, 20 Jul 2007 15:56:11 -0400
Received: from unknown (HELO merlot.juniper.net) ([172.17.27.10])
	by smtpa.juniper.net with ESMTP/TLS/DES-CBC3-SHA;
	20 Jul 2007 12:56:09 -0700
X-IronPort-AV: i="4.16,563,1175497200"; 
	d="scan'208"; a="40783675:sNHT30349056"
Received: from [172.16.13.202] ([172.16.13.202])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id l6KJu7O38905
	for <rtgwg@ietf.org>; Fri, 20 Jul 2007 12:56:07 -0700 (PDT)
	(envelope-from jgs@juniper.net)
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <5660C206-20B1-4366-B964-29E550A6A6C7@juniper.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: rtgwg@ietf.org
From: "John G. Scudder" <jgs@juniper.net>
Date: Fri, 20 Jul 2007 15:56:05 -0400
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
X-Mailman-Approved-At: Fri, 20 Jul 2007 15:59:12 -0400
Subject: rtgwg meeting at IETF-69
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Errors-To: rtgwg-bounces@ietf.org

Folks,

We will meet on Tuesday from 1740 until 1840.  We have a short slot  
and a full agenda so please make an effort to be on time if you plan  
to attend.  Thanks!

Our agenda is:

- Administrivia
    John Scudder
    5 min
- Applicability of not-via to distance vector and routing vector  
protocols
    Stewart Bryant
    10 min
- draft-ietf-rtgwg-ordered-fib update
    Pierre Francois
    10 min
- Graceful Restart extensions for RIP
    Saravana K
    15 min
- draft-hokelek-rLFAP-00
    Ibrahim Hokelek
    20 min

--John


_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg





/rtgwg





From rtgwg-bounces@ietf.org Thu Jul 26 10:09:50 2007
Return-path: <rtgwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE42G-0007Ga-0Y; Thu, 26 Jul 2007 10:09:48 -0400
Received: from rtgwg by megatron.ietf.org with local (Exim 4.43)
	id 1IE42F-0007GT-6e
	for rtgwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 10:09:47 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE42E-0007GL-RN
	for rtgwg@ietf.org; Thu, 26 Jul 2007 10:09:46 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE42E-0004v0-4O
	for rtgwg@ietf.org; Thu, 26 Jul 2007 10:09:46 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 16:09:45 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 26 Jul 2007 16:09:09 +0200
Message-ID: <2AF8FF7D89242541B12E7A47F6ECB4BE05C23E12@ftrdmel3.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Multi-topology interest
thread-index: AcfPjokUPNM6h6f5RL+J0EmpxwNPXw==
From: "CAUCHIE Gregory RD-CORE-ISS" <gregory.cauchie@orange-ftgroup.com>
To: <rtgwg@ietf.org>
X-OriginalArrivalTime: 26 Jul 2007 14:09:45.0072 (UTC)
	FILETIME=[9E411700:01C7CF8E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Subject: Multi-topology interest
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0550882854=="
Errors-To: rtgwg-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0550882854==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CF8E.9D7E019A"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7CF8E.9D7E019A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,
=20
as opinions were requested tuesday during the rtgwg meeting regarding
interests on IGP muti-topology applicability, here is mine.
=20
Today, most of multicast services are deployed using the PIM protocol.
With PIM, multicast trees are set up by relying on IGP informations,
thus decisions to send join and prune messages are made upon an IGP
adjacencies status basis. But for multiple reasons, the IGP adjacencies
states may not exactly overlap the PIM adjacencies states. In that case,
the shortest path from one router to a multicast source or a RP can
include a link where at least one PIM interface is down. The consequence
is that PIM join messages are sent on a dead end and then multicast
service is broken until some other actions (that may request human
direct actions) are made.
=20
To prevent this issue to occur and thus unavailability of multicast
services (like IPTV), multi-topology is a real interesting solution.
Multi-topology could be use to convey in LSPs or LSAs information of
links where a PIM adjacency is UP. Thus LSDB would then have a "PIM
topology" in parallel of a classical network IGP topology so that the
former could be use as a basis for SPF computation from the router to
the multicast source instead of the latter. The PIM join and prune
messages would then be sent on the best "multicast available" way if it
exists.
=20
This is to me the first interest of multi-topology work.
=20
Greg

------_=_NextPart_001_01C7CF8E.9D7E019A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3132" name=3DGENERATOR></HEAD>
<BODY>
<DIV>
<DIV><SPAN class=3D953263517-25072007><FONT face=3DArial size=3D2>Hi=20
all,</FONT></SPAN></DIV>
<DIV><SPAN class=3D953263517-25072007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D953263517-25072007><FONT face=3DArial size=3D2>as =
opinions were=20
requested&nbsp;<SPAN class=3D562300923-25072007>tuesday </SPAN>during =
the rtgwg=20
meeting regarding interests on IGP muti-topology applicability, here is=20
mine.</FONT></SPAN></DIV>
<DIV><SPAN class=3D953263517-25072007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D953263517-25072007><FONT face=3DArial size=3D2>Today, =
most of=20
multicast services are deployed using the PIM protocol. With PIM, =
multicast=20
trees are set up by relying on IGP informations, thus decisions to send =
join and=20
prune messages are made upon an IGP adjacencies status basis. But for =
multiple=20
reasons, the IGP adjacencies states may not exactly overlap the PIM =
adjacencies=20
states. In that case, the shortest path&nbsp;from one router&nbsp;to a =
multicast=20
source or a RP can include a link where at least one&nbsp;PIM interface =
is down.=20
The&nbsp;consequence is that&nbsp;</FONT></SPAN><SPAN=20
class=3D953263517-25072007><FONT face=3DArial size=3D2>PIM join messages =
are sent on a=20
dead end and then multicast service is broken until some other actions =
(that may=20
request human direct actions) are made.</FONT></SPAN></DIV>
<DIV><SPAN class=3D953263517-25072007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D953263517-25072007><FONT face=3DArial size=3D2>To =
prevent this=20
issue to occur and thus unavailability of multicast services (like =
IPTV),=20
multi-topology is a real interesting solution. Multi-topology could be =
use to=20
convey in LSPs or LSAs information of links where a PIM adjacency is UP. =
Thus=20
LSDB would then have a "PIM topology" in parallel of a classical network =
IGP=20
topology&nbsp;so that&nbsp;the former could be use as a basis for SPF=20
computation from the router to the multicast source instead of the =
latter. The=20
PIM join and prune messages would then be sent on the best "multicast =
available"=20
way if it exists.</FONT></SPAN></DIV>
<DIV><SPAN class=3D953263517-25072007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D953263517-25072007><FONT face=3DArial size=3D2>This =
is to me the=20
first interest of multi-topology work.</FONT></SPAN></DIV>
<DIV><SPAN class=3D953263517-25072007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D953263517-25072007><FONT face=3DArial=20
size=3D2>Greg</FONT></SPAN></DIV></DIV></BODY></HTML>

------_=_NextPart_001_01C7CF8E.9D7E019A--



--===============0550882854==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg

--===============0550882854==--





From rtgwg-bounces@ietf.org Fri Jul 27 12:07:50 2007
Return-path: <rtgwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IESLy-0003zh-Ji; Fri, 27 Jul 2007 12:07:46 -0400
Received: from rtgwg by megatron.ietf.org with local (Exim 4.43)
	id 1IESLx-0003zc-3M
	for rtgwg-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 12:07:45 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IESLw-0003zU-OF
	for rtgwg@ietf.org; Fri, 27 Jul 2007 12:07:44 -0400
Received: from smtpb.juniper.net ([207.17.137.119])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IESLv-0008C3-Vd
	for rtgwg@ietf.org; Fri, 27 Jul 2007 12:07:44 -0400
Received: from unknown (HELO merlot.juniper.net) ([172.17.27.10])
	by smtpb.juniper.net with ESMTP/TLS/DES-CBC3-SHA;
	27 Jul 2007 09:07:43 -0700
Received: from [172.23.9.232] ([172.23.9.232])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id l6RG7gO22328
	for <rtgwg@ietf.org>; Fri, 27 Jul 2007 09:07:42 -0700 (PDT)
	(envelope-from jgs@juniper.net)
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <41029217-5006-4AFD-A885-72D13BCF71D0@juniper.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: rtgwg@ietf.org
From: "John G. Scudder" <jgs@juniper.net>
Date: Fri, 27 Jul 2007 11:07:23 -0500
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93e7fb8fef2e780414389440f367c879
Subject: Draft rtgwg minutes for July 24, 2007 meeting
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Errors-To: rtgwg-bounces@ietf.org

Folks,

Here are our draft minutes.  Please send any corrections before  
August 10.  Thanks to Saravana for taking notes.

--John

RTGWG minutes
July 24, 2007
Scribe: Saravana K (with additional notes from John Scudder)

Agenda:
=======

- Administrivia
    John Scudder
    5 min
- Applicability of not-via to distance vector and path vector protocols
    Stewart Bryant
    10 min
- draft-ietf-rtgwg-ordered-fib update
    Pierre Francois
    10 min
- Graceful Restart extensions for RIP
    Saravana K
    15 min
- draft-hokelek-rLFAP-00
    Ibrahim Hokelek
    20 min

------------------------------------------------------------------------ 
-

Working Group Update :
=================

- John Scudder presented a update on the progress of the working  
group with regard to the current status of the documents and milestones.

- John wanted to know if any people were interested in coming up with  
drafts on the following areas : IPFRR for Multicast and Multi- 
Topology applicability.

- wrt Multi-Topology applicability the requirement is to come up with  
some use cases to help people understand how MT can be used in other  
circumstances other than just using it for supporting different  
address families.

- Any interested persons to notify John.

Applicability of not-via to distance vector and path vector protocols  
- Stewart Bryant
==================================================

John : Where do you want go with this presentation
Stewart : The current work for not-via is concentrated on mostly for  
link state protocols, wanted to highlight its applicability for link  
state and distance vector protocols as well.


Graceful Restart extensions for RIP - Saravana K
=====================================

Acee : Why cannot RIP do a mechanism to preserve the stale routes in  
forwarding table, wait for a static time for the route updates to be  
received and then update the forwarding table and clean up the stale  
routes.
Saravana : The main issue is topology change handling, if any routes  
are deleted during the restart the restarting router will not  
propagate the received withdraws. So the topology wont converge for  
180s. Also if there are multiple ECMPs, the set of paths selected  
before and after a restart might be different.

Andrew Lange : What is the requirement for this issue, why the sudden  
need for GR in RIP
Saravana : We do have some active deployments of RIP, one of the  
latest requirements was for the seamless software upgrade capability  
for RIP and when analyzing those requirements we came up with these  
possible issues when RIP undergoes a restart.

Bill Fenner: Your customer is OK with RIP's other deficiencies such  
as counting to infinity, but not this?  Why not migrate them to some  
more capable IGP?
Saravana: It's what the customer wants.

Ross Callon: Do customers thing this will solve all RIP's problems?
Saravana: It's mostly for seamless software upgrade.

Ina Minei: One of the assumptions for GR is topology is stable, so  
what is the issue in RIP with regard to this.
Saravana : In other protocols the topology will converge immediately  
after the protocols complete their restart processing, but in RIP it  
wont converge for a very long time (180s)

John Scudder: Where do you go from here, request show of hands?
Saravana: We're planning to implement it, would like to offer it as  
WG doc if others are interested in standardizing.
Chris Hopps : Need some time to go back to the RIP protocol.
John Scudder: OK, let's move this to the mailing list so folks can  
have a chance to review RIP.

draft-hokelek-rLFAP-00 -  Ibrahim Hokelek
===============================

Stewart Bryant: If you have time to do signaling of failure, why not  
just do an IGP convergence?
Ibrahim: We precompute within a region, we just need failure info

Chris Hopps : IS-IS LSP fragment is advertised when a link fails --  
seems about the same as your failure info.  What is the difference?
Chris Hopps: With IS-IS nearby neighbors will get the flooded LSP  
fragment first so convergence ought to be similar.
Ibrahim : If the link is flapping all the time (esp in case of radio  
links), if you are going to be sending the info again and again, it  
will affect the network.  Our proposal scopes flooding.

Stewart: Can't you just hold down flapping links though?
Ibrahim: Scoped flooding means we don't have to.

Stewart : The idea of FRR is to pre-compute the repair paths, even  
the not-via addresses are pre-computed.
Ibrahim : One issue is that the backup information is computed for  
all the network and the overhead involved is large. In this proposal  
the backup computation is only for the immediate nexthops
Mike Shand: You seem to be overestimating the overhead of not-via?

Ibrahim: Various other proposals don't cover multiple failures or are  
unscalable.

Chris : Give some concrete examples of difference between normal  
convergence used by the protocols and using this mechanism. Because  
it seems like both the mechanisms are similar.  Please include  
numbers/time budgets.

John : What to do with this draft
Ibrahim : Get feedback and see if the WG is interested in the draft
John : move this to the mailing list



_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Fri Jul 27 12:28:49 2007
Return-path: <rtgwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IESg7-00053q-14; Fri, 27 Jul 2007 12:28:35 -0400
Received: from rtgwg by megatron.ietf.org with local (Exim 4.43)
	id 1IESg4-00053k-GA
	for rtgwg-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 12:28:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IESg4-00053c-6Z
	for rtgwg@ietf.org; Fri, 27 Jul 2007 12:28:32 -0400
Received: from nz-out-0506.google.com ([64.233.162.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IESg3-0008Nt-25
	for rtgwg@ietf.org; Fri, 27 Jul 2007 12:28:32 -0400
Received: by nz-out-0506.google.com with SMTP id n1so753932nzf
	for <rtgwg@ietf.org>; Fri, 27 Jul 2007 09:28:30 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
	b=Qi0axjO1Jq9Mb3z/nPRL1uLb2roiaQ3x0aw509KpA5No00XW5KqNefXLARt2P6Cxk9gbPu9OeyZD1yxDRfV16gFmf3EZQItByK3zuRHjPUpu65Blym1PPZ+g6styTbkgHfYzKS/1YcjFZCOB8SlBQR6Mv8CF9qYpRitF4CGhd2o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=PYB/VIddC6mEbQ0XDGx4GXmpX02KG4Eu1Xo5o9f63T+8PNmvpcH86FyukZbaatz/O0uSyNBciRQr5Vpkn013BRePqL1J/6Uz6UJ7OauTj422r1xX+vE/KckTgU19J3Czv9CRrGEEuFsjK10YMRQv/vTvHwQW97XfonOFO2YOgRE=
Received: by 10.142.84.3 with SMTP id h3mr177108wfb.1185553709746;
	Fri, 27 Jul 2007 09:28:29 -0700 (PDT)
Received: by 10.142.109.21 with HTTP; Fri, 27 Jul 2007 09:28:29 -0700 (PDT)
Message-ID: <6280db520707270928v695f760ev266df979748c7eb3@mail.gmail.com>
Date: Fri, 27 Jul 2007 12:28:29 -0400
From: "Alia Atlas" <akatlas@gmail.com>
To: rtgwg@ietf.org, "ZININ Alex" <Alex.Zinin@alcatel-lucent.com>
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Cc: 
Subject: updates to draft-ietf-rtgwg-ipfrr-spec-base
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1114004036=="
Errors-To: rtgwg-bounces@ietf.org

--===============1114004036==
Content-Type: multipart/alternative; 
	boundary="----=_Part_11462_11712934.1185553709730"

------=_Part_11462_11712934.1185553709730
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

After discussion with Stefano Previdi, Mike Shand, and Stewart Bryant, I
think that
we've agreed on the last couple outstanding details for the LFA draft.

Please send any comments on the draft or the below additions very soon,
since I'd
like to get the updated draft out very shortly (next week) so it'll be ready
for a last call.

So, to the changes between 07 & the upcoming 08

1) Changed back the MAY to a SHOULD NOT for setting the "local protection
available" flag
as a result of having LFAs.

    This had been changed to a MAY because having a bit indicate when a link
is protected by
    IPFRR is very useful for implementing Ordered FIB.  If the bit is set,
then the OFIB convergence
    can be used and otherwise not.  However, we concluded that the "local
protection available"
    flag that is currently defined should not be used for this purpose.  The
existing flag is used in
    the CSPF computation for RSVP-TE LSPs to determine what links have
bypass tunnels and
    ensure that the entire path does.  It is quite plausible that a network
will have both IPFRR and
    some non-zero number of RSVP-TE LSP that want to be protected with
RSVP-TE FRR.  Therefore,
    we concluded that a different additional "IP/LDP local protection
available" flag will be required.

    After some discussion, it was clear that there are a number of different
ways and reasons to
    decide when to set the new flag.  For instance, it could be set when
there is an LFA to the
    router at the end of the link, or to the link's far-end IP address, if
it is numbered.  Alternately,
    it could be set when a critical set of prefixes have LFAs or all
prefixes out that link/next-hop
    have LFAs.  The trade-offs and desired policy is really based upon OFIB
and not LFAs.  Because
    of this complexity and the desire not to tie the LFA draft to new ISIS &
OSPF drafts defining
    the new flag, we decided not to mention the new bit in the LFA draft.

    Instead, the OFIB draft will discuss the new flag and provide guidelines
on when it should be set.
    IPFRR is back to SHOULD NOT for setting the existing "local protection
available" flag.

2) From discussion, it's clear that there are implementations that use a
simplified approach that
doesn't give as good coverage, but may be easier to implement.  We wanted to
document this
and clarify the benefits and drawbacks of this.  Therefore, a new section (
3.6) is added with the
text below.   (The references to a Figure 4 and Section 6.1 are the same for
the 07 and 08 versions.)

"3.7.  A Simplification: Per-Next-Hop LFAs

   It is possible to simplify the computation and use of LFAs when
   solely link protection is desired by considering and computing only
   one link-protecting LFA for each next-hop connected to the router.
   All prefixes that use that next-hop as a primary will use the LFA
   computed for that next-hop as its LFA.

   Even a prefix with multiple primary next-hops will have each primary
   next-hop protected individually by the primary next-hop's associated
   LFA.  That associated LFA might or might not be another of the
   primary next-hops of the prefix.

   This simplification may reduce coverage in a network.  In addition to
   limiting protection for multi-homed prefixes (see Section 6.1), the
   computation per next-hop may also not find an LFA when one could be
   found for some of the prefixes that use that next-hop.

   For example, consider Figure 4 where S has 3 ECMP next-hops, E1, E2,
   and E3 to reach D. For the prefix D, E3 can give link protection for
   the next-hops E1 and E2; E1 and E2 can give link protection for the
   next-hops E3.  However, if one uses this simplification to compute
   LFAs for E1, E2 and E3 individually, there is no link-protecting LFA
   for E1.  E3 and E2 can protect each other.
"

Again, I would welcome any comments on these changes or anything else
in the draft.  I plan to submit an updated draft next week.

Thanks,
Alia

------=_Part_11462_11712934.1185553709730
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

After discussion with Stefano Previdi, Mike Shand, and Stewart Bryant, I think that<br>we&#39;ve agreed on the last couple outstanding details for the LFA draft.<br><br>Please send any comments on the draft or the below additions very soon, since I&#39;d
<br>like to get the updated draft out very shortly (next week) so it&#39;ll be ready for a last call.<br><br>So, to the changes between 07 &amp; the upcoming 08<br><br>1) Changed back the MAY to a SHOULD NOT for setting the &quot;local protection available&quot; flag
<br>as a result of having LFAs.&nbsp; <br><br>&nbsp;&nbsp;&nbsp; This had been changed to a MAY because having a bit indicate when a link is protected by<br>&nbsp;&nbsp;&nbsp; IPFRR is very useful for implementing Ordered FIB.&nbsp; If the bit is set, then the OFIB convergence
<br>&nbsp;&nbsp;&nbsp; can be used and otherwise not.&nbsp; However, we concluded that the &quot;local protection available&quot;<br>&nbsp;&nbsp;&nbsp; flag that is currently defined should not be used for this purpose.&nbsp; The existing flag is used in<br>&nbsp;&nbsp;&nbsp; the CSPF computation for RSVP-TE LSPs to determine what links have bypass tunnels and
<br>&nbsp;&nbsp;&nbsp; ensure that the entire path does.&nbsp; It is quite plausible that a network will have both IPFRR and<br>&nbsp;&nbsp;&nbsp; some non-zero number of RSVP-TE LSP that want to be protected with RSVP-TE FRR.&nbsp; Therefore,<br>&nbsp;&nbsp;&nbsp; we concluded that a different additional &quot;IP/LDP local protection available&quot; flag will be required.
<br><br>&nbsp;&nbsp;&nbsp; After some discussion, it was clear that there are a number of different ways and reasons to<br>&nbsp;&nbsp;&nbsp; decide when to set the new flag.&nbsp; For instance, it could be set when there is an LFA to the<br>&nbsp;&nbsp;&nbsp; router at the end of the link, or to the link&#39;s far-end IP address, if it is numbered.&nbsp; Alternately,
<br>&nbsp;&nbsp;&nbsp; it could be set when a critical set of prefixes have LFAs or all prefixes out that link/next-hop<br>&nbsp;&nbsp;&nbsp; have LFAs.&nbsp; The trade-offs and desired policy is really based upon OFIB and not LFAs.&nbsp; Because<br>&nbsp;&nbsp;&nbsp; of this complexity and the desire not to tie the LFA draft to new ISIS &amp; OSPF drafts defining
<br>&nbsp;&nbsp;&nbsp; the new flag, we decided not to mention the new bit in the LFA draft.<br><br>&nbsp;&nbsp;&nbsp; Instead, the OFIB draft will discuss the new flag and provide guidelines on when it should be set.<br>&nbsp;&nbsp;&nbsp; IPFRR is back to SHOULD NOT for setting the existing &quot;local protection available&quot; flag.
<br><br>2) From discussion, it&#39;s clear that there are implementations that use a simplified approach that<br>doesn&#39;t give as good coverage, but may be easier to implement.&nbsp; We wanted to document this<br>and clarify the benefits and drawbacks of this.&nbsp; Therefore, a new section (
3.6) is added with the<br>text below.&nbsp;&nbsp; (The references to a Figure 4 and Section 6.1 are the same for the 07 and 08 versions.)<br><br>&quot;3.7.&nbsp; A Simplification: Per-Next-Hop LFAs<br><br>&nbsp;&nbsp; It is possible to simplify the computation and use of LFAs when
<br>&nbsp;&nbsp; solely link protection is desired by considering and computing only<br>&nbsp;&nbsp; one link-protecting LFA for each next-hop connected to the router.<br>&nbsp;&nbsp; All prefixes that use that next-hop as a primary will use the LFA<br>
&nbsp;&nbsp; computed for that next-hop as its LFA.<br><br>&nbsp;&nbsp; Even a prefix with multiple primary next-hops will have each primary<br>&nbsp;&nbsp; next-hop protected individually by the primary next-hop&#39;s associated<br>&nbsp;&nbsp; LFA.&nbsp; That associated LFA might or might not be another of the
<br>&nbsp;&nbsp; primary next-hops of the prefix.<br><br>&nbsp;&nbsp; This simplification may reduce coverage in a network.&nbsp; In addition to<br>&nbsp;&nbsp; limiting protection for multi-homed prefixes (see Section 6.1), the<br>&nbsp;&nbsp; computation per next-hop may also not find an LFA when one could be
<br>&nbsp;&nbsp; found for some of the prefixes that use that next-hop.<br><br>&nbsp;&nbsp; For example, consider Figure 4 where S has 3 ECMP next-hops, E1, E2,<br>&nbsp;&nbsp; and E3 to reach D. For the prefix D, E3 can give link protection for<br>&nbsp;&nbsp; the next-hops E1 and E2; E1 and E2 can give link protection for the
<br>&nbsp;&nbsp; next-hops E3.&nbsp; However, if one uses this simplification to compute<br>&nbsp;&nbsp; LFAs for E1, E2 and E3 individually, there is no link-protecting LFA<br>&nbsp;&nbsp; for E1.&nbsp; E3 and E2 can protect each other.<br>&quot;<br><br>Again, I would welcome any comments on these changes or anything else
<br>in the draft.&nbsp; I plan to submit an updated draft next week.<br><br>Thanks,<br>Alia<br>

------=_Part_11462_11712934.1185553709730--



--===============1114004036==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg

--===============1114004036==--





