
From nobody Wed Apr  1 01:11:56 2015
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 3666E1A8A62 for <rtgwg@ietfa.amsl.com>; Wed,  1 Apr 2015 01:11:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 yWvtz0ZSY8jP for <rtgwg@ietfa.amsl.com>; Wed,  1 Apr 2015 01:11:50 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32FA81A8A59 for <rtgwg@ietf.org>; Wed,  1 Apr 2015 01:11:49 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 42D303B43C1; Wed,  1 Apr 2015 10:11:47 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 14A854C098; Wed,  1 Apr 2015 10:11: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.0224.002; Wed, 1 Apr 2015 10:11:46 +0200
From: <bruno.decraene@orange.com>
To: Chris Bowers <cbowers@juniper.net>, "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>, Alia Atlas <akatlas@juniper.net>, Robert Kebler <rkebler@juniper.net>, "Gabor.Sandor.Enyedi@ericsson.com" <Gabor.Sandor.Enyedi@ericsson.com>, "Andras.Csaszar@ericsson.com" <Andras.Csaszar@ericsson.com>, "jeff.tantsura@ericsson.com" <jeff.tantsura@ericsson.com>, "russw@riw.us" <russw@riw.us>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Topic: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Index: AdBohapCLAg3Un3wSOKmk0bREwcgiQDiTs4wABBanbA=
Date: Wed, 1 Apr 2015 08:11:45 +0000
Message-ID: <31522_1427875907_551BA843_31522_7672_1_53C29892C857584299CBF5D05346208A0EB8AE1B@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <327562D94EA7BF428CD805F338C31EF04FB31080@NKGEML512-MBS.china.huawei.com> <BLUPR05MB292105B133237D6FF24FD1CA9F30@BLUPR05MB292.namprd05.prod.outlook.com>
In-Reply-To: <BLUPR05MB292105B133237D6FF24FD1CA9F30@BLUPR05MB292.namprd05.prod.outlook.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.6]
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A0EB8AE1BPEXCVZYM11corpo_"
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.4.1.43619
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/Vw6eg2qakEGkTDjRmP1yuAeFmoQ>
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, 01 Apr 2015 08:11:55 -0000

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

Hi Chris,

Thanks for the addition.
Please see inline some comments. [Bruno]

Thanks,
Regards,
Bruno

From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Chris Bowers
Sent: Wednesday, April 01, 2015 3:10 AM
To: Anil Kumar S N (VRP Network BL); Alia Atlas; Robert Kebler; Gabor.Sando=
r.Enyedi@ericsson.com; Andras.Csaszar@ericsson.com; jeff.tantsura@ericsson.=
com; russw@riw.us; rtgwg@ietf.org
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Anil,

Thanks for your input and proposed text.  I added the text below (which is =
a slightly modified version of your proposed text) to the most recent versi=
on which is being maintained at:
https://github.com/cbowers/draft-ietf-rtgwg-mrt-frr-architecture

Tell me if you are OK with the final sentence that I added as well, or you =
can propose some other wording.

Thanks,
Chris

   TI-LFA:    Topology Independent Loop-free Alternate Fast Re-route
      (TI-LFA) [I-D.francois-spring-segment-routing-ti-lfa] aims to
      provide link and node protection of node and adjacency segments
      within the Segment Routing (SR) framework.  It has improved
      coverage over LFA and Remote LFA for link and node protection and
      also guarantees complete coverage.
[Bruno] The last sentence could probably be shortened by only keeping the l=
ast part. "It guarantees complete coverage"


The trade-off of looping
      traffic to improve coverage is still made.
[Bruno] I'm not sure to see what you mean. Contrary to LFA & RLFA, I don't =
think TI-LFA makes such tradeoff.

  The computation
      required is quite high with added complexity.
[Bruno] As in the RLFA description you have made the distinction between li=
nk and node protection, it would be fair to do the same for TI-LFA. (Link p=
rotection computation is much easier)

  TI-LFA is supported
      only for the MPLS data plane due to the requirement for the PLR to
      impose an MPLS label stack on link failure.  On certain topologies
      the label stack size can grow significantly based on repair path.
[Bruno] I agree for node failure. For link failure, this is more debatable =
as compared to RLFA it may require at most 1 additional label. (assuming sy=
mmetric link costs)

      Note that TI-LFA requires shortest path forwarding based on SR
      Node-SIDs, as opposed to LDP labels, in order to construct label
      stacks for backups paths without relying on a large number of
      targeted LDP sessions to learn remote FEC-label bindings.
[Bruno] It also requires Adj-SID (in order to provide 100% coverage).


From: Anil Kumar S N (VRP Network BL) [mailto:anil.sn@huawei.com]
Sent: Saturday, March 28, 2015 8:10 AM
To: Alia Atlas; Robert Kebler; Chris Bowers; Gabor.Sandor.Enyedi@ericsson.c=
om<mailto:Gabor.Sandor.Enyedi@ericsson.com>; Andras.Csaszar@ericsson.com<ma=
ilto:Andras.Csaszar@ericsson.com>; jeff.tantsura@ericsson.com<mailto:jeff.t=
antsura@ericsson.com>; russw@riw.us<mailto:russw@riw.us>; rtgwg@ietf.org<ma=
ilto:rtgwg@ietf.org>
Subject: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Authors,

      In  "comparison of IP/LDP FRR Methods" section of the document , I fe=
el we should add comparison with TI-LFA (draft-francois-spring-segment-rout=
ing-ti-lfa-01) where TI-LFA approach achieves guaranteed coverage  against =
link or node failure, in any IGP network, relying on the  flexibility of SR=
. This will give readers better picture and enables them with more informat=
ion so that they can choose MRT if they feel it suites their requirement be=
tter; compared to IT-LFA...
Changes :

1.  Introduction :

   Other existing or proposed solutions are partial solutions or have
   significant issues, as described below.

                 Summary Comparison of IP/LDP FRR Methods

   +---------+-------------+-------------+-----------------------------+
   |  Method |   Coverage  |  Alternate  |    Computation (in SPFs)    |
   |         |             |   Looping?  |                             |
   +---------+-------------+-------------+-----------------------------+
   | MRT-FRR |     100%    |     None    |         less than 3         |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   |   LFA   |   Partial   |   Possible  |         per neighbor        |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   |  Remote |   Partial   |   Possible  |    per neighbor (link) or   |
   |   LFA   |  Link/Node  |             |  neighbor's neighbor (node) |
   |         |             |             |                             |
   | Not-Via |     100%    |     None    |      per link and node      |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   | TI-LFA  |     100%    |   Possible  |    per neighbor (link) or   |
   |         |  Link/Node  |             |  neighbor's neighbor (node) |
   |         |             |             |                             |
   +---------+-------------+-------------+-----------------------------+

                                  Table 1


   TI-LFA: Topology Independent Loop-free Alternate Fast
   Re-route (TI-LFA), aimed at providing link and node protection of
   node and adjacency segments within the Segment Routing (SR)
   framework [draft-francois-spring-segment-routing-ti-lfa-01].
   Has improved coverage over LFAs and Remote LFA for link and node
   protection and also guarantees complete coverage. The trade-off
   of looping traffic to improve coverage is still made.
  The computation required is quite high with added complexity.
   TI-LFA is supported only MPLS data plane with a requirement to
   carry additional MPLS label stack on the link failure; on certain
   topologies stack size can grow significantly based repair path.

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel



___________________________________________________________________________=
______________________________________________

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.


--_000_53C29892C857584299CBF5D05346208A0EB8AE1BPEXCVZYM11corpo_
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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-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:"Pr\00E9format\00E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:Consolas;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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 lang=3D"FR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Hi Chri=
s,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks =
for the addition.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Please =
see inline some comments. [Bruno]<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks,=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Regards=
,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Bruno<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> rtgwg [m=
ailto:rtgwg-bounces@ietf.org]
<b>On Behalf Of </b>Chris Bowers<br>
<b>Sent:</b> Wednesday, April 01, 2015 3:10 AM<br>
<b>To:</b> Anil Kumar S N (VRP Network BL); Alia Atlas; Robert Kebler; Gabo=
r.Sandor.Enyedi@ericsson.com; Andras.Csaszar@ericsson.com; jeff.tantsura@er=
icsson.com; russw@riw.us; rtgwg@ietf.org<br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Anil,<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks =
for your input and proposed text.&nbsp; I added the text below (which is a =
slightly modified version of your proposed text) to the most recent version=
 which is being maintained at:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><a href=
=3D"https://github.com/cbowers/draft-ietf-rtgwg-mrt-frr-architecture">https=
://github.com/cbowers/draft-ietf-rtgwg-mrt-frr-architecture</a><o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Tell me=
 if you are OK with the final sentence that I added as well, or you can pro=
pose some other wording.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks,=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Chris<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;&nbsp; TI-LFA:&nbsp;&nbsp;&nbsp; Topo=
logy Independent Loop-free Alternate Fast Re-route<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (TI-LFA) [I-=
D.francois-spring-segment-routing-ti-lfa] aims to<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; provide link=
 and node protection of node and adjacency segments<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; within the S=
egment Routing (SR) framework.&nbsp; It has improved<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; coverage ove=
r LFA and Remote LFA for link and node protection and<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; also guarant=
ees complete coverage.&nbsp;<span style=3D"color:#1F497D"><o:p></o:p></span=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 The last sentence could probably be shortened by only keeping the last par=
t. &#8220;It guarantees complete coverage&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">The trade-off of looping<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; traffic to i=
mprove coverage is still made.<span style=3D"color:#1F497D"><o:p></o:p></sp=
an></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 I&#8217;m not sure to see what you mean. Contrary to LFA &amp; RLFA, I don=
&#8217;t think TI-LFA makes such tradeoff.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp; The computation<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; required is =
quite high with added complexity.<span style=3D"color:#1F497D"><o:p></o:p><=
/span></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 As in the RLFA description you have made the distinction between link and =
node protection, it would be fair to do the same for TI-LFA. (Link protecti=
on computation is much easier)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp; TI-LFA is supported<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; only for the=
 MPLS data plane due to the requirement for the PLR to<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; impose an MP=
LS label stack on link failure.&nbsp; On certain topologies<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the label st=
ack size can grow significantly based on repair path.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 I agree for node failure. For link failure, this is more debatable as comp=
ared to RLFA it may require at most 1 additional label. (assuming symmetric=
 link costs)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Note that TI=
-LFA requires shortest path forwarding based on SR<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Node-SIDs, a=
s opposed to LDP labels, in order to construct label<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; stacks for b=
ackups paths without relying on a large number of<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; targeted LDP=
 sessions to learn remote FEC-label bindings.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 It also requires Adj-SID (in order to provide 100% coverage).<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p=
>&nbsp;</o:p></span></b></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> Anil Kumar S N (VRP Network BL) [<a href=3D"mailto:anil.sn@huaw=
ei.com">mailto:anil.sn@huawei.com</a>]
<br>
<b>Sent:</b> Saturday, March 28, 2015 8:10 AM<br>
<b>To:</b> Alia Atlas; Robert Kebler; Chris Bowers; <a href=3D"mailto:Gabor=
.Sandor.Enyedi@ericsson.com">
Gabor.Sandor.Enyedi@ericsson.com</a>; <a href=3D"mailto:Andras.Csaszar@eric=
sson.com">
Andras.Csaszar@ericsson.com</a>; <a href=3D"mailto:jeff.tantsura@ericsson.c=
om">jeff.tantsura@ericsson.com</a>;
<a href=3D"mailto:russw@riw.us">russw@riw.us</a>; <a href=3D"mailto:rtgwg@i=
etf.org">rtgwg@ietf.org</a><br>
<b>Subject:</b> draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p></sp=
an></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi Authors,<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
In &nbsp;&#8220;comparison of IP/LDP FRR Methods&#8221; section of the docu=
ment , I feel we should add comparison with TI-LFA (draft-francois-spring-s=
egment-routing-ti-lfa-01) where TI-LFA approach achieves guaranteed coverag=
e &nbsp;against
 link or node failure, in any IGP network, relying on the&nbsp; flexibility=
 of SR. This will give readers better picture and enables them with more in=
formation so that they can choose MRT if they feel it suites their requirem=
ent better; compared to IT-LFA&#8230;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Changes :<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Arial&quot;,&quot;sans-serif&quot;">1.&nbsp; Introduction :=
</span></b><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; O=
ther existing or proposed solutions are partial solutions or have<o:p></o:p=
></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; s=
ignificant issues, as described below.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; Summary Comparison of IP/LDP FRR Methods<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; &=
#43;---------&#43;-------------&#43;-------------&#43;---------------------=
--------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
&nbsp; Method |&nbsp;&nbsp; Coverage&nbsp; |&nbsp; Alternate&nbsp; |&nbsp;&=
nbsp;&nbsp; Computation (in SPFs)&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"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; Looping?&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;&nb=
sp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; &=
#43;---------&#43;-------------&#43;-------------&#43;---------------------=
--------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
 MRT-FRR |&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbs=
p;&nbsp; None&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; less than 3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"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;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
&nbsp;&nbsp; LFA&nbsp;&nbsp; |&nbsp;&nbsp; Partial&nbsp;&nbsp; |&nbsp;&nbsp=
; Possible&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; per neig=
hbor&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"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;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
&nbsp; Remote |&nbsp;&nbsp; Partial&nbsp;&nbsp; |&nbsp;&nbsp; Possible&nbsp=
; |&nbsp;&nbsp;&nbsp; per neighbor (link) or&nbsp;&nbsp; |<o:p></o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
&nbsp;&nbsp; LFA&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; neighbor's neig=
hbor (node) |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"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;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
 Not-Via |&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbs=
p;&nbsp; None&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; per link an=
d node&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; Link/Node&nbsp; |&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"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;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp; | TI-LFA &nbsp;|&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp=
; |&nbsp; &nbsp;Possible&nbsp; |&nbsp;&nbsp;&nbsp; per neighbor (link) or&n=
bsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp; |&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; Link=
/Node&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; |&nbsp; neighbor's neighbor (node) |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"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;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; &=
#43;---------&#43;-------------&#43;-------------&#43;---------------------=
--------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"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;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Table 1</span><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp; TI-LFA: Topology Independent Loop-free Alternate Fast<o:p></o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp; Re-route (TI-LFA), aimed at providing link and node protection=
 of<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp; node and adjacency segments within the Segment Routing (SR)<o:=
p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp; framework [draft-francois-spring-segment-routing-ti-lfa-01].<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp; &nbsp;Has improved coverage over LFAs and Remote LFA for link and no=
de
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp;&nbsp;protection and also guarantees complete coverage. The tra=
de-off
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp;&nbsp;of looping traffic to improve coverage is still made.<o:p=
></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp;The computation required is quite high with added complexity.<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp; TI-LFA is supported only MPLS data plane with a requirement to
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp;&nbsp;carry additional MPLS label stack on the link failure; on=
 certain<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp; &nbsp;topologies stack size can grow significantly based repair path.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks &amp; Regards<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Anil S N<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&#8220;Be liberal in what you a=
ccept, and conservative in what you send&#8221; - Jon Postel<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

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.
</PRE></body>
</html>

--_000_53C29892C857584299CBF5D05346208A0EB8AE1BPEXCVZYM11corpo_--


From nobody Wed Apr  1 01:12:11 2015
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 C32781A8A51 for <rtgwg@ietfa.amsl.com>; Wed,  1 Apr 2015 01:12:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 B9byyMCrzcRv for <rtgwg@ietfa.amsl.com>; Wed,  1 Apr 2015 01:11:56 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 419BF1A8A68 for <rtgwg@ietf.org>; Wed,  1 Apr 2015 01:11:55 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 00F9D3B43CB; Wed,  1 Apr 2015 10:11:54 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id C6A6A4C098; Wed,  1 Apr 2015 10:11:53 +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.0224.002; Wed, 1 Apr 2015 10:11:53 +0200
From: <bruno.decraene@orange.com>
To: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>, "akatlas@juniper.net" <akatlas@juniper.net>, "rkebler@juniper.net" <rkebler@juniper.net>, "cbowers@juniper.net" <cbowers@juniper.net>, "Gabor.Sandor.Enyedi@ericsson.com" <Gabor.Sandor.Enyedi@ericsson.com>, "Andras.Csaszar@ericsson.com" <Andras.Csaszar@ericsson.com>, "jeff.tantsura@ericsson.com" <jeff.tantsura@ericsson.com>, "russw@riw.us" <russw@riw.us>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Topic: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Index: AdBohapCLAg3Un3wSOKmk0bREwcgiQDx3TwQ
Date: Wed, 1 Apr 2015 08:11:52 +0000
Message-ID: <31522_1427875913_551BA849_31522_7681_1_53C29892C857584299CBF5D05346208A0EB8CE2B@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <327562D94EA7BF428CD805F338C31EF04FB31052@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <327562D94EA7BF428CD805F338C31EF04FB31052@NKGEML512-MBS.china.huawei.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.6]
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A0EB8CE2BPEXCVZYM11corpo_"
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.4.1.43619
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/C2j7jVbCmfBxdeJrZTT8TVL6pDU>
Cc: "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: Wed, 01 Apr 2015 08:12:09 -0000

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

Hi Chris, authors,

Comparing IP FRR methods is a difficult task... The choice of metrics (of c=
omparisons) is difficult and for some (solution, metric) the evaluation is =
very topology dependent.

That being said, it would be interesting to add another metric, related to =
the "quality" of the routing/placement of the FRR path. e.g. for short: opt=
imality of the FRR path (according to the IGP metric). But others quality m=
ay be taken into account e.g. naturally provisioned with enough capacity (i=
n a network having enough capacity to handle single failure), naturally pol=
icy friendly (as per LFA policy).

Another metric, may be how easy is the solution/FRR path determination for =
the human brain/network operators. Because ease of computation for computer=
 is a good thing, but in the end computer follows Moore's Law while human b=
rain do not.

IMHO it may be interesting to indicate the possibility for the SP to choose=
 between link protection, node protection, and SRLG protection, eventually =
on a per PLR/protected link basis. Indeed, the bigger protection may not be=
 the best as it's a trade-off impacting the optimality of the detour path. =
One may prefer link protection only, if the % of node failure is small and =
the detour to avoid the node is big.

The above being considered, the first sentence could probably be slightly m=
odified ( :s/Other/All )  since IMHO MRT has also trade-offs.

Thanks,
Regards,
Bruno


From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Anil Kumar S N (VR=
P Network BL)
Sent: Saturday, March 28, 2015 12:55 PM
To: akatlas@juniper.net; rkebler@juniper.net; cbowers@juniper.net; Gabor.Sa=
ndor.Enyedi@ericsson.com; Andras.Csaszar@ericsson.com; jeff.tantsura@ericss=
on.com; russw@riw.us; rtgwg@ietf.org; rtgwg-owner@ietf.org
Subject: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Authors,

      In  "comparison of IP/LDP FRR Methods" section of the document , I fe=
el we should add comparison with TI-LFA (draft-francois-spring-segment-rout=
ing-ti-lfa-01) where TI-LFA approach achieves guaranteed coverage  against =
link or node failure, in any IGP network, relying on the  flexibility of SR=
. This will give readers better picture and enables them with more informat=
ion so that they can choose MRT if they feel it suites their requirement be=
tter; compared to IT-LFA.
Changes :

1.  Introduction :

   Other existing or proposed solutions are partial solutions or have
   significant issues, as described below.

                 Summary Comparison of IP/LDP FRR Methods

   +---------+-------------+-------------+-----------------------------+
   |  Method |   Coverage  |  Alternate  |    Computation (in SPFs)    |
   |         |             |   Looping?  |                             |
   +---------+-------------+-------------+-----------------------------+
   | MRT-FRR |     100%    |     None    |         less than 3         |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   |   LFA   |   Partial   |   Possible  |         per neighbor        |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   |  Remote |   Partial   |   Possible  |    per neighbor (link) or   |
   |   LFA   |  Link/Node  |             |  neighbor's neighbor (node) |
   |         |             |             |                             |
   | Not-Via |     100%    |     None    |      per link and node      |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   | TI-LFA  |     100%    |   Possible  |    per neighbor (link) or   |
   |         |  Link/Node  |             |  neighbor's neighbor (node) |
   |         |             |             |                             |
   +---------+-------------+-------------+-----------------------------+

                                  Table 1


   TI-LFA: Topology Independent Loop-free Alternate Fast
   Re-route (TI-LFA), aimed at providing link and node protection of
   node and adjacency segments within the Segment Routing (SR)
   framework [draft-francois-spring-segment-routing-ti-lfa-01].
   Has improved coverage over LFAs and Remote LFA for link and node
   protection and also guarantees complete coverage. The trade-off
   of looping traffic to improve coverage is still made.
  The computation required is quite high with added complexity.
   TI-LFA is supported only MPLS data plane with a requirement to
   carry additional MPLS label stack on the link failure; on certain
   topologies stack size can grow significantly based repair path.

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel



___________________________________________________________________________=
______________________________________________

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.


--_000_53C29892C857584299CBF5D05346208A0EB8CE2BPEXCVZYM11corpo_
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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-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;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;}
span.EmailStyle19
	{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:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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 lang=3D"FR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Hi Chri=
s, authors,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Compari=
ng IP FRR methods is a difficult task&#8230; The choice of metrics (of comp=
arisons) is difficult and for some (solution, metric) the evaluation is ver=
y topology dependent.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">That be=
ing said, it would be interesting to add another metric, related to the &#8=
220;quality&#8221; of the routing/placement of the FRR path. e.g. for short=
: optimality of the FRR path (according to the IGP
 metric). But others quality may be taken into account e.g. naturally provi=
sioned with enough capacity (in a network having enough capacity to handle =
single failure), naturally policy friendly (as per LFA policy).<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Another=
 metric, may be how easy is the solution/FRR path determination for the hum=
an brain/network operators. Because ease of computation for computer is a g=
ood thing, but in the end computer follows
 Moore&#8217;s Law while human brain do not.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">IMHO it=
 may be interesting to indicate the possibility for the SP to choose betwee=
n link protection, node protection, and SRLG protection, eventually on a pe=
r PLR/protected link basis. Indeed, the
 bigger protection may not be the best as it&#8217;s a trade-off impacting =
the optimality of the detour path. One may prefer link protection only, if =
the % of node failure is small and the detour to avoid the node is big.<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">The abo=
ve being considered, the first sentence could probably be slightly modified=
 ( :s/Other/All )&nbsp; since IMHO MRT has also trade-offs.<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks,=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Regards=
,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Bruno<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> rtgwg [m=
ailto:rtgwg-bounces@ietf.org]
<b>On Behalf Of </b>Anil Kumar S N (VRP Network BL)<br>
<b>Sent:</b> Saturday, March 28, 2015 12:55 PM<br>
<b>To:</b> akatlas@juniper.net; rkebler@juniper.net; cbowers@juniper.net; G=
abor.Sandor.Enyedi@ericsson.com; Andras.Csaszar@ericsson.com; jeff.tantsura=
@ericsson.com; russw@riw.us; rtgwg@ietf.org; rtgwg-owner@ietf.org<br>
<b>Subject:</b> draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p></sp=
an></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi Authors,<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
In &nbsp;&#8220;comparison of IP/LDP FRR Methods&#8221; section of the docu=
ment , I feel we should add comparison with TI-LFA (draft-francois-spring-s=
egment-routing-ti-lfa-01) where TI-LFA approach achieves guaranteed coverag=
e &nbsp;against
 link or node failure, in any IGP network, relying on the&nbsp; flexibility=
 of SR. This will give readers better picture and enables them with more in=
formation so that they can choose MRT if they feel it suites their requirem=
ent better; compared to IT-LFA.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Changes :<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Arial&quot;,&quot;sans-serif&quot;">1.&nbsp; Introduction :=
</span></b><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; O=
ther existing or proposed solutions are partial solutions or have<o:p></o:p=
></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; s=
ignificant issues, as described below.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; Summary Comparison of IP/LDP FRR Methods<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; &=
#43;---------&#43;-------------&#43;-------------&#43;---------------------=
--------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
&nbsp; Method |&nbsp;&nbsp; Coverage&nbsp; |&nbsp; Alternate&nbsp; |&nbsp;&=
nbsp;&nbsp; Computation (in SPFs)&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"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; Looping?&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;&nb=
sp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; &=
#43;---------&#43;-------------&#43;-------------&#43;---------------------=
--------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
 MRT-FRR |&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbs=
p;&nbsp; None&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; less than 3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"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;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
&nbsp;&nbsp; LFA&nbsp;&nbsp; |&nbsp;&nbsp; Partial&nbsp;&nbsp; |&nbsp;&nbsp=
; Possible&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; per neig=
hbor&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"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;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
&nbsp; Remote |&nbsp;&nbsp; Partial&nbsp;&nbsp; |&nbsp;&nbsp; Possible&nbsp=
; |&nbsp;&nbsp;&nbsp; per neighbor (link) or&nbsp;&nbsp; |<o:p></o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
&nbsp;&nbsp; LFA&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; neighbor's neig=
hbor (node) |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"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;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
 Not-Via |&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbs=
p;&nbsp; None&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; per link an=
d node&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |=
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; Link/Node&nbsp; |&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"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;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp; | TI-LFA &nbsp;|&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp=
; |&nbsp; &nbsp;Possible&nbsp; |&nbsp;&nbsp;&nbsp; per neighbor (link) or&n=
bsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp; |&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; Link=
/Node&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; |&nbsp; neighbor's neighbor (node) |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"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;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; &=
#43;---------&#43;-------------&#43;-------------&#43;---------------------=
--------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"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;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Table 1</span><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp; TI-LFA: Topology Independent Loop-free Alternate Fast<o:p></o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp; Re-route (TI-LFA), aimed at providing link and node protection=
 of<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp; node and adjacency segments within the Segment Routing (SR)<o:=
p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp; framework [draft-francois-spring-segment-routing-ti-lfa-01].<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp; &nbsp;Has improved coverage over LFAs and Remote LFA for link and no=
de
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp;&nbsp;protection and also guarantees complete coverage. The tra=
de-off
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp;&nbsp;of looping traffic to improve coverage is still made.<o:p=
></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp;The computation required is quite high with added complexity.<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp; TI-LFA is supported only MPLS data plane with a requirement to
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp;&nbsp;&nbsp;carry additional MPLS label stack on the link failure; on=
 certain<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">=
&nbsp; &nbsp;topologies stack size can grow significantly based repair path.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks &amp; Regards<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Anil S N<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&#8220;Be liberal in what you a=
ccept, and conservative in what you send&#8221; - Jon Postel<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

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.
</PRE></body>
</html>

--_000_53C29892C857584299CBF5D05346208A0EB8CE2BPEXCVZYM11corpo_--


From nobody Wed Apr  1 01:55:52 2015
Return-Path: <anil.sn@huawei.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 575631A8AD0 for <rtgwg@ietfa.amsl.com>; Wed,  1 Apr 2015 01:55:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.61
X-Spam-Level: 
X-Spam-Status: No, score=-3.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 TwMnhHpsGb42 for <rtgwg@ietfa.amsl.com>; Wed,  1 Apr 2015 01:55:42 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 752911A8AC6 for <rtgwg@ietf.org>; Wed,  1 Apr 2015 01:55:41 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BUJ36944; Wed, 01 Apr 2015 08:55:34 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 1 Apr 2015 09:55:32 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.135]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Wed, 1 Apr 2015 16:55:27 +0800
From: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, "akatlas@juniper.net" <akatlas@juniper.net>, "rkebler@juniper.net" <rkebler@juniper.net>, "cbowers@juniper.net" <cbowers@juniper.net>, "Gabor.Sandor.Enyedi@ericsson.com" <Gabor.Sandor.Enyedi@ericsson.com>, "Andras.Csaszar@ericsson.com" <Andras.Csaszar@ericsson.com>, "jeff.tantsura@ericsson.com" <jeff.tantsura@ericsson.com>, "russw@riw.us" <russw@riw.us>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Topic: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Index: AdBohapCLAg3Un3wSOKmk0bREwcgiQDx3TwQAAL2xRA=
Date: Wed, 1 Apr 2015 08:55:27 +0000
Message-ID: <327562D94EA7BF428CD805F338C31EF04FB35492@nkgeml512-mbx.china.huawei.com>
References: <327562D94EA7BF428CD805F338C31EF04FB31052@NKGEML512-MBS.china.huawei.com> <31522_1427875913_551BA849_31522_7681_1_53C29892C857584299CBF5D05346208A0EB8CE2B@PEXCVZYM11.corporate.adroot.infra.ftgroup>
In-Reply-To: <31522_1427875913_551BA849_31522_7681_1_53C29892C857584299CBF5D05346208A0EB8CE2B@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.152.169]
Content-Type: multipart/alternative; boundary="_000_327562D94EA7BF428CD805F338C31EF04FB35492nkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/H99J8bCD7rpDe1NHvMaas3WLlLQ>
Cc: "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: Wed, 01 Apr 2015 08:55:50 -0000

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

Hi Bruno,Chris,Authors,

I was reading "draft-thubert-rtgwg-arc-vs-mrt-01.pdf" I feel its not bad to=
 add comparison with respect to ARC.
Since ARC is not adopted by IETF, But an attempt could be made to add merit=
s and Demerits of MRT against ARC.

p.s. ARC claims to address the issue stated "MRT is guaranteed to recovery =
from only one failure".

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel


From: bruno.decraene@orange.com [mailto:bruno.decraene@orange.com]
Sent: 01 April 2015 13:42
To: Anil Kumar S N (VRP Network BL); akatlas@juniper.net; rkebler@juniper.n=
et; cbowers@juniper.net; Gabor.Sandor.Enyedi@ericsson.com; Andras.Csaszar@e=
ricsson.com; jeff.tantsura@ericsson.com; russw@riw.us
Cc: rtgwg@ietf.org; pierre.francois@imdea.org
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Chris, authors,

Comparing IP FRR methods is a difficult task... The choice of metrics (of c=
omparisons) is difficult and for some (solution, metric) the evaluation is =
very topology dependent.

That being said, it would be interesting to add another metric, related to =
the "quality" of the routing/placement of the FRR path. e.g. for short: opt=
imality of the FRR path (according to the IGP metric). But others quality m=
ay be taken into account e.g. naturally provisioned with enough capacity (i=
n a network having enough capacity to handle single failure), naturally pol=
icy friendly (as per LFA policy).

Another metric, may be how easy is the solution/FRR path determination for =
the human brain/network operators. Because ease of computation for computer=
 is a good thing, but in the end computer follows Moore's Law while human b=
rain do not.

IMHO it may be interesting to indicate the possibility for the SP to choose=
 between link protection, node protection, and SRLG protection, eventually =
on a per PLR/protected link basis. Indeed, the bigger protection may not be=
 the best as it's a trade-off impacting the optimality of the detour path. =
One may prefer link protection only, if the % of node failure is small and =
the detour to avoid the node is big.

The above being considered, the first sentence could probably be slightly m=
odified ( :s/Other/All )  since IMHO MRT has also trade-offs.

Thanks,
Regards,
Bruno


From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Anil Kumar S N (VR=
P Network BL)
Sent: Saturday, March 28, 2015 12:55 PM
To: akatlas@juniper.net<mailto:akatlas@juniper.net>; rkebler@juniper.net<ma=
ilto:rkebler@juniper.net>; cbowers@juniper.net<mailto:cbowers@juniper.net>;=
 Gabor.Sandor.Enyedi@ericsson.com<mailto:Gabor.Sandor.Enyedi@ericsson.com>;=
 Andras.Csaszar@ericsson.com<mailto:Andras.Csaszar@ericsson.com>; jeff.tant=
sura@ericsson.com<mailto:jeff.tantsura@ericsson.com>; russw@riw.us<mailto:r=
ussw@riw.us>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>; rtgwg-owner@ietf.org<m=
ailto:rtgwg-owner@ietf.org>
Subject: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Authors,

      In  "comparison of IP/LDP FRR Methods" section of the document , I fe=
el we should add comparison with TI-LFA (draft-francois-spring-segment-rout=
ing-ti-lfa-01) where TI-LFA approach achieves guaranteed coverage  against =
link or node failure, in any IGP network, relying on the  flexibility of SR=
. This will give readers better picture and enables them with more informat=
ion so that they can choose MRT if they feel it suites their requirement be=
tter; compared to IT-LFA.
Changes :

1.  Introduction :

   Other existing or proposed solutions are partial solutions or have
   significant issues, as described below.

                 Summary Comparison of IP/LDP FRR Methods

   +---------+-------------+-------------+-----------------------------+
   |  Method |   Coverage  |  Alternate  |    Computation (in SPFs)    |
   |         |             |   Looping?  |                             |
   +---------+-------------+-------------+-----------------------------+
   | MRT-FRR |     100%    |     None    |         less than 3         |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   |   LFA   |   Partial   |   Possible  |         per neighbor        |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   |  Remote |   Partial   |   Possible  |    per neighbor (link) or   |
   |   LFA   |  Link/Node  |             |  neighbor's neighbor (node) |
   |         |             |             |                             |
   | Not-Via |     100%    |     None    |      per link and node      |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   | TI-LFA  |     100%    |   Possible  |    per neighbor (link) or   |
   |         |  Link/Node  |             |  neighbor's neighbor (node) |
   |         |             |             |                             |
   +---------+-------------+-------------+-----------------------------+

                                  Table 1


   TI-LFA: Topology Independent Loop-free Alternate Fast
   Re-route (TI-LFA), aimed at providing link and node protection of
   node and adjacency segments within the Segment Routing (SR)
   framework [draft-francois-spring-segment-routing-ti-lfa-01].
   Has improved coverage over LFAs and Remote LFA for link and node
   protection and also guarantees complete coverage. The trade-off
   of looping traffic to improve coverage is still made.
  The computation required is quite high with added complexity.
   TI-LFA is supported only MPLS data plane with a requirement to
   carry additional MPLS label stack on the link failure; on certain
   topologies stack size can grow significantly based repair path.

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel



___________________________________________________________________________=
______________________________________________



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.

--_000_327562D94EA7BF428CD805F338C31EF04FB35492nkgeml512mbxchi_
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 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-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:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;}
span.EmailStyle19
	{mso-style-type:personal;
	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:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle24
	{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:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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 lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Bruno,Chris,Authors=
,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I was reading &#8220;d=
raft-thubert-rtgwg-arc-vs-mrt-01.pdf&#8221; I feel its not bad to add compa=
rison with respect to ARC.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Since ARC is not adopt=
ed by IETF, But an attempt could be made to add merits and Demerits of MRT =
against ARC.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">p.s. ARC claims to add=
ress the issue stated &#8220;MRT is guaranteed to recovery from only one fa=
ilure&#8221;.
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks &amp; Regards<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Anil S N<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&#8220;Be liberal in w=
hat you accept, and conservative in what you send&#8221; - Jon Postel<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> bruno.de=
craene@orange.com [mailto:bruno.decraene@orange.com]
<br>
<b>Sent:</b> 01 April 2015 13:42<br>
<b>To:</b> Anil Kumar S N (VRP Network BL); akatlas@juniper.net; rkebler@ju=
niper.net; cbowers@juniper.net; Gabor.Sandor.Enyedi@ericsson.com; Andras.Cs=
aszar@ericsson.com; jeff.tantsura@ericsson.com; russw@riw.us<br>
<b>Cc:</b> rtgwg@ietf.org; pierre.francois@imdea.org<br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Chris, authors,<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Comparing IP FRR metho=
ds is a difficult task&#8230; The choice of metrics (of comparisons) is dif=
ficult and for some (solution, metric) the evaluation is very topology depe=
ndent.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">That being said, it wo=
uld be interesting to add another metric, related to the &#8220;quality&#82=
21; of the routing/placement of the FRR path. e.g. for short: optimality of=
 the FRR path (according to the IGP metric). But
 others quality may be taken into account e.g. naturally provisioned with e=
nough capacity (in a network having enough capacity to handle single failur=
e), naturally policy friendly (as per LFA policy).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Another metric, may be=
 how easy is the solution/FRR path determination for the human brain/networ=
k operators. Because ease of computation for computer is a good thing, but =
in the end computer follows Moore&#8217;s
 Law while human brain do not.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">IMHO it may be interes=
ting to indicate the possibility for the SP to choose between link protecti=
on, node protection, and SRLG protection, eventually on a per PLR/protected=
 link basis. Indeed, the bigger protection
 may not be the best as it&#8217;s a trade-off impacting the optimality of =
the detour path. One may prefer link protection only, if the % of node fail=
ure is small and the detour to avoid the node is big.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The above being consid=
ered, the first sentence could probably be slightly modified ( :s/Other/All=
 )&nbsp; since IMHO MRT has also trade-offs.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Bruno<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"FR" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lan=
g=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;san=
s-serif&quot;"> rtgwg [<a href=3D"mailto:rtgwg-bounces@ietf.org">mailto:rtg=
wg-bounces@ietf.org</a>]
<b>On Behalf Of </b>Anil Kumar S N (VRP Network BL)<br>
<b>Sent:</b> Saturday, March 28, 2015 12:55 PM<br>
<b>To:</b> <a href=3D"mailto:akatlas@juniper.net">akatlas@juniper.net</a>; =
<a href=3D"mailto:rkebler@juniper.net">
rkebler@juniper.net</a>; <a href=3D"mailto:cbowers@juniper.net">cbowers@jun=
iper.net</a>;
<a href=3D"mailto:Gabor.Sandor.Enyedi@ericsson.com">Gabor.Sandor.Enyedi@eri=
csson.com</a>;
<a href=3D"mailto:Andras.Csaszar@ericsson.com">Andras.Csaszar@ericsson.com<=
/a>; <a href=3D"mailto:jeff.tantsura@ericsson.com">
jeff.tantsura@ericsson.com</a>; <a href=3D"mailto:russw@riw.us">russw@riw.u=
s</a>; <a href=3D"mailto:rtgwg@ietf.org">
rtgwg@ietf.org</a>; <a href=3D"mailto:rtgwg-owner@ietf.org">rtgwg-owner@iet=
f.org</a><br>
<b>Subject:</b> draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p></sp=
an></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"FR"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">Hi Authors,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In &nbsp;&#8220;compa=
rison of IP/LDP FRR Methods&#8221; section of the document , I feel we shou=
ld add comparison with TI-LFA (draft-francois-spring-segment-routing-ti-lfa=
-01) where TI-LFA approach achieves guaranteed coverage &nbsp;against link =
or node
 failure, in any IGP network, relying on the&nbsp; flexibility of SR. This =
will give readers better picture and enables them with more information so =
that they can choose MRT if they feel it suites their requirement better; c=
ompared to IT-LFA.<o:p></o:p></p>
<p class=3D"MsoNormal">Changes :<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">1.&nbsp; Introduction :</span></b><o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; Other existing o=
r proposed solutions are partial solutions or have<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; significant issu=
es, as described below.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Summary=
 Comparison of IP/LDP FRR Methods<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; &#43;---------&#=
43;-------------&#43;-------------&#43;-----------------------------&#43;<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp; Method |=
&nbsp;&nbsp; Coverage&nbsp; |&nbsp; Alternate&nbsp; |&nbsp;&nbsp;&nbsp; Com=
putation (in SPFs)&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; Looping?&nbsp; |&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; &#43;---------&#=
43;-------------&#43;-------------&#43;-----------------------------&#43;<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; | MRT-FRR |&nbsp=
;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; None&n=
bsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; less tha=
n 3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp; LF=
A&nbsp;&nbsp; |&nbsp;&nbsp; Partial&nbsp;&nbsp; |&nbsp;&nbsp; Possible&nbsp=
; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; per neighbor&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp; Remote |=
&nbsp;&nbsp; Partial&nbsp;&nbsp; |&nbsp;&nbsp; Possible&nbsp; |&nbsp;&nbsp;=
&nbsp; per neighbor (link) or&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp; LF=
A&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; neighbor's neighbor (node) |<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; | Not-Via |&nbsp=
;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; None&n=
bsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; per link and node&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; | &nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; Link/Node&nbsp; |&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp; | =
TI-LFA &nbsp;|&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp; |&nbsp; &nbsp=
;Possible&nbsp; |&nbsp;&nbsp;&nbsp; per neighbor (link) or&nbsp;&nbsp; |<o:=
p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp; |&=
nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; Link/Node&nbsp; |&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nb=
sp; neighbor's neighbor (node) |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; &#43;---------&#=
43;-------------&#43;-------------&#43;-----------------------------&#43;<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Table 1</=
span><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp; TI=
-LFA: Topology Independent Loop-free Alternate Fast<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp; Re=
-route (TI-LFA), aimed at providing link and node protection of<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp; no=
de and adjacency segments within the Segment Routing (SR)<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp; fr=
amework [draft-francois-spring-segment-routing-ti-lfa-01].<o:p></o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp; &nbsp;Ha=
s improved coverage over LFAs and Remote LFA for link and node
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nb=
sp;protection and also guarantees complete coverage. The trade-off
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nb=
sp;of looping traffic to improve coverage is still made.<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;The=
 computation required is quite high with added complexity.<o:p></o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp; TI=
-LFA is supported only MPLS data plane with a requirement to
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nb=
sp;carry additional MPLS label stack on the link failure; on certain<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp; &nbsp;to=
pologies stack size can grow significantly based repair path.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks &amp; Regards<o:p></o:p></p>
<p class=3D"MsoNormal">Anil S N<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&#8220;Be liberal in what you accept, and conservati=
ve in what you send&#8221; - Jon Postel<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<pre><span lang=3D"FR">____________________________________________________=
_____________________________________________________________________<o:p><=
/o:p></span></pre>
<pre><span lang=3D"FR"><o:p>&nbsp;</o:p></span></pre>
<pre><span lang=3D"FR">Ce message et ses pieces jointes peuvent contenir de=
s informations confidentielles ou privilegiees et ne doivent donc<o:p></o:p=
></span></pre>
<pre><span lang=3D"FR">pas etre diffuses, exploites ou copies sans autorisa=
tion. Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o=
:p></span></pre>
<pre><span lang=3D"FR">a l'expediteur et le detruire ainsi que les pieces j=
ointes. Les messages electroniques etant susceptibles d'alteration,<o:p></o=
:p></span></pre>
<pre><span lang=3D"FR">Orange decline toute responsabilite si ce message a =
ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span lang=3D"FR"><o:p>&nbsp;</o:p></span></pre>
<pre><span lang=3D"FR">This message and its attachments may contain confide=
ntial or privileged information that may be protected by law;<o:p></o:p></s=
pan></pre>
<pre><span lang=3D"FR">they should not be distributed, used or copied witho=
ut authorisation.<o:p></o:p></span></pre>
<pre><span lang=3D"FR">If you have received this email in error, please not=
ify the sender and delete this message and its attachments.<o:p></o:p></spa=
n></pre>
<pre><span lang=3D"FR">As emails may be altered, Orange is not liable for m=
essages that have been modified, changed or falsified.<o:p></o:p></span></p=
re>
<pre><span lang=3D"FR">Thank you.<o:p></o:p></span></pre>
</div>
</body>
</html>

--_000_327562D94EA7BF428CD805F338C31EF04FB35492nkgeml512mbxchi_--


From nobody Wed Apr  1 03:33:30 2015
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 B76101A1B44 for <rtgwg@ietfa.amsl.com>; Wed,  1 Apr 2015 03:33:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.91
X-Spam-Level: 
X-Spam-Status: No, score=-13.91 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, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 0QiEoohinrjJ for <rtgwg@ietfa.amsl.com>; Wed,  1 Apr 2015 03:33:25 -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 3EE841A8986 for <rtgwg@ietf.org>; Wed,  1 Apr 2015 03:33:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=35364; q=dns/txt; s=iport; t=1427884404; x=1429094004; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=/rkDjc7aOD/qApSkvJTu8G2H3kO5vShXYIaToB0y2G0=; b=HBXIko1QXEufHIm6gQ6NQYVNG9uxkyPOjC5Y9aIpLRvp1OHCOzNOh8Aa PKAahonO+2JTERTc+faDmnGVtBNMukKPvgA3hKLM/WsNRgUG+J90zNbQo /Si+v3qCY6EcE0d6RcRMO/lIgDR5wyFdJYf6UizgT4WNtj35FsUf48vQg o=;
X-IronPort-AV: E=Sophos;i="5.11,503,1422921600";  d="scan'208,217";a="429581016"
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; 01 Apr 2015 10:33:22 +0000
Received: from [10.55.98.183] (ams-stbryant-8816.cisco.com [10.55.98.183]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t31AXLK6030951; Wed, 1 Apr 2015 10:33:22 GMT
Message-ID: <551BC971.6030208@cisco.com>
Date: Wed, 01 Apr 2015 11:33:21 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>, "bruno.decraene@orange.com" <bruno.decraene@orange.com>, "akatlas@juniper.net" <akatlas@juniper.net>, "rkebler@juniper.net" <rkebler@juniper.net>, "cbowers@juniper.net" <cbowers@juniper.net>, "Gabor.Sandor.Enyedi@ericsson.com" <Gabor.Sandor.Enyedi@ericsson.com>, "Andras.Csaszar@ericsson.com" <Andras.Csaszar@ericsson.com>, "jeff.tantsura@ericsson.com" <jeff.tantsura@ericsson.com>, "russw@riw.us" <russw@riw.us>
Subject: Re: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
References: <327562D94EA7BF428CD805F338C31EF04FB31052@NKGEML512-MBS.china.huawei.com> <31522_1427875913_551BA849_31522_7681_1_53C29892C857584299CBF5D05346208A0EB8CE2B@PEXCVZYM11.corporate.adroot.infra.ftgroup> <327562D94EA7BF428CD805F338C31EF04FB35492@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <327562D94EA7BF428CD805F338C31EF04FB35492@nkgeml512-mbx.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------000104000001020207000507"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/fWBNrv9x5UuxnLHtIedwahF7K98>
Cc: "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: Wed, 01 Apr 2015 10:33:29 -0000

This is a multi-part message in MIME format.
--------------000104000001020207000507
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit


Actually I was going to propose this myself.

ARC is a very interesting approach in that it deals quite well with multiple
failures since the repair is localized to the repair arc making it possible
to do multiple repairs.

I still wonder whether we know enough about the relative
merits of the various post rlfa methods consider any of them
sufficiently best to be on standards track.

The big elephant is the loop free convergence technology
which is very much unfinished work, and I am wondering
whether we need to make it a requirement that any standards
track solution needs to have a workable LFC technology.

Stewart



On 01/04/2015 09:55, Anil Kumar S N (VRP Network BL) wrote:
>
> Hi Bruno,Chris,Authors,
>
> I was reading “draft-thubert-rtgwg-arc-vs-mrt-01.pdf” I feel its not 
> bad to add comparison with respect to ARC.
>
> Since ARC is not adopted by IETF, But an attempt could be made to add 
> merits and Demerits of MRT against ARC.
>
> p.s. ARC claims to address the issue stated “MRT is guaranteed to 
> recovery from only one failure”.
>
> Thanks & Regards
>
> Anil S N
>
> “Be liberal in what you accept, and conservative in what you send” - 
> Jon Postel
>
> *From:*bruno.decraene@orange.com [mailto:bruno.decraene@orange.com]
> *Sent:* 01 April 2015 13:42
> *To:* Anil Kumar S N (VRP Network BL); akatlas@juniper.net; 
> rkebler@juniper.net; cbowers@juniper.net; 
> Gabor.Sandor.Enyedi@ericsson.com; Andras.Csaszar@ericsson.com; 
> jeff.tantsura@ericsson.com; russw@riw.us
> *Cc:* rtgwg@ietf.org; pierre.francois@imdea.org
> *Subject:* RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
>
> Hi Chris, authors,
>
> Comparing IP FRR methods is a difficult task… The choice of metrics 
> (of comparisons) is difficult and for some (solution, metric) the 
> evaluation is very topology dependent.
>
> That being said, it would be interesting to add another metric, 
> related to the “quality” of the routing/placement of the FRR path. 
> e.g. for short: optimality of the FRR path (according to the IGP 
> metric). But others quality may be taken into account e.g. naturally 
> provisioned with enough capacity (in a network having enough capacity 
> to handle single failure), naturally policy friendly (as per LFA policy).
>
> Another metric, may be how easy is the solution/FRR path determination 
> for the human brain/network operators. Because ease of computation for 
> computer is a good thing, but in the end computer follows Moore’s Law 
> while human brain do not.
>
> IMHO it may be interesting to indicate the possibility for the SP to 
> choose between link protection, node protection, and SRLG protection, 
> eventually on a per PLR/protected link basis. Indeed, the bigger 
> protection may not be the best as it’s a trade-off impacting the 
> optimality of the detour path. One may prefer link protection only, if 
> the % of node failure is small and the detour to avoid the node is big.
>
> The above being considered, the first sentence could probably be 
> slightly modified ( :s/Other/All )  since IMHO MRT has also trade-offs.
>
> Thanks,
>
> Regards,
>
> Bruno
>
> *From:*rtgwg [mailto:rtgwg-bounces@ietf.org] *On Behalf Of *Anil Kumar 
> S N (VRP Network BL)
> *Sent:* Saturday, March 28, 2015 12:55 PM
> *To:* akatlas@juniper.net <mailto:akatlas@juniper.net>; 
> rkebler@juniper.net <mailto:rkebler@juniper.net>; cbowers@juniper.net 
> <mailto:cbowers@juniper.net>; Gabor.Sandor.Enyedi@ericsson.com 
> <mailto:Gabor.Sandor.Enyedi@ericsson.com>; Andras.Csaszar@ericsson.com 
> <mailto:Andras.Csaszar@ericsson.com>; jeff.tantsura@ericsson.com 
> <mailto:jeff.tantsura@ericsson.com>; russw@riw.us 
> <mailto:russw@riw.us>; rtgwg@ietf.org <mailto:rtgwg@ietf.org>; 
> rtgwg-owner@ietf.org <mailto:rtgwg-owner@ietf.org>
> *Subject:* draft-ietf-rtgwg-mrt-frr-architecture-05.txt
>
> Hi Authors,
>
>       In  “comparison of IP/LDP FRR Methods” section of the document , 
> I feel we should add comparison with TI-LFA 
> (draft-francois-spring-segment-routing-ti-lfa-01) where TI-LFA 
> approach achieves guaranteed coverage  against link or node failure, 
> in any IGP network, relying on the flexibility of SR. This will give 
> readers better picture and enables them with more information so that 
> they can choose MRT if they feel it suites their requirement better; 
> compared to IT-LFA.
>
> Changes :
>
> *1. Introduction :*
>
>    Other existing or proposed solutions are partial solutions or have
>
>    significant issues, as described below.
>
>                  Summary Comparison of IP/LDP FRR Methods
>
> +---------+-------------+-------------+-----------------------------+
>
>    |  Method |   Coverage  |  Alternate  | Computation (in SPFs)    |
>
>    |         |             |   Looping? |                             |
>
> +---------+-------------+-------------+-----------------------------+
>
>    | MRT-FRR |     100%    |     None |         less than 3         |
>
>    |         |  Link/Node  | |                             |
>
>    |         |             | |                             |
>
>    |   LFA   |   Partial   |   Possible |         per neighbor        |
>
>    |         |  Link/Node  | |                             |
>
>    |         |             | |                             |
>
>    |  Remote |   Partial   |   Possible  | per neighbor (link) or   |
>
>    |   LFA   |  Link/Node  |             | neighbor's neighbor (node) |
>
>    |         |             | |                             |
>
>    | Not-Via |     100%    |     None    | per link and node      |
>
>    |         |  Link/Node  | |                             |
>
>    |         |             | |                             |
>
>    | TI-LFA  |     100%    |  Possible  |    per neighbor (link) or   |
>
>    |         |  Link/Node |             |  neighbor's neighbor (node) |
>
>    |         |             | |                             |
>
> +---------+-------------+-------------+-----------------------------+
>
>                                   Table 1
>
>    TI-LFA: Topology Independent Loop-free Alternate Fast
>
>    Re-route (TI-LFA), aimed at providing link and node protection of
>
>    node and adjacency segments within the Segment Routing (SR)
>
>    framework [draft-francois-spring-segment-routing-ti-lfa-01].
>
>    Has improved coverage over LFAs and Remote LFA for link and node
>
>    protection and also guarantees complete coverage. The trade-off
>
>    of looping traffic to improve coverage is still made.
>
>   The computation required is quite high with added complexity.
>
>    TI-LFA is supported only MPLS data plane with a requirement to
>
>    carry additional MPLS label stack on the link failure; on certain
>
>    topologies stack size can grow significantly based repair path.
>
> Thanks & Regards
>
> Anil S N
>
> “Be liberal in what you accept, and conservative in what you send” - 
> Jon Postel
>
> _________________________________________________________________________________________________________________________
>   
> 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.
>
>
> _______________________________________________
> 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


--------------000104000001020207000507
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix"><br>
      Actually I was going to propose this myself.<br>
      <br>
      ARC is a very interesting approach in that it deals quite well
      with multiple<br>
      failures since the repair is localized to the repair arc making it
      possible<br>
      to do multiple repairs. <br>
      <br>
      I still wonder whether we know enough about the relative<br>
      merits of the various post rlfa methods consider any of them<br>
      sufficiently best to be on standards track.<br>
      <br>
      The big elephant is the loop free convergence technology <br>
      which is very much unfinished work, and I am wondering <br>
      whether we need to make it a requirement that any standards <br>
      track solution needs to have a workable LFC technology.<br>
      <br>
      Stewart<br>
      <br>
      <br>
      <br>
      On 01/04/2015 09:55, Anil Kumar S N (VRP Network BL) wrote:<br>
    </div>
    <blockquote
cite="mid:327562D94EA7BF428CD805F338C31EF04FB35492@nkgeml512-mbx.china.huawei.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-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:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;}
span.EmailStyle19
	{mso-style-type:personal;
	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:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle24
	{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:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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="color:#1F497D">Hi
            Bruno,Chris,Authors,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">I was reading
            “draft-thubert-rtgwg-arc-vs-mrt-01.pdf” I feel its not bad
            to add comparison with respect to ARC.
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Since ARC is
            not adopted by IETF, But an attempt could be made to add
            merits and Demerits of MRT against ARC.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">p.s. ARC claims
            to address the issue stated “MRT is guaranteed to recovery
            from only one failure”.
            <o:p></o:p></span></p>
        <div>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D">Thanks &amp;
              Regards<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D">Anil S N<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D">“Be liberal
              in what you accept, and conservative in what you send” -
              Jon Postel<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        </div>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0cm 0cm 0cm">
            <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                <a class="moz-txt-link-abbreviated" href="mailto:bruno.decraene@orange.com">bruno.decraene@orange.com</a>
                [<a class="moz-txt-link-freetext" href="mailto:bruno.decraene@orange.com">mailto:bruno.decraene@orange.com</a>]
                <br>
                <b>Sent:</b> 01 April 2015 13:42<br>
                <b>To:</b> Anil Kumar S N (VRP Network BL);
                <a class="moz-txt-link-abbreviated" href="mailto:akatlas@juniper.net">akatlas@juniper.net</a>; <a class="moz-txt-link-abbreviated" href="mailto:rkebler@juniper.net">rkebler@juniper.net</a>;
                <a class="moz-txt-link-abbreviated" href="mailto:cbowers@juniper.net">cbowers@juniper.net</a>; <a class="moz-txt-link-abbreviated" href="mailto:Gabor.Sandor.Enyedi@ericsson.com">Gabor.Sandor.Enyedi@ericsson.com</a>;
                <a class="moz-txt-link-abbreviated" href="mailto:Andras.Csaszar@ericsson.com">Andras.Csaszar@ericsson.com</a>; <a class="moz-txt-link-abbreviated" href="mailto:jeff.tantsura@ericsson.com">jeff.tantsura@ericsson.com</a>;
                <a class="moz-txt-link-abbreviated" href="mailto:russw@riw.us">russw@riw.us</a><br>
                <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:pierre.francois@imdea.org">pierre.francois@imdea.org</a><br>
                <b>Subject:</b> RE:
                draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal"><span style="color:#1F497D">Hi Chris,
            authors,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Comparing IP
            FRR methods is a difficult task… The choice of metrics (of
            comparisons) is difficult and for some (solution, metric)
            the evaluation is very topology dependent.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">That being
            said, it would be interesting to add another metric, related
            to the “quality” of the routing/placement of the FRR path.
            e.g. for short: optimality of the FRR path (according to the
            IGP metric). But others quality may be taken into account
            e.g. naturally provisioned with enough capacity (in a
            network having enough capacity to handle single failure),
            naturally policy friendly (as per LFA policy).<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Another metric,
            may be how easy is the solution/FRR path determination for
            the human brain/network operators. Because ease of
            computation for computer is a good thing, but in the end
            computer follows Moore’s Law while human brain do not.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">IMHO it may be
            interesting to indicate the possibility for the SP to choose
            between link protection, node protection, and SRLG
            protection, eventually on a per PLR/protected link basis.
            Indeed, the bigger protection may not be the best as it’s a
            trade-off impacting the optimality of the detour path. One
            may prefer link protection only, if the % of node failure is
            small and the detour to avoid the node is big.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">The above being
            considered, the first sentence could probably be slightly
            modified ( :s/Other/All )  since IMHO MRT has also
            trade-offs.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Thanks,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Regards,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Bruno<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <div style="border:none;border-left:solid blue 1.5pt;padding:0cm
          0cm 0cm 4.0pt">
          <div>
            <div style="border:none;border-top:solid #B5C4DF
              1.0pt;padding:3.0pt 0cm 0cm 0cm">
              <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"
                    lang="FR">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"
                  lang="FR"> rtgwg [<a moz-do-not-send="true"
                    href="mailto:rtgwg-bounces@ietf.org">mailto:rtgwg-bounces@ietf.org</a>]
                  <b>On Behalf Of </b>Anil Kumar S N (VRP Network BL)<br>
                  <b>Sent:</b> Saturday, March 28, 2015 12:55 PM<br>
                  <b>To:</b> <a moz-do-not-send="true"
                    href="mailto:akatlas@juniper.net">akatlas@juniper.net</a>;
                  <a moz-do-not-send="true"
                    href="mailto:rkebler@juniper.net">
                    rkebler@juniper.net</a>; <a moz-do-not-send="true"
                    href="mailto:cbowers@juniper.net">cbowers@juniper.net</a>;
                  <a moz-do-not-send="true"
                    href="mailto:Gabor.Sandor.Enyedi@ericsson.com">Gabor.Sandor.Enyedi@ericsson.com</a>;
                  <a moz-do-not-send="true"
                    href="mailto:Andras.Csaszar@ericsson.com">Andras.Csaszar@ericsson.com</a>;
                  <a moz-do-not-send="true"
                    href="mailto:jeff.tantsura@ericsson.com">
                    jeff.tantsura@ericsson.com</a>; <a
                    moz-do-not-send="true" href="mailto:russw@riw.us">russw@riw.us</a>;
                  <a moz-do-not-send="true" href="mailto:rtgwg@ietf.org">
                    rtgwg@ietf.org</a>; <a moz-do-not-send="true"
                    href="mailto:rtgwg-owner@ietf.org">rtgwg-owner@ietf.org</a><br>
                  <b>Subject:</b>
                  draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><span lang="FR"><o:p> </o:p></span></p>
          <p class="MsoNormal">Hi Authors,<o:p></o:p></p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal">      In  “comparison of IP/LDP FRR
            Methods” section of the document , I feel we should add
            comparison with TI-LFA
            (draft-francois-spring-segment-routing-ti-lfa-01) where
            TI-LFA approach achieves guaranteed coverage  against link
            or node failure, in any IGP network, relying on the 
            flexibility of SR. This will give readers better picture and
            enables them with more information so that they can choose
            MRT if they feel it suites their requirement better;
            compared to IT-LFA.<o:p></o:p></p>
          <p class="MsoNormal">Changes :<o:p></o:p></p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">1. 
                Introduction :</span></b><o:p></o:p></p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   Other existing or proposed solutions are
              partial solutions or have<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   significant issues, as described below.<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;"><o:p> </o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">                 Summary Comparison of IP/LDP
              FRR Methods<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;"><o:p> </o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">  
              +---------+-------------+-------------+-----------------------------+<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   |  Method |   Coverage  |  Alternate  |   
              Computation (in SPFs)    |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   |         |             |   Looping? 
              |                             |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">  
              +---------+-------------+-------------+-----------------------------+<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   | MRT-FRR |     100%    |     None   
              |         less than 3         |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   |         |  Link/Node  |            
              |                             |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   |         |             |            
              |                             |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   |   LFA   |   Partial   |   Possible 
              |         per neighbor        |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   |         |  Link/Node  |            
              |                             |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   |         |             |            
              |                             |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   |  Remote |   Partial   |   Possible  |   
              per neighbor (link) or   |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   |   LFA   |  Link/Node  |             | 
              neighbor's neighbor (node) |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   |         |             |            
              |                             |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   | Not-Via |     100%    |     None    |     
              per link and node      |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   |         |  Link/Node  |            
              |                             |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   |         |             |            
              |                             |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:#00B050">   | TI-LFA  |     100%    | 
               Possible  |    per neighbor (link) or   |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:#00B050">   |         |  Link/Node 
              |             |  neighbor's neighbor (node) |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">   |         |             |            
              |                             |<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">  
              +---------+-------------+-------------+-----------------------------+<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;">                                  Table 1</span><o:p></o:p></p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:#00B050">   TI-LFA: Topology Independent
              Loop-free Alternate Fast<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:#00B050">   Re-route (TI-LFA), aimed at
              providing link and node protection of<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:#00B050">   node and adjacency segments
              within the Segment Routing (SR)<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:#00B050">   framework
              [draft-francois-spring-segment-routing-ti-lfa-01].<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:#00B050">   Has improved coverage over
              LFAs and Remote LFA for link and node
              <o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:#00B050">   protection and also guarantees
              complete coverage. The trade-off
              <o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:#00B050">   of looping traffic to improve
              coverage is still made.<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:#00B050">  The computation required is
              quite high with added complexity.<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:#00B050">   TI-LFA is supported only MPLS
              data plane with a requirement to
              <o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:#00B050">   carry additional MPLS label
              stack on the link failure; on certain<o:p></o:p></span></p>
          <p class="MsoNormal" style="line-height:14.4pt"><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;;color:#00B050">   topologies stack size can grow
              significantly based repair path.
              <o:p></o:p></span></p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal">Thanks &amp; Regards<o:p></o:p></p>
          <p class="MsoNormal">Anil S N<o:p></o:p></p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal">“Be liberal in what you accept, and
            conservative in what you send” - Jon Postel<o:p></o:p></p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal"><o:p> </o:p></p>
        </div>
        <pre><span lang="FR">_________________________________________________________________________________________________________________________<o:p></o:p></span></pre>
        <pre><span lang="FR"><o:p> </o:p></span></pre>
        <pre><span lang="FR">Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc<o:p></o:p></span></pre>
        <pre><span lang="FR">pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o:p></span></pre>
        <pre><span lang="FR">a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,<o:p></o:p></span></pre>
        <pre><span lang="FR">Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
        <pre><span lang="FR"><o:p> </o:p></span></pre>
        <pre><span lang="FR">This message and its attachments may contain confidential or privileged information that may be protected by law;<o:p></o:p></span></pre>
        <pre><span lang="FR">they should not be distributed, used or copied without authorisation.<o:p></o:p></span></pre>
        <pre><span lang="FR">If you have received this email in error, please notify the sender and delete this message and its attachments.<o:p></o:p></span></pre>
        <pre><span lang="FR">As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.<o:p></o:p></span></pre>
        <pre><span lang="FR">Thank you.<o:p></o:p></span></pre>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
rtgwg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/rtgwg">https://www.ietf.org/mailman/listinfo/rtgwg</a>
</pre>
    </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>

--------------000104000001020207000507--


From nobody Wed Apr  1 08:44:30 2015
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 702951ACD48 for <rtgwg@ietfa.amsl.com>; Wed,  1 Apr 2015 08:44:27 -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 0tgfsCTuOEnw for <rtgwg@ietfa.amsl.com>; Wed,  1 Apr 2015 08:44:22 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0133.outbound.protection.outlook.com [207.46.100.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A71581ACDEF for <rtgwg@ietf.org>; Wed,  1 Apr 2015 08:44:15 -0700 (PDT)
Received: from BLUPR05MB292.namprd05.prod.outlook.com (10.141.23.27) by BY1PR0501MB1256.namprd05.prod.outlook.com (25.160.200.142) with Microsoft SMTP Server (TLS) id 15.1.118.21; Wed, 1 Apr 2015 15:44:13 +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.01.0118.022; Wed, 1 Apr 2015 15:44:13 +0000
From: Chris Bowers <cbowers@juniper.net>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>, Alia Atlas <akatlas@juniper.net>, Robert Kebler <rkebler@juniper.net>, "Gabor.Sandor.Enyedi@ericsson.com" <Gabor.Sandor.Enyedi@ericsson.com>, "Andras.Csaszar@ericsson.com" <Andras.Csaszar@ericsson.com>, "jeff.tantsura@ericsson.com" <jeff.tantsura@ericsson.com>, "russw@riw.us" <russw@riw.us>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Topic: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Index: AdBohapCLAg3Un3wSOKmk0bREwcgiQDx3TwQABCKZbA=
Date: Wed, 1 Apr 2015 15:44:13 +0000
Message-ID: <BLUPR05MB2924C52FBB29C49BAE4B0A4A9F30@BLUPR05MB292.namprd05.prod.outlook.com>
References: <327562D94EA7BF428CD805F338C31EF04FB31052@NKGEML512-MBS.china.huawei.com> <31522_1427875913_551BA849_31522_7681_1_53C29892C857584299CBF5D05346208A0EB8CE2B@PEXCVZYM11.corporate.adroot.infra.ftgroup>
In-Reply-To: <31522_1427875913_551BA849_31522_7681_1_53C29892C857584299CBF5D05346208A0EB8CE2B@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.239.13]
authentication-results: orange.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1256;
x-microsoft-antispam-prvs: <BY1PR0501MB1256B9BEE482C70A498BDB1FA9F30@BY1PR0501MB1256.namprd05.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(51444003)(164054003)(377454003)(2201001)(102836002)(54356999)(15975445007)(87936001)(16236675004)(2656002)(19580405001)(2501003)(19580395003)(99286002)(76176999)(19609705001)(74316001)(66066001)(2900100001)(19625215002)(76576001)(77156002)(230783001)(46102003)(122556002)(86362001)(92566002)(5890100001)(50986999)(77096005)(62966003)(40100003)(2950100001)(19300405004)(33656002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1256; H:BLUPR05MB292.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:BY1PR0501MB1256; BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1256; 
x-forefront-prvs: 053315510E
Content-Type: multipart/alternative; boundary="_000_BLUPR05MB2924C52FBB29C49BAE4B0A4A9F30BLUPR05MB292namprd_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Apr 2015 15:44:13.5289 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0501MB1256
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/gsMwI0mFeyxbSorNz4Sb21mKy04>
Cc: "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: Wed, 01 Apr 2015 15:44:27 -0000

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

Bruno,

I agree.  Does the following text work to implement your s/Other/All sugges=
tion?
"All existing and proposed solutions have tradeoffs.  Some of these tradeof=
fs are described below."

In terms of including other solution comparison metrics, I think that makes=
 sense as well.  Would you be able to propose text for the table and descri=
ptions to incorporate other comparison metrics?

Thanks,
Chris

From: bruno.decraene@orange.com [mailto:bruno.decraene@orange.com]
Sent: Wednesday, April 01, 2015 3:12 AM
To: Anil Kumar S N (VRP Network BL); Alia Atlas; Robert Kebler; Chris Bower=
s; Gabor.Sandor.Enyedi@ericsson.com; Andras.Csaszar@ericsson.com; jeff.tant=
sura@ericsson.com; russw@riw.us
Cc: rtgwg@ietf.org; pierre.francois@imdea.org
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Chris, authors,

Comparing IP FRR methods is a difficult task... The choice of metrics (of c=
omparisons) is difficult and for some (solution, metric) the evaluation is =
very topology dependent.

That being said, it would be interesting to add another metric, related to =
the "quality" of the routing/placement of the FRR path. e.g. for short: opt=
imality of the FRR path (according to the IGP metric). But others quality m=
ay be taken into account e.g. naturally provisioned with enough capacity (i=
n a network having enough capacity to handle single failure), naturally pol=
icy friendly (as per LFA policy).

Another metric, may be how easy is the solution/FRR path determination for =
the human brain/network operators. Because ease of computation for computer=
 is a good thing, but in the end computer follows Moore's Law while human b=
rain do not.

IMHO it may be interesting to indicate the possibility for the SP to choose=
 between link protection, node protection, and SRLG protection, eventually =
on a per PLR/protected link basis. Indeed, the bigger protection may not be=
 the best as it's a trade-off impacting the optimality of the detour path. =
One may prefer link protection only, if the % of node failure is small and =
the detour to avoid the node is big.

The above being considered, the first sentence could probably be slightly m=
odified ( :s/Other/All )  since IMHO MRT has also trade-offs.

Thanks,
Regards,
Bruno


From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Anil Kumar S N (VR=
P Network BL)
Sent: Saturday, March 28, 2015 12:55 PM
To: akatlas@juniper.net<mailto:akatlas@juniper.net>; rkebler@juniper.net<ma=
ilto:rkebler@juniper.net>; cbowers@juniper.net<mailto:cbowers@juniper.net>;=
 Gabor.Sandor.Enyedi@ericsson.com<mailto:Gabor.Sandor.Enyedi@ericsson.com>;=
 Andras.Csaszar@ericsson.com<mailto:Andras.Csaszar@ericsson.com>; jeff.tant=
sura@ericsson.com<mailto:jeff.tantsura@ericsson.com>; russw@riw.us<mailto:r=
ussw@riw.us>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>; rtgwg-owner@ietf.org<m=
ailto:rtgwg-owner@ietf.org>
Subject: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Authors,

      In  "comparison of IP/LDP FRR Methods" section of the document , I fe=
el we should add comparison with TI-LFA (draft-francois-spring-segment-rout=
ing-ti-lfa-01) where TI-LFA approach achieves guaranteed coverage  against =
link or node failure, in any IGP network, relying on the  flexibility of SR=
. This will give readers better picture and enables them with more informat=
ion so that they can choose MRT if they feel it suites their requirement be=
tter; compared to IT-LFA.
Changes :

1.  Introduction :

   Other existing or proposed solutions are partial solutions or have
   significant issues, as described below.

                 Summary Comparison of IP/LDP FRR Methods

   +---------+-------------+-------------+-----------------------------+
   |  Method |   Coverage  |  Alternate  |    Computation (in SPFs)    |
   |         |             |   Looping?  |                             |
   +---------+-------------+-------------+-----------------------------+
   | MRT-FRR |     100%    |     None    |         less than 3         |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   |   LFA   |   Partial   |   Possible  |         per neighbor        |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   |  Remote |   Partial   |   Possible  |    per neighbor (link) or   |
   |   LFA   |  Link/Node  |             |  neighbor's neighbor (node) |
   |         |             |             |                             |
   | Not-Via |     100%    |     None    |      per link and node      |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   | TI-LFA  |     100%    |   Possible  |    per neighbor (link) or   |
   |         |  Link/Node  |             |  neighbor's neighbor (node) |
   |         |             |             |                             |
   +---------+-------------+-------------+-----------------------------+

                                  Table 1


   TI-LFA: Topology Independent Loop-free Alternate Fast
   Re-route (TI-LFA), aimed at providing link and node protection of
   node and adjacency segments within the Segment Routing (SR)
   framework [draft-francois-spring-segment-routing-ti-lfa-01].
   Has improved coverage over LFAs and Remote LFA for link and node
   protection and also guarantees complete coverage. The trade-off
   of looping traffic to improve coverage is still made.
  The computation required is quite high with added complexity.
   TI-LFA is supported only MPLS data plane with a requirement to
   carry additional MPLS label stack on the link failure; on certain
   topologies stack size can grow significantly based repair path.

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel



___________________________________________________________________________=
______________________________________________



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.

--_000_BLUPR05MB2924C52FBB29C49BAE4B0A4A9F30BLUPR05MB292namprd_
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;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-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",serif;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;}
span.EmailStyle19
	{mso-style-type:personal;
	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:Consolas;}
span.EmailStyle22
	{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.25in 1.0in 1.25in;}
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 lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Bruno,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I agree. &nbsp;Does th=
e following text work to implement your s/Other/All suggestion?<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&#8220;All existing an=
d proposed solutions have tradeoffs. &nbsp;Some of these tradeoffs are desc=
ribed below.&#8220;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In terms of including =
other solution comparison metrics, I think that makes sense as well.&nbsp; =
Would you be able to propose text for the table and descriptions to incorpo=
rate other comparison metrics?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Chris<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> bruno.decraene@orange.com [mailto:bruno=
.decraene@orange.com]
<br>
<b>Sent:</b> Wednesday, April 01, 2015 3:12 AM<br>
<b>To:</b> Anil Kumar S N (VRP Network BL); Alia Atlas; Robert Kebler; Chri=
s Bowers; Gabor.Sandor.Enyedi@ericsson.com; Andras.Csaszar@ericsson.com; je=
ff.tantsura@ericsson.com; russw@riw.us<br>
<b>Cc:</b> rtgwg@ietf.org; pierre.francois@imdea.org<br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Chris, authors,<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Comparing IP FRR metho=
ds is a difficult task&#8230; The choice of metrics (of comparisons) is dif=
ficult and for some (solution, metric) the evaluation is very topology depe=
ndent.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">That being said, it wo=
uld be interesting to add another metric, related to the &#8220;quality&#82=
21; of the routing/placement of the FRR path. e.g. for short: optimality of=
 the FRR path (according to the IGP metric). But
 others quality may be taken into account e.g. naturally provisioned with e=
nough capacity (in a network having enough capacity to handle single failur=
e), naturally policy friendly (as per LFA policy).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Another metric, may be=
 how easy is the solution/FRR path determination for the human brain/networ=
k operators. Because ease of computation for computer is a good thing, but =
in the end computer follows Moore&#8217;s
 Law while human brain do not.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">IMHO it may be interes=
ting to indicate the possibility for the SP to choose between link protecti=
on, node protection, and SRLG protection, eventually on a per PLR/protected=
 link basis. Indeed, the bigger protection
 may not be the best as it&#8217;s a trade-off impacting the optimality of =
the detour path. One may prefer link protection only, if the % of node fail=
ure is small and the detour to avoid the node is big.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The above being consid=
ered, the first sentence could probably be slightly modified ( :s/Other/All=
 )&nbsp; since IMHO MRT has also trade-offs.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Bruno<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span lang=3D"FR" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,sans-serif">From:</span></b><span lang=3D"FR" sty=
le=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,sans-serif"> rtgwg [<=
a href=3D"mailto:rtgwg-bounces@ietf.org">mailto:rtgwg-bounces@ietf.org</a>]
<b>On Behalf Of </b>Anil Kumar S N (VRP Network BL)<br>
<b>Sent:</b> Saturday, March 28, 2015 12:55 PM<br>
<b>To:</b> <a href=3D"mailto:akatlas@juniper.net">akatlas@juniper.net</a>; =
<a href=3D"mailto:rkebler@juniper.net">
rkebler@juniper.net</a>; <a href=3D"mailto:cbowers@juniper.net">cbowers@jun=
iper.net</a>;
<a href=3D"mailto:Gabor.Sandor.Enyedi@ericsson.com">Gabor.Sandor.Enyedi@eri=
csson.com</a>;
<a href=3D"mailto:Andras.Csaszar@ericsson.com">Andras.Csaszar@ericsson.com<=
/a>; <a href=3D"mailto:jeff.tantsura@ericsson.com">
jeff.tantsura@ericsson.com</a>; <a href=3D"mailto:russw@riw.us">russw@riw.u=
s</a>; <a href=3D"mailto:rtgwg@ietf.org">
rtgwg@ietf.org</a>; <a href=3D"mailto:rtgwg-owner@ietf.org">rtgwg-owner@iet=
f.org</a><br>
<b>Subject:</b> draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p></sp=
an></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"FR"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">Hi Authors,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In &nbsp;&#8220;compa=
rison of IP/LDP FRR Methods&#8221; section of the document , I feel we shou=
ld add comparison with TI-LFA (draft-francois-spring-segment-routing-ti-lfa=
-01) where TI-LFA approach achieves guaranteed coverage &nbsp;against link =
or node
 failure, in any IGP network, relying on the&nbsp; flexibility of SR. This =
will give readers better picture and enables them with more information so =
that they can choose MRT if they feel it suites their requirement better; c=
ompared to IT-LFA.<o:p></o:p></p>
<p class=3D"MsoNormal">Changes :<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,sans-serif">1.&nbsp; Introduction :</span></b><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; Other exis=
ting or proposed solutions are partial solutions or have<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; significan=
t issues, as described below.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif"><o:p>&nbsp;</o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; S=
ummary Comparison of IP/LDP FRR Methods<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif"><o:p>&nbsp;</o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; &#43;-----=
----&#43;-------------&#43;-------------&#43;-----------------------------&=
#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp; Me=
thod |&nbsp;&nbsp; Coverage&nbsp; |&nbsp; Alternate&nbsp; |&nbsp;&nbsp;&nbs=
p; Computation (in SPFs)&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; Looping?&nbsp; |&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; &#43;-----=
----&#43;-------------&#43;-------------&#43;-----------------------------&=
#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; | MRT-FRR =
|&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; =
None&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; le=
ss than 3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp; LFA&nbsp;&nbsp; |&nbsp;&nbsp; Partial&nbsp;&nbsp; |&nbsp;&nbsp; Possibl=
e&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; per neighbor&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp; Re=
mote |&nbsp;&nbsp; Partial&nbsp;&nbsp; |&nbsp;&nbsp; Possible&nbsp; |&nbsp;=
&nbsp;&nbsp; per neighbor (link) or&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp; LFA&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; neighbor's neighbor (nod=
e) |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; | Not-Via =
|&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; =
None&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; per link and node&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; | &nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; Link/Node&nbsp; |&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp; | TI-LFA &nbsp;|&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp; |&nbsp;=
 &nbsp;Possible&nbsp; |&nbsp;&nbsp;&nbsp; per neighbor (link) or&nbsp;&nbsp=
; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp; |&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; Link/Node&nbs=
p; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; |&nbsp; neighbor's neighbor (node) |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; &#43;-----=
----&#43;-------------&#43;-------------&#43;-----------------------------&=
#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif"><o:p>&nbsp;</o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Tab=
le 1</span><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp; TI-LFA: Topology Independent Loop-free Alternate Fast<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp; Re-route (TI-LFA), aimed at providing link and node protection of<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp; node and adjacency segments within the Segment Routing (SR)<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp; framework [draft-francois-spring-segment-routing-ti-lfa-01].<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp; &n=
bsp;Has improved coverage over LFAs and Remote LFA for link and node
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp;&nbsp;protection and also guarantees complete coverage. The trade-off
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp;&nbsp;of looping traffic to improve coverage is still made.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp;The computation required is quite high with added complexity.<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp; TI-LFA is supported only MPLS data plane with a requirement to
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp;&nbsp;carry additional MPLS label stack on the link failure; on certain<=
o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp; &n=
bsp;topologies stack size can grow significantly based repair path.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks &amp; Regards<o:p></o:p></p>
<p class=3D"MsoNormal">Anil S N<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&#8220;Be liberal in what you accept, and conservati=
ve in what you send&#8221; - Jon Postel<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<pre><span lang=3D"FR">____________________________________________________=
_____________________________________________________________________<o:p><=
/o:p></span></pre>
<pre><span lang=3D"FR"><o:p>&nbsp;</o:p></span></pre>
<pre><span lang=3D"FR">Ce message et ses pieces jointes peuvent contenir de=
s informations confidentielles ou privilegiees et ne doivent donc<o:p></o:p=
></span></pre>
<pre><span lang=3D"FR">pas etre diffuses, exploites ou copies sans autorisa=
tion. Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o=
:p></span></pre>
<pre><span lang=3D"FR">a l'expediteur et le detruire ainsi que les pieces j=
ointes. Les messages electroniques etant susceptibles d'alteration,<o:p></o=
:p></span></pre>
<pre><span lang=3D"FR">Orange decline toute responsabilite si ce message a =
ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span lang=3D"FR"><o:p>&nbsp;</o:p></span></pre>
<pre><span lang=3D"FR">This message and its attachments may contain confide=
ntial or privileged information that may be protected by law;<o:p></o:p></s=
pan></pre>
<pre><span lang=3D"FR">they should not be distributed, used or copied witho=
ut authorisation.<o:p></o:p></span></pre>
<pre><span lang=3D"FR">If you have received this email in error, please not=
ify the sender and delete this message and its attachments.<o:p></o:p></spa=
n></pre>
<pre><span lang=3D"FR">As emails may be altered, Orange is not liable for m=
essages that have been modified, changed or falsified.<o:p></o:p></span></p=
re>
<pre><span lang=3D"FR">Thank you.<o:p></o:p></span></pre>
</div>
</body>
</html>

--_000_BLUPR05MB2924C52FBB29C49BAE4B0A4A9F30BLUPR05MB292namprd_--


From nobody Wed Apr  1 09:44:13 2015
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 EB1581AD2A4 for <rtgwg@ietfa.amsl.com>; Wed,  1 Apr 2015 09:44:05 -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 gDH9d01nHue4 for <rtgwg@ietfa.amsl.com>; Wed,  1 Apr 2015 09:43:55 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0112.outbound.protection.outlook.com [65.55.169.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A4AA1AD35B for <rtgwg@ietf.org>; Wed,  1 Apr 2015 09:43:32 -0700 (PDT)
Received: from BLUPR05MB292.namprd05.prod.outlook.com (10.141.23.27) by BY1PR0501MB1253.namprd05.prod.outlook.com (25.160.200.14) with Microsoft SMTP Server (TLS) id 15.1.118.21; Wed, 1 Apr 2015 16:43:29 +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.01.0118.022; Wed, 1 Apr 2015 16:43:29 +0000
From: Chris Bowers <cbowers@juniper.net>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>, Alia Atlas <akatlas@juniper.net>, Robert Kebler <rkebler@juniper.net>, "Gabor.Sandor.Enyedi@ericsson.com" <Gabor.Sandor.Enyedi@ericsson.com>, "Andras.Csaszar@ericsson.com" <Andras.Csaszar@ericsson.com>, "jeff.tantsura@ericsson.com" <jeff.tantsura@ericsson.com>, "russw@riw.us" <russw@riw.us>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Topic: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Index: AdBohapCLAg3Un3wSOKmk0bREwcgiQDiTs4wABBanbAAEjQyoA==
Date: Wed, 1 Apr 2015 16:43:29 +0000
Message-ID: <BLUPR05MB2920299048499D0BDF4C4A8A9F30@BLUPR05MB292.namprd05.prod.outlook.com>
References: <327562D94EA7BF428CD805F338C31EF04FB31080@NKGEML512-MBS.china.huawei.com> <BLUPR05MB292105B133237D6FF24FD1CA9F30@BLUPR05MB292.namprd05.prod.outlook.com> <31522_1427875907_551BA843_31522_7672_1_53C29892C857584299CBF5D05346208A0EB8AE1B@PEXCVZYM11.corporate.adroot.infra.ftgroup>
In-Reply-To: <31522_1427875907_551BA843_31522_7672_1_53C29892C857584299CBF5D05346208A0EB8AE1B@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.239.13]
authentication-results: orange.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1253;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(377454003)(164054003)(62966003)(77096005)(87936001)(230783001)(40100003)(76576001)(99286002)(46102003)(19617315012)(16236675004)(2201001)(92566002)(33656002)(54356999)(2950100001)(77156002)(19580395003)(2656002)(102836002)(19580405001)(50986999)(86362001)(66066001)(2501003)(19625215002)(5890100001)(76176999)(122556002)(2900100001)(15975445007)(19609705001)(74316001)(19300405004); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1253; H:BLUPR05MB292.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-microsoft-antispam-prvs: <BY1PR0501MB12536DC3DD0B5E4B203957B7A9F30@BY1PR0501MB1253.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:BY1PR0501MB1253; BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1253; 
x-forefront-prvs: 053315510E
Content-Type: multipart/alternative; boundary="_000_BLUPR05MB2920299048499D0BDF4C4A8A9F30BLUPR05MB292namprd_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Apr 2015 16:43:29.5813 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0501MB1253
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/v7OjUURHOcA5UOz91TyFGWkraGw>
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, 01 Apr 2015 16:44:06 -0000

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

Bruno,

Here is proposed text to address your comments.  Tell me if this works.

With respect to the sentence: "The trade-off of looping traffic to improve =
coverage is still made."  I had assumed that Anil was referring to the scen=
ario where an SRLG produces correlated link failures such that two nodes ha=
ve different opinions about what the "new" topology is.  I haven't seen a s=
pecific topology that will produce looping for TI-LFA, but I also haven't s=
een a proof that TI-LFA avoids this type of looping.  Perhaps Anil has some=
 insight into this topic since he proposed the text in question.  For the m=
oment, I have removed that sentence until we get clarification.

                <t hangText=3D"TI-LFA: ">Topology Independent Loop-free
                Alternate Fast Re-route (TI-LFA) <xref
                target=3D"I-D.francois-spring-segment-routing-ti-lfa"/> aim=
s to
                provide link and node protection of node and adjacency
                segments within the Segment Routing (SR) framework.  It
                guarantees complete coverage.  The TI-LFA computation for
                link-protection is fairly straightforward, while the
                computation for node-protection is more complex.  For
                link-protection with symmetric link costs, TI-LFA can provi=
de
                complete coverage using an MPLS label stack with two labels=
.
                For node protection on arbitrary topologies, the label stac=
k
                size can grow significantly based on repair path.  Note tha=
t
                TI-LFA requires shortest path forwarding based on SR
                Node-SIDs, as opposed to LDP labels, in order to construct
                label stacks for backups paths without relying on a large
                number of targeted LDP sessions to learn remote FEC-label
                bindings.  It also requires the use of Adj-SIDs to achieve
                100% coverage.

From: bruno.decraene@orange.com [mailto:bruno.decraene@orange.com]
Sent: Wednesday, April 01, 2015 3:12 AM
To: Chris Bowers; Anil Kumar S N (VRP Network BL); Alia Atlas; Robert Keble=
r; Gabor.Sandor.Enyedi@ericsson.com; Andras.Csaszar@ericsson.com; jeff.tant=
sura@ericsson.com; russw@riw.us; rtgwg@ietf.org
Cc: pierre.francois@imdea.org
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Chris,

Thanks for the addition.
Please see inline some comments. [Bruno]

Thanks,
Regards,
Bruno

From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Chris Bowers
Sent: Wednesday, April 01, 2015 3:10 AM
To: Anil Kumar S N (VRP Network BL); Alia Atlas; Robert Kebler; Gabor.Sando=
r.Enyedi@ericsson.com<mailto:Gabor.Sandor.Enyedi@ericsson.com>; Andras.Csas=
zar@ericsson.com<mailto:Andras.Csaszar@ericsson.com>; jeff.tantsura@ericsso=
n.com<mailto:jeff.tantsura@ericsson.com>; russw@riw.us<mailto:russw@riw.us>=
; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Anil,

Thanks for your input and proposed text.  I added the text below (which is =
a slightly modified version of your proposed text) to the most recent versi=
on which is being maintained at:
https://github.com/cbowers/draft-ietf-rtgwg-mrt-frr-architecture

Tell me if you are OK with the final sentence that I added as well, or you =
can propose some other wording.

Thanks,
Chris

   TI-LFA:    Topology Independent Loop-free Alternate Fast Re-route
      (TI-LFA) [I-D.francois-spring-segment-routing-ti-lfa] aims to
      provide link and node protection of node and adjacency segments
      within the Segment Routing (SR) framework.  It has improved
      coverage over LFA and Remote LFA for link and node protection and
      also guarantees complete coverage.
[Bruno] The last sentence could probably be shortened by only keeping the l=
ast part. "It guarantees complete coverage"


The trade-off of looping
      traffic to improve coverage is still made.
[Bruno] I'm not sure to see what you mean. Contrary to LFA & RLFA, I don't =
think TI-LFA makes such tradeoff.

  The computation
      required is quite high with added complexity.
[Bruno] As in the RLFA description you have made the distinction between li=
nk and node protection, it would be fair to do the same for TI-LFA. (Link p=
rotection computation is much easier)

  TI-LFA is supported
      only for the MPLS data plane due to the requirement for the PLR to
      impose an MPLS label stack on link failure.  On certain topologies
      the label stack size can grow significantly based on repair path.
[Bruno] I agree for node failure. For link failure, this is more debatable =
as compared to RLFA it may require at most 1 additional label. (assuming sy=
mmetric link costs)

      Note that TI-LFA requires shortest path forwarding based on SR
      Node-SIDs, as opposed to LDP labels, in order to construct label
      stacks for backups paths without relying on a large number of
      targeted LDP sessions to learn remote FEC-label bindings.
[Bruno] It also requires Adj-SID (in order to provide 100% coverage).


From: Anil Kumar S N (VRP Network BL) [mailto:anil.sn@huawei.com]
Sent: Saturday, March 28, 2015 8:10 AM
To: Alia Atlas; Robert Kebler; Chris Bowers; Gabor.Sandor.Enyedi@ericsson.c=
om<mailto:Gabor.Sandor.Enyedi@ericsson.com>; Andras.Csaszar@ericsson.com<ma=
ilto:Andras.Csaszar@ericsson.com>; jeff.tantsura@ericsson.com<mailto:jeff.t=
antsura@ericsson.com>; russw@riw.us<mailto:russw@riw.us>; rtgwg@ietf.org<ma=
ilto:rtgwg@ietf.org>
Subject: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Authors,

      In  "comparison of IP/LDP FRR Methods" section of the document , I fe=
el we should add comparison with TI-LFA (draft-francois-spring-segment-rout=
ing-ti-lfa-01) where TI-LFA approach achieves guaranteed coverage  against =
link or node failure, in any IGP network, relying on the  flexibility of SR=
. This will give readers better picture and enables them with more informat=
ion so that they can choose MRT if they feel it suites their requirement be=
tter; compared to IT-LFA...
Changes :

1.  Introduction :

   Other existing or proposed solutions are partial solutions or have
   significant issues, as described below.

                 Summary Comparison of IP/LDP FRR Methods

   +---------+-------------+-------------+-----------------------------+
   |  Method |   Coverage  |  Alternate  |    Computation (in SPFs)    |
   |         |             |   Looping?  |                             |
   +---------+-------------+-------------+-----------------------------+
   | MRT-FRR |     100%    |     None    |         less than 3         |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   |   LFA   |   Partial   |   Possible  |         per neighbor        |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   |  Remote |   Partial   |   Possible  |    per neighbor (link) or   |
   |   LFA   |  Link/Node  |             |  neighbor's neighbor (node) |
   |         |             |             |                             |
   | Not-Via |     100%    |     None    |      per link and node      |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   | TI-LFA  |     100%    |   Possible  |    per neighbor (link) or   |
   |         |  Link/Node  |             |  neighbor's neighbor (node) |
   |         |             |             |                             |
   +---------+-------------+-------------+-----------------------------+

                                  Table 1


   TI-LFA: Topology Independent Loop-free Alternate Fast
   Re-route (TI-LFA), aimed at providing link and node protection of
   node and adjacency segments within the Segment Routing (SR)
   framework [draft-francois-spring-segment-routing-ti-lfa-01].
   Has improved coverage over LFAs and Remote LFA for link and node
   protection and also guarantees complete coverage. The trade-off
   of looping traffic to improve coverage is still made.
  The computation required is quite high with added complexity.
   TI-LFA is supported only MPLS data plane with a requirement to
   carry additional MPLS label stack on the link failure; on certain
   topologies stack size can grow significantly based repair path.

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel



___________________________________________________________________________=
______________________________________________



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.

--_000_BLUPR05MB2920299048499D0BDF4C4A8A9F30BLUPR05MB292namprd_
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;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-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:11.0pt;
	font-family:"Calibri",sans-serif;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma",sans-serif;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New",serif;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI",sans-serif;}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
	{mso-style-name:"Pr\00E9format\00E9 HTML";
	mso-style-link:"Pr\00E9format\00E9 HTML Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:Consolas;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle24
	{mso-style-type:personal;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
p.Textedebulles, li.Textedebulles, div.Textedebulles
	{mso-style-name:"Texte de bulles";
	mso-style-link:"Texte de bulles Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma",sans-serif;}
span.EmailStyle29
	{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.25in 1.0in 1.25in;}
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 lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Bruno,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Here is proposed text =
to address your comments.&nbsp; Tell me if this works.<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">With respect to the se=
ntence: &#8220;The trade-off of looping traffic to improve coverage is stil=
l made.&#8221;&nbsp; I had assumed that Anil was referring to the scenario =
where an SRLG produces correlated link failures such
 that two nodes have different opinions about what the &quot;new&quot; topo=
logy is.&nbsp; I haven&#8217;t seen a specific topology that will produce l=
ooping for TI-LFA, but I also haven&#8217;t seen a proof that TI-LFA avoids=
 this type of looping.&nbsp; Perhaps Anil has some insight into
 this topic since he proposed the text in question.&nbsp; For the moment, I=
 have removed that sentence until we get clarification.<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;t =
hangText=3D&quot;TI-LFA: &quot;&gt;Topology Independent Loop-free<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Altern=
ate Fast Re-route (TI-LFA) &lt;xref<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; target=
=3D&quot;I-D.francois-spring-segment-routing-ti-lfa&quot;/&gt; aims to<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; provid=
e link and node protection of node and adjacency<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; segmen=
ts within the Segment Routing (SR) framework.&nbsp; It<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; guaran=
tees complete coverage.&nbsp; The TI-LFA computation for<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; link-p=
rotection is fairly straightforward, while the<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; comput=
ation for node-protection is more complex.&nbsp; For<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; link-p=
rotection with symmetric link costs, TI-LFA can provide<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; comple=
te coverage using an MPLS label stack with two labels.<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; For no=
de protection on arbitrary topologies, the label stack<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; size c=
an grow significantly based on repair path.&nbsp; Note that<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TI-LFA=
 requires shortest path forwarding based on SR<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Node-S=
IDs, as opposed to LDP labels, in order to construct<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; label =
stacks for backups paths without relying on a large<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; number=
 of targeted LDP sessions to learn remote FEC-label<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bindin=
gs.&nbsp; It also requires the use of Adj-SIDs to achieve<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 100% c=
overage. <o:p>
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> bruno.decraene@orange.com [mailto:bruno=
.decraene@orange.com]
<br>
<b>Sent:</b> Wednesday, April 01, 2015 3:12 AM<br>
<b>To:</b> Chris Bowers; Anil Kumar S N (VRP Network BL); Alia Atlas; Rober=
t Kebler; Gabor.Sandor.Enyedi@ericsson.com; Andras.Csaszar@ericsson.com; je=
ff.tantsura@ericsson.com; russw@riw.us; rtgwg@ietf.org<br>
<b>Cc:</b> pierre.francois@imdea.org<br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Chris,<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks for the additio=
n.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Please see inline some=
 comments. [Bruno]<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Bruno<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span lang=3D"FR" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,sans-serif">From:</span></b><span lang=3D"FR" sty=
le=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,sans-serif"> rtgwg [<=
a href=3D"mailto:rtgwg-bounces@ietf.org">mailto:rtgwg-bounces@ietf.org</a>]
<b>On Behalf Of </b>Chris Bowers<br>
<b>Sent:</b> Wednesday, April 01, 2015 3:10 AM<br>
<b>To:</b> Anil Kumar S N (VRP Network BL); Alia Atlas; Robert Kebler; <a h=
ref=3D"mailto:Gabor.Sandor.Enyedi@ericsson.com">
Gabor.Sandor.Enyedi@ericsson.com</a>; <a href=3D"mailto:Andras.Csaszar@eric=
sson.com">
Andras.Csaszar@ericsson.com</a>; <a href=3D"mailto:jeff.tantsura@ericsson.c=
om">jeff.tantsura@ericsson.com</a>;
<a href=3D"mailto:russw@riw.us">russw@riw.us</a>; <a href=3D"mailto:rtgwg@i=
etf.org">rtgwg@ietf.org</a><br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"FR"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Anil,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks for your input =
and proposed text.&nbsp; I added the text below (which is a slightly modifi=
ed version of your proposed text) to the most recent version which is being=
 maintained at:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><a href=3D"https://git=
hub.com/cbowers/draft-ietf-rtgwg-mrt-frr-architecture">https://github.com/c=
bowers/draft-ietf-rtgwg-mrt-frr-architecture</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Tell me if you are OK =
with the final sentence that I added as well, or you can propose some other=
 wording.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Chris<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp; TI-LFA:&nbsp;&nbsp;&nbsp; Topology Inde=
pendent Loop-free Alternate Fast Re-route<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (TI-LFA) [I-D.francoi=
s-spring-segment-routing-ti-lfa] aims to<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; provide link and node=
 protection of node and adjacency segments<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; within the Segment Ro=
uting (SR) framework.&nbsp; It has improved<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; coverage over LFA and=
 Remote LFA for link and node protection and<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; also guarantees compl=
ete coverage.&nbsp;<span style=3D"color:#1F497D"><o:p></o:p></span></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] The last sente=
nce could probably be shortened by only keeping the last part. &#8220;It gu=
arantees complete coverage&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">The trade-off of looping<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; traffic to improve co=
verage is still made.<span style=3D"color:#1F497D"><o:p></o:p></span></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] I&#8217;m not =
sure to see what you mean. Contrary to LFA &amp; RLFA, I don&#8217;t think =
TI-LFA makes such tradeoff.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp; The computation<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; required is quite hig=
h with added complexity.<span style=3D"color:#1F497D"><o:p></o:p></span></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] As in the RLFA=
 description you have made the distinction between link and node protection=
, it would be fair to do the same for TI-LFA. (Link protection computation =
is much easier)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp; TI-LFA is supported<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; only for the MPLS dat=
a plane due to the requirement for the PLR to<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; impose an MPLS label =
stack on link failure.&nbsp; On certain topologies<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the label stack size =
can grow significantly based on repair path.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] I agree for no=
de failure. For link failure, this is more debatable as compared to RLFA it=
 may require at most 1 additional label. (assuming symmetric link costs)<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Note that TI-LFA requ=
ires shortest path forwarding based on SR<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Node-SIDs, as opposed=
 to LDP labels, in order to construct label<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; stacks for backups pa=
ths without relying on a large number of<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; targeted LDP sessions=
 to learn remote FEC-label bindings.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] It also requir=
es Adj-SID (in order to provide 100% coverage).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></=
span></b></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Anil Kumar S N (VRP Network BL) [<a hre=
f=3D"mailto:anil.sn@huawei.com">mailto:anil.sn@huawei.com</a>]
<br>
<b>Sent:</b> Saturday, March 28, 2015 8:10 AM<br>
<b>To:</b> Alia Atlas; Robert Kebler; Chris Bowers; <a href=3D"mailto:Gabor=
.Sandor.Enyedi@ericsson.com">
Gabor.Sandor.Enyedi@ericsson.com</a>; <a href=3D"mailto:Andras.Csaszar@eric=
sson.com">
Andras.Csaszar@ericsson.com</a>; <a href=3D"mailto:jeff.tantsura@ericsson.c=
om">jeff.tantsura@ericsson.com</a>;
<a href=3D"mailto:russw@riw.us">russw@riw.us</a>; <a href=3D"mailto:rtgwg@i=
etf.org">rtgwg@ietf.org</a><br>
<b>Subject:</b> draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi Authors,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In &nbsp;&#8220;compa=
rison of IP/LDP FRR Methods&#8221; section of the document , I feel we shou=
ld add comparison with TI-LFA (draft-francois-spring-segment-routing-ti-lfa=
-01) where TI-LFA approach achieves guaranteed coverage &nbsp;against link =
or node
 failure, in any IGP network, relying on the&nbsp; flexibility of SR. This =
will give readers better picture and enables them with more information so =
that they can choose MRT if they feel it suites their requirement better; c=
ompared to IT-LFA&#8230;<o:p></o:p></p>
<p class=3D"MsoNormal">Changes :<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,sans-serif">1.&nbsp; Introduction :</span></b><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; Other exis=
ting or proposed solutions are partial solutions or have<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; significan=
t issues, as described below.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif"><o:p>&nbsp;</o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; S=
ummary Comparison of IP/LDP FRR Methods<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif"><o:p>&nbsp;</o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; &#43;-----=
----&#43;-------------&#43;-------------&#43;-----------------------------&=
#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp; Me=
thod |&nbsp;&nbsp; Coverage&nbsp; |&nbsp; Alternate&nbsp; |&nbsp;&nbsp;&nbs=
p; Computation (in SPFs)&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; Looping?&nbsp; |&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; &#43;-----=
----&#43;-------------&#43;-------------&#43;-----------------------------&=
#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; | MRT-FRR =
|&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; =
None&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; le=
ss than 3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp; LFA&nbsp;&nbsp; |&nbsp;&nbsp; Partial&nbsp;&nbsp; |&nbsp;&nbsp; Possibl=
e&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; per neighbor&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp; Re=
mote |&nbsp;&nbsp; Partial&nbsp;&nbsp; |&nbsp;&nbsp; Possible&nbsp; |&nbsp;=
&nbsp;&nbsp; per neighbor (link) or&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp; LFA&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; neighbor's neighbor (nod=
e) |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; | Not-Via =
|&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; =
None&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; per link and node&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; | &nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; Link/Node&nbsp; |&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp; | TI-LFA &nbsp;|&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp; |&nbsp;=
 &nbsp;Possible&nbsp; |&nbsp;&nbsp;&nbsp; per neighbor (link) or&nbsp;&nbsp=
; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp; |&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; Link/Node&nbs=
p; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; |&nbsp; neighbor's neighbor (node) |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif">&nbsp;&nbsp; &#43;-----=
----&#43;-------------&#43;-------------&#43;-----------------------------&=
#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif"><o:p>&nbsp;</o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Tab=
le 1</span><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp; TI-LFA: Topology Independent Loop-free Alternate Fast<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp; Re-route (TI-LFA), aimed at providing link and node protection of<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp; node and adjacency segments within the Segment Routing (SR)<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp; framework [draft-francois-spring-segment-routing-ti-lfa-01].<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp; &n=
bsp;Has improved coverage over LFAs and Remote LFA for link and node
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp;&nbsp;protection and also guarantees complete coverage. The trade-off
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp;&nbsp;of looping traffic to improve coverage is still made.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp;The computation required is quite high with added complexity.<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp; TI-LFA is supported only MPLS data plane with a requirement to
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp;&nb=
sp;&nbsp;carry additional MPLS label stack on the link failure; on certain<=
o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;,serif;color:#00B050">&nbsp; &n=
bsp;topologies stack size can grow significantly based repair path.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks &amp; Regards<o:p></o:p></p>
<p class=3D"MsoNormal">Anil S N<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&#8220;Be liberal in what you accept, and conservati=
ve in what you send&#8221; - Jon Postel<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;,serif">__________________________________________________________=
_______________________________________________________________<o:p></o:p><=
/span></pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;,serif"><o:p>&nbsp;</o:p></span></pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;,serif">Ce message et ses pieces jointes peuvent contenir des info=
rmations confidentielles ou privilegiees et ne doivent donc<o:p></o:p></spa=
n></pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;,serif">pas etre diffuses, exploites ou copies sans autorisation. =
Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o:p></s=
pan></pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;,serif">a l'expediteur et le detruire ainsi que les pieces jointes=
. Les messages electroniques etant susceptibles d'alteration,<o:p></o:p></s=
pan></pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;,serif">Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;,serif"><o:p>&nbsp;</o:p></span></pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;,serif">This message and its attachments may contain confidential =
or privileged information that may be protected by law;<o:p></o:p></span></=
pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;,serif">they should not be distributed, used or copied without aut=
horisation.<o:p></o:p></span></pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;,serif">If you have received this email in error, please notify th=
e sender and delete this message and its attachments.<o:p></o:p></span></pr=
e>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;,serif">As emails may be altered, Orange is not liable for message=
s that have been modified, changed or falsified.<o:p></o:p></span></pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;,serif">Thank you.<o:p></o:p></span></pre>
</div>
</body>
</html>

--_000_BLUPR05MB2920299048499D0BDF4C4A8A9F30BLUPR05MB292namprd_--


From nobody Thu Apr  2 00:12:38 2015
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 2A6EC1B2B81 for <rtgwg@ietfa.amsl.com>; Thu,  2 Apr 2015 00:12:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 zHO3vbOEkICT for <rtgwg@ietfa.amsl.com>; Thu,  2 Apr 2015 00:12:24 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9897B1B2B6A for <rtgwg@ietf.org>; Thu,  2 Apr 2015 00:12:23 -0700 (PDT)
Received: from omfeda07.si.francetelecom.fr (unknown [xx.xx.xx.200]) by omfeda10.si.francetelecom.fr (ESMTP service) with ESMTP id CA42037414D; Thu,  2 Apr 2015 09:12:21 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfeda07.si.francetelecom.fr (ESMTP service) with ESMTP id 9172B1580A1; Thu,  2 Apr 2015 09:12:21 +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.0224.002; Thu, 2 Apr 2015 09:12:21 +0200
From: <bruno.decraene@orange.com>
To: Chris Bowers <cbowers@juniper.net>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Topic: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Index: AdBohapCLAg3Un3wSOKmk0bREwcgiQDx3TwQABCKZbAAIGp1YA==
Date: Thu, 2 Apr 2015 07:12:20 +0000
Message-ID: <22557_1427958741_551CEBD5_22557_5665_1_53C29892C857584299CBF5D05346208A0EB90752@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <327562D94EA7BF428CD805F338C31EF04FB31052@NKGEML512-MBS.china.huawei.com> <31522_1427875913_551BA849_31522_7681_1_53C29892C857584299CBF5D05346208A0EB8CE2B@PEXCVZYM11.corporate.adroot.infra.ftgroup> <BLUPR05MB2924C52FBB29C49BAE4B0A4A9F30@BLUPR05MB292.namprd05.prod.outlook.com>
In-Reply-To: <BLUPR05MB2924C52FBB29C49BAE4B0A4A9F30@BLUPR05MB292.namprd05.prod.outlook.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.6]
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A0EB90752PEXCVZYM11corpo_"
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.4.2.32419
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/qNcpG8GtUHq9h384ml9o1sioYbk>
Cc: Alia Atlas <akatlas@juniper.net>, "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, 02 Apr 2015 07:12:35 -0000

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

Chris,

Your proposed text looks fine. Thanks.
In term of proposing text for comparison metrics, I'll think more about it.

Thanks.
Bruno

PS: an alternative and easier path would be to avoid doing comparison in th=
is document, and leave this to another document (or not ;-) ). However, I a=
gree that a light overview would be good, and hopefully not too controversi=
al.


From: Chris Bowers [mailto:cbowers@juniper.net]
Sent: Wednesday, April 01, 2015 5:44 PM
To: DECRAENE Bruno IMT/OLN; Anil Kumar S N (VRP Network BL); Alia Atlas; Ro=
bert Kebler; Gabor.Sandor.Enyedi@ericsson.com<mailto:Gabor.Sandor.Enyedi@er=
icsson.com>; Andras.Csaszar@ericsson.com<mailto:Andras.Csaszar@ericsson.com=
>; jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericsson.com>; russw@riw=
.us<mailto:russw@riw.us>
Cc: rtgwg@ietf.org<mailto:rtgwg@ietf.org>; pierre.francois@imdea.org<mailto=
:pierre.francois@imdea.org>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Bruno,

I agree.  Does the following text work to implement your s/Other/All sugges=
tion?
"All existing and proposed solutions have tradeoffs.  Some of these tradeof=
fs are described below."

In terms of including other solution comparison metrics, I think that makes=
 sense as well.  Would you be able to propose text for the table and descri=
ptions to incorporate other comparison metrics?

Thanks,
Chris

From: bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> [mailto:b=
runo.decraene@orange.com]
Sent: Wednesday, April 01, 2015 3:12 AM
To: Anil Kumar S N (VRP Network BL); Alia Atlas; Robert Kebler; Chris Bower=
s; Gabor.Sandor.Enyedi@ericsson.com<mailto:Gabor.Sandor.Enyedi@ericsson.com=
>; Andras.Csaszar@ericsson.com<mailto:Andras.Csaszar@ericsson.com>; jeff.ta=
ntsura@ericsson.com<mailto:jeff.tantsura@ericsson.com>; russw@riw.us<mailto=
:russw@riw.us>
Cc: rtgwg@ietf.org<mailto:rtgwg@ietf.org>; pierre.francois@imdea.org<mailto=
:pierre.francois@imdea.org>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Chris, authors,

Comparing IP FRR methods is a difficult task... The choice of metrics (of c=
omparisons) is difficult and for some (solution, metric) the evaluation is =
very topology dependent.

That being said, it would be interesting to add another metric, related to =
the "quality" of the routing/placement of the FRR path. e.g. for short: opt=
imality of the FRR path (according to the IGP metric). But others quality m=
ay be taken into account e.g. naturally provisioned with enough capacity (i=
n a network having enough capacity to handle single failure), naturally pol=
icy friendly (as per LFA policy).

Another metric, may be how easy is the solution/FRR path determination for =
the human brain/network operators. Because ease of computation for computer=
 is a good thing, but in the end computer follows Moore's Law while human b=
rain do not.

IMHO it may be interesting to indicate the possibility for the SP to choose=
 between link protection, node protection, and SRLG protection, eventually =
on a per PLR/protected link basis. Indeed, the bigger protection may not be=
 the best as it's a trade-off impacting the optimality of the detour path. =
One may prefer link protection only, if the % of node failure is small and =
the detour to avoid the node is big.

The above being considered, the first sentence could probably be slightly m=
odified ( :s/Other/All )  since IMHO MRT has also trade-offs.

Thanks,
Regards,
Bruno


From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Anil Kumar S N (VR=
P Network BL)
Sent: Saturday, March 28, 2015 12:55 PM
To: akatlas@juniper.net<mailto:akatlas@juniper.net>; rkebler@juniper.net<ma=
ilto:rkebler@juniper.net>; cbowers@juniper.net<mailto:cbowers@juniper.net>;=
 Gabor.Sandor.Enyedi@ericsson.com<mailto:Gabor.Sandor.Enyedi@ericsson.com>;=
 Andras.Csaszar@ericsson.com<mailto:Andras.Csaszar@ericsson.com>; jeff.tant=
sura@ericsson.com<mailto:jeff.tantsura@ericsson.com>; russw@riw.us<mailto:r=
ussw@riw.us>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>; rtgwg-owner@ietf.org<m=
ailto:rtgwg-owner@ietf.org>
Subject: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Authors,

      In  "comparison of IP/LDP FRR Methods" section of the document , I fe=
el we should add comparison with TI-LFA (draft-francois-spring-segment-rout=
ing-ti-lfa-01) where TI-LFA approach achieves guaranteed coverage  against =
link or node failure, in any IGP network, relying on the  flexibility of SR=
. This will give readers better picture and enables them with more informat=
ion so that they can choose MRT if they feel it suites their requirement be=
tter; compared to IT-LFA.
Changes :

1.  Introduction :

   Other existing or proposed solutions are partial solutions or have
   significant issues, as described below.

                 Summary Comparison of IP/LDP FRR Methods

   +---------+-------------+-------------+-----------------------------+
   |  Method |   Coverage  |  Alternate  |    Computation (in SPFs)    |
   |         |             |   Looping?  |                             |
   +---------+-------------+-------------+-----------------------------+
   | MRT-FRR |     100%    |     None    |         less than 3         |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   |   LFA   |   Partial   |   Possible  |         per neighbor        |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   |  Remote |   Partial   |   Possible  |    per neighbor (link) or   |
   |   LFA   |  Link/Node  |             |  neighbor's neighbor (node) |
   |         |             |             |                             |
   | Not-Via |     100%    |     None    |      per link and node      |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   | TI-LFA  |     100%    |   Possible  |    per neighbor (link) or   |
   |         |  Link/Node  |             |  neighbor's neighbor (node) |
   |         |             |             |                             |
   +---------+-------------+-------------+-----------------------------+

                                  Table 1


   TI-LFA: Topology Independent Loop-free Alternate Fast
   Re-route (TI-LFA), aimed at providing link and node protection of
   node and adjacency segments within the Segment Routing (SR)
   framework [draft-francois-spring-segment-routing-ti-lfa-01].
   Has improved coverage over LFAs and Remote LFA for link and node
   protection and also guarantees complete coverage. The trade-off
   of looping traffic to improve coverage is still made.
  The computation required is quite high with added complexity.
   TI-LFA is supported only MPLS data plane with a requirement to
   carry additional MPLS label stack on the link failure; on certain
   topologies stack size can grow significantly based repair path.

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel



___________________________________________________________________________=
______________________________________________



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.

___________________________________________________________________________=
______________________________________________

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.


--_000_53C29892C857584299CBF5D05346208A0EB90752PEXCVZYM11corpo_
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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-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:"Pr\00E9format\00E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:Consolas;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle24
	{mso-style-type:personal;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle27
	{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:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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 lang=3D"FR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Chris,<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Your pr=
oposed text looks fine. Thanks.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">In term=
 of proposing text for comparison metrics, I&#8217;ll think more about it.<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks.=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Bruno<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">PS: an =
alternative and easier path would be to avoid doing comparison in this docu=
ment, and leave this to another document (or not ;-) ). However, I agree th=
at a light overview would be good, and
 hopefully not too controversial. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Chris Bowers [</span><span style=3D"font-size:10.0pt;=
font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"><a href=3D"mailto:cb=
owers@juniper.net"><span lang=3D"EN-US">mailto:cbowers@juniper.net</span></=
a></span><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;T=
ahoma&quot;,&quot;sans-serif&quot;">]
<br>
<b>Sent:</b> Wednesday, April 01, 2015 5:44 PM<br>
<b>To:</b> DECRAENE Bruno IMT/OLN; Anil Kumar S N (VRP Network BL); Alia At=
las; Robert Kebler;
</span><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot=
;sans-serif&quot;"><a href=3D"mailto:Gabor.Sandor.Enyedi@ericsson.com"><spa=
n lang=3D"EN-US">Gabor.Sandor.Enyedi@ericsson.com</span></a></span><span la=
ng=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot=
;sans-serif&quot;">;
</span><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot=
;sans-serif&quot;"><a href=3D"mailto:Andras.Csaszar@ericsson.com"><span lan=
g=3D"EN-US">Andras.Csaszar@ericsson.com</span></a></span><span lang=3D"EN-U=
S" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-seri=
f&quot;">;
</span><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot=
;sans-serif&quot;"><a href=3D"mailto:jeff.tantsura@ericsson.com"><span lang=
=3D"EN-US">jeff.tantsura@ericsson.com</span></a></span><span lang=3D"EN-US"=
 style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;">;
</span><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot=
;sans-serif&quot;"><a href=3D"mailto:russw@riw.us"><span lang=3D"EN-US">rus=
sw@riw.us</span></a></span><span lang=3D"EN-US" style=3D"font-size:10.0pt;f=
ont-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"><br>
<b>Cc:</b> </span><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&=
quot;,&quot;sans-serif&quot;"><a href=3D"mailto:rtgwg@ietf.org"><span lang=
=3D"EN-US">rtgwg@ietf.org</span></a></span><span lang=3D"EN-US" style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">;
</span><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot=
;sans-serif&quot;"><a href=3D"mailto:pierre.francois@imdea.org"><span lang=
=3D"EN-US">pierre.francois@imdea.org</span></a></span><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&q=
uot;"><br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Bruno,<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">I agree=
. &nbsp;Does the following text work to implement your s/Other/All suggesti=
on?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&#8220;=
All existing and proposed solutions have tradeoffs. &nbsp;Some of these tra=
deoffs are described below.&#8220;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">In term=
s of including other solution comparison metrics, I think that makes sense =
as well.&nbsp; Would you be able to propose text for the table and descript=
ions to incorporate other comparison metrics?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks,=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Chris<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> </span>
<a href=3D"mailto:bruno.decraene@orange.com"><span lang=3D"EN-US">bruno.dec=
raene@orange.com</span></a><span lang=3D"EN-US"> [</span><a href=3D"mailto:=
bruno.decraene@orange.com"><span lang=3D"EN-US">mailto:bruno.decraene@orang=
e.com</span></a><span lang=3D"EN-US">]
<br>
<b>Sent:</b> Wednesday, April 01, 2015 3:12 AM<br>
<b>To:</b> Anil Kumar S N (VRP Network BL); Alia Atlas; Robert Kebler; Chri=
s Bowers;
</span><a href=3D"mailto:Gabor.Sandor.Enyedi@ericsson.com"><span lang=3D"EN=
-US">Gabor.Sandor.Enyedi@ericsson.com</span></a><span lang=3D"EN-US">;
</span><a href=3D"mailto:Andras.Csaszar@ericsson.com"><span lang=3D"EN-US">=
Andras.Csaszar@ericsson.com</span></a><span lang=3D"EN-US">;
</span><a href=3D"mailto:jeff.tantsura@ericsson.com"><span lang=3D"EN-US">j=
eff.tantsura@ericsson.com</span></a><span lang=3D"EN-US">;
</span><a href=3D"mailto:russw@riw.us"><span lang=3D"EN-US">russw@riw.us</s=
pan></a><span lang=3D"EN-US"><br>
<b>Cc:</b> </span><a href=3D"mailto:rtgwg@ietf.org"><span lang=3D"EN-US">rt=
gwg@ietf.org</span></a><span lang=3D"EN-US">;
</span><a href=3D"mailto:pierre.francois@imdea.org"><span lang=3D"EN-US">pi=
erre.francois@imdea.org</span></a><span lang=3D"EN-US"><br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Hi Chri=
s, authors,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Compari=
ng IP FRR methods is a difficult task&#8230; The choice of metrics (of comp=
arisons) is difficult and for some (solution, metric) the evaluation is ver=
y topology dependent.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">That be=
ing said, it would be interesting to add another metric, related to the &#8=
220;quality&#8221; of the routing/placement of the FRR path. e.g. for short=
: optimality of the FRR path (according to the IGP
 metric). But others quality may be taken into account e.g. naturally provi=
sioned with enough capacity (in a network having enough capacity to handle =
single failure), naturally policy friendly (as per LFA policy).<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Another=
 metric, may be how easy is the solution/FRR path determination for the hum=
an brain/network operators. Because ease of computation for computer is a g=
ood thing, but in the end computer follows
 Moore&#8217;s Law while human brain do not.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">IMHO it=
 may be interesting to indicate the possibility for the SP to choose betwee=
n link protection, node protection, and SRLG protection, eventually on a pe=
r PLR/protected link basis. Indeed, the
 bigger protection may not be the best as it&#8217;s a trade-off impacting =
the optimality of the detour path. One may prefer link protection only, if =
the % of node failure is small and the detour to avoid the node is big.<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">The abo=
ve being considered, the first sentence could probably be slightly modified=
 ( :s/Other/All )&nbsp; since IMHO MRT has also trade-offs.<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks,=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Regards=
,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Bruno<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> rtgwg [</span><a href=3D"mailto:rtgwg-bounces@ietf.or=
g"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&=
quot;,&quot;sans-serif&quot;">mailto:rtgwg-bounces@ietf.org</span></a><span=
 lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&q=
uot;sans-serif&quot;">]
<b>On Behalf Of </b>Anil Kumar S N (VRP Network BL)<br>
<b>Sent:</b> Saturday, March 28, 2015 12:55 PM<br>
<b>To:</b> </span><a href=3D"mailto:akatlas@juniper.net"><span lang=3D"EN-U=
S" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-seri=
f&quot;">akatlas@juniper.net</span></a><span lang=3D"EN-US" style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">;
</span><a href=3D"mailto:rkebler@juniper.net"><span lang=3D"EN-US" style=3D=
"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">rk=
ebler@juniper.net</span></a><span lang=3D"EN-US" style=3D"font-size:10.0pt;=
font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">;
</span><a href=3D"mailto:cbowers@juniper.net"><span lang=3D"EN-US" style=3D=
"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">cb=
owers@juniper.net</span></a><span lang=3D"EN-US" style=3D"font-size:10.0pt;=
font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">;
</span><a href=3D"mailto:Gabor.Sandor.Enyedi@ericsson.com"><span lang=3D"EN=
-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-se=
rif&quot;">Gabor.Sandor.Enyedi@ericsson.com</span></a><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&q=
uot;">;
</span><a href=3D"mailto:Andras.Csaszar@ericsson.com"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&q=
uot;">Andras.Csaszar@ericsson.com</span></a><span lang=3D"EN-US" style=3D"f=
ont-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">;
</span><a href=3D"mailto:jeff.tantsura@ericsson.com"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&qu=
ot;">jeff.tantsura@ericsson.com</span></a><span lang=3D"EN-US" style=3D"fon=
t-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">;
</span><a href=3D"mailto:russw@riw.us"><span lang=3D"EN-US" style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">russw@riw=
.us</span></a><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&q=
uot;Tahoma&quot;,&quot;sans-serif&quot;">;
</span><a href=3D"mailto:rtgwg@ietf.org"><span lang=3D"EN-US" style=3D"font=
-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">rtgwg@i=
etf.org</span></a><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-famil=
y:&quot;Tahoma&quot;,&quot;sans-serif&quot;">;
</span><a href=3D"mailto:rtgwg-owner@ietf.org"><span lang=3D"EN-US" style=
=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"=
>rtgwg-owner@ietf.org</span></a><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"><br>
<b>Subject:</b> draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p></sp=
an></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi Authors,<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
In &nbsp;&#8220;comparison of IP/LDP FRR Methods&#8221; section of the docu=
ment , I feel we should add comparison with TI-LFA (draft-francois-spring-s=
egment-routing-ti-lfa-01) where TI-LFA approach achieves guaranteed coverag=
e &nbsp;against
 link or node failure, in any IGP network, relying on the&nbsp; flexibility=
 of SR. This will give readers better picture and enables them with more in=
formation so that they can choose MRT if they feel it suites their requirem=
ent better; compared to IT-LFA.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Changes :<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Arial&quot;,&quot;sans-serif&quot;">1.&nbsp; Introduction :=
</span></b><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; Other existing or proposed solutions are partial solutions=
 or have<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; significant issues, as described below.<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; Summary Comparison of IP/LDP FRR Methods<o:p></o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; &#43;---------&#43;-------------&#43;-------------&#43;---=
--------------------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp; Method |&nbsp;&nbsp; Coverage&nbsp; |&nbsp; Altern=
ate&nbsp; |&nbsp;&nbsp;&nbsp; Computation (in SPFs)&nbsp;&nbsp;&nbsp; |<o:p=
></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&n=
bsp; Looping?&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; &#43;---------&#43;-------------&#43;-------------&#43;---=
--------------------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; | MRT-FRR |&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp;=
 |&nbsp;&nbsp;&nbsp;&nbsp; None&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; less than 3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; =
Link/Node&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp; LFA&nbsp;&nbsp; |&nbsp;&nbsp; Partial&nbsp;&=
nbsp; |&nbsp;&nbsp; Possible&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; per neighbor&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; =
Link/Node&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp; Remote |&nbsp;&nbsp; Partial&nbsp;&nbsp; |&nbsp;&n=
bsp; Possible&nbsp; |&nbsp;&nbsp;&nbsp; per neighbor (link) or&nbsp;&nbsp; =
|<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp; LFA&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbs=
p; neighbor's neighbor (node) |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; | Not-Via |&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp;=
 |&nbsp;&nbsp;&nbsp;&nbsp; None&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; per link and node&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; | &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; =
Link/Node&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp; | TI-LFA &nbsp;|&nbsp;&nbsp;&nbsp;&nbsp; 100=
%&nbsp;&nbsp;&nbsp; |&nbsp; &nbsp;Possible&nbsp; |&nbsp;&nbsp;&nbsp; per ne=
ighbor (link) or&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp; |&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;|&nbsp; Link/Node&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; neighbor's neighbor (node) |<o:p></o:p=
></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; &#43;---------&#43;-------------&#43;-------------&#43;---=
--------------------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; Table 1</span><span lang=3D"EN-US"><o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp; TI-LFA: Topology Independent Loop-free Alter=
nate Fast<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp; Re-route (TI-LFA), aimed at providing link a=
nd node protection of<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp; node and adjacency segments within the Segme=
nt Routing (SR)<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp; framework [draft-francois-spring-segment-rou=
ting-ti-lfa-01].<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp; &nbsp;Has improved coverage over LFAs and Remote L=
FA for link and node
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp;&nbsp;protection and also guarantees complete=
 coverage. The trade-off
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp;&nbsp;of looping traffic to improve coverage =
is still made.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp;The computation required is quite high with a=
dded complexity.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp; TI-LFA is supported only MPLS data plane wit=
h a requirement to
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp;&nbsp;carry additional MPLS label stack on th=
e link failure; on certain<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp; &nbsp;topologies stack size can grow significantly=
 based repair path.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks &amp; Regards<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Anil S N<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&#8220;Be liberal in what you a=
ccept, and conservative in what you send&#8221; - Jon Postel<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<pre>______________________________________________________________________=
___________________________________________________<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Ce message et ses pieces jointes peuvent contenir des informations con=
fidentielles ou privilegiees et ne doivent donc<o:p></o:p></pre>
<pre>pas etre diffuses, exploites ou copies sans autorisation. Si vous avez=
 recu ce message par erreur, veuillez le signaler<o:p></o:p></pre>
<pre>a l'expediteur et le detruire ainsi que les pieces jointes. Les messag=
es electroniques etant susceptibles d'alteration,<o:p></o:p></pre>
<pre>Orange decline toute responsabilite si ce message a ete altere, deform=
e ou falsifie. <span lang=3D"EN-US">Merci.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></pre>
<pre><span lang=3D"EN-US">This message and its attachments may contain conf=
idential or privileged information that may be protected by law;<o:p></o:p>=
</span></pre>
<pre><span lang=3D"EN-US">they should not be distributed, used or copied wi=
thout authorisation.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">If you have received this email in error, please =
notify the sender and delete this message and its attachments.<o:p></o:p></=
span></pre>
<pre><span lang=3D"EN-US">As emails may be altered, Orange is not liable fo=
r messages that have been modified, changed or falsified.<o:p></o:p></span>=
</pre>
<pre>Thank you.<o:p></o:p></pre>
</div>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

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.
</PRE></body>
</html>

--_000_53C29892C857584299CBF5D05346208A0EB90752PEXCVZYM11corpo_--


From nobody Thu Apr  2 00:43:09 2015
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 701BD1B2BA9 for <rtgwg@ietfa.amsl.com>; Thu,  2 Apr 2015 00:43:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 bpHp6qjPNpQd for <rtgwg@ietfa.amsl.com>; Thu,  2 Apr 2015 00:42:56 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E25C01A8980 for <rtgwg@ietf.org>; Thu,  2 Apr 2015 00:42:55 -0700 (PDT)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda10.si.francetelecom.fr (ESMTP service) with ESMTP id 212A3374444; Thu,  2 Apr 2015 09:42:54 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id EAC9A38409B; Thu,  2 Apr 2015 09:42:53 +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.0224.002; Thu, 2 Apr 2015 09:42:53 +0200
From: <bruno.decraene@orange.com>
To: Chris Bowers <cbowers@juniper.net>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Topic: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Index: AdBohapCLAg3Un3wSOKmk0bREwcgiQDiTs4wABBanbAAEjQyoAAe1PUw
Date: Thu, 2 Apr 2015 07:42:52 +0000
Message-ID: <20271_1427960574_551CF2FD_20271_1912_1_53C29892C857584299CBF5D05346208A0EB907E6@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <327562D94EA7BF428CD805F338C31EF04FB31080@NKGEML512-MBS.china.huawei.com> <BLUPR05MB292105B133237D6FF24FD1CA9F30@BLUPR05MB292.namprd05.prod.outlook.com> <31522_1427875907_551BA843_31522_7672_1_53C29892C857584299CBF5D05346208A0EB8AE1B@PEXCVZYM11.corporate.adroot.infra.ftgroup> <BLUPR05MB2920299048499D0BDF4C4A8A9F30@BLUPR05MB292.namprd05.prod.outlook.com>
In-Reply-To: <BLUPR05MB2920299048499D0BDF4C4A8A9F30@BLUPR05MB292.namprd05.prod.outlook.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.6]
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A0EB907E6PEXCVZYM11corpo_"
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.2.12.3031
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/p538WLvtQU_zhqaMvstn41ETw3I>
Cc: Alia Atlas <akatlas@juniper.net>, "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, 02 Apr 2015 07:43:07 -0000

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

Chris,

Please see inline. [Bruno]

From: Chris Bowers [mailto:cbowers@juniper.net]
Sent: Wednesday, April 01, 2015 6:43 PM
To: DECRAENE Bruno IMT/OLN; Anil Kumar S N (VRP Network BL); Alia Atlas; Ro=
bert Kebler; Gabor.Sandor.Enyedi@ericsson.com; Andras.Csaszar@ericsson.com;=
 jeff.tantsura@ericsson.com; russw@riw.us; rtgwg@ietf.org
Cc: pierre.francois@imdea.org
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Bruno,

Here is proposed text to address your comments.  Tell me if this works.

With respect to the sentence: "The trade-off of looping traffic to improve =
coverage is still made."  I had assumed that Anil was referring to the scen=
ario where an SRLG produces correlated link failures such that two nodes ha=
ve different opinions about what the "new" topology is.
[Bruno] On my side, I had assumed that it was related to the "downstream" c=
ondition of (R)LFA.

I haven't seen a specific topology that will produce looping for TI-LFA, bu=
t I also haven't seen a proof that TI-LFA avoids this type of looping.
[Bruno] A priori, I see 2 aspects
- At least in theory, TI-LFA should be able to get 100% coverage for any co=
nsidered planned failure (link, node, SRLG, any arbitrary set of "single li=
nk" failures). Hence I don't think there is a need to "improve coverage", n=
ot to mention "trade-off looping traffic"
- Any FRR solution assumes a specific failure that it wants to protect from=
. In reality, the failure may be more extensive than planned. A question is=
 what happens in this case. e.g. traffic is dropped, traffic may be FRR mul=
tiple time (by multiple PLR) to provide "de facto protection" in the good c=
ases at the risk of creating loops in the bad cases, traffic may be FRR mul=
tiple time with no risk of loops (a priori though some in-band knowledge of=
 the previous failure). Eventually, one may further distinguish the path fr=
om the PLR to the "Merge point" (first Q node) and the path from the "Merge=
 point" to the destination.

Perhaps Anil has some insight into this topic since he proposed the text in=
 question.  For the moment, I have removed that sentence until we get clari=
fication.
[Bruno] ok, thanks.

                <t hangText=3D"TI-LFA: ">Topology Independent Loop-free
                Alternate Fast Re-route (TI-LFA) <xref
                target=3D"I-D.francois-spring-segment-routing-ti-lfa"/> aim=
s to
                provide link and node protection of node and adjacency
                segments within the Segment Routing (SR) framework.  It
                guarantees complete coverage.  The TI-LFA computation for
                link-protection is fairly straightforward, while the
                computation for node-protection is more complex.  For
                link-protection with symmetric link costs, TI-LFA can provi=
de
                complete coverage using an MPLS label stack with two labels.

[Bruno] I would propose
OLD: using an MPLS label stack with two labels
NEW: by pushing up to two additional labels

Motivation:
- it's not _always_ 2 labels (could be 0 or 1)
- these are _additional_ labels, in addition to the size of the received st=
acks (or more importantly, "generated" stack for PE. pushing 2 labels looks=
 relatively easy for a PLR but if the PLR is a L3 VPN PE using entropy labe=
l, it may have to push up tp of 6 labels (TI-LFA (2), remote PE, EL (2), VP=
N)

                For node protection on arbitrary topologies, the label stack
                size can grow significantly based on repair path.  Note that
                TI-LFA requires shortest path forwarding based on SR
                Node-SIDs, as opposed to LDP labels, in order to construct
                label stacks for backups paths without relying on a large
                number of targeted LDP sessions to learn remote FEC-label
                bindings.  It also requires the use of Adj-SIDs to achieve
                100% coverage.

[Bruno] Looks good.
Thanks Chris.

Bruno

From: bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> [mailto:b=
runo.decraene@orange.com]
Sent: Wednesday, April 01, 2015 3:12 AM
To: Chris Bowers; Anil Kumar S N (VRP Network BL); Alia Atlas; Robert Keble=
r; Gabor.Sandor.Enyedi@ericsson.com<mailto:Gabor.Sandor.Enyedi@ericsson.com=
>; Andras.Csaszar@ericsson.com<mailto:Andras.Csaszar@ericsson.com>; jeff.ta=
ntsura@ericsson.com<mailto:jeff.tantsura@ericsson.com>; russw@riw.us<mailto=
:russw@riw.us>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Cc: pierre.francois@imdea.org<mailto:pierre.francois@imdea.org>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Chris,

Thanks for the addition.
Please see inline some comments. [Bruno]

Thanks,
Regards,
Bruno

From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Chris Bowers
Sent: Wednesday, April 01, 2015 3:10 AM
To: Anil Kumar S N (VRP Network BL); Alia Atlas; Robert Kebler; Gabor.Sando=
r.Enyedi@ericsson.com<mailto:Gabor.Sandor.Enyedi@ericsson.com>; Andras.Csas=
zar@ericsson.com<mailto:Andras.Csaszar@ericsson.com>; jeff.tantsura@ericsso=
n.com<mailto:jeff.tantsura@ericsson.com>; russw@riw.us<mailto:russw@riw.us>=
; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Anil,

Thanks for your input and proposed text.  I added the text below (which is =
a slightly modified version of your proposed text) to the most recent versi=
on which is being maintained at:
https://github.com/cbowers/draft-ietf-rtgwg-mrt-frr-architecture

Tell me if you are OK with the final sentence that I added as well, or you =
can propose some other wording.

Thanks,
Chris

   TI-LFA:    Topology Independent Loop-free Alternate Fast Re-route
      (TI-LFA) [I-D.francois-spring-segment-routing-ti-lfa] aims to
      provide link and node protection of node and adjacency segments
      within the Segment Routing (SR) framework.  It has improved
      coverage over LFA and Remote LFA for link and node protection and
      also guarantees complete coverage.
[Bruno] The last sentence could probably be shortened by only keeping the l=
ast part. "It guarantees complete coverage"


The trade-off of looping
      traffic to improve coverage is still made.
[Bruno] I'm not sure to see what you mean. Contrary to LFA & RLFA, I don't =
think TI-LFA makes such tradeoff.

  The computation
      required is quite high with added complexity.
[Bruno] As in the RLFA description you have made the distinction between li=
nk and node protection, it would be fair to do the same for TI-LFA. (Link p=
rotection computation is much easier)

  TI-LFA is supported
      only for the MPLS data plane due to the requirement for the PLR to
      impose an MPLS label stack on link failure.  On certain topologies
      the label stack size can grow significantly based on repair path.
[Bruno] I agree for node failure. For link failure, this is more debatable =
as compared to RLFA it may require at most 1 additional label. (assuming sy=
mmetric link costs)

      Note that TI-LFA requires shortest path forwarding based on SR
      Node-SIDs, as opposed to LDP labels, in order to construct label
      stacks for backups paths without relying on a large number of
      targeted LDP sessions to learn remote FEC-label bindings.
[Bruno] It also requires Adj-SID (in order to provide 100% coverage).


From: Anil Kumar S N (VRP Network BL) [mailto:anil.sn@huawei.com]
Sent: Saturday, March 28, 2015 8:10 AM
To: Alia Atlas; Robert Kebler; Chris Bowers; Gabor.Sandor.Enyedi@ericsson.c=
om<mailto:Gabor.Sandor.Enyedi@ericsson.com>; Andras.Csaszar@ericsson.com<ma=
ilto:Andras.Csaszar@ericsson.com>; jeff.tantsura@ericsson.com<mailto:jeff.t=
antsura@ericsson.com>; russw@riw.us<mailto:russw@riw.us>; rtgwg@ietf.org<ma=
ilto:rtgwg@ietf.org>
Subject: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Authors,

      In  "comparison of IP/LDP FRR Methods" section of the document , I fe=
el we should add comparison with TI-LFA (draft-francois-spring-segment-rout=
ing-ti-lfa-01) where TI-LFA approach achieves guaranteed coverage  against =
link or node failure, in any IGP network, relying on the  flexibility of SR=
. This will give readers better picture and enables them with more informat=
ion so that they can choose MRT if they feel it suites their requirement be=
tter; compared to IT-LFA...
Changes :

1.  Introduction :

   Other existing or proposed solutions are partial solutions or have
   significant issues, as described below.

                 Summary Comparison of IP/LDP FRR Methods

   +---------+-------------+-------------+-----------------------------+
   |  Method |   Coverage  |  Alternate  |    Computation (in SPFs)    |
   |         |             |   Looping?  |                             |
   +---------+-------------+-------------+-----------------------------+
   | MRT-FRR |     100%    |     None    |         less than 3         |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   |   LFA   |   Partial   |   Possible  |         per neighbor        |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   |  Remote |   Partial   |   Possible  |    per neighbor (link) or   |
   |   LFA   |  Link/Node  |             |  neighbor's neighbor (node) |
   |         |             |             |                             |
   | Not-Via |     100%    |     None    |      per link and node      |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   | TI-LFA  |     100%    |   Possible  |    per neighbor (link) or   |
   |         |  Link/Node  |             |  neighbor's neighbor (node) |
   |         |             |             |                             |
   +---------+-------------+-------------+-----------------------------+

                                  Table 1


   TI-LFA: Topology Independent Loop-free Alternate Fast
   Re-route (TI-LFA), aimed at providing link and node protection of
   node and adjacency segments within the Segment Routing (SR)
   framework [draft-francois-spring-segment-routing-ti-lfa-01].
   Has improved coverage over LFAs and Remote LFA for link and node
   protection and also guarantees complete coverage. The trade-off
   of looping traffic to improve coverage is still made.
  The computation required is quite high with added complexity.
   TI-LFA is supported only MPLS data plane with a requirement to
   carry additional MPLS label stack on the link failure; on certain
   topologies stack size can grow significantly based repair path.

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel



___________________________________________________________________________=
______________________________________________



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.

___________________________________________________________________________=
______________________________________________

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.


--_000_53C29892C857584299CBF5D05346208A0EB907E6PEXCVZYM11corpo_
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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-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:"Pr\00E9format\00E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:Consolas;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New","serif";}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI","sans-serif";}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle26
	{mso-style-type:personal;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle29
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle30
	{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:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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 lang=3D"FR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Chris,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Please see inline. [Br=
uno]<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Chris Bo=
wers [mailto:cbowers@juniper.net]
<br>
<b>Sent:</b> Wednesday, April 01, 2015 6:43 PM<br>
<b>To:</b> DECRAENE Bruno IMT/OLN; Anil Kumar S N (VRP Network BL); Alia At=
las; Robert Kebler; Gabor.Sandor.Enyedi@ericsson.com; Andras.Csaszar@ericss=
on.com; jeff.tantsura@ericsson.com; russw@riw.us; rtgwg@ietf.org<br>
<b>Cc:</b> pierre.francois@imdea.org<br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Bruno,<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Here is=
 proposed text to address your comments.&nbsp; Tell me if this works.<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">With re=
spect to the sentence: &#8220;The trade-off of looping traffic to improve c=
overage is still made.&#8221;&nbsp; I had assumed that Anil was referring t=
o the scenario where an SRLG produces correlated link failures
 such that two nodes have different opinions about what the &quot;new&quot;=
 topology is.&nbsp;</span><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">[Bruno]=
 On my side, I had assumed that it was related to the &#8220;downstream&#82=
21; condition of (R)LFA.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">I haven=
&#8217;t seen a specific topology that will produce looping for TI-LFA, but=
 I also haven&#8217;t seen a proof that TI-LFA avoids this type of looping.=
&nbsp;</span><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">[Bruno]=
 A priori, I see 2 aspects<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">- At le=
ast in theory, TI-LFA should be able to get 100% coverage for any considere=
d planned failure (link, node, SRLG, any arbitrary set of &#8220;single lin=
k&#8221; failures). Hence I don&#8217;t think there is a
 need to &#8220;improve coverage&#8221;, not to mention &#8220;trade-off lo=
oping traffic&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">- Any F=
RR solution assumes a specific failure that it wants to protect from. In re=
ality, the failure may be more extensive than planned. A question is what h=
appens in this case. e.g. traffic is dropped,
 traffic may be FRR multiple time (by multiple PLR) to provide &#8220;de fa=
cto protection&#8221; in the good cases at the risk of creating loops in th=
e bad cases, traffic may be FRR multiple time with no risk of loops (a prio=
ri though some in-band knowledge of the previous
 failure). Eventually, one may further distinguish the path from the PLR to=
 the &#8220;Merge point&#8221; (first Q node) and the path from the &#8220;=
Merge point&#8221; to the destination.</span><span lang=3D"EN-US" style=3D"=
color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Perhaps=
 Anil has some insight into this topic since he proposed the text in questi=
on.&nbsp; For the moment, I have removed that sentence until we get clarifi=
cation.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">[Bruno]=
 ok, thanks.</span><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; &lt;t hangText=3D&quot;TI-LFA: &quot;&gt;Topology Independent Loop=
-free<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; Alternate Fast Re-route (TI-LFA) &lt;xref<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; target=3D&quot;I-D.francois-spring-segment-routing-ti-lfa&quot;/&g=
t; aims to<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; provide link and node protection of node and adjacency<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; segments within the Segment Routing (SR) framework.&nbsp; It<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; guarantees complete coverage.&nbsp; The TI-LFA computation for<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; link-protection is fairly straightforward, while the<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; computation for node-protection is more complex.&nbsp; For<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; link-protection with symmetric link costs, TI-LFA can provide<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; complete coverage using an MPLS label stack with two labels.<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">[Bruno]=
 I would propose<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">OLD: </=
span><span lang=3D"EN-US" style=3D"color:#1F497D">using an MPLS label stack=
 with two labels</span><span lang=3D"EN-US" style=3D"color:#8064A2"><o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">NEW: by=
 pushing up to two additional labels</span><span lang=3D"EN-US" style=3D"co=
lor:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">Motivat=
ion:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">- it&#8=
217;s not _<i>always</i>_ 2 labels (could be 0 or 1)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">- these=
 are _<i>additional</i>_ labels, in addition to the size of the received st=
acks (or more importantly, &#8220;generated&#8221; stack for PE. pushing 2 =
labels looks relatively easy for a PLR but if the
 PLR is a L3 VPN PE using entropy label, it may have to push up tp of 6 lab=
els (TI-LFA (2), remote PE, EL (2), VPN)</span><span lang=3D"EN-US" style=
=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; For node protection on arbitrary topologies, the label stack<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; size can grow significantly based on repair path.&nbsp; Note that<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; TI-LFA requires shortest path forwarding based on SR<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; Node-SIDs, as opposed to LDP labels, in order to construct<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; label stacks for backups paths without relying on a large<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; number of targeted LDP sessions to learn remote FEC-label<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; bindings.&nbsp; It also requires the use of Adj-SIDs to achieve<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; 100% coverage.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">[Bruno]=
 Looks good.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">Thanks =
Chris.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">Bruno</=
span><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> <a href=3D"mailto:bruno.decraene@orange.com">
bruno.decraene@orange.com</a> [<a href=3D"mailto:bruno.decraene@orange.com"=
>mailto:bruno.decraene@orange.com</a>]
<br>
<b>Sent:</b> Wednesday, April 01, 2015 3:12 AM<br>
<b>To:</b> Chris Bowers; Anil Kumar S N (VRP Network BL); Alia Atlas; Rober=
t Kebler;
<a href=3D"mailto:Gabor.Sandor.Enyedi@ericsson.com">Gabor.Sandor.Enyedi@eri=
csson.com</a>;
<a href=3D"mailto:Andras.Csaszar@ericsson.com">Andras.Csaszar@ericsson.com<=
/a>; <a href=3D"mailto:jeff.tantsura@ericsson.com">
jeff.tantsura@ericsson.com</a>; <a href=3D"mailto:russw@riw.us">russw@riw.u=
s</a>; <a href=3D"mailto:rtgwg@ietf.org">
rtgwg@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:pierre.francois@imdea.org">pierre.francois@imd=
ea.org</a><br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Hi Chri=
s,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks =
for the addition.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Please =
see inline some comments. [Bruno]<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks,=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Regards=
,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Bruno<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> rtgwg [<=
a href=3D"mailto:rtgwg-bounces@ietf.org">mailto:rtgwg-bounces@ietf.org</a>]
<b>On Behalf Of </b>Chris Bowers<br>
<b>Sent:</b> Wednesday, April 01, 2015 3:10 AM<br>
<b>To:</b> Anil Kumar S N (VRP Network BL); Alia Atlas; Robert Kebler; <a h=
ref=3D"mailto:Gabor.Sandor.Enyedi@ericsson.com">
Gabor.Sandor.Enyedi@ericsson.com</a>; <a href=3D"mailto:Andras.Csaszar@eric=
sson.com">
Andras.Csaszar@ericsson.com</a>; <a href=3D"mailto:jeff.tantsura@ericsson.c=
om">jeff.tantsura@ericsson.com</a>;
<a href=3D"mailto:russw@riw.us">russw@riw.us</a>; <a href=3D"mailto:rtgwg@i=
etf.org">rtgwg@ietf.org</a><br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Anil,<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks =
for your input and proposed text.&nbsp; I added the text below (which is a =
slightly modified version of your proposed text) to the most recent version=
 which is being maintained at:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><a href=
=3D"https://github.com/cbowers/draft-ietf-rtgwg-mrt-frr-architecture">https=
://github.com/cbowers/draft-ietf-rtgwg-mrt-frr-architecture</a><o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Tell me=
 if you are OK with the final sentence that I added as well, or you can pro=
pose some other wording.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks,=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Chris<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp; TI-LFA:&nbsp=
;&nbsp;&nbsp; Topology Independent Loop-free Alternate Fast Re-route<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; (TI-LFA) [I-D.francois-spring-segment-routing-ti-lfa] aims to<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; provide link and node protection of node and adjacency segments<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; within the Segment Routing (SR) framework.&nbsp; It has improved<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; coverage over LFA and Remote LFA for link and node protection and<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; also guarantees complete coverage.&nbsp;<span style=3D"color:#1F497D"=
><o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 The last sentence could probably be shortened by only keeping the last par=
t. &#8220;It guarantees complete coverage&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">The trade-off of looping<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; traffic to improve coverage is still made.<span style=3D"color:#1F497=
D"><o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 I&#8217;m not sure to see what you mean. Contrary to LFA &amp; RLFA, I don=
&#8217;t think TI-LFA makes such tradeoff.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp; The computation<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; required is quite high with added complexity.<span style=3D"color:#1F=
497D"><o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 As in the RLFA description you have made the distinction between link and =
node protection, it would be fair to do the same for TI-LFA. (Link protecti=
on computation is much easier)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp; TI-LFA is supporte=
d<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; only for the MPLS data plane due to the requirement for the PLR to<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; impose an MPLS label stack on link failure.&nbsp; On certain topologi=
es<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; the label stack size can grow significantly based on repair path.<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 I agree for node failure. For link failure, this is more debatable as comp=
ared to RLFA it may require at most 1 additional label. (assuming symmetric=
 link costs)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Note that TI-LFA requires shortest path forwarding based on SR<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Node-SIDs, as opposed to LDP labels, in order to construct label<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; stacks for backups paths without relying on a large number of<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; targeted LDP sessions to learn remote FEC-label bindings.<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 It also requires Adj-SID (in order to provide 100% coverage).<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p=
>&nbsp;</o:p></span></b></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> Anil Kumar S N (VRP Network BL) [<a href=3D"mailto:anil.sn@huaw=
ei.com">mailto:anil.sn@huawei.com</a>]
<br>
<b>Sent:</b> Saturday, March 28, 2015 8:10 AM<br>
<b>To:</b> Alia Atlas; Robert Kebler; Chris Bowers; <a href=3D"mailto:Gabor=
.Sandor.Enyedi@ericsson.com">
Gabor.Sandor.Enyedi@ericsson.com</a>; <a href=3D"mailto:Andras.Csaszar@eric=
sson.com">
Andras.Csaszar@ericsson.com</a>; <a href=3D"mailto:jeff.tantsura@ericsson.c=
om">jeff.tantsura@ericsson.com</a>;
<a href=3D"mailto:russw@riw.us">russw@riw.us</a>; <a href=3D"mailto:rtgwg@i=
etf.org">rtgwg@ietf.org</a><br>
<b>Subject:</b> draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p></sp=
an></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi Authors,<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
In &nbsp;&#8220;comparison of IP/LDP FRR Methods&#8221; section of the docu=
ment , I feel we should add comparison with TI-LFA (draft-francois-spring-s=
egment-routing-ti-lfa-01) where TI-LFA approach achieves guaranteed coverag=
e &nbsp;against
 link or node failure, in any IGP network, relying on the&nbsp; flexibility=
 of SR. This will give readers better picture and enables them with more in=
formation so that they can choose MRT if they feel it suites their requirem=
ent better; compared to IT-LFA&#8230;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Changes :<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Arial&quot;,&quot;sans-serif&quot;">1.&nbsp; Introduction :=
</span></b><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; Other existing or proposed solutions are partial solutions=
 or have<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; significant issues, as described below.<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; Summary Comparison of IP/LDP FRR Methods<o:p></o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; &#43;---------&#43;-------------&#43;-------------&#43;---=
--------------------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp; Method |&nbsp;&nbsp; Coverage&nbsp; |&nbsp; Altern=
ate&nbsp; |&nbsp;&nbsp;&nbsp; Computation (in SPFs)&nbsp;&nbsp;&nbsp; |<o:p=
></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&n=
bsp; Looping?&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; &#43;---------&#43;-------------&#43;-------------&#43;---=
--------------------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; | MRT-FRR |&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp;=
 |&nbsp;&nbsp;&nbsp;&nbsp; None&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; less than 3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; =
Link/Node&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp; LFA&nbsp;&nbsp; |&nbsp;&nbsp; Partial&nbsp;&=
nbsp; |&nbsp;&nbsp; Possible&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; per neighbor&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; =
Link/Node&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp; Remote |&nbsp;&nbsp; Partial&nbsp;&nbsp; |&nbsp;&n=
bsp; Possible&nbsp; |&nbsp;&nbsp;&nbsp; per neighbor (link) or&nbsp;&nbsp; =
|<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp; LFA&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbs=
p; neighbor's neighbor (node) |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; | Not-Via |&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp;=
 |&nbsp;&nbsp;&nbsp;&nbsp; None&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; per link and node&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; | &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; =
Link/Node&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp; | TI-LFA &nbsp;|&nbsp;&nbsp;&nbsp;&nbsp; 100=
%&nbsp;&nbsp;&nbsp; |&nbsp; &nbsp;Possible&nbsp; |&nbsp;&nbsp;&nbsp; per ne=
ighbor (link) or&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp; |&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;|&nbsp; Link/Node&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; neighbor's neighbor (node) |<o:p></o:p=
></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;">&nbsp;&nbsp; &#43;---------&#43;-------------&#43;-------------&#43;---=
--------------------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; Table 1</span><span lang=3D"EN-US"><o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp; TI-LFA: Topology Independent Loop-free Alter=
nate Fast<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp; Re-route (TI-LFA), aimed at providing link a=
nd node protection of<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp; node and adjacency segments within the Segme=
nt Routing (SR)<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp; framework [draft-francois-spring-segment-rou=
ting-ti-lfa-01].<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp; &nbsp;Has improved coverage over LFAs and Remote L=
FA for link and node
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp;&nbsp;protection and also guarantees complete=
 coverage. The trade-off
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp;&nbsp;of looping traffic to improve coverage =
is still made.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp;The computation required is quite high with a=
dded complexity.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp; TI-LFA is supported only MPLS data plane wit=
h a requirement to
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp;&nbsp;&nbsp;carry additional MPLS label stack on th=
e link failure; on certain<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&quot;serif&quo=
t;;color:#00B050">&nbsp; &nbsp;topologies stack size can grow significantly=
 based repair path.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks &amp; Regards<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Anil S N<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&#8220;Be liberal in what you a=
ccept, and conservative in what you send&#8221; - Jon Postel<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&q=
uot;serif&quot;">__________________________________________________________=
_______________________________________________________________<o:p></o:p><=
/span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&q=
uot;serif&quot;"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&q=
uot;serif&quot;">Ce message et ses pieces jointes peuvent contenir des info=
rmations confidentielles ou privilegiees et ne doivent donc<o:p></o:p></spa=
n></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&q=
uot;serif&quot;">pas etre diffuses, exploites ou copies sans autorisation. =
Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o:p></s=
pan></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&q=
uot;serif&quot;">a l'expediteur et le detruire ainsi que les pieces jointes=
. Les messages electroniques etant susceptibles d'alteration,<o:p></o:p></s=
pan></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&q=
uot;serif&quot;">Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&q=
uot;serif&quot;"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&q=
uot;serif&quot;">This message and its attachments may contain confidential =
or privileged information that may be protected by law;<o:p></o:p></span></=
pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&q=
uot;serif&quot;">they should not be distributed, used or copied without aut=
horisation.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&q=
uot;serif&quot;">If you have received this email in error, please notify th=
e sender and delete this message and its attachments.<o:p></o:p></span></pr=
e>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&q=
uot;serif&quot;">As emails may be altered, Orange is not liable for message=
s that have been modified, changed or falsified.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;,&q=
uot;serif&quot;">Thank you.<o:p></o:p></span></pre>
</div>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

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.
</PRE></body>
</html>

--_000_53C29892C857584299CBF5D05346208A0EB907E6PEXCVZYM11corpo_--


From nobody Thu Apr  2 01:53:50 2015
Return-Path: <anil.sn@huawei.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 45DF01B2C0C for <rtgwg@ietfa.amsl.com>; Thu,  2 Apr 2015 01:53:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.61
X-Spam-Level: 
X-Spam-Status: No, score=-3.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 IhtT6mASa8eM for <rtgwg@ietfa.amsl.com>; Thu,  2 Apr 2015 01:53:39 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 439B91B2C06 for <rtgwg@ietf.org>; Thu,  2 Apr 2015 01:53:38 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BUK45873; Thu, 02 Apr 2015 08:53:34 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 2 Apr 2015 09:53:32 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.135]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Thu, 2 Apr 2015 16:53:19 +0800
From: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, Chris Bowers <cbowers@juniper.net>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Topic: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Index: AdBohapCLAg3Un3wSOKmk0bREwcgiQDiTs4wABBanbAAEjQyoAAe1PUwAAK3dZA=
Date: Thu, 2 Apr 2015 08:53:19 +0000
Message-ID: <327562D94EA7BF428CD805F338C31EF04FB358AD@nkgeml512-mbx.china.huawei.com>
References: <327562D94EA7BF428CD805F338C31EF04FB31080@NKGEML512-MBS.china.huawei.com> <BLUPR05MB292105B133237D6FF24FD1CA9F30@BLUPR05MB292.namprd05.prod.outlook.com> <31522_1427875907_551BA843_31522_7672_1_53C29892C857584299CBF5D05346208A0EB8AE1B@PEXCVZYM11.corporate.adroot.infra.ftgroup> <BLUPR05MB2920299048499D0BDF4C4A8A9F30@BLUPR05MB292.namprd05.prod.outlook.com> <20271_1427960574_551CF2FD_20271_1912_1_53C29892C857584299CBF5D05346208A0EB907E6@PEXCVZYM11.corporate.adroot.infra.ftgroup>
In-Reply-To: <20271_1427960574_551CF2FD_20271_1912_1_53C29892C857584299CBF5D05346208A0EB907E6@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.152.169]
Content-Type: multipart/alternative; boundary="_000_327562D94EA7BF428CD805F338C31EF04FB358ADnkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/ic0fJca66YNp-25pb4bYD9R_scg>
Cc: Veerendranatha Reddy Vallem <veerendranatharv@huawei.com>, Rajeshmv <rajeshmv@huawei.com>, Alia Atlas <akatlas@juniper.net>, Kalyankumar Asangi <kalyana@huawei.com>, "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, 02 Apr 2015 08:53:49 -0000

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

Hi Bruno,Chris,

          Lets not talk about number of labels. With respect to TI LFA, In =
our implementation we have extended number labels much more than two, Ex: w=
hen there is no PQ node also when there no adjacency b/w any  P and Q node =
pair.  We find a shortest path from P & Q form; a label stack that will be =
pushed. In case L3 VPN PE label stack could become much more. This consumes=
 more computation.

Best effort label for a destination is Destination Label , SR FRR label for=
 the same destination is [P Node -> Label stack to reach Q Node -> Destinat=
ion label].

[Bruno] I would propose
OLD: using an MPLS label stack with two labels
NEW: by pushing up to two additional labels

There is a possibility of Looping in TI-LFA; We can expect in case of multi=
ple simultanious failure:
Consider the case where packet is been forwarded towards destination from a=
 source on backup FRR path with TI LFA backup path Statck  as below :
P Node Lable
P-Node to Q-Node Adj lable
Q-Node Lable
Destination Lable

Topology :
P----Q (Cost 10)
Q----Destination(Cost 10)
P----Destination (Cost 100)

Faliure happens on the only link b/w Q-Node towards destination; Reachabili=
ty to destination with SPF calculation or with FRR falls back towards P-Nod=
e (Q's TI LFA calculation).

So there could be a loop.
So I still feel there is a tradeoff.

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel


From: bruno.decraene@orange.com [mailto:bruno.decraene@orange.com]
Sent: 02 April 2015 15:43
To: Chris Bowers
Cc: pierre.francois@imdea.org; Anil Kumar S N (VRP Network BL); Alia Atlas;=
 Robert Kebler; Gabor.Sandor.Enyedi@ericsson.com; Andras.Csaszar@ericsson.c=
om; jeff.tantsura@ericsson.com; russw@riw.us; rtgwg@ietf.org
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Chris,

Please see inline. [Bruno]

From: Chris Bowers [mailto:cbowers@juniper.net]
Sent: Wednesday, April 01, 2015 6:43 PM
To: DECRAENE Bruno IMT/OLN; Anil Kumar S N (VRP Network BL); Alia Atlas; Ro=
bert Kebler; Gabor.Sandor.Enyedi@ericsson.com<mailto:Gabor.Sandor.Enyedi@er=
icsson.com>; Andras.Csaszar@ericsson.com<mailto:Andras.Csaszar@ericsson.com=
>; jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericsson.com>; russw@riw=
.us<mailto:russw@riw.us>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Cc: pierre.francois@imdea.org<mailto:pierre.francois@imdea.org>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Bruno,

Here is proposed text to address your comments.  Tell me if this works.

With respect to the sentence: "The trade-off of looping traffic to improve =
coverage is still made."  I had assumed that Anil was referring to the scen=
ario where an SRLG produces correlated link failures such that two nodes ha=
ve different opinions about what the "new" topology is.
[Bruno] On my side, I had assumed that it was related to the "downstream" c=
ondition of (R)LFA.

I haven't seen a specific topology that will produce looping for TI-LFA, bu=
t I also haven't seen a proof that TI-LFA avoids this type of looping.
[Bruno] A priori, I see 2 aspects
- At least in theory, TI-LFA should be able to get 100% coverage for any co=
nsidered planned failure (link, node, SRLG, any arbitrary set of "single li=
nk" failures). Hence I don't think there is a need to "improve coverage", n=
ot to mention "trade-off looping traffic"
- Any FRR solution assumes a specific failure that it wants to protect from=
. In reality, the failure may be more extensive than planned. A question is=
 what happens in this case. e.g. traffic is dropped, traffic may be FRR mul=
tiple time (by multiple PLR) to provide "de facto protection" in the good c=
ases at the risk of creating loops in the bad cases, traffic may be FRR mul=
tiple time with no risk of loops (a priori though some in-band knowledge of=
 the previous failure). Eventually, one may further distinguish the path fr=
om the PLR to the "Merge point" (first Q node) and the path from the "Merge=
 point" to the destination.

Perhaps Anil has some insight into this topic since he proposed the text in=
 question.  For the moment, I have removed that sentence until we get clari=
fication.
[Bruno] ok, thanks.

                <t hangText=3D"TI-LFA: ">Topology Independent Loop-free
                Alternate Fast Re-route (TI-LFA) <xref
                target=3D"I-D.francois-spring-segment-routing-ti-lfa"/> aim=
s to
                provide link and node protection of node and adjacency
                segments within the Segment Routing (SR) framework.  It
                guarantees complete coverage.  The TI-LFA computation for
                link-protection is fairly straightforward, while the
                computation for node-protection is more complex.  For
                link-protection with symmetric link costs, TI-LFA can provi=
de
                complete coverage using an MPLS label stack with two labels=
.

[Bruno] I would propose
OLD: using an MPLS label stack with two labels
NEW: by pushing up to two additional labels

Motivation:
- it's not _always_ 2 labels (could be 0 or 1)
- these are _additional_ labels, in addition to the size of the received st=
acks (or more importantly, "generated" stack for PE. pushing 2 labels looks=
 relatively easy for a PLR but if the PLR is a L3 VPN PE using entropy labe=
l, it may have to push up tp of 6 labels (TI-LFA (2), remote PE, EL (2), VP=
N)

                For node protection on arbitrary topologies, the label stac=
k
                size can grow significantly based on repair path.  Note tha=
t
                TI-LFA requires shortest path forwarding based on SR
                Node-SIDs, as opposed to LDP labels, in order to construct
                label stacks for backups paths without relying on a large
                number of targeted LDP sessions to learn remote FEC-label
                bindings.  It also requires the use of Adj-SIDs to achieve
                100% coverage.

[Bruno] Looks good.
Thanks Chris.

Bruno

From: bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> [mailto:b=
runo.decraene@orange.com]
Sent: Wednesday, April 01, 2015 3:12 AM
To: Chris Bowers; Anil Kumar S N (VRP Network BL); Alia Atlas; Robert Keble=
r; Gabor.Sandor.Enyedi@ericsson.com<mailto:Gabor.Sandor.Enyedi@ericsson.com=
>; Andras.Csaszar@ericsson.com<mailto:Andras.Csaszar@ericsson.com>; jeff.ta=
ntsura@ericsson.com<mailto:jeff.tantsura@ericsson.com>; russw@riw.us<mailto=
:russw@riw.us>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Cc: pierre.francois@imdea.org<mailto:pierre.francois@imdea.org>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Chris,

Thanks for the addition.
Please see inline some comments. [Bruno]

Thanks,
Regards,
Bruno

From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Chris Bowers
Sent: Wednesday, April 01, 2015 3:10 AM
To: Anil Kumar S N (VRP Network BL); Alia Atlas; Robert Kebler; Gabor.Sando=
r.Enyedi@ericsson.com<mailto:Gabor.Sandor.Enyedi@ericsson.com>; Andras.Csas=
zar@ericsson.com<mailto:Andras.Csaszar@ericsson.com>; jeff.tantsura@ericsso=
n.com<mailto:jeff.tantsura@ericsson.com>; russw@riw.us<mailto:russw@riw.us>=
; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Anil,

Thanks for your input and proposed text.  I added the text below (which is =
a slightly modified version of your proposed text) to the most recent versi=
on which is being maintained at:
https://github.com/cbowers/draft-ietf-rtgwg-mrt-frr-architecture

Tell me if you are OK with the final sentence that I added as well, or you =
can propose some other wording.

Thanks,
Chris

   TI-LFA:    Topology Independent Loop-free Alternate Fast Re-route
      (TI-LFA) [I-D.francois-spring-segment-routing-ti-lfa] aims to
      provide link and node protection of node and adjacency segments
      within the Segment Routing (SR) framework.  It has improved
      coverage over LFA and Remote LFA for link and node protection and
      also guarantees complete coverage.
[Bruno] The last sentence could probably be shortened by only keeping the l=
ast part. "It guarantees complete coverage"


The trade-off of looping
      traffic to improve coverage is still made.
[Bruno] I'm not sure to see what you mean. Contrary to LFA & RLFA, I don't =
think TI-LFA makes such tradeoff.

  The computation
      required is quite high with added complexity.
[Bruno] As in the RLFA description you have made the distinction between li=
nk and node protection, it would be fair to do the same for TI-LFA. (Link p=
rotection computation is much easier)

  TI-LFA is supported
      only for the MPLS data plane due to the requirement for the PLR to
      impose an MPLS label stack on link failure.  On certain topologies
      the label stack size can grow significantly based on repair path.
[Bruno] I agree for node failure. For link failure, this is more debatable =
as compared to RLFA it may require at most 1 additional label. (assuming sy=
mmetric link costs)

      Note that TI-LFA requires shortest path forwarding based on SR
      Node-SIDs, as opposed to LDP labels, in order to construct label
      stacks for backups paths without relying on a large number of
      targeted LDP sessions to learn remote FEC-label bindings.
[Bruno] It also requires Adj-SID (in order to provide 100% coverage).


From: Anil Kumar S N (VRP Network BL) [mailto:anil.sn@huawei.com]
Sent: Saturday, March 28, 2015 8:10 AM
To: Alia Atlas; Robert Kebler; Chris Bowers; Gabor.Sandor.Enyedi@ericsson.c=
om<mailto:Gabor.Sandor.Enyedi@ericsson.com>; Andras.Csaszar@ericsson.com<ma=
ilto:Andras.Csaszar@ericsson.com>; jeff.tantsura@ericsson.com<mailto:jeff.t=
antsura@ericsson.com>; russw@riw.us<mailto:russw@riw.us>; rtgwg@ietf.org<ma=
ilto:rtgwg@ietf.org>
Subject: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Authors,

      In  "comparison of IP/LDP FRR Methods" section of the document , I fe=
el we should add comparison with TI-LFA (draft-francois-spring-segment-rout=
ing-ti-lfa-01) where TI-LFA approach achieves guaranteed coverage  against =
link or node failure, in any IGP network, relying on the  flexibility of SR=
. This will give readers better picture and enables them with more informat=
ion so that they can choose MRT if they feel it suites their requirement be=
tter; compared to IT-LFA...
Changes :

1.  Introduction :

   Other existing or proposed solutions are partial solutions or have
   significant issues, as described below.

                 Summary Comparison of IP/LDP FRR Methods

   +---------+-------------+-------------+-----------------------------+
   |  Method |   Coverage  |  Alternate  |    Computation (in SPFs)    |
   |         |             |   Looping?  |                             |
   +---------+-------------+-------------+-----------------------------+
   | MRT-FRR |     100%    |     None    |         less than 3         |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   |   LFA   |   Partial   |   Possible  |         per neighbor        |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   |  Remote |   Partial   |   Possible  |    per neighbor (link) or   |
   |   LFA   |  Link/Node  |             |  neighbor's neighbor (node) |
   |         |             |             |                             |
   | Not-Via |     100%    |     None    |      per link and node      |
   |         |  Link/Node  |             |                             |
   |         |             |             |                             |
   | TI-LFA  |     100%    |   Possible  |    per neighbor (link) or   |
   |         |  Link/Node  |             |  neighbor's neighbor (node) |
   |         |             |             |                             |
   +---------+-------------+-------------+-----------------------------+

                                  Table 1


   TI-LFA: Topology Independent Loop-free Alternate Fast
   Re-route (TI-LFA), aimed at providing link and node protection of
   node and adjacency segments within the Segment Routing (SR)
   framework [draft-francois-spring-segment-routing-ti-lfa-01].
   Has improved coverage over LFAs and Remote LFA for link and node
   protection and also guarantees complete coverage. The trade-off
   of looping traffic to improve coverage is still made.
  The computation required is quite high with added complexity.
   TI-LFA is supported only MPLS data plane with a requirement to
   carry additional MPLS label stack on the link failure; on certain
   topologies stack size can grow significantly based repair path.

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel



___________________________________________________________________________=
______________________________________________



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.

___________________________________________________________________________=
______________________________________________



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.

--_000_327562D94EA7BF428CD805F338C31EF04FB358ADnkgeml512mbxchi_
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 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Bookman Old Style";
	panose-1:2 5 6 4 5 5 5 2 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-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:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI","sans-serif";}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
	{mso-style-name:"Pr\00E9format\00E9 HTML";
	mso-style-link:"Pr\00E9format\00E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:Consolas;}
p.Textedebulles, li.Textedebulles, div.Textedebulles
	{mso-style-name:"Texte de bulles";
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle26
	{mso-style-type:personal;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle29
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle30
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle31
	{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:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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 lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Hi Bruno,Chris,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Lets not talk about number of labels. With respect to TI LFA, In our im=
plementation we have extended number labels much more than two, Ex: when th=
ere is no PQ node also when
 there no adjacency b/w any &nbsp;P and Q node pair. &nbsp;We find a shorte=
st path from P &amp; Q form; a label stack that will be pushed. In case L3 =
VPN PE label stack could become much more. This consumes more computation.<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Best effort label for a destination is Destination =
Label , SR FRR label for the same destination is [P Node -&gt; Label stack =
to reach Q Node -&gt; Destination label].<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">[Bruno] I would propos=
e<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">OLD: </span><span styl=
e=3D"color:#1F497D">using an MPLS label stack with two labels</span><span s=
tyle=3D"color:#8064A2"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">NEW: by pushing up to =
two additional labels</span><span style=3D"color:#1F497D"><o:p></o:p></span=
></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">There is a possibility of Looping in TI-LFA; We can=
 expect in case of multiple simultanious failure:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Consider the case where packet is been forwarded to=
wards destination from a source on backup FRR path with TI LFA backup path =
Statck &nbsp;as below :<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">P Node Lable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">P-Node to Q-Node Adj lable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Q-Node Lable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Destination Lable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Topology :<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">P----Q (Cost 10)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Q----Destination(Cost 10)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">P----Destination (Cost 100)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Faliure happens on the only link b/w Q-Node towards=
 destination; Reachability to destination with SPF calculation or with FRR =
falls back towards P-Node (Q&#8217;s TI LFA calculation).
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">So there could be a loop.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">So I still feel there is a tradeoff.<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks &amp; Regards<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Anil S N<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&#8220;Be liberal in w=
hat you accept, and conservative in what you send&#8221; - Jon Postel<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> bruno.de=
craene@orange.com [mailto:bruno.decraene@orange.com]
<br>
<b>Sent:</b> 02 April 2015 15:43<br>
<b>To:</b> Chris Bowers<br>
<b>Cc:</b> pierre.francois@imdea.org; Anil Kumar S N (VRP Network BL); Alia=
 Atlas; Robert Kebler; Gabor.Sandor.Enyedi@ericsson.com; Andras.Csaszar@eri=
csson.com; jeff.tantsura@ericsson.com; russw@riw.us; rtgwg@ietf.org<br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"color:#1F497D">Chris,<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"color:#1F497D">Please see=
 inline. [Bruno]<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"FR" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lan=
g=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;san=
s-serif&quot;"> Chris Bowers [<a href=3D"mailto:cbowers@juniper.net">mailto=
:cbowers@juniper.net</a>]
<br>
<b>Sent:</b> Wednesday, April 01, 2015 6:43 PM<br>
<b>To:</b> DECRAENE Bruno IMT/OLN; Anil Kumar S N (VRP Network BL); Alia At=
las; Robert Kebler;
<a href=3D"mailto:Gabor.Sandor.Enyedi@ericsson.com">Gabor.Sandor.Enyedi@eri=
csson.com</a>;
<a href=3D"mailto:Andras.Csaszar@ericsson.com">Andras.Csaszar@ericsson.com<=
/a>; <a href=3D"mailto:jeff.tantsura@ericsson.com">
jeff.tantsura@ericsson.com</a>; <a href=3D"mailto:russw@riw.us">russw@riw.u=
s</a>; <a href=3D"mailto:rtgwg@ietf.org">
rtgwg@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:pierre.francois@imdea.org">pierre.francois@imd=
ea.org</a><br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"FR"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Bruno,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Here is proposed text =
to address your comments.&nbsp; Tell me if this works.<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">With respect to the se=
ntence: &#8220;The trade-off of looping traffic to improve coverage is stil=
l made.&#8221;&nbsp; I had assumed that Anil was referring to the scenario =
where an SRLG produces correlated link failures such
 that two nodes have different opinions about what the &quot;new&quot; topo=
logy is.&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">[Bruno] On my side, I =
had assumed that it was related to the &#8220;downstream&#8221; condition o=
f (R)LFA.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I haven&#8217;t seen a=
 specific topology that will produce looping for TI-LFA, but I also haven&#=
8217;t seen a proof that TI-LFA avoids this type of looping.&nbsp;<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">[Bruno] A priori, I se=
e 2 aspects<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">- At least in theory, =
TI-LFA should be able to get 100% coverage for any considered planned failu=
re (link, node, SRLG, any arbitrary set of &#8220;single link&#8221; failur=
es). Hence I don&#8217;t think there is a need to &#8220;improve
 coverage&#8221;, not to mention &#8220;trade-off looping traffic&#8221;<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">- Any FRR solution ass=
umes a specific failure that it wants to protect from. In reality, the fail=
ure may be more extensive than planned. A question is what happens in this =
case. e.g. traffic is dropped, traffic
 may be FRR multiple time (by multiple PLR) to provide &#8220;de facto prot=
ection&#8221; in the good cases at the risk of creating loops in the bad ca=
ses, traffic may be FRR multiple time with no risk of loops (a priori thoug=
h some in-band knowledge of the previous failure).
 Eventually, one may further distinguish the path from the PLR to the &#822=
0;Merge point&#8221; (first Q node) and the path from the &#8220;Merge poin=
t&#8221; to the destination.</span><span style=3D"color:#1F497D"><o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Perhaps Anil has some =
insight into this topic since he proposed the text in question.&nbsp; For t=
he moment, I have removed that sentence until we get clarification.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">[Bruno] ok, thanks.</s=
pan><span style=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;t =
hangText=3D&quot;TI-LFA: &quot;&gt;Topology Independent Loop-free<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Altern=
ate Fast Re-route (TI-LFA) &lt;xref<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; target=
=3D&quot;I-D.francois-spring-segment-routing-ti-lfa&quot;/&gt; aims to<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; provid=
e link and node protection of node and adjacency<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; segmen=
ts within the Segment Routing (SR) framework.&nbsp; It<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; guaran=
tees complete coverage.&nbsp; The TI-LFA computation for<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; link-p=
rotection is fairly straightforward, while the<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; comput=
ation for node-protection is more complex.&nbsp; For<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; link-p=
rotection with symmetric link costs, TI-LFA can provide<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; comple=
te coverage using an MPLS label stack with two labels.<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">[Bruno] I would propos=
e<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">OLD: </span><span styl=
e=3D"color:#1F497D">using an MPLS label stack with two labels</span><span s=
tyle=3D"color:#8064A2"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">NEW: by pushing up to =
two additional labels</span><span style=3D"color:#1F497D"><o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">Motivation:<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">- it&#8217;s not _<i>a=
lways</i>_ 2 labels (could be 0 or 1)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">- these are _<i>additi=
onal</i>_ labels, in addition to the size of the received stacks (or more i=
mportantly, &#8220;generated&#8221; stack for PE. pushing 2 labels looks re=
latively easy for a PLR but if the PLR is a L3 VPN
 PE using entropy label, it may have to push up tp of 6 labels (TI-LFA (2),=
 remote PE, EL (2), VPN)</span><span style=3D"color:#1F497D"><o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; For no=
de protection on arbitrary topologies, the label stack<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; size c=
an grow significantly based on repair path.&nbsp; Note that<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TI-LFA=
 requires shortest path forwarding based on SR<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Node-S=
IDs, as opposed to LDP labels, in order to construct<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; label =
stacks for backups paths without relying on a large<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; number=
 of targeted LDP sessions to learn remote FEC-label<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bindin=
gs.&nbsp; It also requires the use of Adj-SIDs to achieve<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 100% c=
overage. <o:p>
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">[Bruno] Looks good.<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">Thanks Chris.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">Bruno</span><span styl=
e=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b>From:</b> <a href=3D"mailto:bruno.decraene@orange=
.com">bruno.decraene@orange.com</a> [<a href=3D"mailto:bruno.decraene@orang=
e.com">mailto:bruno.decraene@orange.com</a>]
<br>
<b>Sent:</b> Wednesday, April 01, 2015 3:12 AM<br>
<b>To:</b> Chris Bowers; Anil Kumar S N (VRP Network BL); Alia Atlas; Rober=
t Kebler;
<a href=3D"mailto:Gabor.Sandor.Enyedi@ericsson.com">Gabor.Sandor.Enyedi@eri=
csson.com</a>;
<a href=3D"mailto:Andras.Csaszar@ericsson.com">Andras.Csaszar@ericsson.com<=
/a>; <a href=3D"mailto:jeff.tantsura@ericsson.com">
jeff.tantsura@ericsson.com</a>; <a href=3D"mailto:russw@riw.us">russw@riw.u=
s</a>; <a href=3D"mailto:rtgwg@ietf.org">
rtgwg@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:pierre.francois@imdea.org">pierre.francois@imd=
ea.org</a><br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Chris,<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks for the additio=
n.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Please see inline some=
 comments. [Bruno]<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Bruno<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"FR" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lan=
g=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;san=
s-serif&quot;"> rtgwg [<a href=3D"mailto:rtgwg-bounces@ietf.org">mailto:rtg=
wg-bounces@ietf.org</a>]
<b>On Behalf Of </b>Chris Bowers<br>
<b>Sent:</b> Wednesday, April 01, 2015 3:10 AM<br>
<b>To:</b> Anil Kumar S N (VRP Network BL); Alia Atlas; Robert Kebler; <a h=
ref=3D"mailto:Gabor.Sandor.Enyedi@ericsson.com">
Gabor.Sandor.Enyedi@ericsson.com</a>; <a href=3D"mailto:Andras.Csaszar@eric=
sson.com">
Andras.Csaszar@ericsson.com</a>; <a href=3D"mailto:jeff.tantsura@ericsson.c=
om">jeff.tantsura@ericsson.com</a>;
<a href=3D"mailto:russw@riw.us">russw@riw.us</a>; <a href=3D"mailto:rtgwg@i=
etf.org">rtgwg@ietf.org</a><br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"FR"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Anil,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks for your input =
and proposed text.&nbsp; I added the text below (which is a slightly modifi=
ed version of your proposed text) to the most recent version which is being=
 maintained at:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><a href=3D"https://git=
hub.com/cbowers/draft-ietf-rtgwg-mrt-frr-architecture">https://github.com/c=
bowers/draft-ietf-rtgwg-mrt-frr-architecture</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Tell me if you are OK =
with the final sentence that I added as well, or you can propose some other=
 wording.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Chris<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; TI-LFA:&nbsp;&nbsp;&nbsp; Topology Independen=
t Loop-free Alternate Fast Re-route<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (TI-LFA) [I-D.francois-spri=
ng-segment-routing-ti-lfa] aims to<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; provide link and node prote=
ction of node and adjacency segments<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; within the Segment Routing =
(SR) framework.&nbsp; It has improved<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; coverage over LFA and Remot=
e LFA for link and node protection and<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; also guarantees complete co=
verage.&nbsp;<span style=3D"color:#1F497D"><o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] The last sente=
nce could probably be shortened by only keeping the last part. &#8220;It gu=
arantees complete coverage&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">The trade-off of looping<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; traffic to improve coverage=
 is still made.<span style=3D"color:#1F497D"><o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] I&#8217;m not =
sure to see what you mean. Contrary to LFA &amp; RLFA, I don&#8217;t think =
TI-LFA makes such tradeoff.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp; The computation<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; required is quite high with=
 added complexity.<span style=3D"color:#1F497D"><o:p></o:p></span></span></=
p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] As in the RLFA=
 description you have made the distinction between link and node protection=
, it would be fair to do the same for TI-LFA. (Link protection computation =
is much easier)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp; TI-LFA is supported<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; only for the MPLS data plan=
e due to the requirement for the PLR to<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; impose an MPLS label stack =
on link failure.&nbsp; On certain topologies<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the label stack size can gr=
ow significantly based on repair path.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] I agree for no=
de failure. For link failure, this is more debatable as compared to RLFA it=
 may require at most 1 additional label. (assuming symmetric link costs)<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Note that TI-LFA requires s=
hortest path forwarding based on SR<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Node-SIDs, as opposed to LD=
P labels, in order to construct label<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; stacks for backups paths wi=
thout relying on a large number of<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; targeted LDP sessions to le=
arn remote FEC-label bindings.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] It also requir=
es Adj-SID (in order to provide 100% coverage).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></=
span></b></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b>From:</b> Anil Kumar S N (VRP Network BL) [<a hre=
f=3D"mailto:anil.sn@huawei.com">mailto:anil.sn@huawei.com</a>]
<br>
<b>Sent:</b> Saturday, March 28, 2015 8:10 AM<br>
<b>To:</b> Alia Atlas; Robert Kebler; Chris Bowers; <a href=3D"mailto:Gabor=
.Sandor.Enyedi@ericsson.com">
Gabor.Sandor.Enyedi@ericsson.com</a>; <a href=3D"mailto:Andras.Csaszar@eric=
sson.com">
Andras.Csaszar@ericsson.com</a>; <a href=3D"mailto:jeff.tantsura@ericsson.c=
om">jeff.tantsura@ericsson.com</a>;
<a href=3D"mailto:russw@riw.us">russw@riw.us</a>; <a href=3D"mailto:rtgwg@i=
etf.org">rtgwg@ietf.org</a><br>
<b>Subject:</b> draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi Authors,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In &nbsp;&#8220;compa=
rison of IP/LDP FRR Methods&#8221; section of the document , I feel we shou=
ld add comparison with TI-LFA (draft-francois-spring-segment-routing-ti-lfa=
-01) where TI-LFA approach achieves guaranteed coverage &nbsp;against link =
or node
 failure, in any IGP network, relying on the&nbsp; flexibility of SR. This =
will give readers better picture and enables them with more information so =
that they can choose MRT if they feel it suites their requirement better; c=
ompared to IT-LFA&#8230;<o:p></o:p></p>
<p class=3D"MsoNormal">Changes :<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">1.&nbsp; Introduction :</span></b><o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; Other existing o=
r proposed solutions are partial solutions or have<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; significant issu=
es, as described below.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Summary=
 Comparison of IP/LDP FRR Methods<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; &#43;---------&#=
43;-------------&#43;-------------&#43;-----------------------------&#43;<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp; Method |=
&nbsp;&nbsp; Coverage&nbsp; |&nbsp; Alternate&nbsp; |&nbsp;&nbsp;&nbsp; Com=
putation (in SPFs)&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; Looping?&nbsp; |&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; &#43;---------&#=
43;-------------&#43;-------------&#43;-----------------------------&#43;<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; | MRT-FRR |&nbsp=
;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; None&n=
bsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; less tha=
n 3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp; LF=
A&nbsp;&nbsp; |&nbsp;&nbsp; Partial&nbsp;&nbsp; |&nbsp;&nbsp; Possible&nbsp=
; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; per neighbor&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp; Remote |=
&nbsp;&nbsp; Partial&nbsp;&nbsp; |&nbsp;&nbsp; Possible&nbsp; |&nbsp;&nbsp;=
&nbsp; per neighbor (link) or&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp; LF=
A&nbsp;&nbsp; |&nbsp; Link/Node&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; neighbor's neighbor (node) |<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; | Not-Via |&nbsp=
;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; None&n=
bsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; per link and node&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; | &nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; Link/Node&nbsp; |&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp; | =
TI-LFA &nbsp;|&nbsp;&nbsp;&nbsp;&nbsp; 100%&nbsp;&nbsp;&nbsp; |&nbsp; &nbsp=
;Possible&nbsp; |&nbsp;&nbsp;&nbsp; per neighbor (link) or&nbsp;&nbsp; |<o:=
p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp; |&=
nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; Link/Node&nbsp; |&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nb=
sp; neighbor's neighbor (node) |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; &#43;---------&#=
43;-------------&#43;-------------&#43;-----------------------------&#43;<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Table 1</=
span><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp; TI=
-LFA: Topology Independent Loop-free Alternate Fast<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp; Re=
-route (TI-LFA), aimed at providing link and node protection of<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp; no=
de and adjacency segments within the Segment Routing (SR)<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp; fr=
amework [draft-francois-spring-segment-routing-ti-lfa-01].<o:p></o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp; &nbsp;Ha=
s improved coverage over LFAs and Remote LFA for link and node
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nb=
sp;protection and also guarantees complete coverage. The trade-off
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nb=
sp;of looping traffic to improve coverage is still made.<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;The=
 computation required is quite high with added complexity.<o:p></o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp; TI=
-LFA is supported only MPLS data plane with a requirement to
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nb=
sp;carry additional MPLS label stack on the link failure; on certain<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:#00B050">&nbsp; &nbsp;to=
pologies stack size can grow significantly based repair path.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks &amp; Regards<o:p></o:p></p>
<p class=3D"MsoNormal">Anil S N<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&#8220;Be liberal in what you accept, and conservati=
ve in what you send&#8221; - Jon Postel<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">________________________________________________________________=
_________________________________________________________<o:p></o:p></span>=
</pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><o:p>&nbsp;</o:p></span></pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">Ce message et ses pieces jointes peuvent contenir des informatio=
ns confidentielles ou privilegiees et ne doivent donc<o:p></o:p></span></pr=
e>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">pas etre diffuses, exploites ou copies sans autorisation. Si vou=
s avez recu ce message par erreur, veuillez le signaler<o:p></o:p></span></=
pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">a l'expediteur et le detruire ainsi que les pieces jointes. Les =
messages electroniques etant susceptibles d'alteration,<o:p></o:p></span></=
pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">Orange decline toute responsabilite si ce message a ete altere, =
deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><o:p>&nbsp;</o:p></span></pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">This message and its attachments may contain confidential or pri=
vileged information that may be protected by law;<o:p></o:p></span></pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">they should not be distributed, used or copied without authorisa=
tion.<o:p></o:p></span></pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">If you have received this email in error, please notify the send=
er and delete this message and its attachments.<o:p></o:p></span></pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">As emails may be altered, Orange is not liable for messages that=
 have been modified, changed or falsified.<o:p></o:p></span></pre>
<pre><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">Thank you.<o:p></o:p></span></pre>
</div>
<pre><span lang=3D"FR">____________________________________________________=
_____________________________________________________________________<o:p><=
/o:p></span></pre>
<pre><span lang=3D"FR"><o:p>&nbsp;</o:p></span></pre>
<pre><span lang=3D"FR">Ce message et ses pieces jointes peuvent contenir de=
s informations confidentielles ou privilegiees et ne doivent donc<o:p></o:p=
></span></pre>
<pre><span lang=3D"FR">pas etre diffuses, exploites ou copies sans autorisa=
tion. Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o=
:p></span></pre>
<pre><span lang=3D"FR">a l'expediteur et le detruire ainsi que les pieces j=
ointes. Les messages electroniques etant susceptibles d'alteration,<o:p></o=
:p></span></pre>
<pre><span lang=3D"FR">Orange decline toute responsabilite si ce message a =
ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span lang=3D"FR"><o:p>&nbsp;</o:p></span></pre>
<pre><span lang=3D"FR">This message and its attachments may contain confide=
ntial or privileged information that may be protected by law;<o:p></o:p></s=
pan></pre>
<pre><span lang=3D"FR">they should not be distributed, used or copied witho=
ut authorisation.<o:p></o:p></span></pre>
<pre><span lang=3D"FR">If you have received this email in error, please not=
ify the sender and delete this message and its attachments.<o:p></o:p></spa=
n></pre>
<pre><span lang=3D"FR">As emails may be altered, Orange is not liable for m=
essages that have been modified, changed or falsified.<o:p></o:p></span></p=
re>
<pre><span lang=3D"FR">Thank you.<o:p></o:p></span></pre>
</div>
</body>
</html>

--_000_327562D94EA7BF428CD805F338C31EF04FB358ADnkgeml512mbxchi_--


From nobody Thu Apr  2 03:32:35 2015
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 C219D1B2C47 for <rtgwg@ietfa.amsl.com>; Thu,  2 Apr 2015 03:32:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_LOW=-0.7, 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 YWbXulkXSQe5 for <rtgwg@ietfa.amsl.com>; Thu,  2 Apr 2015 03:32:29 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBB091B2C42 for <rtgwg@ietf.org>; Thu,  2 Apr 2015 03:32:28 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 756D922C546 for <rtgwg@ietf.org>; Thu,  2 Apr 2015 12:32:27 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 58C0F35C098 for <rtgwg@ietf.org>; Thu,  2 Apr 2015 12:32:27 +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.0224.002; Thu, 2 Apr 2015 12:32:27 +0200
From: <bruno.decraene@orange.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Topic: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Index: AdBohapCLAg3Un3wSOKmk0bREwcgiQDiTs4wABBanbAAEjQyoAAe1PUwAAK3dZAAAq50sAABUkXA
Date: Thu, 2 Apr 2015 10:32:26 +0000
Message-ID: <20780_1427970747_551D1ABB_20780_3129_1_53C29892C857584299CBF5D05346208A0EB90A87@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <327562D94EA7BF428CD805F338C31EF04FB31080@NKGEML512-MBS.china.huawei.com> <BLUPR05MB292105B133237D6FF24FD1CA9F30@BLUPR05MB292.namprd05.prod.outlook.com> <31522_1427875907_551BA843_31522_7672_1_53C29892C857584299CBF5D05346208A0EB8AE1B@PEXCVZYM11.corporate.adroot.infra.ftgroup> <BLUPR05MB2920299048499D0BDF4C4A8A9F30@BLUPR05MB292.namprd05.prod.outlook.com> <20271_1427960574_551CF2FD_20271_1912_1_53C29892C857584299CBF5D05346208A0EB907E6@PEXCVZYM11.corporate.adroot.infra.ftgroup> <327562D94EA7BF428CD805F338C31EF04FB358AD@nkgeml512-mbx.china.huawei.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.6]
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A0EB90A87PEXCVZYM11corpo_"
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.4.2.45719
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/Jkb7W5CS4tHtH4jsC9FA1Y1zrIM>
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, 02 Apr 2015 10:32:33 -0000

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

Re-sending as my previous email was apparently too big.
( "too big to fail" does not work for email ;-) )

From: DECRAENE Bruno IMT/OLN
Sent: Thursday, April 02, 2015 12:24 PM To: 'Anil Kumar S N (VRP Network BL=
)'


Hi Anil,

Please see inline [Bruno]

From: Anil Kumar S N (VRP Network BL) [mailto:anil.sn@huawei.com]
Sent: Thursday, April 02, 2015 10:53 AM


Hi Bruno,Chris,

          Lets not talk about number of labels. With respect to TI LFA, In =
our implementation we have extended number labels much more than two,
[Bruno] Good job.
- For link protection only, in network with symmetric link cost, up to 2 la=
bels may be required for. Never more than 2.
- For others cases, in particular node and/or SRLG protection, more than 2 =
labels may be required. In theory, there is no limit. In practice, there is=
 a limit. In our networks, the max found was 4 labels. So it's good to be a=
ble to push more than 2 labels to enforce the FRR detour.
Ex: when there is no PQ node also when there no adjacency b/w any  P and Q =
node pair.  We find a shortest path from P & Q form; a label stack that wil=
l be pushed. In case L3 VPN PE label stack could become much more. This con=
sumes more computation.

Best effort label for a destination is Destination Label , SR FRR label for=
 the same destination is [P Node -> Label stack to reach Q Node -> Destinat=
ion label].

[Bruno] I would propose
OLD: using an MPLS label stack with two labels
NEW: by pushing up to two additional labels

There is a possibility of Looping in TI-LFA; We can expect in case of multi=
ple simultanious failure:
[Bruno] You are right. In case of independent/non FRR planned failures, the=
 first PLR can't avoid all failures since those failures were expected to n=
ot planned/expected to occur at the same time. The second PLR will try to p=
rotect the second failure. In good cases, the two protections are complemen=
tary and will achieve "de facto" protection. In bad cases, forwarding loop =
will occur. In theory, the handling of the second independent failure, is a=
 (difficult) choice, between dropping or trying to repair. In theory TI-LFA=
 could do both, but as of today, it tries the second protection
This is not specific to TI-LFA. FRR assumes _local_ protection (hence local=
 knowledge) of a _pre_computed_ (hence pre-planned) failure.
I have been told ARC could handle multiple consecutive FRR (through some lo=
calize notification mechanism) but I don't have the details.
Consider the case where packet is been forwarded towards destination from a=
 source on backup FRR path with TI LFA backup path Statck  as below :
P Node Lable
P-Node to Q-Node Adj lable
Q-Node Lable
Destination Lable

Topology :
P----Q (Cost 10)
Q----Destination(Cost 10)
P----Destination (Cost 100)

Faliure happens on the only link b/w Q-Node towards destination; Reachabili=
ty to destination with SPF calculation or with FRR falls back towards P-Nod=
e (Q's TI LFA calculation).
[Bruno] In this specific case, I don't see a loop. Q, acting as the second =
PLR (in a row), has computed that  node "P" is its P node and node "D" is i=
ts Q node. P is reached via a node-SID (possibly implicit label) which is n=
ot affected by the first failure. Q is reached by a Adj-sid, which is not a=
ffected by the first failure.

So there could be a loop.
[Bruno] I could not find one in this example, but I agree that we could fin=
d examples with loops.
e.g. the following topology
A - B
|  \  |
C - D

Where all links have a metric of 10, except AC which has 100. For the traff=
ic from A to C, if both AC and BD links fails at the same time (and were no=
t identified as SRLG), there will be a loop between A and B. (and funnily (=
is it? ;-) ) as packets are looped, the label stack seems to increase to "i=
nfinity" as additional P nodes (alternatively C and D) are used.
So I still feel there is a tradeoff.
[Bruno] There are many tradeoff ;-). But this one is about handling a secon=
d independent failure. Not about increase coverage of a protected resource =
(link/node/SRLG/any)

Thanks
Regards
/Bruno

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel


___________________________________________________________________________=
______________________________________________

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.


--_000_53C29892C857584299CBF5D05346208A0EB90A87PEXCVZYM11corpo_
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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
	{font-family:"Bookman Old Style";
	panose-1:2 5 6 4 5 5 5 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-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:"Pr\00E9format\00E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:Consolas;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New","serif";}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI","sans-serif";}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle26
	{mso-style-type:personal;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle29
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle30
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle31
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle33
	{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:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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 lang=3D"FR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Re-send=
ing as my previous email was apparently too big.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">( &#822=
0;too big to fail&#8221; does not work for email ;-) )<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> DECRAENE=
 Bruno IMT/OLN
<br>
<b>Sent:</b> Thursday, April 02, 2015 12:24 PM <b>To:</b> 'Anil Kumar S N (=
VRP Network BL)'<br>
<br>
<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Anil,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Please see inline [Bru=
no]<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Anil Kum=
ar S N (VRP Network BL) [<a href=3D"mailto:anil.sn@huawei.com">mailto:anil.=
sn@huawei.com</a>]
<br>
<b>Sent:</b> Thursday, April 02, 2015 10:53 AM<br>
<br>
<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">Hi Bruno,Chris,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; Lets not talk about number of labels. With respect to TI=
 LFA, In our implementation we have extended number labels much more than t=
wo,
<span style=3D"color:#1F497D"><o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 Good job.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">- For l=
ink protection only, in network with symmetric link cost, up to 2 labels ma=
y be required for. Never more than 2.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">- For o=
thers cases, in particular node and/or SRLG protection, more than 2 labels =
may be required. In theory, there is no limit. In practice, there is a limi=
t. In our networks, the max found was
 4 labels. So it&#8217;s good to be able to push more than 2 labels to enfo=
rce the FRR detour.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">Ex: when there is no PQ node also wh=
en there no adjacency b/w any &nbsp;P and Q node pair. &nbsp;We find a shor=
test path from P &amp; Q form; a label stack that will be pushed. In case
 L3 VPN PE label stack could become much more. This consumes more computati=
on.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">Best effort label for a destination =
is Destination Label , SR FRR label for the same destination is [P Node -&g=
t; Label stack to reach Q Node -&gt; Destination label].<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">[Bruno]=
 I would propose<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">OLD: </=
span><span lang=3D"EN-US" style=3D"color:#1F497D">using an MPLS label stack=
 with two labels</span><span lang=3D"EN-US" style=3D"color:#8064A2"><o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#8064A2">NEW: by=
 pushing up to two additional labels</span><span lang=3D"EN-US" style=3D"co=
lor:#1F497D"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">There is a possibility of Looping in=
 TI-LFA; We can expect in case of multiple simultanious failure:<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 You are right. In case of independent/non FRR planned failures, the first =
PLR can&#8217;t avoid all failures since those failures were expected to no=
t planned/expected to occur at the same time.
 The second PLR will try to protect the second failure. In good cases, the =
two protections are complementary and will achieve &#8220;de facto&#8221; p=
rotection. In bad cases, forwarding loop will occur. In theory, the handlin=
g of the second independent failure, is a (difficult)
 choice, between dropping or trying to repair. In theory TI-LFA could do bo=
th, but as of today, it tries the second protection<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">This is=
 not specific to TI-LFA. FRR assumes _<i>local</i>_ protection (hence local=
 knowledge) of a _<i>pre_computed</i>_ (hence pre-planned) failure.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">I have =
been told ARC could handle multiple consecutive FRR (through some localize =
notification mechanism) but I don&#8217;t have the details.<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">Consider the case where packet is be=
en forwarded towards destination from a source on backup FRR path with TI L=
FA backup path Statck &nbsp;as below :<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">P Node Lable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">P-Node to Q-Node Adj lable<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">Q-Node Lable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">Destination Lable<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">Topology :<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">P----Q (Cost 10)<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">Q----Destination(Cost 10)<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">P----Destination (Cost 100)<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">Faliure happens on the only link b/w=
 Q-Node towards destination; Reachability to destination with SPF calculati=
on or with FRR falls back towards P-Node (Q&#8217;s TI LFA calculation).
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 In this specific case, I don&#8217;t see a loop. Q, acting as the second P=
LR (in a row), has computed that &nbsp;node &#8220;P&#8221; is its P node a=
nd node &#8220;D&#8221; is its Q node. P is reached via a node-SID (possibly
 implicit label) which is not affected by the first failure. Q is reached b=
y a Adj-sid, which is not affected by the first failure.<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">So there could be a loop.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 I could not find one in this example, but I agree that we could find examp=
les with loops.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">e.g. th=
e following topology<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">A &#821=
1; B<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">|&nbsp;=
 \&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">C &#821=
1; D<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Where a=
ll links have a metric of 10, except AC which has 100. For the traffic from=
 A to C, if both AC and BD links fails at the same time (and were not ident=
ified as SRLG), there will be a loop between
 A and B. (and funnily (is it? ;-) ) as packets are looped, the label stack=
 seems to increase to &#8220;infinity&#8221; as additional P nodes (alterna=
tively C and D) are used.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">So I still feel there is a tradeoff.=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 There are many tradeoff ;-). But this one is about handling a second indep=
endent failure. Not about increase coverage of a protected resource (link/n=
ode/SRLG/any)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Regards=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">/Bruno<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks =
&amp; Regards<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Anil S =
N<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&#8220;=
Be liberal in what you accept, and conservative in what you send&#8221; - J=
on Postel<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
</div>
</div>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

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.
</PRE></body>
</html>

--_000_53C29892C857584299CBF5D05346208A0EB90A87PEXCVZYM11corpo_--


From nobody Thu Apr  2 04:54:23 2015
Return-Path: <anil.sn@huawei.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 B6CA31B2C82 for <rtgwg@ietfa.amsl.com>; Thu,  2 Apr 2015 04:54:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.61
X-Spam-Level: 
X-Spam-Status: No, score=-3.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 JZlFFVPIgmGt for <rtgwg@ietfa.amsl.com>; Thu,  2 Apr 2015 04:54:16 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85D5C1B2C7C for <rtgwg@ietf.org>; Thu,  2 Apr 2015 04:54:15 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQZ23386; Thu, 02 Apr 2015 11:54:12 +0000 (GMT)
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 2 Apr 2015 12:54:09 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.135]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Thu, 2 Apr 2015 19:54:01 +0800
From: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Topic: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Index: AdBohapCLAg3Un3wSOKmk0bREwcgiQDiTs4wABBanbAAEjQyoAAe1PUwAAK3dZAAAq50sAADctrA
Date: Thu, 2 Apr 2015 11:54:01 +0000
Message-ID: <327562D94EA7BF428CD805F338C31EF04FB359F2@nkgeml512-mbx.china.huawei.com>
References: <327562D94EA7BF428CD805F338C31EF04FB31080@NKGEML512-MBS.china.huawei.com> <BLUPR05MB292105B133237D6FF24FD1CA9F30@BLUPR05MB292.namprd05.prod.outlook.com> <31522_1427875907_551BA843_31522_7672_1_53C29892C857584299CBF5D05346208A0EB8AE1B@PEXCVZYM11.corporate.adroot.infra.ftgroup> <BLUPR05MB2920299048499D0BDF4C4A8A9F30@BLUPR05MB292.namprd05.prod.outlook.com> <20271_1427960574_551CF2FD_20271_1912_1_53C29892C857584299CBF5D05346208A0EB907E6@PEXCVZYM11.corporate.adroot.infra.ftgroup> <327562D94EA7BF428CD805F338C31EF04FB358AD@nkgeml512-mbx.china.huawei.com> <3799_1427970236_551D18BC_3799_320_1_53C29892C857584299CBF5D05346208A0EB90A36@PEXCVZYM11.corporate.adroot.infra.ftgroup>
In-Reply-To: <3799_1427970236_551D18BC_3799_320_1_53C29892C857584299CBF5D05346208A0EB90A36@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.152.169]
Content-Type: multipart/alternative; boundary="_000_327562D94EA7BF428CD805F338C31EF04FB359F2nkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/lkF_dr4JuTBJFsS9Zoj0h1_8lno>
Cc: Veerendranatha Reddy Vallem <veerendranatharv@huawei.com>, Rajeshmv <rajeshmv@huawei.com>, Alia Atlas <akatlas@juniper.net>, Kalyankumar Asangi <kalyana@huawei.com>, "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, 02 Apr 2015 11:54:21 -0000

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

Hi Bruno,

                :) Lets finalize on the rephrased statement which need to b=
e updated.
                Please see inline [Anil]

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel


From: bruno.decraene@orange.com [mailto:bruno.decraene@orange.com]
Sent: 02 April 2015 18:24
To: Anil Kumar S N (VRP Network BL)
Cc: pierre.francois@imdea.org; Alia Atlas; Robert Kebler; Gabor.Sandor.Enye=
di@ericsson.com; Andras.Csaszar@ericsson.com; jeff.tantsura@ericsson.com; r=
ussw@riw.us; rtgwg@ietf.org; dhruv.ietf@gmail.com; Kalyankumar Asangi; Raje=
shmv; Veerendranatha Reddy Vallem; Chris Bowers
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Anil,

Please see inline [Bruno]

From: Anil Kumar S N (VRP Network BL) [mailto:anil.sn@huawei.com]
Sent: Thursday, April 02, 2015 10:53 AM
To: DECRAENE Bruno IMT/OLN; Chris Bowers
Cc: pierre.francois@imdea.org<mailto:pierre.francois@imdea.org>; Alia Atlas=
; Robert Kebler; Gabor.Sandor.Enyedi@ericsson.com<mailto:Gabor.Sandor.Enyed=
i@ericsson.com>; Andras.Csaszar@ericsson.com<mailto:Andras.Csaszar@ericsson=
.com>; jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericsson.com>; russw=
@riw.us<mailto:russw@riw.us>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>; dhruv.=
ietf@gmail.com<mailto:dhruv.ietf@gmail.com>; Kalyankumar Asangi; Rajeshmv; =
Veerendranatha Reddy Vallem
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Bruno,Chris,

          Lets not talk about number of labels. With respect to TI LFA, In =
our implementation we have extended number labels much more than two,
[Bruno] Good job.
- For link protection only, in network with symmetric link cost, up to 2 la=
bels may be required for. Never more than 2.
- For others cases, in particular node and/or SRLG protection, more than 2 =
labels may be required. In theory, there is no limit. In practice, there is=
 a limit. In our networks, the max found was 4 labels. So it's good to be a=
ble to push more than 2 labels to enforce the FRR detour.

[Anil] : Agreed

Ex: when there is no PQ node also when there no adjacency b/w any  P and Q =
node pair.  We find a shortest path from P & Q form; a label stack that wil=
l be pushed. In case L3 VPN PE label stack could become much more. This con=
sumes more computation.

Best effort label for a destination is Destination Label , SR FRR label for=
 the same destination is [P Node -> Label stack to reach Q Node -> Destinat=
ion label].

[Bruno] I would propose
OLD: using an MPLS label stack with two labels
NEW: by pushing up to two additional labels

There is a possibility of Looping in TI-LFA; We can expect in case of multi=
ple simultanious failure:
[Bruno] You are right. In case of independent/non FRR planned failures, the=
 first PLR can't avoid all failures since those failures were expected to n=
ot planned/expected to occur at the same time. The second PLR will try to p=
rotect the second failure. In good cases, the two protections are complemen=
tary and will achieve "de facto" protection. In bad cases, forwarding loop =
will occur. In theory, the handling of the second independent failure, is a=
 (difficult) choice, between dropping or trying to repair. In theory TI-LFA=
 could do both, but as of today, it tries the second protection
This is not specific to TI-LFA. FRR assumes _local_ protection (hence local=
 knowledge) of a _pre_computed_ (hence pre-planned) failure.
I have been told ARC could handle multiple consecutive FRR (through some lo=
calize notification mechanism) but I don't have the details.

[Anil] : I also suggested authors to add comparison with respect to ARC too=
.

Consider the case where packet is been forwarded towards destination from a=
 source on backup FRR path with TI LFA backup path Statck  as below :
P Node Lable
P-Node to Q-Node Adj lable
Q-Node Lable
Destination Lable

Topology :
P----Q (Cost 10)
Q----Destination(Cost 10)
P----Destination (Cost 100)

Faliure happens on the only link b/w Q-Node towards destination; Reachabili=
ty to destination with SPF calculation or with FRR falls back towards P-Nod=
e (Q's TI LFA calculation).
[Bruno] In this specific case, I don't see a loop. Q, acting as the second =
PLR (in a row), has computed that  node "P" is its P node and node "D" is i=
ts Q node. P is reached via a node-SID (possibly implicit label) which is n=
ot affected by the first failure. Q is reached by a Adj-sid, which is not a=
ffected by the first failure.

[Anil] : Here P would send a packet to Q and as primary path to D is lost Q=
 would return packet back to P till P learns link b/w Q and D is down.


So there could be a loop.
[Bruno] I could not find one in this example, but I agree that we could fin=
d examples with loops.
e.g. the following topology
A - B
|  \  |
C - D

Where all links have a metric of 10, except AC which has 100. For the traff=
ic from A to C, if both AC and BD links fails at the same time (and were no=
t identified as SRLG), there will be a loop between A and B. (and funnily (=
is it? ;-) ) as packets are looped, the label stack seems to increase to "i=
nfinity" as additional P nodes (alternatively C and D) are used.

[Anil] : I understand Loop here but Label stack increase can you help me to=
 understand.
Here primary path would be A->D->C  [Cost 20]  for A (LFA A->B->D->C), Prim=
ary path for B to would be B->D->C [Cost 20] (LFA B->A->D->C).
On A->C link failure A chooses A->B->D->C, On B->D failure B chooses B->A->=
D->C. A would send packet to B and B would send packet to A.

Here which label is inserted ?

         10
   A           B
    +---------+
    | \       |
    |  \      |
    |   \     |
    |    \10  | 10
100 |     \   |
    |      \  |
    |       \ |
    |        \|
    +---------+
 C      10      D



So I still feel there is a tradeoff.
[Bruno] There are many tradeoff ;-). But this one is about handling a secon=
d independent failure. Not about increase coverage of a protected resource =
(link/node/SRLG/any)
[Anil] : This Could be explicitly specified :)

Thanks
Regards
/Bruno

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel


--_000_327562D94EA7BF428CD805F338C31EF04FB359F2nkgeml512mbxchi_
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 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Bookman Old Style";
	panose-1:2 5 6 4 5 5 5 2 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-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:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI","sans-serif";}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:Consolas;}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
	{mso-style-name:"Pr\00E9format\00E9 HTML";
	mso-style-link:"Pr\00E9format\00E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
p.Textedebulles, li.Textedebulles, div.Textedebulles
	{mso-style-name:"Texte de bulles";
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle26
	{mso-style-type:personal;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle29
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle30
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle31
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle33
	{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:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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 lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Bruno,<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span=
><span style=3D"font-family:Wingdings;color:#1F497D">J</span><span style=3D=
"color:#1F497D"> Lets finalize on the rephrased statement which need to be =
updated. &nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Please=
 see inline [Anil]<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks &amp; Regards<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Anil S N<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&#8220;Be liberal in w=
hat you accept, and conservative in what you send&#8221; - Jon Postel<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> bruno.de=
craene@orange.com [mailto:bruno.decraene@orange.com]
<br>
<b>Sent:</b> 02 April 2015 18:24<br>
<b>To:</b> Anil Kumar S N (VRP Network BL)<br>
<b>Cc:</b> pierre.francois@imdea.org; Alia Atlas; Robert Kebler; Gabor.Sand=
or.Enyedi@ericsson.com; Andras.Csaszar@ericsson.com; jeff.tantsura@ericsson=
.com; russw@riw.us; rtgwg@ietf.org; dhruv.ietf@gmail.com; Kalyankumar Asang=
i; Rajeshmv; Veerendranatha Reddy
 Vallem; Chris Bowers<br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"color:#1F497D">Hi Anil,<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"color:#1F497D">Please see=
 inline [Bruno]<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"FR" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lan=
g=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;san=
s-serif&quot;"> Anil Kumar S N (VRP Network BL) [<a href=3D"mailto:anil.sn@=
huawei.com">mailto:anil.sn@huawei.com</a>]
<br>
<b>Sent:</b> Thursday, April 02, 2015 10:53 AM<br>
<b>To:</b> DECRAENE Bruno IMT/OLN; Chris Bowers<br>
<b>Cc:</b> <a href=3D"mailto:pierre.francois@imdea.org">pierre.francois@imd=
ea.org</a>; Alia Atlas; Robert Kebler;
<a href=3D"mailto:Gabor.Sandor.Enyedi@ericsson.com">Gabor.Sandor.Enyedi@eri=
csson.com</a>;
<a href=3D"mailto:Andras.Csaszar@ericsson.com">Andras.Csaszar@ericsson.com<=
/a>; <a href=3D"mailto:jeff.tantsura@ericsson.com">
jeff.tantsura@ericsson.com</a>; <a href=3D"mailto:russw@riw.us">russw@riw.u=
s</a>; <a href=3D"mailto:rtgwg@ietf.org">
rtgwg@ietf.org</a>; <a href=3D"mailto:dhruv.ietf@gmail.com">dhruv.ietf@gmai=
l.com</a>; Kalyankumar Asangi; Rajeshmv; Veerendranatha Reddy Vallem<br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"FR"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Hi Bruno,Chris,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Lets not talk about number of labels. With respect to TI LFA, In our im=
plementation we have extended number labels much more than two,
<span style=3D"color:#1F497D"><o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] Good job.<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">- For link protection =
only, in network with symmetric link cost, up to 2 labels may be required f=
or. Never more than 2.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">- For others cases, in=
 particular node and/or SRLG protection, more than 2 labels may be required=
. In theory, there is no limit. In practice, there is a limit. In our netwo=
rks, the max found was 4 labels. So
 it&#8217;s good to be able to push more than 2 labels to enforce the FRR d=
etour. <o:p>
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">[Anil] : Agreed<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Ex: when there is no PQ node also when there no adj=
acency b/w any &nbsp;P and Q node pair. &nbsp;We find a shortest path from =
P &amp; Q form; a label stack that will be pushed. In case L3 VPN PE label
 stack could become much more. This consumes more computation.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Best effort label for a destination is Destination =
Label , SR FRR label for the same destination is [P Node -&gt; Label stack =
to reach Q Node -&gt; Destination label].<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">[Bruno] I would propos=
e<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">OLD: </span><span styl=
e=3D"color:#1F497D">using an MPLS label stack with two labels</span><span s=
tyle=3D"color:#8064A2"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#8064A2">NEW: by pushing up to =
two additional labels</span><span style=3D"color:#1F497D"><o:p></o:p></span=
></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">There is a possibility of Looping in TI-LFA; We can=
 expect in case of multiple simultanious failure:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] You are right.=
 In case of independent/non FRR planned failures, the first PLR can&#8217;t=
 avoid all failures since those failures were expected to not planned/expec=
ted to occur at the same time. The second
 PLR will try to protect the second failure. In good cases, the two protect=
ions are complementary and will achieve &#8220;de facto&#8221; protection. =
In bad cases, forwarding loop will occur. In theory, the handling of the se=
cond independent failure, is a (difficult) choice,
 between dropping or trying to repair. In theory TI-LFA could do both, but =
as of today, it tries the second protection<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">This is not specific t=
o TI-LFA. FRR assumes _<i>local</i>_ protection (hence local knowledge) of =
a _<i>pre_computed</i>_ (hence pre-planned) failure.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I have been told ARC c=
ould handle multiple consecutive FRR (through some localize notification me=
chanism) but I don&#8217;t have the details.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">[Anil] : I also sugges=
ted authors to add comparison with respect to ARC too.<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Consider the case where packet is been forwarded to=
wards destination from a source on backup FRR path with TI LFA backup path =
Statck &nbsp;as below :<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">P Node Lable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">P-Node to Q-Node Adj lable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Q-Node Lable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Destination Lable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Topology :<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">P----Q (Cost 10)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Q----Destination(Cost 10)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">P----Destination (Cost 100)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Faliure happens on the only link b/w Q-Node towards=
 destination; Reachability to destination with SPF calculation or with FRR =
falls back towards P-Node (Q&#8217;s TI LFA calculation).
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] In this specif=
ic case, I don&#8217;t see a loop. Q, acting as the second PLR (in a row), =
has computed that &nbsp;node &#8220;P&#8221; is its P node and node &#8220;=
D&#8221; is its Q node. P is reached via a node-SID (possibly implicit
 label) which is not affected by the first failure. Q is reached by a Adj-s=
id, which is not affected by the first failure.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">[Anil] : Here P would =
send a packet to Q and as primary path to D is lost Q would return packet b=
ack to P till P learns link b/w Q and D is down.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">So there could be a loop.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] I could not fi=
nd one in this example, but I agree that we could find examples with loops.=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">e.g. the following top=
ology<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">A &#8211; B<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">|&nbsp; \&nbsp; |<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">C &#8211; D<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Where all links have a=
 metric of 10, except AC which has 100. For the traffic from A to C, if bot=
h AC and BD links fails at the same time (and were not identified as SRLG),=
 there will be a loop between A and
 B. (and funnily (is it? ;-) ) as packets are looped, the label stack seems=
 to increase to &#8220;infinity&#8221; as additional P nodes (alternatively=
 C and D) are used.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">[Anil] : I understand =
Loop here but Label stack increase can you help me to understand.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">Here primary path woul=
d be A-&gt;D-&gt;C &nbsp;[Cost 20] &nbsp;for A (LFA A-&gt;B-&gt;D-&gt;C), P=
rimary path for B to would be B-&gt;D-&gt;C [Cost 20] (LFA B-&gt;A-&gt;D-&g=
t;C).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">On A-&gt;C link failur=
e A chooses A-&gt;B-&gt;D-&gt;C, On B-&gt;D failure B chooses B-&gt;A-&gt;D=
-&gt;C. A would send packet to B and B would send packet to A.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">Here which label is in=
serted ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; &nbsp;&nbsp;10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;A&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;&#43;---=
------&#43;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;| \&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; =
\&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&=
nbsp; \&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&=
nbsp; &nbsp;\10&nbsp; | 10<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">100 |&nbsp;&nbsp;&nbsp;&nbsp; \&=
nbsp;&nbsp; |&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; \&nbsp; |&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \ |&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \|&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;&#43;---=
------&#43;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;;c=
olor:#00B050">&nbsp;C&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; D<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;;c=
olor:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;;c=
olor:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;;c=
olor:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">So I still feel there is a tradeoff.<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] There are many=
 tradeoff ;-). But this one is about handling a second independent failure.=
 Not about increase coverage of a protected resource (link/node/SRLG/any)<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">[Anil] : This Could be=
 explicitly specified
</span><span style=3D"font-family:Wingdings;color:#00B050">J</span><span st=
yle=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">/Bruno<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks &amp; Regards<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Anil S N<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&#8220;Be liberal in w=
hat you accept, and conservative in what you send&#8221; - Jon Postel<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
</div>
</div>
</body>
</html>

--_000_327562D94EA7BF428CD805F338C31EF04FB359F2nkgeml512mbxchi_--


From nobody Thu Apr  2 06:06:47 2015
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 370711A8A12 for <rtgwg@ietfa.amsl.com>; Thu,  2 Apr 2015 06:06:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 OS5ZL89MQjeW for <rtgwg@ietfa.amsl.com>; Thu,  2 Apr 2015 06:06:41 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A84A1A8A7E for <rtgwg@ietf.org>; Thu,  2 Apr 2015 06:05:47 -0700 (PDT)
Received: from omfeda07.si.francetelecom.fr (unknown [xx.xx.xx.200]) by omfeda09.si.francetelecom.fr (ESMTP service) with ESMTP id AC79AC0870 for <rtgwg@ietf.org>; Thu,  2 Apr 2015 15:05:45 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfeda07.si.francetelecom.fr (ESMTP service) with ESMTP id 6E61515805A for <rtgwg@ietf.org>; Thu,  2 Apr 2015 15:05:45 +0200 (CEST)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0224.002; Thu, 2 Apr 2015 15:05:45 +0200
From: <bruno.decraene@orange.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Topic: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Index: AdBohapCLAg3Un3wSOKmk0bREwcgiQDiTs4wABBanbAAEjQyoAAe1PUwAAK3dZAAAq50sAADctrAAAKKjTAAAOfZ0A==
Date: Thu, 2 Apr 2015 13:05:44 +0000
Message-ID: <24865_1427979945_551D3EA9_24865_1491_1_53C29892C857584299CBF5D05346208A0EB90E88@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <327562D94EA7BF428CD805F338C31EF04FB31080@NKGEML512-MBS.china.huawei.com> <BLUPR05MB292105B133237D6FF24FD1CA9F30@BLUPR05MB292.namprd05.prod.outlook.com> <31522_1427875907_551BA843_31522_7672_1_53C29892C857584299CBF5D05346208A0EB8AE1B@PEXCVZYM11.corporate.adroot.infra.ftgroup> <BLUPR05MB2920299048499D0BDF4C4A8A9F30@BLUPR05MB292.namprd05.prod.outlook.com> <20271_1427960574_551CF2FD_20271_1912_1_53C29892C857584299CBF5D05346208A0EB907E6@PEXCVZYM11.corporate.adroot.infra.ftgroup> <327562D94EA7BF428CD805F338C31EF04FB358AD@nkgeml512-mbx.china.huawei.com> <3799_1427970236_551D18BC_3799_320_1_53C29892C857584299CBF5D05346208A0EB90A36@PEXCVZYM11.corporate.adroot.infra.ftgroup> <327562D94EA7BF428CD805F338C31EF04FB359DE@nkgeml512-mbx.china.huawei.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.6]
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A0EB90E88PEXCVZYM11corpo_"
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.2.12.3031
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/SliDiXA4C5w3VVqdNfvR91f6CWE>
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, 02 Apr 2015 13:06:46 -0000

--_000_53C29892C857584299CBF5D05346208A0EB90E88PEXCVZYM11corpo_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Re-sending...

From: DECRAENE Bruno IMT/OLN
Sent: Thursday, April 02, 2015 3:00 PM
To: 'Anil Kumar S N (VRP Network BL)'
Cc: pierre.francois@imdea.org; Alia Atlas; Robert Kebler; Gabor.Sandor.Enye=
di@ericsson.com; Andras.Csaszar@ericsson.com; jeff.tantsura@ericsson.com; r=
ussw@riw.us; rtgwg@ietf.org; dhruv.ietf@gmail.com; Kalyankumar Asangi; Raje=
shmv; Veerendranatha Reddy Vallem; Chris Bowers
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Anil,

Please see inline [Bruno2]

Thanks,
Regards,
Bruno

From: Anil Kumar S N (VRP Network BL) [mailto:anil.sn@huawei.com]
Sent: Thursday, April 02, 2015 1:52 PM
To: DECRAENE Bruno IMT/OLN
Cc: pierre.francois@imdea.org; Alia Atlas; Robert Kebler; Gabor.Sandor.Enye=
di@ericsson.com; Andras.Csaszar@ericsson.com; jeff.tantsura@ericsson.com; r=
ussw@riw.us; rtgwg@ietf.org; dhruv.ietf@gmail.com; Kalyankumar Asangi; Raje=
shmv; Veerendranatha Reddy Vallem; Chris Bowers
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Bruno,

                :) Lets finalize on the rephrased statement which need to b=
e updated.
                Please see inline [Anil]

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel


[...]

Consider the case where packet is been forwarded towards destination from a=
 source on backup FRR path with TI LFA backup path Statck  as below :
P Node Lable
P-Node to Q-Node Adj lable
Q-Node Lable
Destination Lable
[Bruno2] As a side note, "Q-Node Label" is not required. (with previous lab=
el, you reach "Q". Then "Q" can directly reach the destination "D")

Topology :
P----Q (Cost 10)
Q----Destination(Cost 10)
P----Destination (Cost 100)

[Bruno2] I understand the following topology
     10         10
P ------ Q ------- D
|                         |
+--------------+
      100

Faliure happens on the only link b/w Q-Node towards destination; Reachabili=
ty to destination with SPF calculation or with FRR falls back towards P-Nod=
e (Q's TI LFA calculation).
[Bruno] In this specific case, I don't see a loop. Q, acting as the second =
PLR (in a row), has computed that  node "P" is its P node and node "D" is i=
ts Q node. P is reached via a node-SID (possibly implicit label) which is n=
ot affected by the first failure. Q is reached by a Adj-sid, which is not a=
ffected by the first failure.

[Anil] : Here P would send a packet to Q and as primary path to D is lost Q=
 would return packet back to P till P learns link b/w Q and D is down.
[Bruno2] Q sees the failure of QD for destination D. It will swap Node_SID =
(D) to  Node_SID (P), Adj_SID PD, Node_SID (D).  (In MPLS, with PHP, first =
and last SID may be encoded with no label)
P will see, at the topo of the stack "Adj_SID PD" and hence will send the t=
raffic to D.
No loop.

So there could be a loop.
[Bruno] I could not find one in this example, but I agree that we could fin=
d examples with loops.
e.g. the following topology
A - B
|  \  |
C - D

Where all links have a metric of 10, except AC which has 100. For the traff=
ic from A to C, if both AC and BD links fails at the same time (and were no=
t identified as SRLG), there will be a loop between A and B. (and funnily (=
is it? ;-) ) as packets are looped, the label stack seems to increase to "i=
nfinity" as additional P nodes (alternatively C and D) are used.

[Anil] : I understand Loop here but Label stack increase can you help me to=
 understand.
[Bruno2] My mistake. Sorry. I meant all links have a metric of 10, except A=
D which has 100
Notation:
Prefix --> Nominal Next-Hop
           =3D> LFA Next-Hop

On node A:
C --> C
   =3D> B, push Node_SID(D),  Node_SID(C)


On node B:
D --> D
   =3D> A, push  Node_SID(C), Node_SID(D)


If both links AC & BD fails, each PLR (A & B) push 1 additional label (resp=
ectively to D & C). Since C & D are never reached, label are never poped. S=
o at each iteration in the loop, an additional label is pushed.

Here primary path would be A->D->C  [Cost 20]  for A (LFA A->B->D->C), Prim=
ary path for B to would be B->D->C [Cost 20] (LFA B->A->D->C).
On A->C link failure A chooses A->B->D->C, On B->D failure B chooses B->A->=
D->C. A would send packet to B and B would send packet to A.

Here which label is inserted ?

         10
   A           B
    +---------+
    | \       |
    |  \      |
    |   \     |
    |    \10  | 10
100 |     \   |
    |      \  |
    |       \ |
    |        \|
    +---------+
 C      10      D



So I still feel there is a tradeoff.
[Bruno] There are many tradeoff ;-). But this one is about handling a secon=
d independent failure. Not about increase coverage of a protected resource =
(link/node/SRLG/any)
[Anil] : This Could be explicitly specified :)
[Bruno2] Indeed, how each solution handles independent failure may be indic=
ated. However, if space is limited in the draft, this is probably not the m=
ost important metric (IMHO) has this situation should rarely happen (assumi=
ng SRLG are known and the solution protects from SRLG)

Thanks
Regards
/Bruno

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel


___________________________________________________________________________=
______________________________________________

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.


--_000_53C29892C857584299CBF5D05346208A0EB90E88PEXCVZYM11corpo_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
	{font-family:"Bookman Old Style";
	panose-1:2 5 6 4 5 5 5 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-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:"Pr=E9format=E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:Consolas;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New","serif";}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI","sans-serif";}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle26
	{mso-style-type:personal;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle29
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle30
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle31
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle33
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle34
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle35
	{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:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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 lang=3D"FR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Re-sending&#8230;<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> DECRAENE=
 Bruno IMT/OLN
<br>
<b>Sent:</b> Thursday, April 02, 2015 3:00 PM<br>
<b>To:</b> 'Anil Kumar S N (VRP Network BL)'<br>
<b>Cc:</b> pierre.francois@imdea.org; Alia Atlas; Robert Kebler; Gabor.Sand=
or.Enyedi@ericsson.com; Andras.Csaszar@ericsson.com; jeff.tantsura@ericsson=
.com; russw@riw.us; rtgwg@ietf.org; dhruv.ietf@gmail.com; Kalyankumar Asang=
i; Rajeshmv; Veerendranatha Reddy
 Vallem; Chris Bowers<br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Anil,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Please =
see inline [Bruno2]<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks,=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Regards=
,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Bruno<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Anil Kum=
ar S N (VRP Network BL) [mailto:anil.sn@huawei.com]
<br>
<b>Sent:</b> Thursday, April 02, 2015 1:52 PM<br>
<b>To:</b> DECRAENE Bruno IMT/OLN<br>
<b>Cc:</b> pierre.francois@imdea.org; Alia Atlas; Robert Kebler; Gabor.Sand=
or.Enyedi@ericsson.com; Andras.Csaszar@ericsson.com; jeff.tantsura@ericsson=
.com; russw@riw.us; rtgwg@ietf.org; dhruv.ietf@gmail.com; Kalyankumar Asang=
i; Rajeshmv; Veerendranatha Reddy
 Vallem; Chris Bowers<br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Hi Brun=
o,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; </span>
<span lang=3D"EN-US" style=3D"font-family:Wingdings;color:#1F497D">J</span>=
<span lang=3D"EN-US" style=3D"color:#1F497D"> Lets finalize on the rephrase=
d statement which need to be updated. &nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; Please see inline [Anil]<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks =
&amp; Regards<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Anil S =
N<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&#8220;=
Be liberal in what you accept, and conservative in what you send&#8221; - J=
on Postel<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:#1F497D">[&#8230;=
]</span></b><span lang=3D"EN-US" style=3D"color:#00B050"><o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">Consider the case where packet is be=
en forwarded towards destination from a source on backup FRR path with TI L=
FA backup path Statck &nbsp;as below :<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">P Node Lable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">P-Node to Q-Node Adj lable<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">Q-Node Lable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">Destination Lable<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno2=
] As a side note, &#8220;Q-Node Label&#8221; is not required. (with previou=
s label, you reach &#8220;Q&#8221;. Then &#8220;Q&#8221; can directly reach=
 the destination &#8220;D&#8221;)</span><span lang=3D"EN-US" style=3D"font-=
family:&quot;Bookman Old Style&quot;,&quot;serif&quot;;color:#1F497D"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">Topology :<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">P----Q (Cost 10)<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">Q----Destination(Cost 10)<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">P----Destination (Cost 100)<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno2=
] I understand the following topology<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">P -----=
- Q ------- D<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">|&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;;color:#1F497D">&#43;--------------&#4=
3;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; 100<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">Faliure happens on the only link b/w=
 Q-Node towards destination; Reachability to destination with SPF calculati=
on or with FRR falls back towards P-Node (Q&#8217;s TI LFA calculation).
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 In this specific case, I don&#8217;t see a loop. Q, acting as the second P=
LR (in a row), has computed that &nbsp;node &#8220;P&#8221; is its P node a=
nd node &#8220;D&#8221; is its Q node. P is reached via a node-SID (possibly
 implicit label) which is not affected by the first failure. Q is reached b=
y a Adj-sid, which is not affected by the first failure.<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#00B050">[Anil] =
: Here P would send a packet to Q and as primary path to D is lost Q would =
return packet back to P till P learns link b/w Q and D is down.<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno2=
] Q sees the failure of QD for destination D. It will swap Node_SID (D) to =
&nbsp;Node_SID (P), Adj_SID PD, Node_SID (D).&nbsp; (In MPLS, with PHP, fir=
st and last SID may be encoded with no label)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">P will =
see, at the topo of the stack &#8220;Adj_SID PD&#8221; and hence will send =
the traffic to D.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">No loop=
.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">So there could be a loop.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 I could not find one in this example, but I agree that we could find examp=
les with loops.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">e.g. th=
e following topology<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">A &#821=
1; B<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">|&nbsp;=
 \&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">C &#821=
1; D<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Where a=
ll links have a metric of 10, except AC which has 100. For the traffic from=
 A to C, if both AC and BD links fails at the same time (and were not ident=
ified as SRLG), there will be a loop between
 A and B. (and funnily (is it? ;-) ) as packets are looped, the label stack=
 seems to increase to &#8220;infinity&#8221; as additional P nodes (alterna=
tively C and D) are used.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#00B050">[Anil] =
: I understand Loop here but Label stack increase can you help me to unders=
tand.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno2=
] My mistake. Sorry. I meant all links have a metric of 10, except
<b>AD</b> which has 100<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Notatio=
n:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Prefix =
</span><span lang=3D"EN-US" style=3D"font-family:Wingdings;color:#1F497D">=
=E0</span><span lang=3D"EN-US" style=3D"color:#1F497D"> Nominal Next-Hop<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D&gt; LFA Next-Hop<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">On node=
 A:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">C </spa=
n><span lang=3D"EN-US" style=3D"font-family:Wingdings;color:#1F497D">=E0</s=
pan><span lang=3D"EN-US" style=3D"color:#1F497D"> C<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp; =3D&gt; B, push Node_SID(D),&nbsp; Node_SID(C)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">On node=
 B:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">D </spa=
n><span lang=3D"EN-US" style=3D"font-family:Wingdings;color:#1F497D">=E0</s=
pan><span lang=3D"EN-US" style=3D"color:#1F497D"> D<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp; =3D&gt; A, push&nbsp; Node_SID(C), Node_SID(D)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">If both=
 links AC &amp; BD fails, each PLR (A &amp; B) push 1 additional label (res=
pectively to D &amp; C). Since C &amp; D are never reached, label are never=
 poped. So at each iteration in the loop, an additional
 label is pushed.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#00B050">Here pr=
imary path would be A-&gt;D-&gt;C &nbsp;[Cost 20] &nbsp;for A (LFA A-&gt;B-=
&gt;D-&gt;C), Primary path for B to would be B-&gt;D-&gt;C [Cost 20] (LFA B=
-&gt;A-&gt;D-&gt;C).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#00B050">On A-&g=
t;C link failure A chooses A-&gt;B-&gt;D-&gt;C, On B-&gt;D failure B choose=
s B-&gt;A-&gt;D-&gt;C. A would send packet to B and B would send packet to =
A.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#00B050"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#00B050">Here wh=
ich label is inserted ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#00B050"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span lang=3D"EN-US" st=
yle=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;;color:#00B050"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;10&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span lang=3D"EN-US" st=
yle=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;;color:#00B050"=
>&nbsp;&nbsp;&nbsp;A&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; B&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span lang=3D"EN-US" st=
yle=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;;color:#00B050"=
>&nbsp;&nbsp;&nbsp;&nbsp;&#43;---------&#43;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span lang=3D"EN-US" st=
yle=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;;color:#00B050"=
>&nbsp;&nbsp;&nbsp;&nbsp;| \&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nb=
sp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span lang=3D"EN-US" st=
yle=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;;color:#00B050"=
>&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; \&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nb=
sp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span lang=3D"EN-US" st=
yle=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;;color:#00B050"=
>&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp; \&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nb=
sp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span lang=3D"EN-US" st=
yle=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;;color:#00B050"=
>&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp; &nbsp;\10&nbsp; | 10<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span lang=3D"EN-US" st=
yle=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;;color:#00B050"=
>100 |&nbsp;&nbsp;&nbsp;&nbsp; \&nbsp;&nbsp; |&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span lang=3D"EN-US" st=
yle=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;;color:#00B050"=
>&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \&nbsp; |&nbsp;&nb=
sp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span lang=3D"EN-US" st=
yle=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;;color:#00B050"=
>&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \ |&nbsp;&nb=
sp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span lang=3D"EN-US" st=
yle=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;;color:#00B050"=
>&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \|&nbs=
p;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span lang=3D"EN-US" st=
yle=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;;color:#00B050"=
>&nbsp;&nbsp;&nbsp;&nbsp;&#43;---------&#43;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cour=
ier New&quot;,&quot;serif&quot;;color:#00B050">&nbsp;C&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; 10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cour=
ier New&quot;,&quot;serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cour=
ier New&quot;,&quot;serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cour=
ier New&quot;,&quot;serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Book=
man Old Style&quot;,&quot;serif&quot;">So I still feel there is a tradeoff.=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno]=
 There are many tradeoff ;-). But this one is about handling a second indep=
endent failure. Not about increase coverage of a protected resource (link/n=
ode/SRLG/any)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#00B050">[Anil] =
: This Could be explicitly specified
</span><span lang=3D"EN-US" style=3D"font-family:Wingdings;color:#00B050">J=
</span><span lang=3D"EN-US" style=3D"font-family:Wingdings;color:#1F497D"><=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">[Bruno2=
] Indeed, how each solution handles independent failure may be indicated. H=
owever, if space is limited in the draft, this is probably not the most imp=
ortant metric (IMHO) has this situation
 should rarely happen (assuming SRLG are known and the solution protects fr=
om SRLG)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Regards=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">/Bruno<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks =
&amp; Regards<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Anil S =
N<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&#8220;=
Be liberal in what you accept, and conservative in what you send&#8221; - J=
on Postel<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
</div>
</div>
</div>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

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.
</PRE></body>
</html>

--_000_53C29892C857584299CBF5D05346208A0EB90E88PEXCVZYM11corpo_--


From nobody Thu Apr  2 06:15:52 2015
Return-Path: <anil.sn@huawei.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 D6E271A8703 for <rtgwg@ietfa.amsl.com>; Thu,  2 Apr 2015 06:15:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 jjDWU3weQfTm for <rtgwg@ietfa.amsl.com>; Thu,  2 Apr 2015 06:15:46 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E5D51A87BD for <rtgwg@ietf.org>; Thu,  2 Apr 2015 06:15:45 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQZ31918; Thu, 02 Apr 2015 13:15:43 +0000 (GMT)
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 2 Apr 2015 14:15:42 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.135]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Thu, 2 Apr 2015 21:15:36 +0800
From: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Topic: draft-ietf-rtgwg-mrt-frr-architecture-05.txt
Thread-Index: AdBohapCLAg3Un3wSOKmk0bREwcgiQDiTs4wABBanbAAEjQyoAAe1PUwAAK3dZAAAq50sAADctrAAAKKjTAAAOfZ0AAAV06A
Date: Thu, 2 Apr 2015 13:15:35 +0000
Message-ID: <327562D94EA7BF428CD805F338C31EF04FB35A99@nkgeml512-mbx.china.huawei.com>
References: <327562D94EA7BF428CD805F338C31EF04FB31080@NKGEML512-MBS.china.huawei.com> <BLUPR05MB292105B133237D6FF24FD1CA9F30@BLUPR05MB292.namprd05.prod.outlook.com> <31522_1427875907_551BA843_31522_7672_1_53C29892C857584299CBF5D05346208A0EB8AE1B@PEXCVZYM11.corporate.adroot.infra.ftgroup> <BLUPR05MB2920299048499D0BDF4C4A8A9F30@BLUPR05MB292.namprd05.prod.outlook.com> <20271_1427960574_551CF2FD_20271_1912_1_53C29892C857584299CBF5D05346208A0EB907E6@PEXCVZYM11.corporate.adroot.infra.ftgroup> <327562D94EA7BF428CD805F338C31EF04FB358AD@nkgeml512-mbx.china.huawei.com> <3799_1427970236_551D18BC_3799_320_1_53C29892C857584299CBF5D05346208A0EB90A36@PEXCVZYM11.corporate.adroot.infra.ftgroup> <327562D94EA7BF428CD805F338C31EF04FB359DE@nkgeml512-mbx.china.huawei.com> <24865_1427979945_551D3EA9_24865_1491_1_53C29892C857584299CBF5D05346208A0EB90E88@PEXCVZYM11.corporate.adroot.infra.ftgroup>
In-Reply-To: <24865_1427979945_551D3EA9_24865_1491_1_53C29892C857584299CBF5D05346208A0EB90E88@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.152.169]
Content-Type: multipart/alternative; boundary="_000_327562D94EA7BF428CD805F338C31EF04FB35A99nkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/-HU2Odu7Br8u5urfq9PqjOUT2PQ>
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, 02 Apr 2015 13:15:51 -0000

--_000_327562D94EA7BF428CD805F338C31EF04FB35A99nkgeml512mbxchi_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Bruno,

                Understood , Thanks a lot.

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel


From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of bruno.decraene@ora=
nge.com
Sent: 02 April 2015 21:06
To: rtgwg@ietf.org
Subject: FW: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Re-sending...

From: DECRAENE Bruno IMT/OLN
Sent: Thursday, April 02, 2015 3:00 PM
To: 'Anil Kumar S N (VRP Network BL)'
Cc: pierre.francois@imdea.org<mailto:pierre.francois@imdea.org>; Alia Atlas=
; Robert Kebler; Gabor.Sandor.Enyedi@ericsson.com<mailto:Gabor.Sandor.Enyed=
i@ericsson.com>; Andras.Csaszar@ericsson.com<mailto:Andras.Csaszar@ericsson=
.com>; jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericsson.com>; russw=
@riw.us<mailto:russw@riw.us>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>; dhruv.=
ietf@gmail.com<mailto:dhruv.ietf@gmail.com>; Kalyankumar Asangi; Rajeshmv; =
Veerendranatha Reddy Vallem; Chris Bowers
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Anil,

Please see inline [Bruno2]

Thanks,
Regards,
Bruno

From: Anil Kumar S N (VRP Network BL) [mailto:anil.sn@huawei.com]
Sent: Thursday, April 02, 2015 1:52 PM
To: DECRAENE Bruno IMT/OLN
Cc: pierre.francois@imdea.org<mailto:pierre.francois@imdea.org>; Alia Atlas=
; Robert Kebler; Gabor.Sandor.Enyedi@ericsson.com<mailto:Gabor.Sandor.Enyed=
i@ericsson.com>; Andras.Csaszar@ericsson.com<mailto:Andras.Csaszar@ericsson=
.com>; jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericsson.com>; russw=
@riw.us<mailto:russw@riw.us>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>; dhruv.=
ietf@gmail.com<mailto:dhruv.ietf@gmail.com>; Kalyankumar Asangi; Rajeshmv; =
Veerendranatha Reddy Vallem; Chris Bowers
Subject: RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt

Hi Bruno,

                :) Lets finalize on the rephrased statement which need to b=
e updated.
                Please see inline [Anil]

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel


[...]

Consider the case where packet is been forwarded towards destination from a=
 source on backup FRR path with TI LFA backup path Statck  as below :
P Node Lable
P-Node to Q-Node Adj lable
Q-Node Lable
Destination Lable
[Bruno2] As a side note, "Q-Node Label" is not required. (with previous lab=
el, you reach "Q". Then "Q" can directly reach the destination "D")

Topology :
P----Q (Cost 10)
Q----Destination(Cost 10)
P----Destination (Cost 100)

[Bruno2] I understand the following topology
     10         10
P ------ Q ------- D
|                         |
+--------------+
      100

Faliure happens on the only link b/w Q-Node towards destination; Reachabili=
ty to destination with SPF calculation or with FRR falls back towards P-Nod=
e (Q's TI LFA calculation).
[Bruno] In this specific case, I don't see a loop. Q, acting as the second =
PLR (in a row), has computed that  node "P" is its P node and node "D" is i=
ts Q node. P is reached via a node-SID (possibly implicit label) which is n=
ot affected by the first failure. Q is reached by a Adj-sid, which is not a=
ffected by the first failure.

[Anil] : Here P would send a packet to Q and as primary path to D is lost Q=
 would return packet back to P till P learns link b/w Q and D is down.
[Bruno2] Q sees the failure of QD for destination D. It will swap Node_SID =
(D) to  Node_SID (P), Adj_SID PD, Node_SID (D).  (In MPLS, with PHP, first =
and last SID may be encoded with no label)
P will see, at the topo of the stack "Adj_SID PD" and hence will send the t=
raffic to D.
No loop.

So there could be a loop.
[Bruno] I could not find one in this example, but I agree that we could fin=
d examples with loops.
e.g. the following topology
A - B
|  \  |
C - D

Where all links have a metric of 10, except AC which has 100. For the traff=
ic from A to C, if both AC and BD links fails at the same time (and were no=
t identified as SRLG), there will be a loop between A and B. (and funnily (=
is it? ;-) ) as packets are looped, the label stack seems to increase to "i=
nfinity" as additional P nodes (alternatively C and D) are used.

[Anil] : I understand Loop here but Label stack increase can you help me to=
 understand.
[Bruno2] My mistake. Sorry. I meant all links have a metric of 10, except A=
D which has 100
Notation:
Prefix --> Nominal Next-Hop
           =3D> LFA Next-Hop

On node A:
C --> C
   =3D> B, push Node_SID(D),  Node_SID(C)


On node B:
D --> D
   =3D> A, push  Node_SID(C), Node_SID(D)


If both links AC & BD fails, each PLR (A & B) push 1 additional label (resp=
ectively to D & C). Since C & D are never reached, label are never poped. S=
o at each iteration in the loop, an additional label is pushed.

Here primary path would be A->D->C  [Cost 20]  for A (LFA A->B->D->C), Prim=
ary path for B to would be B->D->C [Cost 20] (LFA B->A->D->C).
On A->C link failure A chooses A->B->D->C, On B->D failure B chooses B->A->=
D->C. A would send packet to B and B would send packet to A.

Here which label is inserted ?

         10
   A           B
    +---------+
    | \       |
    |  \      |
    |   \     |
    |    \10  | 10
100 |     \   |
    |      \  |
    |       \ |
    |        \|
    +---------+
 C      10      D



So I still feel there is a tradeoff.
[Bruno] There are many tradeoff ;-). But this one is about handling a secon=
d independent failure. Not about increase coverage of a protected resource =
(link/node/SRLG/any)
[Anil] : This Could be explicitly specified :)
[Bruno2] Indeed, how each solution handles independent failure may be indic=
ated. However, if space is limited in the draft, this is probably not the m=
ost important metric (IMHO) has this situation should rarely happen (assumi=
ng SRLG are known and the solution protects from SRLG)

Thanks
Regards
/Bruno

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel


___________________________________________________________________________=
______________________________________________



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.

--_000_327562D94EA7BF428CD805F338C31EF04FB35A99nkgeml512mbxchi_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Bookman Old Style";
	panose-1:2 5 6 4 5 5 5 2 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-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:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI","sans-serif";}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
	{mso-style-name:"Pr\00E9format\00E9 HTML";
	mso-style-link:"Pr\00E9format\00E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:Consolas;}
p.Textedebulles, li.Textedebulles, div.Textedebulles
	{mso-style-name:"Texte de bulles";
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle26
	{mso-style-type:personal;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle29
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle30
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle31
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle33
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle34
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle35
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle36
	{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:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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 lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Bruno,<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Unders=
tood , Thanks a lot.
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks &amp; Regards<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Anil S N<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&#8220;Be liberal in w=
hat you accept, and conservative in what you send&#8221; - Jon Postel<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> rtgwg [m=
ailto:rtgwg-bounces@ietf.org]
<b>On Behalf Of </b>bruno.decraene@orange.com<br>
<b>Sent:</b> 02 April 2015 21:06<br>
<b>To:</b> rtgwg@ietf.org<br>
<b>Subject:</b> FW: draft-ietf-rtgwg-mrt-frr-architecture-05.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"color:#1F497D">Re-sending=
&#8230;</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"color:#1F497D">&nbsp;</sp=
an><span lang=3D"FR"><o:p></o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"FR" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lan=
g=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;san=
s-serif&quot;"> DECRAENE Bruno IMT/OLN
<br>
<b>Sent:</b> Thursday, April 02, 2015 3:00 PM<br>
<b>To:</b> 'Anil Kumar S N (VRP Network BL)'<br>
<b>Cc:</b> <a href=3D"mailto:pierre.francois@imdea.org">pierre.francois@imd=
ea.org</a>; Alia Atlas; Robert Kebler;
<a href=3D"mailto:Gabor.Sandor.Enyedi@ericsson.com">Gabor.Sandor.Enyedi@eri=
csson.com</a>;
<a href=3D"mailto:Andras.Csaszar@ericsson.com">Andras.Csaszar@ericsson.com<=
/a>; <a href=3D"mailto:jeff.tantsura@ericsson.com">
jeff.tantsura@ericsson.com</a>; <a href=3D"mailto:russw@riw.us">russw@riw.u=
s</a>; <a href=3D"mailto:rtgwg@ietf.org">
rtgwg@ietf.org</a>; <a href=3D"mailto:dhruv.ietf@gmail.com">dhruv.ietf@gmai=
l.com</a>; Kalyankumar Asangi; Rajeshmv; Veerendranatha Reddy Vallem; Chris=
 Bowers<br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt</span><spa=
n lang=3D"FR"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"FR">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"color:#1F497D">Hi Anil,</=
span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"color:#1F497D">&nbsp;</sp=
an><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Please see inline [Bru=
no2]</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks,</span><span la=
ng=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,</span><span l=
ang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Bruno</span><span lang=
=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"FR" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lan=
g=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;san=
s-serif&quot;"> Anil Kumar S N (VRP Network BL) [<a href=3D"mailto:anil.sn@=
huawei.com">mailto:anil.sn@huawei.com</a>]
<br>
<b>Sent:</b> Thursday, April 02, 2015 1:52 PM<br>
<b>To:</b> DECRAENE Bruno IMT/OLN<br>
<b>Cc:</b> <a href=3D"mailto:pierre.francois@imdea.org">pierre.francois@imd=
ea.org</a>; Alia Atlas; Robert Kebler;
<a href=3D"mailto:Gabor.Sandor.Enyedi@ericsson.com">Gabor.Sandor.Enyedi@eri=
csson.com</a>;
<a href=3D"mailto:Andras.Csaszar@ericsson.com">Andras.Csaszar@ericsson.com<=
/a>; <a href=3D"mailto:jeff.tantsura@ericsson.com">
jeff.tantsura@ericsson.com</a>; <a href=3D"mailto:russw@riw.us">russw@riw.u=
s</a>; <a href=3D"mailto:rtgwg@ietf.org">
rtgwg@ietf.org</a>; <a href=3D"mailto:dhruv.ietf@gmail.com">dhruv.ietf@gmai=
l.com</a>; Kalyankumar Asangi; Rajeshmv; Veerendranatha Reddy Vallem; Chris=
 Bowers<br>
<b>Subject:</b> RE: draft-ietf-rtgwg-mrt-frr-architecture-05.txt</span><spa=
n lang=3D"FR"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"FR">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Bruno,</span><span =
lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span=
><span style=3D"font-family:Wingdings;color:#1F497D">J</span><span style=3D=
"color:#1F497D"> Lets finalize on the rephrased statement which need to be =
updated. &nbsp;</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Please=
 see inline [Anil]</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks &amp; Regards</=
span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Anil S N</span><span l=
ang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&#8220;Be liberal in w=
hat you accept, and conservative in what you send&#8221; - Jon Postel</span=
><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:#1F497D">[&#8230;]</span></b><sp=
an lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Consider the case where packet is been forwarded to=
wards destination from a source on backup FRR path with TI LFA backup path =
Statck &nbsp;as below :</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">P Node Lable</span><span lang=3D"FR"><o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">P-Node to Q-Node Adj lable</span><span lang=3D"FR">=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Q-Node Lable</span><span lang=3D"FR"><o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Destination Lable</span><span lang=3D"FR"><o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno2] As a side not=
e, &#8220;Q-Node Label&#8221; is not required. (with previous label, you re=
ach &#8220;Q&#8221;. Then &#8220;Q&#8221; can directly reach the destinatio=
n &#8220;D&#8221;)</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Topology :</span><span lang=3D"FR"><o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">P----Q (Cost 10)</span><span lang=3D"FR"><o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Q----Destination(Cost 10)</span><span lang=3D"FR"><=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">P----Destination (Cost 100)</span><span lang=3D"FR"=
><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno2] I understand =
the following topology</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p; 10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10</span><span lang=
=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">P ------ Q ------- D</=
span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">|&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</span><span lang=3D"FR">=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;;color:#1F497D">&#43;--------------&#43;</span><span =
lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 100</s=
pan><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;;color:#1F497D">&nbsp;</span><span lang=3D"FR"><o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">Faliure happens on the only link b/w Q-Node towards=
 destination; Reachability to destination with SPF calculation or with FRR =
falls back towards P-Node (Q&#8217;s TI LFA calculation).
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] In this specif=
ic case, I don&#8217;t see a loop. Q, acting as the second PLR (in a row), =
has computed that &nbsp;node &#8220;P&#8221; is its P node and node &#8220;=
D&#8221; is its Q node. P is reached via a node-SID (possibly implicit
 label) which is not affected by the first failure. Q is reached by a Adj-s=
id, which is not affected by the first failure.</span><span lang=3D"FR"><o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">[Anil] : Here P would =
send a packet to Q and as primary path to D is lost Q would return packet b=
ack to P till P learns link b/w Q and D is down.</span><span lang=3D"FR"><o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno2] Q sees the fa=
ilure of QD for destination D. It will swap Node_SID (D) to &nbsp;Node_SID =
(P), Adj_SID PD, Node_SID (D).&nbsp; (In MPLS, with PHP, first and last SID=
 may be encoded with no label)</span><span lang=3D"FR"><o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">P will see, at the top=
o of the stack &#8220;Adj_SID PD&#8221; and hence will send the traffic to =
D.</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">No loop.</span><span l=
ang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">So there could be a loop.
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] I could not fi=
nd one in this example, but I agree that we could find examples with loops.=
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">e.g. the following top=
ology</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">A &#8211; B</span><spa=
n lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">|&nbsp; \&nbsp; |</spa=
n><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">C &#8211; D</span><spa=
n lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Where all links have a=
 metric of 10, except AC which has 100. For the traffic from A to C, if bot=
h AC and BD links fails at the same time (and were not identified as SRLG),=
 there will be a loop between A and
 B. (and funnily (is it? ;-) ) as packets are looped, the label stack seems=
 to increase to &#8220;infinity&#8221; as additional P nodes (alternatively=
 C and D) are used.</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">[Anil] : I understand =
Loop here but Label stack increase can you help me to understand.
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno2] My mistake. S=
orry. I meant all links have a metric of 10, except
<b>AD</b> which has 100</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Notation:</span><span =
lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Prefix </span><span st=
yle=3D"font-family:Wingdings;color:#1F497D">=E0</span><span style=3D"color:=
#1F497D"> Nominal Next-Hop</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D&gt; LFA Next-Hop</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">On node A:</span><span=
 lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">C </span><span style=
=3D"font-family:Wingdings;color:#1F497D">=E0</span><span style=3D"color:#1F=
497D"> C</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp; =3D&gt; B=
, push Node_SID(D),&nbsp; Node_SID(C)</span><span lang=3D"FR"><o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">On node B:</span><span=
 lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">D </span><span style=
=3D"font-family:Wingdings;color:#1F497D">=E0</span><span style=3D"color:#1F=
497D"> D</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp; =3D&gt; A=
, push&nbsp; Node_SID(C), Node_SID(D)</span><span lang=3D"FR"><o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">If both links AC &amp;=
 BD fails, each PLR (A &amp; B) push 1 additional label (respectively to D =
&amp; C). Since C &amp; D are never reached, label are never poped. So at e=
ach iteration in the loop, an additional label is pushed.</span><span lang=
=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">Here primary path woul=
d be A-&gt;D-&gt;C &nbsp;[Cost 20] &nbsp;for A (LFA A-&gt;B-&gt;D-&gt;C), P=
rimary path for B to would be B-&gt;D-&gt;C [Cost 20] (LFA B-&gt;A-&gt;D-&g=
t;C).</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">On A-&gt;C link failur=
e A chooses A-&gt;B-&gt;D-&gt;C, On B-&gt;D failure B chooses B-&gt;A-&gt;D=
-&gt;C. A would send packet to B and B would send packet to A.</span><span =
lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">Here which label is in=
serted ?</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; &nbsp;&nbsp;10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;A&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B&nbsp;
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;&#43;---=
------&#43;&nbsp;&nbsp;
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;| \&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; =
\&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&=
nbsp; \&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&=
nbsp; &nbsp;\10&nbsp; | 10</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">100 |&nbsp;&nbsp;&nbsp;&nbsp; \&=
nbsp;&nbsp; |&nbsp;&nbsp;
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; \&nbsp; |&nbsp;&nbsp;
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \ |&nbsp;&nbsp;
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \|&nbsp;&nbsp;
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;;color:#00B050">&nbsp;&nbsp;&nbsp;&nbsp;&#43;---=
------&#43;&nbsp;&nbsp;
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;;c=
olor:#00B050">&nbsp;C&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; D</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;;c=
olor:#1F497D">&nbsp;</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;;c=
olor:#1F497D">&nbsp;</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;;c=
olor:#1F497D">&nbsp;</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Bookman Old Style&q=
uot;,&quot;serif&quot;">So I still feel there is a tradeoff.</span><span la=
ng=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno] There are many=
 tradeoff ;-). But this one is about handling a second independent failure.=
 Not about increase coverage of a protected resource (link/node/SRLG/any)</=
span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">[Anil] : This Could be=
 explicitly specified
</span><span style=3D"font-family:Wingdings;color:#00B050">J</span><span la=
ng=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Bruno2] Indeed, how e=
ach solution handles independent failure may be indicated. However, if spac=
e is limited in the draft, this is probably not the most important metric (=
IMHO) has this situation should rarely
 happen (assuming SRLG are known and the solution protects from SRLG)</span=
><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards</span><span la=
ng=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">/Bruno</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks &amp; Regards</=
span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Anil S N</span><span l=
ang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&#8220;Be liberal in w=
hat you accept, and conservative in what you send&#8221; - Jon Postel</span=
><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"FR"><o:p></o:p></span></p>
</div>
</div>
</div>
<pre><span lang=3D"FR">____________________________________________________=
_____________________________________________________________________<o:p><=
/o:p></span></pre>
<pre><span lang=3D"FR"><o:p>&nbsp;</o:p></span></pre>
<pre><span lang=3D"FR">Ce message et ses pieces jointes peuvent contenir de=
s informations confidentielles ou privilegiees et ne doivent donc<o:p></o:p=
></span></pre>
<pre><span lang=3D"FR">pas etre diffuses, exploites ou copies sans autorisa=
tion. Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o=
:p></span></pre>
<pre><span lang=3D"FR">a l'expediteur et le detruire ainsi que les pieces j=
ointes. Les messages electroniques etant susceptibles d'alteration,<o:p></o=
:p></span></pre>
<pre><span lang=3D"FR">Orange decline toute responsabilite si ce message a =
ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span lang=3D"FR"><o:p>&nbsp;</o:p></span></pre>
<pre><span lang=3D"FR">This message and its attachments may contain confide=
ntial or privileged information that may be protected by law;<o:p></o:p></s=
pan></pre>
<pre><span lang=3D"FR">they should not be distributed, used or copied witho=
ut authorisation.<o:p></o:p></span></pre>
<pre><span lang=3D"FR">If you have received this email in error, please not=
ify the sender and delete this message and its attachments.<o:p></o:p></spa=
n></pre>
<pre><span lang=3D"FR">As emails may be altered, Orange is not liable for m=
essages that have been modified, changed or falsified.<o:p></o:p></span></p=
re>
<pre><span lang=3D"FR">Thank you.<o:p></o:p></span></pre>
</div>
</body>
</html>

--_000_327562D94EA7BF428CD805F338C31EF04FB35A99nkgeml512mbxchi_--


From nobody Thu Apr 16 10:24:38 2015
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 55A861B3370 for <rtgwg@ietfa.amsl.com>; Thu, 16 Apr 2015 10:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 6omi8Qrfyala for <rtgwg@ietfa.amsl.com>; Thu, 16 Apr 2015 10:24:35 -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 796E91B3369 for <rtgwg@ietf.org>; Thu, 16 Apr 2015 10:24:34 -0700 (PDT)
X-AuditID: c618062d-f79686d0000030a8-c9-552f9965ea31
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 0E.8F.12456.5699F255; Thu, 16 Apr 2015 13:13:41 +0200 (CEST)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0210.002; Thu, 16 Apr 2015 13:24:32 -0400
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Thread-Topic: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Thread-Index: AQHQeGozBdo1pgIIQk2vMrK3UlMfNA==
Date: Thu, 16 Apr 2015 17:24:32 +0000
Message-ID: <D1553E65.9546D%jeff.tantsura@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.4.140807
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E27E0A3DF5D74945B28005188649A734@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBLMWRmVeSWpSXmKPExsUyuXRPgm7qTP1Qg83PTSwuvPnN7MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujGmXDrIX7GKt+Ha0g6WBcSNLFyMnh4SAicSzfxvYIGwxiQv3 1gPZXBxCAkcZJX7fXc0I4SxnlFj1+y4TSBWbgIHE/2/HwbpFBFQleme1gnULC1RLLL36gwWk QUSggVHi87L/UEV6Esdb7oE1swA13D60iRXE5hUwl3i9bx47iM0ItPr7qTVgNcwC4hK3nsxn gjhJQGLJnvPMELaoxMvH/8B6RYFmPtuwmR0iriQx5/U1ZoheHYkFuz+xQdjWEidm3ICKa0ss W/iaGWKvoMTJmU9YJjCKzkKybhaS9llI2mchaZ+FpH0BI+sqRo7S4tSy3HQjg02MwKg4JsGm u4Nxz0vLQ4wCHIxKPLwLxPVDhVgTy4orcw8xSnOwKInzLnpwMERIID2xJDU7NbUgtSi+qDQn tfgQIxMHp1QDY2jtw43Hg1ZO+DF57fKFj1Uf+11gcFn+xbp1UUFOgoDMq7qy7AcvT8mL7NuY YbWTaVb+dGmF4qCExm8157RqGeYvflqUVHK6qHTypNWfF7r2azxZcsHzQb3ENy2n8NczEsR3 m30+y51ntchxUt0s44bPKqslMnIrW+5035g8JeHHzpLXe3O6G5RYijMSDbWYi4oTASZwHXBr AgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/nBtSKWE_c-WH9e0cZBnBGVOLTlY>
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, 16 Apr 2015 17:24:36 -0000

Hi RTGWG,

The authors have requested the RTGWG to adopt:
draft-litkowski-rtgwg-spf-uloop-pb-statement and
draft-decraene-rtgwg-backoff-algo as working group documents.

There was support during the last IETF meeting (92) in Dallas.
Please indicate support or no-support by May 1st, 2015.


If you are listed as a document author or contributor please respond to
this email stating of whether or not you are aware of any relevant IPR.
The response needs to be sent to the RTGWG mailing list. The document will
not advance to the next stage until a response has been received from each
author and each individual that has contributed to the document.


Thanks,


Jeff & Chris


From nobody Thu Apr 16 12:18:43 2015
Return-Path: <ietf-secretariat-reply@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 7D69A1B3501; Thu, 16 Apr 2015 12:18:42 -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 f152J_FIuhL7; Thu, 16 Apr 2015 12:18:41 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 09B091B34F9; Thu, 16 Apr 2015 12:18:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <draft-ietf-rtgwg-mofrr@ietf.org>, <rtgwg-chairs@ietf.org>, <draft-ietf-rtgwg-mofrr.shepherd@ietf.org>, <aretana@cisco.com>, <draft-ietf-rtgwg-mofrr.ad@ietf.org>, <rtgwg@ietf.org>
Subject: ID Tracker State Update Notice: <draft-ietf-rtgwg-mofrr-06.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150416191841.23453.23603.idtracker@ietfa.amsl.com>
Date: Thu, 16 Apr 2015 12:18:41 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/PlurDIxR2_JV68779ddNWHFW9x8>
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, 16 Apr 2015 19:18:42 -0000

IESG state changed to Last Call Requested from AD Evaluation
I have two questions about missing content that I raised during my AD review.  Discussion can happen during IETF Last Call.

It would have been nice to have a sentence or two in there that considered the operational and troubleshooting aspects of MoFRR.  For instance, can mtrace work?  Would lsp-ping fail to work on the secondary UMH because of packets being dropped?

I also recall a private discussion about the interaction of MoFRR and IGP reconvergence after a failure and whether there can be relevant micro-forwarding loops as a result.  It would be very useful to have a sentence or two in this draft that discusses whether micro-forwarding loops are a concern that can either be frequently avoided because the secondary UMH or that needs to be considered in modeling or....
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-rtgwg-mofrr/


From nobody Thu Apr 16 12:19:36 2015
Return-Path: <akatlas@gmail.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 DF6AE1B3503 for <rtgwg@ietfa.amsl.com>; Thu, 16 Apr 2015 12:19:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.399
X-Spam-Level: 
X-Spam-Status: No, score=-101.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_48=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 JGXdTqj1R41t for <rtgwg@ietfa.amsl.com>; Thu, 16 Apr 2015 12:19:33 -0700 (PDT)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3A861B3500 for <rtgwg@ietf.org>; Thu, 16 Apr 2015 12:19:33 -0700 (PDT)
Received: by obbfy7 with SMTP id fy7so49271495obb.2 for <rtgwg@ietf.org>; Thu, 16 Apr 2015 12:19:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=2ORSBbQw+0WUT8zkbjHfJtNMvJqnLA+jWl/ur13wKxY=; b=OaiF0ifi6yTBkhdms/v2pKjOcpIIVZNsXhcg5FxbZjuhczXuNehntcw6BF9l+KgeXw 3VAuCxz/9BnC9hIZM1yhT7E7jOJslzZicsAgM2sYt7ptRyBV7zXZo76BSVrAl/k5e/Cd 8dkJyNvMQx8W9ynNq0/DTKP8QSQSH3v7o6Q6hny99XfYYojXp6FKMB9EZhZ7KKG+nS3H anLDp2/PeJUlFXcnwmQRgVxUZnWEqmP5QHhk4HUHizpXM77ZnYk+azEmQ18UVu96yuqo RsysSeW3jCUZabqjd41hz39jzDofJzo9GwLQAxCqMOP2XXKOqJKYPrb9o8frabczh1QD X8tA==
MIME-Version: 1.0
X-Received: by 10.202.175.213 with SMTP id y204mr21807508oie.22.1429211973276;  Thu, 16 Apr 2015 12:19:33 -0700 (PDT)
Received: by 10.60.44.198 with HTTP; Thu, 16 Apr 2015 12:19:33 -0700 (PDT)
Date: Thu, 16 Apr 2015 15:19:33 -0400
Message-ID: <CAG4d1rcpPxtO7e8sM42qEtzCOoyYsVUZB070Xua4deJreOLsLg@mail.gmail.com>
Subject: progressing draft-ietf-rtgwg-mofrr-06
From: Alia Atlas <akatlas@gmail.com>
To: draft-ietf-rtgwg-mofrr@tools.ietf.org, "rtgwg@ietf.org" <rtgwg@ietf.org>
Content-Type: multipart/alternative; boundary=001a113cf05af9da960513dc57a3
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/buZNw6E2Gh37Yrkfvo9TQF_hnaw>
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, 16 Apr 2015 19:19:35 -0000

--001a113cf05af9da960513dc57a3
Content-Type: text/plain; charset=UTF-8

As is usual, I have done my AD review of draft-ietf-rtgwg-mofrr-06.  I
don't have any specific comments on the text(assuming that the RFC Editor
will pick up the typos I saw).  However, I do see a couple gaps that I
think would be very useful to address.   Feel free to convince me otherwise
- but I think these will make for a stronger RFC.

It would have been nice to have a sentence or two in there that considered
the operational and troubleshooting aspects of MoFRR.  For instance, can
mtrace work?  Would lsp-ping fail to work on the secondary UMH because of
packets being dropped?

I also recall a private discussion about the interaction of MoFRR and IGP
reconvergence after a failure and whether there can be relevant
micro-forwarding loops as a result.  It would be very useful to have a
sentence or two in this draft that discusses whether micro-forwarding loops
are a concern that can either be frequently avoided because the secondary
UMH or that needs to be considered in modeling or....

I'd welcome discussion to clarify these two aspects while the draft is in
IETF Last Call.  I'd like to have these resolved by May 7 so that it can be
on the IESG telechat on May 15.

Thanks for the good work,
Alia

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

<div dir=3D"ltr">As is usual, I have done my AD review of draft-ietf-rtgwg-=
mofrr-06.=C2=A0 I don&#39;t have any specific comments on the text(assuming=
 that the RFC Editor will pick up the typos I saw).=C2=A0 However, I do see=
 a couple gaps that I think would be very useful to address. =C2=A0 Feel fr=
ee to convince me otherwise - but I think these will make for a stronger RF=
C.<br><br>It would have been nice to have a sentence or two in there that c=
onsidered the operational and troubleshooting aspects of MoFRR.=C2=A0 For i=
nstance, can mtrace work?=C2=A0 Would lsp-ping fail to work on the secondar=
y UMH because of packets being dropped?<br><br>I also recall a private disc=
ussion about the interaction of MoFRR and IGP reconvergence after a failure=
 and whether there can be relevant micro-forwarding loops as a result.=C2=
=A0 It would be very useful to have a sentence or two in this draft that di=
scusses whether micro-forwarding loops are a concern that can either be fre=
quently avoided because the secondary UMH or that needs to be considered in=
 modeling or....<br><br>I&#39;d welcome discussion to clarify these two asp=
ects while the draft is in IETF Last Call.=C2=A0 I&#39;d like to have these=
 resolved by May 7 so that it can be on the IESG telechat on May 15.<br><br=
>Thanks for the good work,<br>Alia<br></div>

--001a113cf05af9da960513dc57a3--


From nobody Thu Apr 16 12:19:48 2015
Return-Path: <ietf-secretariat-reply@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 1785C1B350A; Thu, 16 Apr 2015 12:19: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, TVD_SPACE_RATIO=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 895OQBADyFbC; Thu, 16 Apr 2015 12:19:46 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6113A1B3501; Thu, 16 Apr 2015 12:19:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <draft-ietf-rtgwg-mofrr@ietf.org>, <rtgwg-chairs@ietf.org>, <draft-ietf-rtgwg-mofrr.shepherd@ietf.org>, <iesg-secretary@ietf.org>, <iesg@ietf.org>, <aretana@cisco.com>, <draft-ietf-rtgwg-mofrr.ad@ietf.org>, <rtgwg@ietf.org>
Subject: Telechat update notice: <draft-ietf-rtgwg-mofrr-06.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150416191938.19639.72633.idtracker@ietfa.amsl.com>
Date: Thu, 16 Apr 2015 12:19:38 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/eyZ0Jj4iM4n_c-VR5dwQgevHL_g>
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, 16 Apr 2015 19:19:47 -0000

Placed on agenda for telechat - 2015-05-14
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-rtgwg-mofrr/


From nobody Thu Apr 16 12:37:06 2015
Return-Path: <iesg-secretary@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 2CE9B1B3572; Thu, 16 Apr 2015 12:37:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 j7_k40jd9bkC; Thu, 16 Apr 2015 12:37:01 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DE1611B3569; Thu, 16 Apr 2015 12:37:01 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-rtgwg-mofrr-06.txt> (Multicast only Fast Re-Route) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20150416193701.4193.32587.idtracker@ietfa.amsl.com>
Date: Thu, 16 Apr 2015 12:37:01 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/-0OKo4DL734JXDblXh46jX2V7Tk>
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
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, 16 Apr 2015 19:37:04 -0000

The IESG has received a request from the Routing Area Working Group WG
(rtgwg) to consider the following document:
- 'Multicast only Fast Re-Route'
  <draft-ietf-rtgwg-mofrr-06.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-04-30. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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 document 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 file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-rtgwg-mofrr/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-rtgwg-mofrr/ballot/


The following IPR Declarations may be related to this I-D:

   http://datatracker.ietf.org/ipr/2378/
   http://datatracker.ietf.org/ipr/2332/
   http://datatracker.ietf.org/ipr/1127/




From nobody Thu Apr 16 12:37:16 2015
Return-Path: <ietf-secretariat-reply@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 3939A1B357E; Thu, 16 Apr 2015 12:37:12 -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 QlrnJmVHsC-w; Thu, 16 Apr 2015 12:37:05 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 791291B356E; Thu, 16 Apr 2015 12:37:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <draft-ietf-rtgwg-mofrr@ietf.org>, <rtgwg-chairs@ietf.org>, <draft-ietf-rtgwg-mofrr.shepherd@ietf.org>, <aretana@cisco.com>, <draft-ietf-rtgwg-mofrr.ad@ietf.org>, <rtgwg@ietf.org>
Subject: ID Tracker State Update Notice: <draft-ietf-rtgwg-mofrr-06.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150416193702.4193.64680.idtracker@ietfa.amsl.com>
Date: Thu, 16 Apr 2015 12:37:02 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/BtM_U21igxBNdrx7J1XACBLCsAk>
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, 16 Apr 2015 19:37:12 -0000

Last call has been made for draft-ietf-rtgwg-mofrr and state has been changed to In Last Call
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-rtgwg-mofrr/


From nobody Fri Apr 17 08:16:33 2015
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 C800B1B2BDA for <rtgwg@ietfa.amsl.com>; Fri, 17 Apr 2015 08:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 pPe-NxRUrYDL for <rtgwg@ietfa.amsl.com>; Fri, 17 Apr 2015 08:16:28 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52F951B2BD3 for <rtgwg@ietf.org>; Fri, 17 Apr 2015 08:16:28 -0700 (PDT)
Received: from omfeda05.si.francetelecom.fr (unknown [xx.xx.xx.198]) by omfeda10.si.francetelecom.fr (ESMTP service) with ESMTP id A89F63742EB; Fri, 17 Apr 2015 17:16:26 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfeda05.si.francetelecom.fr (ESMTP service) with ESMTP id 8FD8318004F; Fri, 17 Apr 2015 17:16:26 +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.0224.002; Fri, 17 Apr 2015 17:16:26 +0200
From: <bruno.decraene@orange.com>
To: Jeff Tantsura <jeff.tantsura@ericsson.com>
Subject: RE: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Thread-Topic: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Thread-Index: AQHQeGozBdo1pgIIQk2vMrK3UlMfNJ1QzIvA
Date: Fri, 17 Apr 2015 15:16:25 +0000
Message-ID: <18135_1429283786_553123CA_18135_4513_1_53C29892C857584299CBF5D05346208A0EBA5C42@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <D1553E65.9546D%jeff.tantsura@ericsson.com>
In-Reply-To: <D1553E65.9546D%jeff.tantsura@ericsson.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.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.4.17.145722
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/bq7m_qsLg_c1Mvfx60uyebHS0WE>
Cc: "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: Fri, 17 Apr 2015 15:16:32 -0000

Hi Jeff, Chris, all

Support.
Having different SPF-delays across the IGP domain increases micro-loops pro=
bability and/or duration. We don't need this, especially when the IGP is ex=
periencing instability (i.e. when SPF back-off algorithm kicks in). Hence h=
aving a common SPF back-off procedure is an improvement. IMHO it's a low co=
st one.

I'm not aware of IPR.

Thanks,
Bruno

> -----Original Message-----
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Jeff Tantsura
> Sent: Thursday, April 16, 2015 7:25 PM
> To: rtgwg@ietf.org
> Subject: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-
> statement and draft-decraene-rtgwg-backoff-algo
>=20
> Hi RTGWG,
>=20
> The authors have requested the RTGWG to adopt:
> draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-
> backoff-algo as working group documents.
>=20
> There was support during the last IETF meeting (92) in Dallas.
> Please indicate support or no-support by May 1st, 2015.
>=20
>=20
> If you are listed as a document author or contributor please respond to t=
his
> email stating of whether or not you are aware of any relevant IPR.
> The response needs to be sent to the RTGWG mailing list. The document will
> not advance to the next stage until a response has been received from each
> author and each individual that has contributed to the document.
>=20
>=20
> Thanks,
>=20
>=20
> Jeff & Chris
>=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 Apr 17 08:52:50 2015
Return-Path: <acee@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 0B5C41A876C for <rtgwg@ietfa.amsl.com>; Fri, 17 Apr 2015 08:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 XEsOtVHXvv-9 for <rtgwg@ietfa.amsl.com>; Fri, 17 Apr 2015 08:52:46 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D0161A8738 for <rtgwg@ietf.org>; Fri, 17 Apr 2015 08:52:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1336; q=dns/txt; s=iport; t=1429285962; x=1430495562; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=+2A3YWnip7mTZHOXBSHakmGgVA68eg0+tgP0CBRI2Sc=; b=eIMxDDxPOUJhPUmiDNaCLR8GEToTLeByZRch+XsOAAKhWCaBYq19vQ6u tvfnEo006s1BhhGZ7pmePyVMbjjOD2o0yVEsDs73s3bbkyNvme2U53nnz +yH/rL2Ive1IKwG3GAT78t4nQgUjGfLsBvg8IQsmQbbZIzA1JQN2dhxGj I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BYBACHKzFV/4QNJK1dgwxSXAWDEsMECYFFCoYDAhyBNTgUAQEBAQEBAX2EIQEBBAEBASAROgYVAgEIGgIfBwICAiULFRACBAESiCoNs1CVGAEBAQEBAQEBAQEBAQEBAQEBAQEVBIEhigiEGREBHjqCaIFFBZEiih6BHYM6hyKJESKCM4E8b4ELOX8BAQE
X-IronPort-AV: E=Sophos;i="5.11,595,1422921600"; d="scan'208";a="142204568"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-2.cisco.com with ESMTP; 17 Apr 2015 15:52:41 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t3HFqfS5032701 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 17 Apr 2015 15:52:41 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.120]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0195.001; Fri, 17 Apr 2015 10:52:41 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Jeff Tantsura <jeff.tantsura@ericsson.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Thread-Topic: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Thread-Index: AQHQeGozBdo1pgIIQk2vMrK3UlMfNJ1RbRmA
Date: Fri, 17 Apr 2015 15:52:40 +0000
Message-ID: <D156A48B.17F2C%acee@cisco.com>
References: <D1553E65.9546D%jeff.tantsura@ericsson.com>
In-Reply-To: <D1553E65.9546D%jeff.tantsura@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.152.198]
Content-Type: text/plain; charset="utf-8"
Content-ID: <B41C7BFDE6A4B449B196CDA851BC1E69@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/7MVsNBZAsKEI066O6-9SDczfyl0>
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, 17 Apr 2015 15:52:48 -0000

SSBzdXBwb3J0IGJvdGggZHJhZnRzLg0KVGhhbmtzLA0KQWNlZQ0KDQpPbiA0LzE2LzE1LCAxOjI0
IFBNLCAiSmVmZiBUYW50c3VyYSIgPGplZmYudGFudHN1cmFAZXJpY3Nzb24uY29tPiB3cm90ZToN
Cg0KPkhpIFJUR1dHLA0KPg0KPlRoZSBhdXRob3JzIGhhdmUgcmVxdWVzdGVkIHRoZSBSVEdXRyB0
byBhZG9wdDoNCj5kcmFmdC1saXRrb3dza2ktcnRnd2ctc3BmLXVsb29wLXBiLXN0YXRlbWVudCBh
bmQNCj5kcmFmdC1kZWNyYWVuZS1ydGd3Zy1iYWNrb2ZmLWFsZ28gYXMgd29ya2luZyBncm91cCBk
b2N1bWVudHMuDQo+DQo+VGhlcmUgd2FzIHN1cHBvcnQgZHVyaW5nIHRoZSBsYXN0IElFVEYgbWVl
dGluZyAoOTIpIGluIERhbGxhcy4NCj5QbGVhc2UgaW5kaWNhdGUgc3VwcG9ydCBvciBuby1zdXBw
b3J0IGJ5IE1heSAxc3QsIDIwMTUuDQo+DQo+DQo+SWYgeW91IGFyZSBsaXN0ZWQgYXMgYSBkb2N1
bWVudCBhdXRob3Igb3IgY29udHJpYnV0b3IgcGxlYXNlIHJlc3BvbmQgdG8NCj50aGlzIGVtYWls
IHN0YXRpbmcgb2Ygd2hldGhlciBvciBub3QgeW91IGFyZSBhd2FyZSBvZiBhbnkgcmVsZXZhbnQg
SVBSLg0KPlRoZSByZXNwb25zZSBuZWVkcyB0byBiZSBzZW50IHRvIHRoZSBSVEdXRyBtYWlsaW5n
IGxpc3QuIFRoZSBkb2N1bWVudCB3aWxsDQo+bm90IGFkdmFuY2UgdG8gdGhlIG5leHQgc3RhZ2Ug
dW50aWwgYSByZXNwb25zZSBoYXMgYmVlbiByZWNlaXZlZCBmcm9tIGVhY2gNCj5hdXRob3IgYW5k
IGVhY2ggaW5kaXZpZHVhbCB0aGF0IGhhcyBjb250cmlidXRlZCB0byB0aGUgZG9jdW1lbnQuDQo+
DQo+DQo+VGhhbmtzLA0KPg0KPg0KPkplZmYgJiBDaHJpcw0KPg0KPl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+cnRnd2cgbWFpbGluZyBsaXN0DQo+cnRn
d2dAaWV0Zi5vcmcNCj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3J0Z3dn
DQoNCg==


From nobody Mon Apr 20 08:31:39 2015
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 B4BC61B2EAF for <rtgwg@ietfa.amsl.com>; Mon, 20 Apr 2015 08:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 rNmSospB3Hyo for <rtgwg@ietfa.amsl.com>; Mon, 20 Apr 2015 08:31:37 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B2191B2BFE for <rtgwg@ietf.org>; Mon, 20 Apr 2015 08:31:37 -0700 (PDT)
Received: from omfeda07.si.francetelecom.fr (unknown [xx.xx.xx.200]) by omfeda14.si.francetelecom.fr (ESMTP service) with ESMTP id D44B72AC448; Mon, 20 Apr 2015 17:31:35 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.31]) by omfeda07.si.francetelecom.fr (ESMTP service) with ESMTP id AF842158078; Mon, 20 Apr 2015 17:31:35 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM22.corporate.adroot.infra.ftgroup ([fe80::8c90:f4e9:be28:2a1%19]) with mapi id 14.03.0224.002; Mon, 20 Apr 2015 17:31:35 +0200
From: <stephane.litkowski@orange.com>
To: Jeff Tantsura <jeff.tantsura@ericsson.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Thread-Topic: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Thread-Index: AQHQeGozBdo1pgIIQk2vMrK3UlMfNJ1WDUQg
Date: Mon, 20 Apr 2015 15:31:35 +0000
Message-ID: <17402_1429543895_55351BD7_17402_19728_1_9E32478DFA9976438E7A22F69B08FF921663B5C2@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <D1553E65.9546D%jeff.tantsura@ericsson.com>
In-Reply-To: <D1553E65.9546D%jeff.tantsura@ericsson.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.5]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.4.20.142418
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/6M6lM3k1F0Mvz-nHMScIQk9wSd4>
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, 20 Apr 2015 15:31:38 -0000

Hi,

I support both drafts.

I'm not aware of any IPR.

Stephane


-----Original Message-----
From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Jeff Tantsura
Sent: Thursday, April 16, 2015 19:25
To: rtgwg@ietf.org
Subject: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-stat=
ement and draft-decraene-rtgwg-backoff-algo

Hi RTGWG,

The authors have requested the RTGWG to adopt:
draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backo=
ff-algo as working group documents.

There was support during the last IETF meeting (92) in Dallas.
Please indicate support or no-support by May 1st, 2015.


If you are listed as a document author or contributor please respond to thi=
s email stating of whether or not you are aware of any relevant IPR.
The response needs to be sent to the RTGWG mailing list. The document will =
not advance to the next stage until a response has been received from each =
author and each individual that has contributed to the document.


Thanks,


Jeff & Chris

_______________________________________________
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 Mon Apr 20 09:49:05 2015
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 65C331A8720; Mon, 20 Apr 2015 09:49:03 -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 G-_l6Qcx26sX; Mon, 20 Apr 2015 09:49:02 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4499A1A8729; Mon, 20 Apr 2015 09:49:01 -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-bgp-routing-large-dc-02.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150420164901.10822.34791.idtracker@ietfa.amsl.com>
Date: Mon, 20 Apr 2015 09:49:01 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/-cz_z5-9dtzsXeHingN9Zf5shqU>
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, 20 Apr 2015 16:49:03 -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           : Use of BGP for routing in large-scale data centers
        Authors         : Petr Lapukhov
                          Ariff Premji
                          Jon Mitchell
	Filename        : draft-ietf-rtgwg-bgp-routing-large-dc-02.txt
	Pages           : 31
	Date            : 2015-04-20

Abstract:
   Some network operators build and operate data centers that support
   over one hundred thousand servers.  In this document, such data
   centers are referred to as "large-scale" to differentiate them from
   smaller infrastructures.  Environments of this scale have a unique
   set of network requirements with an emphasis on operational
   simplicity and network stability.  This document summarizes
   operational experience in designing and operating large-scale data
   centers using BGP as the only routing protocol.  The intent is to
   report on a proven and stable routing design that could be leveraged
   by others in the industry.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-bgp-routing-large-dc/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rtgwg-bgp-routing-large-dc-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-bgp-routing-large-dc-02


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 Tue Apr 21 10:38:47 2015
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 9E3ED1A87AF for <rtgwg@ietfa.amsl.com>; Tue, 21 Apr 2015 10:38:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 b3-MLseJbgMx for <rtgwg@ietfa.amsl.com>; Tue, 21 Apr 2015 10:38:43 -0700 (PDT)
Received: from estafeta21.imdea.org (maquina46.madrimasd.org [193.145.15.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3A751A877B for <rtgwg@ietf.org>; Tue, 21 Apr 2015 10:38:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by estafeta21.imdea.org (imdea mail daemon) with ESMTP id AEB841BA7D0; Tue, 21 Apr 2015 19:38:12 +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 mw9M5_ua1BbO; Tue, 21 Apr 2015 19:38:12 +0200 (CEST)
Received: from [10.141.126.9] (126.Red-176-83-225.dynamicIP.rima-tde.net [176.83.225.126]) (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 A54761BA7CD; Tue, 21 Apr 2015 19:38:02 +0200 (CEST)
References: <D1553E65.9546D%jeff.tantsura@ericsson.com> <17402_1429543895_55351BD7_17402_19728_1_9E32478DFA9976438E7A22F69B08FF921663B5C2@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Mime-Version: 1.0 (1.0)
In-Reply-To: <17402_1429543895_55351BD7_17402_19728_1_9E32478DFA9976438E7A22F69B08FF921663B5C2@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <48042F44-5172-4E7F-BDCB-C210F230ACB4@imdea.org>
X-Mailer: iPhone Mail (11D257)
From: Pierre Francois <pierre.francois@imdea.org>
Subject: Re: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Date: Tue, 21 Apr 2015 19:37:13 +0200
To: "<stephane.litkowski@orange.com>" <stephane.litkowski@orange.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/bkkG4SbZxrAqLHFrpsgIAQgD-Y8>
Cc: "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: Tue, 21 Apr 2015 17:38:45 -0000

+1

Sent from my iPhone

> On Apr 20, 2015, at 5:31 PM, <stephane.litkowski@orange.com> wrote:
>=20
> Hi,
>=20
> I support both drafts.
>=20
> I'm not aware of any IPR.
>=20
> Stephane
>=20
>=20
> -----Original Message-----
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Jeff Tantsura
> Sent: Thursday, April 16, 2015 19:25
> To: rtgwg@ietf.org
> Subject: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-sta=
tement and draft-decraene-rtgwg-backoff-algo
>=20
> Hi RTGWG,
>=20
> The authors have requested the RTGWG to adopt:
> draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-back=
off-algo as working group documents.
>=20
> There was support during the last IETF meeting (92) in Dallas.
> Please indicate support or no-support by May 1st, 2015.
>=20
>=20
> If you are listed as a document author or contributor please respond to th=
is email stating of whether or not you are aware of any relevant IPR.
> The response needs to be sent to the RTGWG mailing list. The document will=
 not advance to the next stage until a response has been received from each a=
uthor and each individual that has contributed to the document.
>=20
>=20
> Thanks,
>=20
>=20
> Jeff & Chris
>=20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>=20
> __________________________________________________________________________=
_______________________________________________
>=20
> Ce message et ses pieces jointes peuvent contenir des informations confide=
ntielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez rec=
u ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages e=
lectroniques 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 in=
formation 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 del=
ete 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


From nobody Wed Apr 22 02:03:46 2015
Return-Path: <hannes@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 513401B32BE for <rtgwg@ietfa.amsl.com>; Wed, 22 Apr 2015 02:03:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 YfRa_ozJOGbo for <rtgwg@ietfa.amsl.com>; Wed, 22 Apr 2015 02:03:44 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0132.outbound.protection.outlook.com [65.55.169.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FA8E1B32BB for <rtgwg@ietf.org>; Wed, 22 Apr 2015 02:03:43 -0700 (PDT)
Authentication-Results: ericsson.com; dkim=none (message not signed) header.d=none;
Received: from hannes-mba.local (193.110.55.10) by BLUPR05MB436.namprd05.prod.outlook.com (10.141.27.152) with Microsoft SMTP Server (TLS) id 15.1.136.25; Wed, 22 Apr 2015 09:03:42 +0000
Received: from hannes-mba.local (localhost [127.0.0.1]) by hannes-mba.local (Postfix) with ESMTP id 01FAE121863E; Wed, 22 Apr 2015 11:03:23 +0200 (CEST)
Message-ID: <553763DB.3050904@juniper.net>
Date: Wed, 22 Apr 2015 11:03:23 +0200
From: Hannes Gredler <hannes@juniper.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: <bruno.decraene@orange.com>, Jeff Tantsura <jeff.tantsura@ericsson.com>
Subject: Re: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
References: <D1553E65.9546D%jeff.tantsura@ericsson.com> <18135_1429283786_553123CA_18135_4513_1_53C29892C857584299CBF5D05346208A0EBA5C42@PEXCVZYM11.corporate.adroot.infra.ftgroup>
In-Reply-To: <18135_1429283786_553123CA_18135_4513_1_53C29892C857584299CBF5D05346208A0EBA5C42@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [193.110.55.10]
X-ClientProxiedBy: AM2PR09CA0080.eurprd09.prod.outlook.com (25.160.228.176) To BLUPR05MB436.namprd05.prod.outlook.com (10.141.27.152)
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR05MB436;
X-Microsoft-Antispam-PRVS: <BLUPR05MB4367C47BE85711B2F502602CBEE0@BLUPR05MB436.namprd05.prod.outlook.com>
X-Forefront-Antispam-Report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(51704005)(377454003)(24454002)(164054003)(52604005)(13464003)(479174004)(122856001)(47776003)(65956001)(40100003)(5001770100001)(62966003)(59896002)(65806001)(77096005)(77156002)(5890100001)(4001350100001)(64126003)(66066001)(19580395003)(76506005)(19580405001)(230783001)(83506001)(50466002)(92566002)(87266999)(2950100001)(65816999)(50986999)(76176999)(54356999)(46102003)(36756003)(122386002)(86362001)(15975445007)(87976001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR05MB436; H:hannes-mba.local; FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:BLUPR05MB436; BCL:0; PCL:0; RULEID:; SRVR:BLUPR05MB436; 
X-Forefront-PRVS: 0554B1F54F
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 22 Apr 2015 09:03:42.0635 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR05MB436
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/rMUk-sDTWeUF-d89x80V3lbcH_g>
Cc: "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: Wed, 22 Apr 2015 09:03:46 -0000

support for both drafts;

thanks for doing this - this is useful work !

/hannes

On 4/17/15 17:16, bruno.decraene@orange.com wrote:
> Hi Jeff, Chris, all
>
> Support.
> Having different SPF-delays across the IGP domain increases micro-loops probability and/or duration. We don't need this, especially when the IGP is experiencing instability (i.e. when SPF back-off algorithm kicks in). Hence having a common SPF back-off procedure is an improvement. IMHO it's a low cost one.
>
> I'm not aware of IPR.
>
> Thanks,
> Bruno
>
>> -----Original Message-----
>> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Jeff Tantsura
>> Sent: Thursday, April 16, 2015 7:25 PM
>> To: rtgwg@ietf.org
>> Subject: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-
>> statement and draft-decraene-rtgwg-backoff-algo
>>
>> Hi RTGWG,
>>
>> The authors have requested the RTGWG to adopt:
>> draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-
>> backoff-algo as working group documents.
>>
>> There was support during the last IETF meeting (92) in Dallas.
>> Please indicate support or no-support by May 1st, 2015.
>>
>>
>> If you are listed as a document author or contributor please respond to this
>> email stating of whether or not you are aware of any relevant IPR.
>> The response needs to be sent to the RTGWG mailing list. The document will
>> not advance to the next stage until a response has been received from each
>> author and each individual that has contributed to the document.
>>
>>
>> Thanks,
>>
>>
>> Jeff & Chris
>>
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
> _________________________________________________________________________________________________________________________
>
> 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.
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


From nobody Wed Apr 22 13:32:54 2015
Return-Path: <luis.tomotaki@verizon.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 81F671A8AB3 for <rtgwg@ietfa.amsl.com>; Wed, 22 Apr 2015 13:32:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 jPWRe45TrLFI for <rtgwg@ietfa.amsl.com>; Wed, 22 Apr 2015 13:32:51 -0700 (PDT)
Received: from omzsmtpe02.verizonbusiness.com (omzsmtpe02.verizonbusiness.com [199.249.25.209]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA68D1A8A7D for <rtgwg@ietf.org>; Wed, 22 Apr 2015 13:32:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1429734771; x=1461270771; h=from:to:date:subject:message-id:mime-version; bh=d1yfTzN/Zj2Lp2o3skVlejmT0UiYXv9M77RUaQNUCa0=; b=ayx/VFayT7mu5CYWpFCMIPuOkCZesqbmXgeZlztunn3suoxpuFPmWfIw Bm8xYCzRE2YzilMwbKM2ug4XNQnSQu+66KA5Ve8ch50jCJLYpfPD/cyNG C7iXQqZe0OE1zh26zbAqJp4hyCvyngaHjDZbM8un4igUuWCyewRVy6Yq3 Q=;
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi01.verizon.com) ([166.68.71.143]) by omzsmtpe02.verizonbusiness.com with ESMTP; 22 Apr 2015 20:32:48 +0000
From: "Tomotaki, Luis M" <luis.tomotaki@verizon.com>
X-IronPort-AV: E=Sophos; i="5.11,625,1422921600"; d="scan'208,217"; a="17075400"
Received: from fhdp1lumxc7hb05.verizon.com (HELO FHDP1LUMXC7HB05.us.one.verizon.com) ([166.68.59.192]) by fldsmtpi01.verizon.com with ESMTP; 22 Apr 2015 20:32:49 +0000
Received: from FHDP1LUMXC7V91.us.one.verizon.com ([166.68.240.155]) by FHDP1LUMXC7HB05.us.one.verizon.com ([166.68.59.192]) with mapi; Wed, 22 Apr 2015 16:32:47 -0400
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Wed, 22 Apr 2015 16:32:47 -0400
Subject: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Thread-Topic: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Thread-Index: AdB9O3yQdYAEE0o5S/m3hTnQsPeVEg==
Message-ID: <467340A77F13C944919805BFF3B8ACFC300586F86A@FHDP1LUMXC7V91.us.one.verizon.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_467340A77F13C944919805BFF3B8ACFC300586F86AFHDP1LUMXC7V9_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/5DVha0kt2DNRZV90ebDaTgcLNII>
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, 22 Apr 2015 20:32:53 -0000

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

Support for both drafts.


Luis Tomotaki (Verizon)

>> -----Original Message-----
>> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Jeff Tantsura
>> Sent: Thursday, April 16, 2015 7:25 PM
>> To: rtgwg@ietf.org
>> Subject: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-
>> statement and draft-decraene-rtgwg-backoff-algo
>>
>> Hi RTGWG,
>>
>> The authors have requested the RTGWG to adopt:
>> draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-
>> backoff-algo as working group documents.
>>
>> There was support during the last IETF meeting (92) in Dallas.
>> Please indicate support or no-support by May 1st, 2015.
>>
>>
>> If you are listed as a document author or contributor please respond to =
this
>> email stating of whether or not you are aware of any relevant IPR.
>> The response needs to be sent to the RTGWG mailing list. The document wi=
ll
>> not advance to the next stage until a response has been received from ea=
ch
>> author and each individual that has contributed to the document.
>>
>>
>> Thanks,
>>
>>
>> Jeff & Chris
>>
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
> _________________________________________________________________________=
________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confid=
entielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez re=
cu 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 o=
u falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged i=
nformation 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 bee=
n modified, changed or falsified.
> Thank you.
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

--_000_467340A77F13C944919805BFF3B8ACFC300586F86AFHDP1LUMXC7V9_
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=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 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:11.0pt;
	font-family:"Calibri","sans-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;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@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 lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:Courier'>Support for both drafts.<o:p></o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Co=
urier'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:10.0pt;font-family:Courier'><o:p>&nbsp;</o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:10.0pt;font-family:Courier'>Luis Tomotaki =
(Verizon)<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-siz=
e:10.0pt;font-family:Courier'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNor=
mal><span style=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt; -----Orig=
inal Message-----<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin=
-top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt; =
From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Jeff Tantsura<o:p>=
</o:p></span></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'><span sty=
le=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt; Sent: Thursday, April =
16, 2015 7:25 PM<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-=
top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt; T=
o: rtgwg@ietf.org<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin=
-top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt; =
Subject: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-<o:p=
></o:p></span></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'><span st=
yle=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt; statement and draft-d=
ecraene-rtgwg-backoff-algo<o:p></o:p></span></p><p class=3DMsoNormal style=
=3D'margin-top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'=
>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal style=3D'margin-t=
op:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt; Hi=
 RTGWG,<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-top:12.0p=
t'><span style=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt;<o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'><span sty=
le=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt; The authors have reque=
sted the RTGWG to adopt:<o:p></o:p></span></p><p class=3DMsoNormal style=3D=
'margin-top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'>&g=
t;&gt; draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgw=
g-<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'><s=
pan style=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt; backoff-algo as=
 working group documents.<o:p></o:p></span></p><p class=3DMsoNormal style=
=3D'margin-top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'=
>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal style=3D'margin-t=
op:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt; Th=
ere was support during the last IETF meeting (92) in Dallas.<o:p></o:p></sp=
an></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'><span style=3D'font=
-size:10.0pt;font-family:Courier'>&gt;&gt; Please indicate support or no-su=
pport by May 1st, 2015.<o:p></o:p></span></p><p class=3DMsoNormal style=3D'=
margin-top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'>&gt=
;&gt;<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal style=3D'margin-top:1=
2.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt;<o:p>&n=
bsp;</o:p></span></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'><span=
 style=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt; If you are listed =
as a document author or contributor please respond to this<o:p></o:p></span=
></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'><span style=3D'font-s=
ize:10.0pt;font-family:Courier'>&gt;&gt; email stating of whether or not yo=
u are aware of any relevant IPR.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Cou=
rier'>&gt;&gt; The response needs to be sent to the RTGWG mailing list. The=
 document will<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-to=
p:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt; not=
 advance to the next stage until a response has been received from each<o:p=
></o:p></span></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'><span st=
yle=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt; author and each indiv=
idual that has contributed to the document.<o:p></o:p></span></p><p class=
=3DMsoNormal style=3D'margin-top:12.0pt'><span style=3D'font-size:10.0pt;fo=
nt-family:Courier'>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal=
 style=3D'margin-top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Co=
urier'>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal style=3D'ma=
rgin-top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'>&gt;&=
gt; Thanks,<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-top:1=
2.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt;<o:p>&n=
bsp;</o:p></span></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'><span=
 style=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt;<o:p>&nbsp;</o:p></=
span></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'><span style=3D'fo=
nt-size:10.0pt;font-family:Courier'>&gt;&gt; Jeff &amp; Chris<o:p></o:p></s=
pan></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'><span style=3D'fon=
t-size:10.0pt;font-family:Courier'>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p c=
lass=3DMsoNormal style=3D'margin-top:12.0pt'><span style=3D'font-size:10.0p=
t;font-family:Courier'>&gt;&gt; ___________________________________________=
____<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'>=
<span style=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt; rtgwg mailing=
 list<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'=
><span style=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt; rtgwg@ietf.o=
rg<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'><s=
pan style=3D'font-size:10.0pt;font-family:Courier'>&gt;&gt; https://www.iet=
f.org/mailman/listinfo/rtgwg<o:p></o:p></span></p><p class=3DMsoNormal styl=
e=3D'margin-top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier=
'>&gt; ____________________________________________________________________=
_____________________________________________________<o:p></o:p></span></p>=
<p class=3DMsoNormal style=3D'margin-top:12.0pt'><span style=3D'font-size:1=
0.0pt;font-family:Courier'>&gt;<o:p>&nbsp;</o:p></span></p><p class=3DMsoNo=
rmal style=3D'margin-top:12.0pt'><span style=3D'font-size:10.0pt;font-famil=
y:Courier'>&gt; Ce message et ses pieces jointes peuvent contenir des infor=
mations confidentielles ou privilegiees et ne doivent donc<o:p></o:p></span=
></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'><span style=3D'font-s=
ize:10.0pt;font-family:Courier'>&gt; pas etre diffuses, exploites ou copies=
 sans autorisation. Si vous avez recu ce message par erreur, veuillez le si=
gnaler<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-top:12.0pt=
'><span style=3D'font-size:10.0pt;font-family:Courier'>&gt; a l'expediteur =
et le detruire ainsi que les pieces jointes. Les messages electroniques eta=
nt susceptibles d'alteration,<o:p></o:p></span></p><p class=3DMsoNormal sty=
le=3D'margin-top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courie=
r'>&gt; Orange decline toute responsabilite si ce message a ete altere, def=
orme ou falsifie. Merci.<o:p></o:p></span></p><p class=3DMsoNormal style=3D=
'margin-top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'>&g=
t;<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal style=3D'margin-top:12.0=
pt'><span style=3D'font-size:10.0pt;font-family:Courier'>&gt; This message =
and its attachments may contain confidential or privileged information that=
 may be protected by law;<o:p></o:p></span></p><p class=3DMsoNormal style=
=3D'margin-top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'=
>&gt; they should not be distributed, used or copied without authorisation.=
<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'><spa=
n style=3D'font-size:10.0pt;font-family:Courier'>&gt; If you have received =
this email in error, please notify the sender and delete this message and i=
ts attachments.<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-t=
op:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'>&gt; As ema=
ils may be altered, Orange is not liable for messages that have been modifi=
ed, changed or falsified.<o:p></o:p></span></p><p class=3DMsoNormal style=
=3D'margin-top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'=
>&gt; Thank you.<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-=
top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'>&gt;<o:p>&=
nbsp;</o:p></span></p><p class=3DMsoNormal style=3D'margin-top:12.0pt'><spa=
n style=3D'font-size:10.0pt;font-family:Courier'>&gt; _____________________=
__________________________<o:p></o:p></span></p><p class=3DMsoNormal style=
=3D'margin-top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'=
>&gt; rtgwg mailing list<o:p></o:p></span></p><p class=3DMsoNormal style=3D=
'margin-top:12.0pt'><span style=3D'font-size:10.0pt;font-family:Courier'>&g=
t; rtgwg@ietf.org<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'=
font-size:10.0pt;font-family:Courier'>&gt; https://www.ietf.org/mailman/lis=
tinfo/rtgwg</span><o:p></o:p></p></div></body></html>=

--_000_467340A77F13C944919805BFF3B8ACFC300586F86AFHDP1LUMXC7V9_--


From nobody Wed Apr 22 20:15:02 2015
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 9F5691B2E85; Wed, 22 Apr 2015 20:15:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level: 
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 WZ4aNTW5itve; Wed, 22 Apr 2015 20:15:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id A4E3A1B2E72; Wed, 22 Apr 2015 20:14:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8505118046D; Wed, 22 Apr 2015 20:13:32 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7490 on Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150423031332.8505118046D@rfc-editor.org>
Date: Wed, 22 Apr 2015 20:13:32 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/Le48F-ITfVTXKZGkfPo2660XSqk>
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: Thu, 23 Apr 2015 03:15:01 -0000

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

        
        RFC 7490

        Title:      Remote Loop-Free Alternate (LFA) Fast 
                    Reroute (FRR) 
        Author:     S. Bryant, C. Filsfils,
                    S. Previdi, M. Shand, N. So
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2015
        Mailbox:    stbryant@cisco.com, 
                    cfilsfil@cisco.com, 
                    sprevidi@cisco.com,
                    imc.shand@gmail.com, 
                    ningso@vinci-systems.com
        Pages:      29
        Characters: 66207
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-remote-lfa-11.txt

        URL:        https://www.rfc-editor.org/info/rfc7490

This document describes an extension to the basic IP fast reroute
mechanism, described in RFC 5286, that provides additional backup
connectivity for point-to-point link failures when none can be
provided by the basic mechanisms.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

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

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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 Fri Apr 24 10:55:43 2015
Return-Path: <uma.chunduri@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 698711ACE09 for <rtgwg@ietfa.amsl.com>; Fri, 24 Apr 2015 10:55:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 CusUe5TFUroo for <rtgwg@ietfa.amsl.com>; Fri, 24 Apr 2015 10:55:39 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A24181ACDA6 for <rtgwg@ietf.org>; Fri, 24 Apr 2015 10:55:39 -0700 (PDT)
X-AuditID: c6180641-f790b6d000004359-47-553a201caa90
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 57.24.17241.C102A355; Fri, 24 Apr 2015 12:51:08 +0200 (CEST)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.03.0210.002; Fri, 24 Apr 2015 13:55:36 -0400
From: Uma Chunduri <uma.chunduri@ericsson.com>
To: Jeff Tantsura <jeff.tantsura@ericsson.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Thread-Topic: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Thread-Index: AQHQeGozBdo1pgIIQk2vMrK3UlMfNJ1cfqhQ
Date: Fri, 24 Apr 2015 17:55:35 +0000
Message-ID: <1B502206DFA0C544B7A60469152008633F659C48@eusaamb105.ericsson.se>
References: <D1553E65.9546D%jeff.tantsura@ericsson.com>
In-Reply-To: <D1553E65.9546D%jeff.tantsura@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.9]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrBLMWRmVeSWpSXmKPExsUyuXSPn66MglWowYReVYsLb34zOzB6LFny kymAMYrLJiU1J7MstUjfLoErY9nqwoJJnBWvrv5kaWA8zt7FyMkhIWAi8fjjNmYIW0ziwr31 bCC2kMBRRolDM7W7GLmA7OWMEktufmUBSbAJ6El8nPoTqJmDQ0QgWOJTZz5IWFigTuLm719g JSIC9RJrHh5mhbCNJN78+Q5mswioSixonsoIYvMK+Eqs2NrDBLHLXOLQsptg93AKWEg8m/8W bA4j0D3fT60Bq2EWEJe49WQ+E8SdAhJL9pyHullU4uXjf6wQtqLEvv7p7BD1OhILdn9ig7C1 JZYtfM0MsVdQ4uTMJywTGEVnIRk7C0nLLCQts5C0LGBkWcXIUVqcWpabbmS4iREY9Mck2Bx3 MC74ZHmIUYCDUYmHNyHbMlSINbGsuDL3EKM0B4uSOG/ZlYMhQgLpiSWp2ampBalF8UWlOanF hxiZODilGhgDf3GpFXvkiD9v6kiumHDlTsxCBs40ns+zV5azqu9wv8X0IW3uq/SMR2dcVFYd W7jaZIf6lSdbv0SusGwIWsOmZPE/ybstM8ViRvLUsOnlPhGBuxY6+LG8Os+2Re7w74kPFkfN v9sanbye2+vwUrPTcWFaz9ZMKuCfapHPbF53t/rVIzb70otKLMUZiYZazEXFiQA5hmr5WwIA AA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/-59ApT758SV2OyAVPCqtP3sqMRY>
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, 24 Apr 2015 17:55:41 -0000

Support (for both the drafts).

--
Uma C.

-----Original Message-----
From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Jeff Tantsura
Sent: Thursday, April 16, 2015 10:25 AM
To: rtgwg@ietf.org
Subject: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-stat=
ement and draft-decraene-rtgwg-backoff-algo

Hi RTGWG,

The authors have requested the RTGWG to adopt:
draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backo=
ff-algo as working group documents.

There was support during the last IETF meeting (92) in Dallas.
Please indicate support or no-support by May 1st, 2015.


If you are listed as a document author or contributor please respond to thi=
s email stating of whether or not you are aware of any relevant IPR.
The response needs to be sent to the RTGWG mailing list. The document will =
not advance to the next stage until a response has been received from each =
author and each individual that has contributed to the document.


Thanks,


Jeff & Chris

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


From nobody Tue Apr 28 00:13:22 2015
Return-Path: <anil.sn@huawei.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 6E52A1A19E3; Tue, 28 Apr 2015 00:13:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 DuKXhrAaT_Ze; Tue, 28 Apr 2015 00:13:16 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41CD01A0A6A; Tue, 28 Apr 2015 00:13:15 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BRX25536; Tue, 28 Apr 2015 07:13:13 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 28 Apr 2015 08:13:12 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.135]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Tue, 28 Apr 2015 15:13:00 +0800
From: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>
To: "akatlas@juniper.net" <akatlas@juniper.net>, "shraddha@juniper.net" <shraddha@juniper.net>, "cbowers@juniper.net" <cbowers@juniper.net>, "jeff.tantsura@ericsson.com" <jeff.tantsura@ericsson.com>, Lizhenbin <lizhenbin@huawei.com>, "rkebler@juniper.net" <rkebler@juniper.net>, "Gabor.Sandor.Enyedi@ericsson.com" <Gabor.Sandor.Enyedi@ericsson.com>, "Andras.Csaszar@ericsson.com" <Andras.Csaszar@ericsson.com>
Subject: [MRT] draft-ietf-ospf-mrt-00 & draft-ietf-rtgwg-mrt-frr-architecture-05 [OSPF Extensions to Support Maximally Redundant Trees & An Architecture for IP/LDP Fast-Reroute Using Maximally Redundant Trees]
Thread-Topic: [MRT] draft-ietf-ospf-mrt-00 & draft-ietf-rtgwg-mrt-frr-architecture-05 [OSPF Extensions to Support Maximally Redundant Trees & An Architecture for IP/LDP Fast-Reroute Using Maximally Redundant Trees]
Thread-Index: AdCBgr+0YN14KM3+QRezBqe2zf8iQQ==
Date: Tue, 28 Apr 2015 07:12:59 +0000
Message-ID: <327562D94EA7BF428CD805F338C31EF04FB394E0@nkgeml512-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.212.150]
Content-Type: multipart/alternative; boundary="_000_327562D94EA7BF428CD805F338C31EF04FB394E0nkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/G4O8UHeSeKeV8lcnrgkEHt6wA9k>
Cc: Rajeshmv <rajeshmv@huawei.com>, OSPF WG List <ospf@ietf.org>, "Wunan \(Eric\)" <eric.wu@huawei.com>, Dhruv Dhody <dhruv.dhody@huawei.com>, Kalyankumar Asangi <kalyana@huawei.com>, "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: Tue, 28 Apr 2015 07:13:18 -0000

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

Hi Authors,

     I feel MRT-RED and MRT-BLUE MT-ID should be per MT.
When MRT protection is desired on the network with multiple MT, How do we h=
ave a unique MRT-BLUE and MRT-RED MT-ID since MT-ID is a global to system?
Finalizing on MT-ID values for Red and Blue per MT is a open question I fee=
l :)
Please let me know your opinion.

We need following changes in OSPF extension on MRT if we desired to support=
 MRT on multiple MT network.
5.3<https://tools.ietf.org/html/draft-ietf-ospf-mrt-00#section-5.3>.  MRT P=
rofile TLV in Router Information LSA
       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |              Type             |           Length              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | Profile ID(1) |GADAG Priority | Primary MT-ID |   Reserved    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                         ..............                        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | Profile ID(n) |GADAG Priority | Primary MT-ID |   Reserved    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      TYPE:  TBA-MRT-OSPF-1 (To Be Allocated by IANA)
      LENGTH: 4 * (number of Profiles)
      Profile ID :  1 byte
             GADAG Priority: 1 byte
             Primary MT-ID : 1 byte


6.1<https://tools.ietf.org/html/draft-ietf-ospf-mrt-00#section-6.1>.  MRT-I=
neligible Link sub-TLV

       0                   1                   2                   3

       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      |              Type             |          Length               |

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | Primary MT-ID |                   Reserved                    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+





      TYPE:  TBA-MRT-OSPF-2 in OSPFv2 Extended Link TLV

             TBA-MRT-OSPF-3 in OSPFv3 Router-Link TLV

             (To Be Allocated by IANA)

      LENGTH: 4 * (number of MT's on which this link is Ineligible)

      Primary MT-ID : 1 byte


                        MRT-Ineligible Link sub-TLV


Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel



--_000_327562D94EA7BF428CD805F338C31EF04FB394E0nkgeml512mbxchi_
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 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h3
	{mso-style-priority:9;
	mso-style-link:"Heading 3 Char";
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-line-height-alt:0pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.Heading3Char
	{mso-style-name:"Heading 3 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 3";
	font-family:"Courier New";
	font-weight:bold;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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 lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
Hi Authors,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
<o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp; I feel MRT-RED and MRT-BLUE MT-ID should be per MT=
.
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span style=3D"font-fam=
ily:&quot;Courier New&quot;">When MRT protection is desired on the network =
with multiple MT, How do we have a unique MRT-BLUE and MRT-RED MT-ID since =
MT-ID is a global to system?<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Courier New&quot;">Finalizing on MT-ID values fo=
r Red and Blue per MT is a open question I feel
</span><span style=3D"font-size:12.0pt;font-family:Wingdings">J</span><span=
 style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;">
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Courier New&quot;">Please let me know your opini=
on.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Courier New&quot;">We need following changes in =
OSPF extension on MRT if we desired to support MRT on multiple MT network.<=
o:p></o:p></span></p>
<h3 style=3D"page-break-before:always"><a name=3D"section-5.3"></a><a href=
=3D"https://tools.ietf.org/html/draft-ietf-ospf-mrt-00#section-5.3"><span l=
ang=3D"EN" style=3D"color:black;text-decoration:none">5.3</span></a><span l=
ang=3D"EN">.&nbsp; MRT Profile TLV in Router Information
 LSA<o:p></o:p></span></h3>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4=
 5 6 7 8 9 0 1<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&=
#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43=
;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.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; Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&=
#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43=
;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; | Profile ID(1) |GADAG Priority
<span style=3D"color:#00B050">| Primary MT-ID | &nbsp;&nbsp;Reserved&nbsp;&=
nbsp;&nbsp; |<o:p></o:p></span></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&=
#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43=
;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.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;&nb=
sp;&nbsp;&nbsp; ..............&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&=
#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43=
;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; | Profile ID(n) |GADAG Priority
<span style=3D"color:#00B050">| Primary MT-ID | &nbsp;&nbsp;Reserved&nbsp;&=
nbsp;&nbsp; |<o:p></o:p></span></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&=
#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43=
;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;=
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; TYPE:&nbsp; TBA-MRT-OSPF-1 (To Be Allocated by IANA)<o:=
p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; LENGTH: 4 * (number of Profiles)<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; Profile ID :&nbsp; 1 byte<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"font-size:12.0pt;font-fam=
ily:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nb=
sp; &nbsp;&nbsp;&nbsp;GADAG Priority: 1 byte<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"font-size:12.0pt;font-fam=
ily:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nb=
sp; &nbsp;&nbsp;&nbsp;Primary MT-ID : 1 byte<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"font-size:12.0pt;font-fam=
ily:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
</span><span lang=3D"EN" style=3D"font-family:&quot;Courier New&quot;"><o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
<o:p>&nbsp;</o:p></span></p>
<h3 style=3D"page-break-before:always"><a name=3D"section-6.1"></a><a href=
=3D"https://tools.ietf.org/html/draft-ietf-ospf-mrt-00#section-6.1"><span l=
ang=3D"EN" style=3D"color:black;text-decoration:none">6.1</span></a><span l=
ang=3D"EN">.&nbsp; MRT-Ineligible Link sub-TLV<o:p></o:p></span></h3>
<pre style=3D"page-break-before:always"><span lang=3D"EN">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7=
 8 9 0 1<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN">&nbsp;&nbsp; &nbs=
p;&nbsp;&nbsp;&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&=
#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43=
;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<o:p></o:p></s=
pan></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; |<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&=
#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43=
;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<o:p></o:p></s=
pan></pre>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;
<span style=3D"color:#00B050">|</span> <span style=3D"color:#00B050">Primar=
y MT-ID | &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Reserved&nbsp;&nbsp;&nbsp; &nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&=
nbsp;&nbsp;|<o:p></o:p></span></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&=
#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43=
;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<o:p></o=
:p></span></p>
<pre style=3D"page-break-before:always"><span lang=3D"EN"><o:p>&nbsp;</o:p>=
</span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN"><o:p>&nbsp;</o:p>=
</span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; TYPE:&nbsp; TBA-MRT-OSPF-2 in OSPFv2 Extended Link TLV<o:p></=
o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TBA-MRT-OSPF-3 in O=
SPFv3 Router-Link TLV<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (To Be Allocated by=
 IANA)<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; LENGTH: 4 * (number of MT&#8217;s on which this link is Ineli=
gible)<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; Primary MT-ID : 1 byte<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN"><o:p>&nbsp;</o:p>=
</span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"font-family:&quot;Courier=
 New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 MRT-Ineligible Link sub-TLV</span><span style=3D"font-family:&quot;Courier=
 New&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
<o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
<o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
Thanks &amp; Regards<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
Anil S N<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
<o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&#8220;Be liberal in what you accept, and conservative in what you send&#82=
21; - Jon Postel<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
<o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
<o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_327562D94EA7BF428CD805F338C31EF04FB394E0nkgeml512mbxchi_--


From nobody Tue Apr 28 05:01:49 2015
Return-Path: <maho@nic.dtag.de>
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 9DCD71A8AA6 for <rtgwg@ietfa.amsl.com>; Tue, 28 Apr 2015 05:01:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.489
X-Spam-Level: ***
X-Spam-Status: No, score=3.489 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, RCVD_IN_BL_SPAMCOP_NET=1.347, RDNS_NONE=0.793] 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 hHOuYl4QVhnB for <rtgwg@ietfa.amsl.com>; Tue, 28 Apr 2015 05:01:47 -0700 (PDT)
Received: from owl2.lab.dtag.de (unknown [194.25.1.238]) by ietfa.amsl.com (Postfix) with ESMTP id C87C31A88AC for <rtgwg@ietf.org>; Tue, 28 Apr 2015 05:01:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by owl2.lab.dtag.de (Postfix) with ESMTP id 5E42CC01D4 for <rtgwg@ietf.org>; Tue, 28 Apr 2015 14:01:45 +0200 (CEST)
Received: from Martins-MacBook-Air.local (unknown [85.29.8.182]) by owl2.lab.dtag.de (Postfix) with ESMTPSA id 2FA98C019B for <rtgwg@ietf.org>; Tue, 28 Apr 2015 14:01:45 +0200 (CEST)
Message-ID: <553F76A8.5080705@nic.dtag.de>
Date: Tue, 28 Apr 2015 15:01:44 +0300
From: Martin Horneffer <maho@nic.dtag.de>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
References: <D1553E65.9546D%jeff.tantsura@ericsson.com>
In-Reply-To: <D1553E65.9546D%jeff.tantsura@ericsson.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/gjPP-totuNmBA_3GEUskiq14NzM>
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: Tue, 28 Apr 2015 12:01:48 -0000

Full support for adoption of both drafts from my side!

With all the optimization in IGPs we got during the last decade, but 
also the increase of availability and performance requirements towards a 
converged IP backbone, this is in my opinion the next step for a better 
IP backbone that we can do.

Best regards, Martin


Am 16.04.15 um 20:24 schrieb Jeff Tantsura:
> Hi RTGWG,
>
> The authors have requested the RTGWG to adopt:
> draft-litkowski-rtgwg-spf-uloop-pb-statement and
> draft-decraene-rtgwg-backoff-algo as working group documents.
>
> There was support during the last IETF meeting (92) in Dallas.
> Please indicate support or no-support by May 1st, 2015.
>
>
> If you are listed as a document author or contributor please respond to
> this email stating of whether or not you are aware of any relevant IPR.
> The response needs to be sent to the RTGWG mailing list. The document will
> not advance to the next stage until a response has been received from each
> author and each individual that has contributed to the document.
>
>
> Thanks,
>
>
> Jeff & Chris
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>


From nobody Wed Apr 29 02:55:12 2015
Return-Path: <sprevidi@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 90C3C1A90C6 for <rtgwg@ietfa.amsl.com>; Wed, 29 Apr 2015 02:55:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 e3cWsDrOawAP for <rtgwg@ietfa.amsl.com>; Wed, 29 Apr 2015 02:55:09 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AB8C1A1B5E for <rtgwg@ietf.org>; Wed, 29 Apr 2015 02:55:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1022; q=dns/txt; s=iport; t=1430301309; x=1431510909; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=daQly/C+pxZEfLm2MQBKg2cxZjbhCoJvNjxLjbu8NXo=; b=gUPcWt/MA4mhZJUMwk9/eOSg5RzGrq1UvI3OCFG/dGHltgnwxA9TKXVn TzOfjWw+49LbHy+RIXBGqOg5Fk5x8TFELwaPiFlQsNPpjc6Vpnrj+kDKQ 0mk9evRXABreNzNB4R3qamCX86Z0Lque63j17uJQ0pSHQN0LUIXtlJyoe k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B5BQDEqUBV/4wNJK1cgwxTXAXFE4I4CoYEAoE9TAEBAQEBAYELhCEBAQMBAQEBNzQGBQULAgEINgULJwslAgQOBYgjCA3GeQEBAQEBAQEBAQEBAQEBAQEBAQEBARMEiziEIhEBHjMHgxeBFgWRaopIAYEig0mHU4k5I4I4gTxvgQs5gQEBAQE
X-IronPort-AV: E=Sophos;i="5.11,670,1422921600"; d="scan'208";a="412540911"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-1.cisco.com with ESMTP; 29 Apr 2015 09:55:08 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t3T9t80p015591 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 Apr 2015 09:55:08 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.245]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0195.001; Wed, 29 Apr 2015 04:55:08 -0500
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Jeff Tantsura <jeff.tantsura@ericsson.com>
Subject: Re: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Thread-Topic: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Thread-Index: AQHQgmKT1UmiwerD1UexvMCR1nujog==
Date: Wed, 29 Apr 2015 09:55:08 +0000
Message-ID: <EAE35640-EF4D-46A8-985F-AB41CFCBAA66@cisco.com>
References: <D1553E65.9546D%jeff.tantsura@ericsson.com>
In-Reply-To: <D1553E65.9546D%jeff.tantsura@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.147.74.82]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E8BD7688A036974F85834F1754FC18F5@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/4y5tuqQb_KmEFZnpUyTm8bSC1xg>
Cc: "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: Wed, 29 Apr 2015 09:55:10 -0000

support on both drafts.
s.


On Apr 16, 2015, at 7:24 PM, Jeff Tantsura <jeff.tantsura@ericsson.com> wro=
te:

> Hi RTGWG,
>=20
> The authors have requested the RTGWG to adopt:
> draft-litkowski-rtgwg-spf-uloop-pb-statement and
> draft-decraene-rtgwg-backoff-algo as working group documents.
>=20
> There was support during the last IETF meeting (92) in Dallas.
> Please indicate support or no-support by May 1st, 2015.
>=20
>=20
> If you are listed as a document author or contributor please respond to
> this email stating of whether or not you are aware of any relevant IPR.
> The response needs to be sent to the RTGWG mailing list. The document wil=
l
> not advance to the next stage until a response has been received from eac=
h
> author and each individual that has contributed to the document.
>=20
>=20
> Thanks,
>=20
>=20
> Jeff & Chris
>=20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


From nobody Thu Apr 30 02:47:51 2015
Return-Path: <mach.chen@huawei.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 3A83E1ACD8B for <rtgwg@ietfa.amsl.com>; Thu, 30 Apr 2015 02:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Nu-BRwCaPBgU for <rtgwg@ietfa.amsl.com>; Thu, 30 Apr 2015 02:47:48 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1626E1A8A8F for <rtgwg@ietf.org>; Thu, 30 Apr 2015 02:47:47 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BVM89736; Thu, 30 Apr 2015 09:47:46 +0000 (GMT)
Received: from SZXEMA413-HUB.china.huawei.com (10.82.72.72) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 30 Apr 2015 10:47:46 +0100
Received: from SZXEMA510-MBX.china.huawei.com ([169.254.3.219]) by SZXEMA413-HUB.china.huawei.com ([10.82.72.72]) with mapi id 14.03.0158.001; Thu, 30 Apr 2015 17:47:20 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Jeff Tantsura <jeff.tantsura@ericsson.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Thread-Topic: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backoff-algo
Thread-Index: AQHQeGozBdo1pgIIQk2vMrK3UlMfNJ1k2pxA
Date: Thu, 30 Apr 2015 09:47:18 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE28B4252E9@SZXEMA510-MBX.china.huawei.com>
References: <D1553E65.9546D%jeff.tantsura@ericsson.com>
In-Reply-To: <D1553E65.9546D%jeff.tantsura@ericsson.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.102.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/N6bWtlw5WNy6hDZuKlkjgURYEGg>
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, 30 Apr 2015 09:47:50 -0000

I have read the drafts and support both.

Best regards,
Mach

-----Original Message-----
From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Jeff Tantsura
Sent: Friday, April 17, 2015 1:25 AM
To: rtgwg@ietf.org
Subject: Request for WG adoption of draft-litkowski-rtgwg-spf-uloop-pb-stat=
ement and draft-decraene-rtgwg-backoff-algo

Hi RTGWG,

The authors have requested the RTGWG to adopt:
draft-litkowski-rtgwg-spf-uloop-pb-statement and draft-decraene-rtgwg-backo=
ff-algo as working group documents.

There was support during the last IETF meeting (92) in Dallas.
Please indicate support or no-support by May 1st, 2015.


If you are listed as a document author or contributor please respond to thi=
s email stating of whether or not you are aware of any relevant IPR.
The response needs to be sent to the RTGWG mailing list. The document will =
not advance to the next stage until a response has been received from each =
author and each individual that has contributed to the document.


Thanks,


Jeff & Chris

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

