
From nobody Thu May  8 17:08:08 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C6F91A01BE; Thu,  8 May 2014 17:08:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GwUMjGeVzXg8; Thu,  8 May 2014 17:08:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id EB4301A01BF; Thu,  8 May 2014 17:08:01 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 92C2E1801C2; Thu,  8 May 2014 17:07:18 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7226 on Requirements for Advanced Multipath in MPLS Networks
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140509000718.92C2E1801C2@rfc-editor.org>
Date: Thu,  8 May 2014 17:07:18 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/L5_rHBIjeOLLKKnGtzIOjU15Jn8
Cc: drafts-update-ref@iana.org, rtgwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 May 2014 00:08:06 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7226

        Title:      Requirements for Advanced Multipath in 
                    MPLS Networks 
        Author:     C. Villamizar, Ed.,
                    D. McDysan, Ed.,
                    S. Ning, 
                    A. Malis,
                    L. Yong
        Status:     Informational
        Stream:     IETF
        Date:       May 2014
        Mailbox:    curtis@occnc.com, 
                    dave.mcdysan@verizon.com, 
                    ning.so@tatacommunications.com,
                    agmalis@gmail.com, 
                    lucy.yong@huawei.com
        Pages:      17
        Characters: 38581
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-cl-requirement-16.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7226.txt

This document provides a set of requirements for Advanced Multipath
in MPLS networks.

Advanced Multipath is a formalization of multipath techniques
currently in use in IP and MPLS networks and a set of extensions to
existing multipath techniques.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Mon May 12 08:06:11 2014
Return-Path: <pierre.francois@imdea.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFC5B1A072B for <rtgwg@ietfa.amsl.com>; Mon, 12 May 2014 08:06:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9b1LJrLGodVs for <rtgwg@ietfa.amsl.com>; Mon, 12 May 2014 08:06:05 -0700 (PDT)
Received: from estafeta21.imdea.org (maquina46.madrimasd.org [193.145.15.46]) by ietfa.amsl.com (Postfix) with ESMTP id 1223A1A071C for <rtgwg@ietf.org>; Mon, 12 May 2014 08:06:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by estafeta21.imdea.org (imdea mail daemon) with ESMTP id 2B9D91C918F; Mon, 12 May 2014 17:04:02 +0200 (CEST)
X-Virus-Scanned: by antispam-antivirus system at imdea.org
Received: from estafeta21.imdea.org ([127.0.0.1]) by localhost (estafeta21.imdea.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qdk_uWzvAs-T; Mon, 12 May 2014 17:04:01 +0200 (CEST)
Received: from dhcp-10-61-104-28.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: pierre.francois) by estafeta21.imdea.org (imdea mail daemon) with ESMTPSA id A7D7A1C918C; Mon, 12 May 2014 17:03:56 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_74BF5D14-4A13-4F5D-85BA-86E75E0E82A5"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: IPR Claims related to draft-litkowski-rtgwg-uloop-delay
From: Pierre Francois <pierre.francois@imdea.org>
In-Reply-To: <8333_1397225463_5347F7F7_8333_3783_1_53C29892C857584299CBF5D05346208A07130DAF@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Date: Mon, 12 May 2014 17:05:50 +0200
Message-Id: <65BBF285-0F59-41B0-9C1A-5EF4C67C4981@imdea.org>
References: <CF480B54.5097D%aretana@cisco.com> <CF6D68EA.5457B%aretana@cisco.com> <8333_1397225463_5347F7F7_8333_3783_1_53C29892C857584299CBF5D05346208A07130DAF@PEXCVZYM11.corporate.adroot.infra.ftgroup>
To: bruno.decraene@orange.com
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/QEMpapSkZN6bDUfHAzaNpO9_2Dw
Cc: "draft-litkowski-rtgwg-uloop-delay@tools.ietf.org" <draft-litkowski-rtgwg-uloop-delay@tools.ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 May 2014 15:06:09 -0000

--Apple-Mail=_74BF5D14-4A13-4F5D-85BA-86E75E0E82A5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


Hello Alvaro,=20

I am not sure I replied to this one :-S

Just to be sure: I am not aware of any other IPR claims than the ones =
already mentioned.=20

Regards,=20

Pierre.

On Apr 11, 2014, at 4:11 PM, bruno.decraene@orange.com wrote:

> Hi Alvaro,
> =20
> I am not aware of any other IPR claims than the one already mentioned.
> =20
> Best regards,
> Bruno
> =20
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Alvaro Retana =
(aretana)
> Sent: Friday, April 11, 2014 3:41 PM
> To: draft-litkowski-rtgwg-uloop-delay@tools.ietf.org
> Cc: rtgwg@ietf.org
> Subject: Re: IPR Claims related to draft-litkowski-rtgwg-uloop-delay
> =20
> Authors:
> =20
> So far I have only heard back from one of you (Stephane).  We must =
hear from all of you (yes, all 4 of you) if this draft is to progress.
> =20
> Thanks!
> =20
> Alvaro.
> =20
> =20
> On 3/14/14 1:26 AM, "Alvaro Retana (aretana)" <aretana@cisco.com> =
wrote:
> =20
> Hi!
> =20
> In parallel to the WG Adoption Call for this draft, I want to formally =
ask the authors (no additional contributors are listed in the latest =
version) to please respond to this message indicating whether or not you =
are aware of any relevant IPR.  The draft will not progress (pending the =
results of the WG Adoption Call) until we have received a response from =
each author.
> =20
> Thanks!
> =20
> Alvaro.
> =20
> =
__________________________________________________________________________=
_______________________________________________
>=20
> Ce message et ses pieces jointes peuvent contenir des informations =
confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez =
recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les =
messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, =
deforme ou falsifie. Merci.
>=20
> This message and its attachments may contain confidential or =
privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and =
delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have =
been modified, changed or falsified.
> Thank you.
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


--Apple-Mail=_74BF5D14-4A13-4F5D-85BA-86E75E0E82A5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"><base href=3D"x-msg://8985/"></head><body =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><br></div>Hello =
Alvaro,&nbsp;<div><br></div><div>I am not sure I replied to this one =
:-S</div><div><br></div><div>Just to be sure: I am not aware of any =
other IPR claims than the ones already =
mentioned.&nbsp;</div><div><br></div><div>Regards,&nbsp;</div><div><br></d=
iv><div>Pierre.</div><div><br><div><div>On Apr 11, 2014, at 4:11 PM, <a =
href=3D"mailto:bruno.decraene@orange.com">bruno.decraene@orange.com</a> =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div lang=3D"FR" link=3D"blue" vlink=3D"purple" =
style=3D"font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><div class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><font size=3D"2" color=3D"#1f497d" =
face=3D"Calibri"><span lang=3D"EN-US" style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">Hi =
Alvaro,<o:p></o:p></span></font></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri"><span lang=3D"EN-US"=
 style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">&nbsp;</span></font></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri"><span lang=3D"EN-US"=
 style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">I am not aware of any other IPR claims than the one =
already mentioned.<o:p></o:p></span></font></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><font size=3D"2" color=3D"#1f497d" face=3D"Calibri"><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">&nbsp;</span></font></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri"><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">Best regards,<o:p></o:p></span></font></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><font size=3D"2" color=3D"#1f497d" =
face=3D"Calibri"><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); =
">Bruno<o:p></o:p></span></font></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri"><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">&nbsp;</span></font></div><div style=3D"border-style: =
none none none solid; border-left-width: 1.5pt; border-left-color: blue; =
padding: 0cm 0cm 0cm 4pt; "><div><div style=3D"border-style: solid none =
none; border-top-width: 1pt; border-top-color: rgb(181, 196, 223); =
padding: 3pt 0cm 0cm; "><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><b><font =
size=3D"2" face=3D"Tahoma"><span style=3D"font-size: 10pt; font-family: =
Tahoma, sans-serif; font-weight: bold; ">From:</span></font></b><font =
size=3D"2" face=3D"Tahoma"><span style=3D"font-size: 10pt; font-family: =
Tahoma, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span>rtgwg [mailto:rtgwg-<a =
href=3D"mailto:bounces@ietf.org" style=3D"color: purple; =
text-decoration: underline; ">bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b><span =
style=3D"font-weight: bold; ">On Behalf Of<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b>Alvaro Retana =
(aretana)<br><b><span style=3D"font-weight: bold; =
">Sent:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Friday, April 11, 2014 3:41 =
PM<br><b><span style=3D"font-weight: bold; ">To:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:draft-litkowski-rtgwg-uloop-delay@tools.ietf.org" =
style=3D"color: purple; text-decoration: underline; =
">draft-litkowski-rtgwg-uloop-delay@tools.ietf.org</a><br><b><span =
style=3D"font-weight: bold; ">Cc:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:rtgwg@ietf.org" style=3D"color: purple; text-decoration: =
underline; ">rtgwg@ietf.org</a><br><b><span style=3D"font-weight: bold; =
">Subject:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: IPR Claims related to =
draft-litkowski-rtgwg-uloop-delay<o:p></o:p></span></font></div></div></di=
v><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: =
'Times New Roman', serif; "><font size=3D"3" face=3D"Times New =
Roman"><span style=3D"font-size: 12pt; =
">&nbsp;</span></font></div><div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><font size=3D"2"=
 face=3D"Calibri"><span style=3D"font-size: 10.5pt; font-family: =
Calibri, sans-serif; =
">Authors:<o:p></o:p></span></font></div></div><div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><font size=3D"2" face=3D"Calibri"><span style=3D"font-size: =
10.5pt; font-family: Calibri, sans-serif; =
">&nbsp;</span></font></div></div><div><div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><font size=3D"2" face=3D"Calibri"><span style=3D"font-size: 10.5pt; =
font-family: Calibri, sans-serif; ">So far I have only heard back from =
one of you (Stephane). &nbsp;We must hear from all of you (yes, all 4 of =
you) if this draft is to =
progress.<o:p></o:p></span></font></div></div><div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><font size=3D"2" face=3D"Calibri"><span style=3D"font-size: =
10.5pt; font-family: Calibri, sans-serif; =
">&nbsp;</span></font></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><font size=3D"2" face=3D"Calibri"><span style=3D"font-size: 10.5pt; =
font-family: Calibri, sans-serif; =
">Thanks!<o:p></o:p></span></font></div></div><div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><font size=3D"2" face=3D"Calibri"><span style=3D"font-size: =
10.5pt; font-family: Calibri, sans-serif; =
">&nbsp;</span></font></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><font size=3D"2" face=3D"Calibri"><span style=3D"font-size: 10.5pt; =
font-family: Calibri, sans-serif; =
">Alvaro.<o:p></o:p></span></font></div></div></div><div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><font size=3D"2" face=3D"Calibri"><span =
style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; =
">&nbsp;</span></font></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><font size=3D"2" face=3D"Calibri"><span style=3D"font-size: 10.5pt; =
font-family: Calibri, sans-serif; =
">&nbsp;</span></font></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><font size=3D"2" face=3D"Calibri"><span style=3D"font-size: 10.5pt; =
font-family: Calibri, sans-serif; ">On 3/14/14 1:26 AM, "Alvaro Retana =
(aretana)" &lt;<a href=3D"mailto:aretana@cisco.com" style=3D"color: =
purple; text-decoration: underline; ">aretana@cisco.com</a>&gt; =
wrote:<o:p></o:p></span></font></div></div><div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><font size=3D"2" face=3D"Calibri"><span style=3D"font-size: =
10.5pt; font-family: Calibri, sans-serif; =
">&nbsp;</span></font></div></div><blockquote =
id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"border-style: none =
none none solid; border-left-width: 4.5pt; border-left-color: rgb(181, =
196, 223); padding: 0cm 0cm 0cm 4pt; margin-left: 3.75pt; margin-right: =
0cm; "><div><div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><font size=3D"2" =
face=3D"Calibri"><span style=3D"font-size: 10.5pt; font-family: Calibri, =
sans-serif; ">Hi!<o:p></o:p></span></font></div></div><div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><font size=3D"2" face=3D"Calibri"><span =
style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; =
">&nbsp;</span></font></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><font size=3D"2" face=3D"Calibri"><span style=3D"font-size: 10.5pt; =
font-family: Calibri, sans-serif; ">In parallel to the WG Adoption Call =
for this draft,&nbsp;I want to formally ask the authors (no additional =
contributors are listed in the latest version) to please respond to this =
message indicating whether or not you are aware of any relevant IPR. =
&nbsp;The draft will not progress (pending the results of the WG =
Adoption Call) until we have received a response from each =
author.<o:p></o:p></span></font></div></div><div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><font size=3D"2" face=3D"Calibri"><span style=3D"font-size: =
10.5pt; font-family: Calibri, sans-serif; =
">&nbsp;</span></font></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><font size=3D"2" face=3D"Calibri"><span style=3D"font-size: 10.5pt; =
font-family: Calibri, sans-serif; =
">Thanks!<o:p></o:p></span></font></div></div><div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><font size=3D"2" face=3D"Calibri"><span style=3D"font-size: =
10.5pt; font-family: Calibri, sans-serif; =
">&nbsp;</span></font></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><font size=3D"2" face=3D"Calibri"><span style=3D"font-size: 10.5pt; =
font-family: Calibri, sans-serif; =
">Alvaro.<o:p></o:p></span></font></div></div></div><div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><font size=3D"2" face=3D"Calibri"><span =
style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; =
">&nbsp;</span></font></div></div></blockquote></div></div><pre>__________=
__________________________________________________________________________=
_____________________________________

Ce message et ses pieces jointes peuvent contenir des informations =
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez =
recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages =
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme =
ou falsifie. Merci.

This message and its attachments may contain confidential or privileged =
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and =
delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have =
been modified, changed or falsified.
Thank you.
</pre>_______________________________________________<br>rtgwg mailing =
list<br><a href=3D"mailto:rtgwg@ietf.org" style=3D"color: purple; =
text-decoration: underline; ">rtgwg@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/rtgwg" style=3D"color: =
purple; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/rtgwg</a><br></div></blockquote></=
div><br></div></body></html>=

--Apple-Mail=_74BF5D14-4A13-4F5D-85BA-86E75E0E82A5--


From nobody Mon May 12 15:12:41 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD41B1A078D for <rtgwg@ietfa.amsl.com>; Mon, 12 May 2014 15:12:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.15
X-Spam-Level: 
X-Spam-Status: No, score=-10.15 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MplWkyRATlcI for <rtgwg@ietfa.amsl.com>; Mon, 12 May 2014 15:12:31 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) by ietfa.amsl.com (Postfix) with ESMTP id EFD021A0785 for <rtgwg@ietf.org>; Mon, 12 May 2014 15:12:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=32100; q=dns/txt; s=iport; t=1399932744; x=1401142344; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=u6qJ2YvgejeapJPGx6aIAId24wTcl2ciTiWD7aRZ2WE=; b=VjHO21ExKOC2zWpebvlf3zGYK3OkpF50e8T8BjhJaIMY8ulieQiilcm0 ScunmZWn06dRtEGnQf2+dddu6Ujp9Gl/f/qahc9DaMzsNcYIunrRfUPDB Q7SW812mD+luUb9owLYzBVj/JV6YR3apFvi3qWFWSDBgz6/nrluPTYTyQ E=;
X-IronPort-AV: E=Sophos;i="4.97,1038,1389744000";  d="scan'208,217";a="42235196"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 12 May 2014 22:12:23 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s4CMCMwc021590 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 May 2014 22:12:23 GMT
Received: from STBRYANT-M-R010.CISCO.COM (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s4CMCLCC024359; Mon, 12 May 2014 23:12:21 +0100 (BST)
Message-ID: <53714745.9040207@cisco.com>
Date: Mon, 12 May 2014 23:12:21 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Alia Atlas <akatlas@gmail.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>
Subject: Re: WGLC for draft-ietf-rtgwg-remote-lfa
References: <CEC4C406.43593%aretana@cisco.com> <CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com>
In-Reply-To: <CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------000604050504020503050302"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/t84xJh757LdeRlZFZMl8__Z1uHo
Cc: "draft-ietf-rtgwg-remote-lfa@tools.ietf.org" <draft-ietf-rtgwg-remote-lfa@tools.ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 May 2014 22:12:36 -0000

This is a multi-part message in MIME format.
--------------000604050504020503050302
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I am in the process of working through the comments received.

I have started with Alia's comments, which I have addressed as indicated
below.

I will post this as version -05. I will incorporate the other comments and
comments on the changes made in -05 in -06.


On 06/12/2013 23:03, Alia Atlas wrote:
> I've given this draft a thorough reading (except for commenting on the 
> cost-based algorithm that Pushpasis already gave feedback on).
>
> I have two major concerns.  First, I see no discussion at all about 
> how multipoint interfaces are handled.  Nothing indicates that they 
> are out of scope for protection nor does the discussion describe how 
> to handle avoiding the pseudo-nodes or related computation.
This is clarified in the Abstract, the ending of the Introduction and 
with some additional text in Section 4.3.

> Second, as a standards-track document, I see almost no description of 
> what MUST or even SHOULD be implemented.  What would conformance mean?
Please look version -05 and let us know if this is now addressed.
If not, please indicate what we need to address.
>
> Here are my detailed comments - in going through the draft order, not 
> by priority.
>
> 0)Sec 2: Can you add a paragraph describing the extended-P space and
> Q-space for the example in Figure 2?  It's fine to have the
> definitions, but it is jarring to run into Q-space in Sec 4 without
> any other reference.  For instance, just adding:
>
> "In [Figure 1], S can reach A, B, and C without going via E; these
> form S's extended P-space.  The routers that can reach E without going
> through S-E will be E's Q-space; these are D and C.  B has equal-cost
> paths via B-A-S-E and B-C-D-E and so may go through S-E.  The single
> node in both S's P-space and E's Q-space is C; thus node C is selected
> as the repair tunnel's end-point.  For more details on the reasoning
> behind these calculations, please see [Sec 4.2]"

Added

>
> 1) Sec 3, 2nd paragraph, 1 sentence:
>   "A tunneled repair path tunnels traffic to some staging point in the
>    network from which it is assumed that, in the absence of multiple
>    failures, it will travel to its destination using normal forwarding
>    without looping back."
>
> First, can you replace "assumed" with precalculated or the like?  This
> isn't an assumption - it is based on shortest-path forwarding and is
> carefully determined.
Done
>
> Second, "in the absence of multiple failures" should be "in the
> absence of a worse failure (e.g. node or SRLG) or multiple failures".
>
Done
> 2) Sec 3.1: For clarity, could you add a sentence indicating that the
> tunnel itself must also avoid going over the link S-E?
Done
>
> 3) Sec 3.2, 2nd paragraph:  "In order for S to obtain
>    the correct inner label it is necessary to establish a directed LDP
>    session[RFC5036] to the tunnel end point."
>
> Shouldn't that be a "targeted LDP session"?  I don't see directed at
> all in RFC5036 and am personally only familiar with them being called
> targeted LDP sessions.
Done
>
> 4) Sec 3.2 3rd paragraph: "The performance of the encapsulation and
> decapsulation is efficient as encapsulation is just a push of one
> label (like conventional MPLS TE FRR) and the decapsulation occurs
> naturally at the penultimate hop before the repair tunnel endpoint."
>
> Decapsulation can occur at the penultimate hop, if the repair tunnel
> endpoint so specifies.

The text now says ...the decapsulation is normally configured
to occur at the penultimate hop...

>
> 5) Sec 3.2 3rd paragraph: "The time to establish the TLDP session and
> acquire labels will limit the speed at which a new tunnel can be put
> into service, but this will not be a problem in normal operation."
>
> Can you please put some justification as to why this will not be a
> problem in normal operation?  Is your assumption that the added delay
> before the network is fully repaired acceptable because failure
> analysis studies indicate the separation between failures is generally
> at least X seconds and the time to establish a TLDP session and
> exchange labels (how many) is no more than Y seconds (in a router that
> is also dealing with reconvergence of all protocols beyond the IGP)?
>
> The extra communication clearly adds some delay before protection is
> available and a blanket assertion that it doesn't matter is more
> marketing than engineering.
It now says

"The time to establish the TLDP session and acquire labels will limit the
speed at which a new tunnel can be put into service. This is not 
anticipated
to be a problem in normal operation since the managed introduction
and removal of links is relatively rare as is the incidence of failure in a
well managed network."

>
> 6) Given that this is a standards-track draft, is there a reason that
> a minimum-to-implement tunnel type isn't specified?  I don't see/know
> of any references for how a router can know if a remote router can
> decapsulate IP-in-IP at speed or support GRE or even support a tLDP
> session.
There will normally be a preferred IP tunnel type in a particular IP network
and I would assume that was the type preferred for this purpose as well.
If we specify GRE and the network prefers IP-IP we cause more problems
than we solve. It therefore seems best to leave the IP tunnel type to the
preference of the operator.

Section 7 discusses the LDP case.

>
> 7) Sec 4.1: This seems to be ignoring the protection of per-prefix
> LFA, which is a superset of "link LFA".  More critically, as you know,
> doing per-prefix LFA can allow the protection of multi-homed prefixes.
> Can you please update this section to indicate how and if remote LFA
> applies to multi-homed prefixes?  As written, it sounds like it does
> not.  It also sounds as if remote LFA is required even if there is a
> per-prefix LFA for all destinations going via S-E.
The text now says:

Tunneled repair paths (which may be calculated per-prefix) are only
required for links which do not have a link or per-prefix LFA.
>
> 8) Sec 4.2.1, 2nd paragraph: "We will proceed as follows: we will
> describe how to compute the set of routers which can be reached from S
> without traversing S-E."
>
> For clarity, can you change this to: "how to compute the set of
> routers which can be reached from S on the shortest-path tree without
> traversing S-E"?  That may help remove some of the confusion when you
> then define extended P-space - where clearly S can reach as well."
>
> Please make the same change in the first sentence of 4.2.1.1.
I have reworded section 4.2.1 and included this change.
>
> 9) Sec 4.2.1.1 <http://4.2.1.1>: First, can you explain why you remove 
> those nodes that
> are ECMP in the draft?  I assume it is because such nodes require a
> directed first hop to avoid accidentally going through S-E.
>
> Second, after describing "excising the sub-tree" - what about a quick
> clue such as: "For example, if an SPF computation stores at each node
> the next-hops to be used to reach that node from S, then one can
> simply add a node to P-space if none of its next-hops are S-E"

The text has been reworded. Please check it.
>
> 10) How are multi-point interfaces handled?  I see no discussion of
> that in Sec 4.2.1.1 or Sec 4.2.1.2.
I am not sure further text is required. Please explain the problem
you are concerned about.
>
> 11) In Sec 5, I am confused by the example and I believe it is because
> there are typos?
>
> "When a failure occurs on the link between PE1 and P2, PE1 does not
> have an LFA for traffic reachable via P1.  Similarly, by symmetry, if
> the link between PE2 and P1 fails, PE2 does not have an LFA for
> traffic reachable via P2."
>
> But PE2->P1 has a cost of 1000 and PE1's path to P1 isn't affected by
> the failure of the link PE1-P2...  Could you please correct or clarify?
Figure corrected.
>
> 12) Sec 6: Given that [I-D.bryant-ipfrr-tunnels] is expired and not
> intended for publication and this draft is heading towards RFC, is
> there a reason not to accurately and fully pull out the problem
> description into this draft?
I am in the process of sending this to the ISE with some de-conflict
notes in the introduction.

Given that text and the existence of the node-protecting draft I think
that pulling text into this draft will make this draft unbalanced WRT the
problem it addresses.

>
> 13) Sec 6: The same problems can occur with SRLG failures.  Can you
> please add a brief paragraph decribing how the different cases apply
> for SRLG failure?  Also, please expand on the analysis recommendation.
I have added a sentence which I think addresses the issue succinctly.
>
> 14) Sec 7, 2nd paragraph: reference is to "Section 2" instead of
> "Figure 2".
Done
>
> 15) Sec 8: please update the "date of this draft" to be an actual date
> - as the draft is revised and progresses, this would falsely imply
> more recent data than will be there.
Done
>
> 16) Sec 8: Can you please define what is meant by "protected
> destinations" and "guaranteed node-protected destinations"?  Is the
> first if a destination is protected from all sources against all link
> failures?  Is it something more limited such as PLR/dest pairs?
This is clarified in the text
>
> 17) Sec 8.4: typo - "saleability" should be "scaleability".
Done
>
> 18) Sec 8.4:  The end of this section
>
> "In the very few cases where P and Q spaces have an empty
> intersection, one could select the closest node in the Q space and
> signal an explicitly-routed RSVP TE LSP to that Q node.  A directed
> LDP session is then established with the selected Q node and the rest
> of the solution is identical to that described elsewhere in this
> document.  Alternatively the segment routing technology being defined
> in the IETF may be used to carry the traffic between non-collocated P
> and Q nodes [I-D.filsfils-rtgwg-segment-routing-use-cases],
> [I-D.filsfils-rtgwg-segment-routing],
> [I-D.gredler-rtgwg-igp-label-advertisement]."
>
> seems to be describing functionality that isn't fully specified or
> mentioned elsewhere in the draft and that doesn't fall within RTGWG's
> charter.  If we include explicit routing rather than hop-by-hop, we've
> known how to do that for years.  At a minimum, it'd be useful to put
> this paragraph in a section by itself that is "Potential Coverage
> Improvements Via Explicit Routing" or the like.

I have used the word "potential"

- Stewart


--------------000604050504020503050302
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">I am in the process of working through
      the comments received.<br>
      <br>
      I have started with Alia's comments, which I have addressed as
      indicated<br>
      below.<br>
      <br>
      I will post this as version -05. I will incorporate the other
      comments and<br>
      comments on the changes made in -05 in -06.<br>
      <br>
      <br>
      On 06/12/2013 23:03, Alia Atlas wrote:<br>
    </div>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div dir="ltr">I've given this draft a thorough reading (except
        for commenting on the cost-based algorithm that Pushpasis
        already gave feedback on).
        <div><br>
        </div>
        <div>I have two major concerns. &nbsp;First, I see no discussion at
          all about how multipoint interfaces are handled. &nbsp;Nothing
          indicates that they are out of scope for protection nor does
          the discussion describe how to handle avoiding the
          pseudo-nodes or related computation.&nbsp; <br>
        </div>
      </div>
    </blockquote>
    This is clarified in the Abstract, the ending of the Introduction
    and with some additional text in Section 4.3.<br>
    <br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>Second, as a standards-track document, I see almost no
          description of what MUST or even SHOULD be implemented. &nbsp;What
          would conformance mean?</div>
      </div>
    </blockquote>
    Please look version -05 and let us know if this is now addressed.<br>
    If not, please indicate what we need to address.<br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br>
        </div>
        <div>Here are my detailed comments - in going through the draft
          order, not by priority.</div>
        <div><br>
        </div>
        <div>
          <div>0)Sec 2: Can you add a paragraph describing the
            extended-P space and</div>
          <div>Q-space for the example in Figure 2? &nbsp;It's fine to have
            the</div>
          <div>definitions, but it is jarring to run into Q-space in Sec
            4 without</div>
          <div>any other reference. &nbsp;For instance, just adding:</div>
          <div><br>
          </div>
          <div>"In [Figure 1], S can reach A, B, and C without going via
            E; these</div>
          <div>form S's extended P-space. &nbsp;The routers that can reach E
            without going</div>
          <div>through S-E will be E's Q-space; these are D and C. &nbsp;B
            has equal-cost</div>
          <div>paths via B-A-S-E and B-C-D-E and so may go through S-E.
            &nbsp;The single</div>
          <div>node in both S's P-space and E's Q-space is C; thus node
            C is selected</div>
          <div>as the repair tunnel's end-point. &nbsp;For more details on
            the reasoning</div>
          <div>behind these calculations, please see [Sec 4.2]"</div>
        </div>
      </div>
    </blockquote>
    <br>
    Added<br>
    <br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>1) Sec 3, 2nd paragraph, 1 sentence:</div>
          <div>&nbsp; "A tunneled repair path tunnels traffic to some staging
            point in the</div>
          <div>&nbsp; &nbsp;network from which it is assumed that, in the absence
            of multiple</div>
          <div>&nbsp; &nbsp;failures, it will travel to its destination using
            normal forwarding</div>
          <div>&nbsp; &nbsp;without looping back."</div>
          <div><br>
          </div>
          <div>First, can you replace "assumed" with precalculated or
            the like? &nbsp;This</div>
          <div>isn't an assumption - it is based on shortest-path
            forwarding and is</div>
          <div>carefully determined.</div>
        </div>
      </div>
    </blockquote>
    Done<br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>Second, "in the absence of multiple failures" should be
            "in the</div>
          <div>
            absence of a worse failure (e.g. node or SRLG) or multiple
            failures".</div>
          <div><br>
          </div>
        </div>
      </div>
    </blockquote>
    Done<br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>2) Sec 3.1: For clarity, could you add a sentence
            indicating that the</div>
          <div>tunnel itself must also avoid going over the link S-E?</div>
        </div>
      </div>
    </blockquote>
    Done<br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>3) Sec 3.2, 2nd paragraph: &nbsp;"In order for S to obtain</div>
          <div>&nbsp; &nbsp;the correct inner label it is necessary to establish a
            directed LDP</div>
          <div>&nbsp; &nbsp;session[RFC5036] to the tunnel end point."</div>
          <div><br>
          </div>
          <div>Shouldn't that be a "targeted LDP session"? &nbsp;I don't see
            directed at</div>
          <div>all in RFC5036 and am personally only familiar with them
            being called</div>
          <div>targeted LDP sessions.</div>
        </div>
      </div>
    </blockquote>
    Done<br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>4) Sec 3.2 3rd paragraph: "The performance of the
            encapsulation and</div>
          <div>decapsulation is efficient as encapsulation is just a
            push of one</div>
          <div>label (like conventional MPLS TE FRR) and the
            decapsulation occurs</div>
          <div>naturally at the penultimate hop before the repair tunnel
            endpoint."</div>
          <div><br>
          </div>
          <div>Decapsulation can occur at the penultimate hop, if the
            repair tunnel</div>
          <div>endpoint so specifies.</div>
        </div>
      </div>
    </blockquote>
    <br>
    The text now says ...the decapsulation is normally configured <br>
    to occur at the penultimate hop...<br>
    <br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>5) Sec 3.2 3rd paragraph: "The time to establish the TLDP
            session and</div>
          <div>acquire labels will limit the speed at which a new tunnel
            can be put</div>
          <div>into service, but this will not be a problem in normal
            operation."</div>
          <div><br>
          </div>
          <div>Can you please put some justification as to why this will
            not be a</div>
          <div>problem in normal operation? &nbsp;Is your assumption that the
            added delay</div>
          <div>before the network is fully repaired acceptable because
            failure</div>
          <div>analysis studies indicate the separation between failures
            is generally</div>
          <div>at least X seconds and the time to establish a TLDP
            session and</div>
          <div>exchange labels (how many) is no more than Y seconds (in
            a router that</div>
          <div>is also dealing with reconvergence of all protocols
            beyond the IGP)?</div>
          <div><br>
          </div>
          <div>The extra communication clearly adds some delay before
            protection is</div>
          <div>available and a blanket assertion that it doesn't matter
            is more</div>
          <div>marketing than engineering.</div>
        </div>
      </div>
    </blockquote>
    It now says <br>
    <br>
    "The time to establish the TLDP session and acquire labels will
    limit the <br>
    speed at which a new tunnel can be put into service. This is not
    anticipated <br>
    to be a problem in normal operation since the managed introduction <br>
    and removal of links is relatively rare as is the incidence of
    failure in a <br>
    well managed network."<br>
    <br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>6) Given that this is a standards-track draft, is there a
            reason that</div>
          <div>a minimum-to-implement tunnel type isn't specified? &nbsp;I
            don't see/know</div>
          <div>of any references for how a router can know if a remote
            router can</div>
          <div>decapsulate IP-in-IP at speed or support GRE or even
            support a tLDP</div>
          <div>session.</div>
        </div>
      </div>
    </blockquote>
    There will normally be a preferred IP tunnel type in a particular IP
    network<br>
    and I would assume that was the type preferred for this purpose as
    well.<br>
    If we specify GRE and the network prefers IP-IP we cause more
    problems<br>
    than we solve. It therefore seems best to leave the IP tunnel type
    to the<br>
    preference of the operator. <br>
    <br>
    Section 7 discusses the LDP case.<br>
    <br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>7) Sec 4.1: This seems to be ignoring the protection of
            per-prefix</div>
          <div>LFA, which is a superset of "link LFA". &nbsp;More critically,
            as you know,</div>
          <div>doing per-prefix LFA can allow the protection of
            multi-homed prefixes.</div>
          <div>Can you please update this section to indicate how and if
            remote LFA</div>
          <div>applies to multi-homed prefixes? &nbsp;As written, it sounds
            like it does</div>
          <div>not. &nbsp;It also sounds as if remote LFA is required even if
            there is a</div>
          <div>per-prefix LFA for all destinations going via S-E.</div>
        </div>
      </div>
    </blockquote>
    The text now says:<br>
    <br>
    Tunneled repair paths (which may be calculated per-prefix) are only
    <br>
    required for links which do not have a link or per-prefix LFA.<br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <br>
          </div>
          <div>8) Sec 4.2.1, 2nd paragraph: "We will proceed as follows:
            we will</div>
          <div>describe how to compute the set of routers which can be
            reached from S</div>
          <div>without traversing S-E."</div>
          <div><br>
          </div>
          <div>For clarity, can you change this to: "how to compute the
            set of</div>
          <div>routers which can be reached from S on the shortest-path
            tree without</div>
          <div>traversing S-E"? &nbsp;That may help remove some of the
            confusion when you</div>
          <div>then define extended P-space - where clearly S can reach
            as well."</div>
          <div><br>
          </div>
          <div>Please make the same change in the first sentence of
            4.2.1.1.</div>
        </div>
      </div>
    </blockquote>
    I have reworded section 4.2.1 and included this change.<br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>9) Sec <a moz-do-not-send="true" href="http://4.2.1.1">4.2.1.1</a>:
            First, can you explain why you remove those nodes that</div>
          <div>are ECMP in the draft? &nbsp;I assume it is because such nodes
            require a</div>
          <div>directed first hop to avoid accidentally going through
            S-E.</div>
          <div><br>
          </div>
          <div>Second, after describing "excising the sub-tree" - what
            about a quick</div>
          <div>clue such as: "For example, if an SPF computation stores
            at each node</div>
          <div>the next-hops to be used to reach that node from S, then
            one can</div>
          <div>simply add a node to P-space if none of its next-hops are
            S-E"</div>
        </div>
      </div>
    </blockquote>
    <br>
    The text has been reworded. Please check it.<br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>10) How are multi-point interfaces handled? &nbsp;I see no
            discussion of</div>
          <div>that in Sec 4.2.1.1 or Sec 4.2.1.2.</div>
        </div>
      </div>
    </blockquote>
    I am not sure further text is required. Please explain the problem<br>
    you are concerned about.<br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>11) In Sec 5, I am confused by the example and I believe
            it is because</div>
          <div>there are typos?</div>
          <div><br>
          </div>
          <div>"When a failure occurs on the link between PE1 and P2,
            PE1 does not</div>
          <div>have an LFA for traffic reachable via P1. &nbsp;Similarly, by
            symmetry, if</div>
          <div>the link between PE2 and P1 fails, PE2 does not have an
            LFA for</div>
          <div>traffic reachable via P2."</div>
          <div><br>
          </div>
          <div>But PE2-&gt;P1 has a cost of 1000 and PE1's path to P1
            isn't affected by</div>
          <div>the failure of the link PE1-P2... &nbsp;Could you please
            correct or clarify?</div>
        </div>
      </div>
    </blockquote>
    Figure corrected.<br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>12) Sec 6: Given that [I-D.bryant-ipfrr-tunnels] is
            expired and not</div>
          <div>intended for publication and this draft is heading
            towards RFC, is</div>
          <div>there a reason not to accurately and fully pull out the
            problem</div>
          <div>description into this draft?</div>
        </div>
      </div>
    </blockquote>
    I am in the process of sending this to the ISE with some de-conflict<br>
    notes in the introduction.<br>
    <br>
    Given that text and the existence of the node-protecting draft I
    think<br>
    that pulling text into this draft will make this draft unbalanced
    WRT the<br>
    problem it addresses.<br>
    <br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>13) Sec 6: The same problems can occur with SRLG
            failures. &nbsp;Can you</div>
          <div>please add a brief paragraph decribing how the different
            cases apply</div>
          <div>for SRLG failure? &nbsp;Also, please expand on the analysis
            recommendation.</div>
        </div>
      </div>
    </blockquote>
    I have added a sentence which I think addresses the issue
    succinctly.<br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>14) Sec 7, 2nd paragraph: reference is to "Section 2"
            instead of</div>
          <div>"Figure 2".</div>
        </div>
      </div>
    </blockquote>
    Done<br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>15) Sec 8: please update the "date of this draft" to be
            an actual date</div>
          <div>- as the draft is revised and progresses, this would
            falsely imply</div>
          <div>more recent data than will be there.</div>
        </div>
      </div>
    </blockquote>
    Done<br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>16) Sec 8: Can you please define what is meant by
            "protected</div>
          <div>destinations" and "guaranteed node-protected
            destinations"? &nbsp;Is the</div>
          <div>first if a destination is protected from all sources
            against all link</div>
          <div>failures? &nbsp;Is it something more limited such as PLR/dest
            pairs?</div>
        </div>
      </div>
    </blockquote>
    This is clarified in the text<br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>17) Sec 8.4: typo - "saleability" should be
            "scaleability".</div>
        </div>
      </div>
    </blockquote>
    Done<br>
    <blockquote
cite="mid:CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>18) Sec 8.4: &nbsp;The end of this section</div>
          <div><br>
          </div>
          <div>"In the very few cases where P and Q spaces have an empty</div>
          <div>intersection, one could select the closest node in the Q
            space and</div>
          <div>signal an explicitly-routed RSVP TE LSP to that Q node.
            &nbsp;A directed</div>
          <div>LDP session is then established with the selected Q node
            and the rest</div>
          <div>of the solution is identical to that described elsewhere
            in this</div>
          <div>document. &nbsp;Alternatively the segment routing technology
            being defined</div>
          <div>in the IETF may be used to carry the traffic between
            non-collocated P</div>
          <div>and Q nodes
            [I-D.filsfils-rtgwg-segment-routing-use-cases],</div>
          <div>[I-D.filsfils-rtgwg-segment-routing],</div>
          <div>[I-D.gredler-rtgwg-igp-label-advertisement]."</div>
          <div><br>
          </div>
          <div>seems to be describing functionality that isn't fully
            specified or</div>
          <div>mentioned elsewhere in the draft and that doesn't fall
            within RTGWG's</div>
          <div>charter. &nbsp;If we include explicit routing rather than
            hop-by-hop, we've</div>
          <div>known how to do that for years. &nbsp;At a minimum, it'd be
            useful to put</div>
          <div>this paragraph in a section by itself that is "Potential
            Coverage</div>
          <div>Improvements Via Explicit Routing" or the like.</div>
        </div>
      </div>
    </blockquote>
    <br>
    I have used the word "potential"<br>
    <br>
    - Stewart<br>
    <br>
  </body>
</html>

--------------000604050504020503050302--


From nobody Mon May 12 15:49:45 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AC5A1A07D0; Mon, 12 May 2014 15:49:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GqpUUWrQ4UBb; Mon, 12 May 2014 15:49:39 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1061F1A07B2; Mon, 12 May 2014 15:49:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-rtgwg-remote-lfa-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140512224939.16327.37051.idtracker@ietfa.amsl.com>
Date: Mon, 12 May 2014 15:49:39 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/smkCw9F4E9rLuwpkTUrTOMiboOc
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 May 2014 22:49:40 -0000

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           : Remote LFA FRR
        Authors         : Stewart Bryant
                          Clarence Filsfils
                          Stefano Previdi
                          Mike Shand
                          Ning So
	Filename        : draft-ietf-rtgwg-remote-lfa-05.txt
	Pages           : 26
	Date            : 2014-05-12

Abstract:
   This draft describes an extension to the basic IP fast re-route
   mechanism described in RFC5286, that provides additional backup
   connectivity for point to point link failures when none can be
   provided by the basic mechanisms.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-remote-lfa-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Wed May 14 08:04:24 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A20FF1A00CD; Wed, 14 May 2014 08:04:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yt72zVpga-af; Wed, 14 May 2014 08:04:04 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A502B1A0138; Wed, 14 May 2014 08:03:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-rtgwg-cl-use-cases-06.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140514150352.16236.23431.idtracker@ietfa.amsl.com>
Date: Wed, 14 May 2014 08:03:52 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/U9Aj6PCrg3TkQUFeMhQhZzUll84
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 May 2014 15:04:06 -0000

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           : Advanced Multipath Use Cases and Design Considerations
        Authors         : So Ning
                          Andrew Malis
                          Dave McDysan
                          Lucy Yong
                          Curtis Villamizar
	Filename        : draft-ietf-rtgwg-cl-use-cases-06.txt
	Pages           : 24
	Date            : 2014-05-14

Abstract:
   Advanced Multipath is a formalization of multipath techniques
   currently in use in IP and MPLS networks and a set of extensions to
   existing multipath techniques.

   This document provides a set of use cases and design considerations
   for Advanced Multipath.  Existing practices are described.  Use cases
   made possible through Advanced Multipath extensions are described.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-cl-use-cases/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rtgwg-cl-use-cases-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-cl-use-cases-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Wed May 14 16:28:43 2014
Return-Path: <jeff.tantsura@ericsson.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A21021A0371 for <rtgwg@ietfa.amsl.com>; Wed, 14 May 2014 16:28:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QcUuxnmoRL3r for <rtgwg@ietfa.amsl.com>; Wed, 14 May 2014 16:28:39 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27DB81A036F for <rtgwg@ietf.org>; Wed, 14 May 2014 16:28:38 -0700 (PDT)
X-AuditID: c618062d-f79c96d000001cfc-ea-5373acbbbc44
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id E6.78.07420.BBCA3735; Wed, 14 May 2014 19:49:47 +0200 (CEST)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0174.001; Wed, 14 May 2014 19:28:30 -0400
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: YANG Advice and Editing Session at the next IETF meeting
Thread-Topic: YANG Advice and Editing Session at the next IETF meeting
Thread-Index: AQJemqlFCRGuNovK+JtC2MqxA5ciq5ogt5awgAF5NoA=
Date: Wed, 14 May 2014 23:28:30 +0000
Message-ID: <CF9949D0.5E07B%jeff.tantsura@ericsson.com>
References: <5372944D.5010509@cisco.com> <003701cf6ef6$941d92d0$bc58b870$@olddog.co.uk>
In-Reply-To: <003701cf6ef6$941d92d0$bc58b870$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.1.140326
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <93CAF70EB3BAA842A62676A2942A25BF@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyuXRPuO7uNcXBBo3rjCwuvPnN7MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujL7F+1gK3rNUzLr4m7GB8TtzFyMnh4SAicTxS/tYIGwxiQv3 1rOB2EICRxklpv/26GLkArKXM0q0X1oGVsQmYCDx/9txMFtEQFWid1YrUAMHh7CAq8SFm7YQ YTeJDWe+sEPYVhITFkwGK2cBKt/UMQcszitgLrH4y3ZmiF2RErv7+5hAbE4Ba4nVD16A2YxA 93w/tQbMZhYQl7j1ZD4TxJ0CEkv2nIe6X1Ti5eN/rCC2qICexLvjMDVKEnNeX2OG6NWRWLD7 ExuEbS3RcWQxO4StLbFs4WtmiHsEJU7OfMIygVF8FpJ1s5C0z0LSPgtJ+ywk7QsYWVcxcpQW p5blphsZbGIExs8xCTbdHYx7XloeYhTgYFTi4X1QVhwsxJpYVlyZe4hRmoNFSZy34EtssJBA emJJanZqakFqUXxRaU5q8SFGJg5OqQbGGckF8zXkPa5e/XTySKGvSapUSaKS+77fRlIf+U4y Gt81EBd7I/B3t9H9vJ2aXlf7s97d/T1z2q5VISqzAlS2/jRamcZeLN1dsCSxVmFNyP5jbSXT Vs147OIQN29brq3H3kNNLgdrG1NCruUfun9uhqzXihPzZzz/+4Ppvcn/a9N0rb5t2lhiqcRS nJFoqMVcVJwIAORoXweAAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/JH7pCFrZYg1OAv-LIYzgfYErsP0
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 May 2014 23:28:40 -0000

Hi,

If you are interested on YANG related work please come and join.

Cheers,
Jeff


>
>> -----Original Message-----
>> From: iesg [mailto:iesg-bounces@ietf.org] On Behalf Of Benoit Claise
>> Sent: 13 May 2014 22:53
>> To: undisclosed-recipients:
>> Subject: YANG Advice and Editing Session at the next IETF meeting
>>=20
>> [Sorry for the potential cross-posting]
>>=20
>> http://www.ietf.org/meeting/90/tutorials/yang-session.html
>> Let me stress that this should be an interactive session, and not a
>> tutorial.
>> So come with your (plan to create) YANG modules.
>>=20
>> Regards, Benoit
>


From nobody Wed May 14 22:08:29 2014
Return-Path: <liu.bin21@zte.com.cn>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32E3D1A03CE for <rtgwg@ietfa.amsl.com>; Wed, 14 May 2014 22:08:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.25
X-Spam-Level: 
X-Spam-Status: No, score=-99.25 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.651, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iiiMSpNeJyqU for <rtgwg@ietfa.amsl.com>; Wed, 14 May 2014 22:08:23 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 8173F1A022A for <rtgwg@ietf.org>; Wed, 14 May 2014 22:08:22 -0700 (PDT)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id B55A01261958 for <rtgwg@ietf.org>; Thu, 15 May 2014 13:08:04 +0800 (CST)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id 8F69C72700E; Thu, 15 May 2014 13:08:03 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id s4F586kw073022; Thu, 15 May 2014 13:08:06 +0800 (GMT-8) (envelope-from liu.bin21@zte.com.cn)
To: Hannes Gredler <hannes@juniper.net>, "Alvaro Retana (aretana)" <aretana@cisco.com>
Subject: Reply to comments -- Comparison between FAR and OSPF
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0 August 18, 2005
Message-ID: <OF7B611F3A.6F9BF7DF-ON48257CD9.0018F932-48257CD9.001C368E@zte.com.cn>
From: liu.bin21@zte.com.cn
Date: Thu, 15 May 2014 13:08:07 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2014-05-15 13:08:08, Serialize complete at 2014-05-15 13:08:08
Content-Type: multipart/alternative; boundary="=_alternative 001C368C48257CD9_="
X-MAIL: mse02.zte.com.cn s4F586kw073022
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/sbWpmAeFjc85kirVfCHSgzoNfkw
Cc: adrian@olddog.co.uk, ytsun <ytsun@bjtu.edu.cn>, rtgwg-chairs@tools.ietf.org, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 May 2014 05:08:27 -0000

This is a multipart message in MIME format.
--=_alternative 001C368C48257CD9_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

R3JlZXRpbmcgYWxsOg0KDQpJIHJlYWQgY29tbWVudHMgb24gb3VyIGRyYWZ0LCB0aGFuayB5b3Ug
Zm9yIHlvdXIgY29tbWVudHMuDQoNCkFuZCBzb21lIHF1ZXN0aW9ucyBoYWQgYWxyZWFkeSBiZWVu
IHJlcGxpZWQgaW4gb3VyIGxhdGVzdCBGQVIgcHJlc2VudGF0aW9uIA0KbWF0ZXJpYWwobm90IGJl
ZW4gcHJlc2VudGVkIGF0IHRoZSBtZWV0aW5nIGJlY2F1c2Ugb2YgaGFyZC1kZWFkbGluZSk6DQoN
Ci0tLS0tLS0tIkRyYWZ0IGlzIGhpZ2hseSBzdWJqZWN0aXZlLiBEYXRhIENlbnRlcnMgYXJlIHVz
aW5nIGV4aXN0aW5nIA0KcHJvdG9jb2xzIHdpdGhvdXQgcHJvYmxlbXMuIg0KV2h5IE9TUEYgYW5k
IG90aGVyIGNvbnZlbnRpb25hbCByb3V0aW5nIG1ldGhvZHMgZG8gbm90IHdvcmsgd2VsbCBpbiBh
IA0KbGFyZ2Utc2NhbGUgbmV0d29yayB3aXRoIHNldmVyYWwgdGhvdXNhbmRzIG9mIHJvdXRlcnM/
DQpBcyBldmVyeW9uZSBrbm93cywgdGhlIE9TUEYgcHJvdG9jb2wgdXNlcyBtdWx0aXBsZSBkYXRh
YmFzZXMsIG1vcmUgDQp0b3BvbG9naWNhbCBleGNoYW5nZSBpbmZvcm1hdGlvbiAoYXMgc2VlbiBp
biB0aGUgZm9sbG93aW5nIGV4YW1wbGUpIGFuZCANCmNvbXBsaWNhdGVkIGFsZ29yaXRobS4gSXQg
cmVxdWlyZXMgcm91dGVycyB0byBjb25zdW1lIG1vcmUgbWVtb3J5IGFuZCBDUFUgDQpwcm9jZXNz
aW5nIGNhcGFiaWxpdHkuIEJ1dCB0aGUgcHJvY2Vzc2luZyByYXRlIG9mIENQVSBvbiB0aGUgcHJv
dG9jb2wgDQptZXNzYWdlIHBlciBzZWNvbmQgaXMgdmVyeSBsaW1pdGVkLiBXaGVuIHRoZSBuZXR3
b3JrIGV4cGFuZHMsIENQVSB3aWxsIA0KcXVpY2tseSBhcHByb2FjaCBpdHMgcHJvY2Vzc2luZyBs
aW1pdHMsIGFuZCBhdCB0aGlzIHRpbWUgT1NQRiBjYW4gbm90IA0KY29udGludWUgdG8gZXhwYW5k
IHRoZSBzY2FsZSBvZiB0aGUgbWFuYWdlbWVudC4gVGhlIFNQRiBhbGdvcml0aG0gaXRzZWxmIA0K
ZG9lcyBub3QgdGhvcm91Z2hseSBzb2x2ZSB0aGVzZSBwcm9ibGVtcy4gDQoNCk9uIHRoZSBjb250
cmFyeSwgRkFSIGRvZXMgbm90IGhhdmUgdGhlIGNvbnZlcmdlbmNlIHRpbWUgZGVsYXkgYW5kIHRo
ZSANCmFkZGl0aW9uYWwgQ1BVIG92ZXJoZWFkcywgd2hpY2ggU1BGIHJlcXVpcmVzLiBCZWNhdXNl
IGluIHRoZSBpbml0aWFsIA0Kc3RhZ2UsIEZBUiBhbHJlYWR5IGtub3dzIHRoZSByZWd1bGFyIGlu
Zm9ybWF0aW9uIG9mIHRoZSB3aG9sZSBuZXR3b3JrIA0KdG9wb2xvZ3kgYW5kIGRvZXMgbm90IG5l
ZWQgdG8gcGVyaW9kaWNhbGx5IGRvIFNQRiBvcGVyYXRpb24uDQoNCk9uZSBvZiB0aGUgZXhhbXBs
ZXMgb2YgIm1vcmUgdG9wb2xvZ2ljYWwgZXhjaGFuZ2UgaW5mb3JtYXRpb24iOg0KSW4gdGhlIE9T
UEYgcHJvdG9jb2wsIExTQSBmbG9vZHMgZXZlcnkgMTgwMCBzZWNvbmRzLiBFc3BlY2lhbGx5IGlu
IHRoZSANCmxhcmdlciBuZXR3b3JrLCB0aGUgb2NjdXBhdGlvbiBvZiBDUFUgYW5kIGJhbmQgYmFu
ZHdpZHRoIHdpbGwgc29vbiByZWFjaCANCnRoZSByb3V0ZXKhr3MgcGVyZm9ybWFuY2UgYm90dGxl
bmVjay4NCkluIG9yZGVyIHRvIHJlZHVjZSB0aGVzZSBhZHZlcnNlIGVmZmVjdHMsIE9TUEYgaW50
cm9kdWNlZCB0aGUgY29uY2VwdCBvZiANCkFyZWEsIHdoaWNoIHN0aWxsIGhhcyBub3Qgc29sdmVk
IHRoZSBwcm9ibGVtIHRob3JvdWdobHkpLiBCeSBkaXZpZGluZyB0aGUgDQpPU1BGIEFyZWEgaW50
byBzZXZlcmFsIGFyZWFzLCB0aGUgcm91dGVycyBpbiB0aGUgc2FtZSBhcmVhIGRvIG5vdCBuZWVk
IHRvIA0Ka25vdyB0aGUgdG9wb2xvZ2ljYWwgZGV0YWlscyBvdXRzaWRlIHRoZWlyIGFyZWEuIChJ
biBjb21wYXJpc29uIHdpdGggRkFSLCANCmFmdGVyICBPU1BGIGludHJvZHVjaW5nIHRoZSBjb25j
ZXB0IG9mIEFyZWEsIHRoZSBlcXVpdmFsZW50IHBhdGhzIGNhbm5vdCANCmJlIHNlbGVjdGVkIGlu
IHRoZSB3aG9sZSBuZXR3b3JrIHNjb3BlKSANCg0KIE9TUEYgY2FuIGFjaGlldmUgdGhlIGZvbGxv
d2luZyByZXN1bHRzIGJ5IEFyZWEgOg0KMSkgUm91dGVycyBvbmx5IG5lZWQgdG8gbWFpbnRhaW4g
dGhlIHNhbWUgbGluayBzdGF0ZSBkYXRhYmFzZXMgYXMgb3RoZXIgDQpyb3V0ZXJzIHdpdGhpbiB0
aGUgc2FtZSBBcmVhLCB3aXRob3V0IHRoZSBuZWNlc3NpdHkgb2YgbWFpbnRhaW5pbmcgdGhlIA0K
c2FtZSBsaW5rIHN0YXRlIGRhdGFiYXNlIGFzIGFsbCByb3V0ZXJzIGluIHRoZSB3aG9sZSBPU1BG
IGRvbWFpbi4gDQoyKSBUaGUgcmVkdWN0aW9uIG9mIHRoZSBsaW5rIHN0YXRlIGRhdGFiYXNlcyBt
ZWFucyBkZWFsaW5nIHdpdGggcmVsYXRpdmVseSANCmZld2VyIExTQSwgd2hpY2ggcmVkdWNlcyB0
aGUgQ1BVIGNvbnN1bXB0aW9uIG9mIHJvdXRlcnM7DQozKSBUaGUgbGFyZ2UgbnVtYmVyIG9mIExT
QXMgZmxvb2Qgb25seSB3aXRoaW4gdGhlIHNhbWUgQXJlYS4NCkJ1dCwgaXRzIG5lZ2F0aXZlIGVm
ZmVjdCBpcyB0aGF0IHRoZSBzbWFsbGVyIG51bWJlciBvZiByb3V0ZXJzIHdoaWNoIGNhbiANCmJl
IG1hbmFnZWQgaW4gZWFjaCBPU1BGIGFyZWEuDQpPbiB0aGUgY29udHJhcnksIGJlY2F1c2UgRkFS
IGRvZXMgbm90IGhhdmUgdGhlIGFib3ZlIGRpc2FkdmFudGFnZXMsIEZBUiANCmNhbiBhbHNvIG1h
bmFnZSBsYXJnZS1zY2FsZSBuZXR3b3JrIGV2ZW4gd2l0aG91dCBkaXZpZGluZyBBcmVhcy4NCg0K
VGhlIGFnaW5nIHRpbWUgb2YgT1NQRiBpcyBzZXQgaW4gb3JkZXIgdG8gYWRhcHQgdG8gcm91dGlu
ZyB0cmFuc2Zvcm1hdGlvbiANCmFuZCBwcm90b2NvbCBtZXNzYWdlIGV4Y2hhbmdlIGhhcHBlbmVk
IGZyZXF1ZW50bHkgaW4gdGhlIGlycmVndWxhciANCnRvcG9sb2d5LiBJdHMgbmVnYXRpdmUgZWZm
ZWN0IGlzOiANCndoZW4gdGhlIG5ldHdvcmsgZG9lcyBub3QgY2hhbmdlLCB0aGUgTFNBIG5lZWRz
IHRvIGJlIHJlZnJlc2hlZCBldmVyeSAxODAwIA0Kc2Vjb25kcyB0byByZXNldCB0aGUgYWdpbmcg
dGltZS4gSW4gdGhlIHJlZ3VsYXIgdG9wb2xvZ3ksIGFzIHRoZSByb3V0aW5ncyANCmFyZSBmaXhl
ZCwgaXQgZG9lcyBub3QgbmVlZCB0aGUgY29tcGxleCBwcm90b2NvbCBtZXNzYWdlIGV4Y2hhbmdl
IGFuZCANCmFnaW5nIHJ1bGVzIHRvIHJlZmxlY3QgdGhlIHJvdXRpbmcgY2hhbmdlcywgYXMgbG9u
ZyBhcyBMRkEgbWVjaGFuaXNtIGluIA0KdGhlIEZBUiBpcyBlbm91Z2guDQoNClRoZXJlZm9yZSwg
aW4gRkFSLCB3ZSBjYW4gb21pdCBtYW55IHVubmVjZXNzYXJ5IHByb2Nlc3NpbmcgYW5kIHRoZSBw
YWNrZXQgDQpleGNoYW5nZS4gVGhlIGJlbmVmaXRzIGFyZSBmYXN0IGNvbnZlcmdlbmNlIHNwZWVk
IGFuZCBtdWNoIGxhcmdlciBuZXR3b3JrIA0Kc2NhbGUgdGhhbiBvdGhlciBkeW5hbWljIHJvdXRp
bmcgcHJvdG9jb2wuDQpOb3cgdGhlcmUgYXJlIHNvbWUgc3VjY2Vzc2Z1bCBpbXBsZW1lbnRhdGlv
bnMgb2Ygc2ltcGxpZmllZCByb3V0aW5ncyBpbiANCnRoZSByZWd1bGFyIHRvcG9sb2d5IGluIHRo
ZSBIUEMgZW52aXJvbm1lbnQuDQpDb25jbHVzaW9uOgtBcyBGQVIgbmVlZHMgZmV3IHJvdXRpbmcg
ZW50cmllcyBhbmQgdGhlIHRvcG9sb2d5IGlzIHJlZ3VsYXIsIA0KdGhlIGRhdGFiYXNlIGRvZXMg
bm90IG5lZWQgdG8gYmUgdXBkYXRlZCByZWd1bGFybHkuIFdpdGhvdXQgdGhlIG5lZWQgZm9yIA0K
YWdpbmcsIHRoZXJlIGlzIG5vIG5lZWQgZm9yIENQVSBhbmQgYmFuZHdpZHRoIG92ZXJoZWFkIGJy
b3VnaHQgYnkgTFNBIA0KZmxvb2QgZXZlcnkgMzAgbWludXRlcywgc28gdGhlIGV4cGFuc2lvbiBv
ZiB0aGUgbmV0d29yayBoYXMgbm8gb2J2aW91cyANCmVmZmVjdCBvbiB0aGUgcGVyZm9ybWFuY2Ug
b2YgRkFSLCB3aGljaCBpcyBjb250cmFyeSB0byBPU1BGLg0KDQotLS0tLS0tLSJOZXR3b3JrIGNv
bnZlcmdlbmNlIGRvZXNuJ3QgZm9sbG93IGxpbmsgc3RhdGUgDQogICAgICAgICAgZHluYW1pY3Mg
LSBGYXN0IHJlcm91dGUgZXhpc3RzLiAiDQoNCkNvbXBhcmlzb24gb2YgY29udmVyZ2VuY2UgdGlt
ZToNClRoZSBzZXR0aW5ncyBvZiBPU1BGIHNwZl9kZWxheSBhbmQgc3BmX2hvbGRfdGltZSBjYW4g
YWZmZWN0IHRoZSBjaGFuZ2Ugb2YgDQpjb252ZXJnZW5jZSB0aW1lLiBUaGUgY29udmVyZ2VuY2Ug
dGltZSBvZiB0aGUgbmV0d29yayB3aXRoIDI0ODAgbm9kZXMgaXMgDQphYm91dCAxNS0yMCBzZWNv
bmRzKGFzIHNlZW4gaW4gdGhlIGZvbGxvd2luZyBwYWdlcyk7IHdoaWxlIHRoZSBGQVIgZG9lcyAN
Cm5vdCBuZWVkIHRvIGNhbGN1bGF0ZSB0aGUgU0ZQLCBzbyB0aGVyZSBpcyBubyBzdWNoIGNvbnZl
cmdlbmNlIHRpbWUuDQpUaGVzZSBpc3N1ZXMgc3RpbGwgZXhpc3QgaW4gcmFwaWQgY29udmVyZ2Vu
Y2UgdGVjaG5vbG9neSBvZiBPU1BGIGFuZCBJU0lTIA0KKHN1Y2ggYXMgSS1TUEYpLiBUaGUgY29u
dmVyZ2VuY2Ugc3BlZWQgYW5kIG5ldHdvcmsgc2NhbGUgY29uc3RyYWludCBlYWNoIA0Kb3RoZXIu
IEZBUiBkb2VzIG5vdCBoYXZlIHRoZSBhYm92ZSBwcm9ibGVtcywgYW5kIHRoZSBjb252ZXJnZW5j
ZSB0aW1lIGlzIA0KYWxtb3N0IG5lZ2xpZ2libGUuCw0KDQpBbmQgdGVzdCBkYXRhIGlzIGJlZW4g
aW5jbHVkZSBpbiBhbm90aGVyIHBwdHggbWF0ZXJpYWwgbmFtZWQgT1NQRiBpbiANCkRDTigyKS5w
cHR4LCB3aGljaCBjYW4gYmUgZG93bmxvYWQgZnJvbSBJRVRGLg0KDQpMb29raW5nIGZvcndhcmQg
dG8gZnVydGhlciBkaXNjdXNzaW9uLg0KDQpCZXN0Lg0KDQpSaWNoYXJkIEJpbiBMaXUNCg0K
--=_alternative 001C368C48257CD9_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkdyZWV0aW5nIGFsbDo8L2ZvbnQ+
DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkkgcmVhZCBjb21tZW50
cyBvbiBvdXIgZHJhZnQsIHRoYW5rDQp5b3UgZm9yIHlvdXIgY29tbWVudHMuPC9mb250Pg0KPGJy
Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5BbmQgc29tZSBxdWVzdGlvbnMg
aGFkIGFscmVhZHkgYmVlbg0KcmVwbGllZCBpbiBvdXIgbGF0ZXN0IEZBUiBwcmVzZW50YXRpb24g
bWF0ZXJpYWwobm90IGJlZW4gcHJlc2VudGVkIGF0IHRoZQ0KbWVldGluZyBiZWNhdXNlIG9mIGhh
cmQtZGVhZGxpbmUpOjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1z
ZXJpZiI+LS0tLS0tLS0mcXVvdDtEcmFmdCBpcyBoaWdobHkgc3ViamVjdGl2ZS4NCkRhdGEgQ2Vu
dGVycyBhcmUgdXNpbmcgZXhpc3RpbmcgcHJvdG9jb2xzIHdpdGhvdXQgcHJvYmxlbXMuJnF1b3Q7
PC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5XaHkgT1NQRiBhbmQg
b3RoZXIgY29udmVudGlvbmFsIHJvdXRpbmcNCm1ldGhvZHMgZG8gbm90IHdvcmsgd2VsbCBpbiBh
IGxhcmdlLXNjYWxlIG5ldHdvcmsgd2l0aCBzZXZlcmFsIHRob3VzYW5kcw0Kb2Ygcm91dGVycz88
L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkFzIGV2ZXJ5b25lIGtu
b3dzLCB0aGUgT1NQRiBwcm90b2NvbA0KdXNlcyBtdWx0aXBsZSBkYXRhYmFzZXMsIG1vcmUgdG9w
b2xvZ2ljYWwgZXhjaGFuZ2UgaW5mb3JtYXRpb24gKGFzIHNlZW4NCmluIHRoZSBmb2xsb3dpbmcg
ZXhhbXBsZSkgYW5kIGNvbXBsaWNhdGVkIGFsZ29yaXRobS4gSXQgcmVxdWlyZXMgcm91dGVycw0K
dG8gY29uc3VtZSBtb3JlIG1lbW9yeSBhbmQgQ1BVIHByb2Nlc3NpbmcgY2FwYWJpbGl0eS4gQnV0
IHRoZSBwcm9jZXNzaW5nDQpyYXRlIG9mIENQVSBvbiB0aGUgcHJvdG9jb2wgbWVzc2FnZSBwZXIg
c2Vjb25kIGlzIHZlcnkgbGltaXRlZC4gV2hlbiB0aGUNCm5ldHdvcmsgZXhwYW5kcywgQ1BVIHdp
bGwgcXVpY2tseSBhcHByb2FjaCBpdHMgcHJvY2Vzc2luZyBsaW1pdHMsIGFuZCBhdA0KdGhpcyB0
aW1lIE9TUEYgY2FuIG5vdCBjb250aW51ZSB0byBleHBhbmQgdGhlIHNjYWxlIG9mIHRoZSBtYW5h
Z2VtZW50Lg0KVGhlIFNQRiBhbGdvcml0aG0gaXRzZWxmIGRvZXMgbm90IHRob3JvdWdobHkgc29s
dmUgdGhlc2UgcHJvYmxlbXMuIDwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0i
c2Fucy1zZXJpZiI+T24gdGhlIGNvbnRyYXJ5LCBGQVIgZG9lcyBub3QgaGF2ZSB0aGUNCmNvbnZl
cmdlbmNlIHRpbWUgZGVsYXkgYW5kIHRoZSBhZGRpdGlvbmFsIENQVSBvdmVyaGVhZHMsIHdoaWNo
IFNQRiByZXF1aXJlcy4NCkJlY2F1c2UgaW4gdGhlIGluaXRpYWwgc3RhZ2UsIEZBUiBhbHJlYWR5
IGtub3dzIHRoZSByZWd1bGFyIGluZm9ybWF0aW9uDQpvZiB0aGUgd2hvbGUgbmV0d29yayB0b3Bv
bG9neSBhbmQgZG9lcyBub3QgbmVlZCB0byBwZXJpb2RpY2FsbHkgZG8gU1BGDQpvcGVyYXRpb24u
PC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5PbmUgb2Yg
dGhlIGV4YW1wbGVzIG9mICZxdW90O21vcmUgdG9wb2xvZ2ljYWwNCmV4Y2hhbmdlIGluZm9ybWF0
aW9uJnF1b3Q7OjwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+SW4g
dGhlIE9TUEYgcHJvdG9jb2wsIExTQSBmbG9vZHMgZXZlcnkNCjE4MDAgc2Vjb25kcy4gRXNwZWNp
YWxseSBpbiB0aGUgbGFyZ2VyIG5ldHdvcmssIHRoZSBvY2N1cGF0aW9uIG9mIENQVSBhbmQNCmJh
bmQgYmFuZHdpZHRoIHdpbGwgc29vbiByZWFjaCB0aGUgcm91dGVyoa9zIHBlcmZvcm1hbmNlIGJv
dHRsZW5lY2suPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5JbiBv
cmRlciB0byByZWR1Y2UgdGhlc2UgYWR2ZXJzZSBlZmZlY3RzLA0KT1NQRiBpbnRyb2R1Y2VkIHRo
ZSBjb25jZXB0IG9mIEFyZWEsIHdoaWNoIHN0aWxsIGhhcyBub3Qgc29sdmVkIHRoZSBwcm9ibGVt
DQp0aG9yb3VnaGx5KS4gQnkgZGl2aWRpbmcgdGhlIE9TUEYgQXJlYSBpbnRvIHNldmVyYWwgYXJl
YXMsIHRoZSByb3V0ZXJzDQppbiB0aGUgc2FtZSBhcmVhIGRvIG5vdCBuZWVkIHRvIGtub3cgdGhl
IHRvcG9sb2dpY2FsIGRldGFpbHMgb3V0c2lkZSB0aGVpcg0KYXJlYS4gKEluIGNvbXBhcmlzb24g
d2l0aCBGQVIsIGFmdGVyICZuYnNwO09TUEYgaW50cm9kdWNpbmcgdGhlIGNvbmNlcHQNCm9mIEFy
ZWEsIHRoZSBlcXVpdmFsZW50IHBhdGhzIGNhbm5vdCBiZSBzZWxlY3RlZCBpbiB0aGUgd2hvbGUg
bmV0d29yayBzY29wZSkNCjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fu
cy1zZXJpZiI+Jm5ic3A7T1NQRiBjYW4gYWNoaWV2ZSB0aGUgZm9sbG93aW5nDQpyZXN1bHRzIGJ5
IEFyZWEgOjwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+MSkgUm91
dGVycyBvbmx5IG5lZWQgdG8gbWFpbnRhaW4gdGhlDQpzYW1lIGxpbmsgc3RhdGUgZGF0YWJhc2Vz
IGFzIG90aGVyIHJvdXRlcnMgd2l0aGluIHRoZSBzYW1lIEFyZWEsIHdpdGhvdXQNCnRoZSBuZWNl
c3NpdHkgb2YgbWFpbnRhaW5pbmcgdGhlIHNhbWUgbGluayBzdGF0ZSBkYXRhYmFzZSBhcyBhbGwg
cm91dGVycw0KaW4gdGhlIHdob2xlIE9TUEYgZG9tYWluLiA8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6
ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjIpIFRoZSByZWR1Y3Rpb24gb2YgdGhlIGxpbmsgc3RhdGUg
ZGF0YWJhc2VzDQptZWFucyBkZWFsaW5nIHdpdGggcmVsYXRpdmVseSBmZXdlciBMU0EsIHdoaWNo
IHJlZHVjZXMgdGhlIENQVSBjb25zdW1wdGlvbg0Kb2Ygcm91dGVyczs8L2ZvbnQ+DQo8YnI+PGZv
bnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjMpIFRoZSBsYXJnZSBudW1iZXIgb2YgTFNBcyBm
bG9vZCBvbmx5DQp3aXRoaW4gdGhlIHNhbWUgQXJlYS48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0y
IGZhY2U9InNhbnMtc2VyaWYiPkJ1dCwgaXRzIG5lZ2F0aXZlIGVmZmVjdCBpcyB0aGF0IHRoZQ0K
c21hbGxlciBudW1iZXIgb2Ygcm91dGVycyB3aGljaCBjYW4gYmUgbWFuYWdlZCBpbiBlYWNoIE9T
UEYgYXJlYS48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPk9uIHRo
ZSBjb250cmFyeSwgYmVjYXVzZSBGQVIgZG9lcyBub3QNCmhhdmUgdGhlIGFib3ZlIGRpc2FkdmFu
dGFnZXMsIEZBUiBjYW4gYWxzbyBtYW5hZ2UgbGFyZ2Utc2NhbGUgbmV0d29yayBldmVuDQp3aXRo
b3V0IGRpdmlkaW5nIEFyZWFzLjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0i
c2Fucy1zZXJpZiI+VGhlIGFnaW5nIHRpbWUgb2YgT1NQRiBpcyBzZXQgaW4gb3JkZXINCnRvIGFk
YXB0IHRvIHJvdXRpbmcgdHJhbnNmb3JtYXRpb24gYW5kIHByb3RvY29sIG1lc3NhZ2UgZXhjaGFu
Z2UgaGFwcGVuZWQNCmZyZXF1ZW50bHkgaW4gdGhlIGlycmVndWxhciB0b3BvbG9neS4gSXRzIG5l
Z2F0aXZlIGVmZmVjdCBpczogPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNl
cmlmIj53aGVuIHRoZSBuZXR3b3JrIGRvZXMgbm90IGNoYW5nZSwgdGhlDQpMU0EgbmVlZHMgdG8g
YmUgcmVmcmVzaGVkIGV2ZXJ5IDE4MDAgc2Vjb25kcyB0byByZXNldCB0aGUgYWdpbmcgdGltZS4g
SW4NCnRoZSByZWd1bGFyIHRvcG9sb2d5LCBhcyB0aGUgcm91dGluZ3MgYXJlIGZpeGVkLCBpdCBk
b2VzIG5vdCBuZWVkIHRoZSBjb21wbGV4DQpwcm90b2NvbCBtZXNzYWdlIGV4Y2hhbmdlIGFuZCBh
Z2luZyBydWxlcyB0byByZWZsZWN0IHRoZSByb3V0aW5nIGNoYW5nZXMsDQphcyBsb25nIGFzIExG
QSBtZWNoYW5pc20gaW4gdGhlIEZBUiBpcyBlbm91Z2guPC9mb250Pg0KPGJyPg0KPGJyPjxmb250
IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5UaGVyZWZvcmUsIGluIEZBUiwgd2UgY2FuIG9taXQg
bWFueQ0KdW5uZWNlc3NhcnkgcHJvY2Vzc2luZyBhbmQgdGhlIHBhY2tldCBleGNoYW5nZS4gVGhl
IGJlbmVmaXRzIGFyZSBmYXN0IGNvbnZlcmdlbmNlDQpzcGVlZCBhbmQgbXVjaCBsYXJnZXIgbmV0
d29yayBzY2FsZSB0aGFuIG90aGVyIGR5bmFtaWMgcm91dGluZyBwcm90b2NvbC48L2ZvbnQ+DQo8
YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPk5vdyB0aGVyZSBhcmUgc29tZSBzdWNj
ZXNzZnVsIGltcGxlbWVudGF0aW9ucw0Kb2Ygc2ltcGxpZmllZCByb3V0aW5ncyBpbiB0aGUgcmVn
dWxhciB0b3BvbG9neSBpbiB0aGUgSFBDIGVudmlyb25tZW50LjwvZm9udD4NCjxicj48Zm9udCBz
aXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Q29uY2x1c2lvbjoLQXMgRkFSIG5lZWRzIGZldyByb3V0
aW5nDQplbnRyaWVzIGFuZCB0aGUgdG9wb2xvZ3kgaXMgcmVndWxhciwgdGhlIGRhdGFiYXNlIGRv
ZXMgbm90IG5lZWQgdG8gYmUgdXBkYXRlZA0KcmVndWxhcmx5LiBXaXRob3V0IHRoZSBuZWVkIGZv
ciBhZ2luZywgdGhlcmUgaXMgbm8gbmVlZCBmb3IgQ1BVIGFuZCBiYW5kd2lkdGgNCm92ZXJoZWFk
IGJyb3VnaHQgYnkgTFNBIGZsb29kIGV2ZXJ5IDMwIG1pbnV0ZXMsIHNvIHRoZSBleHBhbnNpb24g
b2YgdGhlDQpuZXR3b3JrIGhhcyBubyBvYnZpb3VzIGVmZmVjdCBvbiB0aGUgcGVyZm9ybWFuY2Ug
b2YgRkFSLCB3aGljaCBpcyBjb250cmFyeQ0KdG8gT1NQRi48L2ZvbnQ+DQo8YnI+DQo8YnI+PGZv
bnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPi0tLS0tLS0tJnF1b3Q7TmV0d29yayBjb252ZXJn
ZW5jZSBkb2Vzbid0DQpmb2xsb3cgbGluayBzdGF0ZSA8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0y
IGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgZHlu
YW1pY3MNCi0gRmFzdCByZXJvdXRlIGV4aXN0cy4gJnF1b3Q7PC9mb250Pg0KPGJyPg0KPGJyPjxm
b250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5Db21wYXJpc29uIG9mIGNvbnZlcmdlbmNlIHRp
bWU6PC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5UaGUgc2V0dGlu
Z3Mgb2YgT1NQRiBzcGZfZGVsYXkgYW5kIHNwZl9ob2xkX3RpbWUNCmNhbiBhZmZlY3QgdGhlIGNo
YW5nZSBvZiBjb252ZXJnZW5jZSB0aW1lLiBUaGUgY29udmVyZ2VuY2UgdGltZSBvZiB0aGUNCm5l
dHdvcmsgd2l0aCAyNDgwIG5vZGVzIGlzIGFib3V0IDE1LTIwIHNlY29uZHMoYXMgc2VlbiBpbiB0
aGUgZm9sbG93aW5nDQpwYWdlcyk7IHdoaWxlIHRoZSBGQVIgZG9lcyBub3QgbmVlZCB0byBjYWxj
dWxhdGUgdGhlIFNGUCwgc28gdGhlcmUgaXMgbm8NCnN1Y2ggY29udmVyZ2VuY2UgdGltZS48L2Zv
bnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlRoZXNlIGlzc3VlcyA8L2Zv
bnQ+PGZvbnQgc2l6ZT0yIGNvbG9yPWJsdWUgZmFjZT0ic2Fucy1zZXJpZiI+PGI+c3RpbGwNCmV4
aXN0PC9iPjwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+IGluIHJhcGlkIGNv
bnZlcmdlbmNlIHRlY2hub2xvZ3kNCm9mIE9TUEYgYW5kIElTSVMgKHN1Y2ggYXMgSS1TUEYpLiBU
aGUgY29udmVyZ2VuY2Ugc3BlZWQgYW5kIG5ldHdvcmsgc2NhbGUNCmNvbnN0cmFpbnQgZWFjaCBv
dGhlci4gRkFSIGRvZXMgbm90IGhhdmUgdGhlIGFib3ZlIHByb2JsZW1zLCBhbmQgdGhlIGNvbnZl
cmdlbmNlDQp0aW1lIGlzIGFsbW9zdCBuZWdsaWdpYmxlLgs8L2ZvbnQ+DQo8YnI+DQo8YnI+PGZv
bnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkFuZCB0ZXN0IGRhdGEgaXMgYmVlbiBpbmNsdWRl
IGluIGFub3RoZXINCnBwdHggbWF0ZXJpYWwgbmFtZWQgT1NQRiBpbiBEQ04oMikucHB0eCwgd2hp
Y2ggY2FuIGJlIGRvd25sb2FkIGZyb20gSUVURi48L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6
ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkxvb2tpbmcgZm9yd2FyZCB0byBmdXJ0aGVyIGRpc2N1c3Np
b24uPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5CZXN0
LjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+UmljaGFy
ZCBCaW4gTGl1PC9mb250Pg0KPGJyPg0K
--=_alternative 001C368C48257CD9_=--


From nobody Wed May 14 23:41:26 2014
Return-Path: <ppsenak@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 598401A03E3 for <rtgwg@ietfa.amsl.com>; Wed, 14 May 2014 23:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.952
X-Spam-Level: 
X-Spam-Status: No, score=-8.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_52=0.6, J_CHICKENPOX_72=0.6, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aXgTBbFSx0ND for <rtgwg@ietfa.amsl.com>; Wed, 14 May 2014 23:41:21 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32CE41A03DC for <rtgwg@ietf.org>; Wed, 14 May 2014 23:41:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5632; q=dns/txt; s=iport; t=1400136075; x=1401345675; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=LTk2xApNL5pGeZe0Fgmuhc/U22gDBh8RIbk1LD9V29I=; b=UdC14DVpS4ZC2/0vTRbii3NXslp6OFRY8ZaOVc2Ul5dKegkmxWba1dOv cqTrgDmpGXOo3C6QpwxCrzUymAX6fWIAnA9vxsClblZ1SYvPcg0LCEtsG ajFBZfoy3CNc4K+LWb9htc9HK6QPivBbibbIgMhvz/EMBknqs/Wh3GY9E g=;
X-IronPort-AV: E=Sophos;i="4.97,1057,1389744000"; d="scan'208";a="49863149"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 15 May 2014 06:41:14 +0000
Received: from [10.55.51.199] (ams-ppsenak-8716.cisco.com [10.55.51.199]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s4F6fCb1017922; Thu, 15 May 2014 06:41:12 GMT
Message-ID: <53746188.7050902@cisco.com>
Date: Thu, 15 May 2014 08:41:12 +0200
From: Peter Psenak <ppsenak@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: liu.bin21@zte.com.cn, Hannes Gredler <hannes@juniper.net>, "Alvaro Retana (aretana)" <aretana@cisco.com>
Subject: Re: Reply to comments -- Comparison between FAR and OSPF
References: <OF7B611F3A.6F9BF7DF-ON48257CD9.0018F932-48257CD9.001C368E@zte.com.cn>
In-Reply-To: <OF7B611F3A.6F9BF7DF-ON48257CD9.0018F932-48257CD9.001C368E@zte.com.cn>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/OylSBqXtT_1p3-ZG7t3H_vQlAAQ
Cc: adrian@olddog.co.uk, ytsun <ytsun@bjtu.edu.cn>, rtgwg-chairs@tools.ietf.org, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 May 2014 06:41:23 -0000

Liu,

the arguments you use against existing IGPs would be valid 20 years ago, 
but not today. First, links have high bandwidth, CPUs are fast and any 
serious IGP implementation has addressed the bottlenecks you are talking 
about. These days IGPs can support thousands of nodes in an area without 
any problem, and converge sub-second, with precomputed backups, even 
withing few tens of miliseconds. There are real deployments that clearly 
prove it, it's not an academic statement. Even the periodic flooding can 
be avoided completely using RFC 4136.

regards,
Peter


On 5/15/14 07:08 , liu.bin21@zte.com.cn wrote:
>
> Greeting all:
>
> I read comments on our draft, thank you for your comments.
>
> And some questions had already been replied in our latest FAR
> presentation material(not been presented at the meeting because of
> hard-deadline):
>
> --------"Draft is highly subjective. Data Centers are using existing
> protocols without problems."
> Why OSPF and other conventional routing methods do not work well in a
> large-scale network with several thousands of routers?
> As everyone knows, the OSPF protocol uses multiple databases, more
> topological exchange information (as seen in the following example) and
> complicated algorithm. It requires routers to consume more memory and
> CPU processing capability. But the processing rate of CPU on the
> protocol message per second is very limited. When the network expands,
> CPU will quickly approach its processing limits, and at this time OSPF
> can not continue to expand the scale of the management. The SPF
> algorithm itself does not thoroughly solve these problems.
>
> On the contrary, FAR does not have the convergence time delay and the
> additional CPU overheads, which SPF requires. Because in the initial
> stage, FAR already knows the regular information of the whole network
> topology and does not need to periodically do SPF operation.
>
> One of the examples of "more topological exchange information":
> In the OSPF protocol, LSA floods every 1800 seconds. Especially in the
> larger network, the occupation of CPU and band bandwidth will soon reach
> the router’s performance bottleneck.
> In order to reduce these adverse effects, OSPF introduced the concept of
> Area, which still has not solved the problem thoroughly). By dividing
> the OSPF Area into several areas, the routers in the same area do not
> need to know the topological details outside their area. (In comparison
> with FAR, after  OSPF introducing the concept of Area, the equivalent
> paths cannot be selected in the whole network scope)
>
>   OSPF can achieve the following results by Area :
> 1) Routers only need to maintain the same link state databases as other
> routers within the same Area, without the necessity of maintaining the
> same link state database as all routers in the whole OSPF domain.
> 2) The reduction of the link state databases means dealing with
> relatively fewer LSA, which reduces the CPU consumption of routers;
> 3) The large number of LSAs flood only within the same Area.
> But, its negative effect is that the smaller number of routers which can
> be managed in each OSPF area.
> On the contrary, because FAR does not have the above disadvantages, FAR
> can also manage large-scale network even without dividing Areas.
>
> The aging time of OSPF is set in order to adapt to routing
> transformation and protocol message exchange happened frequently in the
> irregular topology. Its negative effect is:
> when the network does not change, the LSA needs to be refreshed every
> 1800 seconds to reset the aging time. In the regular topology, as the
> routings are fixed, it does not need the complex protocol message
> exchange and aging rules to reflect the routing changes, as long as LFA
> mechanism in the FAR is enough.
>
> Therefore, in FAR, we can omit many unnecessary processing and the
> packet exchange. The benefits are fast convergence speed and much larger
> network scale than other dynamic routing protocol.
> Now there are some successful implementations of simplified routings in
> the regular topology in the HPC environment.
> Conclusion:As FAR needs few routing entries and the topology is
> regular, the database does not need to be updated regularly. Without the
> need for aging, there is no need for CPU and bandwidth overhead brought
> by LSA flood every 30 minutes, so the expansion of the network has no
> obvious effect on the performance of FAR, which is contrary to OSPF.
>
> --------"Network convergence doesn't follow link state
>            dynamics - Fast reroute exists. "
>
> Comparison of convergence time:
> The settings of OSPF spf_delay and spf_hold_time can affect the change
> of convergence time. The convergence time of the network with 2480 nodes
> is about 15-20 seconds(as seen in the following pages); while the FAR
> does not need to calculate the SFP, so there is no such convergence time.
> These issues *still exist*in rapid convergence technology of OSPF and
> ISIS (such as I-SPF). The convergence speed and network scale constraint
> each other. FAR does not have the above problems, and the convergence
> time is almost negligible.
>
> And test data is been include in another pptx material named OSPF in
> DCN(2).pptx, which can be download from IETF.
>
> Looking forward to further discussion.
>
> Best.
>
> Richard Bin Liu
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>


From nobody Thu May 15 08:17:03 2014
Return-Path: <bruno.decraene@orange.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94E661A00C9 for <rtgwg@ietfa.amsl.com>; Thu, 15 May 2014 08:17:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xq-I3MsokzsK for <rtgwg@ietfa.amsl.com>; Thu, 15 May 2014 08:16:57 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D69EF1A00CB for <rtgwg@ietf.org>; Thu, 15 May 2014 08:16:56 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id 771502DC182; Thu, 15 May 2014 17:16:48 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 593C7238055; Thu, 15 May 2014 17:16:48 +0200 (CEST)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0181.006; Thu, 15 May 2014 17:16:48 +0200
From: <bruno.decraene@orange.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Subject: RE: WGLC for draft-ietf-rtgwg-mofrr
Thread-Topic: WGLC for draft-ietf-rtgwg-mofrr
Thread-Index: AQHPPz7K8hNpTHe0LUm1JLi/CDk63Jr1kHaAgEySLNA=
Date: Thu, 15 May 2014 15:16:47 +0000
Message-ID: <11338_1400167008_5374DA60_11338_18583_1_53C29892C857584299CBF5D05346208A0714A838@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <CF47FF3B.5093A%aretana@cisco.com> <CF59D08A.52ABB%aretana@cisco.com>
In-Reply-To: <CF59D08A.52ABB%aretana@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.5.13.75120
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/aBWOhP9EDl4iF8djmGhea4a1PBI
Cc: "draft-ietf-rtgwg-mofrr@tools.ietf.org" <draft-ietf-rtgwg-mofrr@tools.ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 May 2014 15:17:01 -0000

Hi Alvaro,

Many thanks for your in depth review of the draft. It has been really helpf=
ul to improve the document.

We have just published v04 which should address your comments.

Please find below the answer to each of your comments.

Ice, Bruno
---

> However, I think that the organization can be improved to avoid duplicati=
on of some information and to clarify when/where does MoFRR work better (or=
 not).  Please see below for more comments.

Agreed.
Section "5. Detecting Failures" has been moved to section 4, just after the=
 determination of the backup upstream (section 3 Upstream Multicast Hop Sel=
ection). This is to group the specification text together.

> Major issues:

> 1.        Basic Overview.  You wrote: "The two divergent paths SHOULD nev=
er merge upstream".  Do you really want/need to use "SHOULD" (as in rfc2119=
) here?  While I don't think anyone can argue that it is a good network des=
ign practice, there is no way (at least not mentioned in the draft) for MoF=
RR to verify that the paths are divergent (or not).  Also, in the "Topologi=
es for MoFRR" section you write that "MoFRR works best in topologies illust=
rated in the figure below"..but doesn't mandate them.   All this is to say =
that I think that the "SHOULD" in this section should just say "should".

Agreed that "SHOULD" is not required.

OLD: The two divergent paths SHOULD never merge upstream
NEW: In order maximize robustness against any failure, the two paths should=
 be as diverse as possible. Ideally, they should not merge upstream.

> 2.        Topologies for MoFRR.  Which topologies are not well suited for=
 MoFRR.  A short discussion would help a lot.

Agreed. A section "MoFRR applicability" has been added which discuss the ap=
plicability of MoFRR depending on the topology.
Author Response: The text of this section was mostly already present in the=
 draft, but used to be split in multiple sections, which I agree was no opt=
imal for the reader.

>3.         Security Considerations.  I know that the operation of PIM/mLDP=
 is not changed on the wire, but it is changed locally resulting in a redun=
dant stream.  Not all topologies will result in merging the secondary tree =
with the primary at a relatively close point in the topology (as in the exa=
mples)..and not all deployments will have the ability to plan/predict the u=
tilization.  All this could result (in some topologies/deployments) in the =
inability to offer other services (because of congestion, for example).  Do=
 you consider this a security issue?    A related discussion would help bet=
ter understand the effect.  Note that this point is related to #2 above, an=
d may be addressed by clearly talking about the topologies and potential ef=
fects.

Author Response: I don't think this is a security consideration. MoFRR is a=
 service that is applied to the network by the operator, and which links ca=
rry traffic is depending on where receivers are joining from. The fact that=
 you don't know in which parts of the network multicast receivers will join=
 is not considered a security concern either, right?


>4.         Consider Reordering the Sections.  When reading through the doc=
ument I felt at times that information maybe should have been presented..an=
d in some cases the information seemed to be disjoint.  For example,=20=20
> o         Section 3 ('Upstream Multicast Hop Selection') presents the bas=
ic selection (no change from PIM/mLDP), but it doesn't explain what to real=
ly do for MoFRR (which is explained in sections 6 ('ECMP-mode MoFRR') and 7=
 ('Non-ECMP-mode MoFRR')).
> o         Parts of Section 4.1 talk about deployment considerations (why =
is it easy to apply MoFRR to the topology), but that information is repeate=
d in section 8 ('Keep It Simple Principle') and complemented by sections 9 =
('Capacity Planning for MoFRR') and 5 ('Detecting Failures').  I would sugg=
est consolidating these operations/deployment oriented sections into a sing=
le one.

Author Response: Agreed. The sections have been reorganized as follow:

- Section 2 "Basic Overview" provides the overview of the solution, includi=
ng pointers to the sections providing the details
- Section 3 "Determination of the secondary UMH" defines how the alternate =
UMH is found. In the general case and with a focus on ECMP and ECMP cases.
- Section 4 "Upstream Multicast Hop Selection" defines which UMH should be =
used for forwarding.
- Section 5 "Detecting failures" discusses multiple options to detect the f=
ailure (either locally or end to end)
- Section 6 "MoFRR applicability" discusses the applicability of MoFRR depe=
nding on the network topology.

So sections 2 to 4 are intended to be normative, while sections 5 to 6 are =
more informational.


> Minor issues:

>1.         Introduction. "Multiple techniques have been developed and depl=
oyed .."  Which ones?  Can you provide a (short) discussion as to why MoFRR=
 is better/addresses issues not addressed before/etc.?

Author Response: Reworked the text, the reasons its better is explained lat=
er on in the text, i.e. no changes to the protocols.

>2.         Introduction.  "With MoFRR, in many cases, multicast routing pr=
otocols don't necessarily have to depend on or have to wait on unicast rout=
ing protocols to detect network failures."   Which are those cases?  Maybe =
a pointer to the 'Failure Detection' section might be enough.
Author Response: Done.

>3.         Terminology.  Please add "merge point" to the list.
Author Response: Done.

>4.         Terminology.  You defined some acronyms, but not all.  I'm thin=
king that you should either expand them all in this section or just be clea=
r about them (specifically the ones that have a definition and are not just=
 an expansion) where they are first introduced.

Author Response: Updated the Terminology section.

> 5.        Section 4.1.  You wrote "PEs not enabled for MoFRR do not see a=
ny change or degradation."  I'm sure you meant that the PEs where MoFRR is =
not enabled won't see any effect resulting from enabling it in other PEs, r=
ight?  It sounds as if you meant that the PEs without MoFRR won't see a dif=
ference in performance of the multicast stream/convergence characteristics,=
 etc. when compared to the ones with it..which would make me think, then wh=
y use MoFRR?  ;-)   Please clarify.

Author Response: I removed that sentence as the previous one was enough ("E=
ach PE device can be enabled one by one".)

> 6.        Section 4.1. "End-to-end failure detection and recovery.."  A p=
ointer to the 'Detecting Failures' section would be nice.

Author Response: Agreed. Done

> 7.        Section 4.1. "(the backup path crosses links/nodes which alread=
y carry the primary/normal tree and hence twice as much capacity is require=
d)"  Are you talking about the "conventional FRR mechanisms" or about MoFRR=
?  In either case it sounds like you're contradicting yourself.

This sentence was talking about conventional FRR. The sentence has been cha=
nged to make this clearer: "This is different from conventional FRR mechani=
sms which often duplicate the capacity requirements when the backup path cr=
osses links/nodes which already carry the primary/normal tree and hence twi=
ce as much capacity is required."

That been clarified, I'm not seeing the contradiction. Could you please poi=
nt it out?

> 8.        Detecting Failures.  In a couple of places you mention that "50=
msec switchover is possible".  Even though I can see how you're making that=
 assumption (link down detection time, for example), the part about knowing=
 the minimum packet rate doesn't make much sense to me because that rate ma=
y be larger than 50ms.  Am I missing something?  [I know that the general a=
pplication is IPTV, see below, but I'm assuming the application is not limi=
ted to that.]

Author Response: Agreed.

For the first option (local link failure detection), a reference to unicast=
 FRR performance "50 ms" has been added:
OLD: 50msec switchover is possible.
NEW: Just like for unicast fast reroute, 50msec switchover is possible.

Author Response: For the third option (detecting the absence of the multica=
st stream), the dependency on the multicast rate has been added:
OLD: 50msec switchover may be possible.
NEW: 50msec switchover may be possible for high rate stream (e.g. IP TV) bu=
t in general the delay is dependant on the rate of the multicast stream.

> 9.        ECMP-mode MoFRR.  "If more than two ECMP paths exist.."  In thi=
s paragraph you suggest that other aspects may be taken into account (such =
as looking into the IGP topology), but you're not specific.  I realize that=
 the operation doesn't require interoperability..but it would be nice to ei=
ther specify some options or just leave it at "the decision on how to selec=
t a secondary UHM is left to a local decision".  The later would be my pref=
erence.

Author Response: Updated.

> 10.      Non-ECMP-mode MoFRR. "Router X MUST stop joining the seconday pa=
th if the following as described below occurs. . .In order to prevent contr=
ol-plane loops a router MUST never setup a secondary path to a LFA UMH if t=
his UMH is the only member in the OIF list."  I think there are really two =
conditions here (not just one as the text seems to indicate):=20
> o         The secondary path shouldn't be established if the LFA is the o=
nly member of the OIF list.
> o         The secondary path is established through an LFA (because there=
 are multiple members in the OIF list), but later a change in the network r=
esults in the secondary UMH being alone in the OIF list.

Author Response: Indeed. However, the first point seems implicit: a router =
will not compute an alternate if there is no nominal. We have rephrased to =
"In order to prevent control-plane loops a router MUST stop joining the sec=
ondary UMH if this UMH is the only member in the OIF list." Do you think th=
is is clear enough?


>11.       Keep It Simple.  This section seems to answer my point #8 above.=
  You should consider merging the two.

Author Response: That section has been removed and the text moved in other =
section (cf the above point about section reorganisation)

> Nits:

>1.         Abstract.  You mention "IPTV deployments", but isn't it any str=
eaming media application over IP?  Maybe just splitting hairs..but a good i=
ntro/abstract is important.

Author Response: Not sure what you mean here.

> 2.        Basic Overview. s/'upstream paths at the time'/'upstream paths =
at a time'

Author Response: Done.

> 3.        Basic Overview.  There are a couple of places in this section (=
when talking about redundancy and the selection of the UMH) that refer to o=
ther places in the draft.  It would be nice if a reference to the specific =
section was included.

Author Response: Agreed. Done. One additional reference has also been added=
, so that this overview can be read as an overview introducing and pointing=
 to the different section of the document.

> 4.        Section 3.2. s/'independent on the interface'/'independent of t=
he interface'

Author Response: Done.

> 5.        Topologies for MoFRR.  "MoFRR works best in topologies illustra=
ted in the figure below."  I think you meant "figures".

Author Response: Done.

> 6.        Dual-Plane Topology. s/its its/its

Author Response: Done.

>7.         Section 4.1. "..described later in the document.."  Pointer to =
the section.

Author Response: Done.

> 8.        ECMP-mode MoFRR. s/same as if MoFRR extension/same as if the Mo=
FRR extension

Author Response: Done.

> 9.        Non-ECMP-mode MoFRR.  s/seconday/secondary

Author Response: Done.

> 10.      s/draft-ietf-rtgwg-lfa-applicability/rfc6571

Author Response: Done.

> 11.      Capacity Planning. s/can still benefit from MoFRR benefits/can s=
till benefit from MoFRR.

Author Response: Done.

>12.       References to MPLS-OAM, BFD, MVPN..

Author Response: Done

> 13.      You're missing the 'IANA Considerations' section.

Author Response: Done (no IANA request)

> 14.      References:  rfc5036 is not referenced anywhere.

Author Response: Done.


> -----Original Message-----
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Alvaro Retana
> (aretana)
> Sent: Thursday, March 27, 2014 9:57 PM
> To: draft-ietf-rtgwg-mofrr@tools.ietf.org
> Cc: rtgwg@ietf.org
> Subject: Re: WGLC for draft-ietf-rtgwg-mofrr
>=20
> On 3/14/14 12:35 AM, "Alvaro Retana (aretana)" <aretana@cisco.com>
> wrote:
>=20
> [WG Chair hat off.]
>=20
> Hi!
>=20
> Please provide specific feedback as to why you support (or not) the
> advancement of this draft. =A0Please avoid "+1"-type responses.
>=20
> I support the publication of this draft. =A0The content is valuable, ther=
e are a
> few implementations, etc.
>=20
> However, I think that the organization can be improved to avoid duplicati=
on
> of some information and to clarify when/where does MoFRR work better (or
> not). =A0Please see below for more comments.
>=20
> Thanks!
>=20
> Alvaro.
>=20
>=20
>=20
> Major issues:
> 1. Basic Overview. =A0You wrote: "The two divergent paths SHOULD never
> merge=A0upstream". =A0Do you really want/need to use "SHOULD" (as in rfc2=
119)
> here? =A0While I don't think anyone can argue that it is a good network d=
esign
> practice, there is no way (at least not mentioned in the draft) for MoFRR=
 to
> verify that the paths are divergent (or not). =A0Also, in the "Topologies=
 for
> MoFRR" section you write that "MoFRR works best in topologies illustrated=
 in
> the figure below"..but doesn't mandate them. =A0 All this is to say that=
=A0I think
> that the "SHOULD" in this section should just say "should".
> 2. Topologies for MoFRR. =A0Which topologies are not well suited for MoFR=
R. =A0A
> short discussion would help a lot.
> 3. Security Considerations. =A0I know that the operation of PIM/mLDP is n=
ot
> changed on the wire, but it is changed locally resulting in a redundant
> stream. =A0Not all topologies will result in merging the secondary tree w=
ith the
> primary at a relatively close point in the topology (as in the examples).=
.and
> not all deployments will have the ability to plan/predict the utilization=
. =A0All this
> could result (in some topologies/deployments) in the inability to offer o=
ther
> services (because of congestion, for example). =A0Do you consider this a
> security issue? =A0 =A0A related discussion would help better understand =
the
> effect. =A0Note that this point is related to #2 above, and may be addres=
sed by
> clearly talking about the topologies and potential effects.
> 4. Consider Reordering the Sections. =A0When reading through the document=
 I
> felt at times that information maybe should have been presented..and in
> some cases the information seemed to be disjoint. =A0For example, o Secti=
on 3
> ('Upstream Multicast Hop Selection') presents the basic selection (no cha=
nge
> from PIM/mLDP), but it doesn't explain what to really do for MoFRR (which=
 is
> explained in sections 6 ('ECMP-mode MoFRR') and 7 ('Non-ECMP-mode
> MoFRR')).
> o Parts of Section 4.1 talk about deployment considerations (why is it ea=
sy to
> apply MoFRR to the topology), but that information is repeated in section=
 8
> ('Keep It Simple Principle') and complemented by sections 9 ('Capacity
> Planning for MoFRR') and 5 ('Detecting Failures'). =A0I would suggest
> consolidating these operations/deployment oriented sections into a single
> one.
>=20
> Minor issues:
> 1. Introduction. "Multiple techniques have been developed and deployed
> .." =A0Which ones? =A0Can you provide a (short) discussion as to why MoFR=
R is
> better/addresses issues not addressed before/etc.?
> 2. Introduction. =A0"With MoFRR, in many cases,=A0multicast routing proto=
cols
> don't necessarily have to depend on or=A0have to wait on unicast routing
> protocols to detect network failures." =A0 Which are those cases? =A0Mayb=
e a
> pointer to the 'Failure Detection' section might be=A0enough.
> 3. Terminology. =A0Please add "merge point" to the list.
> 4. Terminology. =A0You defined some acronyms, but not all. =A0I'm thinkin=
g that
> you should either expand them all in this section or just be clear about =
them
> (specifically the ones that have a definition and are not just an expansi=
on)
> where they are first introduced.
> 5. Section 4.1. =A0You wrote "PEs not enabled for MoFRR do not see any=A0=
change
> or degradation." =A0I'm sure you meant that the=A0PEs where MoFRR is not
> enabled won't see any effect resulting from enabling it in other=A0PEs, r=
ight? =A0It
> sounds as if you=A0meant=A0that the=A0PEs without MoFRR won't see a diffe=
rence in
> performance of the multicast stream/convergence characteristics, etc. when
> compared to the ones with it..which would make me think, then why use
> MoFRR? =A0;-) =A0 Please clarify.
> 6. Section 4.1. "End-to-end failure detection and recovery.." =A0A pointe=
r to the
> 'Detecting Failures' section would be nice.
> 7. Section 4.1. "(the backup path=A0crosses links/nodes which already car=
ry the
> primary/normal tree=A0and hence twice as much capacity is required)" =A0A=
re you
> talking about the "conventional FRR mechanisms" or about MoFRR? =A0In eit=
her
> case it sounds like you're contradicting yourself.
> 8. Detecting Failures. =A0In a couple of places you mention that "50msec
> switchover is possible". =A0Even though I can see how you're making that
> assumption (link down detection time, for example), the part about knowing
> the minimum packet rate doesn't make much sense to me because that rate
> may be larger than 50ms. =A0Am I missing something? =A0[I know that the
> general=A0application=A0is IPTV, see below, but I'm assuming the=A0applic=
ation=A0is not
> limited to that.] 9. ECMP-mode MoFRR. =A0"If more than two ECMP paths
> exist.." =A0In this paragraph you suggest that other aspects may be taken=
 into
> account (such as looking into the IGP topology), but you're not specific.=
 =A0I
> realize that the operation doesn't require interoperability..but it would=
 be
> nice to either=A0specify some options or just leave it at "the decision o=
n how to
> select a secondary UHM is left to a local decision". =A0The later would b=
e my
> preference.
> 10. Non-ECMP-mode MoFRR. "Router X MUST stop joining the seconday
> path if the=A0following as described below occurs. . .In order to=A0preve=
nt control-
> plane loops a router MUST never setup a secondary=A0path to a LFA UMH if =
this
> UMH is the only member in the OIF list." =A0I think there are really two
> conditions here (not just one as the text seems to indicate):
> o The secondary path shouldn't be established if the LFA is the only memb=
er
> of the OIF list.
> o The secondary path is established through an LFA (because there are
> multiple members in the OIF list), but later a change in the network resu=
lts in
> the secondary UMH being alone in the OIF list.
> 11. Keep It Simple. =A0This section seems to answer my point #8 above. =
=A0You
> should consider merging the two.
>=20
> Nits:
> 1. Abstract. =A0You mention "IPTV deployments", but isn't it any streaming
> media application over IP? =A0Maybe just splitting hairs..but a good
> intro/abstract is important.
> 2. Basic Overview. s/'upstream paths at the time'/'upstream paths at a ti=
me'
> 3. Basic Overview. =A0There are a couple of places in this section (when =
talking
> about redundancy and the selection of the UMH) that refer to other places=
 in
> the draft. =A0It would be nice if a reference to the specific section was=
 included.
> 4. Section 3.2. s/'independent on the interface'/'independent of the
> interface'
> 5. Topologies for MoFRR. =A0"MoFRR works best in topologies illustrated i=
n the
> figure below." =A0I think you meant "figures".
> 6. Dual-Plane Topology. s/its its/its
> 7. Section 4.1. "..described later in the document.." =A0Pointer to the s=
ection.
> 8. ECMP-mode MoFRR. s/same as if MoFRR extension/same as if the MoFRR
> extension 9. Non-ECMP-mode MoFRR. =A0s/seconday/secondary 10. s/draft-
> ietf-rtgwg-lfa-applicability/rfc6571
> 11. Capacity Planning. s/can still benefit=A0from MoFRR benefits/can still
> benefit=A0from MoFRR.
> 12. References to MPLS-OAM, BFD, MVPN..
> 13. You're missing the 'IANA Considerations' section.
> 14. References: =A0rfc5036 is not referenced anywhere.

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Thu May 15 08:29:05 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 809791A00D8; Thu, 15 May 2014 08:28:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YpOHw9SQNmw0; Thu, 15 May 2014 08:28:53 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FD4D1A00E1; Thu, 15 May 2014 08:28:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-rtgwg-mofrr-04.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140515152853.22982.62340.idtracker@ietfa.amsl.com>
Date: Thu, 15 May 2014 08:28:53 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/9YISjHuMwu0aGmkPeFRt9MjyBpo
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 May 2014 15:28:59 -0000

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           : Multicast only Fast Re-Route
        Authors         : Apoorva Karan
                          Clarence Filsfils
                          Dino Farinacci
                          IJsbrand Wijnands
                          Bruno Decraene
                          Uwe Joorde
                          Wim Henderickx
	Filename        : draft-ietf-rtgwg-mofrr-04.txt
	Pages           : 14
	Date            : 2014-05-15

Abstract:
   As IPTV deployments grow in number and size, service providers are
   looking for solutions that minimize the service disruption due to
   faults in the IP network carrying the packets for these services.
   This draft describes a mechanism for minimizing packet loss in a
   network when node or link failures occur.  Multicast only Fast Re-
   Route (MoFRR) works by making simple enhancements to multicast
   routing protocols such as PIM and mLDP.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-mofrr/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rtgwg-mofrr-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-mofrr-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Thu May 15 09:54:12 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 953371A0678 for <rtgwg@ietfa.amsl.com>; Thu, 15 May 2014 09:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.953
X-Spam-Level: 
X-Spam-Status: No, score=-1.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_72=0.6, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lJ6lspHRRep5 for <rtgwg@ietfa.amsl.com>; Thu, 15 May 2014 09:54:07 -0700 (PDT)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D4151A0672 for <rtgwg@ietf.org>; Thu, 15 May 2014 09:54:06 -0700 (PDT)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s4FGo69e032306; Thu, 15 May 2014 12:50:06 -0400 (EDT) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201405151650.s4FGo69e032306@maildrop2.v6ds.occnc.com>
To: liu.bin21@zte.com.cn
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: Reply to comments -- Comparison between FAR and OSPF - FRR
In-reply-to: Your message of "Thu, 15 May 2014 13:08:07 +0800." <OF7B611F3A.6F9BF7DF-ON48257CD9.0018F932-48257CD9.001C368E@zte.com.cn>
Date: Thu, 15 May 2014 12:50:06 -0400
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/2Tc7B9xYoiwaIVyHVkJ8uCBLQAc
Cc: rtgwg-chairs@tools.ietf.org, ytsun <ytsun@bjtu.edu.cn>, adrian@olddog.co.uk, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 May 2014 16:54:09 -0000

Richard,

Just addressing the FRR comments.

Another point is that IETF does not create standards based solely on
research projects.  For a whole new routing protocol to be considered,
implementation and some deployment experience is generally needed.
IRTF may be interested in considering routing research.

Curtis


In message <OF7B611F3A.6F9BF7DF-ON48257CD9.0018F932-48257CD9.001C368E@zte.com.cn>
liu.bin21@zte.com.cn writes:
>  
> --------"Network convergence doesn't follow link state
>           dynamics - Fast reroute exists. "
>  
> Comparison of convergence time: The settings of OSPF spf_delay and
> spf_hold_time can affect the change of convergence time. The
> convergence time of the network with 2480 nodes is about 15-20
> seconds(as seen in the following pages); while the FAR does not need
> to calculate the SFP, so there is no such convergence time.  These
> issuesstill existin rapid convergence technology of OSPF and ISIS
> (such as I-SPF). The convergence speed and network scale constraint
> each other. FAR does not have the above problems, and the convergence
> time is almost negligible.
>  
> And test data is been include in another pptx material named OSPF in
> DCN (2).pptx, which can be download from IETF.
>  
> Looking forward to further discussion.
>  
> Best.
>  
> Richard Bin Liu

Your comments above seem to ignore the point about fast reroute (FRR)
stated above "Network convergence doesn't follow link state dynamics -
Fast reroute exists", though the comment could have been better
worded.  MPLS RSVP-TE FRR and IP/LDP FRR are both order(1) or at worst
scale with route install speed.  No SPF is required for FRR to provide
protection, restoring traffic flow though sometimes on a suboptimal
path.  The goal of FRR is to keep protection time under 45 msec (and
old and some argue meaningless SONET target).  In practice many FRR
implementations provide protection in under 20 msec even for large
topologies.  The convergence which follows only serves to further
optimize traffic flow, particularly where RSVP-TE is used.

One commercial CSPF measured about a decade ago completed in 30-40
msec on a test topology of 450.  That was on a 300 MHz or less PPC or
Pentium-2.  Todays processors are an order of magnitude faster, so we
could expect (with order NlogN scaling of SPF) to get about the same
SPF time on a topology of 4K or more nodes with no improvements in
software.  The CSPF was in an RSVP-TE implementation with a lot of
ancilliary data structures built for later incremental CSPF and for
caching of CSPF results.  I don't remember the plain ol' SPF results
but I think it was under 10 msec and wasn't an issue so wasn't studied
to the same extent.

Curtis


From nobody Fri May 23 05:43:35 2014
Return-Path: <cbowers@juniper.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75E5A1A01A8 for <rtgwg@ietfa.amsl.com>; Fri, 23 May 2014 05:43:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lMlqbkpeDeLN for <rtgwg@ietfa.amsl.com>; Fri, 23 May 2014 05:43:31 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0142.outbound.protection.outlook.com [207.46.163.142]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB6DF1A01A0 for <rtgwg@ietf.org>; Fri, 23 May 2014 05:43:30 -0700 (PDT)
Received: from BLUPR05MB292.namprd05.prod.outlook.com (10.141.23.27) by BLUPR05MB292.namprd05.prod.outlook.com (10.141.23.27) with Microsoft SMTP Server (TLS) id 15.0.944.11; Fri, 23 May 2014 12:43:27 +0000
Received: from BLUPR05MB292.namprd05.prod.outlook.com ([10.141.23.27]) by BLUPR05MB292.namprd05.prod.outlook.com ([10.141.23.27]) with mapi id 15.00.0944.000; Fri, 23 May 2014 12:43:27 +0000
From: Chris Bowers <cbowers@juniper.net>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: comments on draft-ietf-rtgwg-remote-lfa-05
Thread-Topic: comments on draft-ietf-rtgwg-remote-lfa-05
Thread-Index: Ac92FiVpk8eyOkqjQay+lyXFoyqc3g==
Date: Fri, 23 May 2014 12:43:26 +0000
Message-ID: <fb486e33b3a24b57abe8968004cf625c@BLUPR05MB292.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.239.14]
x-forefront-prvs: 0220D4B98D
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(428001)(164054003)(199002)(189002)(86362001)(79102001)(21056001)(54356999)(2656002)(76482001)(74662001)(99286001)(99396002)(81542001)(76576001)(31966008)(4396001)(87936001)(77982001)(81342001)(50986999)(74502001)(92566001)(77096999)(85852003)(15202345003)(66066001)(15975445006)(46102001)(64706001)(83072002)(20776003)(33646001)(19580395003)(101416001)(83322001)(80022001)(74316001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR05MB292; H:BLUPR05MB292.namprd05.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (: juniper.net does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=cbowers@juniper.net; 
Content-Type: multipart/alternative; boundary="_000_fb486e33b3a24b57abe8968004cf625cBLUPR05MB292namprd05pro_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/4O2uf1hOLQ9f9Loq8HvqFVZBn68
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 May 2014 12:43:33 -0000

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

Authors,

Below are two comments on draft-ietf-rtgwg-remote-lfa-05.

1) A section should be added to the document clarifying what the expected b=
ehavior is for RLFA when routers advertise themselves as not desiring to ca=
rry transit traffic or links have been costed out.    RFC5286 has a useful =
section on this topic entitled "Interactions with IS-IS Overload, RFC 3137,=
 and Costed Out Links".  The current document would benefit from additional=
 clarity in this topic.

2) The current document doesn't appear to say anything about the expected b=
ehavior of RLFA when the IGP has multiple areas or levels.  It would be use=
ful to either address this topic, or explicitly narrow the scope of the doc=
ument to describing the behavior when the IGP has a single area or level.

Thanks,
Chris



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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri" size=3D"2"><span style=3D"font-size:11pt;">
<div>Authors,</div>
<div>&nbsp;</div>
<div>Below are two comments on draft-ietf-rtgwg-remote-lfa-05.</div>
<div>&nbsp;</div>
<div>1) A section should be added to the document clarifying what the expec=
ted behavior is for RLFA when routers advertise themselves as not desiring =
to carry transit traffic or links have been costed out.&nbsp;&nbsp;&nbsp; R=
FC5286 has a useful section on this topic entitled
&#8220;Interactions with IS-IS Overload, RFC 3137, and Costed Out Links&#82=
21;.&nbsp; The current document would benefit from additional clarity in th=
is topic.</div>
<div>&nbsp;</div>
<div>2) The current document doesn&#8217;t appear to say anything about the=
 expected behavior of RLFA when the IGP has multiple areas or levels.&nbsp;=
 It would be useful to either address this topic, or explicitly narrow the =
scope of the document to describing the behavior
when the IGP has a single area or level.&nbsp; </div>
<div>&nbsp;</div>
<div>Thanks,</div>
<div>Chris </div>
<div>&nbsp;</div>
<div>&nbsp;</div>
</span></font>
</body>
</html>

--_000_fb486e33b3a24b57abe8968004cf625cBLUPR05MB292namprd05pro_--


From nobody Fri May 23 05:53:02 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDEE91A01AA for <rtgwg@ietfa.amsl.com>; Fri, 23 May 2014 05:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.151
X-Spam-Level: 
X-Spam-Status: No, score=-10.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHi5k61AhtLx for <rtgwg@ietfa.amsl.com>; Fri, 23 May 2014 05:52:55 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 530E31A01A9 for <rtgwg@ietf.org>; Fri, 23 May 2014 05:52:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=29718; q=dns/txt; s=iport; t=1400849573; x=1402059173; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=Wrj51CWsBqZxo/RZmkqnh/QhJInCE5y/MTVBiYuKMUQ=; b=J6HM+W9GfWxVxeeqeBb5IchpjY1OGvbhHGOH5P7nWw5Ige0L5KEDnn7U 8KrZeEJAh3Vp/ToRP727czdGu8zQwyp5pm7JX9rddfu/KktxpvYmvD9Lh YKmanjvwYTKR8aiXo1Py8T3exRZHFe4NFqQpj5jshw2K4OInRVBMlnemt c=;
X-IronPort-AV: E=Sophos; i="4.98,893,1392163200"; d="scan'208,217"; a="59401896"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 23 May 2014 12:52:51 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s4NCqp50004966 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 May 2014 12:52:51 GMT
Received: from STBRYANT-M-R010.CISCO.COM (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s4NCqoub026037; Fri, 23 May 2014 13:52:50 +0100 (BST)
Message-ID: <537F44A7.20902@cisco.com>
Date: Fri, 23 May 2014 13:52:55 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Pushpasis Sarkar <psarkar@juniper.net>, "Alvaro Retana (aretana)" <aretana@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: WGLC for draft-ietf-rtgwg-remote-lfa
References: <CEC4C406.43593%aretana@cisco.com> <c043b7fae6fc4aba9c98bbaad5eab388@BN1PR05MB520.namprd05.prod.outlook.com>
In-Reply-To: <c043b7fae6fc4aba9c98bbaad5eab388@BN1PR05MB520.namprd05.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------030802040401080806020000"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/KTMJZUZYPKBgM8PFWwQZ5c5rcTI
Cc: "draft-ietf-rtgwg-remote-lfa@tools.ietf.org" <draft-ietf-rtgwg-remote-lfa@tools.ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 May 2014 12:52:59 -0000

This is a multi-part message in MIME format.
--------------030802040401080806020000
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 04/12/2013 20:26, Pushpasis Sarkar wrote:
>
> Hi Stewart/Alvaro,
>
> It maybe a very late, but I wanted to point the following issue with 
> the algorithm/psuedocode text provided in section 4.3.
>
> /////////////////////////////////////////////////////////////////
>
> //
>
> // Calculate extended P-space
>
> //
>
> // Note the strictly less than operator is needed to
>
> // avoid ECMP issues.
>
> Compute_Extended_P_Space(fail_intf)
>
> foreach node y in network
>
> y.in_extended_P_space = false
>
> // Extend P-space to the P-spaces of all reachable
>
> // neighbours
>
> foreach interface intf in self
>
> *[Pushpasis] From definition of intf.remote_node, there maybe multiple 
> 'remote_node's for a given 'intf' (specially if the 'intf' is a LAN 
> intf. So there should be another 'foreach intf.remote_node in intf' 
> loop here in this algorithm text.*
>
Since we do not support repair of a next hop lan the text is now:
               if (intf != fail_intf)
                    foreach neighbor n in intf.remote_node
                        // Apply RFC5286 Inequality 1
                        if ( D_opt(n, y) <
                                D_opt(n,self) + D_opt)(self, y)
                            y.in_extended_P_space = true


> **
>
> if (intf.remote_node != fail_intf.remote_node)
>
> if ( D_opt(intf.remote_node, y) <
>
> D_opt(intf.remote_node, self) +
>
> D_opt(self,fail_intf.remote_node) +
>
> D_opt(fail_intf.remote_node,y) )
>
> y.in_extended_P_space = true
>
> /////////////////////////////////////////////////////////////////
>
> //
>
> // Compute the nodes in Q-space
>
> //
>
> Compute_Q_Space(fail_intf)
>
> // Compute the cost from every node the network to the
>
> // node normally reachable across the failed link
>
> Compute_and_Store_Reverse_SPF(fail_intf.remote_node)
>
> // Compute the cost from every node the network to self
>
> Compute_and_Store_Reverse_SPF(self)
>
> foreach node y in network
>
> *[Pushpasis] Again from definition of intf.remote_node, there maybe 
> multiple 'remote_node's for a given 'fail_intf' (specially if the 
> 'fail_intf' is a LAN intf. So there should be another 'foreach 
> intf.remote_node in intf' loop here in this algorithm text. Also there 
> is a question of which 'remote_node' will the below inequality be 
> evaluated on in this case. This needs to be clarified. *
>
No, we are not supporting repair of a LAN, so I don't think this change 
is needed.*

*
>
> **
>
>               if ( D_opt(y,fail_intf.remote_node) < D_opt(y,self) +
>
> D_opt(self,fail_intf.remote_node) )
>
> y.in_Q_space = true
>
> else
>
> y.in_Q_space = false
>
> /////////////////////////////////////////////////////////////////
>
> //
>
> // Compute set of nodes in both extended P-space and in Q-space
>
> Intersect_Extended_P_and_Q_Space()
>
> *[Pushpasis] The PQ-space is a function of the 'fail_intf'. One node 
> maybe PQ-node for one 'fail_intf' and still not be the PQ-node for 
> another 'fail_intf'. So the 'fail_intf' should be a input parameter 
> for this procedure. Also the flags in_extended_P_space and in_Q_space 
> for node y should be defined per 'fail_intf'.*
>
> foreach node y in network
>
> if ( y.in_extended_P_space && y.in_Q_space )
>
> y.valid_tunnel_endpoint = true
>
> else
>
> y.valid_tunnel_endpoint = false
>
fail_intf was a parameter to Compute_Extended_P_Space(fail_intf) and 
Compute_Q_Space(fail_intf)

I have clarified this in the introduction:
This section describes a method of computing the remote LFA repair 
target *for a specific failed link* using a cost based algorithm.

Clearly we could add the additional for loop in, but we are writing a 
description to aid understanding not compilable code, so the simpler we 
make it the better.

Stewart

> The current text needs to be enhanced and clarified with more details 
> to achieve completeness in my opinion. Once again regret the late 
> response.
>
> Thanks
>
> -Pushpasis
>
> *From:*Alvaro Retana (aretana) [mailto:aretana@cisco.com]
> *Sent:* Wednesday, December 04, 2013 7:06 PM
> *To:* rtgwg@ietf.org
> *Cc:* draft-ietf-rtgwg-remote-lfa@tools.ietf.org
> *Subject:* WGLC for draft-ietf-rtgwg-remote-lfa
>
> Hi!
>
> After what I thought was a productive set of feedback and discussion 
> related to this draft, both in the mailing list as well as at the 
> meeting in Vancouver, I would like to start a Working Group Last Call. 
>  This call will close by EOD (pick your favorite time zone) on 
> December 19, 2013.
>
> http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa
>
> Please provide specific feedback as to why you support (or not) the 
> advancement of this draft.  Please avoid "+1"-type responses.
>
> Thanks!
>
> Alvaro.
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


--------------030802040401080806020000
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 04/12/2013 20:26, Pushpasis Sarkar
      wrote:<br>
    </div>
    <blockquote
cite="mid:c043b7fae6fc4aba9c98bbaad5eab388@BN1PR05MB520.namprd05.prod.outlook.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.mftr
	{mso-style-name:m_ftr;}
span.mhdr
	{mso-style-name:m_hdr;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi
            Stewart/Alvaro,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">It
            maybe a very late, but I wanted to point the following issue
            with the algorithm/psuedocode text provided in section 4.3.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
/////////////////////////////////////////////////////////////////<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            //<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            // Calculate extended P-space<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            //<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            // Note the strictly less than operator is needed to<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            // avoid ECMP issues.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            Compute_Extended_P_Space(fail_intf)<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            foreach node y in network<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            y.in_extended_P_space = false<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            // Extend P-space to the P-spaces of all reachable<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            // neighbours<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            foreach interface intf in self<o:p></o:p></span></p>
        <p class="MsoNormal"><b><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:red">[Pushpasis] From definition of
              intf.remote_node, there maybe multiple &#8216;remote_node&#8217;s for
              a given &#8216;intf&#8217; (specially if the &#8216;intf&#8217; is a LAN intf. So
              there should be another &#8216;foreach intf.remote_node in intf&#8217;
              loop here in this algorithm text.</span></b></p>
      </div>
    </blockquote>
    Since we do not support repair of a next hop lan the text is now:<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (intf != fail_intf)<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; foreach neighbor n in intf.remote_node<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Apply RFC5286 Inequality 1<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if ( D_opt(n, y) &lt;<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D_opt(n,self) + D_opt)(self, y)<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; y.in_extended_P_space = true&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
    <br>
    <br>
    <blockquote
cite="mid:c043b7fae6fc4aba9c98bbaad5eab388@BN1PR05MB520.namprd05.prod.outlook.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><b><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:red"><o:p></o:p></span></b></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            if (intf.remote_node != fail_intf.remote_node)<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            if ( D_opt(intf.remote_node, y) &lt;<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            D_opt(intf.remote_node, self) +<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            D_opt(self,fail_intf.remote_node) +<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            D_opt(fail_intf.remote_node,y) )<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            y.in_extended_P_space = true<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
/////////////////////////////////////////////////////////////////<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            //<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            // Compute the nodes in Q-space<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            //<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            Compute_Q_Space(fail_intf)<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            // Compute the cost from every node the network to the<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            // node normally reachable across the failed link<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            Compute_and_Store_Reverse_SPF(fail_intf.remote_node)<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            // Compute the cost from every node the network to self<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            Compute_and_Store_Reverse_SPF(self)<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            foreach node y in network<o:p></o:p></span></p>
        <p class="MsoNormal"><b><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:red">[Pushpasis] Again from definition of
              intf.remote_node, there maybe multiple &#8216;remote_node&#8217;s for
              a given &#8216;fail_intf&#8217; (specially if the &#8216;fail_intf&#8217; is a LAN
              intf. So there should be another &#8216;foreach intf.remote_node
              in intf&#8217; loop here in this algorithm text. Also there is a
              question of which &#8216;remote_node&#8217; will the below inequality
              be evaluated on in this case. This needs to be clarified.
            </span></b></p>
      </div>
    </blockquote>
    No, we are not supporting repair of a LAN, so I don't think this
    change is needed.<b><br>
      <br>
    </b>
    <blockquote
cite="mid:c043b7fae6fc4aba9c98bbaad5eab388@BN1PR05MB520.namprd05.prod.outlook.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><b><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:red"><o:p></o:p></span></b></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if
            ( D_opt(y,fail_intf.remote_node) &lt; D_opt(y,self) +<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            D_opt(self,fail_intf.remote_node) )<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            y.in_Q_space = true<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            else<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            y.in_Q_space = false<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
/////////////////////////////////////////////////////////////////<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            //<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            // Compute set of nodes in both extended P-space and in
            Q-space<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            Intersect_Extended_P_and_Q_Space()<o:p></o:p></span></p>
        <p class="MsoNormal"><b><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:red">[Pushpasis] The PQ-space is a
              function of the &#8216;fail_intf&#8217;. One node maybe PQ-node for
              one &#8216;fail_intf&#8217; and still not be the PQ-node for another
              &#8216;fail_intf&#8217;. So the &#8216;fail_intf&#8217; should be a input
              parameter for this procedure. Also the flags
              in_extended_P_space and in_Q_space for node y should be
              defined per &#8216;fail_intf&#8217;.<o:p></o:p></span></b></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            foreach node y in network<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            if ( y.in_extended_P_space &amp;&amp; y.in_Q_space )<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            y.valid_tunnel_endpoint = true<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            else<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            y.valid_tunnel_endpoint = false<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
      </div>
    </blockquote>
    fail_intf was a parameter to Compute_Extended_P_Space(fail_intf) and
    Compute_Q_Space(fail_intf)<br>
    <br>
    I have clarified this in the introduction:<br>
    This section describes a method of computing the remote LFA repair
    target *for a specific failed link* using a cost based algorithm.<br>
    <br>
    Clearly we could add the additional for loop in, but we are writing
    a description to aid understanding not compilable code, so the
    simpler we make it the better.<br>
    <br>
    Stewart<br>
    <br>
    <blockquote
cite="mid:c043b7fae6fc4aba9c98bbaad5eab388@BN1PR05MB520.namprd05.prod.outlook.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The
            current text needs to be enhanced and clarified with more
            details to achieve completeness in my opinion. Once again
            regret the late response.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">-Pushpasis<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #E1E1E1
            1.0pt;padding:3.0pt 0in 0in 0in">
            <p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">
                Alvaro Retana (aretana) [<a class="moz-txt-link-freetext" href="mailto:aretana@cisco.com">mailto:aretana@cisco.com</a>]
                <br>
                <b>Sent:</b> Wednesday, December 04, 2013 7:06 PM<br>
                <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
                <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-rtgwg-remote-lfa@tools.ietf.org">draft-ietf-rtgwg-remote-lfa@tools.ietf.org</a><br>
                <b>Subject:</b> WGLC for draft-ietf-rtgwg-remote-lfa<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <div>
          <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Hi!<o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">After
              what I thought was a productive set of feedback and
              discussion related to this draft, both in the mailing list
              as well as at the meeting in Vancouver, I would like to
              start a Working Group Last Call. &nbsp;This call will close by
              EOD (pick your favorite time zone) on December 19, 2013.<o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><a
                moz-do-not-send="true"
                href="http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa">http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa</a><o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Please
              provide specific feedback as to why you support (or not)
              the advancement of this draft. &nbsp;Please avoid "+1"-type
              responses.<o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Thanks!<o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Alvaro.<o:p></o:p></span></p>
        </div>
      </div>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

<a class="moz-txt-link-freetext" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a>

</pre>
  </body>
</html>

--------------030802040401080806020000--


From nobody Fri May 23 08:11:03 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF1D11A0537 for <rtgwg@ietfa.amsl.com>; Fri, 23 May 2014 08:11:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.151
X-Spam-Level: 
X-Spam-Status: No, score=-10.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pII5kXIIFUMu for <rtgwg@ietfa.amsl.com>; Fri, 23 May 2014 08:11:00 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEDE11A0176 for <rtgwg@ietf.org>; Fri, 23 May 2014 08:10:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5047; q=dns/txt; s=iport; t=1400857858; x=1402067458; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to; bh=978o1Gvv3cqz9yT1Zug14Mk3mnVOQoy6hkqNfr3M2fU=; b=LRgItUgCKvfrBWPrG078TTd2l4Q8zbe2cE6eI6QTQxzI1LnLnygQxTzy XYgRPsrpaTtyQNOxEmiYuuyS6HKo1pmSm+3trhQBU73Fa5aDEamg+o7G8 EZKyj1fi/e8ez+tf5PWK1FviazJN8IiyfgZ5ZXmrByi0YiY/MdJLT1ZZP o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqIEAGJkf1OtJssW/2dsb2JhbABagkLDJIMSAYEedIIlAQEBBC1LEQsECgoJDAoPCQMCAQIBRQYBDAgBAYg9uW2eKxeOWQqENgSZcpMngzk
X-IronPort-AV: E=Sophos; i="4.98,894,1392163200"; d="scan'208,217"; a="55434594"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 23 May 2014 15:10:56 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s4NFAtJ2021049 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 May 2014 15:10:56 GMT
Received: from STBRYANT-M-R010.CISCO.COM (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s4NFAt1a004425; Fri, 23 May 2014 16:10:55 +0100 (BST)
Message-ID: <537F6504.3010105@cisco.com>
Date: Fri, 23 May 2014 16:11:00 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Chris Bowers <cbowers@juniper.net>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: comments on draft-ietf-rtgwg-remote-lfa-05
References: <fb486e33b3a24b57abe8968004cf625c@BLUPR05MB292.namprd05.prod.outlook.com>
In-Reply-To: <fb486e33b3a24b57abe8968004cf625c@BLUPR05MB292.namprd05.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------020005020503080807050504"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/Ng7tPysaZA4MOHb5WofDlJW5-TQ
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 May 2014 15:11:02 -0000

This is a multi-part message in MIME format.
--------------020005020503080807050504
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 23/05/2014 13:43, Chris Bowers wrote:
> Authors,
> Below are two comments on draft-ietf-rtgwg-remote-lfa-05.
> 1) A section should be added to the document clarifying what the 
> expected behavior is for RLFA when routers advertise themselves as not 
> desiring to carry transit traffic or links have been costed out.    
> RFC5286 has a useful section on this topic entitled "Interactions with 
> IS-IS Overload, RFC 3137, and Costed Out Links".  The current document 
> would benefit from additional clarity in this topic.
New section 4.4.

The consideration concerning interactions with IS-IS Overload, [RFC3137],
and costed out links as described in [RFC5286] apply. In selecting a PQ
node a PLR MUST exclude any candidate that is reachable (including via 
ECMP)
from the PLR via a path subject to one of the above exclusions.
The method of determining the exclusion is a local matter.
> 2) The current document doesn't appear to say anything about the 
> expected behavior of RLFA when the IGP has multiple areas or levels.  
> It would be useful to either address this topic, or explicitly narrow 
> the scope of the document to describing the behavior when the IGP has 
> a single area or level.
I have added to the bottom of the intro:

This document considers the case when the repair path is confined to 
either a
single area or to the level two routing domain. In all other cases, the 
chosen
PQ node should be regarded as a tunnel adjacency of the repairing node,
and the considerations  described in Section 6 of [RFC5286] taken
into account.

- Stewart

--------------020005020503080807050504
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 23/05/2014 13:43, Chris Bowers
      wrote:<br>
    </div>
    <blockquote
cite="mid:fb486e33b3a24b57abe8968004cf625c@BLUPR05MB292.namprd05.prod.outlook.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Exchange Server">
      <!-- converted from rtf -->
      <style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
      <font face="Calibri" size="2"><span style="font-size:11pt;">
          <div>Authors,</div>
          <div>&nbsp;</div>
          <div>Below are two comments on draft-ietf-rtgwg-remote-lfa-05.</div>
          <div>&nbsp;</div>
          <div>1) A section should be added to the document clarifying
            what the expected behavior is for RLFA when routers
            advertise themselves as not desiring to carry transit
            traffic or links have been costed out.&nbsp;&nbsp;&nbsp; RFC5286 has a
            useful section on this topic entitled
            &#8220;Interactions with IS-IS Overload, RFC 3137, and Costed Out
            Links&#8221;.&nbsp; The current document would benefit from additional
            clarity in this topic.</div>
        </span></font></blockquote>
    New section 4.4.<br>
    <br>
    The consideration concerning interactions with IS-IS Overload,
    [RFC3137], <br>
    and costed out links as described in [RFC5286] apply. In selecting a
    PQ <br>
    node a PLR MUST exclude any candidate that is reachable (including
    via ECMP) <br>
    from the PLR via a path subject to one of the above exclusions. <br>
    The method of determining the exclusion is a local matter.<br>
    <blockquote
cite="mid:fb486e33b3a24b57abe8968004cf625c@BLUPR05MB292.namprd05.prod.outlook.com"
      type="cite"><font face="Calibri" size="2"><span
          style="font-size:11pt;">
          <div>&nbsp;</div>
          <div>2) The current document doesn&#8217;t appear to say anything
            about the expected behavior of RLFA when the IGP has
            multiple areas or levels.&nbsp; It would be useful to either
            address this topic, or explicitly narrow the scope of the
            document to describing the behavior
            when the IGP has a single area or level.&nbsp; </div>
        </span></font></blockquote>
    I have added to the bottom of the intro:<br>
    <br>
    This document considers the case when the repair path is confined to
    either a <br>
    single area or to the level two routing domain. In all other cases,
    the chosen <br>
    PQ node should be regarded as a tunnel adjacency of the repairing
    node, <br>
    and the considerations&nbsp; described in Section 6 of [RFC5286] taken <br>
    into account.<br>
    <br>
    - Stewart<br>
  </body>
</html>

--------------020005020503080807050504--


From nobody Fri May 23 08:51:13 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E35A71A06A2; Fri, 23 May 2014 08:51:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FChJLE-lIFSt; Fri, 23 May 2014 08:51:04 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9201A06A3; Fri, 23 May 2014 08:50:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-rtgwg-remote-lfa-06.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140523155059.4731.53028.idtracker@ietfa.amsl.com>
Date: Fri, 23 May 2014 08:50:59 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/Drt_KpSVbfnnBBaQg3aTP4Y5vl4
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 May 2014 15:51:11 -0000

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           : Remote LFA FRR
        Authors         : Stewart Bryant
                          Clarence Filsfils
                          Stefano Previdi
                          Mike Shand
                          Ning So
	Filename        : draft-ietf-rtgwg-remote-lfa-06.txt
	Pages           : 27
	Date            : 2014-05-23

Abstract:
   This draft describes an extension to the basic IP fast re-route
   mechanism described in RFC5286, that provides additional backup
   connectivity for point to point link failures when none can be
   provided by the basic mechanisms.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-remote-lfa-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Fri May 23 08:59:19 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41BD31A01BA for <rtgwg@ietfa.amsl.com>; Fri, 23 May 2014 08:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.152
X-Spam-Level: 
X-Spam-Status: No, score=-10.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vGMLgB_AZ6jS for <rtgwg@ietfa.amsl.com>; Fri, 23 May 2014 08:59:17 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EB801A016C for <rtgwg@ietf.org>; Fri, 23 May 2014 08:59:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2194; q=dns/txt; s=iport; t=1400860755; x=1402070355; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=0tnoaMWrmRVWI4gU7O0HcYc73KGMpLL29H39ACXKWbA=; b=ibwUOLC2UZTFLQEtG19VkBWu8UQhT/H4Gt3O13kU+GFlPSW7cabL3HHc WPQbM+uZRJnRuuLrjOZMUOfAQVnylfuL8F4Vn9R9iYrCKP2GOTQiFu1No k5sPqgua8HicknhHZK5T47ro+U9o2SgRRyLa2aoQ9hW9Lkw/1DeMR8KGG s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsgGAOJuf1OtJssW/2dsb2JhbABag1lRvHOHPAGBHnSCJQEBAQQBAQE1NgoBEAsYCRYPCQMCAQIBFTAGDQEFAgEBBYg4CAW5Xp4iF41naweEQASZcoE9kWqDOWw
X-IronPort-AV: E=Sophos;i="4.98,894,1392163200"; d="scan'208";a="60223672"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 23 May 2014 15:59:13 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s4NFxCFM030324 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 May 2014 15:59:13 GMT
Received: from STBRYANT-M-R010.CISCO.COM (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s4NFx9kA007197; Fri, 23 May 2014 16:59:12 +0100 (BST)
Message-ID: <537F7052.6090903@cisco.com>
Date: Fri, 23 May 2014 16:59:14 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>
Subject: Re: I-D Action: draft-ietf-rtgwg-remote-lfa-06.txt
References: <20140523155059.4731.53028.idtracker@ietfa.amsl.com>
In-Reply-To: <20140523155059.4731.53028.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/VV7p0wFCr0gWVHDCWcp6u02wGYA
Cc: "draft-ietf-rtgwg-remote-lfa@tools.ietf.org" <draft-ietf-rtgwg-remote-lfa@tools.ietf.org>, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 May 2014 15:59:18 -0000

Baring an error in the editing, this version has addressed
all of the issues that were raised post version 4 and post version
5, and therefore should include all of the changes that I said
I was making in the various reply notes I have been sending
to the list.

I think that this is now ready for the WGCs to continue
the publication process.

Thanks to everyone that contributed review comments.

- Stewart

On 23/05/2014 16:50, internet-drafts@ietf.org wrote:
> 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           : Remote LFA FRR
>          Authors         : Stewart Bryant
>                            Clarence Filsfils
>                            Stefano Previdi
>                            Mike Shand
>                            Ning So
> 	Filename        : draft-ietf-rtgwg-remote-lfa-06.txt
> 	Pages           : 27
> 	Date            : 2014-05-23
>
> Abstract:
>     This draft describes an extension to the basic IP fast re-route
>     mechanism described in RFC5286, that provides additional backup
>     connectivity for point to point link failures when none can be
>     provided by the basic mechanisms.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa-06
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-remote-lfa-06
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
> .
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From nobody Tue May 27 14:36:14 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13B361A0286; Tue, 27 May 2014 14:36:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ecj-ZZ_Hy1l; Tue, 27 May 2014 14:36:08 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CD20C1A027A; Tue, 27 May 2014 14:36:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140527213608.31267.80528.idtracker@ietfa.amsl.com>
Date: Tue, 27 May 2014 14:36:08 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/8qfP1kwigBmBU5bkuQR-o63oN0g
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 21:36:10 -0000

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 MIB for IP Fast-Reroute
        Authors         : Alia Atlas
                          Cisco Systems
                          John Flick
                          Stephane Litkowski
	Filename        : draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
	Pages           : 26
	Date            : 2014-05-27

Abstract:
   This draft defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects relevant for IP routes
   using IP Fast-Reroute [RFC5714]



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-ipfrr-ip-mib/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rtgwg-ipfrr-ip-mib-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-ipfrr-ip-mib-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Wed May 28 00:17:50 2014
Return-Path: <stephane.litkowski@orange.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4F4E1A03C1 for <rtgwg@ietfa.amsl.com>; Wed, 28 May 2014 00:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ByACnH1fXwc for <rtgwg@ietfa.amsl.com>; Wed, 28 May 2014 00:17:45 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E22A1A039A for <rtgwg@ietf.org>; Wed, 28 May 2014 00:17:45 -0700 (PDT)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda10.si.francetelecom.fr (ESMTP service) with ESMTP id 43F4F3741DC for <rtgwg@ietf.org>; Wed, 28 May 2014 09:17:40 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.55]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id 87C2AC8088 for <rtgwg@ietf.org>; Wed, 28 May 2014 09:17:39 +0200 (CEST)
Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.246]) by OPEXCLILH03.corporate.adroot.infra.ftgroup ([10.114.31.55]) with mapi id 14.03.0181.006; Wed, 28 May 2014 09:17:39 +0200
From: <stephane.litkowski@orange.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
Thread-Topic: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
Thread-Index: AQHPefOyESAdv20HH02eg6JxXc256ZtVlPwA
Date: Wed, 28 May 2014 07:17:38 +0000
Message-ID: <9235_1401261459_53858D93_9235_2274_1_9E32478DFA9976438E7A22F69B08FF92011FDB@OPEXCLILM34.corporate.adroot.infra.ftgroup>
References: <20140527213608.31267.80528.idtracker@ietfa.amsl.com>
In-Reply-To: <20140527213608.31267.80528.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.5.13.75120
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/y9DtxsH0-9jKr3JAhlm1KojwMt8
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 May 2014 07:17:48 -0000

Hi all,

To followup discussion in London, I updated the IP FRR MIB draft with some =
new things :
- different objects for IPv4 and IPv6 protection stats
- Interface configuration table
- IPFRR instance table as we may expect to have multiple flavors running on=
 a common node
- Protectstats per instance table.
- Few other things

Feel free to comment and propose addings/corrections.


Stephane



-----Original Message-----
From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of inte=
rnet-drafts@ietf.org
Sent: Tuesday, May 27, 2014 23:36
To: i-d-announce@ietf.org
Cc: rtgwg@ietf.org
Subject: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt


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

        Title           : IP MIB for IP Fast-Reroute
        Authors         : Alia Atlas
                          Cisco Systems
                          John Flick
                          Stephane Litkowski
	Filename        : draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
	Pages           : 26
	Date            : 2014-05-27

Abstract:
   This draft defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects relevant for IP routes
   using IP Fast-Reroute [RFC5714]



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-ipfrr-ip-mib/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rtgwg-ipfrr-ip-mib-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-rtgwg-ipfrr-ip-mib-03


Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at tools.ietf.org.

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

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ie=
tf.org/ietf/1shadow-sites.txt

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Wed May 28 01:20:56 2014
Return-Path: <bruno.decraene@orange.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A55C1A02A4 for <rtgwg@ietfa.amsl.com>; Wed, 28 May 2014 01:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2lWKBIongXtn for <rtgwg@ietfa.amsl.com>; Wed, 28 May 2014 01:20:52 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C896A1A01F2 for <rtgwg@ietf.org>; Wed, 28 May 2014 01:20:51 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id EE9283B40DD for <rtgwg@ietf.org>; Wed, 28 May 2014 10:20:46 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id CFD654C075 for <rtgwg@ietf.org>; Wed, 28 May 2014 10:20:46 +0200 (CEST)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0181.006; Wed, 28 May 2014 10:20:43 +0200
From: <bruno.decraene@orange.com>
To: LITKOWSKI Stephane SCE/IBNF <stephane.litkowski@orange.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
Thread-Topic: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
Thread-Index: AQHPefOyESAdv20HH02eg6JxXc256ZtVlPwAgAALmjA=
Date: Wed, 28 May 2014 08:20:43 +0000
Message-ID: <29389_1401265246_53859C5E_29389_9110_1_6e0f1d94-6412-413d-b85b-cb17f18ccef9@PEXCVZYH02.corporate.adroot.infra.ftgroup>
References: <20140527213608.31267.80528.idtracker@ietfa.amsl.com> <9235_1401261459_53858D93_9235_2274_1_9E32478DFA9976438E7A22F69B08FF92011FDB@OPEXCLILM34.corporate.adroot.infra.ftgroup>
In-Reply-To: <9235_1401261459_53858D93_9235_2274_1_9E32478DFA9976438E7A22F69B08FF92011FDB@OPEXCLILM34.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.6]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.5.13.75120
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/61cGmVeFfdlJNEDMFZlwi_gdLZw
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 May 2014 08:20:54 -0000

Hi St=E9phane,

Looks good, thanks.

I have a question related to object "ipFrrAltType"

>       loopFreeRemote (4), -- remote loop free alternate
>       loopFreeTunnel (5), -- loop free alternate using a configured tunnel

>       loopFreeRemote : remote LFA as described in draft-ietf-rtgwg-remote=
-lfa
>       loopFreeTunnel : remote LFA reachable through a RSVP-TE or GRE tunn=
el

It's not clear to me what exactly is the difference between loopFreeRemote =
and loopFreeTunnel:
Is this the type of tunnels: explicitly routed (i.e. RSVP-TE) vs following =
the shortest path (i.e. LDP, GRE, draft-ietf-rtgwg-remote-lfa
Is this the determination of the required tunnels: automatically computed (=
i.e. draft-ietf-rtgwg-remote-lfa, automatic RSVP-TE LSP bypass tunnel to th=
e next-hop) vs configured.

Current description seems to mix both aspects.

> loopFreeTI : remote LFA reachable through a SPRING tunnel
To some expect, the question also applies to "loopFreeTI" where there is a =
mix of FRR algorithm (how is the alternate computed i.e. TI FRR) and the ty=
pe of tunnels to reach the alternate (here SPRING tunnels, while in theory =
the alternate could equally be reached using a RSVP-TE+ T-LDP tunnels

I'm open to any solution. IMHO the description of the FRR algo is the more =
important:
      ipFrrAltType OBJECT-TYPE
          SYNTAX   INTEGER {
                      other             (1), -- type not defined
                      equalCost         (2), -- primary path
                      loopFreeConnected          (3), -- loop free connecte=
d alternate (LFA)
                      loopFreeRemote    (4), -- remote loop free alternate =
(RLFA)
                      loopFreeNH    (5), -- loop free alternate using a tun=
nel toward the Next Hop
                      loopFreeNNH    (6), -- loop free alternate using a tu=
nnel toward the Next Next Hop
                      loopFreeTI        (7), -- loop free alternate using t=
opology independent algorithm
                      mrt               (8)  -- Maximally Redundant Trees
                   }

If you believe that we also need the type of tunnels/forwarding infrastruct=
ure, another object could be added
      ipFrrTunnType OBJECT-TYPE
          SYNTAX   INTEGER {
                      other             (1), -- type not defined
                      LDP         (2)
                      IP          (3),  GRE, L2TP...
                      RSVP-TE   (4)
                      SPRING MPLS  (5)
                      SPRING IPv6  (6)
                      Multi-topology (7)
                   }

Bruno

> -----Original Message-----
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of
> stephane.litkowski@orange.com
> Sent: Wednesday, May 28, 2014 9:18 AM
> To: rtgwg@ietf.org
> Subject: FW: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
>=20
> Hi all,
>=20
> To followup discussion in London, I updated the IP FRR MIB draft with some
> new things :
> - different objects for IPv4 and IPv6 protection stats
> - Interface configuration table
> - IPFRR instance table as we may expect to have multiple flavors running =
on a
> common node
> - Protectstats per instance table.
> - Few other things
>=20
> Feel free to comment and propose addings/corrections.
>=20
>=20
> Stephane
>=20
>=20
>=20
> -----Original Message-----
> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: Tuesday, May 27, 2014 23:36
> To: i-d-announce@ietf.org
> Cc: rtgwg@ietf.org
> Subject: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>  This draft is a work item of the Routing Area Working Group Working Group
> of the IETF.
>=20
>         Title           : IP MIB for IP Fast-Reroute
>         Authors         : Alia Atlas
>                           Cisco Systems
>                           John Flick
>                           Stephane Litkowski
> 	Filename        : draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
> 	Pages           : 26
> 	Date            : 2014-05-27
>=20
> Abstract:
>    This draft defines a portion of the Management Information Base (MIB)
>    for use with network management protocols in the Internet community.
>    In particular, it describes managed objects relevant for IP routes
>    using IP Fast-Reroute [RFC5714]
>=20
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-rtgwg-ipfrr-ip-mib/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-rtgwg-ipfrr-ip-mib-03
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-rtgwg-ipfrr-ip-mib-03
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
> __________________________________________________________
> __________________________________________________________
> _____
>=20
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exp=
loites
> ou copies sans autorisation. Si vous avez recu ce message par erreur, veu=
illez
> le signaler a l'expediteur et le detruire ainsi que les pieces jointes. L=
es
> messages electroniques etant susceptibles d'alteration, Orange decline to=
ute
> responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>=20
> This message and its attachments may contain confidential or privileged
> information that may be protected by law; they should not be distributed,
> used or copied without authorisation.
> If you have received this email in error, please notify the sender and de=
lete
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.
>=20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Wed May 28 11:55:13 2014
Return-Path: <cbowers@juniper.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 548A41A063A for <rtgwg@ietfa.amsl.com>; Wed, 28 May 2014 11:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K1AX3REqkphE for <rtgwg@ietfa.amsl.com>; Wed, 28 May 2014 11:55:08 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (dns-bn1lp0143.outbound.protection.outlook.com [207.46.163.143]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C77821A212D for <rtgwg@ietf.org>; Wed, 28 May 2014 11:55:04 -0700 (PDT)
Received: from BLUPR05MB292.namprd05.prod.outlook.com (10.141.23.27) by BLUPR05MB292.namprd05.prod.outlook.com (10.141.23.27) with Microsoft SMTP Server (TLS) id 15.0.949.11; Wed, 28 May 2014 18:54:59 +0000
Received: from BLUPR05MB292.namprd05.prod.outlook.com ([10.141.23.27]) by BLUPR05MB292.namprd05.prod.outlook.com ([10.141.23.27]) with mapi id 15.00.0949.001; Wed, 28 May 2014 18:54:59 +0000
From: Chris Bowers <cbowers@juniper.net>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: comments on draft-ietf-rtgwg-remote-lfa-05
Thread-Topic: comments on draft-ietf-rtgwg-remote-lfa-05
Thread-Index: Ac92FiVpk8eyOkqjQay+lyXFoyqc3gAgw8YAAQMxP2A=
Date: Wed, 28 May 2014 18:54:58 +0000
Message-ID: <4e22fad75d914bb3bb19bae69647d259@BLUPR05MB292.namprd05.prod.outlook.com>
References: <fb486e33b3a24b57abe8968004cf625c@BLUPR05MB292.namprd05.prod.outlook.com> <537F6504.3010105@cisco.com>
In-Reply-To: <537F6504.3010105@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.239.13]
x-forefront-prvs: 0225B0D5BC
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(428001)(377454003)(199002)(189002)(479174003)(24454002)(2656002)(54356999)(87936001)(83072002)(19625215002)(19580405001)(31966008)(16236675002)(83322001)(19580395003)(74502001)(74662001)(15975445006)(85852003)(21056001)(76482001)(77982001)(15202345003)(81542001)(46102001)(99396002)(86362001)(92566001)(4396001)(76576001)(99286001)(19300405004)(33646001)(77096999)(76176999)(81342001)(20776003)(101416001)(74316001)(66066001)(80022001)(50986999)(79102001)(64706001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR05MB292; H:BLUPR05MB292.namprd05.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (: juniper.net does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=cbowers@juniper.net; 
Content-Type: multipart/alternative; boundary="_000_4e22fad75d914bb3bb19bae69647d259BLUPR05MB292namprd05pro_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/wWeM7pWCUsireA3PmNZyukQ9OSU
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 May 2014 18:55:11 -0000

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

See inline [CB] for comment on the new section 4.4.

Chris

From: Stewart Bryant [mailto:stbryant@cisco.com]
Sent: Friday, May 23, 2014 10:11 AM
To: Chris Bowers; rtgwg@ietf.org
Subject: Re: comments on draft-ietf-rtgwg-remote-lfa-05

On 23/05/2014 13:43, Chris Bowers wrote:
Authors,

Below are two comments on draft-ietf-rtgwg-remote-lfa-05.

1) A section should be added to the document clarifying what the expected b=
ehavior is for RLFA when routers advertise themselves as not desiring to ca=
rry transit traffic or links have been costed out.    RFC5286 has a useful =
section on this topic entitled "Interactions with IS-IS Overload, RFC 3137,=
 and Costed Out Links".  The current document would benefit from additional=
 clarity in this topic.
New section 4.4.

The consideration concerning interactions with IS-IS Overload, [RFC3137],
and costed out links as described in [RFC5286] apply. In selecting a PQ
node a PLR MUST exclude any candidate that is reachable (including via ECMP=
)
from the PLR via a path subject to one of the above exclusions.
The method of determining the exclusion is a local matter.

[CB] I think the following text explains the expected behavior more clearly=
.

"Since normal IGP routing takes into account the IS-IS overload bit , RFC 3=
137, and costing out of links, the forward SPFs performed by the PLR rooted=
 at neighbors of the PLR also need to take this into account.  Therefore a =
repair tunnel path from a neighbor of the PLR to a repair tunnel endpoint w=
ill generally avoid the nodes and links excluded by the IGP overload/costin=
g out rules.  However, there are two situations where this behavior may res=
ult in a repair path traversing  a link or router that should be excluded.

1) The first hop on the repair tunnel path (from the PLR to a direct neighb=
or) does not necessarily follow the IGP shortest path.   Therefore, the PLR=
 MUST NOT use a repair tunnel path whose first hop is along a link whose co=
st or reverse cost is LSInfinity (for OSPF) or the maximum cost (for IS-IS)=
 or, has the overload bit set (for IS-IS).

2) The IS-IS overload bit and the mechanism of RFC 3137 only prevent transi=
t traffic from traversing a node.  It does not prevent traffic destined to =
a node.  So the per-neighbor forwards SPFs using standard IGP overload rule=
s will not prevent  a PLR from choosing a repair tunnel endpoint that is ad=
vertising a desire to not carry transit traffic.  Therefore, the PLR MUST N=
OT use a repair tunnel endpoint with the IS-IS overload bit set (or all out=
going interfaces with cost set to LSInfinity for OSPF).  "

2) The current document doesn't appear to say anything about the expected b=
ehavior of RLFA when the IGP has multiple areas or levels.  It would be use=
ful to either address this topic, or explicitly narrow the scope of the doc=
ument to describing the behavior when the IGP has a single area or level.
I have added to the bottom of the intro:

This document considers the case when the repair path is confined to either=
 a
single area or to the level two routing domain. In all other cases, the cho=
sen
PQ node should be regarded as a tunnel adjacency of the repairing node,
and the considerations  described in Section 6 of [RFC5286] taken
into account.

- Stewart

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	border:none;
	padding:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">See inline [CB] for comme=
nt on the new section 4.4.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Chris<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><sp=
an style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:windowtext"> Stewart Bryant [mailto:stbryant@cisco.com]
<br>
<b>Sent:</b> Friday, May 23, 2014 10:11 AM<br>
<b>To:</b> Chris Bowers; rtgwg@ietf.org<br>
<b>Subject:</b> Re: comments on draft-ietf-rtgwg-remote-lfa-05<o:p></o:p></=
span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On 23/05/2014 13:43, Chris Bowers wrote:<o:p></o:p><=
/p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Authors,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Below are two comments on draft-ietf-rt=
gwg-remote-lfa-05.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">1) A section should be added to the doc=
ument clarifying what the expected behavior is for RLFA when routers advert=
ise themselves as not desiring to carry transit traffic
 or links have been costed out.&nbsp;&nbsp;&nbsp; RFC5286 has a useful sect=
ion on this topic entitled &#8220;Interactions with IS-IS Overload, RFC 313=
7, and Costed Out Links&#8221;.&nbsp; The current document would benefit fr=
om additional clarity in this topic.<o:p></o:p></span></p>
</div>
</blockquote>
<p class=3D"MsoNormal">New section 4.4.<br>
<br>
The consideration concerning interactions with IS-IS Overload, [RFC3137], <=
br>
and costed out links as described in [RFC5286] apply. In selecting a PQ <br=
>
node a PLR MUST exclude any candidate that is reachable (including via ECMP=
) <br>
from the PLR via a path subject to one of the above exclusions. <br>
The method of determining the exclusion is a local matter.<br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">[CB] I think the followin=
g text explains the expected behavior more clearly.&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8220;Since normal IGP r=
outing takes into account the IS-IS overload bit , RFC 3137, and costing ou=
t of links, the forward SPFs performed by the PLR rooted at neighbors
 of the PLR also need to take this into account.&nbsp; Therefore a repair t=
unnel path from a neighbor of the PLR to a repair tunnel endpoint will gene=
rally avoid the nodes and links excluded by the IGP overload/costing out ru=
les.&nbsp; However, there are two situations
 where this behavior may result in a repair path traversing&nbsp; a link or=
 router that should be excluded.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">1) The first hop on the r=
epair tunnel path (from the PLR to a direct neighbor) does not necessarily =
follow the IGP shortest path.&nbsp;&nbsp; Therefore, the PLR MUST
 NOT use a repair tunnel path whose first hop is along a link whose cost or=
 reverse cost is LSInfinity (for OSPF) or the maximum cost (for IS-IS) or, =
has the overload bit set (for IS-IS).&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">2) The IS-IS overload bit=
 and the mechanism of RFC 3137 only prevent transit traffic from traversing=
 a node.&nbsp; It does not prevent traffic destined to a node.&nbsp;
 So the per-neighbor forwards SPFs using standard IGP overload rules will n=
ot prevent&nbsp; a PLR from choosing a repair tunnel endpoint that is adver=
tising a desire to not carry transit traffic.&nbsp; Therefore, the PLR MUST=
 NOT use a repair tunnel endpoint with the
 IS-IS overload bit set (or all outgoing interfaces with cost set to LSInfi=
nity for OSPF).&nbsp; &#8220;<o:p></o:p></span></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">2) The current document doesn&#8217;t a=
ppear to say anything about the expected behavior of RLFA when the IGP has =
multiple areas or levels.&nbsp; It would be useful to either address
 this topic, or explicitly narrow the scope of the document to describing t=
he behavior when the IGP has a single area or level.&nbsp;
<o:p></o:p></span></p>
</div>
</blockquote>
<p class=3D"MsoNormal">I have added to the bottom of the intro:<br>
<br>
This document considers the case when the repair path is confined to either=
 a <br>
single area or to the level two routing domain. In all other cases, the cho=
sen <br>
PQ node should be regarded as a tunnel adjacency of the repairing node, <br=
>
and the considerations&nbsp; described in Section 6 of [RFC5286] taken <br>
into account.<br>
<br>
- Stewart<o:p></o:p></p>
</div>
</body>
</html>

--_000_4e22fad75d914bb3bb19bae69647d259BLUPR05MB292namprd05pro_--


From nobody Fri May 30 01:11:14 2014
Return-Path: <stephane.litkowski@orange.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FB1B1A0351 for <rtgwg@ietfa.amsl.com>; Fri, 30 May 2014 01:11:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4M1jMjhPrqxg for <rtgwg@ietfa.amsl.com>; Fri, 30 May 2014 01:11:07 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9437A1A00AA for <rtgwg@ietf.org>; Fri, 30 May 2014 01:11:05 -0700 (PDT)
Received: from omfeda05.si.francetelecom.fr (unknown [xx.xx.xx.198]) by omfeda14.si.francetelecom.fr (ESMTP service) with ESMTP id 1C5A72AC378 for <rtgwg@ietf.org>; Fri, 30 May 2014 10:11:00 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.56]) by omfeda05.si.francetelecom.fr (ESMTP service) with ESMTP id F1F51180073 for <rtgwg@ietf.org>; Fri, 30 May 2014 10:10:59 +0200 (CEST)
Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.246]) by OPEXCLILH04.corporate.adroot.infra.ftgroup ([10.114.31.56]) with mapi id 14.03.0181.006; Fri, 30 May 2014 10:10:57 +0200
From: <stephane.litkowski@orange.com>
To: DECRAENE Bruno IMT/OLN <bruno.decraene@orange.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
Thread-Topic: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
Thread-Index: AQHPefOyESAdv20HH02eg6JxXc256ZtVlPwAgAALmjCAAybIQA==
Date: Fri, 30 May 2014 08:10:57 +0000
Message-ID: <24768_1401437460_53883D14_24768_13993_1_bcbdecf8-5824-42fb-9fe8-473cd2b175d3@OPEXCLILH04.corporate.adroot.infra.ftgroup>
References: <20140527213608.31267.80528.idtracker@ietfa.amsl.com> <9235_1401261459_53858D93_9235_2274_1_9E32478DFA9976438E7A22F69B08FF92011FDB@OPEXCLILM34.corporate.adroot.infra.ftgroup> <53C29892C857584299CBF5D05346208A0714E281@PEXCVZYM11.corporate.adroot.infra.ftgroup>
In-Reply-To: <53C29892C857584299CBF5D05346208A0714E281@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.5.30.3920
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/CgBNXJc2qOX0qKe9ef2mtmJf9Kc
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 May 2014 08:11:13 -0000

Hi Bruno

Answers inline ...


-----Original Message-----
From: DECRAENE Bruno IMT/OLN=20
Sent: Wednesday, May 28, 2014 10:21
To: LITKOWSKI Stephane SCE/IBNF; rtgwg@ietf.org
Subject: RE: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt

Hi St=E9phane,

Looks good, thanks.

I have a question related to object "ipFrrAltType"

>       loopFreeRemote (4), -- remote loop free alternate
>       loopFreeTunnel (5), -- loop free alternate using a configured=20
> tunnel

>       loopFreeRemote : remote LFA as described in draft-ietf-rtgwg-remote=
-lfa
>       loopFreeTunnel : remote LFA reachable through a RSVP-TE or GRE=20
> tunnel

It's not clear to me what exactly is the difference between loopFreeRemote =
and loopFreeTunnel:
Is this the type of tunnels: explicitly routed (i.e. RSVP-TE) vs following =
the shortest path (i.e. LDP, GRE, draft-ietf-rtgwg-remote-lfa Is this the d=
etermination of the required tunnels: automatically computed (i.e. draft-ie=
tf-rtgwg-remote-lfa, automatic RSVP-TE LSP bypass tunnel to the next-hop) v=
s configured.



Current description seems to mix both aspects.

[SLI] Good point ! :) I had some concern to express this ... the idea was t=
o differentiate rLFA alternates (based on the draft) from other tunneled al=
ternate. If you have a good way to express it , I will take it ...

> loopFreeTI : remote LFA reachable through a SPRING tunnel
To some expect, the question also applies to "loopFreeTI" where there is a =
mix of FRR algorithm (how is the alternate computed i.e. TI FRR) and the ty=
pe of tunnels to reach the alternate (here SPRING tunnels, while in theory =
the alternate could equally be reached using a RSVP-TE+ T-LDP tunnels

I'm open to any solution. IMHO the description of the FRR algo is the more =
important:
      ipFrrAltType OBJECT-TYPE
          SYNTAX   INTEGER {
                      other             (1), -- type not defined
                      equalCost         (2), -- primary path
                      loopFreeConnected          (3), -- loop free connecte=
d alternate (LFA)
                      loopFreeRemote    (4), -- remote loop free alternate =
(RLFA)
                      loopFreeNH    (5), -- loop free alternate using a tun=
nel toward the Next Hop
                      loopFreeNNH    (6), -- loop free alternate using a tu=
nnel toward the Next Next Hop
                      loopFreeTI        (7), -- loop free alternate using t=
opology independent algorithm
                      mrt               (8)  -- Maximally Redundant Trees
                   }

[SLI] Agree, but in your proposal what is exactly loopFreeNH and loopFreeNN=
H ?

If you believe that we also need the type of tunnels/forwarding infrastruct=
ure, another object could be added
      ipFrrTunnType OBJECT-TYPE
          SYNTAX   INTEGER {
                      other             (1), -- type not defined
                      LDP         (2)
                      IP          (3),  GRE, L2TP...
                      RSVP-TE   (4)
                      SPRING MPLS  (5)
                      SPRING IPv6  (6)
                      Multi-topology (7)
                   }

[SLI] Yes , this may be very interesting, I will add it.=20


Bruno

> -----Original Message-----
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of=20
> stephane.litkowski@orange.com
> Sent: Wednesday, May 28, 2014 9:18 AM
> To: rtgwg@ietf.org
> Subject: FW: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
>=20
> Hi all,
>=20
> To followup discussion in London, I updated the IP FRR MIB draft with=20
> some new things :
> - different objects for IPv4 and IPv6 protection stats
> - Interface configuration table
> - IPFRR instance table as we may expect to have multiple flavors=20
> running on a common node
> - Protectstats per instance table.
> - Few other things
>=20
> Feel free to comment and propose addings/corrections.
>=20
>=20
> Stephane
>=20
>=20
>=20
> -----Original Message-----
> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of=20
> internet-drafts@ietf.org
> Sent: Tuesday, May 27, 2014 23:36
> To: i-d-announce@ietf.org
> Cc: rtgwg@ietf.org
> Subject: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>  This draft is a work item of the Routing Area Working Group Working=20
> Group of the IETF.
>=20
>         Title           : IP MIB for IP Fast-Reroute
>         Authors         : Alia Atlas
>                           Cisco Systems
>                           John Flick
>                           Stephane Litkowski
> 	Filename        : draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
> 	Pages           : 26
> 	Date            : 2014-05-27
>=20
> Abstract:
>    This draft defines a portion of the Management Information Base (MIB)
>    for use with network management protocols in the Internet community.
>    In particular, it describes managed objects relevant for IP routes
>    using IP Fast-Reroute [RFC5714]
>=20
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-rtgwg-ipfrr-ip-mib/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-rtgwg-ipfrr-ip-mib-03
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-rtgwg-ipfrr-ip-mib-03
>=20
>=20
> Please note that it may take a couple of minutes from the time of=20
> submission until the htmlized version and diff are available at tools.iet=
f.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or=20
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
> __________________________________________________________
> __________________________________________________________
> _____
>=20
> Ce message et ses pieces jointes peuvent contenir des informations=20
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses,=20
> exploites ou copies sans autorisation. Si vous avez recu ce message=20
> par erreur, veuillez le signaler a l'expediteur et le detruire ainsi=20
> que les pieces jointes. Les messages electroniques etant susceptibles=20
> d'alteration, Orange decline toute responsabilite si ce message a ete alt=
ere, deforme ou falsifie. Merci.
>=20
> This message and its attachments may contain confidential or=20
> privileged information that may be protected by law; they should not=20
> be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and=20
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have=20
> been modified, changed or falsified.
> Thank you.
>=20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Fri May 30 05:28:13 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDBFE1A6F6D for <rtgwg@ietfa.amsl.com>; Fri, 30 May 2014 05:28:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.151
X-Spam-Level: 
X-Spam-Status: No, score=-10.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f2G-HBvXpuIz for <rtgwg@ietfa.amsl.com>; Fri, 30 May 2014 05:28:09 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA1211A04AF for <rtgwg@ietf.org>; Fri, 30 May 2014 05:28:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15088; q=dns/txt; s=iport; t=1401452885; x=1402662485; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to; bh=e0S2iBqIciE6XuVB+dEypz1yz67Nsp+q2aDsIAoz8Sg=; b=lN/s5MYQJKvbrWOT2276WhtGoA19o8vAej/++ya29G7H68R1m1fct3as Mc6S4VwA1/n7+28BlLyc4xQM/25EW9tWQGpzoMnrtZY6zUmHGXa+VqLsn ztfdyAI2FrNpnbxi1MCwavjaXB4q02fn7uNnrhDD4nbUlEZqRtwRpxvf9 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai8FACt4iFOtJssW/2dsb2JhbABZgkKBF1XCPQGBH3SCJQEBAQQtSxELDgMEAQEBCQwKCAcJAwIBAgE0CQgGAQwGAgEBiD4NuGudcheOWAEKhDYEmXqTLIM5aw
X-IronPort-AV: E=Sophos; i="4.98,941,1392163200"; d="scan'208,217"; a="63658323"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 30 May 2014 12:28:02 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s4UCS0AG005711 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 May 2014 12:28:02 GMT
Received: from STBRYANT-M-R010.CISCO.COM (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s4UCRxm8012968; Fri, 30 May 2014 13:28:00 +0100 (BST)
Message-ID: <53887951.1060808@cisco.com>
Date: Fri, 30 May 2014 13:28:01 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Chris Bowers <cbowers@juniper.net>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: comments on draft-ietf-rtgwg-remote-lfa-05
References: <fb486e33b3a24b57abe8968004cf625c@BLUPR05MB292.namprd05.prod.outlook.com> <537F6504.3010105@cisco.com> <4e22fad75d914bb3bb19bae69647d259@BLUPR05MB292.namprd05.prod.outlook.com>
In-Reply-To: <4e22fad75d914bb3bb19bae69647d259@BLUPR05MB292.namprd05.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------030503010201070704040009"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/mgwu6tTzSBJwJkkyEAQQlNv9u_8
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 May 2014 12:28:12 -0000

This is a multi-part message in MIME format.
--------------030503010201070704040009
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Chris

I would like to take this together with final review coments
from the WGCs

Stewart

On 28/05/2014 19:54, Chris Bowers wrote:
>
> See inline [CB] for comment on the new section 4.4.
>
> Chris
>
> *From:*Stewart Bryant [mailto:stbryant@cisco.com]
> *Sent:* Friday, May 23, 2014 10:11 AM
> *To:* Chris Bowers; rtgwg@ietf.org
> *Subject:* Re: comments on draft-ietf-rtgwg-remote-lfa-05
>
> On 23/05/2014 13:43, Chris Bowers wrote:
>
>     Authors,
>
>     Below are two comments on draft-ietf-rtgwg-remote-lfa-05.
>
>     1) A section should be added to the document clarifying what the
>     expected behavior is for RLFA when routers advertise themselves as
>     not desiring to carry transit traffic or links have been costed
>     out.    RFC5286 has a useful section on this topic entitled
>     "Interactions with IS-IS Overload, RFC 3137, and Costed Out
>     Links".  The current document would benefit from additional
>     clarity in this topic.
>
> New section 4.4.
>
> The consideration concerning interactions with IS-IS Overload, [RFC3137],
> and costed out links as described in [RFC5286] apply. In selecting a PQ
> node a PLR MUST exclude any candidate that is reachable (including via 
> ECMP)
> from the PLR via a path subject to one of the above exclusions.
> The method of determining the exclusion is a local matter.
>
> [CB] I think the following text explains the expected behavior more 
> clearly.
>
> "Since normal IGP routing takes into account the IS-IS overload bit , 
> RFC 3137, and costing out of links, the forward SPFs performed by the 
> PLR rooted at neighbors of the PLR also need to take this into 
> account.  Therefore a repair tunnel path from a neighbor of the PLR to 
> a repair tunnel endpoint will generally avoid the nodes and links 
> excluded by the IGP overload/costing out rules.  However, there are 
> two situations where this behavior may result in a repair path 
> traversing  a link or router that should be excluded.
>
> 1) The first hop on the repair tunnel path (from the PLR to a direct 
> neighbor) does not necessarily follow the IGP shortest path.   
> Therefore, the PLR MUST NOT use a repair tunnel path whose first hop 
> is along a link whose cost or reverse cost is LSInfinity (for OSPF) or 
> the maximum cost (for IS-IS) or, has the overload bit set (for IS-IS).
>
> 2) The IS-IS overload bit and the mechanism of RFC 3137 only prevent 
> transit traffic from traversing a node.  It does not prevent traffic 
> destined to a node.  So the per-neighbor forwards SPFs using standard 
> IGP overload rules will not prevent  a PLR from choosing a repair 
> tunnel endpoint that is advertising a desire to not carry transit 
> traffic. Therefore, the PLR MUST NOT use a repair tunnel endpoint with 
> the IS-IS overload bit set (or all outgoing interfaces with cost set 
> to LSInfinity for OSPF).  "
>
>     2) The current document doesn't appear to say anything about the
>     expected behavior of RLFA when the IGP has multiple areas or
>     levels.  It would be useful to either address this topic, or
>     explicitly narrow the scope of the document to describing the
>     behavior when the IGP has a single area or level.
>
> I have added to the bottom of the intro:
>
> This document considers the case when the repair path is confined to 
> either a
> single area or to the level two routing domain. In all other cases, 
> the chosen
> PQ node should be regarded as a tunnel adjacency of the repairing node,
> and the considerations  described in Section 6 of [RFC5286] taken
> into account.
>
> - Stewart
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


--------------030503010201070704040009
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Chris<br>
      <br>
      I would like to take this together with final review coments<br>
      from the WGCs<br>
      <br>
      Stewart<br>
      <br>
      On 28/05/2014 19:54, Chris Bowers wrote:<br>
    </div>
    <blockquote
cite="mid:4e22fad75d914bb3bb19bae69647d259@BLUPR05MB292.namprd05.prod.outlook.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	border:none;
	padding:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">See
            inline [CB] for comment on the new section 4.4.
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Chris<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #E1E1E1
            1.0pt;padding:3.0pt 0in 0in 0in">
            <p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:windowtext">
                Stewart Bryant [<a class="moz-txt-link-freetext" href="mailto:stbryant@cisco.com">mailto:stbryant@cisco.com</a>]
                <br>
                <b>Sent:</b> Friday, May 23, 2014 10:11 AM<br>
                <b>To:</b> Chris Bowers; <a class="moz-txt-link-abbreviated" href="mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
                <b>Subject:</b> Re: comments on
                draft-ietf-rtgwg-remote-lfa-05<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <div>
          <p class="MsoNormal">On 23/05/2014 13:43, Chris Bowers wrote:<o:p></o:p></p>
        </div>
        <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
          <div>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Authors,<o:p></o:p></span></p>
          </div>
          <div>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
          </div>
          <div>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Below
                are two comments on draft-ietf-rtgwg-remote-lfa-05.<o:p></o:p></span></p>
          </div>
          <div>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
          </div>
          <div>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">1)
                A section should be added to the document clarifying
                what the expected behavior is for RLFA when routers
                advertise themselves as not desiring to carry transit
                traffic or links have been costed out.&nbsp;&nbsp;&nbsp; RFC5286 has a
                useful section on this topic entitled &#8220;Interactions with
                IS-IS Overload, RFC 3137, and Costed Out Links&#8221;.&nbsp; The
                current document would benefit from additional clarity
                in this topic.<o:p></o:p></span></p>
          </div>
        </blockquote>
        <p class="MsoNormal">New section 4.4.<br>
          <br>
          The consideration concerning interactions with IS-IS Overload,
          [RFC3137], <br>
          and costed out links as described in [RFC5286] apply. In
          selecting a PQ <br>
          node a PLR MUST exclude any candidate that is reachable
          (including via ECMP) <br>
          from the PLR via a path subject to one of the above
          exclusions. <br>
          The method of determining the exclusion is a local matter.<br>
          <br>
          <o:p></o:p></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[CB]
            I think the following text explains the expected behavior
            more clearly.&nbsp;
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8220;Since
            normal IGP routing takes into account the IS-IS overload bit
            , RFC 3137, and costing out of links, the forward SPFs
            performed by the PLR rooted at neighbors of the PLR also
            need to take this into account.&nbsp; Therefore a repair tunnel
            path from a neighbor of the PLR to a repair tunnel endpoint
            will generally avoid the nodes and links excluded by the IGP
            overload/costing out rules.&nbsp; However, there are two
            situations where this behavior may result in a repair path
            traversing&nbsp; a link or router that should be excluded.
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">1)
            The first hop on the repair tunnel path (from the PLR to a
            direct neighbor) does not necessarily follow the IGP
            shortest path.&nbsp;&nbsp; Therefore, the PLR MUST NOT use a repair
            tunnel path whose first hop is along a link whose cost or
            reverse cost is LSInfinity (for OSPF) or the maximum cost
            (for IS-IS) or, has the overload bit set (for IS-IS).&nbsp;
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">2)
            The IS-IS overload bit and the mechanism of RFC 3137 only
            prevent transit traffic from traversing a node.&nbsp; It does not
            prevent traffic destined to a node.&nbsp; So the per-neighbor
            forwards SPFs using standard IGP overload rules will not
            prevent&nbsp; a PLR from choosing a repair tunnel endpoint that
            is advertising a desire to not carry transit traffic.&nbsp;
            Therefore, the PLR MUST NOT use a repair tunnel endpoint
            with the IS-IS overload bit set (or all outgoing interfaces
            with cost set to LSInfinity for OSPF).&nbsp; &#8220;<o:p></o:p></span></p>
        <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
          <div>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
          </div>
          <div>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">2)
                The current document doesn&#8217;t appear to say anything
                about the expected behavior of RLFA when the IGP has
                multiple areas or levels.&nbsp; It would be useful to either
                address this topic, or explicitly narrow the scope of
                the document to describing the behavior when the IGP has
                a single area or level.&nbsp;
                <o:p></o:p></span></p>
          </div>
        </blockquote>
        <p class="MsoNormal">I have added to the bottom of the intro:<br>
          <br>
          This document considers the case when the repair path is
          confined to either a <br>
          single area or to the level two routing domain. In all other
          cases, the chosen <br>
          PQ node should be regarded as a tunnel adjacency of the
          repairing node, <br>
          and the considerations&nbsp; described in Section 6 of [RFC5286]
          taken <br>
          into account.<br>
          <br>
          - Stewart<o:p></o:p></p>
      </div>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

<a class="moz-txt-link-freetext" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a>

</pre>
  </body>
</html>

--------------030503010201070704040009--


From nobody Fri May 30 05:35:58 2014
Return-Path: <bruno.decraene@orange.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDAD11A6F7F for <rtgwg@ietfa.amsl.com>; Fri, 30 May 2014 05:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o9MKlP19nhld for <rtgwg@ietfa.amsl.com>; Fri, 30 May 2014 05:35:53 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D73751A6F79 for <rtgwg@ietf.org>; Fri, 30 May 2014 05:35:52 -0700 (PDT)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda11.si.francetelecom.fr (ESMTP service) with ESMTP id 6D5E21B8230 for <rtgwg@ietf.org>; Fri, 30 May 2014 14:35:47 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id 50EA7384088 for <rtgwg@ietf.org>; Fri, 30 May 2014 14:35:47 +0200 (CEST)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0181.006; Fri, 30 May 2014 14:35:46 +0200
From: <bruno.decraene@orange.com>
To: LITKOWSKI Stephane SCE/IBNF <stephane.litkowski@orange.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
Thread-Topic: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
Thread-Index: AQHPefOyESAdv20HH02eg6JxXc256ZtVlPwAgAALmjCAAybIQIAASleA
Date: Fri, 30 May 2014 12:35:45 +0000
Message-ID: <29605_1401453347_53887B23_29605_1052_1_50d76f4f-2719-4c5e-a3de-7865ec549cc6@PEXCVZYH02.corporate.adroot.infra.ftgroup>
References: <20140527213608.31267.80528.idtracker@ietfa.amsl.com> <9235_1401261459_53858D93_9235_2274_1_9E32478DFA9976438E7A22F69B08FF92011FDB@OPEXCLILM34.corporate.adroot.infra.ftgroup> <53C29892C857584299CBF5D05346208A0714E281@PEXCVZYM11.corporate.adroot.infra.ftgroup> <9E32478DFA9976438E7A22F69B08FF92012715@OPEXCLILM34.corporate.adroot.infra.ftgroup>
In-Reply-To: <9E32478DFA9976438E7A22F69B08FF92012715@OPEXCLILM34.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.5.13.75120
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/AXyLmPoWxGDomLm27SQb26LFhn8
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 May 2014 12:35:55 -0000

Hi St=E9phane,

Please see 1 point inline

=20
> Hi St=E9phane,
>=20
> Looks good, thanks.
>=20
> I have a question related to object "ipFrrAltType"
>=20
> >       loopFreeRemote (4), -- remote loop free alternate
> >       loopFreeTunnel (5), -- loop free alternate using a configured
> > tunnel
>=20
> >       loopFreeRemote : remote LFA as described in draft-ietf-rtgwg-remo=
te-
> lfa
> >       loopFreeTunnel : remote LFA reachable through a RSVP-TE or GRE
> > tunnel
>=20
> It's not clear to me what exactly is the difference between loopFreeRemote
> and loopFreeTunnel:
> Is this the type of tunnels: explicitly routed (i.e. RSVP-TE) vs followin=
g the
> shortest path (i.e. LDP, GRE, draft-ietf-rtgwg-remote-lfa Is this the
> determination of the required tunnels: automatically computed (i.e. draft-
> ietf-rtgwg-remote-lfa, automatic RSVP-TE LSP bypass tunnel to the next-
> hop) vs configured.
>=20
>=20
>=20
> Current description seems to mix both aspects.
>=20
> [SLI] Good point ! :) I had some concern to express this ... the idea was=
 to
> differentiate rLFA alternates (based on the draft) from other tunneled
> alternate. If you have a good way to express it , I will take it ...
>=20
> > loopFreeTI : remote LFA reachable through a SPRING tunnel
> To some expect, the question also applies to "loopFreeTI" where there is a
> mix of FRR algorithm (how is the alternate computed i.e. TI FRR) and the =
type
> of tunnels to reach the alternate (here SPRING tunnels, while in theory t=
he
> alternate could equally be reached using a RSVP-TE+ T-LDP tunnels
>=20
> I'm open to any solution. IMHO the description of the FRR algo is the more
> important:
>       ipFrrAltType OBJECT-TYPE
>           SYNTAX   INTEGER {
>                       other             (1), -- type not defined
>                       equalCost         (2), -- primary path
>                       loopFreeConnected          (3), -- loop free connec=
ted alternate
> (LFA)
>                       loopFreeRemote    (4), -- remote loop free alternat=
e (RLFA)
>                       loopFreeNH    (5), -- loop free alternate using a t=
unnel toward the
> Next Hop
>                       loopFreeNNH    (6), -- loop free alternate using a =
tunnel toward
> the Next Next Hop
>                       loopFreeTI        (7), -- loop free alternate using=
 topology
> independent algorithm
>                       mrt               (8)  -- Maximally Redundant Trees
>                    }
>=20
> [SLI] Agree, but in your proposal what is exactly loopFreeNH and
> loopFreeNNH ?

loopFreeNH or may be "Next Hop" :  Next Hop (5), -- loop free alternate usi=
ng an explicitly routed  tunnel toward the original Next Hop (link protecti=
on only)
This typically what is offered by a single hop RSVP-TE LSP over the protect=
ed link.

NextNextHop    (5), -- loop free alternate using an explicitly routed  tunn=
el toward the original Next Next Hop

By "original Next Hop" I mean the Next Hop in the current IGP topology (aka=
 "old" during FRR activation/pre failure)

Thanks,
Bruno

=20
> If you believe that we also need the type of tunnels/forwarding
> infrastructure, another object could be added
>       ipFrrTunnType OBJECT-TYPE
>           SYNTAX   INTEGER {
>                       other             (1), -- type not defined
>                       LDP         (2)
>                       IP          (3),  GRE, L2TP...
>                       RSVP-TE   (4)
>                       SPRING MPLS  (5)
>                       SPRING IPv6  (6)
>                       Multi-topology (7)
>                    }
>=20
> [SLI] Yes , this may be very interesting, I will add it.
>=20
>=20
> Bruno
>=20
> > -----Original Message-----
> > From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of
> > stephane.litkowski@orange.com
> > Sent: Wednesday, May 28, 2014 9:18 AM
> > To: rtgwg@ietf.org
> > Subject: FW: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
> >
> > Hi all,
> >
> > To followup discussion in London, I updated the IP FRR MIB draft with
> > some new things :
> > - different objects for IPv4 and IPv6 protection stats
> > - Interface configuration table
> > - IPFRR instance table as we may expect to have multiple flavors
> > running on a common node
> > - Protectstats per instance table.
> > - Few other things
> >
> > Feel free to comment and propose addings/corrections.
> >
> >
> > Stephane
> >
> >
> >
> > -----Original Message-----
> > From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
> > internet-drafts@ietf.org
> > Sent: Tuesday, May 27, 2014 23:36
> > To: i-d-announce@ietf.org
> > Cc: rtgwg@ietf.org
> > Subject: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
> >
> >
> > 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 MIB for IP Fast-Reroute
> >         Authors         : Alia Atlas
> >                           Cisco Systems
> >                           John Flick
> >                           Stephane Litkowski
> > 	Filename        : draft-ietf-rtgwg-ipfrr-ip-mib-03.txt
> > 	Pages           : 26
> > 	Date            : 2014-05-27
> >
> > Abstract:
> >    This draft defines a portion of the Management Information Base (MIB)
> >    for use with network management protocols in the Internet community.
> >    In particular, it describes managed objects relevant for IP routes
> >    using IP Fast-Reroute [RFC5714]
> >
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-rtgwg-ipfrr-ip-mib/
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-ietf-rtgwg-ipfrr-ip-mib-03
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-rtgwg-ipfrr-ip-mib-03
> >
> >
> > Please note that it may take a couple of minutes from the time of
> > submission until the htmlized version and diff are available at tools.i=
etf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html or
> > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> >
> __________________________________________________________
> >
> __________________________________________________________
> > _____
> >
> > Ce message et ses pieces jointes peuvent contenir des informations
> > confidentielles ou privilegiees et ne doivent donc pas etre diffuses,
> > exploites ou copies sans autorisation. Si vous avez recu ce message
> > par erreur, veuillez le signaler a l'expediteur et le detruire ainsi
> > que les pieces jointes. Les messages electroniques etant susceptibles
> > d'alteration, Orange decline toute responsabilite si ce message a ete a=
ltere,
> deforme ou falsifie. Merci.
> >
> > This message and its attachments may contain confidential or
> > privileged information that may be protected by law; they should not
> > be distributed, used or copied without authorisation.
> > If you have received this email in error, please notify the sender and
> > delete this message and its attachments.
> > As emails may be altered, Orange is not liable for messages that have
> > been modified, changed or falsified.
> > Thank you.
> >
> > _______________________________________________
> > rtgwg mailing list
> > rtgwg@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtgwg

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.

