
From nobody Tue Feb  3 01:24:54 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 F149B1A005D; Tue,  3 Feb 2015 01:24:52 -0800 (PST)
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 GX9vSkTLLBbD; Tue,  3 Feb 2015 01:24:51 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E1DF61A0032; Tue,  3 Feb 2015 01:24:51 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-rtgwg-mofrr-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150203092451.4489.97042.idtracker@ietfa.amsl.com>
Date: Tue, 03 Feb 2015 01:24:51 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/vjiAawCQnn3MH_DUkFOgZSiwV9E>
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Feb 2015 09:24:53 -0000

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

        Title           : Multicast only Fast Re-Route
        Authors         : Apoorva Karan
                          Clarence Filsfils
                          IJsbrand Wijnands
                          Bruno Decraene
	Filename        : draft-ietf-rtgwg-mofrr-05.txt
	Pages           : 15
	Date            : 2015-02-03

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 IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-mofrr/

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

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


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

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


From nobody Fri Feb  6 02:01:17 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 8CD941A1B1D; Fri,  6 Feb 2015 02:01:14 -0800 (PST)
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 F3GCFGQ_sti4; Fri,  6 Feb 2015 02:01:13 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 65C3A1A024C; Fri,  6 Feb 2015 02:01:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-rtgwg-mofrr-06.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150206100113.29116.33970.idtracker@ietfa.amsl.com>
Date: Fri, 06 Feb 2015 02:01:13 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/pRThsxkiHu_EI9lE44W_1Vdun9s>
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2015 10:01:14 -0000

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

        Title           : Multicast only Fast Re-Route
        Authors         : Apoorva Karan
                          Clarence Filsfils
                          IJsbrand Wijnands
                          Bruno Decraene
	Filename        : draft-ietf-rtgwg-mofrr-06.txt
	Pages           : 14
	Date            : 2015-02-06

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 IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-mofrr/

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

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


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

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


From nobody Wed Feb 11 00:43:15 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 DF1741A037A; Wed, 11 Feb 2015 00:43:07 -0800 (PST)
X-Quarantine-ID: <KAVyaSPCcY1t>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): References: ...@OPEXCLILM34.corporate.adroot.infra.ftgroup>\n 
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 KAVyaSPCcY1t; Wed, 11 Feb 2015 00:43:03 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3DCA1A036C; Wed, 11 Feb 2015 00:43:02 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id AB7113B4503; Wed, 11 Feb 2015 09:43:01 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.30]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 82CE94C066; Wed, 11 Feb 2015 09:43:01 +0100 (CET)
Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.53]) by OPEXCLILH02.corporate.adroot.infra.ftgroup ([10.114.31.30]) with mapi id 14.03.0224.002; Wed, 11 Feb 2015 09:43:01 +0100
From: <stephane.litkowski@orange.com>
To: "isis-wg@ietf.org list (isis-wg@ietf.org)" <isis-wg@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: [mpls] Survey for YANG model design : routing protocols CLI implementation
Thread-Topic: [mpls] Survey for YANG model design : routing protocols CLI implementation
Thread-Index: AdBFLLfJ87T7mg7qSBKOVExsw2JGuwAqVntQAAAnGkA=
Date: Wed, 11 Feb 2015 08:43:00 +0000
Message-ID: <7138_1423644181_54DB1615_7138_3898_1_9E32478DFA9976438E7A22F69B08FF920C7A12CC@OPEXCLILM34.corporate.adroot.infra.ftgroup>
References: <12023_1423571161_54D9F8D8_12023_1801_1_9E32478DFA9976438E7A22F69B08FF920C7A0F1A@OPEXCLILM34.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: multipart/related; boundary="_004_9E32478DFA9976438E7A22F69B08FF920C7A12CCOPEXCLILM34corp_"; type="multipart/alternative"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.2.11.73029
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/Su5p4_D3r3fnqgXlv9X0SI1efAQ>
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, 11 Feb 2015 08:43:08 -0000

--_004_9E32478DFA9976438E7A22F69B08FF920C7A12CCOPEXCLILM34corp_
Content-Type: multipart/alternative;
	boundary="_000_9E32478DFA9976438E7A22F69B08FF920C7A12CCOPEXCLILM34corp_"


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


From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of stephane.litkowski@o=
range.com<mailto:stephane.litkowski@orange.com>
Sent: Tuesday, February 10, 2015 13:26
To: ospf@ietf.org<mailto:ospf@ietf.org>; isis-wg@ietf.org<mailto:isis-wg@ie=
tf.org> list (isis-wg@ietf.org<mailto:isis-wg@ietf.org>); mpls@ietf.org<mai=
lto:mpls@ietf.org>; idr@ietf.org<mailto:idr@ietf.org>; rtgwg@ietf.org<mailt=
o:rtgwg@ietf.org>
Cc: Rtg-yang-coord@ietf.org<mailto:Rtg-yang-coord@ietf.org>
Subject: [mpls] Survey for YANG model design : routing protocols CLI implem=
entation
Importance: High

Hi Folks,

A lot of us are currently working on Yang model drafts. In the framework of=
 routing protocols related drafts, we have some discussion regarding how to=
 model the configuration of routing protocols and
especially do it need to be routing-instance centric or protocol centric. T=
his is a cross protocol discussion, as we would like to apply the same desi=
gn to all.

Example of routing-instance centric CLI : (Typically Juniper, ALU)
routing-instance R1 {
                protocol isis {};
                protocol ospf {};
                protocol ldp {};
}
routing-instance R2 {
                protocol isis {};
                protocol ospf {};
                protocol ldp {};
}

Example of protocol centric CLI : (Typically CISCO)
protocol isis {
routing-instance R1 {}
routing-instance R2 {}
}
protocol ospf {
routing-instance R1 {}
routing-instance R2 {}
}



In order to decide how to progress on this major design point, one point  i=
s to evaluate current implementations and how many are routing-instance cen=
tric and protocol centric. The famous implementations are well known, but w=
e would like to have a more global view. This metric would be one among oth=
ers.

In order to help us to do this inventory, could you please respond unicast =
to me, if you are an implementor and you have an implementation of a routin=
g-protocol (ISIS,OSPF,RIP,BGP, PIM ... but also MPLS-TE, LDP, RSVP ...) and=
 in this case, what is your CLI flavor ?

Please use this sample format, so it would be easier for me to aggregate :
(If you own multiple implementations, you can fill multiple lines.)


Vendor

OS

Protocol Centric

VRF centric

Cisco

IOS/IOS-XE

X





Thanks for your help !


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/IBNF/ENDD/NDE
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>



___________________________________________________________________________=
______________________________________________



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_9E32478DFA9976438E7A22F69B08FF920C7A12CCOPEXCLILM34corp_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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: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";}
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:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<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 0in =
0in 0in">
<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;"> mpls [<a=
 href=3D"mailto:mpls-bounces@ietf.org">mailto:mpls-bounces@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:stephane.litkowski@orange.com">stepha=
ne.litkowski@orange.com</a><br>
<b>Sent:</b> Tuesday, February 10, 2015 13:26<br>
<b>To:</b> <a href=3D"mailto:ospf@ietf.org">ospf@ietf.org</a>; <a href=3D"m=
ailto:isis-wg@ietf.org">
isis-wg@ietf.org</a> list (<a href=3D"mailto:isis-wg@ietf.org">isis-wg@ietf=
.org</a>);
<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>; <a href=3D"mailto:idr@i=
etf.org">idr@ietf.org</a>;
<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:Rtg-yang-coord@ietf.org">Rtg-yang-coord@ietf.o=
rg</a><br>
<b>Subject:</b> [mpls] Survey for YANG model design : routing protocols CLI=
 implementation<br>
<b>Importance:</b> High<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi Folks,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">A lot of us are currently working on Yang model draf=
ts. In the framework of routing protocols related drafts, we have some disc=
ussion regarding how to model the configuration of routing protocols and
<span style=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal">especially do it need to be routing-instance centric=
 or protocol centric<span style=3D"color:#1F497D">.
</span>This is a cross protocol discussion, as we would like to apply the s=
ame design to all.<o:p></o:p></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">Example of routing-ins=
tance centric CLI : (Typically Juniper, ALU)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">routing-instance R1 {<=
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; protoc=
ol isis {};<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; protoc=
ol ospf {};<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; protoc=
ol ldp {};<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">}<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">routing-instance R2 {<=
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; protoc=
ol isis {};<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; protoc=
ol ospf {};<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; protoc=
ol ldp {};<o:p></o:p></span></p>
<p class=3D"MsoNormal"><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">Example of protocol ce=
ntric CLI : (Typically CISCO)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">protocol isis {<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in"><span style=3D"color:#1F4=
97D">routing-instance R1 {}<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in"><span style=3D"color:#1F4=
97D">routing-instance R2 {}<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">}<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">protocol ospf {<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in"><span style=3D"color:#1F4=
97D">routing-instance R1 {}<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in"><span style=3D"color:#1F4=
97D">routing-instance R2 {}<o:p></o:p></span></p>
<p class=3D"MsoNormal"><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"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In order to decide how to progress on this major des=
ign point, one point &nbsp;is to evaluate current implementations and how m=
any are routing-instance centric and protocol centric. The famous implement=
ations are well known, but we would like
 to have a more global view. This metric would be one among others.<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In order to help us to do this inventory, could you =
please respond unicast to me, if you are an implementor and you have an imp=
lementation of a routing-protocol (ISIS,OSPF,RIP,BGP, PIM &#8230; but also =
MPLS-TE, LDP, RSVP &#8230;) and in this case,
 what is your CLI flavor ? <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please use this sample format, so it would be easier=
 for me to aggregate :<o:p></o:p></p>
<p class=3D"MsoNormal">(If you own multiple implementations, you can fill m=
ultiple lines.)<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>
<table class=3D"MsoNormalTable" border=3D"0" cellspacing=3D"0" cellpadding=
=3D"0" width=3D"348" style=3D"width:261.0pt;margin-left:-1.15pt;border-coll=
apse:collapse">
<tbody>
<tr style=3D"height:15.0pt">
<td width=3D"79" nowrap=3D"" valign=3D"bottom" style=3D"width:59.0pt;border=
:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:15.0pt">
<p class=3D"MsoNormal"><b><span style=3D"color:black">Vendor<o:p></o:p></sp=
an></b></p>
</td>
<td width=3D"75" nowrap=3D"" valign=3D"bottom" style=3D"width:56.0pt;border=
:solid windowtext 1.0pt;border-left:none;padding:0in 5.4pt 0in 5.4pt;height=
:15.0pt">
<p class=3D"MsoNormal"><b><span style=3D"color:black">OS<o:p></o:p></span><=
/b></p>
</td>
<td width=3D"119" nowrap=3D"" valign=3D"bottom" style=3D"width:89.0pt;borde=
r:solid windowtext 1.0pt;border-left:none;padding:0in 5.4pt 0in 5.4pt;heigh=
t:15.0pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><b><spa=
n style=3D"color:black">Protocol Centric<o:p></o:p></span></b></p>
</td>
<td width=3D"76" nowrap=3D"" valign=3D"bottom" style=3D"width:57.0pt;border=
:solid windowtext 1.0pt;border-left:none;padding:0in 5.4pt 0in 5.4pt;height=
:15.0pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><b><spa=
n style=3D"color:black">VRF centric<o:p></o:p></span></b></p>
</td>
</tr>
<tr style=3D"height:15.0pt">
<td width=3D"79" nowrap=3D"" valign=3D"bottom" style=3D"width:59.0pt;border=
:solid windowtext 1.0pt;border-top:none;padding:0in 5.4pt 0in 5.4pt;height:=
15.0pt">
<p class=3D"MsoNormal"><span style=3D"color:black">Cisco<o:p></o:p></span><=
/p>
</td>
<td width=3D"75" nowrap=3D"" valign=3D"bottom" style=3D"width:56.0pt;border=
-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-righ=
t:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:15.0pt">
<p class=3D"MsoNormal"><span style=3D"color:black">IOS/IOS-XE<o:p></o:p></s=
pan></p>
</td>
<td width=3D"119" nowrap=3D"" valign=3D"bottom" style=3D"width:89.0pt;borde=
r-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-rig=
ht:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:15.0pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span s=
tyle=3D"color:black">X<o:p></o:p></span></p>
</td>
<td width=3D"76" nowrap=3D"" valign=3D"bottom" style=3D"width:57.0pt;border=
-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-righ=
t:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:15.0pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span s=
tyle=3D"color:black">&nbsp;<o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks for your help !<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"><a href=3D"http://www.orange.com/"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;te=
xt-decoration:none"><img border=3D"0" width=3D"40" height=3D"40" id=3D"Pict=
ure_x0020_1" src=3D"cid:image001.gif@01D045DF.1F80E970" alt=3D"Orange logo"=
></span></a><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot;T=
imes New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;">&nbsp;<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:black">Stephane Litkowski
</span></b><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Network Architect
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Orange/SCE/EQUANT/IBNF/ENDD/NDE
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Orange Expert Fut=
ure Networks</span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:=
&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<span style=3D"color:black;text-decoration:none">&#43;33 2 23 28 49 83 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;"><br>
</span><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:black">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<span style=3D"color:black;text-decoration:none">&#43;33 6 37 86 97 52 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><span style=3D"font-size:1=
0.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#FF6600;te=
xt-decoration:none">stephane.litkowski@orange.com</span></a>
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span lang=3D"FR" style=
=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&qu=
ot;">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<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. Merci.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>This message and its attachments may contain confidential or privilege=
d information that may be protected by law;<o:p></o:p></pre>
<pre>they should not be distributed, used or copied without authorisation.<=
o:p></o:p></pre>
<pre>If you have received this email in error, please notify the sender and=
 delete this message and its attachments.<o:p></o:p></pre>
<pre>As emails may be altered, Orange is not liable for messages that have =
been modified, changed or falsified.<o:p></o:p></pre>
<pre>Thank you.<o:p></o:p></pre>
</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_9E32478DFA9976438E7A22F69B08FF920C7A12CCOPEXCLILM34corp_--

--_004_9E32478DFA9976438E7A22F69B08FF920C7A12CCOPEXCLILM34corp_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: inline; filename="image001.gif"; size=381;
	creation-date="Wed, 11 Feb 2015 08:43:00 GMT";
	modification-date="Wed, 11 Feb 2015 08:43:00 GMT"
Content-ID: <image001.gif@01D045DF.1F80E970>
Content-Transfer-Encoding: base64

R0lGODlhKAAoAMQAAP+MQP+zgP/17//s3/+DMP/iz/+fYP+8j/9wEP95IP/Gn/+WUP/Pr/+pcP/Z
v/////9mAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAAA
AAAALAAAAAAoACgAAAX6oAONZGmeaEqKauum7Cu/8Wyj9a2P+X73vhkwSCPuhkYVMolj2pbOEjTK
oxatrSlVG+U6vUxwUmwkE81BtE99xGbdSjhMPgo4BAoA+wUICAR6IwQODwMNEAcOigAFhQYQDgoD
DwcQBJOKBIOFDQmaCCyTB416hQcBBQuTEA8Cow8EBQINpHcGhAkrEAkPChAAD3YPCLuSDw+sIgEP
wCILzK0OjY9VBJS/wYQjfwaNyRDLzRAG0AMB5wC6ENyEt8jWDAsCyA/KzJN+zLILqLlVv/OuaYPU
alU9cMwuPSCl8AEDYv8EQbwRgAEABcziJFl2bMmeEQgATEwRAgA7

--_004_9E32478DFA9976438E7A22F69B08FF920C7A12CCOPEXCLILM34corp_--


From nobody Wed Feb 11 06:10:47 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 881E41A01E7; Tue, 10 Feb 2015 04:26:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.102
X-Spam-Level: 
X-Spam-Status: No, score=0.102 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 jujMeIUbm79k; Tue, 10 Feb 2015 04:26:04 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A85F1A019B; Tue, 10 Feb 2015 04:26:03 -0800 (PST)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 45A2E26404F; Tue, 10 Feb 2015 13:26:01 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.30]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id D8EA2238067; Tue, 10 Feb 2015 13:26:00 +0100 (CET)
Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.53]) by OPEXCLILH02.corporate.adroot.infra.ftgroup ([10.114.31.30]) with mapi id 14.03.0224.002; Tue, 10 Feb 2015 13:26:00 +0100
From: <stephane.litkowski@orange.com>
To: "ospf@ietf.org" <ospf@ietf.org>, "isis-wg@ietf.org list (isis-wg@ietf.org)" <isis-wg@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Survey for YANG model design : routing protocols CLI implementation
Thread-Topic: Survey for YANG model design : routing protocols CLI implementation
Thread-Index: AdBFLLfJ87T7mg7qSBKOVExsw2JGuw==
Importance: high
X-Priority: 1
Date: Tue, 10 Feb 2015 12:26:00 +0000
Message-ID: <12023_1423571161_54D9F8D8_12023_1801_1_9E32478DFA9976438E7A22F69B08FF920C7A0F1A@OPEXCLILM34.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: multipart/mixed; boundary="_006_9E32478DFA9976438E7A22F69B08FF920C7A0F1AOPEXCLILM34corp_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.12.16.112421
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/uu8aAJmpQ1pAN0xR_898UYqgl8U>
X-Mailman-Approved-At: Wed, 11 Feb 2015 06:10:35 -0800
Cc: "Rtg-yang-coord@ietf.org" <Rtg-yang-coord@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, 10 Feb 2015 12:26:08 -0000

--_006_9E32478DFA9976438E7A22F69B08FF920C7A0F1AOPEXCLILM34corp_
Content-Type: multipart/related;
	boundary="_005_9E32478DFA9976438E7A22F69B08FF920C7A0F1AOPEXCLILM34corp_";
	type="multipart/alternative"


--_005_9E32478DFA9976438E7A22F69B08FF920C7A0F1AOPEXCLILM34corp_
Content-Type: multipart/alternative;
	boundary="_000_9E32478DFA9976438E7A22F69B08FF920C7A0F1AOPEXCLILM34corp_"


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

Hi Folks,

A lot of us are currently working on Yang model drafts. In the framework of=
 routing protocols related drafts, we have some discussion regarding how to=
 model the configuration of routing protocols and especially do it need to =
be routing-instance centric or protocol centric (see slides for quick expla=
nation of the difference). This is a cross protocol discussion, as we would=
 like to apply the same design to all.

In order to decide how to progress on this major design point, one point  i=
s to evaluate current implementations and how many are routing-instance cen=
tric and protocol centric. The famous implementations are well known, but w=
e would like to have a more global view. This metric would be one among oth=
ers.

In order to help us to do this inventory, could you please respond unicast =
to me, if you are an implementor and you have an implementation of a routin=
g-protocol (ISIS,OSPF,RIP,BGP, PIM ... but also MPLS-TE, LDP, RSVP ...) and=
 in this case, what is your CLI flavor ?

Please use this sample format, so it would be easier for me to aggregate :
(If you own multiple implementations, you can fill multiple lines.)


Vendor

OS

Protocol Centric

VRF centric

Cisco

IOS/IOS-XE

X





Thanks for your help !


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/IBNF/ENDD/NDE
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>



___________________________________________________________________________=
______________________________________________

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_9E32478DFA9976438E7A22F69B08FF920C7A0F1AOPEXCLILM34corp_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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: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;}
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.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Folks,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">A lot of us are currently working on Yang model draf=
ts. In the framework of routing protocols related drafts, we have some disc=
ussion regarding how to model the configuration of routing protocols and es=
pecially do it need to be routing-instance
 centric or protocol centric (see slides for quick explanation of the diffe=
rence). This is a cross protocol discussion, as we would like to apply the =
same design to all.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In order to decide how to progress on this major des=
ign point, one point &nbsp;is to evaluate current implementations and how m=
any are routing-instance centric and protocol centric. The famous implement=
ations are well known, but we would like
 to have a more global view. This metric would be one among others.<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In order to help us to do this inventory, could you =
please respond unicast to me, if you are an implementor and you have an imp=
lementation of a routing-protocol (ISIS,OSPF,RIP,BGP, PIM &#8230; but also =
MPLS-TE, LDP, RSVP &#8230;) and in this case,
 what is your CLI flavor ? <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please use this sample format, so it would be easier=
 for me to aggregate :<o:p></o:p></p>
<p class=3D"MsoNormal">(If you own multiple implementations, you can fill m=
ultiple lines.)<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>
<table class=3D"MsoNormalTable" border=3D"0" cellspacing=3D"0" cellpadding=
=3D"0" width=3D"348" style=3D"width:261.0pt;margin-left:-1.15pt;border-coll=
apse:collapse">
<tbody>
<tr style=3D"height:15.0pt">
<td width=3D"79" nowrap=3D"" valign=3D"bottom" style=3D"width:59.0pt;border=
:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:15.0pt">
<p class=3D"MsoNormal"><b><span style=3D"color:black">Vendor<o:p></o:p></sp=
an></b></p>
</td>
<td width=3D"75" nowrap=3D"" valign=3D"bottom" style=3D"width:56.0pt;border=
:solid windowtext 1.0pt;border-left:none;padding:0in 5.4pt 0in 5.4pt;height=
:15.0pt">
<p class=3D"MsoNormal"><b><span style=3D"color:black">OS<o:p></o:p></span><=
/b></p>
</td>
<td width=3D"119" nowrap=3D"" valign=3D"bottom" style=3D"width:89.0pt;borde=
r:solid windowtext 1.0pt;border-left:none;padding:0in 5.4pt 0in 5.4pt;heigh=
t:15.0pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><b><spa=
n style=3D"color:black">Protocol Centric<o:p></o:p></span></b></p>
</td>
<td width=3D"76" nowrap=3D"" valign=3D"bottom" style=3D"width:57.0pt;border=
:solid windowtext 1.0pt;border-left:none;padding:0in 5.4pt 0in 5.4pt;height=
:15.0pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><b><spa=
n style=3D"color:black">VRF centric<o:p></o:p></span></b></p>
</td>
</tr>
<tr style=3D"height:15.0pt">
<td width=3D"79" nowrap=3D"" valign=3D"bottom" style=3D"width:59.0pt;border=
:solid windowtext 1.0pt;border-top:none;padding:0in 5.4pt 0in 5.4pt;height:=
15.0pt">
<p class=3D"MsoNormal"><span style=3D"color:black">Cisco<o:p></o:p></span><=
/p>
</td>
<td width=3D"75" nowrap=3D"" valign=3D"bottom" style=3D"width:56.0pt;border=
-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-righ=
t:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:15.0pt">
<p class=3D"MsoNormal"><span style=3D"color:black">IOS/IOS-XE<o:p></o:p></s=
pan></p>
</td>
<td width=3D"119" nowrap=3D"" valign=3D"bottom" style=3D"width:89.0pt;borde=
r-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-rig=
ht:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:15.0pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span s=
tyle=3D"color:black">X<o:p></o:p></span></p>
</td>
<td width=3D"76" nowrap=3D"" valign=3D"bottom" style=3D"width:57.0pt;border=
-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-righ=
t:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:15.0pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span s=
tyle=3D"color:black">&nbsp;<o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks for your help !<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"><a href=3D"http://www.orange.com/"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;co=
lor:blue;text-decoration:none"><img border=3D"0" width=3D"40" height=3D"40"=
 id=3D"Picture_x0020_1" src=3D"cid:image001.gif@01D04534.27AF7310" alt=3D"O=
range logo"></span></a><span lang=3D"FR" style=3D"font-size:12.0pt;font-fam=
ily:&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;">&nbsp;<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:black">Stephane Litkowski
</span></b><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Network Architect
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Orange/SCE/EQUANT/IBNF/ENDD/NDE
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Orange Expert Fut=
ure Networks</span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:=
&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<span style=3D"color:black;text-decoration:none">&#43;33 2 23 28 49 83 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;"><br>
</span><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:black">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<span style=3D"color:black;text-decoration:none">&#43;33 6 37 86 97 52 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><span style=3D"font-size:1=
0.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#FF6600;te=
xt-decoration:none">stephane.litkowski@orange.com</span></a>
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span lang=3D"FR" style=
=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&qu=
ot;">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</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_9E32478DFA9976438E7A22F69B08FF920C7A0F1AOPEXCLILM34corp_--

--_005_9E32478DFA9976438E7A22F69B08FF920C7A0F1AOPEXCLILM34corp_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: inline; filename="image001.gif"; size=381;
	creation-date="Tue, 10 Feb 2015 12:26:00 GMT";
	modification-date="Tue, 10 Feb 2015 12:26:00 GMT"
Content-ID: <image001.gif@01D04534.27AF7310>
Content-Transfer-Encoding: base64

R0lGODlhKAAoAMQAAP+MQP+zgP/17//s3/+DMP/iz/+fYP+8j/9wEP95IP/Gn/+WUP/Pr/+pcP/Z
v/////9mAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAAA
AAAALAAAAAAoACgAAAX6oAONZGmeaEqKauum7Cu/8Wyj9a2P+X73vhkwSCPuhkYVMolj2pbOEjTK
oxatrSlVG+U6vUxwUmwkE81BtE99xGbdSjhMPgo4BAoA+wUICAR6IwQODwMNEAcOigAFhQYQDgoD
DwcQBJOKBIOFDQmaCCyTB416hQcBBQuTEA8Cow8EBQINpHcGhAkrEAkPChAAD3YPCLuSDw+sIgEP
wCILzK0OjY9VBJS/wYQjfwaNyRDLzRAG0AMB5wC6ENyEt8jWDAsCyA/KzJN+zLILqLlVv/OuaYPU
alU9cMwuPSCl8AEDYv8EQbwRgAEABcziJFl2bMmeEQgATEwRAgA7

--_005_9E32478DFA9976438E7A22F69B08FF920C7A0F1AOPEXCLILM34corp_--

--_006_9E32478DFA9976438E7A22F69B08FF920C7A0F1AOPEXCLILM34corp_
Content-Type: application/vnd.openxmlformats-officedocument.presentationml.presentation;
	name="VRF centric vs protocol centric - IETF.pptx"
Content-Description: VRF centric vs protocol centric - IETF.pptx
Content-Disposition: attachment;
	filename="VRF centric vs protocol centric - IETF.pptx"; size=48433;
	creation-date="Tue, 10 Feb 2015 12:14:02 GMT";
	modification-date="Tue, 10 Feb 2015 12:13:45 GMT"
Content-Transfer-Encoding: base64

UEsDBBQABgAIAAAAIQA9JG3t2AEAAMwNAAATAAgCW0NvbnRlbnRfVHlwZXNdLnhtbCCiBAIooAAC
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADM
l8tOwzAQRfdI/EPkLWrc8gY1ZcFjxUsCPsAk09bg2JY9LfTvmaSlhCpQShM1m0iOPfceT5KJp3v2
nqpgDM5LoyPWCdssAB2bROpBxJ4er1rHLPAodCKU0RCxCXh21tve6j5OLPiAorWP2BDRnnLu4yGk
wofGgqaZvnGpQBq6AbcifhUD4Lvt9iGPjUbQ2MJMg/W6F9AXI4XB5TvdnpK8WBiw4Hy6MPOKmEwz
gXyCl8Y4UH4hRlirZCyQdsfHOlkga82oQorM1/ihtH6H0Fm5QzbzHapoMIu7o3Q6mUBwLxzeipTQ
ubXIrQNPu86Nwt+VSlBNvy9jSEw8SkkkLIql6tswTIXUn5v4CcYrIrwRHunR88KgUzVZQftPTDOa
ejhWIditJROrEOxtnGB/IwTZu33vjPVVu8+Flz2FsYS3WgjmwssIkCop8Py6/qeQyyx1FM8KHnCi
oPK845f0Moq8XFyLiRnhrBJMB+snYaFiFoz+y1RPhZju979M9dSM9ZjqqSLrMR1UXVsqeJ8OG8h0
1ECm4wYynTSQqdNuItSmKjkdnfNfOnUfDlZPzGerkEW3LJ1OwKGEebNQds6eO1KTsLrhwoEfst4o
gaTEm+e9WO8DAAD//wMAUEsDBBQABgAIAAAAIQBo+HShBQEAAOICAAALAAgCX3JlbHMvLnJlbHMg
ogQCKKAAAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAArJLbSgMxEIbvBd8hzH032yoi0mxvROidyPoAYzK7G90cSKbSvr2h4GFhLYK9nNM/X/LP
erN3o3inlG3wCpZVDYK8Dsb6XsFz+7C4BZEZvcExeFJwoAyb5vJi/UQjchnKg41ZFBWfFQzM8U7K
rAdymKsQyZdKF5JDLmHqZUT9hj3JVV3fyPRTA5qJptgaBWlrrkC0h1g2/0dbOmI0yCh1SLSIqZAl
tuUtosXUEyswQT+WdD52VIUa5DzQ6rxAPOzci0c7zqB81arXSP1vQMu/A4Wus5rug9458jxjgpx2
fDPFyDImymXsaPupH7o+JxDtmbwhc9o0jPGTSE4us/kAAAD//wMAUEsDBBQABgAIAAAAIQBjXCO0
wQAAADcBAAAgAAAAcHB0L3NsaWRlcy9fcmVscy9zbGlkZTEueG1sLnJlbHOEj8FqwzAQRO+F/IPY
eyQ7h1KKZV9CIJBTcT5gkda2iC0JrRLqv6+ONgR6nB3mzU7T/S6zeFFiF7yGWlYgyJtgnR813PvL
8QsEZ/QW5+BJw0oMXXv4aH5oxlxCPLnIolA8a5hyjt9KsZloQZYhki/OENKCucg0qojmgSOpU1V9
qrRlQLtjiqvVkK62BtGvsTT/zw7D4Aydg3ku5PObCsWzs3TDNTxzwWIaKWuQcnvnrahleR9U26jd
3PYPAAD//wMAUEsDBBQABgAIAAAAIQBL9T3svwAAADcBAAAgAAAAcHB0L3NsaWRlcy9fcmVscy9z
bGlkZTIueG1sLnJlbHOEj8EKwjAQRO+C/xD2blI9iEhTLyIInkQ/YEm2bbBNQjaK/XtzrCB4nB3m
zU59eI+DeFFiF7yGtaxAkDfBOt9puN9Oqx0IzugtDsGThokYDs1yUV9pwFxC3LvIolA8a+hzjnul
2PQ0IssQyRenDWnEXGTqVETzwI7Upqq2Ks0Z0HwxxdlqSGe7BnGbYmn+zw5t6wwdg3mO5POPCsWD
s3TBKTxzwWLqKGuQcn7nudjI8j6oplZfc5sPAAAA//8DAFBLAwQUAAYACAAAACEAS/U97L8AAAA3
AQAAIAAAAHBwdC9zbGlkZXMvX3JlbHMvc2xpZGUzLnhtbC5yZWxzhI/BCsIwEETvgv8Q9m5SPYhI
Uy8iCJ5EP2BJtm2wTUI2iv17c6wgeJwd5s1OfXiPg3hRYhe8hrWsQJA3wTrfabjfTqsdCM7oLQ7B
k4aJGA7NclFfacBcQty7yKJQPGvoc457pdj0NCLLEMkXpw1pxFxk6lRE88CO1KaqtirNGdB8McXZ
akhnuwZxm2Jp/s8ObesMHYN5juTzjwrFg7N0wSk8c8Fi6ihrkHJ+57nYyPI+qKZWX3ObDwAAAP//
AwBQSwMEFAAGAAgAAAAhAEv1Pey/AAAANwEAACAAAABwcHQvc2xpZGVzL19yZWxzL3NsaWRlNC54
bWwucmVsc4SPwQrCMBBE74L/EPZuUj2ISFMvIgieRD9gSbZtsE1CNor9e3OsIHicHebNTn14j4N4
UWIXvIa1rECQN8E632m4306rHQjO6C0OwZOGiRgOzXJRX2nAXELcu8iiUDxr6HOOe6XY9DQiyxDJ
F6cNacRcZOpURPPAjtSmqrYqzRnQfDHF2WpIZ7sGcZtiaf7PDm3rDB2DeY7k848KxYOzdMEpPHPB
Yuooa5Byfue52MjyPqimVl9zmw8AAAD//wMAUEsDBBQABgAIAAAAIQDd8422KwEAAF8FAAAfAAgB
cHB0L19yZWxzL3ByZXNlbnRhdGlvbi54bWwucmVscyCiBAEooAABAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAALyUX0vDMBTF3wW/Q8m7S9vN+YelexFhD4Lo/ACxvW2DaRJy47Tf3tDqusmIL8Gn
ck7ouT/ugbtaf3Yy2YFFoRUj2SwlCahSV0I1jLxs7y+uSYKOq4pLrYCRHpCsi/Oz1RNI7vxP2AqD
iU9RyEjrnLmlFMsWOo4zbUD5l1rbjjsvbUMNL994AzRP0yW1hxmkOMpMNhUjdlP5+dve+Ml/Z+u6
FiXc6fK9A+VOjKDOc4EP5LYBx8ggRzObeVBCTzPMYzKgFNUBwyCRDp88BHEVE2In4OPRaoPTMvZW
CCKPCRHYRLCOLDrEA0cHdtrFQDaa39WMIoi1jIllLOCvgvZWqKDLmBCBghYhiMU/QcxDEDcxIRx/
lfDseunP33Q+JvMHhB6dxeILAAD//wMAUEsDBBQABgAIAAAAIQA+vRFLYgIAAPkMAAAUAAAAcHB0
L3ByZXNlbnRhdGlvbi54bWzsllGOmzAQht8r9Q7Ir1WWQIAQFLJSW0VaaStFTfYAszBJ0BqDbCdN
9vQdO85CE1XaA/CGGc8/488/xvPHU829I0pVNSJnwcOYeSiKpqzELmcvm+UoZZ7SIErgjcCcnVGx
x8XXL/M2ayUqFBo0pXokI1QGOdtr3Wa+r4o91qAemhYFxbaNrEHTUO78UsIfkq+5H47HiV9DJZjL
l5/Jb7bbqsCfTXGoqfxFRCK3fah91aqrWvsZtf4q/m1JwRHXh1eFetkIrYgOW9CyFS9/gdIon8pn
pW/eeFWZszCIplE6SSJiJzPzhuYGzF/M/f+k96WeyotInPSyQ5Ntk6/hhHbqQ3xyF477taP78KyX
HXet9RtZv3vFKWezIIrGY6pWnHOWpHFqB/rckhtUIRFFdHL1RaNRubSPmSbtqmEXUeIWDlxv8KTX
+sxxMYeM3q1W0j39XkmPgzEgitHL2nbXn8KPPGhpTg3yOWfUGfAdmZczj2Q28Lp+v1akRWpupyA8
i+/yzWwiaetKuCFl76kU+XF1EIW+bLItZrpQpBTQgpn3htJ8H+RYMgFkquFVuaw4twPjdfzBpXcE
qqZPl72+mWWreobbFgpi960WI67N4iBDuAkgXAKFugkUqsNBHZKlIHM8jBA9hh2aKJ6ahgc+Forj
M+n4XGw58DlyA8XxiTo+wWQaJIOBzFdlqDhAcQ9QGqb2eBhOIEPFAUo6QGGYkoGGI4gcZKg4QNMe
oGk0Gc5o++MyVBygtANk6ND9Yzikj9xQcYBmPUBJPB0OaesgQ8Vesu+vmHTz7t/0F38BAAD//wMA
UEsDBBQABgAIAAAAIQCtjlK6zQUAAO1JAAAVAAAAcHB0L3NsaWRlcy9zbGlkZTMueG1s7Fzdb+I4
EH8/6f4HK+9pEhpayBVWhV1WJ+21Vdvdd68xEG0S52yXwq72f79xPoCEj7YR91DjSi1p4gyeyczP
8+HM1YdFHKE55SJkSc/yzlwL0YSwcZhMe9bXx5HdsZCQOBnjiCW0Zy2psD70//zjKg1ENEZwdyIC
3LNmUqaB4wgyozEWZyylCVybMB5jCf/yqTPm+BmoxpHTct0LJ8ZhYhX389fczyaTkNCPjDzFNJE5
EU4jLGHmYhamoqSWvoZayqkAMtndlSn1gTPyEI3Vp0gfOaXqKJl/5ulDesezyzfzO47CMcjLQgmO
QSyWU1wohmX/JjAMDpza7dOSEg4WEx73r3AAvKFFzwLhL9VfuAkHdCERyU+S9Vkyu90xlsw+7Rjt
lF8AM1h9qeIq52ibnVbJzmMoI4q8FVf5UAy3fmHkh0AJAz4V+zl75GZeElM8K/LpDMllCpKRilQx
Lr+YyaMcL0CmmbDkYsDGS8X4d/hURHCQgPpcP0k2CSWasEQ+EBwBya4LPxnJzcGRkA9yGdFMeMAi
DjIaHB5VhJU2T7g9urfQOOQykyeiHBQPHqGI5TCiGPS/EL3sf6PJmPErkKCEB1iSyojup7eDDnoj
iQNTCuM0okr1c41/I+Fdc2OTI06PsycJ5n2EaRGWTMIpCtC3+9ERJ0hAdDwkR5jgG0kceKZ0gdVT
rREE3bvDHN+vNI0m9teHDc1VVocD0HEwpdJu4DA37P3m3S7N+54SgPQpmLivzAgALzfg7HgTtTat
VCl/Da/OO56yRAVaXrfjAa4rcmvouvT8TteHr1UA1na9i8t2p7DbklLKhfxMWYzUQc/iMDNLkcDz
L0IWfBZDMnYVXqgZl2yXCICeOQZEEv8+YU4zCiJV0DEKCyprVHkRKApxi5/A1oXibwUZamZqxUky
cJtgAmg0ZE88pBzd0GcLpThhAk66LffSPXe78Nly2/Druz5cDSWZjXAcRiAPvwtymWEuKPBdCI6I
/4WwArAcUWU/rSlbDST3816BSQ0EwZlkhEXiBYg5IJBdhq2BYEIRCqMk6kHKPvpVkUSOuhn0lj7B
CqQL92IHauhmOegFkzkgCU1NJqJzGlU05ZTVwzNWU6zomwsvgp/GKqKp3eAnOQO3PCRZTNNYOpvB
jQYLsP2DLtHj7ePtXzWJbAUG+5H2/YphzWQZ5Zj19ndFEZp5Ie9XI1axS3P81AwhUJhIylX8iabU
dh3fcZvLRtO1xfhkG1E/8ox+5NmkFZjE9NXpwFOI6TzXeBuFo3GgeHACmnAMX2NnaUUDB+T+DUWO
E1AVO0xUbZhQoWo1xwn7NdCS5kutbm5qJWx5S0pMU580LYsOjQVjNORA8V4D7Hi5+LI/56NdncEU
X/LCcD2N3HyB0RRXTaxvYv36bopNoxmHAn/f2mdT2/pwOsBajfRNOrn0TJX/APmh6n7BE4jjVGly
nVFeqIzyuWPyQc0MQzsvDFUzQrC9r74/cT9yvl+PfM2kKUOqpyj7VTVoaByaOqAmMagyGqvaSjUx
2DL7gXbuB2qcBNLUiEx2rFaiNHF+TSAmO7bG2KOA6vv1z1ZrTXMj0S2XbjaYlm8FrpTDJAY3vDLU
am4rmrocz+GY2vlOIGGzJFo29sk0A5OgIoiGwZ5mMlFpMmNBNZfMIOwmwpptlsX7vasV2JReKpmR
Y5Re9MswA67W6g+tev3BLEHZ+6i1ZLyRynZmekeB4sBL3Hr4KHurFesLRVVzvyjeby5gzWRZq9lu
jJH1xyjb+UBvHWgvofpIqC470L+hZ/0aDLoXrWFnYA88f2T7H7uX9vXoom2P2ue+Pxx0rofnn35D
Z4nU8wPCafbG4t9lByQ4udV1KA4JZ4JN5BlhsZO3L3JS9kx5ygDtoIOR5xZtkOY4Ur0mfM9rQ8OM
VraGZnPLel6UswUWys5EJOL/4PR2nm1hgIZL8DbQMDuVQg8W5aHB0PUQxTt0NPoPAAD//wMAUEsD
BBQABgAIAAAAIQBGnJjREQgAAJRbAAAVAAAAcHB0L3NsaWRlcy9zbGlkZTIueG1s7FzNcts2ED63
M30HlOcqEsUf/UzkjKVESTpp4rGd3FEKsjihCBaAZLuZzPRRcuqlj9CbH6VP0gVIiiJN06QstxHD
g22ZIpfAx93F7oflPn12tfTQmjDuUn+k6U86GiK+Q2eufzHS3p9PW30NcYH9GfaoT0baNeHas6Mf
vn8aDLk3Q3C1z4d4pC2ECIbtNncWZIn5ExoQH76bU7bEAv5lF+0Zw5cgdem1u52O3V5i19ei61mZ
6+l87jrkOXVWS+KLUAgjHhYwcr5wAx5LC8pICxjhIEZdnRrSEczMOfNm8i8Pzhkh8pO/fsmCs+CE
qa/frk8YcmeAl4Z8vARYtHb0RXSa+teH0+BDO3P5RSwJD6/mbHn0FA9hbuhqpAH41/I3XISH5Eog
JzzoJEedxbucc53Fi5yz2/ENYASbm8pZhTO6PR0jns6E+gLQQScedsiCejPCUHczx/BCDILeUOcj
Rz6FWUswwsk6b9exaImAvFmwALhgLvEp4XEFTHwqB3AVauJqTGfXEoFf4a+8Hg990KPjlaBzV8h7
bH/lcXEmrj2iMIOZ4aG6gsET8rBU4jlrTU9BiX8faV2zAxDPXCYUoIgw0Dx4hnwpJh7BYAAR9uLo
/JLK+wh1t1Cikl1GbI44tLOwgjHOPbymjO8sOm+cw5Q0QEBBGv6Sc1970VMsxLmTxjnnRh9OpxUw
ycgrwMQBtWWuk5rFA4eKymCirKPoRnr/XkyOPQ+JBUEO9efuxYop54ToXB0sPaPsjQrAYnQlwCXv
LDrnuZZ/qBXGGTAqqEO9r36gbnljzE7/v8ISlEvA0ktmXz2Yl65YuP5ehymta2eBBYaEOaeOi8We
UXV9GXo5JDXkfJ8c+R/iz04ww6d5y9Q9GrcvueECnbNsHMAQVXxS5MUhdE1FEDlWexI5q/KKlhVa
oGjN8pbV4gKwouWt1Swf9wSwFTD95pePm79uvszIHK880Ur55SK3UQHgR4jJWvE6cvPl5u/ybqnC
oF3f8VaSM9gZkRxHKuNgFaowjoBIQBJ5SBsebRI8II4LHMO+55DE8tno8NZqTfzW+7MwV82gv1lV
IWmOM2T4GObyd2f0ZpzRn7vCI0itb8BvxBl6xRxeXAfAdQgpKsr1H5DIwzP1xZmDPRA5gGVVpd4Q
hCRZf9nUvlRC/wHApqzUs03k5WllRREF65O7DDwiyayQw6ooOG9skCtWlFIwvCqeqBiyMKHNjOwu
5d+I2lHlrY3KA4M2plfITBFXSFpPTEVJZi7h6LapKEn2ZNg50+pBpKYoOkPvmvKzIp1ios6wrZ4t
T5B0na7bA8sK+a5EUsC4eEnoEskPI40RR2jyTnj9hkfMVnyKPOzTqet5Egdp6SGVFht/bCjokmEg
3/hvK8yIhpjwJhQ4mo6SywPJmk0fxprpJVgzOVpJxfpI+og5sIYjbUJXzAXi8C251FCAfcrhYKfb
6XWMzgD+djsW/Jgd8FGBK5zFFC9dD6AzBwDhAjNOAKIIY4c/imBwN0AUysGLo9OqZEgGlm17rAEc
m6ABwZqrp2w3lSmGoWVuvllvgL5LYVIY/WWAyPO5NdCY6mlWBpeaWVC5pVjuS3wjHtblVfjRmivH
p88p/7GbT62B12jcaBjnbuKQxo2Ge65xXNa40YyCUB7MU76jSuxRtzW2caNh9tK40YyVNG60caO3
iITtfN+bBY0XDZ0HarxoCMSPGY24i6PMSdoONxRPJqk8BuzcV9tjsLOEq7UnwnVDqAIpaHWtnqyg
Ai+flEZavYGuKFnFuFr2wLbjXYSYu43p1MNiXNWkNkR4bp3i4erbAzKdDC51C2Yz3qeAWs0AUVNG
sRphlMGkbsrxKaUdZfmimoMSVzaoTYpsGAMLRVE5XBqaw/WnySTj9RuHVdvl/UfdbGVbLbpZtWhM
R2537kY/p22mCUyiF0vCKDQJ2OpmT6mlp5Bu/DYUpBoFm8Gkbsqxj8DkcFffTTZTYZ+i3gqxvfjq
+1l8G/WI3k6sARDb6nErNmtCdqC3wKXcfne15iFGXjhajYbsZWlIe080pGmbfeWxgYaEwk+jY8Zv
MkXvXG94yqbwsyn8PPg62FThZzcV+ZfNnOtdutVstTdb7YU7yxUygYylNDz+7WLY2qXLeaHO/Yxt
WlNqkAc0brRxo40bve/Vp+2KpWqsY9phpHoc1cB77MorpVGpARCNG23caONGq7jRpvAz2bNoCj/l
EiCOmsJPlYFUY1yhNWjY/fI8etO+tyfG1RqYhnqTXhZ+9nQrag6RFH52e6ahKFnJuNqmbRgH/6Z9
UjyQRwKoslfoSnkduNAxw7tO0XJ3bcgnIrdz6EgUmrw+m7yLeg22KsorGKLnfkz3K7t7S+fO8ZXg
GZNrC8YyZtTBM/LTq5OfXq3wJXErTjMPtn/++DMjJam/inZtoi4umyGGAUrlumpY1dPm1d+XeRkG
hMFhJ4tuz+p1LFWxnZiX0ddVQxbVycKwB4ahdjzgsRxsWfXmYeTWLD2CeWWUJL8Wr9Sofl75bkD2
0Lqmffzm/f9j8BUsQrU6idsuw7oCjVFkB2HZZAXaiYy0T+PxwO5O+uPWWDenLfP5oNc6ntpWa2oZ
pjkZ948nxovPGlyjm0OHEdVb53XcqRoO3uoOvXQdRjmdiycOXbbDNtPtgF4SFlBXdZrWO1G76jWG
1ip93eqbA2MQ2oQamnplIh4szCBuIO147BccvFurpw99sQVhE3UogF5Z0i3AqckpcurQePpfAAAA
//8DAFBLAwQUAAYACAAAACEAE3fd24YCAADQBgAAFQAAAHBwdC9zbGlkZXMvc2xpZGUxLnhtbLRV
0U7bMBR9n7R/sPwe0pbAStQU0UIQEisVLZP2aByXRnNs69qEVtP+fddOAtuoBAj2Ejv2vSf3HF+f
jI43lSS1AFtqldH+Xo8SobguSnWX0ZtlHg0psY6pgkmtREa3wtLj8edPI5NaWRDMVjZlGV07Z9I4
tnwtKmb3tBEK91YaKubwFe7iAtgDolYyHvR6h3HFSkXbfHhNvl6tSi5ONb+vhHINCAjJHFZu16Wx
HZp5DZoBYREmZP9V0hiZ8YUs/GjNEoTwM1Wfg1mYOYTtWT0HUhaoFyWKVSgLjduNNiy8KgzDSfxP
+l2HxNLNCqrxiKXIjWwyiuJv/ROTWCo2jvBmkT+t8vXVjli+PtsRHXcfwAoeP+pZNYye0xl0dJal
k4L0H1k1oQxTLzX/YYnSyNPTb+jxWd2Bec4e3qyJ2xpUhjsIaG1osx8k6VIsyhr0cpuJLrae+y2O
YZGl0rqF20oRNMHKWYr4+MATkMw36Qqi/JqSogQXZCK2clMpGLZzq6QbX5wtc/L9ZHZORiiKwzPp
YF7AEoC9iae8AxP0vcN+fiPgDqAPrKnShZD23SX5U20Fun2j2pjXpryg7A4hvl3nH6gFx+sNJX+3
GGNSWzIH7TTX8r/XJ1QxZ8CuH9tbqOhm8Ud7N2eDFwHvUHdhcOovdRg6x0L7uLTY6SYYyT2UGf05
mRwdDqbDSTTpJ3mUnB59iU7yw4MoP9hPkulkeDLdP/tFMaefpBxEMMeLzuRx8ZmxViUHbfXK7XFd
xY1Dx0Y/CDC6DCbd77VOXzOZ0UEy7PUG/cFR0toBVhnq7qpFCp35cglfmbmqQwPiP8UJmIYlg7fO
q4ChTyGeO5r2bwAAAP//AwBQSwMEFAAGAAgAAAAhABRlUw5vBAAAmCIAABUAAABwcHQvc2xpZGVz
L3NsaWRlNC54bWzsWl1v4jgUfV9p/4M37zQJUChRYVSYoVpptlOVzrx7jAPWJrbXNhQ02v++107M
99Ay6r4EUEtCYp/cc20fX8f39sMiz9CcKs0E7wbxVRQgyokYMz7pBl+fh7WbAGmD+RhngtNusKQ6
+ND7/bdbmehsjKA21wnuBlNjZBKGmkxpjvWVkJTDvVSoHBv4qSbhWOEXQM2zsB5FrTDHjAdlffWW
+iJNGaEfBZnllJsCRNEMG7BcT5nUHk2+BU0qqgHG1d4yqQfMyCgb26OWz4pSe8bn90qO5KNytx/m
jwqxMfgrQBzn4JYgLG+UxdxPDsXgJNypPvFIOFmkKu/d4gS4oUU3AOcv7TdUwgldGESKi2R9lUy/
HChLpp8OlA79A8CC1UMtq4LRPp26p/PMTEZRvGJVFMVQ9bMgf2vEBfC09At65GHuwSxnCy+nyCwl
eMZYqLJccdP5w5fX4FPnLLPoi/HSEv8ORwuCEw7d525mRMoMSgU3I4IzgOxE8HGQm4UzbUZmmVHn
PKCIE4ehoKkybHtzqmrDpwCNmTLOn4gq6HjQhDo3g4xi6P+l603vG+VjoW7BgwYa0EM50J/jHcBB
J0IcMYnlMqO26xc9/kTgQ7aJ9B3NU2JmYHi/g1lE8JRNUPKOxkkljCAiewfrToQ40qAE2lIxciLg
oYY8EeKITXSBbTfbAYTB8IgVflp1fcprX0cbQ8nKAE5g0MHY9gMZTgul+bneNL3ePFECc8wENKdh
xzUocKEo7nxTRjdlw47GHQFtRZ0WSINV0Xp03W4WMrHW0nar04LZJ0BWURuddtSIb0oh8UhSaXNP
RY7sSTdQYFlgn4Tnn7UpeZZFHF0rYNZiT9tLEnpRGCRS/zPDijoELa2WDVmJspa5V5Vr191bimWN
s7Mgd4KbYgIKORAzxahCD/QlQBJzoeFiVI+AcNSBIzgH/psRNIBkhkyHOGcZuKTZAddMsdIUqJdi
SPT/AmxFtVB507PaAdbu9Lod+d5zwqFuXAFnCC3TEz2xqQkV8ACKoy0HFNLi9MXPxCsl2p3Uq0B/
i/yrjKspBjU2RnF85f92XPLqhFQRp6x5+gn28CjY08aqKcJO+5/p1DBX5z4zfHsaxlt94djcUPlR
gYrA6ZhWnrd/IPTG6NeDiYrMIqs4G8GHcQi17SoB3bNJHG47B1ZKry31KuKTNc8zn1nRHxc9deGE
6V0WoPAqwfQuUQZEGfXLqPCj4hJl7L0V23x5hZCLMt4ell5eWVQkhtiMq7bCqvolrALxOO+lxyWs
8m/3LxHmSigOdYr9LTO3c+YzDyANADae7A6TTQiAbZ1u8KPfh22swU2/1o+bw1rzY6dduxu2rmvD
60azOejf3A0an/4NoE7cTAgsgW2KxJ8+WQMu7iVI5IwooUVqrojIwyLTIpTihSopQNkg2SKOyoyN
Oc5gcy3uNNpRPa4Xu2fONrcb5q0FCj6JgmTqLyy/zF04AbkhsPwcuEsStovthhoUXRex3CH54j8A
AAD//wMAUEsDBBQABgAIAAAAIQDV0ZLxvgAAADcBAAAsAAAAcHB0L3NsaWRlTGF5b3V0cy9fcmVs
cy9zbGlkZUxheW91dDYueG1sLnJlbHOEj8EKwjAQRO+C/xD2btJ6EJGmXkTw4EX0A5Zk2wbbJGSj
6N+bYwXB4+wwb3aa/WsaxZMSu+A11LICQd4E63yv4XY9rrYgOKO3OAZPGt7EsG+Xi+ZCI+YS4sFF
FoXiWcOQc9wpxWagCVmGSL44XUgT5iJTryKaO/ak1lW1UWnOgPaLKU5WQzrZGsT1HUvzf3boOmfo
EMxjIp9/VCgenaUzcqZUsJh6yhqknN95LmpZ3gfVNuprbvsBAAD//wMAUEsDBBQABgAIAAAAIQBp
ol8hHgEAAMcHAAAsAAAAcHB0L3NsaWRlTWFzdGVycy9fcmVscy9zbGlkZU1hc3RlcjEueG1sLnJl
bHPE1d1qwyAUB/D7wd5Bzv1ikrbpBzW9GYPCrkb3ABJPPliionYsbz8pDBIojkLAm4CK5/z4K+Z4
+hl68o3GdkoyyJIUCMpKiU42DD4vby87INZxKXivJDIY0cKpfH46fmDPnd9k205b4qtIy6B1Th8o
tVWLA7eJ0ij9Sq3MwJ0fmoZqXn3xBmmepgU10xpQzmqSs2BgzsL3v4zad/6/tqrrrsJXVV0HlO5O
C2r7TuA7H9XV+bLcNOgYJMl03k4Hu8Tzgd6XrWLKViHZNqZsG5Jl+ZI0568Zzg7yNkNv3yzkWJTx
6K3KQ7JsyYAelQUzK2LKimBmcUMLpraJmdommJp/6+M9rVkasq1j0tYh2T6mbP8no7Pfb/kLAAD/
/wMAUEsDBBQABgAIAAAAIQDV0ZLxvgAAADcBAAAsAAAAcHB0L3NsaWRlTGF5b3V0cy9fcmVscy9z
bGlkZUxheW91dDgueG1sLnJlbHOEj8EKwjAQRO+C/xD2btJ6EJGmXkTw4EX0A5Zk2wbbJGSj6N+b
YwXB4+wwb3aa/WsaxZMSu+A11LICQd4E63yv4XY9rrYgOKO3OAZPGt7EsG+Xi+ZCI+YS4sFFFoXi
WcOQc9wpxWagCVmGSL44XUgT5iJTryKaO/ak1lW1UWnOgPaLKU5WQzrZGsT1HUvzf3boOmfoEMxj
Ip9/VCgenaUzcqZUsJh6yhqknN95LmpZ3gfVNuprbvsBAAD//wMAUEsDBBQABgAIAAAAIQDV0ZLx
vgAAADcBAAAsAAAAcHB0L3NsaWRlTGF5b3V0cy9fcmVscy9zbGlkZUxheW91dDkueG1sLnJlbHOE
j8EKwjAQRO+C/xD2btJ6EJGmXkTw4EX0A5Zk2wbbJGSj6N+bYwXB4+wwb3aa/WsaxZMSu+A11LIC
Qd4E63yv4XY9rrYgOKO3OAZPGt7EsG+Xi+ZCI+YS4sFFFoXiWcOQc9wpxWagCVmGSL44XUgT5iJT
ryKaO/ak1lW1UWnOgPaLKU5WQzrZGsT1HUvzf3boOmfoEMxjIp9/VCgenaUzcqZUsJh6yhqknN95
LmpZ3gfVNuprbvsBAAD//wMAUEsDBBQABgAIAAAAIQDV0ZLxvgAAADcBAAAsAAAAcHB0L3NsaWRl
TGF5b3V0cy9fcmVscy9zbGlkZUxheW91dDcueG1sLnJlbHOEj8EKwjAQRO+C/xD2btJ6EJGmXkTw
4EX0A5Zk2wbbJGSj6N+bYwXB4+wwb3aa/WsaxZMSu+A11LICQd4E63yv4XY9rrYgOKO3OAZPGt7E
sG+Xi+ZCI+YS4sFFFoXiWcOQc9wpxWagCVmGSL44XUgT5iJTryKaO/ak1lW1UWnOgPaLKU5WQzrZ
GsT1HUvzf3boOmfoEMxjIp9/VCgenaUzcqZUsJh6yhqknN95LmpZ3gfVNuprbvsBAAD//wMAUEsD
BBQABgAIAAAAIQDV0ZLxvgAAADcBAAAtAAAAcHB0L3NsaWRlTGF5b3V0cy9fcmVscy9zbGlkZUxh
eW91dDEwLnhtbC5yZWxzhI/BCsIwEETvgv8Q9m7SehCRpl5E8OBF9AOWZNsG2yRko+jfm2MFwePs
MG92mv1rGsWTErvgNdSyAkHeBOt8r+F2Pa62IDijtzgGTxrexLBvl4vmQiPmEuLBRRaF4lnDkHPc
KcVmoAlZhki+OF1IE+YiU68imjv2pNZVtVFpzoD2iylOVkM62RrE9R1L83926Dpn6BDMYyKff1Qo
Hp2lM3KmVLCYesoapJzfeS5qWd4H1Tbqa277AQAA//8DAFBLAwQUAAYACAAAACEA1dGS8b4AAAA3
AQAALAAAAHBwdC9zbGlkZUxheW91dHMvX3JlbHMvc2xpZGVMYXlvdXQyLnhtbC5yZWxzhI/BCsIw
EETvgv8Q9m7SehCRpl5E8OBF9AOWZNsG2yRko+jfm2MFwePsMG92mv1rGsWTErvgNdSyAkHeBOt8
r+F2Pa62IDijtzgGTxrexLBvl4vmQiPmEuLBRRaF4lnDkHPcKcVmoAlZhki+OF1IE+YiU68imjv2
pNZVtVFpzoD2iylOVkM62RrE9R1L83926Dpn6BDMYyKff1QoHp2lM3KmVLCYesoapJzfeS5qWd4H
1Tbqa277AQAA//8DAFBLAwQUAAYACAAAACEA1dGS8b4AAAA3AQAALAAAAHBwdC9zbGlkZUxheW91
dHMvX3JlbHMvc2xpZGVMYXlvdXQzLnhtbC5yZWxzhI/BCsIwEETvgv8Q9m7SehCRpl5E8OBF9AOW
ZNsG2yRko+jfm2MFwePsMG92mv1rGsWTErvgNdSyAkHeBOt8r+F2Pa62IDijtzgGTxrexLBvl4vm
QiPmEuLBRRaF4lnDkHPcKcVmoAlZhki+OF1IE+YiU68imjv2pNZVtVFpzoD2iylOVkM62RrE9R1L
83926Dpn6BDMYyKff1QoHp2lM3KmVLCYesoapJzfeS5qWd4H1Tbqa277AQAA//8DAFBLAwQUAAYA
CAAAACEA1dGS8b4AAAA3AQAALAAAAHBwdC9zbGlkZUxheW91dHMvX3JlbHMvc2xpZGVMYXlvdXQ0
LnhtbC5yZWxzhI/BCsIwEETvgv8Q9m7SehCRpl5E8OBF9AOWZNsG2yRko+jfm2MFwePsMG92mv1r
GsWTErvgNdSyAkHeBOt8r+F2Pa62IDijtzgGTxrexLBvl4vmQiPmEuLBRRaF4lnDkHPcKcVmoAlZ
hki+OF1IE+YiU68imjv2pNZVtVFpzoD2iylOVkM62RrE9R1L83926Dpn6BDMYyKff1QoHp2lM3Km
VLCYesoapJzfeS5qWd4H1Tbqa277AQAA//8DAFBLAwQUAAYACAAAACEA1dGS8b4AAAA3AQAALAAA
AHBwdC9zbGlkZUxheW91dHMvX3JlbHMvc2xpZGVMYXlvdXQxLnhtbC5yZWxzhI/BCsIwEETvgv8Q
9m7SehCRpl5E8OBF9AOWZNsG2yRko+jfm2MFwePsMG92mv1rGsWTErvgNdSyAkHeBOt8r+F2Pa62
IDijtzgGTxrexLBvl4vmQiPmEuLBRRaF4lnDkHPcKcVmoAlZhki+OF1IE+YiU68imjv2pNZVtVFp
zoD2iylOVkM62RrE9R1L83926Dpn6BDMYyKff1QoHp2lM3KmVLCYesoapJzfeS5qWd4H1Tbqa277
AQAA//8DAFBLAwQUAAYACAAAACEA1dGS8b4AAAA3AQAALQAAAHBwdC9zbGlkZUxheW91dHMvX3Jl
bHMvc2xpZGVMYXlvdXQxMS54bWwucmVsc4SPwQrCMBBE74L/EPZu0noQkaZeRPDgRfQDlmTbBtsk
ZKPo35tjBcHj7DBvdpr9axrFkxK74DXUsgJB3gTrfK/hdj2utiA4o7c4Bk8a3sSwb5eL5kIj5hLi
wUUWheJZw5Bz3CnFZqAJWYZIvjhdSBPmIlOvIpo79qTWVbVRac6A9ospTlZDOtkaxPUdS/N/dug6
Z+gQzGMin39UKB6dpTNyplSwmHrKGqSc33kualneB9U26mtu+wEAAP//AwBQSwMEFAAGAAgAAAAh
ACdxx8UcBAAAsQwAACIAAABwcHQvc2xpZGVMYXlvdXRzL3NsaWRlTGF5b3V0MTEueG1stFfbbts4
EH1fYP+B0D4rupiSbSF2YTnWYoE0CWq37yxFx0IpUUvRrt2iQH+r+zn9kh1SotM4XqzTuC++UJzD
mXNmhqPLV9uSow2TTSGqkRNc+A5iFRV5Ud2PnLeLzB04qFGkygkXFRs5O9Y4r8a//3ZZJw3Pr8lO
rBUCjKpJyMhZKVUnntfQFStJcyFqVsGzpZAlUfBX3nu5JB8Bu+Re6PuxV5Kicjp7eYq9WC4Lyq4E
XZesUi2IZJwo8L9ZFXVj0epT0GrJGoAx1o9dUrsaogVi1KJQnE2qfLF1kNkvN/AkcMZAAZ3zHFWk
hIV3sLWghCOzHwFjaMG2ymxr6oVkTBtUmz9lPa/vpLG+2dxJVOQarUNxvO5Bt838rWAb/PAOzO8t
Ekm2S1mOL0kC7KDtyAERd/oTjEgCTiDaLtKHVbq6PbKXrmZHdnv2APBgfyjoX7cRPQ0ntOEckBLs
w2ttCGBcC/qhQZWAgDUPbZz0ZmNRdfD6nHqFWk2U1sNBQhagXCtRZ9VuNTRZ68ZQbf3fExTH4RD7
LU1hH8e9wWOuQj/qm+easWgQBVEYmUMsEhzSQteJ2qYi32mm38M3CKqTZuQwooNvYXmj5mrHmdED
WCMJhAQfsJkTXWisct/OodBKNeWMQCF22qnxlBf0A1ICsbxQ6DVpFJPIUABlCZCXII6C3OggWZXf
EUneHCBrVkkCJ4Pf1l8Tgmb2v3XsPdVRZ9MdJ5StBM/BlVBHCIVgBfspSTVxB4pCWUDO2nw4XVkc
9aGxmPw/JmzsB8OBfv6rhIV8Q3zD9wq+UGhNt9G5eSR0K6ZRFD7skYatZ+TWnFEBbYqzDeMnwBup
nwG/WBXydPReWyon85WJtVSrk53Hz4UvlkfRoZ+etcSwLbErotijyjKEvLSycgVd5RNchYQvna6m
TG8xXVJ3VvPjx3Zp6tk2CdvUTOd62saWcP3p++tzNEsnEzzMXIz9qYujNHLTcBq6wazv43CS+ngS
fXG6Dp5DqKooWVbcryW7XetL8rRuGPpB5PoA6z/kK/igzc8rS2RlyYTQHffHlmdS6aXCLJVslfl7
TSScYMX5n473HHHOy0hsGZnzImfoZl2+P+DF3JAv5QWGSoA+So3pP2fO295VD2dxGLmTOJ25OBhi
dzhL++4sxbNhFvbDqJ/t87bRkVfg3anp+v3rtz++f/3nDLlqLms7RMKlcN3ApV+b2W4tCyjANB3G
4XSQummAoQqvhn13ksWRm0U9jKfpYDLtzb6A43WAEyqZmXj/yrvJGxafTMtlQaVoxFJdUFF67djt
1eIjk7UozOQd+N34viFw3/Xguh3iKOjFutOCv+Cl/TbewpIel820wOVrUt9uoP2QBF4UIP+nZqmG
V4PWmj5s0bHbV43xvwAAAP//AwBQSwMEFAAGAAgAAAAhAAs+iyjuBAAAXREAACEAAABwcHQvc2xp
ZGVMYXlvdXRzL3NsaWRlTGF5b3V0My54bWzMWNtu4zYQfS/QfxDUZ8WSrIslJFlYjt0WyCZBnf0A
RqJjYalLKdprt1hgf6v9nP2SnqEk28mmqJsNgrwkMi/DM2fOkEOevtsUwlhz2eRVeWY6J7Zp8DKt
sry8PzM/3M6skWk0ipUZE1XJz8wtb8x35z/+cFrHjcgu2bZaKQM2yiZmZ+ZSqToeDJp0yQvWnFQ1
L9G3qGTBFH7K+0Em2SfYLsTAte1gULC8NLv58pj51WKRp/yiSlcFL1VrRHLBFPA3y7xuemv1MdZq
yRuY0bMfQlLbGt42PP2Fs8w09EC5RpNjnsP3dC4yo2QFGuY8pcUNGsil7m3qW8k5jSvXP8t6Xt9I
PelqfSONPCMj3WRz0HV0w/TPEsPwMXg0/b63xOLNQhbnpywGG8bmzETQtvQXk1jMN8pI28Z035ou
r58Ymy6nT4we9AsAwW5RxLtuPfrWHbd35zZXghvOzqt2KMPUyyr92BhlBT/J/da99GrdGyOfyXy9
NFrqFZnqxrWdmo9+fKM57YHumAhdd+gMNR2eZweR/YiUMAxdD40GUeMMA9cOfb1IbwmLtKbrWG2S
KtsSpXf4j8ixMl1WUKmiGSwWjZqrrUCc8b0WDhAZTNwjjQRUwOKML35DU/PHmYklseadDnzKwAAT
olu2m4lwP7QIslkMSvAHRgSjfOSl9WGOfCzURHCGhTrv1PlE5OlHQ1UGz3JlvGeN4tLQFCJ7gZGs
K72GNsnL7IZJRvAOLVNUWIyVwULvvSaEIvPv4QffbSrckvZuBEv5shJIBsMlJ5EtfZyfpQRi30Ta
QNO9cJ4lCDeygxDi0MHrs+ShIHzbdkZhF5k2yY4RxF1r8ylBFExe6gTNyww7DX1STO9WV9hONZID
mWBLbLubSuTZLBeCxurdlE+ENNZMQH0b2oIQzrxUbUsI2FoJCN5usA7lgR30tSvpjp3qtHRdkm6L
1PNDoADdR8B1Rq8IlzCS20A+3MONHKT5sXCDV4RLGDu43h6uMwwdQnEcveSZFsArqIFAdnj9A7wj
d0RBfnt4CWSHN9jjdd0R6H2LeAlkhzc8wBt6w+PT7TX1QCA7vKM9XgJ7fL69Jl4C2eGNDvAGfvg2
841AtjvxQRWhz3xCj01ud7hrt55fA9BBp0uA5kEN8Jxz3uvP+Qum+INzXh+q33vOZwqlDYqlJROL
/rxvjzUqhDVd9DHXzLVlmq4u+kqlr9P0qdqfxfqH5nWBip1q7z/9aTIee9HMwtExsTw/8a3EnbiW
Mw1tzx0ntjf2P5tdGZrBVZUXfJbfryS/XimTVHZMOFzb8S0bZu098cBA01+2/PL7sMyqisq+wwLM
e4kCbKFkG5nfV0xihT44/1GN/Z/gvCwjQc/IHGUUN65Wxd0jXnTR/72CxQUYpp+kRhe+KB1fUrfD
i6E3C1zfGgfJ1PKcyLOiaRJa08SbRjM3dP1wttNtQ56XQHesXL9++eunr1/+fgGt6oq5vwBj+7ls
cPOo9b10JXMkYJJEgTsZJVbieMjCiyi0xrPAt2b+0PMmyWg8GU4/A3jteHEqub6d/5p1rwRo/OZm
X+SprJpqoU7Sqhi0TwSDuvrEZV2hSsYrgWN3Tw26hB4Oo8B3AjfqwwSU+tLTo4ULdMPXdxch37P6
eq23YTxqQP8oxdFU4xkDEqeh+yHke/8scv4PAAAA//8DAFBLAwQUAAYACAAAACEAZYZdK7cDAACa
CwAAIQAAAHBwdC9zbGlkZUxheW91dHMvc2xpZGVMYXlvdXQyLnhtbKxWXW7jNhB+L9A7EOqzoh9L
dizEXliKVRTIJkGdPQBDUZG6lKiStNZuscBeqz3OnqRDSsw2WRdwar/IFjXzceab4ce5erdrGOqp
kDVvF05w4TuItoQXdfu0cD485O6lg6TCbYEZb+nC2VPpvFv++MNVl0hW3OA93yoEGK1M8MKplOoS
z5Okog2WF7yjLXwruWiwglfx5BUCfwLshnmh70+9BtetM/qLY/x5WdaEXnOybWirBhBBGVYQv6zq
Tlq07hi0TlAJMMb7ZUhq30G2/PE3Bxkj0cNr4Cwhb7JhBWpxAwsPtWIUATso460CJGMguwdBqTZt
+59Ft+nuhfG77e8FqguNM/o73vhhNDOvLZjBH++V+5NFwsmuFM3yCidABtotHKjZXj/BCSd0pxAZ
Fsm3VVLdHbAl1fqAtWc3gAieN4Vyd0NG36cT2nQGOoLnrAZTDK43nHyUqOWQp05/SI/c9hZM56zh
uwoNzCvN7Gg3fDR8WHsJnBqy1C7lxV4n/gi/ZhEnTKqN2jNqCIGwcQLg8AD6GdaNTVv3wwYau1EZ
oxgafyRPLTNWk49IcUSLWqH3WCoqkAkGjgFAXgE7CoozQtK2uMcC//oKWeeHE9gZgrYRwt+Bwv8m
cmKJHLsJ3TNMaMVZAUGEp9FaF9AUlvkzMAoFQKxnz9SdyLBuW0OwfMHwwKKhEh52S5PGG4q6oYTD
GWW0p+wIeMP0G+Afqlocjz7RdXwDes63QlVHBx+9Fb4uD6KDkpy1tyPb29dY0ReNbQgBWbVq8L/0
olBwnP8AzcesdEBkdbObQ21kQ4vLSfpRguRr5f4zXqerVTTP3SjyMzeK09hNwyx0g/XMj8JV6ker
+LMzilgBqaq6oXn9tBX0bquvB6j8K7E4JEOhH8SuD7D+t36FGLT7ecsS27LknGup+7fimFY6tTCl
EkNlft9iATvY4pxRis7LyNQysmF1QdHttnl8xUt8mhIPFxxMTwB9kBqjP2fu28n1JMqnYeyupuna
jYJ55M7X6cxdp9F6noezMJ7lz30rdeYtRHdsu3798tdPX7/8fYZeNbekHZ/gUriRcNt2ZqrZihoO
YJrOp2F2mbppEMEpvJ7P3FU+jd08nkRRll6ussn6MwTeBVFCBDWj3S/FOGLC4ndjYVMTwSUv1QXh
jTfMl17HP1HR8dqMmIE/zqk9hvsumE4m0WwexFZeIEqjLjZaSEGPiDpswsR73N31ID84gYkY+j8z
Sx3MwHpIeGGic7cz9fIfAAAA//8DAFBLAwQUAAYACAAAACEAp5PHy6AEAAAJEQAAIQAAAHBwdC9z
bGlkZUxheW91dHMvc2xpZGVMYXlvdXQxLnhtbMxYXW7jNhB+L9A7COqzYv1LFhIvLMcuCmSTYJ09
ACPRtrCUqJK0126xwF6rPc6eZGco0XayKWoURuEXm6KGw2/mmyFndP1uWzNrQ4WseHNje1eubdGm
4GXVLG/sj08zJ7UtqUhTEsYbemPvqLTfjX7+6brNJCvvyI6vlQU6GpmRG3ulVJsNBrJY0ZrIK97S
Bt4tuKiJgkexHJSCfAbdNRv4rhsPalI1dr9enLKeLxZVQW95sa5pozolgjKiAL9cVa002tpTtLWC
SlCjV7+EpHYtWKsqxahtaTGxgQnPHoHlxZyVVkNqmHhCCWvOqpLqV7J9EpSiULP5VbTz9lHoFfeb
R2FVJWroV9qD/kUvph8bEIPB4NXypdFEsu1C1KNrkoEjrO2NDXzt8BcWkYxulVV0k8Vhtlg9vCFb
rKZvSA/MBoBgvylQ3XYW/WiOb8zpHOHtrepECSy948UnaTUc7ETzO/OK+41Rhjaj+nZldV4vlNDa
etHuvXaJWSK1Ww3WvTPiNErdziO+F7ihH730S5IkfogC6B0vTFy3kzi2ulPdZmqb83KHXn2Gf80K
yZhUc7VjVHsbfEIyQA4/wC0jmDG0cT7OIWNqNWGUQEb1zKjRhFXFJ0txi5aVst4TqaiwlI4eiSqv
AYQC5nuVtCkfiSAfXmlG55EMdgZ3GIQw7Pj5Z5YCw9J8/dzt6Z+DKLl+7oiCyIawM9yeTpgXJF7c
MxakaQxnwkvGYqBLU6oZSyIfpTsndImgje/ix/jjTcaQJrZhHgSOVRNxpzOnakrIfj0kbAlsQeRB
FoOC9T2cdprlki6ABJyUHLJ8VjGmH/CIoxMmrA1hcFBs8WQABqtGdTNJ5O6h6vMQhTV7R3qAS6Mf
hj0+1AND/wA1jBL0jHV5eBFkjzc44B16oU6zy8OLIHu84QHvPgwvDzCi7AFHR4BTP9VpcXmAEWUP
OD4A9v0UMvciQxhR9oCTI8BJGFxoziHKHnB6AIxoLzTpEGUPeHgEOI4SffZfXgwjSn1Um/se0Z/h
uof78v+68UNz498SRa1HRgq64qyEmiM4x81fKihy/oASm7AF3Ev69u8uZqxctfdwMNeOxPpEF1CH
muXNO/pQVS2gvsZi+c9omo/H4XDmwIUyccIoj5zcn/iON02gvBvnbjiOvth93ViCqaqq6axargV9
WCsbeTulOPNdL3JcUOseyjDAgMvPW4hFhpYZ51gAHhMTnoOYBVQwmpnf10TADoacf6nNwPUnk3Ne
j8TGI7qHsu7X9fMrv+giHpou0zH8p54CmlVQ/aZrdCms24vzxW1wG4Sz2I+ccZxPndAbhs5wmifO
NA+nw5mf+FEy28etxO6xAXSnhuu3r3/98u3r32eIVV0+m44V2sc7CT1IqxvJtaggAfN8GPuTNHdy
L4QsvB0mzngWR84sCsJwkqfjSTD9AsBbL8wKQXUn/VvZd/Qw+UMXXleF4JIv1FXB60HXzg9a/pmK
lkPxDB295/afBXRlDU1cnIaeF5kIBpS6/TFowQTsxxF2wcR70j5s4PAmGXyAgPiHohumWvjkgF3D
CxG03XzCGH0HAAD//wMAUEsDBBQABgAIAAAAIQCVzk/GEQgAAOkwAAAhAAAAcHB0L3NsaWRlTWFz
dGVycy9zbGlkZU1hc3RlcjEueG1s7FvrbuPGFf5foO9AsD8LrsS7KKwcSForXcDZGLHzACNyZLEe
XjocKXaCAPsOfYO+Rdt/fZR9kp4zF4qypY0M24C9FrKQyJnh4cz5vnOV8/67m4JZa8qbvCpHtvuu
b1u0TKssL69G9s+XM2dgW40gZUZYVdKRfUsb+7uTP//pfT1sWPYDaQTlFsgomyEZ2Ush6mGv16RL
WpDmXVXTEuYWFS+IgFt+1cs4+QVkF6zn9ftRryB5aevn+SHPV4tFntIPVboqaCmUEE4ZEbD/ZpnX
jZFWHyKt5rQBMfLprS2dwPnSC5bh9/xKff5EF1ae3YCW+n3XPnlPhvKcdMq4tSZsZM+vXLt38r6H
j8BifYUPN/UlpxSvyvX3vL6ozznepJ/W5xxkgkjbKkkB+kUBckIvk7clLFOCtx6/MpLI8GbBC9wR
qMeCHQKKt/gJD5EhvRFWqgbTzWi6/HHH2nR5umN1z7wAjta+FE+lTnT/OJ45zmUuGLXOGUnpsmIZ
cEWqSJ5QPQZarM+q9LqxygrOjKpQRwXlGMF4fnxVvbTEbQ1aEihWr1OTsLOyXd9I/ZpNt1oJwhhI
J1XjxUHkD7b1M/C8JMJ51JLrBn4fbnAvG0E1b8T3tCosvBjZnKZCEoGszxqhlpolEn21kXoobiZV
dotgzOEbMAeLg+eXFf/VttjHshnZiRsE8G4hb+RObYt3Z+ZbM4JNK6AcPEHKFOSM7FRwuZcSrG28
EtUi1ztSr8SXs0ZciFtGJS0APDIEtcIHbIgRNHhaOj9fgMEXYsooAYegKSROpixPry1RWTTLhaXt
XsIA7gFEopaE1JUUScvsnHDy0x3JWkVSN0YngJwi0n46+S2dkMtdNnkI0GPZhAqytWk/hlQusAcJ
JtVrrG6LVUHohUnkv3xWIS0eRCSwOIutJSPl8R9JLNSe5FWzRSwgmaSt+jCvlB7jAVy+oGlVZhaj
a8oOEC859gDxl8ucHy5dkuEB0mfViovlwZsPFBsPhmOWL3ZKhzDypCYdGJP+QMR2gJAKeaxJZwK8
2K/gYQlbaNOWMMowgcHkgfEi8kP4d8e0Pdf324DhR6HrhS/fsrfihTRVExVkhFgzF02ZsCvw/szG
sYwu0I+jOl10bzjWVCzPZjlj8gbTvU0aJG5UdiTyUqjEKA43obTNmWSw6MgB21ZvkhPgS3Aj6lqH
LXyXtPwFy2TW9Ft4OhmPg2TmQOycOkE4CZ2JN/Uc9zTuB9540g/G4e8QVGXSkAHTRF7QWX614vTH
lQrdhwQ/r++GTh/E9jfuAvaA+3laqwiNVcyqChPrbqiTlvxYu1hAkiCR/MeKcHiDtg0VkTCFOtQ2
fNcLTDK12zgGSfhNG4fJt16eeTwtJyPDyQsweWp9WhXzO8yUXu+xzIRqEkTvIqck/oMcdxSG/tfJ
+a17blUKvDxqtp7b/+AHs8gLnXE0OXUCNwmc5HQSO6eT4DSZebEXxrPWczfIvBLYgR73EIf95fO/
//Ll83+ewFvL6sQU75CVQp2HBQfmpyuej+zfJpMk8qaDiTNxA4hDH5LYGc+i0JmFfhBMJ4Px1D/9
HTZeu8Ew5VS2Gj5muuUBg/faFEWe8qqpFuJdWhU91e/o1dUvlNcVRFRoebh93TeRXQc3SYJoEESx
Klbl3mR+Y3YLRzCtjJTxH0htQaMCgruApgPE6pGdXcPV/MrDMajcxQ1cZddwRdIUuiOwQl+YEZhX
I+0a34xAqaam4GD6woyEZgSinJqKzAj4mCXLy2tQBn7Z1qJif1MD5gozK9lzOiO31Up8zDQS4DfM
iMwJPDeIg4EfBQnUz0PsrfCPmW467FsLid1mrS4p964FXbVyda66dy3op12r4/fetaC5dq32qHvX
Qvbcro3uaWZLDyFou10b/8FawKFdK7sjWxrflht31iZ/IBeaiK1cV/L0K4K3gDPdoI4qNPDiRvYy
GqSFbETIW/QQOnfUSSzGaQs84SWZX0AKK/ssiLdQ7RNKzsoJB+YBrthGLPUtLFlCTwR6leerMhU4
j7KbOp1ga09enac6wVWm152drz5Bv1Tm1x0vDGkqyL2mHHuth+bSIARy406mDCfEjcq0dgGdtZH9
1+LvDhMIAmSk5M4EJWoibe5MpA1O7Mu7t7UKPU3oktxTcUH42cj2Ay/Bg+UluGlQlWMGTBnx3PoH
Vaq+CyqqRWi+mlVQgmD2r9Q05jlhtlWTsmpAa9CsmfSjfgDf5j8wrDoX6XJGipxBG9CHgXRJeEPh
WLr8m6+mMCKHR/aXz/9S2u2grHKP50C53Idy6exBuXS+irI0Fg8rPoVkDEiiN2yR9AYhVG/gsHVB
+C0j+c97SHqD57LXJ0QS4dNuz98gaRrYHSi9gSzI3gKU943SezbX+4RQIn4ayqADpe4rv00od1gl
OvtniaJPCCXip6EMN1B6/TCWRNw42Ddjlf/7733/+hqQRPg0klEHydANpDt9g0juSnowBXvxRon4
aSjjDpRJ7MpAf4RS9oZfBZSIn4ZysIFSFR5bCeyb8a+v1ioRPw1l0oFyMIiwRH6bWc+OBPY1OFjE
TzYfO92CeliJJeVt7wAq5XMFuK6Zu3970jYk9BLTy1HlKbDh6auXTuWuwsCrrNzNHzcd9bO7HjZ9
v6N+9hSZfox/v3Q0sDXbXbq5A28gs8Qjg/ZURDLTOjIIQtaeOiMOVGv4yKA92Tvke7I7clTQnpw4
CuOjk5Y/WrSZZje5hJ+6Nz8L4k/35n9ROPk/AAAA//8DAFBLAwQUAAYACAAAACEA3LD1Ln4EAABs
EgAAIQAAAHBwdC9zbGlkZUxheW91dHMvc2xpZGVMYXlvdXQ0LnhtbOxYXW7jNhB+L9A7EOqzYkmm
ZFtIvLAcqyiQTYJ19gCMRMfqUqJK0k68xQJ7rfY4e5IOKdFJHGdtN37MSyJTH4cz3/xwNKcfHkqG
llTIgldnjn/iOYhWGc+L6u7M+XyTun0HSUWqnDBe0TNnRaXzYfjrL6d1LFl+QVZ8oRDIqGRMzpy5
UnXc6chsTksiT3hNK3g346IkCn6Ku04uyD3ILlkn8LyoU5Kictr9Yp/9fDYrMnrOs0VJK9UIEZQR
BfrLeVFLK63eR1otqAQxZvdzldSqBmvVPb+6/dNBBieWsOI7QzA9m7IcVaSEhZt7jsa8UiDGvJL1
jaBUg6rl76Ke1tfC7LhcXgtU5FpCu9PptC9amPlZAQweOhvb76wkEj/MRDk8JTEwgR7OHHDYSv+F
TSSmDwplzWL2uJrNr7Zgs/lkC7pjDwAN1oeCr+vGopfmBNacm0Ixivy1VQ2UwNYLnn2RqOJgpza/
MS+7XFph2mYtvp6jlnYtqsU1Lw0fFi+BU0OWekh4vtKG38J/s0hiJtVUrRg1hIDaJAbh8AfoZ0RH
Na3cz1OI6lKNGSUQ9S15ajhmRfYFKY5oXij0kUhFBVLGLqlFngI7CpzTiqRVfk0E+bQhWdtHYjgZ
lLYawmND4etEdi2RbTSha0YyOucsByWCt9Eqv0I2EDZzIAIhPKwPXuFW07URZTjsQb6aUPMjz9PP
hl8bcNjr9mHdQTrscBiEg6hrHGglGQIaN1tOtnpNn82WzDdpQ+KczjS9Wv+g3xwK3D4BwGOwBYuf
Yi0AsN0tWO8p1gIAi19i/Wc6WABgw11YCwBstAtrAYDt7cJaAGD7u7AWANjBLmwD0Fy36aQdY7IJ
diKQsE6bN2aXjiCTXPJZdjUZtHmkCdwDEnpKM17liNElZXuIN1l2gPibeSH2l24S4gDpKV8INd9b
edxk5N7uSIvZVulwixy1ruGf1TXDCdyn9jI48LrYqGvGf+aq0JXGPDy9M7bVtQj33wsb3AjvhS1+
L2zrRui9sO3RsIW2sJ0TRZ91a6YU//+q1jTBuYIedaNvMw56vcAd0hTP4AtGf478HU6S0QgPUhdj
b+ziMAndJBgHrj/peTgYJR4ehd+ctjPPwVRVlDQt7haCXi30Nw9caRsd8LbeOvD80PVArPd4EYMO
evtx75vIuiXlXPfvT9vo8G1tdOOYmRKNZ/5aEAEn2KZ6R1d9iHOOy0jPMjJlRU7R5aK83eAlOgYv
MA8A0Vup2XExH0LNOm67512cRkHojqJk4mJ/gN3BJOm5kwRPBmnQC8Jeuo5bqS2vQLt9w/XH939+
+/H93yPEqqkkdiYA3e6FhE/I2nyqL0QBCZgkgygY9xM38TFk4fmg547SKHTTsIvxOOmPxt3JN1C8
9nGcCWqGFX/k7dAEFl8MOsoiE1zymTrJeNlpJiadmt9TUfPCDE18r528LAk08tjrR4HfG3RNGIC+
oKVpn6y2sKQnHlrtjImPpL5aQn9FYpjxQPyPzVINUx3wo4Y+QrTtdko0/A8AAP//AwBQSwMEFAAG
AAgAAAAhAMkd9nTbBQAAOxwAACEAAABwcHQvc2xpZGVMYXlvdXRzL3NsaWRlTGF5b3V0NS54bWzs
Wd1uo0YUvq/Ud0D0mjX/2FaclXHsqlI2iRrvA4xhHNMFhg5jJ2m10r5W+zj7JD1nYGz8t0ucXKxU
39gYf3ycnzkfhzMX75+yVFtRXiYsH+jWO1PXaB6xOMkfBvrH6cTo6lopSB6TlOV0oD/TUn9/+fNP
F0W/TONr8syWQgOOvOyTgb4Qouh3OmW0oBkp37GC5vDfnPGMCPjJHzoxJ4/AnaUd2zT9TkaSXK+v
522uZ/N5EtErFi0zmouKhNOUCLC/XCRFqdiKNmwFpyXQyKu3TRLPBXgrHtn0afrIbmd/6JoE8xWc
tvRL8D+6T2MtJxmcGLGsIDwpWS7/KYsppxQx+epXXtwXd1xecLO641oSI0F9od6p/6hh8mcOMDjo
7Fz+oJhI/2nOs8sL0odoaE8DHZL2jJ9wEenTJ6FF1cloczZa3B7ARovxAXRH3QAsWN8U8l1UHu27
Yyt3polIqWatvaqgBC69ZtGnUssZ+InuV+5FNytFhj4jfbHQ6tAjVY2r/pTxUPgSYiqDJZ5CFj+j
4zP4lidJPy3FvXhOIQVwvEotmQDSj+n89yq0jdPgbRMOTpI+mAIfkKyUYB3Q3Ph4D3WQiVFKCdRJ
HWpxOUqT6JMmmEbjRGgfSCko14SMQokGXAC7gFTWlDSP7wgnYMQWM0aD9OHO4KLyBw6rgB8Pu7MO
O+b8LiURXbA0Bgvst8gAxlOH5QprSSXsSCIwWjtL0vUCKHC5Li3P8SzLQZM2q9M1XdPqgrjgGvWd
XuBLmyEMFZF0v1oSKiIqwxrJowUDtZhVlM3s1cnWMsKvZV0keQwFjod499nyBlRMGlKtBa38a6Db
Llo6U2421oY8tGH11ITKq1as5j4rUqEdYKazYe1ZrrSgDavV3WdFqprV3bBaTmD5CG5FK5HbIUCu
mtZr0HbtrrThVFrkqmn9Da1td8GEV1iLXDVt0KANXEeuw1OtRa6atruhRc72KTsQW+SqaXsNWt8L
XpUy5JJa0qwJqWh4E1h1a+mSdz9d4VBwpMCVWwp3ioq5SsVGLBdQq1tCJlUDHrXqQfHCRwlW94Kk
81rGKonBx6oMEx40nyeYkOMyZluB2w28b8iY0/MsKA5EtNExKUPNRO09qTbqVFE2AHCoxKSpZFhC
a6wCAFZJRAMrlWSNVQDAqrpvYnFVrrEKAFhVzEexCgBYVaFHsQoAWFV2R7EKAFhVS0exCgDYqkBU
JyDjK0Vy7duPUUGyGYAPVbTy+fuCtuSeRiyPtZSuaHqgQHfpZV28gH66SHh79vrJ31pxJmzJxaK1
8W5Vke3pk/lBduhN3rQ785SuTXe7M2nx6aJW9cdVd4YC9+eScGg7a42T0ZatcmuN813PtMFc6MSO
9WpWAMp37tUG+rlXg3753KsNdOf/2Kv5StMO9WqyNTpd1valTOrkyVJ2rF/bSNm5X8OYb/c/537t
yEznm288uw3VuV/DEVr1Nrgbmx+1XwuUtl0RQbdeQn3sME8XtqpfiwUMELdfR63qnero+6i86+70
C05uBpbyh3y/n8MsGifLf3vjcDh0exMDZkojw/VCzwjtkW1Y48B07WFoukPvs14PWWNwVSQZnSQP
S05vl0JH9jZjAdu0PMMEWnPzfgE24OVv20bDiLCasU8Yw+Fqc8wZvEVi5gJa5/2Hj/WdmedLkvO2
EempiNynSUy1m2U224mLHEG8dsHC9g5QHwzNd+YoLwnNet06V4478W3PGPrh2HCtnmv0xmFgjEN3
3JvYge0Fk/W6LdHzHKxru1y/fvnnl69f/n2DtSoH02p7Bx4K1yXM9wu567LkCRRgGPZ8e9QNjdBy
oQqveoExnPieMfEc1x2F3eHIGX8GwwvL7Uecyr2n3+J6DwxO7u1bZUnEWcnm4l3Esk61AdYp2CPl
BUvkHphl1htpKwITPqvndK1uENSTKGmb3FpQ1oILuHclNS3lH0hxuwK1Jn3YsoMKG8lTBWzSQR4R
uoGg72rT7/I/AAAA//8DAFBLAwQUAAYACAAAACEAOGDKsUEDAAC9CAAAIQAAAHBwdC9zbGlkZUxh
eW91dHMvc2xpZGVMYXlvdXQ2LnhtbKxW/27TMBD+H4l3sMLfWX7Uaddo7dR0DUIa20THA3iOu0Zz
bGO7pQUh8VrwODwJZyfZYBvSJPpPm9h3n+/77s6Xk9Ndw9GWaVNLMQmSozhATFBZ1eJ2Eny8LsPj
ABlLREW4FGwS7JkJTqevX52o3PDqnOzlxiLAECYnk2BtrcqjyNA1a4g5kooJ2FtJ3RALr/o2qjT5
DNgNj9I4HkYNqUXQ+euX+MvVqqbsTNJNw4RtQTTjxEL8Zl0r06Opl6ApzQzAeO+/Q7J7BWxtbTm7
FHwfIG+qt7CYBFNgT5e8QoI0sHDtrJA3cztGXWvG3JPYvtVqqa60d7jYXmlUVw6gcwyibqMz868C
zOAheuR+2yORfLfSzfSE5KAF2k0CSNne/YITydnOItou0odVur58xpauF89YR/0BEMH9oY5Vy+gp
nbSn0+qQ3LNqTQm4nkt6Z5CQwNPRb+nRi20P5jg7eLVGfwjf2bWbXo/e3oCmXiy7K2S1d8Rv4N8v
kpwbu7R7zrwgEDbJARx+QH5OXF0zEX5cQl03ds4ZgbrvxLPTOa/pHbISsaq26D0xlmnkqwC6ACBP
QB0LyekgmaiuiCYfHiE7fiSHkyHoPkJ4bCX8t5CDXsgzYhm64oSyteQVRJAeQtPKAuUv0BaErwIo
RKiSxBP30roE/JfGK+gHV91fs0Uxm+FxGWIcz0OcFVlYpPM0TBajGKezIsaz7FvQJboCqrZuWFnf
bjS73NjgpalK4yQLY4CNH5ICMTj3w6YF92kppXTl8GdiBodIzMrqNjOfNkTDCX1y+kY5QAMcVpGs
V2TJ64qhi01z80gXfAhdYMAA9LPS+IY4cN0Ozga4HKZZOBsWixAnYxyOF8UoXBR4MS7TUZqNyvu6
NY65gOheWq6/vv948+v7zwPUqr9J+hED9/25gRtJ+Zt/o2towKIYD9P5cREWCYYuPBuPwlk5zMIy
G2A8L45n88HiGwSuEpxTzfz0e1d1UxgWn0zOpqZaGrmyR1Q2UTuCIyU/M61k7adwEnejfEs4XCuj
AT6OcRz3FQxR+tuljxYouPnpwqZcvyfqcgvXD8nhowHqf+6XFHwmdIPiwcRx7z87pr8BAAD//wMA
UEsDBBQABgAIAAAAIQA8blmfzgMAANALAAAiAAAAcHB0L3NsaWRlTGF5b3V0cy9zbGlkZUxheW91
dDEwLnhtbKxWwW7bOBC9L7D/QGjPimRZsmMhdmE5VrFAmgS12ztL0RFRSlRJWrVbFOhvdT+nX7JD
Skyb1AWcxhfZomYeZ94MH+fixa7iqKVSMVFPvcFZ6CFaE1Gw+m7qvVnn/rmHlMZ1gbmo6dTbU+W9
mP3910WTKl5c4b3YagQYtUrx1Cu1btIgUKSkFVZnoqE1fNsIWWENr/IuKCT+CNgVD6IwHAUVZrXX
+8tj/MVmwwi9FGRb0Vp3IJJyrCF+VbJGObTmGLRGUgUw1vthSHrfQLZAjF7vPGTtZAsrA28GqZMV
L1CNK1hYM80pAoLQWzBmBHO0pjttzVSzlpQah7p9KZtVcyut93V7KxErDFqP4gX9h97MvtZgBn+C
R+53Dgmnu42sZhc4BVbQbupB8fbmCU44hSAQ6RbJj1VS3hywJeXygHXgNoAI7jeFujddRr+mE7l0
OlIG91l1phhcrwR5r1AtIE+TfpceuW4dmMnZwDcl6kqgDb+9XffR8uHsFXBqydK7TBR7k/g7+LWL
OOVKr/SeU0sIhI1TAIcH0M+x6XBa+29W0OGVXnCK4QT05OnZgjPyHmmBaME0eoWVphLZYOA8AOQF
sKOhOD0krYtbLPHrR8gmP5zCzhC0ixD+dhT+nsihI/JBT6FbjgktBS8glOgU5BqqPCQkg0PQdbsH
fQlN4yrzFMaNjAAKxSZoE90h/qFciLf8nuhn1sM0uS2HelCPjnNLPDzcljapJ7TAihIB55rTlvIj
4G1FngC/Lpk8Hn3YMXo0X7nYSl0eHXz8VHi2OYgOunPSkxC7k3CJNX1wACwhIMVOO/5IXQoNh/8T
XBWYb1zrWwmwImOk6Flqs4Frwuj852SZzefxJPfjOFz4cZIlfhYtIn+wHIdxNM/CeJ588XrJKyBV
zSqas7utpDdbc5kcJ1pROEj8EGDDH/0KMRj305YlcWXJhTDC+LMy2VZ6bmE2WnaV+bDFEnZwxfkT
YfqNFJ2WkZFjZMVZQdH1tnr3iJfkFIoNQxdAH6TG6s+J+3Z4OYzzUZT481G29OPBJPYny2zsL7N4
OcmjcZSM8/u+VSbzGqI7tl2/f/32z/ev/52gV+2d6oYtuBSuFNzNjZ2BtpLBAcyyyShanGd+Nojh
FF5Oxv48HyV+ngzjeJGdzxfD5RcIvBnEKZHUToT/Fv1kCou/TJMVI1IosdFnRFRBN5YGjfhIZSOY
nUwHYT/ethjuuziOotF4PB6ZLoBwIUj3a4OFJTNVmqgJl69wc9OC+uAU5mho/4VdamBy7rx/MjGp
u0l89j8AAAD//wMAUEsDBBQABgAIAAAAIQA6Cnq2FwUAADUSAAAhAAAAcHB0L3NsaWRlTGF5b3V0
cy9zbGlkZUxheW91dDkueG1srFjrbuI4FP6/0r6Dlf2dEodcICodEQqrlTpttXQewE1MiSa3dQyF
WY00r7X7OPMke44TA2npDmXypwVz/Plcv3Psyw+bLCVrLqqkyEcGvbAMwvOoiJP8aWR8epiZA4NU
kuUxS4ucj4wtr4wPV7/+clkGVRrfsG2xkgQw8ipgI2MpZRn0elW05BmrLoqS5/DbohAZk/BVPPVi
wZ4BO0t7tmV5vYwludHsF6fsLxaLJOLXRbTKeC5rEMFTJkH/apmUlUYrT0ErBa8ARu1uqyS3JVhb
JtHDxiBKTKxhgRpXYHk0T2OSswwW7pNIrgQnz4lckgkrUQ8lU5UPgnOUzte/i3Je3gu19XZ9L0gS
I1QDYfSaHxox9TUHMfjQe7H9SSOxYLMQ2dUlC8AjZDMyIHBb/AubWMA3kkT1YrRfjZZ3R2Sj5fSI
dE8fABrsDoWYl7VFr82xtTkPiUw5oTuralEGW2+K6HNF8gLsRPNr86LbtQZDmxG+XJLa/RKhGrn6
R+UPLV8pn2pFd56g/tC2B5C3YLkzgCyzXnjFdQaeA4sEfeN6nt8fqEM0EhxSQ5eB3IRFvEWXPsJ/
iBzLo2UBmfqIO1iQVnIutynEGT6vUwoaEZY+QSmlkAUsiPniT1iqvowMyHc48lFbvpOHILdxwMUs
AEfAH9iaMqxEnpuf5lCJmZyknAF8Y5K8mqRJ9JnIgvA4keQjqyQXRDkO6hY0Q3SpzlCQPI/vmWCo
1CEyxoIFcDLYrm1WbsB4vB30vg66LoP7lEV8WaQxKGGji6BYdIDPSgGoQAPKBXJZJ8x5ieBR2/fd
Omi6Olp54FCKyXJqIrwZ/YyJG1WNSR4DteBHDOXj6hb4U+06yIk+JEVzYpM9KAsfbUykGspxfZQi
p+DZewsakAavv8cbUkcl/0l4KFnnBuAhSIPn7PFo36dYYqcpiEWwA0SUBtA9ABxA9Z4HiCgNoLcH
BDYABc/SEFEaQP8A0HdU5M4wGVEawMEeENFOD0rLh4jSAA4PAD3XPzMoiHKck7rlDkdzxwPW4yFx
9DFDfpY4kK+BMIF4lyxdNByiKEn1EGUjNte5Mlczvm4BR5uJ24dWUfeKfYttkcjAgtZSH6KR/qeZ
KDY41kHexSG0VaPYgZp0OJNDaIuTEKTBO5NDaCtdO+CQYccU0sLrgEFaeB0QSAuvA/5o4XVAHy28
t9kDEolAE9mNLiqtzp9wkDTUgFO1JpxzphhXM9E1k7zFRE4XTBTLVzxE6yaI/HOUiBT/6TlMz54t
ulBf1KS4gLsI3if+dqfheOwMZyb094npuKFrhvbENunUtxx7HFrO2P1qNKN1DKbKJOOz5AmuL3cr
aWCVnxIO26KuaQGstXc86IDbu20Qng7LrChwqD1sEWqS+9kWsZCijsxfKybgBD1o/mDSfE9wuvWI
rz0yT5OYk9tV9vjCL14XCQsXe4A+6pofNND3uGaXt/3rvjPzbNcce+HUdOjQMYfT0DenoTMdzmzf
dv3ZLm8rtDwH7U5N1+/f/vnt+7d/O8hV1cn1pR7o56aCe1Wp7torkUABhuHQsyeD0AypA1V4PfTN
8cxzzZnbd5xJOBhP+tOvoHhJnSASXL06/BE3rx+w+OrFIksiUVTFQl5ERdarnz56ZfHMRVkk6vWD
Ws0TypoBs9qUWp7tDIZqggJ9QUt1pdPawhK+XajpKhUfWXm3VjQMjzWQ/xO1VMLzDMQRRfciaLt+
7rn6DwAA//8DAFBLAwQUAAYACAAAACEAhDlft1YFAADFEgAAIQAAAHBwdC9zbGlkZUxheW91dHMv
c2xpZGVMYXlvdXQ4LnhtbMxY3XLiNhS+70zfQeNeO1j+BU/IDibQ6Uw2yRT2AYQtgru25cqCQDs7
s6/VPs4+SY9ki7+wi0ly0Rsw4tOn83+Odf1hnWdoRXmVsqJv4CvLQLSIWZIWT33j03Rsdg1UCVIk
JGMF7RsbWhkfbn7+6boMqyy5Ixu2FAg4iiokfWMhRBl2OlW8oDmprlhJC/hvznhOBPzkT52Ek2fg
zrOObVl+JydpYTT7eZv9bD5PY3rL4mVOC1GTcJoRAfJXi7SsNFvZhq3ktAIatftQJLEpQVs2+2O6
NpCC8RUsYOMGNI8nWYIKksPCkBUCGNBzKhZoSEoph8JU5ZRTKtHF6ldeTspHrrberx45ShNJ1VAY
neaPBqZ+FgCDh87R9ifNRML1nOc31yQEi6B13wDHbeQnbCIhXQsU14vxbjVePJzAxovRCXRHHwAS
bA8Fn5e1Ri/VsbU601RkFOGtVjWUwNY7Fn+uUMFAT6l+rV58v9JkUmdJXy5QbX4hqRpc/aeyh8ZX
yqZa0K0lXC+A2FLmsAPH8o5s4lhW18GOgaRlMPbtBrGvcc1chmIdsWQjLTqDb3AcKeIFg0Cd1XbO
KjERmwzcTMJslWEQCJHsCTIpgyAgYULnv8NS9VffAJFApplWfIsHH8PzHg9YmIRgB/iArRmRiUgL
89MEEjEXw4wSoG90EjfDLI0/I8EQTVKBPpJKUI6U3SBtQTLJLtQZipIWySPhRAq1zyxdQUI4Geyr
dYbH2tvf9zkY8TALHjMS0wXLEhDCflsEpAnErw6S9s53vMCTDpXJcMr7HsYYELX3va7nYAiFWv06
oZTadRxqS2jvq9Tad1Xj8iNPOzL6aso9ADzaTbzuR0V3H6sBgHVOYN19rAYA1j2BldG2lUEDAOud
w2oAYP1zWA0AbHAOqwGA7Z7DagBge+ewNeBUDsFOBAzbZHljTsmaqlKqOsipOm9U8sCHPlIF7gVp
PKExKxKU0RXNWtCr3LqAfrpIeXt2lRAXsI/ZkkP3ayu8KwPzEvp0fpId2ty7VjNXV7OpdPV+KVMG
gbavW9WrmpnsIFDCoRUsSDY3YAaAAqccqZqaLDnqYaIiXhZfufSj7oZdx8N1nu9a/kF7c/0etvw3
FziUE36nRoy0SGDakY9StNnyHoZC5c29moYP6pTsiRILmSjLW0Ole3QrvoN6elQjG74eduWpqBXf
QW08qqMNH3YC7Lcl7P2g1mq+rt2Vpb6VgAd8R/W44bPtLoj3Gr6jmq35Ale1rcvlO6rrDZ8ka+2Q
A32Par/m873gdf74f/QHyGw9TagBQ46535+rPF2JbomgB5VI1c63VqJEvKhDuJ4W5NvGyUIEOb7T
4OQ8pKqAml3n8HIkX3D+9kbRYOD2xibk5tB0vcgzI3tom3gUWK49iCx34H0xmlk/AVVFmtNx+rTk
9GEpVIVpMwLbFvZMC2itXecEGWTRed8G4Wu3jBmTY/Z+i/BkU3urY+aC1575c0k4nNA0CXxmDL7E
Oe9rkUBbZJKlCUX3y3x2ZBf/PewCNw1AfdI0ZxroJabZxq1z67hj3/bMgR+NTBf3XLM3igJzFLmj
3tgObC8Yb+O2kpoXIJ2Mtzbh+u3rP798+/rvO8SqqiT6lgFmlrsK3vRK9fK/5CkkYBT1fHvYjcwI
u5CFt73AHIx9zxx7jusOo+5g6Iy+gOAldsOYU3UN8lvSXMfA4osrlDyNOavYXFzFLO/UdzGdkj1T
XrJUXcdgq7nTWRGYvB3fhxHEdusJRImmphwtLGgg71JU5mT8IykfVmpYgMsjCP+hWirhugjcKKE7
iFRdXz/d/AcAAP//AwBQSwMEFAAGAAgAAAAhAHToxsMQAwAAawcAACEAAABwcHQvc2xpZGVMYXlv
dXRzL3NsaWRlTGF5b3V0Ny54bWysVf9u2jAQ/n/S3iHK/k7zAwdKBFQEyDSpa9FoH8B1HIjq2J5t
GGyq1NfaHqdPsouTtFvbSZWGkIJzuTvf933n8+hsXzFnR5UuBR+74UngOpQTkZd8PXavrzLv1HW0
wTzHTHA6dg9Uu2eT9+9GMtEsP8cHsTUO5OA6wWN3Y4xMfF+TDa2wPhGScvhWCFVhA69q7ecKf4Pc
FfOjIOj7FS6528art8SLoigJnQuyrSg3TRJFGTZQv96UUnfZ5FuySUU1pLHRf5dkDhLQ3jDMb13H
uqkdGEJ3AsjJiuUOxxUYUutRG7W8UpTWK777qORKLpX1vdgtlVPmdWwb4/rth9bNvnJwg4X/LHzd
ZcLJvlDVZIQToMDZj11Q6lA/IQgndG8c0hjJk5VsLl/xJZvFK95+twFU8LhpjapB9BJO1MGZY0Od
JcOEbgTLqXLCR4BNFIYs54LcaocLgFwz0SAlF7subw2/3klunIb63EDjfQcRMStc4A/AhRasZah2
tosuXgPdlkezT0V+qDm5gX9rxAnTZmUOjFquABFOClCwFuVHvEinUzTMPISCmYfiNPbSaBZ54WIQ
oGiaBmga37ldUQDVlBXNyvVW0cutgXbAiQKBoQ3gwFDuXa+g7srMGMVwoFp5zCQKwtgLIG0wAqYN
VG9rsNrxfIkV/vIsS00RTqBYwNmBgmUjyL9l6XWyZEIYEONPYaJjCFMY1SjzdYsV7NCJ04naKPlf
4tCjMoI6RlaszKlzsa1unvHSOwYvMA4h9avUWN4tI8fr2968h7J+FHvTfrrwUDhE3nCRDrxFihbD
LBpE8SB77FtdI+dQ3Vvb9eH+54eH+19H6FXbst1khDF1rqH5pR1YW1XCAUzTYT+anaZeGiI4hfPh
wJtm/djL4h5Cs/R0Oust7qBwGaKEKGpn9ae8vTPA+GLOVyVRQovCnBBR+c2F4UvxjSopSntnhEF7
8ewwG7sRigLUj+DXjiWo0p66rlqAUE/8umzC1GcsL3cwfnACVxz0/8yaJFxq7VB7cqmxd5fk5DcA
AAD//wMAUEsDBBQABgAIAAAAIQDV0ZLxvgAAADcBAAAsAAAAcHB0L3NsaWRlTGF5b3V0cy9fcmVs
cy9zbGlkZUxheW91dDUueG1sLnJlbHOEj8EKwjAQRO+C/xD2btJ6EJGmXkTw4EX0A5Zk2wbbJGSj
6N+bYwXB4+wwb3aa/WsaxZMSu+A11LICQd4E63yv4XY9rrYgOKO3OAZPGt7EsG+Xi+ZCI+YS4sFF
FoXiWcOQc9wpxWagCVmGSL44XUgT5iJTryKaO/ak1lW1UWnOgPaLKU5WQzrZGsT1HUvzf3boOmfo
EMxjIp9/VCgenaUzcqZUsJh6yhqknN95LmpZ3gfVNuprbvsBAAD//wMAUEsDBBQABgAIAAAAIQC5
f+5zlgYAALAbAAAUAAAAcHB0L3RoZW1lL3RoZW1lMS54bWzsWU9v2zYUvw/YdyB0b2MndhoHdYrY
sZutTRvEboceaYmWWFOiQNJJfRva44ABw7phlwG77TBsK9ACu3SfJluHrQP6FfZISrIYy0jSBtuw
xYdEIn98/9/jI3X9xqOYoUMiJOVJ26tfrXmIJD4PaBK2vXvD/pUND0mFkwAznpC2NyPSu7H1/nvX
8aaKSEwQrE/kJm57kVLp5sqK9GEYy6s8JQnMjbmIsYJXEa4EAh8B3ZitrNZq6ysxpomHEhwD2bvj
MfUJGmqS3lZOvMfgNVFSD/hMDDRp4qww2GBS1wg5k10m0CFmbQ/4BPxoSB4pDzEsFUy0vZr5eStb
11fwZraIqSVrS+v65petyxYEk1XDU4Sjgmm932hd2ynoGwBTi7her9ft1Qt6BoB9HzS1spRpNvob
9U5OswSyj4u0u7VmreHiS/TXFmRudTqdZiuTxRI1IPvYWMBv1NYb26sO3oAsvrmAb3S2u911B29A
Fr++gO9fa603XLwBRYwmkwW0dmi/n1EvIGPOdivhGwDfqGXwOQqioYguzWLME7Us1mL8kIs+ADSQ
YUUTpGYpGWMforiLGR0JqhngTYJLM3bIlwtDmheSvqCpansfphgyYk7vzcvv37x8jt68fHb8+MXx
45+Onzw5fvyjpeUs3MVJWF74+tvP/vz6Y/TH829eP/2iGi/L+F9/+OSXnz+vBkIGzSV69eWz3148
e/XVp79/97QCvi3wqAwf0phIdIccoQMeg27GMK7kZCTOt2IYYVpesZ2EEidYc6mg31ORg74zwwxX
4DrEteB9ARWkCnhz+tAReBCJqcpc7mh2K4od4B7nrMNFpRVuaV4lMw+nSVjNXEzLuAOMD6t4d3Hi
+Lc3TaF00iqS3Yg4Yu4znCgckoQopOf4hJAKez2g1LHrHvUFl3ys0AOKOphWmmRIR040zRft0hj8
MqsSEPzt2GbvPupwVqX1Djl0kZAVmFUIPyTMMeNNPFU4riI5xDErG/w2VlGVkIOZ8Mu4nlTg6ZAw
jnoBkbJqzV0B+pacfguqR7Xb99gsdpFC0UkVzduY8zJyh0+6EY7TKuyAJlEZ+4GcQIhitM9VFXyP
uxmi38EPOFnq7vuUOO4+vRrco6Ej0jxA9MxUVPjyJuFO/A5mbIyJKTVQ151yHdPksnafuXZvC1qZ
PLsnKvYy3Mk63eUioP/+Mr2Dp8k+gcxY3Ksuq/Rllfb+81V6WT5ffG2el2Oo1Lp3sk23acHjpR34
mDI2UDNGbkvThEvYhII+DOp15vRJihNZGsGjzmRg4OBCgc0aJLj6iKpoEOEUGvi6p4mEMiMdSpRy
CQdHM1xJW+PhEKDssbOpDyS2ckis9nhgh9f0cH7uKMgYqUJzuM0ZrWkCZ2W2di0jCrq9DbO6FurM
3OpGNFMUHW6FytrE5oAOJi9Ug8HCmtDdIOiJwMrrcP7XrOHggxkJtN2tj3K3GC9cpItkhAOS+Ujr
veijunFSHisLimg9bDDoQ+QpVitxa2my78DtLE4qs2ssYZd77128lEfw3EtA7WQ6sqScnCxBR22v
1VxtesjHadsbw5kZHuMUvC51Q4lZCBdPvhI27E9NZpPlc2+2csXcJKjDNYi1+4LCTh1IhVQ7WEY2
NMxUFgIs0Zys/KtNMOtFKVBRjc4mxdoGBMM/JgXY0XUtGY+Jr8rOLo1o29nXrJTyqSJiEAVHaMSm
4gCD+3Wogj4BlXD1YSqCfoF7Om1tM+UW5yzpyrdjBmfHMUsjnJVbnaJ5Jlu4KUiFDOatJB7oVim7
Ue78qpiUvyBVymH8P1NF7ydwDbEWaA/4cE0sMNKZ0va4UBGHKpRG1O8LaBxM7YBogbtemIaggstq
81+QQ/3f5pylYdIaTpPqgIZIUNiPVCQI2YeyZKLvFGL1bO+yJFlGyERUSVyZWrFH5JCwoa6B63pv
91AEoW6qSVYGDO5k/LnvWQaNQt3klPPNqWTF3mtz4O/ufGwyg1JuHTYNTW7/QsSiPZjvqna9WZ7v
vWVF9MS8zWrkWQHMSltBK0v7txThnFutrVgLGq82c+HAi4saw2DREKVwmYT0H9j/qPCZ/fKhN9Qh
P4DaiuBDhiYGYQNRfcU2HkgXSDs4gsbJDtpg0qSsabPWSVst36wvuNMt+J4wtpbsLP4+p7GL5sxl
5+TiRRo7s7Bjazu21NTg2ZMpCkPj/CBjHGM+mZW/avHRQ3D0Dnw/mDIlTTDBNyuBoYcemDyA5Lcc
zdKtvwAAAP//AwBQSwMECgAAAAAAAAAhAOpbAisAMAAAADAAABcAAABkb2NQcm9wcy90aHVtYm5h
aWwuanBlZ//Y/+AAEEpGSUYAAQEBAGAAYAAA/9sAQwABAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB
AQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB/9sAQwEBAQEBAQEBAQEBAQEB
AQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB/8AAEQgA
wAEAAwEiAAIRAQMRAf/EAB8AAAEFAQEBAQEBAAAAAAAAAAABAgMEBQYHCAkKC//EALUQAAIBAwMC
BAMFBQQEAAABfQECAwAEEQUSITFBBhNRYQcicRQygZGhCCNCscEVUtHwJDNicoIJChYXGBkaJSYn
KCkqNDU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6g4SFhoeIiYqSk5SVlpeY
mZqio6Slpqeoqaqys7S1tre4ubrCw8TFxsfIycrS09TV1tfY2drh4uPk5ebn6Onq8fLz9PX29/j5
+v/EAB8BAAMBAQEBAQEBAQEAAAAAAAABAgMEBQYHCAkKC//EALURAAIBAgQEAwQHBQQEAAECdwAB
AgMRBAUhMQYSQVEHYXETIjKBCBRCkaGxwQkjM1LwFWJy0QoWJDThJfEXGBkaJicoKSo1Njc4OTpD
REVGR0hJSlNUVVZXWFlaY2RlZmdoaWpzdHV2d3h5eoKDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ip
qrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uLj5OXm5+jp6vLz9PX29/j5+v/aAAwDAQACEQMR
AD8A/v4ooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooA
KKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAo
oooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACii
igAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKK
ACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigArxX9pPxb4h8Afs6/Hzx34
S1D+yfFfgr4K/FPxb4Z1X7JZX/8AZniHw54G13WNF1D7DqdteabefY9Ss7a5+yahZ3djceX5N3bT
wPJE3tVec/GL4f8A/C2fhH8U/hZ/a39gf8LL+HPjf4f/ANu/YP7V/sX/AITLwzqfhz+1v7L+26b/
AGl/Zv8AaX2z7B/aNh9s8n7P9ttfM8+Py88pY2vkucUcudSOYVsrzClgHRqrD1VjamErQwrpV3Om
qFRV3BwrOpTVOVpuceXmXflVTDUs0y2rjVB4Onj8HPFqpTdam8NDEU5V1UpKM3Vg6SnzU1CbnG8V
GV7P8DvH37Ynxx1fx9/wT28KeL/2p/2yfg/4X+NP/BNKy/aM+I2pfsUfsZ+EP2o/iJ43+Nkmo/Au
ybWvEvhPTP2G/wBsbUfBPg+Wy8beKp55dC8D+B/CUOsXOk6eNSglk03S7r6Q/bh0f9qL4X2X7I3i
L4Wf8FFP2u/CVn8Zv2lf2VP2a/Fek3nwn/YKf7T4Z+IaSaD4w+Ibab43/YTvfEnh74r+I304eItT
sriSy8EaD4j1DUbLSfhj4f0WGz8Nad6fN+wN+0H4B8a/sq/Eb9nP9p34N+C/Fv7OH7F0H7GesD41
/sq+NvjT4d8f+H4tQ+F2rSeN9M0nwL+1v+z5qfgnWJNQ+F9iU0q68QeNbKKz1W7t2uJZ4Ibw/TPx
w/Zn8V/tBeDf2YtM8d/Ezw9YeNvgP+0F8Bv2h/F3iPwl8NtS0vwt8QvEnweubjUNa0Pw54N1j4le
I9W+Hmh+MNRu7h9LOp+O/iNf+ErLybS7uvF08b3030eMlhKmMwE6HLHDQ4/jjMZGEJ0VPhar4m5v
jqqcLTdXBw4GxGEpRwVOWGq0cKsPl1HLamMwsPYfNYOGYUssxtOs5yxs+CFhMI51KdaceJKfh7lO
Eg1Vcowp4uXGOGxVSeMqfWIVsRKvjqmYU8HiqirfmH+0t8dtY/Z//bF+EH7MPx7/AOCwnjv9k74U
f8Mc+Kvio/xn+Jd9/wAE0fhn43+M/wAXIvjva+G7Kx13XvjT+yNdfCppdJ8D6ld21r4b+Fnw/wDA
8ktjolrq+qQ6hex6tqN/9xftvfFT41fs5/s+fCf9pz4TfEPVPiJ8Pv2ePFfgTx3+1Jpdxonw61rU
Pj3+ylcaLN4Z+MHjqHVND8JaTYaH4u+HOi61B+0pp138MF8DeH9f/wCFfav4STSv+Eb8RW+lWvvk
v7OHmftnWX7XX/CZY+x/sxan+zh/wr3/AIR3Pmf2l8VdI+Jv/CZf8JZ/bg2eT/ZX9if8I9/wjTeZ
5/8AaX9uJ5X2CT1f4xfD/wD4Wz8I/in8LP7W/sD/AIWX8OfG/wAP/wC3fsH9q/2L/wAJl4Z1Pw5/
a39l/bdN/tL+zf7S+2fYP7RsPtnk/Z/ttr5nnx+LKrjcPkNKrRoU8bnmHxWdZosJUdOnSxlbD8X8
R5lkuV4ytKSg8DmGTzybB1aeFxODoYfK6scBONDE4X2mG9qjSoVc6xMa9Wphsnr0sty/28XOpOhh
cTwvkGAzfHYSnFc9HF4TM4ZxXo1q1DEYz+0YyzDC1vZ14e2/IaD9rL9pj4sfs6y/FP4e/EObwTrv
/BQv9qfw18Hf+Cd1t/whXgW8vvg9+zjPaSpc/tGtpXiDwxq6eP8AxD4m+Dvw4+MP7X+jaN8Qo9c8
PReHtU+HHge60bSorfXU1Hyf48/tgftteKP+CdH7NN7+z/8AFzwx8O/27L/9sf4Y/sTfGfxXr3w4
8Ja54T1D44+CPGniv4ZfFrTdZ8E+INGudM0Dwf8AFTxT4Qt/EVld+GY9N1TQ/BPjDTNS8KapaEWz
P9uX/wDwTB+E3xFn/ZC8P/tJj4e/tL/Bf9kL9l9/gh4a+BXxX+C3hnxV8OvF3xWuNN+GHhp/2h9e
0DxjrHjDw9/wkOjeDfh1f+GfBPh248PandeEIPH/AI0urXxjePqXlDhrH/gkz4D8D+Nb9PgZ4s8D
fAr4Af8ADYX7L37Z/hj9nT4efA3SPD/g/wAD/Eb4E+Hm8LfETSfCh8NeNPDfhrRNB+Num6N4H1G5
g0vwJYDwf4q0TxL4imh8ZTeMpLXRO6rQowxdLD0MZW+of6x8PcmPUIVcdDIuH+Kchy+NTHUsTS+q
uGY8M4XifiPNqWGwuKxGfV86yzL83ozll1PKcFyRr4meAq4p4SnTzRcPZ1N5dOaeAee51kmc4z6t
gKlGpGtOOXZzi+Gsly2tj8VRp5RRyLOMXgMTXebRzPEeBWv/AAVtkvvEPiL9oGF9Sg+A3w9/4JSf
Gz9qz4j/ALP2oWXhvTPFfhL9pL4FfGwfD74j/DDxD4nudFk8QaR4x8GeIND8U/CPU7FtTk8JNqts
fEEGmX8T2Gpy+qeBvHHxI8F+NP2c4v2of+Cw/wANPh5+1Z8aP+FeeP5/2HdT0j9i/wAK/BHxfoXj
3W/sV58L/gp8NfEvhDQ/23vEdobRNY8EfDr4jN+074l1G/8AidokXi7V/DniXw/BqnwauOy0v/gk
b8H7P9sj9sT9pHUvF+oa98H/ANtn9nnxJ8Ffiv8Asu6hoLx+FbLxJ8RL/wAPH4tfEXwv4wtPEcFx
o6fE/SPCujN4k8L2vheK4PjSXW/HMPir7brEmnW9Sx/4J5/tQ32hfs8/Bf4j/tt+Dvin+zR+zX8a
PhF8VfBdt4n/AGW9Vtf2tPE2lfAPxVD4s+E/hH4iftG6P+0rZfCXxFeabNpmgaF4s8Z6f+yToWse
MfD+lzy3Vtp/i3VbzxbRl04r+yJ4ulHD1quLwNTMoqU8Xhsro4vjjjPHZzRoe3liJ4+nluR5nw08
qljaWZTzDKcooZTUhk9dYrDVjFQqU45xHC1J4mnThjVl3tJQp4jMnhuDOEcJkcqko06UcDUxOcYD
iennawtbL6VLOM3Wb0v7Ww9HDYqj9lftW/tb+Dv2SdJ+EN54n+Hvxb+KOt/Hb4y6V8BPhl4K+DPh
vQPEvivXfiX4h8D+PvHHh3TLmLxN4r8GaJomj6tB8PdS0a48Wa3rmn+FvCl7qOn69471fwr4BsfF
PjPw581+Pf8AgqT4H+HkPxD1XVf2Xf2tNZ8I/s+aT4Q1H9sPxx4P0H4C+LPDf7HV94m8OaR451vw
z8W10X9oS68QfEjxN8L/AIc69o/xH+K2nfsmaD+0nH4O8HalYX811d3t9ZafcfT/AO0d+zb/AMNA
+Kv2VPE3/CZ/8Il/wzJ+0zov7Rf2L/hHf7e/4Tf+x/hR8XPhh/wh32n+3dF/4Rv7R/wtP+3P+Eh+
z6/5P9hf2b/Ycv8Aan9oad8f/GL/AIJw/E/xt4m/a98P/DL9qLRfhn+zd+37e6Zqf7VPws174BRf
Ef4oLqeofDLw38Dfipdfs9fGwfFvwZonwqX4q/BzwV4S8OX9v8Svg18f4vCHiWx1Txh4MGkHVk0X
TsKTreyxjlGl9Zjicd/Zsa7msHUjRwfDbyxZk8OpYqnl2LxWM4rWYVcHz5nTqZTk0cLh6GHr4qtj
fQl9U9vgE3V+qfU8HLNJYdJ432tTM8+jmMMt+sNYZ5jh8vw/DlTARxcYZVOnjs1eJxFTF0cPRo++
fEb/AIKB/BH4a/Dn9sz4p6jpHj/xB4T/AGH/AAfovjj4m3HhbTfC2ozeMtA8QfCDRPjXpk/wsN74
x0yy155/CGv2ECnxLe+D7ZtZ86CK4k04RapL8oXf7f8A8efFfxx/4KRfAl/gR8UvhN8P/wBmb4Ja
N4v+Hf7Tei6N+zp4yfwLdeI/gn8Q/HcHjnxd4H1r9qO61fx+fEep+G7DVPg34T0n4a6ZE0Vpc6N8
cG8CJfR3kNv9pv8A4Jc/EP4x6J+1f8Lvg/8AtSaL8CPgN+2X8GvB3wz+LnhHUfgAfi18SdD1v4ff
DGb4T+Htc+GHxO1X4yeFNC8PeFPEHg7SfAeg/Efwh4v+F3xB8R6zpOg+I5vh/wDEn4W+LPFdl4u8
K+y+Jf2FfiFefG39qvx94T+PPhTRPhj+2L+zx4X+DPxX+HfiP4Jan4p8ZaN4s8B/DP4hfDPwf4/+
HXxO0z40eDtJ0LRVsPG1lqHinwJ4n+GHjW61y40OWHR/G/hVdW83TuXOqVapleZrK3WnjJ4HOMNl
9CtU+q1JVv7OxiwOKrV8JWpSw9avi6eGjg5YbHQVCtiYzxsaFGnOrh4y+Xs8Tw5PGuhGMMXQxGfz
oU3XpwhGvkK+r4ajjKVWnXw6VfO6mMhWw9aVTC4JwoSniKmEpYvgbL/gpVp/gfwR8FPCdp8EP2uP
2vfitrv7Evwk/a48Vaz8Ifhf8DvCtzqfw28TaDqNvrfjzxTb+Nfjr8PPhd4L8ZXeteHrm/uPhD4d
8aazrWpXPiCDTPhHY/EKy8P+KJ/Dmj8Vf+CtnwT8E+E7Dxt8Kvgr+0l+1b4dX9knw/8Atx+Mr39n
vw98I4v+Fbfs0eMrLV9Q8D+OfFkfx3+NHwOOqap4zs/DHjG50LwD8PP+E6+IK2/g/W7rV/C+lW0m
izav6r8Iv2Gv+FV6voWq/wDC0P7e/sT9gf4O/sPeR/whP9l/af8AhU83iyb/AIWf5v8Awluo+T/b
/wDwlG3/AIQry5f7K+w5/wCEt1L7Ti3/AJ9f2iv2H/FXwI+I/wAPvhdq1t8ZPE/h74Bf8E2/2VP2
WPCnxB0T9jL/AIKhftVfCj9r/RvhL/ws9fFXw48XfCT/AIJt/tC/A3wH8OvDl54gOnP49+Gn7Zvj
r9ofwt4/07xrpEWhaR4b8HaF4pl8b+nmFalKvmE4Ta9tnWaTwCw2D56tXAzx3iVLAxw2WYWlS+sx
pZbl/hzjI5XhKeFzCtHNM3w1CccRCWFyrmymhUWEy6GIpVJVKGU5NSxkJYm/+3ToeHVDHzxGPxNa
tKnP69mHHuGWYVamJwdGpl2WY7GQq4FSr5l/WX8N/HJ+Inw48F/EaTwr4i8Er4z8JaJ4uHhDxXc+
EL7xR4dh1zTINVi0jXLvwD4r8ceCLnVbOG4SK7m8LeMvEuhSTBm07W7+2KXL/lV8P/8Ags98Nvij
bfAG98EfsZft56vZ/tZ+DfFvij9lq6k+HHwN0yD45ax8PotDvPHvgXSX1X9oqyPwz1nwxpGp6v4h
i8afH4fCH4LeM/Dvg7xBrfw2+KvjXT73wdP4r/TX4G6t8QvFHwM+E2t/Fr4cWHwb+KWv/C/wVqHx
G+E+lazpniTS/hl431Hwxp0/ijwJpuvaJLLo+tWHhLWpb3RLPUdLnlsLy3sY5rSaSB0kb4g+A3/B
OL/hSXh//gmvoX/C5P8AhJv+Hefgz4oeEPtX/CvP7F/4W9/wsn4Y3Hw4/tDyP+E51b/hAP7F+0f2
z9k87xr/AGjs/s77TY7vty3jaSo5lm1OPLHDUMXh6GDp0MRSxEJ0ZVs3pZhKjjIqrCpPCwhlVTB4
mXtMPWlKU/YYynKrCGWBryq5Xg61SKrYutRwdWc6kKlCPvUoVKkpYfmhKCnVa9tRdSNWOG+sYelK
hiqlDGYXT0f/AIKd/Cjxx4E+BmufB/4NftCfGn4rfHyP4sy+G/2ZPA+i/CXRPjf4Rh/Z/wDFcvw+
+P118Trz4qfGP4b/AAQ8DWHwd+JS2nw28TapqfxnbTNf8b6to2ifDi88cNqdtM9S2/4KjfCnxT4Y
+B1x8Ivgd+0l8bfi38ctY+MegWv7NXgrw58KPCXxv+GGr/s5ah/wjn7Qtn8ZI/jf8Y/hJ8K/A/8A
wp3x3Npfw78Q3X/C09UsvE/i3xD4cj+GVz480PXNP1yby7wf/wAEwviV8Frr4RfET9nn9p/wr4Q+
Pfwo8aftwyt4q+J/7PV/8U/hH44+D/7cX7ROq/tJeLPhp4o+E+gfHf4VeMbTxH8PvGtp8PT4P+JP
hL42+G3vD4S1v/hIvCGp6R4wXQfDtnQv+CYvj/4S3nwX+Kn7PP7TWg+E/wBqHwHdftSXvxW+Kvxd
+AkvxW+HPxtu/wBs7x74c+L/AMdrm6+Dngr4y/A7UvAbW3xa8HeFvEfwmstA+Kt5ovgjQdNuPDfi
nSfiRe37+JIsINSlTdVOnCrHH1MUqUeeeFxsK+J/sbD4GFStGNXJK+Ehhf7dqYyu84o4qrWhlUql
GEay65KMZ1qdKcZqnj50cHWrqcaWIyiEMVCtiswVFe2o51VrrDVsphgqLy2WElbNaOFxM50qHi37
Bv8AwUG1Cx/ZY+FEet+Cv2n/ANqX9oP9oD9pL/gorf8Aw0+Dmjjw1H8cIvhP8H/2xvjLpl5f+MtS
/ad+KPwb8F/DPwl8HPC+o/Dv4eL4e8ffEbw1qei3uoeFfh34R8O397ajSLD1/Xf2th8a/wBpr/gl
x4s+Gev/ABQ8D+A/iF4s/bo8LfGL4Sa5cX/h3W9O8c/Bb4Pa/ovif4Y/GDwV4b1rWPDmveLfhD8T
fDmuaX5Nnf8AjDw5H4j0pte8Ca/ruk3uka/qHkGt/wDBD7wlqfwu+AHh7WfiL8FPj18UP2fviP8A
tf8Ai7TPE/7an7HPgP8AaW+DXxC0D9sf4z6/8aPG1p8QP2etL8f/AAg0u3+InhnX7vw0/hf4lfDP
x18N7e0vdH17Z4Jg8J+L7jwVpf1l8Nf+CeqfD3VP2MfEWj6n+zZ8MdS/ZJ1X9pHXZPBP7Lv7Jo/Z
2+BHjXV/j74M1bwZb3ug/CW1+Nnjuf4eS+Hobyx1jxNK3jTxnc+PdZttRuUufCKapDHphiXzYfHu
nyrFRmvqkYqVanJ0q7jh/q3NPAuWDeBjTnjYY+VLG1cz5lh69DAy0xrx58S3Rc3RxGeZhiKkqrhT
lDL8Rm2PxUJ1owjWXt+SWF9g8JGFGjgpOjVy+eKu6Pr/AOyZ+2bD+2FpVj488A/s6/Hrwh8CvFHh
258V/C/9ob4gar+zYPhz8WtDXWF0vTLjwn4X+H37RPxB+Onhy61u18/WrbSvix8Hfhtq+jWVneaV
4vsfDXi2E+Gm+0q/L39mT/gn34x+Dn7Uvi39q7x549/ZntvGXjLwf4v8P+MvD37Gn7IWu/sdeG/j
T4n8ceKtG8Wan8T/ANp6HWf2mv2j7r49/ETwxe6RfJ8NvFGpzeGtY8H/APCdfEyW6v8AxCfGUiad
+oVaT9l7HCShdVJUav1ilOTq1aNSONxdOnCtiVSw9DFVKmEhhsQ6+FwmCouNaNN4SjXp1ojbf1jF
2UvYe3j9Vk1GCnRlhcPOXLRUqs6EaeIlXo+zrYjFVG6bq+3lTqU4QKKKKyKCiiigAooooAKKKKAP
iPwx+338DPEP7Knxx/a91C28beDPh3+zhf8A7RWjfGPwz4v0rQrT4ieDvEP7MHiPxb4Z+JPh280T
SPE2taJPrNzeeELm78J21t4llj1/TdZ8O3Kz2r6oIYPGviB/wVB0TwL4q+Inhq0/Y4/bK8e23wU+
B/wo/aB+PniPwRpX7Msln8FPAfxZ8P8AinxRp9v4o8K+Kv2n/CnxP8Y+KvCmjeCfFk/i7w18GvAH
xQv459EmsPDQ8TX15pdvffGX7QP7OHxbv/23/HH7JXhj4T+Pr39jz9vj4w/s8ftf/Gr4neG/DWon
4Y+AtT/Z+ttQvv2hvhr4w8TxafceH9E1P9o7WPgp+y9oq+Hbqe21Lxxpfjz4wanbl57HUbiqv7Vf
7Jf7WXxf/ab/AOCovir4JfET4yfDG08R/snfsr6H4R8BJ4P8JWfwE/bAvfD+kfH+Xxz8FPF/xIvv
hrP8a9ETVdDvh8PNS8S/sxfHT4Q/ED4dyfEmz8Sy6rLqtt4eWPjrVqtLKFmUXThXdBRUMXGtUwdL
GZRlNaOdY3EUcBCpmtfIcTxHPFYHDU8HTWe1MPkPt8JhJUsxpVMR0qlTnmawD9p7L6zTlKWHqYeV
eeAzzN8B/Y+Eo4jEOGX0M+y7IubEY2WKlLKvb5vQeKlh3gqlGH6JePf+ChGgaT8Tfhj8Kfgl+zd+
0X+1t4i+K/7PNj+1J4cvfgRd/s0+GtAtvg3qviDS/Dej+INU1L9pz9pD9nRxearfa3pMtpo+k22r
agllepPeQ2piuY4fvDQdRvNY0PRdW1DQdW8K3+qaTp2o33hjXptDuNc8OXl7Zw3NzoOtXHhjWvEf
hqfVtHmlfT9Rm8PeIde0OW8t5n0nWtUsGt76f8L9E+BXxS+Of7ZH7L/xG+D2vftbfsD/AArtf+CU
3h/w/bXPgH4PfCnTdT8F6pP8XfBGo6X+zh48t/2t/wBmn43eH/DPinwfoUXn3HhSHw54Z8fRr4dN
3JdPoiXkNx9rf8FNPBHxX8V/sQ+OPC/w1sviF8Rbuy174L6j8WvCngIvB8V/i9+z34W+K/gXWf2l
fAfhC08Jjw9NqXjL4kfBLTPHugw+FfCtrZXXjCTVrnwb4c0iS712x0uT0q8IUKC0dKpVz3PMBz5l
Wow+p4PB8dcR8O4LFYqtl6r4WlgMLlGBy/G5tiuTEVZKnXx2XwrYSrTjPy8DUr4uvyz5ZKGW5LX5
MDQr8tfFY3hDhzO8XRpUsb7PFVMXVzTHY/C5dQUqVGnGVLB4+dLFUqk4fohRX80f7U3wW8DeMv2Z
vBtl+wN+yP4x+Bv7Kuk/trfDzxb+1J8G/G3/AAT5/aCt/hR8Uvh3Y/CnXtJv/Edv/wAEv7PXP2bP
jf8AGP4a+Hvide/CTUfib4J8GeBPBZ+Jer+EZ/G3/CL/ABr0zwfrFrqHP/Dn9jm38c/Br4KfDJ9E
1/4nfs8eI/8AgqJ4Q8da/wDAbwd/wTo/bA/4JvfBr4E/DVv2bvHmnfEPwn4c/Z6/aC8X+J/G+m/s
7ePfGl3H4j+IEtrqVp8C/Fvi/wCKPxC8D6hpl5ZeJvE3hmXClzVas6PJKlL+18hyuHtYyUnTzrMe
GMBLMa1OEZ1MNgMPDiDFYmhi6sfqmNjk+IoxxNGvV5KHXU5adGNbnhVj/Zec5nUdB+0hF5TheI8R
/ZtKpL2dOvm9aeR4SnVwEGquEpZvQxFTnhCjHF/0W/E/4y/Db4NR+ApviT4j/wCEbj+J3xP8GfBr
wO39j69rH9t/En4g3c9j4Q8OY0HS9UbTf7XuraeL+2NXGn6DYbN+p6pZRsjt0Xj/AMW/8ID4E8ae
Of8AhGfF3jT/AIQzwp4i8V/8Id4A0b/hI/Hfiv8A4R7SLvVv+Eb8F+HvtNn/AG74s1z7J/Znh3R/
tdr/AGnq91aWX2iDzvMX+Wz40fsM+DdD8GfF3wx4j/YUuPG37Mn7OP8AwWy+C3xH+Fnwf0T9k7Uv
i1onhP8AY+8b/CD9nPU/j/c/s8/BDQfAHijWvFHwV134ra745v8Ax74N+CXg/X9C1DVrPxhFJ4eu
E8Oatbad9T+Gv2NPAHiv4h/8FdvjYv7Kd7Jq1z4H8C6X+xFqfjD4GeKdD1Hwr4Uvv+Canwt8AXWn
fs0eB/GnhfTbn4a67fajHL8LPHdp8N/DXhnxjeXvhfS/hX48jln8BaP4a0HhxWIq08gzjM4RqfWM
JlVTOMJTpU1KqsPX4O4Gz/A4Kth58/8At7zLinM8CqqnKjiJZHj6EMJGtlmJliezB0I1c/w2WVXC
OHk3QnVnJqjXxmG41z7h7E+zxKlT5cK8py7Ls0qwjTlXwP8AaGEcquIw+Z0KuE/e7wH4r/4TvwN4
M8cf8I34s8G/8Jl4U8O+K/8AhEPHmj/8I7458Kf8JFo9nq//AAjfjPw/9ovP7D8WaH9s/svxFo/2
u6/szWLW8svtE/kea3V1/Mm/wa8H6Trf7NL/APBQL9jn44ftL/BO0/4JafsvfD79nfwN4e/ZV+L3
7SS/BD9pjwfYalD+0PoepeCfAXg3xbf/ALOPx98ZabqvwXs/Bvx08bW/wqi0S08CeIdCg+Knhe48
Na0kX6cf8FAvht4qT4X/ALPH7UPwu+H/AI88VfF79h/4teBvjZofgPRINd8ffFnxT8KtU0ub4aft
H/C7S7Dw3eeLdY+IfjbX/gl4t8WXOl6LZXvia58W/ELwv4Yazv8AUr9rS+k9rNIYfBYvG2qR+pUM
+xOWrEUlUq0MPgaGf47Ka2OrSkvbSWCwmEhm2Kw2Hhi66wFajVpyrRxeXVcw8XLa2JxWDwblSlPG
V+H8HmcacrU54vHYrIMDmtPA0LQjSj7bMMVVyJYqtLD0YZrg8dQdOP1HHRwv6aV8/wD7U/7RnhH9
kr4AfEr9onx34e8ZeLPCvww0mx1bVfDXw+tfDt74z1v+0tc0rw9Y6f4etvF3ibwb4Ze+n1LWLNQd
b8U6HYRQ+bLNfxhAG/ng+Lf7KejXHwF+AHxl/aH8GeKPEX7S/wAZPG37QX7XPxJ+BXxm/wCCVX7U
3/BUD9nLVfFf7Qll4bfRPA/xx+CfwD8Oh/h38cf2bPh1o3wq+BXwd+JniL4i+GNb8KeEfDnxM8MW
PhPxVoGv6ra+Hf0L/bR8G/F34w/8EWfE/gzRf2ctZ+Cnxg8W/AD4L2cH7Mfwc0ex8b6p8H9ah8S/
Dq4u/h54D0Twx4Xn0nUrf4c2dpPb6dY2PhBtJsNO0Xy7nRFsLO4tl46lOr9Qx1SSnTxuBWGw2Kw9
B0avssdXw+O+sUcJi6rjhcW8HjsvxWFjPkt7lGvmFDARxeFo1+2pUhTr4f2U6NbD4mOPr4etUdWK
nhcLi6MMHXr4eipYiFHMcBicLmC9lNyhCvLDUKmIr0K8qX2p+z7+2Fo3xv8AiV8Rvgh4q+Cnxv8A
2a/jp8MfDHg74ga58I/jva/Ca713VPhl8QLzX9I8JfEjwt4u+Anxb+Onwm8Q+GtT8R+EvF3hi5s7
L4inxZoWueG76HxF4Z0i0vNEvdW+wK/Bf9u3/gnlqGm/sufH/wARWXjz9qj9sT9o/wCO/wAUP2C/
B/iv4k+Lbjw4nxd034J/Cf8AbD+EHiZfBPw20D9k/wCF3wK8KfDPwb4BsNW+JXxQ1rxP4A8BaB4z
h1PVvEXjjxb42vY/D+h3Phzzb9ov9lP9lP4TftN+MvBf7Qf/AATy1r4z/sMz/skeG9C/Y2+FX7Pf
7Ffin9oP4Q/Cn45zfED4r6r+1BZaX8KvgJ4C8R2PwB+OPxetfE3wR1fw38f/ABh4d8D2mrWmga9B
pvxt8O3eieKbBpqVrYZ1fZqeJp4nHYT6thFiKjxksHlkM3ofUqVWHtp4zE4bE4XL/q15U8VnVLHw
y+q6U8DhJ7qjFxrVo1KrowqYRxp1Y0PrMKFWeUYLGV5OFaNGdHDY7FZpj3KXsFhOHMFSxeOqvEQx
0qP7xN8Zfhsnxnh/Z7bxHj4v3HwwuvjLD4R/sfXjv+G1n4rtPBFz4j/t8aWfDC+X4nv7TTP7HbWl
15/N+2x6W2npJdp6fX8wfwO/ZB8S/Cz9q39g34j/ALX37Ms3xI/aW1P/AIJq+H/hVcftOXH7Ouqf
tPah4K/bg8DeP/A6+DNf+Mfx78F/Dv4mS+AfH3hPwDLDpNr+0B8Tde0zw/d2Oi+IrWw+JWrww3j3
WD+yZ8A9cPiP/gnrcfCv9lb43fAj/goz8K9e8Y3H/BTv9qD4kfAD4m/DSy+Klg/wk+Ivhj432XxN
/ao17RLX4cftv6R8Yv2mb34ZfEX4QaR4A+IXxy0zTNF0DRvGegr8MdE8JQtpWluXDOpria1HHZrg
6sMGoVZ4mGH4r4lybCYzBYf2j5sLgspyfL834hqvEz+pYHOcozXCRxVDOKGDwfNeXt8VGUqVOhDB
YHFYatUdaNGVWrwvk+bVsLPESoQlUnmGc43MMnyCUMJTni8ZluY5fi6GExOWTrY3+pqvOfjF8QP+
FTfCP4p/FP8Asj+3/wDhWnw58b/ED+wvt/8AZX9tf8Ib4Z1PxH/ZP9qfYtS/s3+0v7N+x/b/AOzr
/wCx+d9o+xXXl+RJ/OL8Cvgvrdn+xr8UPA/wG/ZQ/aF+FH/BZeP9jj9oXwb8aP2p9b+DHxC+Ct18
Rf2mrm1NhruueJf2yvHun+DPhf8AtR3HxX+KsEfi34BeJPDfxB+Nel/D/R30vxFa6r8LdG0ttStb
fgv4FfD7V/E3ijxT/wAE+/2Mfjj+yv8ADMf8E1P2nfh3+1p4a8X/ALLXxj/Zav8A44fGbxf4V8Jf
8M2+DtW8EfEnwh4W1b9qH4/+A9VsvjRPrnxt8Nab8SXtovGl5pUnxr8SXHxAttJ1bzs8licNlueP
A16dTEYTI82xmDx+Bg8Zhp4nDZVxBi8Ji8K8RRo08XlmIxeUYbBYTGyg/b4/McLgq2ChXrYWjjPR
yyFGpmGVQxcLUMRnVDA4vD4ibw88NSWMyCFXDZk6MqlTA4/EYbNsZVw2Fg6ntKeVYyssVSw9HFYr
Bf0PfAb4n/8AC7fgb8GfjP8A2H/wjP8Awt34UfDv4n/8I3/aX9tf8I9/wn3hDR/Ff9h/2x/Z+k/2
t/ZP9rfYP7T/ALK037f9n+1f2fZ+b9nj9Xr5W/ZD8O+LvDf7EX7MHhK/02/8I+PNB/ZW+Cvhy90j
xPpV7puqeGPF2l/CPw1plxpviHQ7+G21Cwv9F1mB7XVtKvYLe9tbi2uLS5hinjdF/D39nD4K3Vv+
yR8R/Afwb/ZT/aC+Ef8AwWJb9jf9ovwP8bf2rtf+DHxL+C0njv8Aaev9Nm0vVPE/i39sjxjp/g34
dftSj4mfF+O18bfArxF4S8ffHCx8A6Aun+IbG++Gmk6YbyH2+IfY4HNOJ6eAoe0w+U1cwq4DCUal
WviMdRpVM0lRp4GKjXqYihhKeAowzHFzqSnhY5hl9WNPGe3q+y8Xh32+Pynhutj8RCjiMzpZPRx+
LxUY4XDYOvjKeAjWrY2fLTp4epWqYqtPC4aFNRrSwmLpylhI06bqf011znjHxb4f8AeEfFPjvxbq
H9k+FPBXhzXPFvibVfsl9f8A9meHvDmmXWsa1qH2HTLa81K8+x6bZ3Nz9k0+zu7248vybS2nneOJ
v5R/2e/2Z9Z074bftJSfC3w43wy8W6v/AME1f2ifhp8Q/wBnb4P/APBE39u79g6T46ePdW8CaRB4
Ov8A4ufHP40fF74t/CP9pf8AaB+HXip9f0Lwdrfg+98WfEHx7/wsf4m6voXijxT4d1O91CL6F8R/
8E5/CnhbxzpXw2+Ef7JVvB4B/aC/4I9ftKeGf2irW9+Hdzq3hj4y/tS+HPE37Our/AW6/aL8V+Nb
S+0/x1+0PZ654k+K+s+E/F/xe1vUvidcTt4t1Ztanj0W9udP8vMp18PRzZYP2davgskxeY4Oqqc8
ThcXi6OU+IeaUaNB0KkKeOw1WPAuGo06+BxdRV8RxFgcKnRrUpe09PAxpV5ZbPEqpQpYzMsNhcRQ
qNYXF4TCSzLgbLsVUxUK8JTwOLovi/FVlhsTh/dw+RYivVlBVp08L/RX4D8ceF/ib4G8GfEnwPqf
9t+CviF4U8O+OPCGtfYtR03+1/C/izR7PXvD+qf2dq9pYatYfb9Jv7S7+xapY2Wo2vm+Re2ltcxy
wpyPwn+K/wDwtZfiO3/Ctfiz8Nv+Fc/Ffxj8KsfFjwb/AMIc3jv/AIQ86eP+FkfDgf2jqP8AwlHw
o8U/2hnwd4w/0H+2xY6h/wAS61+zfP8Azpfs4fsYfAT4xap/wSB8GXH7CWt+GPgN8Nv2Vf2qtK/a
e+FPxN/Y4+IvwJ+GD/tJT+Bv2Kra7n+PHwu+IPwz8CeD/iXqXirxb4Y1vXvDPiTxxoXjDwh8QvGv
gGPxz4P1bxF4m+HWn69oHT+NvgV8QdN8LfFIfEv9n74r+N/2TI/+C2HxO+Jn7SfwM8N/Bnx349v/
AIyfstav8HdM8LfDnxJYfA7wv4d1jxP+0F8DfDvx2l+GXjDxb4H8F+C/H+n+JvDXgzVL5fDeuaX4
W1a3h9TF0qFHOMTg6NWP1R4XNamErYirB4a2G494a4VweInj6dOEKkMRl2ZY3N6Ff2FHCV8uj9cm
qFBvEYPzMJVxNfJcoxtWlJY/E1IrMMHSoThiqdelwxxdnFXLqGBnOtVeKrY7JMBlyws6ixNDNsXS
y2M8RJc2M/pfor5a/Y40n4OaL8DdJsv2fvgj46/Z5+Dh8S+NbnwL8LvHfw68U/BifSNMufE+pTXO
o+Fvgj41Gn+Kfgz4G1/VWv8AWvCnw51jwb8NrjR9OvVuo/h54bttRhin+pa55x5Gk1Ui3TpSlCrT
dKrTnOlCc6VSlJudKpSlJ0506qp16couFejQrKdGHTTn7SPNenJOU1GVKp7WlOMZyjGpTqqMY1ad
SKU4VKfNSqRkp0alWk4VZlFFFQWFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAF
FFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUU
UUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRR
QAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFA
BRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAF
FFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUU
UUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRR
QAUUUUAf/9kAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFBLAwQUAAYACAAAACEA3DEv
8fIBAABeBAAAEQAAAHBwdC9wcmVzUHJvcHMueG1srJPNjpswEIDvlfoOyHcHGwgQFLKywZEqtas9
tA/ggpNYMhjZzmarqu9e85NVor3sIVwYsGfmm8+wfXrrVPAqjJW6LwFeIRCIvtGt7I8l+PVzD3MQ
WMf7livdixL8ERY87b5+2Q7FYIQVvePOp76YwBfqbcFLcHJuKMLQNifRcbvSg+j92kGbjjv/aI5h
a/jFN+hUGCGUhh2XPVjyzWfy9eEgG1Hr5tx5gLmIEWoisSc52Gu14TPVbue4Q9r5Ie1JX/xw4+2Z
GzO18J7AuLYkhtM+1RKlptDPWymz23K/wTofBq9clcCIFvj10OctG4ZCvLnv1o35PgrORpbgL6tw
mtG6hjnOI5gQmkHCqgoymqCYxYTSOPs39sdJobgVZuwwy/evPgzcycZoqw9u1egunM2Fg74IM2g5
ycNoPoGR2Jrj73fi/R75a4a+aTbN4HnvsaN9TaMUZRBneQITxiik2SaHGaPrPE4Zq3NyxR5t/hCt
5JUzyj4EfnaMF8MTnTd99evD+SAX5o/Ss7Rim4TAFMUVTHASQbrxI6Q1jjOEMCLRu/RW2oab9lvH
j4K10tXc8QfOsAgf2e8N1zEmKI0I9FoJTOJoA8n4nVBK8nWaRmiN0dVwKw78rNzEWA/ygXhRdAd4
L/n2V3oxu/8AAAD//wMAUEsDBBQABgAIAAAAIQDY/Y2PrAAAALYAAAATAAAAcHB0L3RhYmxlU3R5
bGVzLnhtbAzMSQ6CMBhA4b2Jd2j+fS1DUSQUwiArd+oBKpQh6UBooxLj3WX58pIvzT9KopdY7GQ0
A//gARK6Nd2kBwaPe4NjQNZx3XFptGCwCgt5tt+lPHFPeXOrFFfr0KZom3AGo3NzQohtR6G4PZhZ
6O31ZlHcbbkMpFv4e9OVJIHnHYnikwbUiZ7BN6qCIKK0wKfL5YhpSANcejTGcVTW1bmp/SosfkCy
PwAAAP//AwBQSwMEFAAGAAgAAAAhAIOirVmhAQAAWQMAABEAAABwcHQvdmlld1Byb3BzLnhtbIxS
wU7jMBC9r8Q/WL6XJEW0JWparbTixAGJwt3Y09Qrx7Y8Tmn5esZxuw2wB24z45k3773xcn3oDNtD
QO1sw6vrkjOw0ilt24Y/b+4nC84wCquEcRYafgTk69XVr6Wv9xreHgMjAIu1aPguRl8XBcoddAKv
nQdLb1sXOhEpDW2hgngj4M4U07KcFZ3Qlp/mw0/m3XarJfxxsu/AxgwSwIhI5HGnPZ7R/E/QfAAk
mGH6MyUjML6QuoajUZtd371aoU2q8BUJt0nSkD6GlBNOdAHUA2wjw3ey8XY2LXkxfts4PzzdzW9u
ZpyJPrrf6m+PseFDZ/EdFo1WkJbmLfLJqFF2CVEKA6ulqPHA6IZzOqEiDuWAS9Xj9yptO0352gXd
assODZ9U5YKGjxTdVdPEn/rkZVHbE6EHjEnXEDOaJQfJbBfeOfMOGz6tZifpuSUXFwSc8S4gCXyk
KXH6rNi6CLiBw3CLkwkXNl9kV1l12nLWPCol8GzTWHAWe2b2Tyk1/2d1G7R68kLSB2aS3JrTjQlA
kl05zPr2+WAfAAAA//8DAFBLAwQUAAYACAAAACEAb3wtb5kBAADxAgAAEQAIAWRvY1Byb3BzL2Nv
cmUueG1sIKIEASigAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAhJLdTuMwEIXvkXgHy/ep
43SLUJQGLSxBFT+LaFhg7yx7aC0S27KHlr79OikNRax2L2fmzKczxy5O3tqGrMAHbc2U8lFKCRhp
lTaLKb2vq+SYkoDCKNFYA1O6gUBPysODQrpcWg+33jrwqCGQSDIhl25Kl4guZyzIJbQijKLCxOGz
9a3AWPoFc0K+iAWwLE2PWAsolEDBOmDiBiJ9Ryo5IN2rb3qAkgwaaMFgYHzE2YcWwbfhrwv9ZE/Z
aty4eNO73X22ktvhoH4LehCu1+vRetzbiP45e7y+mvenJtp0WUmgZaFkjhobKGfndUWevt9cEG9f
MeZKWqugCeTXXUVkPMBrSVaBxCTRStvsegUbEB1MehBofXk1qy9/PswvZ2SO4JbCAJmfnbPZ6U3V
b+x03QM1IuB1fMtnDep08+/Vr/KO4GGlu69R8nHB9utoqY9z6wsUiQHl2zh3k4fx2Y+6omWW8kmS
8iQ7qvk4n2R5mv3urH7a7wLbNmI6veH/ErOEpzXP8gj9Ntkj7gBl7/jzJy3/AAAA//8DAFBLAwQU
AAYACAAAACEAFuRJg1sCAACBBQAAEAAIAWRvY1Byb3BzL2FwcC54bWwgogQBKKAAAQAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAACkVN1P2zAQf5+0/8HK0/YAaVnHWOUaoUIBadCKhk579JxLa83x
WbYpsL9+l6TpB0WTNvJ0X/7d3e8ux0+fSsOW4INGO0i6h52EgVWYazsfJPfZ6OAkYSFKm0uDFgbJ
M4TkVLx/xyceHfioITCCsGGQLGJ0/TQNagGlDIfktuQp0JcykurnKRaFVnCO6qEEG9OjTuc4hacI
Nof8wK0Bkwaxv4z/C5qjquoLs+zZUcGCZxilyXQJont8xNONyr+jz4Pofj3haSPyM+eMVjISI+JG
K48Bi8jGde1sgo/gJ6ht5Ol2IPEBgZqqn43qnsXYHgTlASybLvCRfej1P33k6SuBfCK9nHvpFkEc
f6GQjcqnRucQRI+nK4nfYiRDh6eNwK90noNdecm8o/Obm6HRro5vRT5V0sCQCBKFNAEIem3gVyCr
4U+k9kHwZewvQUX0LOjfNP5ewn7KABWtg2QpvZY2Er1VWKPUsnEhepHRHhA2+Rq9FrfDtmXdE906
gIS/BjZYdbcs09FA+IcUxCKVs5eiMjZtUu5dApoU44JGEl/h4/M2H3VpDRtNlaud2SNiTcn1RTZi
P85uL5nHh0i0sxJzMIHN7kZM0Tp5rdgyMFrmiApNa9tueQ02o/+IBqVLZ4j41SoGhsUaXKEt9PxN
j1l/pzZ4klW6t0K6F/2xV3B3hvRiLEMsnbTPYnxHXF6wUcYuiVDH09bBv2n7K9y7DM9lhHbtd418
upAecjpPrX9j4Fe08d5UIMOFtHPI25h9R3VAZs1FFd3eYYe++la0tuoEtLdT/AEAAP//AwBQSwEC
LQAUAAYACAAAACEAPSRt7dgBAADMDQAAEwAAAAAAAAAAAAAAAAAAAAAAW0NvbnRlbnRfVHlwZXNd
LnhtbFBLAQItABQABgAIAAAAIQBo+HShBQEAAOICAAALAAAAAAAAAAAAAAAAABEEAABfcmVscy8u
cmVsc1BLAQItABQABgAIAAAAIQBjXCO0wQAAADcBAAAgAAAAAAAAAAAAAAAAAEcHAABwcHQvc2xp
ZGVzL19yZWxzL3NsaWRlMS54bWwucmVsc1BLAQItABQABgAIAAAAIQBL9T3svwAAADcBAAAgAAAA
AAAAAAAAAAAAAEYIAABwcHQvc2xpZGVzL19yZWxzL3NsaWRlMi54bWwucmVsc1BLAQItABQABgAI
AAAAIQBL9T3svwAAADcBAAAgAAAAAAAAAAAAAAAAAEMJAABwcHQvc2xpZGVzL19yZWxzL3NsaWRl
My54bWwucmVsc1BLAQItABQABgAIAAAAIQBL9T3svwAAADcBAAAgAAAAAAAAAAAAAAAAAEAKAABw
cHQvc2xpZGVzL19yZWxzL3NsaWRlNC54bWwucmVsc1BLAQItABQABgAIAAAAIQDd8422KwEAAF8F
AAAfAAAAAAAAAAAAAAAAAD0LAABwcHQvX3JlbHMvcHJlc2VudGF0aW9uLnhtbC5yZWxzUEsBAi0A
FAAGAAgAAAAhAD69EUtiAgAA+QwAABQAAAAAAAAAAAAAAAAArQ0AAHBwdC9wcmVzZW50YXRpb24u
eG1sUEsBAi0AFAAGAAgAAAAhAK2OUrrNBQAA7UkAABUAAAAAAAAAAAAAAAAAQRAAAHBwdC9zbGlk
ZXMvc2xpZGUzLnhtbFBLAQItABQABgAIAAAAIQBGnJjREQgAAJRbAAAVAAAAAAAAAAAAAAAAAEEW
AABwcHQvc2xpZGVzL3NsaWRlMi54bWxQSwECLQAUAAYACAAAACEAE3fd24YCAADQBgAAFQAAAAAA
AAAAAAAAAACFHgAAcHB0L3NsaWRlcy9zbGlkZTEueG1sUEsBAi0AFAAGAAgAAAAhABRlUw5vBAAA
mCIAABUAAAAAAAAAAAAAAAAAPiEAAHBwdC9zbGlkZXMvc2xpZGU0LnhtbFBLAQItABQABgAIAAAA
IQDV0ZLxvgAAADcBAAAsAAAAAAAAAAAAAAAAAOAlAABwcHQvc2xpZGVMYXlvdXRzL19yZWxzL3Ns
aWRlTGF5b3V0Ni54bWwucmVsc1BLAQItABQABgAIAAAAIQBpol8hHgEAAMcHAAAsAAAAAAAAAAAA
AAAAAOgmAABwcHQvc2xpZGVNYXN0ZXJzL19yZWxzL3NsaWRlTWFzdGVyMS54bWwucmVsc1BLAQIt
ABQABgAIAAAAIQDV0ZLxvgAAADcBAAAsAAAAAAAAAAAAAAAAAFAoAABwcHQvc2xpZGVMYXlvdXRz
L19yZWxzL3NsaWRlTGF5b3V0OC54bWwucmVsc1BLAQItABQABgAIAAAAIQDV0ZLxvgAAADcBAAAs
AAAAAAAAAAAAAAAAAFgpAABwcHQvc2xpZGVMYXlvdXRzL19yZWxzL3NsaWRlTGF5b3V0OS54bWwu
cmVsc1BLAQItABQABgAIAAAAIQDV0ZLxvgAAADcBAAAsAAAAAAAAAAAAAAAAAGAqAABwcHQvc2xp
ZGVMYXlvdXRzL19yZWxzL3NsaWRlTGF5b3V0Ny54bWwucmVsc1BLAQItABQABgAIAAAAIQDV0ZLx
vgAAADcBAAAtAAAAAAAAAAAAAAAAAGgrAABwcHQvc2xpZGVMYXlvdXRzL19yZWxzL3NsaWRlTGF5
b3V0MTAueG1sLnJlbHNQSwECLQAUAAYACAAAACEA1dGS8b4AAAA3AQAALAAAAAAAAAAAAAAAAABx
LAAAcHB0L3NsaWRlTGF5b3V0cy9fcmVscy9zbGlkZUxheW91dDIueG1sLnJlbHNQSwECLQAUAAYA
CAAAACEA1dGS8b4AAAA3AQAALAAAAAAAAAAAAAAAAAB5LQAAcHB0L3NsaWRlTGF5b3V0cy9fcmVs
cy9zbGlkZUxheW91dDMueG1sLnJlbHNQSwECLQAUAAYACAAAACEA1dGS8b4AAAA3AQAALAAAAAAA
AAAAAAAAAACBLgAAcHB0L3NsaWRlTGF5b3V0cy9fcmVscy9zbGlkZUxheW91dDQueG1sLnJlbHNQ
SwECLQAUAAYACAAAACEA1dGS8b4AAAA3AQAALAAAAAAAAAAAAAAAAACJLwAAcHB0L3NsaWRlTGF5
b3V0cy9fcmVscy9zbGlkZUxheW91dDEueG1sLnJlbHNQSwECLQAUAAYACAAAACEA1dGS8b4AAAA3
AQAALQAAAAAAAAAAAAAAAACRMAAAcHB0L3NsaWRlTGF5b3V0cy9fcmVscy9zbGlkZUxheW91dDEx
LnhtbC5yZWxzUEsBAi0AFAAGAAgAAAAhACdxx8UcBAAAsQwAACIAAAAAAAAAAAAAAAAAmjEAAHBw
dC9zbGlkZUxheW91dHMvc2xpZGVMYXlvdXQxMS54bWxQSwECLQAUAAYACAAAACEACz6LKO4EAABd
EQAAIQAAAAAAAAAAAAAAAAD2NQAAcHB0L3NsaWRlTGF5b3V0cy9zbGlkZUxheW91dDMueG1sUEsB
Ai0AFAAGAAgAAAAhAGWGXSu3AwAAmgsAACEAAAAAAAAAAAAAAAAAIzsAAHBwdC9zbGlkZUxheW91
dHMvc2xpZGVMYXlvdXQyLnhtbFBLAQItABQABgAIAAAAIQCnk8fLoAQAAAkRAAAhAAAAAAAAAAAA
AAAAABk/AABwcHQvc2xpZGVMYXlvdXRzL3NsaWRlTGF5b3V0MS54bWxQSwECLQAUAAYACAAAACEA
lc5PxhEIAADpMAAAIQAAAAAAAAAAAAAAAAD4QwAAcHB0L3NsaWRlTWFzdGVycy9zbGlkZU1hc3Rl
cjEueG1sUEsBAi0AFAAGAAgAAAAhANyw9S5+BAAAbBIAACEAAAAAAAAAAAAAAAAASEwAAHBwdC9z
bGlkZUxheW91dHMvc2xpZGVMYXlvdXQ0LnhtbFBLAQItABQABgAIAAAAIQDJHfZ02wUAADscAAAh
AAAAAAAAAAAAAAAAAAVRAABwcHQvc2xpZGVMYXlvdXRzL3NsaWRlTGF5b3V0NS54bWxQSwECLQAU
AAYACAAAACEAOGDKsUEDAAC9CAAAIQAAAAAAAAAAAAAAAAAfVwAAcHB0L3NsaWRlTGF5b3V0cy9z
bGlkZUxheW91dDYueG1sUEsBAi0AFAAGAAgAAAAhADxuWZ/OAwAA0AsAACIAAAAAAAAAAAAAAAAA
n1oAAHBwdC9zbGlkZUxheW91dHMvc2xpZGVMYXlvdXQxMC54bWxQSwECLQAUAAYACAAAACEAOgp6
thcFAAA1EgAAIQAAAAAAAAAAAAAAAACtXgAAcHB0L3NsaWRlTGF5b3V0cy9zbGlkZUxheW91dDku
eG1sUEsBAi0AFAAGAAgAAAAhAIQ5X7dWBQAAxRIAACEAAAAAAAAAAAAAAAAAA2QAAHBwdC9zbGlk
ZUxheW91dHMvc2xpZGVMYXlvdXQ4LnhtbFBLAQItABQABgAIAAAAIQB06MbDEAMAAGsHAAAhAAAA
AAAAAAAAAAAAAJhpAABwcHQvc2xpZGVMYXlvdXRzL3NsaWRlTGF5b3V0Ny54bWxQSwECLQAUAAYA
CAAAACEA1dGS8b4AAAA3AQAALAAAAAAAAAAAAAAAAADnbAAAcHB0L3NsaWRlTGF5b3V0cy9fcmVs
cy9zbGlkZUxheW91dDUueG1sLnJlbHNQSwECLQAUAAYACAAAACEAuX/uc5YGAACwGwAAFAAAAAAA
AAAAAAAAAADvbQAAcHB0L3RoZW1lL3RoZW1lMS54bWxQSwECLQAKAAAAAAAAACEA6lsCKwAwAAAA
MAAAFwAAAAAAAAAAAAAAAAC3dAAAZG9jUHJvcHMvdGh1bWJuYWlsLmpwZWdQSwECLQAUAAYACAAA
ACEA3DEv8fIBAABeBAAAEQAAAAAAAAAAAAAAAADspAAAcHB0L3ByZXNQcm9wcy54bWxQSwECLQAU
AAYACAAAACEA2P2Nj6wAAAC2AAAAEwAAAAAAAAAAAAAAAAANpwAAcHB0L3RhYmxlU3R5bGVzLnht
bFBLAQItABQABgAIAAAAIQCDoq1ZoQEAAFkDAAARAAAAAAAAAAAAAAAAAOqnAABwcHQvdmlld1By
b3BzLnhtbFBLAQItABQABgAIAAAAIQBvfC1vmQEAAPECAAARAAAAAAAAAAAAAAAAALqpAABkb2NQ
cm9wcy9jb3JlLnhtbFBLAQItABQABgAIAAAAIQAW5EmDWwIAAIEFAAAQAAAAAAAAAAAAAAAAAIqs
AABkb2NQcm9wcy9hcHAueG1sUEsFBgAAAAArACsAAA0AABuwAAAAAA==

--_006_9E32478DFA9976438E7A22F69B08FF920C7A0F1AOPEXCLILM34corp_--


From nobody Wed Feb 11 12:06:53 2015
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71B4B1A9026; Wed, 11 Feb 2015 12:06:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.512
X-Spam-Level: 
X-Spam-Status: No, score=-0.512 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, SPF_HELO_PASS=-0.001, 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 2u_F406oeqPx; Wed, 11 Feb 2015 12:06:33 -0800 (PST)
Received: from maildrop31.somerville.occnc.com (maildrop31.somerville.occnc.com [IPv6:2001:550:3800:203::3131]) (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 B0D171A904D; Wed, 11 Feb 2015 12:06:17 -0800 (PST)
Received: from harbor31.somerville.occnc.com (harbor31.somerville.occnc.com [IPv6:2001:550:3800:203::3231]) (authenticated bits=128) by maildrop31.somerville.occnc.com (8.14.9/8.14.9) with ESMTP id t1BK63b4073326; Wed, 11 Feb 2015 15:06:04 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201502112006.t1BK63b4073326@maildrop31.somerville.occnc.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: RtgDir review: draft-ietf-rtgwg-cl-use-cases-06.txt
In-reply-to: Your message of "Fri, 23 Jan 2015 16:08:58 -0500." <54C2B86A.6010607@joelhalpern.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <73324.1423685163.1@harbor31.somerville.occnc.com>
Date: Wed, 11 Feb 2015 15:06:03 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/RWj4X8MzgiJzNScCAWh7KvIGotQ>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "<rtgwg@ietf.org>" <rtgwg@ietf.org>, draft-ietf-rtgwg-cl-use-cases@tools.ietf.org, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2015 20:06:42 -0000

In message <54C2B86A.6010607@joelhalpern.com>
"Joel M. Halpern" writes:
> 
> Hello,
>  
> I have been selected as the Routing Directorate reviewer for this draft. 
> The Routing Directorate seeks to review all routing or routing-related 
> drafts as they pass through IETF last call and IESG review, and 
> sometimes on special request. The purpose of the review is to provide 
> assistance to the Routing ADs. For more information about the Routing 
> Directorate, please see  
> http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir
>  
> Although these comments are primarily for the use of the Routing ADs, it 
> would be helpful if you could consider them along with any other IETF 
> Last Call comments that you receive, and strive to resolve them through 
> discussion or by updating the draft.
>  
> Document: draft-ietf-rtgwg-cl-use-cases-06.txt
>      Advanced Multipath Use Cases and Design Considerations
> Reviewer: Joel M. Halpern
> Review Date: 23-January-2015
> IETF LC End Date: N/A
> Intended Status: Informational
>  
> Summary: No issues found. This document is ready for publication.
>  
> Minor note: This draft appears to have expired.


Hello again Joel,

FYI - to the Cc.  I emailed Joel off list about this.  This draft lay
dormant in "AD review" for a long time.  Apparently the AD shepard had
a change of heart about this .. or something.

The draft itself could be described as inconsequential but contains
parts of earlier CL requirements draft and CL framework that more
closely resembled use cases.  This draft exists both to be
informational and to unclutter the requirements and framework.

At this point I can submit another draft.  But ...

I would like to know from the co-authors two things:

  1.  Is there still interest in CL aka Advanced Multipath?
  2.  Any changes in contact information?

I'm particularly interested in whether there is interest at Verizon
since they were the potential user driving this in the first place.
However two of the three Verizon co-authors to the CL drafts are no
longer at Verizon.

No further replies should be interpreted as "no interest" although an
explicit "no interest" would be preferred if that is the case.

If there is interest I'll resubmit this.  If there is still interest
in the framework, we can resurrect that document as well but the
framework needs work and discussion had fallen off to nothing by the
time it expired.

Curtis


From nobody Wed Feb 11 13:31:35 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 515B91A1C05; Wed, 11 Feb 2015 13:31:28 -0800 (PST)
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 gufq_HP0X4wO; Wed, 11 Feb 2015 13:31:22 -0800 (PST)
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 48F5F1A3BA3; Wed, 11 Feb 2015 13:30:52 -0800 (PST)
X-AuditID: c618062d-f79376d000000ceb-4d-54db76688afd
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id A9.74.03307.8667BD45; Wed, 11 Feb 2015 16:34:00 +0100 (CET)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0210.002; Wed, 11 Feb 2015 16:30:50 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>, "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: RtgDir review: draft-ietf-rtgwg-cl-use-cases-06.txt
Thread-Topic: RtgDir review: draft-ietf-rtgwg-cl-use-cases-06.txt
Thread-Index: AQHQRjZQ0kyh0Pj+aUqZnOf/CCiJ+pzrxWmA
Date: Wed, 11 Feb 2015 21:30:50 +0000
Message-ID: <D10108C4.8DB10%jeff.tantsura@ericsson.com>
References: <54C2B86A.6010607@joelhalpern.com> <201502112006.t1BK63b4073326@maildrop31.somerville.occnc.com>
In-Reply-To: <201502112006.t1BK63b4073326@maildrop31.somerville.occnc.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.9]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <068BBC651BE4154DA033DC32A2C9E4E0@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCIsWRmVeSWpSXmKPExsUyuXRPoG5G2e0Qg2nbRS0mzzrDZjH3xxom i4+n3jBZPJ8zk8ViwZqn7BYX3vxmdmDzWLLkJ5PHsvsX2TzOTfnO6PHl8me2AJYoLpuU1JzM stQifbsErozDb7czFyyRrji6dj5zA+N2sS5GTg4JAROJpzs3MUHYYhIX7q1n62Lk4hASOMIo caTjHBOEs5xRYsuab2wgVWwCBhL/vx1nAbFFBOIkLn5ZzQpSxCzwjFFi4dMVYKOEBRwkdi+E KXKUuDDnKzOEbSTR1bmZEcRmEVCV6OzsAxvKK2Au8e3wPzBbSCBP4sHpX+wgNqeAl8SnqdfA 6hmBzvt+ag3YfGYBcYlbT+ZDnS0gsWTPeWYIW1Ti5eN/rCC2qICexLMNm9kh4ooS+/qns0P0 6kncmDqFDcK2ljj+pAFqprbEsoWvmSHuEZQ4OfMJywRGiVlI1s1C0j4LSfssJO2zkLQvYGRd xchRWpxalptuZLCJERitxyTYdHcw7nlpeYhRgINRiYe3oPdWiBBrYllxZe4hRmkOFiVx3kUP DoYICaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRqYOxmT/9+s7Hhffefiwp5P+ecae722dZ2pGyX vNyz+9pdR1WWH9tQfbzPYFP7vG/scj1fow2Yo+LmXsr2D/Y9P0l96bRbDs/mla1QLH8YtmT1 ZKvAvTVnDyl/TV6wqKfx5wHp6Ys6DA7/m9UheZ/lk5co48IZt7xO7lh/oPnAGu29qzW39hmw LrmmxFKckWioxVxUnAgACmLNB7cCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/R7a6Iu3TNWt7epRBZaY1UAe-7NU>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>, "draft-ietf-rtgwg-cl-use-cases@tools.ietf.org" <draft-ietf-rtgwg-cl-use-cases@tools.ietf.org>, "<rtgwg@ietf.org>" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2015 21:31:29 -0000

Hi Curtis,

Please let me know how would you like to proceed with the draft.
If you feel it should progress and since Routing Directorate is done with
no issues found - please resubmit, I=B9ll provide writeup and submit to the
IESG.

Thanks!

Cheers,
Jeff




-----Original Message-----
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Reply-To: "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
Date: Wednesday, February 11, 2015 at 12:06 PM
To: Joel Halpern <jmh@joelhalpern.com>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "<rtgwg@ietf.org>"
<rtgwg@ietf.org>, "draft-ietf-rtgwg-cl-use-cases@tools.ietf.org"
<draft-ietf-rtgwg-cl-use-cases@tools.ietf.org>, "rtg-ads@tools.ietf.org"
<rtg-ads@tools.ietf.org>
Subject: Re: RtgDir review: draft-ietf-rtgwg-cl-use-cases-06.txt

>In message <54C2B86A.6010607@joelhalpern.com>
>"Joel M. Halpern" writes:
>>=20
>> Hello,
>> =20
>> I have been selected as the Routing Directorate reviewer for this
>>draft.=20
>> The Routing Directorate seeks to review all routing or routing-related
>> drafts as they pass through IETF last call and IESG review, and
>> sometimes on special request. The purpose of the review is to provide
>> assistance to the Routing ADs. For more information about the Routing
>> Directorate, please see
>> http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir
>> =20
>> Although these comments are primarily for the use of the Routing ADs,
>>it=20
>> would be helpful if you could consider them along with any other IETF
>> Last Call comments that you receive, and strive to resolve them through
>> discussion or by updating the draft.
>> =20
>> Document: draft-ietf-rtgwg-cl-use-cases-06.txt
>>      Advanced Multipath Use Cases and Design Considerations
>> Reviewer: Joel M. Halpern
>> Review Date: 23-January-2015
>> IETF LC End Date: N/A
>> Intended Status: Informational
>> =20
>> Summary: No issues found. This document is ready for publication.
>> =20
>> Minor note: This draft appears to have expired.
>
>
>Hello again Joel,
>
>FYI - to the Cc.  I emailed Joel off list about this.  This draft lay
>dormant in "AD review" for a long time.  Apparently the AD shepard had
>a change of heart about this .. or something.
>
>The draft itself could be described as inconsequential but contains
>parts of earlier CL requirements draft and CL framework that more
>closely resembled use cases.  This draft exists both to be
>informational and to unclutter the requirements and framework.
>
>At this point I can submit another draft.  But ...
>
>I would like to know from the co-authors two things:
>
>  1.  Is there still interest in CL aka Advanced Multipath?
>  2.  Any changes in contact information?
>
>I'm particularly interested in whether there is interest at Verizon
>since they were the potential user driving this in the first place.
>However two of the three Verizon co-authors to the CL drafts are no
>longer at Verizon.
>
>No further replies should be interpreted as "no interest" although an
>explicit "no interest" would be preferred if that is the case.
>
>If there is interest I'll resubmit this.  If there is still interest
>in the framework, we can resurrect that document as well but the
>framework needs work and discussion had fallen off to nothing by the
>time it expired.
>
>Curtis
>
>_______________________________________________
>rtgwg mailing list
>rtgwg@ietf.org
>https://www.ietf.org/mailman/listinfo/rtgwg


From nobody Thu Feb 12 06:48:08 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 2ADA01A8A65; Thu, 12 Feb 2015 06:48:07 -0800 (PST)
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 2TG-854YpXmW; Thu, 12 Feb 2015 06:48:05 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 14DD21A8A90; Thu, 12 Feb 2015 06:48:04 -0800 (PST)
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-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150212144804.28979.97723.idtracker@ietfa.amsl.com>
Date: Thu, 12 Feb 2015 06:48:04 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/oYvzxbZ7Gh9jzrMvvABXVQKbpJI>
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Feb 2015 14:48:07 -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-01.txt
	Pages           : 31
	Date            : 2015-02-12

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-01

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


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

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


From nobody Thu Feb 12 07:03:06 2015
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBF961A9122; Thu, 12 Feb 2015 07:02:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.891
X-Spam-Level: 
X-Spam-Status: No, score=-0.891 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 InrBImx8A7kh; Thu, 12 Feb 2015 07:02:37 -0800 (PST)
Received: from maildrop31.somerville.occnc.com (maildrop31.somerville.occnc.com [IPv6:2001:550:3800:203::3131]) (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 913551A9027; Thu, 12 Feb 2015 07:02:30 -0800 (PST)
Received: from harbor31.somerville.occnc.com (harbor31.somerville.occnc.com [IPv6:2001:550:3800:203::3231]) (authenticated bits=128) by maildrop31.somerville.occnc.com (8.14.9/8.14.9) with ESMTP id t1CF2Ffd099176; Thu, 12 Feb 2015 10:02:15 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201502121502.t1CF2Ffd099176@maildrop31.somerville.occnc.com>
BTo: Jeff Tantsura <jeff.tantsura@ericsson.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: RtgDir review: draft-ietf-rtgwg-cl-use-cases-06.txt
In-reply-to: Your message of "Wed, 11 Feb 2015 21:30:50 +0000." <D10108C4.8DB10%jeff.tantsura@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <99174.1423753334.1@harbor31.somerville.occnc.com>
Date: Thu, 12 Feb 2015 10:02:15 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/PsJ9DPnlMJr9tp7lazjsmUyiY04>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "draft-ietf-rtgwg-cl-use-cases@tools.ietf.org" <draft-ietf-rtgwg-cl-use-cases@tools.ietf.org>, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>, "Joel M. Halpern" <jmh@joelhalpern.com>, "<rtgwg@ietf.org>" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Feb 2015 15:02:41 -0000

So far I got one message from a co-author and its not encouraging:

  ning.so@tatacommunications.com
    (generated from draft-ietf-rtgwg-cl-use-cases@tools.ietf.org)
    SMTP error from remote mail server \
      after RCPT TO:<ning.so@tatacommunications.com>:
    host mx5.tatacommunications.com [115.114.148.135]:
    550 #5.1.0 Address rejected.

At best that counts as an address change at least temporarily to
"unknown".

This has been idle for very long.  Lets give it a week or two and if
no responses, then move use-cases and framework to abandoned state.
If there is interest in the topic later, a new individual submission
can be started (possibly just a framework) and the WG can decide if
there is enough interest to make that new draft a WG item.

Curtis


In message <D10108C4.8DB10%jeff.tantsura@ericsson.com>
Jeff Tantsura writes:
> 
> Hi Curtis,
>  
> Please let me know how would you like to proceed with the draft.
> If you feel it should progress and since Routing Directorate is done with
> no issues found - please resubmit, I'll provide writeup and submit to the
> IESG.
>  
> Thanks!
>  
> Cheers,
> Jeff
>  
>  
>  
>  
> -----Original Message-----
> From: Curtis Villamizar <curtis@ipv6.occnc.com>
> Reply-To: "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
> Date: Wednesday, February 11, 2015 at 12:06 PM
> To: Joel Halpern <jmh@joelhalpern.com>
> Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "<rtgwg@ietf.org>"
> <rtgwg@ietf.org>, "draft-ietf-rtgwg-cl-use-cases@tools.ietf.org"
> <draft-ietf-rtgwg-cl-use-cases@tools.ietf.org>, "rtg-ads@tools.ietf.org"
> <rtg-ads@tools.ietf.org>
> Subject: Re: RtgDir review: draft-ietf-rtgwg-cl-use-cases-06.txt
>  
> >In message <54C2B86A.6010607@joelhalpern.com>
> >"Joel M. Halpern" writes:
> >> 
> >> Hello,
> >>  
> >> I have been selected as the Routing Directorate reviewer for this
> >>draft. 
> >> The Routing Directorate seeks to review all routing or routing-related
> >> drafts as they pass through IETF last call and IESG review, and
> >> sometimes on special request. The purpose of the review is to provide
> >> assistance to the Routing ADs. For more information about the Routing
> >> Directorate, please see
> >> http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir
> >>  
> >> Although these comments are primarily for the use of the Routing ADs,
> >>it 
> >> would be helpful if you could consider them along with any other IETF
> >> Last Call comments that you receive, and strive to resolve them through
> >> discussion or by updating the draft.
> >>  
> >> Document: draft-ietf-rtgwg-cl-use-cases-06.txt
> >>      Advanced Multipath Use Cases and Design Considerations
> >> Reviewer: Joel M. Halpern
> >> Review Date: 23-January-2015
> >> IETF LC End Date: N/A
> >> Intended Status: Informational
> >>  
> >> Summary: No issues found. This document is ready for publication.
> >>  
> >> Minor note: This draft appears to have expired.
> >
> >
> >Hello again Joel,
> >
> >FYI - to the Cc.  I emailed Joel off list about this.  This draft lay
> >dormant in "AD review" for a long time.  Apparently the AD shepard had
> >a change of heart about this .. or something.
> >
> >The draft itself could be described as inconsequential but contains
> >parts of earlier CL requirements draft and CL framework that more
> >closely resembled use cases.  This draft exists both to be
> >informational and to unclutter the requirements and framework.
> >
> >At this point I can submit another draft.  But ...
> >
> >I would like to know from the co-authors two things:
> >
> >  1.  Is there still interest in CL aka Advanced Multipath?
> >  2.  Any changes in contact information?
> >
> >I'm particularly interested in whether there is interest at Verizon
> >since they were the potential user driving this in the first place.
> >However two of the three Verizon co-authors to the CL drafts are no
> >longer at Verizon.
> >
> >No further replies should be interpreted as "no interest" although an
> >explicit "no interest" would be preferred if that is the case.
> >
> >If there is interest I'll resubmit this.  If there is still interest
> >in the framework, we can resurrect that document as well but the
> >framework needs work and discussion had fallen off to nothing by the
> >time it expired.
> >
> >Curtis
> >
> >_______________________________________________
> >rtgwg mailing list
> >rtgwg@ietf.org
> >https://www.ietf.org/mailman/listinfo/rtgwg


From nobody Thu Feb 12 15:06:27 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 BB70A1A0368; Thu, 12 Feb 2015 15:06:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.911
X-Spam-Level: 
X-Spam-Status: No, score=-13.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_14=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 m17lXWtRJ1jO; Thu, 12 Feb 2015 15:06:25 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9FBA1A008F; Thu, 12 Feb 2015 15:06:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1114; q=dns/txt; s=iport; t=1423782385; x=1424991985; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=jevJWotksWVVynhP8t65dHgsgN7B3JpcXAZE4WGoTlA=; b=Qq5Q1LhwY4HjehDc+nf7nwL0n7jfjlTp7hhNEvjF+qVkcTIzlbkMDKKV AlJEQHlIAnBfavJZfLHgVqiWzqoGXjZ71OVesSmwRnktCjgoZV9SvBrHi aET1SUKvXkojnEcxMgeYEfKQa7GXZQqVEsr3TEky/i0Xc9JAEmf+JfW9d U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkAFAMgx3VStJA2G/2dsb2JhbABbgwaBMIJ+xjWBCUMBAQEBAQF8hBM0VwEkKAQwJwQBiD+hP5xkBpcpAQEBAQEFAQEBAR6BG5FHgUgFjymJM4EYjiqDPiKDboIzfwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,567,1418083200"; d="scan'208";a="392606947"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-9.cisco.com with ESMTP; 12 Feb 2015 23:05:59 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t1CN5wxm002171 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 12 Feb 2015 23:05:58 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.175]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0195.001; Thu, 12 Feb 2015 17:05:57 -0600
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Routing YANG <rtg-yang-coord@ietf.org>, Routing WG <rtgwg@ietf.org>, Thomas Morin <thomas.morin@orange-ftgroup.com>, Ladislav Lhotka <lhotka@nic.cz>
Subject: rtg-cfg draft hierarchy (Reply to this one) 
Thread-Topic: rtg-cfg draft hierarchy (Reply to this one) 
Thread-Index: AQHQRxh1ZqTFjLUtMEu1r3b/ugmA/w==
Date: Thu, 12 Feb 2015 23:05:57 +0000
Message-ID: <D1029C03.E4F6%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.152.200]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <1DEF16B43DD0EB43A323A7FEF3577C25@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/xwKZVVm4a-euhKBvNPfbKsSxhGc>
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, 12 Feb 2015 23:06:27 -0000

SGkgVGhvbWFzLCANCg0KSXQgaXMgbXkgdW5kZXJzdGFuZGluZyB0aGF0IHRoZSBSSUJzIHdlcmUg
bW92ZWQgb3V0IG9mIHRoZQ0Kcm91dGluZy1pbnN0YW5jZSBpbiByZXNwb25zZSB0byB5b3VyIGNv
bW1lbnQgdGhhdCBhIFJJQiB3b3VsZCBuZWVkIHRvIGJlDQphdHRhY2hlZCB0byBtdWx0aXBsZSBy
b3V0aW5nIGluc3RhbmNlcy4gSSBkb26p9nQgYWdyZWUgd2l0aCB0aGlzIG1vZGVsLiBJDQpiZWxp
ZXZlIHRoYXQgYSByb3V0aW5nIGluc3RhbmNlIGltcGxpZXMgYSBWUkYsIHZpcnR1YWwgcm91dGVy
IG9yIHNvbWV0aGluZw0KaW4gYmV0d2VlbiBhbmQgdGhhdCBhIFJJQiBzaG91bGQgYmUgYXNzb2Np
YXRlZCB3aXRoIG9uZSBhbmQgb25seSBvbmUNCnJvdXRpbmcgaW5zdGFuY2UuIEFkZGl0aW9uYWxs
eSwgSSBmZWVsIHRoYXQgUklCcyBhcmUgYmFzaWNhbGx5IHBhc3NpdmUNCmVudGl0aWVzIHdpdGgg
cmVzcGVjdCB0byBpbXBvcnQvZXhwb3J0IG9mIHJvdXRlcyBiZXR3ZWVuIFJJQnMgaW4gdGhlIHNh
bWUNCm9yIG90aGVyIHJvdXRpbmctaW5zdGFuY2VzLiBSYXRoZXIsIGFsbCBpbXBvcnQvZXhwb3J0
IGlzIHVuZGVyIHRoZSBjb250cm9sDQpvZiBhIHJvdXRpbmctcHJvdG9jb2wuIEZvciBleGFtcGxl
LCB0aGlzIHdvdWxkIGJlIGhhbmRsZWQgYnkgYSBCR1ANCnJvdXRpbmctcHJvdG9jb2wgaW5zdGFu
Y2UgZm9yIEwzVlBOcy4NCg0KSan2ZCBsaWtlIHRvIGdldCB0aGUgb3BpbmlvbnMgb2Ygb3RoZXJz
IG9uIHRoaXMgZnVuZGFtZW50YWwgYXNwZWN0IG9mIHRoZQ0KcnRnLWNmZyBtb2RlbC4gDQoNClRo
YW5rcywNCkFjZWUNCg0K


From nobody Thu Feb 12 15:09:51 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 E71671A008F; Thu, 12 Feb 2015 15:09:47 -0800 (PST)
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 yytubQjVVXbj; Thu, 12 Feb 2015 15:09:45 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 067331A1A4F; Thu, 12 Feb 2015 15:09:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2085; q=dns/txt; s=iport; t=1423782584; x=1424992184; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=vEDsKePdCR9yCgTFrvu39WtSkJpXL1u97SeQsEy7NSU=; b=ReWj8jQPTm1W8FMagyYcQSPz/jLrDKCCnmqV31tZ51gqqlFfyP9FfvPs fNIlGDSgYcpDuFI051s6q+9p1W79MnLN1gJP+d6c6s7K0AeEG44W8Fn5v 3+qq9VsHXy4B28fIQVv37ksv+5kocChEAtCaa+gdkwM5dfGw+v+zNZD3e g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkIFAGox3VStJV2d/2dsb2JhbABYA4MGUloEwyCFdQKBJUMBAQEBAQF8hA0BAQRyBw4CAgEIDgIILhsXJQIEAQ0FG4gS1VABAQEBAQEBAQEBAQEBAQEBAQEBAQEXBIsIhF0QBxGEGQWKAoUniTOBGI4qgz4ig25vgUR/AQEB
X-IronPort-AV: E=Sophos;i="5.09,567,1418083200"; d="scan'208";a="396071617"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-2.cisco.com with ESMTP; 12 Feb 2015 23:09:43 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id t1CN9hxL012936 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 12 Feb 2015 23:09:43 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.175]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0195.001; Thu, 12 Feb 2015 17:09:42 -0600
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Xufeng Liu <xufeng.liu@ericsson.com>
Subject: Re: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances
Thread-Topic: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances
Thread-Index: AQHQRxj77tD6GUYxhkmEAnTuReZw3g==
Date: Thu, 12 Feb 2015 23:09:42 +0000
Message-ID: <D1029726.E4B5%acee@cisco.com>
References: <AAB1CC9C17CBA440BDFA169056B93B9EB10521@eusaamb107.ericsson.se> <35023717-7EE8-4F45-B2F4-B24E0F86FA5A@nic.cz> <20150113212732.GD1545@elstar.local> <23976026-499F-4C9C-844A-DB53BE244992@nic.cz> <AAB1CC9C17CBA440BDFA169056B93B9EB1128D@eusaamb107.ericsson.se> <20150114155450.GA3625@elstar.local> <AAB1CC9C17CBA440BDFA169056B93B9EB1139B@eusaamb107.ericsson.se> <CABCOCHSiWG=x0vTYKKxqhMqd69yK+Nuo0k_Y_=Y_KHkQBDi3FA@mail.gmail.com> <D0DBD855.889EB%jeff.tantsura@ericsson.com> <AAB1CC9C17CBA440BDFA169056B93B9EB11472@eusaamb107.ericsson.se> <20150114174655.GA3932@elstar.local>
In-Reply-To: <20150114174655.GA3932@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.152.200]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <46F9CFCEA069744DADDD76A62BE62B93@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/_j0QBlq6BrUCKNX3_sSsfYQK5zg>
Cc: "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>, Routing WG <rtgwg@ietf.org>, Andy Bierman <andy@yumaworks.com>
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, 12 Feb 2015 23:09:48 -0000

I believe the fact that we are having trouble resolving this is that the
model is wrong. I would propose the following:

   1. Remove the interface list completely from rtf-cfg configuration.
   2. Augment the RFC 7223 to include a reference to a routing-instance.
An interface should be part of one and only one routing-instance.
   3. Provide a list of interfaces in the operational state in the rtg-cfg
model.=20

One reason I'm proposing this change is that I believe a routing-instance
implies an IPv4/IPv6 address space and the interfaces list MUST NOT be
disjoint from the assigned addresses (refer to RFC 7277). If you want to
have a list of interfaces in the routing-instance, you should deprecate
RFC 7277 or, at least, say that it only applies to the default instance.

In all fairness, Lada disagrees with me on this point and wants the
flexibility of associating an interface with multiple routing-instances.
Additionally, he feels that the list inside the routing-instance will
facilitate better interface selection checking. I don=B9t see the latter as
an issue as the same checking could be applied when an attempt is made to
augment the RFC 7223 interface.

Thanks,
Acee=20

  =20

On 1/14/15, 12:46 PM, "Juergen Schoenwaelder"
<j.schoenwaelder@jacobs-university.de> wrote:

>On Wed, Jan 14, 2015 at 04:43:29PM +0000, Xufeng Liu wrote:
>> Hi Andy,
>>=20
>> The concatenated string format is actually what we plan to do. However,
>>to me, it is more like a hack than an engineered solution. The model
>>fails to capture such a relationship properly.
>>
>
>If your interface names are no unique, I would assume that you will
>face other issues as well. For example, one may use an interface name
>to disambiguate link-local addresses. I am not sure how that works if
>your interface name is not unique.
>
>/js
>
>--=20
>Juergen Schoenwaelder           Jacobs University Bremen gGmbH
>Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
>Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


From nobody Thu Feb 12 15:18:30 2015
Return-Path: <antoni.przygienda@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 EB80A1A6F22; Thu, 12 Feb 2015 15:18:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.601
X-Spam-Level: 
X-Spam-Status: No, score=-3.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6, 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 yZV_zBqip5DC; Thu, 12 Feb 2015 15:18:26 -0800 (PST)
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 3D4471A1DBE; Thu, 12 Feb 2015 15:18:02 -0800 (PST)
X-AuditID: c618062d-f79376d000000ceb-79-54dce0f7fe13
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 2D.68.03307.7F0ECD45; Thu, 12 Feb 2015 18:20:56 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0210.002; Thu, 12 Feb 2015 18:18:00 -0500
From: Antoni Przygienda <antoni.przygienda@ericsson.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, Routing YANG <rtg-yang-coord@ietf.org>, Routing WG <rtgwg@ietf.org>, Thomas Morin <thomas.morin@orange-ftgroup.com>, Ladislav Lhotka <lhotka@nic.cz>
Subject: RE: rtg-cfg draft hierarchy (Reply to this one) 
Thread-Topic: rtg-cfg draft hierarchy (Reply to this one) 
Thread-Index: AQHQRxh1ZqTFjLUtMEu1r3b/ugmA/5ztozGw
Date: Thu, 12 Feb 2015 23:18:00 +0000
Message-ID: <2E4BB27CAB87BF43B4207C0E55860F1824B724@eusaamb103.ericsson.se>
References: <D1029C03.E4F6%acee@cisco.com>
In-Reply-To: <D1029C03.E4F6%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDLMWRmVeSWpSXmKPExsUyuXRPgu6PB3dCDP5NELKY/HYes8WFVXPZ LH4/vw1kvfnNbLF5+VoWB1aPKb83snosWfKTyWPT5TuMHj+OhQWwRHHZpKTmZJalFunbJXBl XD14jrXglkDF3sOt7A2MR3i7GDk5JARMJDbfXMoEYYtJXLi3ng3EFhI4wiixbG58FyMXkL2c UeLbrGfMIAk2AQuJy9+eMoMkRAQOM0pMv7WYBSQhLGAp0baykxXEFhGwktg68ymQzQFkG0k8 3WgIEmYRUJV4svw1O4jNK+AtcWtWNzPEMi2JS8engsU5BbQlbuzbAhZnBDro+6k1YMcxC4hL 3HoyH+pQAYkle84zQ9iiEi8f/2OFsJUkJi09xwpRrydxY+oUNghbW2LZwtfMEHsFJU7OfMIy gVF0FpKxs5C0zELSMgtJywJGllWMHKXFqWW56UYGmxiB0XNMgk13B+Oel5aHGAU4GJV4eA3E 74QIsSaWFVfmHmKU5mBREudd9OBgiJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQbG4L9hB7Pq +Lruxk3WlZ3Gvenylqsbu2IKYwKqe1XkrI5eFz5y+PYRofTeuZ9fvLmzT/yoROXJNex32ozO 6q/5UJQ022Gl7hxd9g8Lr/rvkDbi91/3f4e553KJojnxEuyn2D+dPN/8iINpf9r5npK7PVOL t/M5uP/WelDDLq5wbI/KvJZArbnLlFiKMxINtZiLihMBKXBtzX8CAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/8I46drCAsNGFzZnnJOiO_63_24M>
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, 12 Feb 2015 23:18:29 -0000

In short, I agree with Mr. Lindem (unsurprisingly).

An "n to 1"  model between (same) routing protocol instances and RIB presen=
ts many unresolvable problems as soon address spaces overlap. Basically rou=
te from instance 1 becomes undistinguishable from route from instance 2 wit=
h same address (RDs are not intended to be in RIB, they are local concepts =
within a protocol).  One could image different ADs _per_ instance of same p=
rotocol but I'd like to see the use case for that.=20

Same for interfaces, an interface has an address (generally, let's not disc=
uss link locals and unnumbered and such) and the address is in an address s=
pace. RIB is basically a closure of an 'routable' address space and its sum=
maries (prefixes) over multiple protocols dealing with reachability computa=
tion.

--- tony=20

> -----Original Message-----
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Acee Lindem (ace=
e)
> Sent: Thursday, February 12, 2015 3:06 PM
> To: Routing YANG; Routing WG; Thomas Morin; Ladislav Lhotka
> Subject: rtg-cfg draft hierarchy (Reply to this one)
>=20
> Hi Thomas,
>=20
> It is my understanding that the RIBs were moved out of the routing-instan=
ce in
> response to your comment that a RIB would need to be attached to multiple
> routing instances. I don=B9t agree with this model. I believe that a rout=
ing instance
> implies a VRF, virtual router or something in between and that a RIB shou=
ld be
> associated with one and only one routing instance. Additionally, I feel t=
hat RIBs
> are basically passive entities with respect to import/export of routes be=
tween
> RIBs in the same or other routing-instances. Rather, all import/export is=
 under
> the control of a routing-protocol. For example, this would be handled by =
a BGP
> routing-protocol instance for L3VPNs.
>=20
> I=B9d like to get the opinions of others on this fundamental aspect of th=
e rtg-cfg
> model.
>=20
> Thanks,
> Acee
>=20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


From nobody Fri Feb 13 02:26:05 2015
Return-Path: <lhotka@nic.cz>
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 373931A6F24; Fri, 13 Feb 2015 02:26:02 -0800 (PST)
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 JAvQaLG6_WY5; Fri, 13 Feb 2015 02:25:57 -0800 (PST)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id 3EF671A6F22; Fri, 13 Feb 2015 02:25:57 -0800 (PST)
Received: from localhost (unknown [195.113.220.110]) by trail.lhotka.name (Postfix) with ESMTPSA id 3515B1CC05B5; Fri, 13 Feb 2015 11:25:56 +0100 (CET)
From: Ladislav Lhotka <lhotka@nic.cz>
To: "Acee Lindem \(acee\)" <acee@cisco.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Xufeng Liu <xufeng.liu@ericsson.com>
Subject: Re: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances
In-Reply-To: <D1029726.E4B5%acee@cisco.com>
References: <AAB1CC9C17CBA440BDFA169056B93B9EB10521@eusaamb107.ericsson.se> <35023717-7EE8-4F45-B2F4-B24E0F86FA5A@nic.cz> <20150113212732.GD1545@elstar.local> <23976026-499F-4C9C-844A-DB53BE244992@nic.cz> <AAB1CC9C17CBA440BDFA169056B93B9EB1128D@eusaamb107.ericsson.se> <20150114155450.GA3625@elstar.local> <AAB1CC9C17CBA440BDFA169056B93B9EB1139B@eusaamb107.ericsson.se> <CABCOCHSiWG=x0vTYKKxqhMqd69yK+Nuo0k_Y_=Y_KHkQBDi3FA@mail.gmail.com> <D0DBD855.889EB%jeff.tantsura@ericsson.com> <AAB1CC9C17CBA440BDFA169056B93B9EB11472@eusaamb107.ericsson.se> <20150114174655.GA3932@elstar.local> <D1029726.E4B5%acee@cisco.com>
User-Agent: Notmuch/0.19 (http://notmuchmail.org) Emacs/24.4.51.2 (x86_64-apple-darwin14.0.0)
Date: Fri, 13 Feb 2015 11:25:58 +0100
Message-ID: <m2k2zm9kg9.fsf@birdie.labs.nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/xHBFmn8OHkO_2YBtTzrP_aq0Ryk>
Cc: "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>, Andy Bierman <andy@yumaworks.com>, Routing WG <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, 13 Feb 2015 10:26:02 -0000

"Acee Lindem (acee)" <acee@cisco.com> writes:

> I believe the fact that we are having trouble resolving this is that the
> model is wrong. I would propose the following:

I don't agree the model is wrong. In fact, I belive in Junos CLI it is
done exactly the same way, e.g.

  set interface fe-0/0/2 unit 0 family inet address 6.6.6.5/24

  set routing-instances blue-vr interface fe-0/0/2.0

(IP address is configured in the interface subtree, and an interface is
assigned to a VRF in the routing-instance subtree).

I believe the troubles we are having are due to the different logic in
the CLIs of the two major routing platforms.

Lada

>
>    1. Remove the interface list completely from rtf-cfg configuration.
>    2. Augment the RFC 7223 to include a reference to a routing-instance.
> An interface should be part of one and only one routing-instance.
>    3. Provide a list of interfaces in the operational state in the rtg-cfg
> model.=20
>
> One reason I'm proposing this change is that I believe a routing-instance
> implies an IPv4/IPv6 address space and the interfaces list MUST NOT be
> disjoint from the assigned addresses (refer to RFC 7277). If you want to
> have a list of interfaces in the routing-instance, you should deprecate
> RFC 7277 or, at least, say that it only applies to the default instance.
>
> In all fairness, Lada disagrees with me on this point and wants the
> flexibility of associating an interface with multiple routing-instances.
> Additionally, he feels that the list inside the routing-instance will
> facilitate better interface selection checking. I don=C2=B9t see the latt=
er as
> an issue as the same checking could be applied when an attempt is made to
> augment the RFC 7223 interface.
>
> Thanks,
> Acee=20
>
>=20=20=20=20
>
> On 1/14/15, 12:46 PM, "Juergen Schoenwaelder"
> <j.schoenwaelder@jacobs-university.de> wrote:
>
>>On Wed, Jan 14, 2015 at 04:43:29PM +0000, Xufeng Liu wrote:
>>> Hi Andy,
>>>=20
>>> The concatenated string format is actually what we plan to do. However,
>>>to me, it is more like a hack than an engineered solution. The model
>>>fails to capture such a relationship properly.
>>>
>>
>>If your interface names are no unique, I would assume that you will
>>face other issues as well. For example, one may use an interface name
>>to disambiguate link-local addresses. I am not sure how that works if
>>your interface name is not unique.
>>
>>/js
>>
>>--=20
>>Juergen Schoenwaelder           Jacobs University Bremen gGmbH
>>Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
>>Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
>

--=20
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C


From nobody Fri Feb 13 09:45:52 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 702001A001B; Fri, 13 Feb 2015 09:45:38 -0800 (PST)
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 NEN4UxZ7FnLU; Fri, 13 Feb 2015 09:45:34 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91EAE1A0018; Fri, 13 Feb 2015 09:45:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4710; q=dns/txt; s=iport; t=1423849536; x=1425059136; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=tqKO0oqnhi3KGjpQ0GoQS6jF5JlKsR2avfYIm38NB/w=; b=hqVjGX4x6d4pbUYhxkQKIbFO7n90cPQuhS/7yHrfme+tH+0RqawVPf/c +xLOOFE9vf4Q7FOlE/X3yuZpaKJRnnLd7U+bwuOlqdtXT9uu8XDvjOhVw sWELCjzunbtA1XH1bqhjh9fEqFA2cxMeFMETmk5PeEzCGRCdPZ8QZSh77 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AtBQCON95U/5NdJa1YA4MGUloEgn6/KIV1Ahx4QwEBAQEBAXyEDQEBBDQ+Bw4CAgEIEAgEKAICGRclAgQBDQUbiBKhS5xkBpciAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwSBF4lxhDoYCxAHEYJRgUgFjzSJNYEYji+DPiKDbm+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.09,572,1418083200"; d="scan'208";a="123368306"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-3.cisco.com with ESMTP; 13 Feb 2015 17:45:35 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t1DHjXLD021284 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 13 Feb 2015 17:45:33 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.175]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0195.001; Fri, 13 Feb 2015 11:45:33 -0600
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Ladislav Lhotka <lhotka@nic.cz>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Xufeng Liu <xufeng.liu@ericsson.com>
Subject: Re: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances
Thread-Topic: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances
Thread-Index: AQHQRxj77tD6GUYxhkmEAnTuReZw3pzuxUwAgAAm/wA=
Date: Fri, 13 Feb 2015 17:45:33 +0000
Message-ID: <D103A0D5.E60D%acee@cisco.com>
References: <AAB1CC9C17CBA440BDFA169056B93B9EB10521@eusaamb107.ericsson.se> <35023717-7EE8-4F45-B2F4-B24E0F86FA5A@nic.cz> <20150113212732.GD1545@elstar.local> <23976026-499F-4C9C-844A-DB53BE244992@nic.cz> <AAB1CC9C17CBA440BDFA169056B93B9EB1128D@eusaamb107.ericsson.se> <20150114155450.GA3625@elstar.local> <AAB1CC9C17CBA440BDFA169056B93B9EB1139B@eusaamb107.ericsson.se> <CABCOCHSiWG=x0vTYKKxqhMqd69yK+Nuo0k_Y_=Y_KHkQBDi3FA@mail.gmail.com> <D0DBD855.889EB%jeff.tantsura@ericsson.com> <AAB1CC9C17CBA440BDFA169056B93B9EB11472@eusaamb107.ericsson.se> <20150114174655.GA3932@elstar.local> <D1029726.E4B5%acee@cisco.com> <m2k2zm9kg9.fsf@birdie.labs.nic.cz>
In-Reply-To: <m2k2zm9kg9.fsf@birdie.labs.nic.cz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.152.200]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <75C74B08A8E30A46AF60F338B03F1736@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/gfWULzjS3nUSlKh_IJe3dA5LcmI>
Cc: "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>, Andy Bierman <andy@yumaworks.com>, Routing WG <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, 13 Feb 2015 17:45:38 -0000

DQoNCk9uIDIvMTMvMTUsIDU6MjUgQU0sICJMYWRpc2xhdiBMaG90a2EiIDxsaG90a2FAbmljLmN6
PiB3cm90ZToNCg0KPiJBY2VlIExpbmRlbSAoYWNlZSkiIDxhY2VlQGNpc2NvLmNvbT4gd3JpdGVz
Og0KPg0KPj4gSSBiZWxpZXZlIHRoZSBmYWN0IHRoYXQgd2UgYXJlIGhhdmluZyB0cm91YmxlIHJl
c29sdmluZyB0aGlzIGlzIHRoYXQgdGhlDQo+PiBtb2RlbCBpcyB3cm9uZy4gSSB3b3VsZCBwcm9w
b3NlIHRoZSBmb2xsb3dpbmc6DQo+DQo+SSBkb24ndCBhZ3JlZSB0aGUgbW9kZWwgaXMgd3Jvbmcu
IEluIGZhY3QsIEkgYmVsaXZlIGluIEp1bm9zIENMSSBpdCBpcw0KPmRvbmUgZXhhY3RseSB0aGUg
c2FtZSB3YXksIGUuZy4NCj4NCj4gIHNldCBpbnRlcmZhY2UgZmUtMC8wLzIgdW5pdCAwIGZhbWls
eSBpbmV0IGFkZHJlc3MgNi42LjYuNS8yNA0KPg0KPiAgc2V0IHJvdXRpbmctaW5zdGFuY2VzIGJs
dWUtdnIgaW50ZXJmYWNlIGZlLTAvMC8yLjANCj4NCj4oSVAgYWRkcmVzcyBpcyBjb25maWd1cmVk
IGluIHRoZSBpbnRlcmZhY2Ugc3VidHJlZSwgYW5kIGFuIGludGVyZmFjZSBpcw0KPmFzc2lnbmVk
IHRvIGEgVlJGIGluIHRoZSByb3V0aW5nLWluc3RhbmNlIHN1YnRyZWUpLg0KPg0KPkkgYmVsaWV2
ZSB0aGUgdHJvdWJsZXMgd2UgYXJlIGhhdmluZyBhcmUgZHVlIHRvIHRoZSBkaWZmZXJlbnQgbG9n
aWMgaW4NCj50aGUgQ0xJcyBvZiB0aGUgdHdvIG1ham9yIHJvdXRpbmcgcGxhdGZvcm1zLg0KDQpE
b2VzIGl0IHNob3cgdXAgYXMgYSBzZXBhcmF0ZSBsaXN0IGluIHRoZSBKVU5PUyBnYXRlZC1saWtl
IGNvbmZpZ3VyYXRpb24NCmhpZXJhcmNoeT8gSWYgdGhleSBkbyBjb25maWd1cmUgdGhlIElQdjQv
SVB2NiBhZGRyZXNzZXMgZGlzam9pbnQgZnJvbSB0aGUNCnJvdXRpbmcgLWluc3RhbmNlIGluc3Rh
bmNlcyBpbXBseSB0aGUgY29ycmVzcG9uZGluZyBJUHY0L0lQdjYgYWRkcmVzcw0Kc3BhY2UgYW5k
IHRoZSBSSUJzLCBJIHN0aWxsIGRvbqGvdCBsaWtlIHRoZSBpbmNvbnNpc3RlbmN5Lg0KDQpUaGUg
cHJldmlvdXMgcHJvZHVjdCBJIHdvcmtlZCBvbiwgSVBPUywgaGFkIHRoZSBpbnRlcmZhY2VzIGlu
DQpyb3V0aW5nLWluc3RhbmNlIGJ1dCB0aGUgcm91dGluZy1pbnN0YW5jZSBpbnRlcmZhY2UgaW5j
bHVkZWQgYWxsIHRoZSBsYXllcg0KMyBkZWZpbml0aW9uIGluY2x1ZGluZyB0aGUgSVAvSVB2NiBh
ZGRyZXNzZXMgKGkuZS4sIHRoZSBSRkMgNzI3Nw0KZGVmaW5pdGlvbnMpLiANCg0KVGhhbmtzLA0K
QWNlZSANCg0KDQoNCg0KDQoNCj4NCj5MYWRhDQo+DQo+Pg0KPj4gICAgMS4gUmVtb3ZlIHRoZSBp
bnRlcmZhY2UgbGlzdCBjb21wbGV0ZWx5IGZyb20gcnRmLWNmZyBjb25maWd1cmF0aW9uLg0KPj4g
ICAgMi4gQXVnbWVudCB0aGUgUkZDIDcyMjMgdG8gaW5jbHVkZSBhIHJlZmVyZW5jZSB0byBhIHJv
dXRpbmctaW5zdGFuY2UuDQo+PiBBbiBpbnRlcmZhY2Ugc2hvdWxkIGJlIHBhcnQgb2Ygb25lIGFu
ZCBvbmx5IG9uZSByb3V0aW5nLWluc3RhbmNlLg0KPj4gICAgMy4gUHJvdmlkZSBhIGxpc3Qgb2Yg
aW50ZXJmYWNlcyBpbiB0aGUgb3BlcmF0aW9uYWwgc3RhdGUgaW4gdGhlDQo+PnJ0Zy1jZmcNCj4+
IG1vZGVsLiANCj4+DQo+PiBPbmUgcmVhc29uIEknbSBwcm9wb3NpbmcgdGhpcyBjaGFuZ2UgaXMg
dGhhdCBJIGJlbGlldmUgYQ0KPj5yb3V0aW5nLWluc3RhbmNlDQo+PiBpbXBsaWVzIGFuIElQdjQv
SVB2NiBhZGRyZXNzIHNwYWNlIGFuZCB0aGUgaW50ZXJmYWNlcyBsaXN0IE1VU1QgTk9UIGJlDQo+
PiBkaXNqb2ludCBmcm9tIHRoZSBhc3NpZ25lZCBhZGRyZXNzZXMgKHJlZmVyIHRvIFJGQyA3Mjc3
KS4gSWYgeW91IHdhbnQgdG8NCj4+IGhhdmUgYSBsaXN0IG9mIGludGVyZmFjZXMgaW4gdGhlIHJv
dXRpbmctaW5zdGFuY2UsIHlvdSBzaG91bGQgZGVwcmVjYXRlDQo+PiBSRkMgNzI3NyBvciwgYXQg
bGVhc3QsIHNheSB0aGF0IGl0IG9ubHkgYXBwbGllcyB0byB0aGUgZGVmYXVsdCBpbnN0YW5jZS4N
Cj4+DQo+PiBJbiBhbGwgZmFpcm5lc3MsIExhZGEgZGlzYWdyZWVzIHdpdGggbWUgb24gdGhpcyBw
b2ludCBhbmQgd2FudHMgdGhlDQo+PiBmbGV4aWJpbGl0eSBvZiBhc3NvY2lhdGluZyBhbiBpbnRl
cmZhY2Ugd2l0aCBtdWx0aXBsZSByb3V0aW5nLWluc3RhbmNlcy4NCj4+IEFkZGl0aW9uYWxseSwg
aGUgZmVlbHMgdGhhdCB0aGUgbGlzdCBpbnNpZGUgdGhlIHJvdXRpbmctaW5zdGFuY2Ugd2lsbA0K
Pj4gZmFjaWxpdGF0ZSBiZXR0ZXIgaW50ZXJmYWNlIHNlbGVjdGlvbiBjaGVja2luZy4gSSBkb26p
9nQgc2VlIHRoZSBsYXR0ZXINCj4+YXMNCj4+IGFuIGlzc3VlIGFzIHRoZSBzYW1lIGNoZWNraW5n
IGNvdWxkIGJlIGFwcGxpZWQgd2hlbiBhbiBhdHRlbXB0IGlzIG1hZGUNCj4+dG8NCj4+IGF1Z21l
bnQgdGhlIFJGQyA3MjIzIGludGVyZmFjZS4NCj4+DQo+PiBUaGFua3MsDQo+PiBBY2VlIA0KPj4N
Cj4+ICAgIA0KPj4NCj4+IE9uIDEvMTQvMTUsIDEyOjQ2IFBNLCAiSnVlcmdlbiBTY2hvZW53YWVs
ZGVyIg0KPj4gPGouc2Nob2Vud2FlbGRlckBqYWNvYnMtdW5pdmVyc2l0eS5kZT4gd3JvdGU6DQo+
Pg0KPj4+T24gV2VkLCBKYW4gMTQsIDIwMTUgYXQgMDQ6NDM6MjlQTSArMDAwMCwgWHVmZW5nIExp
dSB3cm90ZToNCj4+Pj4gSGkgQW5keSwNCj4+Pj4gDQo+Pj4+IFRoZSBjb25jYXRlbmF0ZWQgc3Ry
aW5nIGZvcm1hdCBpcyBhY3R1YWxseSB3aGF0IHdlIHBsYW4gdG8gZG8uDQo+Pj4+SG93ZXZlciwN
Cj4+Pj50byBtZSwgaXQgaXMgbW9yZSBsaWtlIGEgaGFjayB0aGFuIGFuIGVuZ2luZWVyZWQgc29s
dXRpb24uIFRoZSBtb2RlbA0KPj4+PmZhaWxzIHRvIGNhcHR1cmUgc3VjaCBhIHJlbGF0aW9uc2hp
cCBwcm9wZXJseS4NCj4+Pj4NCj4+Pg0KPj4+SWYgeW91ciBpbnRlcmZhY2UgbmFtZXMgYXJlIG5v
IHVuaXF1ZSwgSSB3b3VsZCBhc3N1bWUgdGhhdCB5b3Ugd2lsbA0KPj4+ZmFjZSBvdGhlciBpc3N1
ZXMgYXMgd2VsbC4gRm9yIGV4YW1wbGUsIG9uZSBtYXkgdXNlIGFuIGludGVyZmFjZSBuYW1lDQo+
Pj50byBkaXNhbWJpZ3VhdGUgbGluay1sb2NhbCBhZGRyZXNzZXMuIEkgYW0gbm90IHN1cmUgaG93
IHRoYXQgd29ya3MgaWYNCj4+PnlvdXIgaW50ZXJmYWNlIG5hbWUgaXMgbm90IHVuaXF1ZS4NCj4+
Pg0KPj4+L2pzDQo+Pj4NCj4+Pi0tIA0KPj4+SnVlcmdlbiBTY2hvZW53YWVsZGVyICAgICAgICAg
ICBKYWNvYnMgVW5pdmVyc2l0eSBCcmVtZW4gZ0dtYkgNCj4+PlBob25lOiArNDkgNDIxIDIwMCAz
NTg3ICAgICAgICAgQ2FtcHVzIFJpbmcgMSwgMjg3NTkgQnJlbWVuLCBHZXJtYW55DQo+Pj5GYXg6
ICAgKzQ5IDQyMSAyMDAgMzEwMyAgICAgICAgIDxodHRwOi8vd3d3LmphY29icy11bml2ZXJzaXR5
LmRlLz4NCj4+DQo+DQo+LS0gDQo+TGFkaXNsYXYgTGhvdGthLCBDWi5OSUMgTGFicw0KPlBHUCBL
ZXkgSUQ6IEU3NEU4QzBDDQoNCg==


From nobody Fri Feb 13 10:07:25 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 848801A0161; Fri, 13 Feb 2015 10:07:16 -0800 (PST)
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 3Dp7IJIwr2ZI; Fri, 13 Feb 2015 10:07:13 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 872151A007C; Fri, 13 Feb 2015 10:07:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5526; q=dns/txt; s=iport; t=1423850833; x=1425060433; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=HLwtn8XWKaKxFvHxasJkOzjmBxrcADoBjAVbr5LjpNk=; b=bzlcSvoVOhkSIHsOR/caG7DC7SbNI+GJ8IkzUwicrhdk8rb7Abhg7fK3 uUjk/2Cb3Kjbv759NZ2k+FHAGSJ7wewLEDkc7LFBe0P/fCLsXjOr+awN2 SSAmd7FXmkd5KRUYK7yoEsqv1NlmiOv2IJf/a9DajqNqkB4bB9wb/x4hy g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A0BQDpPN5U/4MNJK1YA4MGUk8LBIJ+vyIKhXECHHhDAQEBAQEBfIQNAQEEAQEBMToEBw4CAgEIEAgEKAICGQwLJQIEAQ0FG4gSDaEwnGQGlyABAQEBAQEBAQEBAQEBAQEBAQEBAQEXBIEXiXGEOhgLEAcRglGBSAWPNIk1gRiOL4M+IoNub4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,572,1418083200"; d="scan'208";a="123381400"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-6.cisco.com with ESMTP; 13 Feb 2015 18:07:12 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t1DI7CVL028468 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 13 Feb 2015 18:07:12 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.175]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0195.001; Fri, 13 Feb 2015 12:07:12 -0600
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, Ladislav Lhotka <lhotka@nic.cz>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Xufeng Liu <xufeng.liu@ericsson.com>
Subject: Re: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances
Thread-Topic: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances
Thread-Index: AQHQRxj77tD6GUYxhkmEAnTuReZw3pzuxUwAgAAm/wCAAAYLAA==
Date: Fri, 13 Feb 2015 18:07:11 +0000
Message-ID: <D103A6D1.E624%acee@cisco.com>
References: <AAB1CC9C17CBA440BDFA169056B93B9EB10521@eusaamb107.ericsson.se> <35023717-7EE8-4F45-B2F4-B24E0F86FA5A@nic.cz> <20150113212732.GD1545@elstar.local> <23976026-499F-4C9C-844A-DB53BE244992@nic.cz> <AAB1CC9C17CBA440BDFA169056B93B9EB1128D@eusaamb107.ericsson.se> <20150114155450.GA3625@elstar.local> <AAB1CC9C17CBA440BDFA169056B93B9EB1139B@eusaamb107.ericsson.se> <CABCOCHSiWG=x0vTYKKxqhMqd69yK+Nuo0k_Y_=Y_KHkQBDi3FA@mail.gmail.com> <D0DBD855.889EB%jeff.tantsura@ericsson.com> <AAB1CC9C17CBA440BDFA169056B93B9EB11472@eusaamb107.ericsson.se> <20150114174655.GA3932@elstar.local> <D1029726.E4B5%acee@cisco.com> <m2k2zm9kg9.fsf@birdie.labs.nic.cz> <D103A0D5.E60D%acee@cisco.com>
In-Reply-To: <D103A0D5.E60D%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.152.200]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <E446C1455FAD814B9128FCEB68B62EB5@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/BUHt-zWpcY9pJPPH1PQfz2grQEo>
Cc: "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>, Andy Bierman <andy@yumaworks.com>, Routing WG <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, 13 Feb 2015 18:07:17 -0000

SW5kZXBlbmRlbnQgb2YgdGhlIGhpZXJhcmNoeSwgSSB0aGluayBhbiBpbnRlcmZhY2Ugc2hvdWxk
IGJlIGFzc29jaWF0ZWQNCndpdGggb25lIGFuZCBvbmx5IHJvdXRpbmctaW5zdGFuY2UuIEkga25v
dyBvZiBubyBpbXBsZW1lbnRhdGlvbiB0aGF0DQphbGxvd3MgdGhpcyAoaW5jbHVkaW5nIHRoZSB1
c2UgY2FzZSBvZiBzZXBhcmF0ZSBpbnN0YW5jZXMgZm9yIElQdjQgYW5kDQpJUHY2KS4gDQoNClRo
YW5rcywNCkFjZWUgDQoNCk9uIDIvMTMvMTUsIDEyOjQ1IFBNLCAiQWNlZSBMaW5kZW0gKGFjZWUp
IiA8YWNlZUBjaXNjby5jb20+IHdyb3RlOg0KDQo+DQo+DQo+T24gMi8xMy8xNSwgNToyNSBBTSwg
IkxhZGlzbGF2IExob3RrYSIgPGxob3RrYUBuaWMuY3o+IHdyb3RlOg0KPg0KPj4iQWNlZSBMaW5k
ZW0gKGFjZWUpIiA8YWNlZUBjaXNjby5jb20+IHdyaXRlczoNCj4+DQo+Pj4gSSBiZWxpZXZlIHRo
ZSBmYWN0IHRoYXQgd2UgYXJlIGhhdmluZyB0cm91YmxlIHJlc29sdmluZyB0aGlzIGlzIHRoYXQN
Cj4+PnRoZQ0KPj4+IG1vZGVsIGlzIHdyb25nLiBJIHdvdWxkIHByb3Bvc2UgdGhlIGZvbGxvd2lu
ZzoNCj4+DQo+PkkgZG9uJ3QgYWdyZWUgdGhlIG1vZGVsIGlzIHdyb25nLiBJbiBmYWN0LCBJIGJl
bGl2ZSBpbiBKdW5vcyBDTEkgaXQgaXMNCj4+ZG9uZSBleGFjdGx5IHRoZSBzYW1lIHdheSwgZS5n
Lg0KPj4NCj4+ICBzZXQgaW50ZXJmYWNlIGZlLTAvMC8yIHVuaXQgMCBmYW1pbHkgaW5ldCBhZGRy
ZXNzIDYuNi42LjUvMjQNCj4+DQo+PiAgc2V0IHJvdXRpbmctaW5zdGFuY2VzIGJsdWUtdnIgaW50
ZXJmYWNlIGZlLTAvMC8yLjANCj4+DQo+PihJUCBhZGRyZXNzIGlzIGNvbmZpZ3VyZWQgaW4gdGhl
IGludGVyZmFjZSBzdWJ0cmVlLCBhbmQgYW4gaW50ZXJmYWNlIGlzDQo+PmFzc2lnbmVkIHRvIGEg
VlJGIGluIHRoZSByb3V0aW5nLWluc3RhbmNlIHN1YnRyZWUpLg0KPj4NCj4+SSBiZWxpZXZlIHRo
ZSB0cm91YmxlcyB3ZSBhcmUgaGF2aW5nIGFyZSBkdWUgdG8gdGhlIGRpZmZlcmVudCBsb2dpYyBp
bg0KPj50aGUgQ0xJcyBvZiB0aGUgdHdvIG1ham9yIHJvdXRpbmcgcGxhdGZvcm1zLg0KPg0KPkRv
ZXMgaXQgc2hvdyB1cCBhcyBhIHNlcGFyYXRlIGxpc3QgaW4gdGhlIEpVTk9TIGdhdGVkLWxpa2Ug
Y29uZmlndXJhdGlvbg0KPmhpZXJhcmNoeT8gSWYgdGhleSBkbyBjb25maWd1cmUgdGhlIElQdjQv
SVB2NiBhZGRyZXNzZXMgZGlzam9pbnQgZnJvbSB0aGUNCj5yb3V0aW5nIC1pbnN0YW5jZSBpbnN0
YW5jZXMgaW1wbHkgdGhlIGNvcnJlc3BvbmRpbmcgSVB2NC9JUHY2IGFkZHJlc3MNCj5zcGFjZSBh
bmQgdGhlIFJJQnMsIEkgc3RpbGwgZG9uoa90IGxpa2UgdGhlIGluY29uc2lzdGVuY3kuDQo+DQo+
VGhlIHByZXZpb3VzIHByb2R1Y3QgSSB3b3JrZWQgb24sIElQT1MsIGhhZCB0aGUgaW50ZXJmYWNl
cyBpbg0KPnJvdXRpbmctaW5zdGFuY2UgYnV0IHRoZSByb3V0aW5nLWluc3RhbmNlIGludGVyZmFj
ZSBpbmNsdWRlZCBhbGwgdGhlIGxheWVyDQo+MyBkZWZpbml0aW9uIGluY2x1ZGluZyB0aGUgSVAv
SVB2NiBhZGRyZXNzZXMgKGkuZS4sIHRoZSBSRkMgNzI3Nw0KPmRlZmluaXRpb25zKS4gDQo+DQo+
VGhhbmtzLA0KPkFjZWUgDQo+DQo+DQo+DQo+DQo+DQo+DQo+Pg0KPj5MYWRhDQo+Pg0KPj4+DQo+
Pj4gICAgMS4gUmVtb3ZlIHRoZSBpbnRlcmZhY2UgbGlzdCBjb21wbGV0ZWx5IGZyb20gcnRmLWNm
ZyBjb25maWd1cmF0aW9uLg0KPj4+ICAgIDIuIEF1Z21lbnQgdGhlIFJGQyA3MjIzIHRvIGluY2x1
ZGUgYSByZWZlcmVuY2UgdG8gYQ0KPj4+cm91dGluZy1pbnN0YW5jZS4NCj4+PiBBbiBpbnRlcmZh
Y2Ugc2hvdWxkIGJlIHBhcnQgb2Ygb25lIGFuZCBvbmx5IG9uZSByb3V0aW5nLWluc3RhbmNlLg0K
Pj4+ICAgIDMuIFByb3ZpZGUgYSBsaXN0IG9mIGludGVyZmFjZXMgaW4gdGhlIG9wZXJhdGlvbmFs
IHN0YXRlIGluIHRoZQ0KPj4+cnRnLWNmZw0KPj4+IG1vZGVsLiANCj4+Pg0KPj4+IE9uZSByZWFz
b24gSSdtIHByb3Bvc2luZyB0aGlzIGNoYW5nZSBpcyB0aGF0IEkgYmVsaWV2ZSBhDQo+Pj5yb3V0
aW5nLWluc3RhbmNlDQo+Pj4gaW1wbGllcyBhbiBJUHY0L0lQdjYgYWRkcmVzcyBzcGFjZSBhbmQg
dGhlIGludGVyZmFjZXMgbGlzdCBNVVNUIE5PVCBiZQ0KPj4+IGRpc2pvaW50IGZyb20gdGhlIGFz
c2lnbmVkIGFkZHJlc3NlcyAocmVmZXIgdG8gUkZDIDcyNzcpLiBJZiB5b3Ugd2FudA0KPj4+dG8N
Cj4+PiBoYXZlIGEgbGlzdCBvZiBpbnRlcmZhY2VzIGluIHRoZSByb3V0aW5nLWluc3RhbmNlLCB5
b3Ugc2hvdWxkIGRlcHJlY2F0ZQ0KPj4+IFJGQyA3Mjc3IG9yLCBhdCBsZWFzdCwgc2F5IHRoYXQg
aXQgb25seSBhcHBsaWVzIHRvIHRoZSBkZWZhdWx0DQo+Pj5pbnN0YW5jZS4NCj4+Pg0KPj4+IElu
IGFsbCBmYWlybmVzcywgTGFkYSBkaXNhZ3JlZXMgd2l0aCBtZSBvbiB0aGlzIHBvaW50IGFuZCB3
YW50cyB0aGUNCj4+PiBmbGV4aWJpbGl0eSBvZiBhc3NvY2lhdGluZyBhbiBpbnRlcmZhY2Ugd2l0
aCBtdWx0aXBsZQ0KPj4+cm91dGluZy1pbnN0YW5jZXMuDQo+Pj4gQWRkaXRpb25hbGx5LCBoZSBm
ZWVscyB0aGF0IHRoZSBsaXN0IGluc2lkZSB0aGUgcm91dGluZy1pbnN0YW5jZSB3aWxsDQo+Pj4g
ZmFjaWxpdGF0ZSBiZXR0ZXIgaW50ZXJmYWNlIHNlbGVjdGlvbiBjaGVja2luZy4gSSBkb26p9nQg
c2VlIHRoZSBsYXR0ZXINCj4+PmFzDQo+Pj4gYW4gaXNzdWUgYXMgdGhlIHNhbWUgY2hlY2tpbmcg
Y291bGQgYmUgYXBwbGllZCB3aGVuIGFuIGF0dGVtcHQgaXMgbWFkZQ0KPj4+dG8NCj4+PiBhdWdt
ZW50IHRoZSBSRkMgNzIyMyBpbnRlcmZhY2UuDQo+Pj4NCj4+PiBUaGFua3MsDQo+Pj4gQWNlZSAN
Cj4+Pg0KPj4+ICAgIA0KPj4+DQo+Pj4gT24gMS8xNC8xNSwgMTI6NDYgUE0sICJKdWVyZ2VuIFNj
aG9lbndhZWxkZXIiDQo+Pj4gPGouc2Nob2Vud2FlbGRlckBqYWNvYnMtdW5pdmVyc2l0eS5kZT4g
d3JvdGU6DQo+Pj4NCj4+Pj5PbiBXZWQsIEphbiAxNCwgMjAxNSBhdCAwNDo0MzoyOVBNICswMDAw
LCBYdWZlbmcgTGl1IHdyb3RlOg0KPj4+Pj4gSGkgQW5keSwNCj4+Pj4+IA0KPj4+Pj4gVGhlIGNv
bmNhdGVuYXRlZCBzdHJpbmcgZm9ybWF0IGlzIGFjdHVhbGx5IHdoYXQgd2UgcGxhbiB0byBkby4N
Cj4+Pj4+SG93ZXZlciwNCj4+Pj4+dG8gbWUsIGl0IGlzIG1vcmUgbGlrZSBhIGhhY2sgdGhhbiBh
biBlbmdpbmVlcmVkIHNvbHV0aW9uLiBUaGUgbW9kZWwNCj4+Pj4+ZmFpbHMgdG8gY2FwdHVyZSBz
dWNoIGEgcmVsYXRpb25zaGlwIHByb3Blcmx5Lg0KPj4+Pj4NCj4+Pj4NCj4+Pj5JZiB5b3VyIGlu
dGVyZmFjZSBuYW1lcyBhcmUgbm8gdW5pcXVlLCBJIHdvdWxkIGFzc3VtZSB0aGF0IHlvdSB3aWxs
DQo+Pj4+ZmFjZSBvdGhlciBpc3N1ZXMgYXMgd2VsbC4gRm9yIGV4YW1wbGUsIG9uZSBtYXkgdXNl
IGFuIGludGVyZmFjZSBuYW1lDQo+Pj4+dG8gZGlzYW1iaWd1YXRlIGxpbmstbG9jYWwgYWRkcmVz
c2VzLiBJIGFtIG5vdCBzdXJlIGhvdyB0aGF0IHdvcmtzIGlmDQo+Pj4+eW91ciBpbnRlcmZhY2Ug
bmFtZSBpcyBub3QgdW5pcXVlLg0KPj4+Pg0KPj4+Pi9qcw0KPj4+Pg0KPj4+Pi0tIA0KPj4+Pkp1
ZXJnZW4gU2Nob2Vud2FlbGRlciAgICAgICAgICAgSmFjb2JzIFVuaXZlcnNpdHkgQnJlbWVuIGdH
bWJIDQo+Pj4+UGhvbmU6ICs0OSA0MjEgMjAwIDM1ODcgICAgICAgICBDYW1wdXMgUmluZyAxLCAy
ODc1OSBCcmVtZW4sIEdlcm1hbnkNCj4+Pj5GYXg6ICAgKzQ5IDQyMSAyMDAgMzEwMyAgICAgICAg
IDxodHRwOi8vd3d3LmphY29icy11bml2ZXJzaXR5LmRlLz4NCj4+Pg0KPj4NCj4+LS0gDQo+Pkxh
ZGlzbGF2IExob3RrYSwgQ1ouTklDIExhYnMNCj4+UEdQIEtleSBJRDogRTc0RThDMEMNCj4NCj5f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPlJ0Zy15YW5n
LWNvb3JkIG1haWxpbmcgbGlzdA0KPlJ0Zy15YW5nLWNvb3JkQGlldGYub3JnDQo+aHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9ydGcteWFuZy1jb29yZA0KDQo=


From nobody Fri Feb 13 10:31:31 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 8EA581A00E6; Fri, 13 Feb 2015 10:31:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.911
X-Spam-Level: 
X-Spam-Status: No, score=-13.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_14=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 IDUyZe-DGfOf; Fri, 13 Feb 2015 10:31:22 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB4811A0060; Fri, 13 Feb 2015 10:31:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2908; q=dns/txt; s=iport; t=1423852282; x=1425061882; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=Bf1V+J5luEW75fjWeOKHOhy9PK4H8D8Hc+8KXcFrUpY=; b=HCkd3zbUEgTGxx6uw3seyVFW5MARBJLaIU2fNp9ggh6a0+a5ClE77zza swr59H81ppNxXM3jDRcTMan7bTvRVlHr2M949BnzM5Eeb4cHraUHpMRzv 0cLWrQM6vs3EEH3b88Gjb8msI/xJq36KMgE+uZRmdNZEto0tBAPBK6fwb s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AisFALlC3lStJA2I/2dsb2JhbABbgwZSWgSCfr8shXEeeEMBAQEBAQF8hA0CBDRXAQgcKAQwJwQBEgmIJA2hJpxkBpcfAQEIIoEbiXGEHAEBHIMcgUgFjzSJNYEYgweLKIM+IoIHF4FQbwGBCjl/AQEB
X-IronPort-AV: E=Sophos;i="5.09,572,1418083200"; d="scan'208";a="395957513"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-5.cisco.com with ESMTP; 13 Feb 2015 18:31:22 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t1DIVLv5027835 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 13 Feb 2015 18:31:21 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.175]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0195.001; Fri, 13 Feb 2015 12:31:21 -0600
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Thomas Morin <thomas.morin@orange-ftgroup.com>, Ladislav Lhotka <lhotka@nic.cz>, Routing YANG <rtg-yang-coord@ietf.org>, Routing WG <rtgwg@ietf.org>
Subject: Re: rtg-cfg hierachy (PLEASE REPLY TO THIS ONE WITH THE CORRECT MAIL ALIASES)
Thread-Topic: rtg-cfg hierachy (PLEASE REPLY TO THIS ONE WITH THE CORRECT MAIL ALIASES)
Thread-Index: AQHQR7tDYrs6RMzmJ0iGnkpid0CpeQ==
Date: Fri, 13 Feb 2015 18:31:20 +0000
Message-ID: <D103AD28.E652%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.152.200]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <BB49104534C1144DB807A51C0D45FDD9@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/-E14zHSDKRE0VHojjxxMl8xlYnU>
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, 13 Feb 2015 18:31:25 -0000

SGkgTGFkYSwgVGhvbWFzLCANCg0KT24gMi8xMy8xNSwgNToxMCBBTSwgIkxhZGlzbGF2IExob3Rr
YSIgPGxob3RrYUBuaWMuY3o+IHdyb3RlOg0KDQo+SGksDQo+DQo+IkFjZWUgTGluZGVtIChhY2Vl
KSIgPGFjZWVAY2lzY28uY29tPiB3cml0ZXM6DQo+DQo+PkhpIFRob21hcywgDQo+Pg0KPj5JdCBp
cyBteSB1bmRlcnN0YW5kaW5nIHRoYXQgdGhlIFJJQnMgd2VyZSBtb3ZlZCBvdXQgb2YgdGhlDQo+
PnJvdXRpbmctaW5zdGFuY2UgaW4gcmVzcG9uc2UgdG8geW91ciBjb21tZW50IHRoYXQgYSBSSUIg
d291bGQgbmVlZCB0byBiZQ0KPj5hdHRhY2hlZCB0byBtdWx0aXBsZSByb3V0aW5nIGluc3RhbmNl
cy4gSSBkb26p9nQgYWdyZWUgd2l0aCB0aGlzDQo+Pm1vZGVsLiBJDQo+DQo+QWNlZSByZWZlcnMg
dG8gdGhpcyBjb21tZW50IHRoYXQgVGhvbWFzIG1hZGUgaW4gaGlzIHJldmlldyBvZg0KPmRyYWZ0
LWlldGYtbmV0bW9kLXJvdXRpbmctY2ZnLTAyIG9uIDIwMTItMDMtMjM6DQo+DQo+IkFsbG93aW5n
IG11bHRpcGxlICJyb3V0ZXJzIiBpcyBhIGdvb2Qgc3RhcnRpbmcgcG9pbnQgZm9yIHVzaW5nIHRo
ZXNlDQo+c3BlY3MgaW4gdGhlIGNvbnRleHQgb2YgUkZDNDM2NCAoTVBMUy9CR1AgSVAgVlBOcyku
IEhvd2V2ZXIsIGlmIEkNCj51bmRlcnN0YW5kIGNvcnJlY3RseSBZYW5nIHN5bnRheCwgdGhlIHdh
eSB0aGUgZmlsdGVycyBhcmUgZGVmaW5lZCB3b3VsZA0KPm5vdCB3b3JrIGluIHRoZSBjb250ZXh0
IG9mIFJGQzQzNjQsIHdoZXJlIGEgQkdQIHJvdXRpbmcgaW5zdGFuY2UgaW4gdGhlDQo+bWFzdGVy
ICJyb3V0ZXIiIGV4cG9ydHMgc2VsZWN0ZWQgcm91dGVzIGluIGVhY2ggb2YgdGhlIHJvdXRpbmcg
dGFibGUgb2YNCj5lYWNoIFZQTiAoVlJGKS4gIFRoZSBWUkYgYWxzbyBleHBvcnQgcm91dGVzIHRv
IHRoZSBtYXN0ZXIgaW5zdGFuY2UuIg0KPg0KPkFuZCBpbmRlZWQsIGluIHJldi4gLTAzIHRoZSBs
aXN0IG9mIFJJQnMgKHRoZW4gY2FsbGVkICJyb3V0aW5nLXRhYmxlIikNCj53YXMgdGhlIG1vdmVk
IG91dCBvZiB0aGUgcm91dGluZyBpbnN0YW5jZSAodGhlbiBjYWxsZWQgInJvdXRlciIpIGFuZA0K
PmJlY2FtZSBnbG9iYWwuDQoNClRoZW4gZG8geW91IGFncmVlIHRvIG1vdmUgdGhlIFJJQnMgYmFj
ayBpbnRvIHRoZSByb3V0aW5nLWluc3RhbmNlPyBCb3RoDQp0aGUgQkdQIFlBTkcgZHJhZnRzIG1v
ZGVsIEwzVlBOIGRlZmluaXRpb25zIHVuZGVyIHRoZSBjb3JyZXNwb25kaW5nDQphZGRyZXNzIGZh
bWlseSBpbiBCR1AuDQoNCmh0dHA6Ly93d3cuaWV0Zi5vcmcvaWQvZHJhZnQtc2hhaWtoLWlkci1i
Z3AtbW9kZWwtMDAudHh0DQpodHRwOi8vd3d3LmlldGYub3JnL2lkL2RyYWZ0LXpoZGFua2luLWlk
ci1iZ3AtY2ZnLTAwLnR4dA0KDQpUaGFua3MsDQpBY2VlIA0KDQoNCg0KPg0KPkxhZGENCj4NCj4+
YmVsaWV2ZSB0aGF0IGEgcm91dGluZyBpbnN0YW5jZSBpbXBsaWVzIGEgVlJGLCB2aXJ0dWFsIHJv
dXRlciBvcg0KPj5zb21ldGhpbmcNCj4+aW4gYmV0d2VlbiBhbmQgdGhhdCBhIFJJQiBzaG91bGQg
YmUgYXNzb2NpYXRlZCB3aXRoIG9uZSBhbmQgb25seSBvbmUNCj4+cm91dGluZyBpbnN0YW5jZS4g
QWRkaXRpb25hbGx5LCBJIGZlZWwgdGhhdCBSSUJzIGFyZSBiYXNpY2FsbHkgcGFzc2l2ZQ0KPj5l
bnRpdGllcyB3aXRoIHJlc3BlY3QgdG8gaW1wb3J0L2V4cG9ydCBvZiByb3V0ZXMgYmV0d2VlbiBS
SUJzIGluIHRoZQ0KPj5zYW1lDQo+Pm9yIG90aGVyIHJvdXRpbmctaW5zdGFuY2VzLiBSYXRoZXIs
IGFsbCBpbXBvcnQvZXhwb3J0IGlzIHVuZGVyIHRoZQ0KPj5jb250cm9sDQo+Pm9mIGEgcm91dGlu
Zy1wcm90b2NvbC4gRm9yIGV4YW1wbGUsIHRoaXMgd291bGQgYmUgaGFuZGxlZCBieSBhIEJHUA0K
Pj5yb3V0aW5nLXByb3RvY29sIGluc3RhbmNlIGZvciBMM1ZQTnMuDQo+Pg0KPj5JqfZkIGxpa2Ug
dG8gZ2V0IHRoZSBvcGluaW9ucyBvZiBvdGhlcnMgb24gdGhpcyBmdW5kYW1lbnRhbCBhc3BlY3Qg
b2YgdGhlDQo+PnJ0Zy1jZmcgbW9kZWwuIA0KPj4NCj4+VGhhbmtzLA0KPj5BY2VlIA0KPj4NCj4+
DQo+DQo+LS0gDQo+TGFkaXNsYXYgTGhvdGthLCBDWi5OSUMgTGFicw0KPlBHUCBLZXkgSUQ6IEU3
NEU4QzBDDQoNCg0KDQo=


From nobody Fri Feb 13 16:36:38 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 3980A1A0368 for <rtgwg@ietfa.amsl.com>; Fri, 13 Feb 2015 16:36:35 -0800 (PST)
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, 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 5B4MD-l4ZbAM for <rtgwg@ietfa.amsl.com>; Fri, 13 Feb 2015 16:36:32 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0716.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::716]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85D021A01F2 for <rtgwg@ietf.org>; Fri, 13 Feb 2015 16:36:32 -0800 (PST)
Received: from BLUPR05MB292.namprd05.prod.outlook.com (10.141.23.27) by BLUPR05MB292.namprd05.prod.outlook.com (10.141.23.27) with Microsoft SMTP Server (TLS) id 15.1.81.19; Sat, 14 Feb 2015 00:36: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.0081.018; Sat, 14 Feb 2015 00:36:13 +0000
From: Chris Bowers <cbowers@juniper.net>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: New Version Notification for draft-bowers-rtgwg-mrt-applicability-to-8021qca-00.txt
Thread-Topic: New Version Notification for draft-bowers-rtgwg-mrt-applicability-to-8021qca-00.txt
Thread-Index: AQHQR+2V77/WI0ZQdUWJGzIDDN5155zvS4HQ
Date: Sat, 14 Feb 2015 00:36:12 +0000
Message-ID: <BLUPR05MB2920F206BF5226A76668296A9200@BLUPR05MB292.namprd05.prod.outlook.com>
References: <20150214003127.11072.29014.idtracker@ietfa.amsl.com>
In-Reply-To: <20150214003127.11072.29014.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.239.11]
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BLUPR05MB292;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:BLUPR05MB292;
x-forefront-prvs: 0487C0DB7E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(377454003)(377424004)(13464003)(2950100001)(99286002)(74316001)(92566002)(46102003)(106116001)(122556002)(2501002)(19580405001)(19580395003)(110136001)(230783001)(66066001)(450100001)(2900100001)(62966003)(77156002)(54356999)(76576001)(87936001)(2351001)(40100003)(107886001)(2656002)(1720100001)(33656002)(77096005)(86362001)(76176999)(2420400003)(50986999)(102836002)(15975445007); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR05MB292; H:BLUPR05MB292.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Feb 2015 00:36:12.7756 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR05MB292
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/O-GufLhPkBv4aJKU4hXcz-qShu4>
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: Sat, 14 Feb 2015 00:36:35 -0000

SSdkIGxpa2UgdG8gYnJpbmcgdGhlIGZvbGxvd2luZyBkcmFmdCB0byB0aGUgYXR0ZW50aW9uIG9m
IHRoZSBSVEdXRy4gIEl0IGRpc2N1c3NlcyB0aGUgYXBwbGljYWJpbGl0eSBvZiB0aGUgTVJUIGFs
Z29yaXRobSB0byBJRUVFIDgwMi4xUWNhIFBhdGggQ29udHJvbCBhbmQgUmVzZXJ2YXRpb24gZm9y
IGJyaWRnZWQgbmV0d29ya3MuDQoNCkNocmlzDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
DQpGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNA
aWV0Zi5vcmddIA0KU2VudDogRnJpZGF5LCBGZWJydWFyeSAxMywgMjAxNSA2OjMxIFBNDQpUbzog
Q2hyaXMgQm93ZXJzOyBDaHJpcyBCb3dlcnM7IEphbm9zIEZhcmthczsgSmFub3MgRmFya2FzDQpT
dWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWJvd2Vycy1ydGd3Zy1t
cnQtYXBwbGljYWJpbGl0eS10by04MDIxcWNhLTAwLnR4dA0KDQoNCkEgbmV3IHZlcnNpb24gb2Yg
SS1ELCBkcmFmdC1ib3dlcnMtcnRnd2ctbXJ0LWFwcGxpY2FiaWxpdHktdG8tODAyMXFjYS0wMC50
eHQNCmhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgQ2hyaXMgQm93ZXJzIGFuZCBw
b3N0ZWQgdG8gdGhlIElFVEYgcmVwb3NpdG9yeS4NCg0KTmFtZToJCWRyYWZ0LWJvd2Vycy1ydGd3
Zy1tcnQtYXBwbGljYWJpbGl0eS10by04MDIxcWNhDQpSZXZpc2lvbjoJMDANClRpdGxlOgkJQXBw
bGljYWJpbGl0eSBvZiBNYXhpbWFsbHkgUmVkdW5kYW50IFRyZWVzIHRvIElFRUUgODAyLjFRY2Eg
UGF0aCBDb250cm9sIGFuZCBSZXNlcnZhdGlvbg0KRG9jdW1lbnQgZGF0ZToJMjAxNS0wMi0xMw0K
R3JvdXA6CQlJbmRpdmlkdWFsIFN1Ym1pc3Npb24NClBhZ2VzOgkJNw0KVVJMOiAgICAgICAgICAg
IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWJvd2Vycy1ydGd3Zy1t
cnQtYXBwbGljYWJpbGl0eS10by04MDIxcWNhLTAwLnR4dA0KU3RhdHVzOiAgICAgICAgIGh0dHBz
Oi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWJvd2Vycy1ydGd3Zy1tcnQtYXBwbGlj
YWJpbGl0eS10by04MDIxcWNhLw0KSHRtbGl6ZWQ6ICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9y
Zy9odG1sL2RyYWZ0LWJvd2Vycy1ydGd3Zy1tcnQtYXBwbGljYWJpbGl0eS10by04MDIxcWNhLTAw
DQoNCg0KQWJzdHJhY3Q6DQogICBJRUVFIDgwMi4xUWNhIFBhdGggQ29udHJvbCBhbmQgUmVzZXJ2
YXRpb24gKFBDUikgW0lFRUU4MDIxUWNhXSB1c2VzDQogICB0aGUgYWxnb3JpdGhtIHNwZWNpZmll
ZCBpbiBbSS1ELmlldGYtcnRnd2ctbXJ0LWZyci1hbGdvcml0aG1dIHRvDQogICBjb21wdXRlIE1h
eGltYWxseSBSZWR1bmRhbnQgVHJlZXMgKE1SVHMpIHRvIGJlIHVzZWQgZm9yIHRoZQ0KICAgcHJv
dGVjdGlvbiBvZiBkYXRhIHRyYWZmaWMgaW4gYnJpZGdlZCBuZXR3b3Jrcy4gIFRoaXMgZG9jdW1l
bnQNCiAgIGRpc2N1c3NlcyB0aGUgYXBwbGljYWJpbGl0eSBvZiB0aGUgTVJUIGFsZ29yaXRobSB0
byA4MDIuMVFjYS4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KDQoNClBsZWFzZSBub3Rl
IHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1
Ym1pc3Npb24gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJs
ZSBhdCB0b29scy5pZXRmLm9yZy4NCg0KVGhlIElFVEYgU2VjcmV0YXJpYXQNCg0K


From nobody Sat Feb 14 03:49:21 2015
Return-Path: <lhotka@nic.cz>
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 E97D71A1BE7; Sat, 14 Feb 2015 03:49:16 -0800 (PST)
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 Hi6HcTv2iQuC; Sat, 14 Feb 2015 03:49:13 -0800 (PST)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id CD4351A1BE0; Sat, 14 Feb 2015 03:49:12 -0800 (PST)
Received: from localhost (unknown [172.29.2.202]) by trail.lhotka.name (Postfix) with ESMTPSA id 8EA901CC0475; Sat, 14 Feb 2015 12:49:12 +0100 (CET)
From: Ladislav Lhotka <lhotka@nic.cz>
To: "Acee Lindem \(acee\)" <acee@cisco.com>, "Acee Lindem \(acee\)" <acee@cisco.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Xufeng Liu <xufeng.liu@ericsson.com>
Subject: Re: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances
In-Reply-To: <D103A6D1.E624%acee@cisco.com>
References: <AAB1CC9C17CBA440BDFA169056B93B9EB10521@eusaamb107.ericsson.se> <35023717-7EE8-4F45-B2F4-B24E0F86FA5A@nic.cz> <20150113212732.GD1545@elstar.local> <23976026-499F-4C9C-844A-DB53BE244992@nic.cz> <AAB1CC9C17CBA440BDFA169056B93B9EB1128D@eusaamb107.ericsson.se> <20150114155450.GA3625@elstar.local> <AAB1CC9C17CBA440BDFA169056B93B9EB1139B@eusaamb107.ericsson.se> <CABCOCHSiWG=x0vTYKKxqhMqd69yK+Nuo0k_Y_=Y_KHkQBDi3FA@mail.gmail.com> <D0DBD855.889EB%jeff.tantsura@ericsson.com> <AAB1CC9C17CBA440BDFA169056B93B9EB11472@eusaamb107.ericsson.se> <20150114174655.GA3932@elstar.local> <D1029726.E4B5%acee@cisco.com> <m2k2zm9kg9.fsf@birdie.labs.nic.cz> <D103A0D5.E60D%acee@cisco.com> <D103A6D1.E624%acee@cisco.com>
User-Agent: Notmuch/0.19 (http://notmuchmail.org) Emacs/24.4.51.2 (x86_64-apple-darwin14.0.0)
Date: Sat, 14 Feb 2015 12:49:11 +0100
Message-ID: <m23868n26g.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/ZPJq7-TFdE4bgqANcFLVZGf_XEc>
Cc: "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>, Andy Bierman <andy@yumaworks.com>, Routing WG <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: Sat, 14 Feb 2015 11:49:17 -0000

"Acee Lindem (acee)" <acee@cisco.com> writes:

> Independent of the hierarchy, I think an interface should be associated
> with one and only routing-instance. I know of no implementation that

We've been there, too. In revision -02, we had this definition ("router"
later became "routing-instance"):

list router {
    key "name";
    unique "interfaces/interface/name";
    ...
}

The role of the "unique" statement was to restrict the assignment of
interfaces exactly as you write.

But then we had a discussion in the NETMOD mailing list about whether
such a unique statement is legal or not:

http://www.ietf.org/mail-archive/web/netmod/current/msg06386.html

While I still think there is nothing wrong with that unique statement,
it was eventually removed for the "ietf-routing" module.

> allows this (including the use case of separate instances for IPv4 and
> IPv6).

This is not necessarily true. In my data model for the BIRD routing
daemon

(https://gitlab.labs.nic.cz/labs/yang-tools/tree/master/data-models/bird)

I am using special types of routing-instances "bird-ipv4" and
"bird-ipv6", and the same interface can be in both instances. This is
because BIRD has to be compiled separately with support for IPv4 and
IPv6, and each routing-instance then corresponds to one BIRD process.

Yes, such an implementation is somewhat peculiar and needn't serve as a
model. On the other hand, I don't see any reason why overlapping
interface assignments should be made illegal for *all* types of routing
instances.

I assume the data model for routing instances of the type "VRF" will
state that assignments of interfaces to routing instances have to be
disjoint, and the draft explicitly states such an additional constraint
is allowed (last paragraph in sec. 5.1). Isn't this sufficient?

Lada

>
> Thanks,
> Acee=20
>
> On 2/13/15, 12:45 PM, "Acee Lindem (acee)" <acee@cisco.com> wrote:
>
>>
>>
>>On 2/13/15, 5:25 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:
>>
>>>"Acee Lindem (acee)" <acee@cisco.com> writes:
>>>
>>>> I believe the fact that we are having trouble resolving this is that
>>>>the
>>>> model is wrong. I would propose the following:
>>>
>>>I don't agree the model is wrong. In fact, I belive in Junos CLI it is
>>>done exactly the same way, e.g.
>>>
>>>  set interface fe-0/0/2 unit 0 family inet address 6.6.6.5/24
>>>
>>>  set routing-instances blue-vr interface fe-0/0/2.0
>>>
>>>(IP address is configured in the interface subtree, and an interface is
>>>assigned to a VRF in the routing-instance subtree).
>>>
>>>I believe the troubles we are having are due to the different logic in
>>>the CLIs of the two major routing platforms.
>>
>>Does it show up as a separate list in the JUNOS gated-like configuration
>>hierarchy? If they do configure the IPv4/IPv6 addresses disjoint from the
>>routing -instance instances imply the corresponding IPv4/IPv6 address
>>space and the RIBs, I still don=E2=80=99t like the inconsistency.
>>
>>The previous product I worked on, IPOS, had the interfaces in
>>routing-instance but the routing-instance interface included all the layer
>>3 definition including the IP/IPv6 addresses (i.e., the RFC 7277
>>definitions).=20
>>
>>Thanks,
>>Acee=20
>>
>>
>>
>>
>>
>>
>>>
>>>Lada
>>>
>>>>
>>>>    1. Remove the interface list completely from rtf-cfg configuration.
>>>>    2. Augment the RFC 7223 to include a reference to a
>>>>routing-instance.
>>>> An interface should be part of one and only one routing-instance.
>>>>    3. Provide a list of interfaces in the operational state in the
>>>>rtg-cfg
>>>> model.=20
>>>>
>>>> One reason I'm proposing this change is that I believe a
>>>>routing-instance
>>>> implies an IPv4/IPv6 address space and the interfaces list MUST NOT be
>>>> disjoint from the assigned addresses (refer to RFC 7277). If you want
>>>>to
>>>> have a list of interfaces in the routing-instance, you should deprecate
>>>> RFC 7277 or, at least, say that it only applies to the default
>>>>instance.
>>>>
>>>> In all fairness, Lada disagrees with me on this point and wants the
>>>> flexibility of associating an interface with multiple
>>>>routing-instances.
>>>> Additionally, he feels that the list inside the routing-instance will
>>>> facilitate better interface selection checking. I don=C2=B9t see the l=
atter
>>>>as
>>>> an issue as the same checking could be applied when an attempt is made
>>>>to
>>>> augment the RFC 7223 interface.
>>>>
>>>> Thanks,
>>>> Acee=20
>>>>
>>>>=20=20=20=20
>>>>
>>>> On 1/14/15, 12:46 PM, "Juergen Schoenwaelder"
>>>> <j.schoenwaelder@jacobs-university.de> wrote:
>>>>
>>>>>On Wed, Jan 14, 2015 at 04:43:29PM +0000, Xufeng Liu wrote:
>>>>>> Hi Andy,
>>>>>>=20
>>>>>> The concatenated string format is actually what we plan to do.
>>>>>>However,
>>>>>>to me, it is more like a hack than an engineered solution. The model
>>>>>>fails to capture such a relationship properly.
>>>>>>
>>>>>
>>>>>If your interface names are no unique, I would assume that you will
>>>>>face other issues as well. For example, one may use an interface name
>>>>>to disambiguate link-local addresses. I am not sure how that works if
>>>>>your interface name is not unique.
>>>>>
>>>>>/js
>>>>>
>>>>>--=20
>>>>>Juergen Schoenwaelder           Jacobs University Bremen gGmbH
>>>>>Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
>>>>>Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
>>>>
>>>
>>>--=20
>>>Ladislav Lhotka, CZ.NIC Labs
>>>PGP Key ID: E74E8C0C
>>
>>_______________________________________________
>>Rtg-yang-coord mailing list
>>Rtg-yang-coord@ietf.org
>>https://www.ietf.org/mailman/listinfo/rtg-yang-coord
>

--=20
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C


From nobody Sun Feb 15 22:28:17 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 E7CA31A8744 for <rtgwg@ietfa.amsl.com>; Sun, 15 Feb 2015 22:28:15 -0800 (PST)
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 I2QMRhmpCzRF for <rtgwg@ietfa.amsl.com>; Sun, 15 Feb 2015 22:28:14 -0800 (PST)
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 5691D1A1A30 for <rtgwg@ietf.org>; Sun, 15 Feb 2015 22:28:14 -0800 (PST)
X-AuditID: c618062d-f79376d000000ceb-d7-54e13a1f1369
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id E2.F3.03307.F1A31E45; Mon, 16 Feb 2015 01:30:24 +0100 (CET)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0210.002; Mon, 16 Feb 2015 01:28:11 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RTGWG timeslots for Dallas
Thread-Topic: RTGWG timeslots for Dallas
Thread-Index: AQHQSbG864VyIZCMpUa+feSj4QA/mg==
Date: Mon, 16 Feb 2015 06:28:11 +0000
Message-ID: <D106CE03.8E10D%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.11]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <43EB47D8BF46C540B1CADEBB77D274B1@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGLMWRmVeSWpSXmKPExsUyuXRPuK6C1cMQg7+djBYX3vxmdmD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxpeDy9kLVjNWNJ8QbGBsYexi5OSQEDCRuLb2BpQtJnHh3nq2 LkYuDiGBI4wS644shnKWM0rc+LOHFaSKTcBA4v+34ywgtoiAqkTvrFY2EFtYQFni0YxWqLiG xK3NfxghbD2J5k2zwWwWoPqpC/Ywg9i8AuYSO/pmMoHYjECbv59aA2YzC4hL3HoynwniIgGJ JXvOM0PYohIvH/8Du0EUaOazDZvZIeJKEh9/z2eH6NWRWLD7ExuEbS1x+e4FVghbW2LZwtdQ ewUlTs58wjKBUXQWknWzkLTPQtI+C0n7LCTtCxhZVzFylBanluWmGxlsYgRGxDEJNt0djHte Wh5iFOBgVOLh3fDmQYgQa2JZcWXuIUZpDhYlcd5FDw6GCAmkJ5akZqemFqQWxReV5qQWH2Jk 4uCUamCcrPI3P/GDVfh2h5W8X3wXFn5K/FLIGThBXv0Fu/XGkr13uX9v5lKy3ZY107MnesGH 36U8R4SvsX/6/8P03LV3gn/6Epj6XiReY1TqY5//QXX2xSlzVbRjVi9oXtOyyo6ZOYp/ocyh jmu/L8wtk/y/6YTMe+OalPYVt56GmIT+Ec7RyYzYKfZSiaU4I9FQi7moOBEAHbVyTGkCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/mWh1GC-OmAsO3Wzbp8dz7Ev7oM0>
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, 16 Feb 2015 06:28:16 -0000

Hi RTGWG,

IETF92 is approaching, please request a timeslot if you are planning to
present, usual disclaimer applies - no draft/no time.

Thanks!

Cheers,
Jeff


From nobody Tue Feb 17 04:40:43 2015
Return-Path: <ietfa@btconnect.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 2F9511A8822 for <rtgwg@ietfa.amsl.com>; Tue, 17 Feb 2015 04:40:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_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 mApt5WY-AAhh for <rtgwg@ietfa.amsl.com>; Tue, 17 Feb 2015 04:40:39 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0759.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::759]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D73181A8791 for <rtgwg@ietf.org>; Tue, 17 Feb 2015 04:40:37 -0800 (PST)
Received: from pc6 (81.151.167.59) by DB4PR07MB380.eurprd07.prod.outlook.com (10.141.235.23) with Microsoft SMTP Server (TLS) id 15.1.87.18; Tue, 17 Feb 2015 12:34:10 +0000
Message-ID: <006d01d04aad$c7630f60$4001a8c0@gateway.2wire.net>
From: t.petch <ietfa@btconnect.com>
To: Alia Atlas <akatlas@gmail.com>, Adrian Farrel <adrian@olddog.co.uk>
Subject: Fw: Interim meetings - changing the way we work
Date: Tue, 17 Feb 2015 12:32:12 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.151.167.59]
X-ClientProxiedBy: DB3PR05CA0048.eurprd05.prod.outlook.com (25.160.41.176) To DB4PR07MB380.eurprd07.prod.outlook.com (10.141.235.23)
Authentication-Results: gmail.com; dkim=none (message not signed) header.d=none;
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR07MB380;
X-Microsoft-Antispam-PRVS: <DB4PR07MB3806E8EE923D75E924C6ED3892F0@DB4PR07MB380.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005003); SRVR:DB4PR07MB380; 
X-Forefront-PRVS: 0490BBA1F0
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(377454003)(377424004)(51704005)(13464003)(23676002)(50466002)(62966003)(77156002)(33646002)(87976001)(14496001)(46102003)(122386002)(47776003)(62236002)(19580405001)(44716002)(19580395003)(66066001)(61296003)(86362001)(40100003)(42186005)(50226001)(44736004)(92566002)(116806002)(50986999)(81686999)(19273905006)(84392001)(19300405004)(77096005)(15975445007)(74416001)(7726001)(562404015)(563064011); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR07MB380; H:pc6; FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:DB4PR07MB380;
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 17 Feb 2015 12:34:10.8019 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR07MB380
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/H0r_NEJ416jzHrboIwTPyhUbdyM>
Cc: routing WG <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, 17 Feb 2015 12:40:42 -0000

Adrian, Alia

Looking for the outcome of an Interim meeting on the IETF website, I
became aware of how rarely the proceedings are fully reported (as I
posted to the main IETF list recently).

Of the meetings in 2014 that produced no Minutes, three are in the
Routing
Area,
2014-12-18 teas
2014-12-15 bier
2014-10-21 nvo3

These are not lists I normally follow but I did look at the Mailing List
Archives and, for all three, there is mention of 'Rough' or 'Draft'
minutes, in one case even adding

'I will post them to the meeting materials, by end of this week'

Thoughts?

Tom Petch

----- Original Message -----
From: "t.p." <daedulus@btconnect.com>
To: "ietf" <ietf@ietf.org>
Sent: Sunday, February 15, 2015 1:57 PM
Subject: Interim meetings - changing the way we work


> There has been a marked increase in the number of  interim meetings.
> Using
> http://www.ietf.org/meeting/interim/proceedings.html
> as a guide, there were
> 18 in 2011
> 35 in 2012
> 45 in 2013
> 84 in 2014
> 13 in January 2015 alone.
>
> With them comes a change in the way of working, perhaps rendering some
> of our practices historic.
>
> Of the 84 meetings listed for 2014, 21 left no other trace on the IETF
> web site, no Agenda, no Minutes, no Proceedings.  Perhaps the WG
> provided no materials, perhaps they did not happen; sometimes a
> cancellation notice is apparent in the WG List Archives, other times
> not.
>
> Of the 63 that have left a trace, 6 produced no Minutes but did
produce
> slides or recordings and so presumably happened.
>
> Of the 57 that produced Minutes, 18 produced no Agenda while in 13
> cases, the Minutes contained no list of Attendees (goodbye Blue
> Sheets?).
>
> Only 26 meetings left a complete record, of Agenda, Minutes and
> Attendees.
>
> The meetings encompassed 30 Working Groups, of which 16 met once, 14
> more than once, with one WG meeting 8 times.
>
> What is more subjective is that, with Virtual Interims, increasingly
the
> only kind, there is a tendency for the WG Mailing List to no longer
> provide a record of discussions, choices, consensus.  For example,
they
> may make greater use of github so that the minutes record a discussion
> of options 1, 2 and 3 for Issue 29 with no indication of what the
issue
> or options are; a while later, they may record an update to option 3
so
> it would now seem impossible to know what was discussed at the earlier
> meeting.
>
> Even with the better minutes, they never give the same sense as posts
to
> a mailing list of who was or was not in favour and how strong their
view
> was.
>
> Of course, we still have WG Last Calls on the list but if at a future
> date, an AD or GenArt reviewer wants to look back and see what options
> were discussed and  how rough the consensus was, well, it may be
> impossible.
>
> A post in another thread recently said
>
> > I do think that the increased significance of meetings
> > in IETF participation (and here, I'm not talking about
> > things like nomcom but about significance to our technical
> > work) is a problem, both because it tends to marginalize
> > people who can't come to meetings and because it slows
> > work down.
>
> Well, I disagree about slowing the work down but certainly agree with
> the marginalisation, that WGs holding multiple Interims may tend to
> develop an in-crowd of those that can participate with the world at
> large only seeing the end result without knowing how it was arrived at
> by whom.
>
> Tom Petch
>


From nobody Tue Feb 17 05:49:42 2015
Return-Path: <lberger@labn.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 251C41A1AFB for <rtgwg@ietfa.amsl.com>; Tue, 17 Feb 2015 05:49:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.677
X-Spam-Level: 
X-Spam-Status: No, score=-0.677 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_BIZ=0.288, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_15=0.6, WEIRD_PORT=0.001] 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 jimsad9ThPeD for <rtgwg@ietfa.amsl.com>; Tue, 17 Feb 2015 05:49:38 -0800 (PST)
Received: from newdragon.webhostserver.biz (newdragon.webhostserver.biz [69.25.136.252]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 770B81A8884 for <rtgwg@ietf.org>; Tue, 17 Feb 2015 05:49:26 -0800 (PST)
Received: from localhost ([::1]:50053) by newdragon.webhostserver.biz with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <lberger@labn.net>) id 1YNiWj-0000qQ-Ad; Tue, 17 Feb 2015 16:49:25 +0300
Message-ID: <54E346E2.5050407@labn.net>
Date: Tue, 17 Feb 2015 08:49:22 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "t.petch" <ietfa@btconnect.com>, Alia Atlas <akatlas@gmail.com>,  Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: Fw: Interim meetings - changing the way we work
References: <006d01d04aad$c7630f60$4001a8c0@gateway.2wire.net>
In-Reply-To: <006d01d04aad$c7630f60$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - newdragon.webhostserver.biz
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-Get-Message-Sender-Via: newdragon.webhostserver.biz: authenticated_id: lberger@blabn.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/HCd8d8VYDybFu7SY8_0albmWLvg>
Cc: routing WG <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, 17 Feb 2015 13:49:41 -0000

Hi Tom,
    Thanks for pointing out that the teas minutes didn't make it to the
proceedings page!=20

New WG, 1st Interim-- minutes didn't get posted to the proceedings
page.  Good thing they were circulated on the list and and remain
available in the archive:

Slides:
http://www.ietf.org/proceedings/interim/2014/12/18/teas/proceedings.html
Initial minutes (posted day of meeting thanks to the good work of our
secretary): http://www.ietf.org/mail-archive/web/teas/current/msg00072.ht=
ml
Recording (posed next day):
http://www.ietf.org/mail-archive/web/teas/current/msg00074.html
Working minutes (url on list):
http://etherpad.tools.ietf.org:9000/p/notes-ietf-92-teas?

Not quite "no minutes".

Certainly the minutes didn't make it to the proceedings page and you
are, of course, correct that they should be.  And they are there now:
http://www.ietf.org/proceedings/interim/2014/12/18/teas/minutes/minutes-i=
nterim-2014-teas-1

Perhaps there's a suggestion to made to the tools team to get the
tracker to send a reminder to post minutes automatically some number of
days after an interim is held. It would also be nice if interims showed
on the WG tools pages too...

Lou (TEAS co-chair)

BTW why are we discussing this on the RTG WG list? Perhaps you meant
routing-discussion@ietf.org <mailto:routing-discussion@ietf.org>?=20

On 2/17/2015 7:32 AM, t.petch wrote:
> Adrian, Alia
>
> Looking for the outcome of an Interim meeting on the IETF website, I
> became aware of how rarely the proceedings are fully reported (as I
> posted to the main IETF list recently).
>
> Of the meetings in 2014 that produced no Minutes, three are in the
> Routing
> Area,
> 2014-12-18 teas
> 2014-12-15 bier
> 2014-10-21 nvo3
>
> These are not lists I normally follow but I did look at the Mailing Lis=
t
> Archives and, for all three, there is mention of 'Rough' or 'Draft'
> minutes, in one case even adding
>
> 'I will post them to the meeting materials, by end of this week'
>
> Thoughts?
>
> Tom Petch
>
> ----- Original Message -----
> From: "t.p." <daedulus@btconnect.com>
> To: "ietf" <ietf@ietf.org>
> Sent: Sunday, February 15, 2015 1:57 PM
> Subject: Interim meetings - changing the way we work
>
>
>> There has been a marked increase in the number of  interim meetings.
>> Using
>> http://www.ietf.org/meeting/interim/proceedings.html
>> as a guide, there were
>> 18 in 2011
>> 35 in 2012
>> 45 in 2013
>> 84 in 2014
>> 13 in January 2015 alone.
>>
>> With them comes a change in the way of working, perhaps rendering some=

>> of our practices historic.
>>
>> Of the 84 meetings listed for 2014, 21 left no other trace on the IETF=

>> web site, no Agenda, no Minutes, no Proceedings.  Perhaps the WG
>> provided no materials, perhaps they did not happen; sometimes a
>> cancellation notice is apparent in the WG List Archives, other times
>> not.
>>
>> Of the 63 that have left a trace, 6 produced no Minutes but did
> produce
>> slides or recordings and so presumably happened.
>>
>> Of the 57 that produced Minutes, 18 produced no Agenda while in 13
>> cases, the Minutes contained no list of Attendees (goodbye Blue
>> Sheets?).
>>
>> Only 26 meetings left a complete record, of Agenda, Minutes and
>> Attendees.
>>
>> The meetings encompassed 30 Working Groups, of which 16 met once, 14
>> more than once, with one WG meeting 8 times.
>>
>> What is more subjective is that, with Virtual Interims, increasingly
> the
>> only kind, there is a tendency for the WG Mailing List to no longer
>> provide a record of discussions, choices, consensus.  For example,
> they
>> may make greater use of github so that the minutes record a discussion=

>> of options 1, 2 and 3 for Issue 29 with no indication of what the
> issue
>> or options are; a while later, they may record an update to option 3
> so
>> it would now seem impossible to know what was discussed at the earlier=

>> meeting.
>>
>> Even with the better minutes, they never give the same sense as posts
> to
>> a mailing list of who was or was not in favour and how strong their
> view
>> was.
>>
>> Of course, we still have WG Last Calls on the list but if at a future
>> date, an AD or GenArt reviewer wants to look back and see what options=

>> were discussed and  how rough the consensus was, well, it may be
>> impossible.
>>
>> A post in another thread recently said
>>
>>> I do think that the increased significance of meetings
>>> in IETF participation (and here, I'm not talking about
>>> things like nomcom but about significance to our technical
>>> work) is a problem, both because it tends to marginalize
>>> people who can't come to meetings and because it slows
>>> work down.
>> Well, I disagree about slowing the work down but certainly agree with
>> the marginalisation, that WGs holding multiple Interims may tend to
>> develop an in-crowd of those that can participate with the world at
>> large only seeing the end result without knowing how it was arrived at=

>> by whom.
>>
>> Tom Petch
>>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>



From nobody Wed Feb 18 04:43:21 2015
Return-Path: <tmmorin.orange@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 543A91A87A5; Wed, 18 Feb 2015 03:36:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_14=0.6, 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 D2uzpfUaK45S; Wed, 18 Feb 2015 03:36:13 -0800 (PST)
Received: from mail-we0-f175.google.com (mail-we0-f175.google.com [74.125.82.175]) (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 989071A802A; Wed, 18 Feb 2015 03:36:12 -0800 (PST)
Received: by wesw55 with SMTP id w55so578791wes.5; Wed, 18 Feb 2015 03:36:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=sender:message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=IEBLgCMYZSOR/Dz8niXyx1WoKdpf4BiOaSkQ5CPn+R4=; b=G0lJpoTJ0r1LKHZoTkDbwLnToMOJ5hqsNEmNJ50S+zN9L99Y0AQTTXrcZjblCssF/B iJ1tCNjcLFShvJVEPLY7DTJwv/GMWJiksJZih/RHeFpRfrO3HJIFr489eFhKpbx+bgyw S1LLrejz1DqoYusXWvO0l52xlXA/jj1/SYwNMb33zzXB/+loW+0w5OTRJZgqGbKg5C1N dDZ4VMIvy6EYlVwrApHY7a2quV2GvEhwcvm4Kfk22ZBdMcQkAFMoJxibYlP2hYmbUacV WL2gAABUA8A/AWyv027IyxN5oIp8HqjlRyfhOcqoDBHtdtY0gNMLiWCd9NNiiBB5jxt0 7m/Q==
X-Received: by 10.194.5.37 with SMTP id p5mr72422060wjp.20.1424259371395; Wed, 18 Feb 2015 03:36:11 -0800 (PST)
Received: from [127.0.0.1] (ARennes-652-1-96-43.w2-11.abo.wanadoo.fr. [2.11.199.43]) by mx.google.com with ESMTPSA id hs7sm25011528wib.4.2015.02.18.03.36.09 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Feb 2015 03:36:10 -0800 (PST)
Sender: Thomas Morin <tmmorin.orange@gmail.com>
Message-ID: <54E47928.8050108@orange.com>
Date: Wed, 18 Feb 2015 12:36:08 +0100
From: Thomas Morin <thomas.morin@orange.com>
Organization: Orange
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Acee Lindem (acee)" <acee@cisco.com>, Ladislav Lhotka <lhotka@nic.cz>, Routing YANG <rtg-yang-coord@ietf.org>, Routing WG <rtgwg@ietf.org>
Subject: Re: rtg-cfg hierachy (PLEASE REPLY TO THIS ONE WITH THE CORRECT MAIL ALIASES)
References: <14011_1423852286_54DE42FE_14011_2207_1_D103AD28.E652%acee@cisco.com>
In-Reply-To: <14011_1423852286_54DE42FE_14011_2207_1_D103AD28.E652%acee@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/FbtOdNmWH0nCNG9CCHHTK_Ddcug>
X-Mailman-Approved-At: Wed, 18 Feb 2015 04:43:19 -0800
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, 18 Feb 2015 11:36:15 -0000

Hi Acee, Lada,

It seems that my comment that you quote was more related to filters than 
to routing tables, and indeed, *filters* were moved from "router" to 
"global" in revision -03 that followed my review.

Additionally, Lada, you say that based on my comments "in rev. -03 the 
list of RIBs (then called "routing-table") was the moved out of the 
routing instance (then called "router") and became global.". But if I 
look at -03, "routing-table" is still a child of "router".  The change 
to make "routing-table" global was made in -05.

I guess you need to find out what was the motivation for the change in 
-05, a few months after my initial comments were address.

Best,

-Thomas





2015-02-13, Acee Lindem (acee):
>
> Hi Lada, Thomas,
>
> On 2/13/15, 5:10 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:
>
>> Hi,
>>
>> "Acee Lindem (acee)" <acee@cisco.com> writes:
>>
>>> Hi Thomas,
>>>
>>> It is my understanding that the RIBs were moved out of the
>>> routing-instance in response to your comment that a RIB would need to be
>>> attached to multiple routing instances. I donÂ¹t agree with this
>>> model. I
>>
>> Acee refers to this comment that Thomas made in his review of
>> draft-ietf-netmod-routing-cfg-02 on 2012-03-23:
>>
>> "Allowing multiple "routers" is a good starting point for using these
>> specs in the context of RFC4364 (MPLS/BGP IP VPNs). However, if I
>> understand correctly Yang syntax, the way the filters are defined would
>> not work in the context of RFC4364, where a BGP routing instance in the
>> master "router" exports selected routes in each of the routing table of
>> each VPN (VRF).  The VRF also export routes to the master instance."
>>
>> And indeed, in rev. -03 the list of RIBs (then called "routing-table")
>> was the moved out of the routing instance (then called "router") and
>> became global.
>
> Then do you agree to move the RIBs back into the routing-instance? Both
> the BGP YANG drafts model L3VPN definitions under the corresponding
> address family in BGP.
>
> http://www.ietf.org/id/draft-shaikh-idr-bgp-model-00.txt
> http://www.ietf.org/id/draft-zhdankin-idr-bgp-cfg-00.txt
>
> Thanks,
> Acee
>
>
>
>>
>> Lada
>>
>>> believe that a routing instance implies a VRF, virtual router or
>>> something
>>> in between and that a RIB should be associated with one and only one
>>> routing instance. Additionally, I feel that RIBs are basically passive
>>> entities with respect to import/export of routes between RIBs in the
>>> same
>>> or other routing-instances. Rather, all import/export is under the
>>> control
>>> of a routing-protocol. For example, this would be handled by a BGP
>>> routing-protocol instance for L3VPNs.
>>>
>>> IÂ¹d like to get the opinions of others on this fundamental aspect of the
>>> rtg-cfg model.
>>>
>>> Thanks,
>>> Acee
>>>
>>>
>>
>> --
>> Ladislav Lhotka, CZ.NIC Labs
>> PGP Key ID: E74E8C0C
>
>
>


From nobody Wed Feb 18 12:55:27 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 24DED1A1ADB; Wed, 18 Feb 2015 12:55:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.911
X-Spam-Level: 
X-Spam-Status: No, score=-13.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_14=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 9dcaYhJtxCct; Wed, 18 Feb 2015 12:55:24 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CACD21A1ADA; Wed, 18 Feb 2015 12:55:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6150; q=dns/txt; s=iport; t=1424292924; x=1425502524; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=W2giS0p8z4bUths7Ro6TcJVFXGRecRORJwlSw69cWIo=; b=W984Fjz0qfgB0ZEGtF88O0H8r+ah5Q9QbTeLQ4vVH8Re44qPJ9Bw1XP0 WmsTtjwUzaGjLUt6Hoc2MXxHI8DtaonGKbxpQFRMj9TkspoopCZTX58B+ qWft1FAmqdXsQ+OjTWBpNoU0bx3ekdL3qjBeo/FVwQY4guvTMnGl7tW5O s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BkBQD7++RU/4wNJK1bgwZSWgSDBL9YhXECHIEDQwEBAQEBAXyEDQEBBDRVAgEIGAQoAgIwJQIEARIJiCYNnUKcZAaYQAEBAQEBBQIBH4EbiXSEHQEBHDqCYoFIBY9DiTyBGYMPhj6EboM+IoIHFxSBPG8BgQo5fwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,604,1418083200"; d="scan'208";a="397257274"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-6.cisco.com with ESMTP; 18 Feb 2015 20:55:23 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t1IKtMwU023622 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 18 Feb 2015 20:55:22 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.175]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0195.001; Wed, 18 Feb 2015 14:55:22 -0600
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Thomas Morin <thomas.morin@orange.com>, Ladislav Lhotka <lhotka@nic.cz>, Routing YANG <rtg-yang-coord@ietf.org>, Routing WG <rtgwg@ietf.org>
Subject: Re: rtg-cfg hierachy        (PLEASE REPLY TO THIS ONE WITH THE CORRECT MAIL ALIASES)
Thread-Topic: rtg-cfg hierachy        (PLEASE REPLY TO THIS ONE WITH THE CORRECT MAIL ALIASES)
Thread-Index: AQHQS28ZM/kyJuKUo0W6/2wfbzbSMZz29E2A
Date: Wed, 18 Feb 2015 20:55:21 +0000
Message-ID: <D10A606C.EAED%acee@cisco.com>
References: <14011_1423852286_54DE42FE_14011_2207_1_D103AD28.E652%acee@cisco.com> <54E47928.8050108@orange.com>
In-Reply-To: <54E47928.8050108@orange.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.152.197]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <5C2546D04EF6BD4984E909402BFED729@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/upbqlE9tMVRpS1Kv1ib9__gnaVI>
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, 18 Feb 2015 20:55:26 -0000

VGhhbmtzIFRob21hcyBmb3IgdGhlIGNsYXJpZmljYXRpb24uDQoNCkmhr2QgbGlrZSB0byB0aGVu
IHN1Z2dlc3Qgd2UgY2hhbmdlIHRoZSBydGctY2ZnIG1vZGVsIGhpZXJhcmNoeSB0byByZWZsZWN0
DQp3aGF0IG1vc3Qgcm91dGluZyBkZXZpY2UgaW1wbGVtZW50YXRpb25zLg0KVGhlcmUgaXMgYSBS
SUIgKHlvdSBjYW4gY2FsbCBpdCBhIGRlZmF1bHQtUklCIGlmIHlvdSBsaWtlKSBmb3IgZXZlcnkN
CkFkZHJlc3MgRmFtaWx5IChBRikuIE11bHRpcGxlIFJJQnMgcGVyIEFGIGlzIG5vdCB3aWRlbHkg
aW1wbGVtZW50ZWQgYW5kIEkNCmRvbqGvdCBzZWUgaXQgYmVjb21pbmcgbW9yZSBwcmV2YWxlbnQu
IEhlbmNlLCBJIGFncmVlIGl0IHNob3VsZCBiZSBhDQpmZWF0dXJlLiBUaGUgb25lIGltcGxlbWVu
dGF0aW9uIEmhr20gZmFtaWxpYXIgd2l0aCBpcyBtdWx0aXBsZSB0b3BvbG9neQ0Kcm91dGluZyAo
ZS5nLiwgUkZDIDQ5MTUpLCB3aGVyZSBSSUIgY29ycmVzcG9uZHMgdG8gYSBGSUIgdGhhdCBpcyBz
ZWxlY3RlZA0KYmFzZWQgb24gcGFja2V0IG1hcmtpbmcuIERvZXMgYW55b25lIGhhdmUgYW55IG90
aGVyIGV4YW1wbGVzPw0KDQpUaGlzIHdvdWxkIGltcGx5IHRoYXQgUklCcyBhcmUgd2l0aGluIGEg
cm91dGluZy1pbnN0YW5jZSBhbmQgdGhhdA0Kcm91dGluZy1wcm90b2NvbHMgd2l0aGluIHRoZSBy
b3V0aW5nLWluc3RhbmNlIGNhbiBvcGVyYXRlIG9uIHRoZXNlIFJJQnMuDQpUaGVyZSBpcyBubyBy
ZXF1aXJlbWVudCBjb25uZWN0IFJJQnMgdG8gcm91dGluZy1wcm90b2NvbHMgb3IgdG8gZm9ybQ0K
Y29ubmVjdGlvbnMgYmV0d2VlbiBSSUJzLg0KDQpUaGlzIHdvdWxkIGdpdmUgdXMgYSBoaWdoLWxl
dmVsIGhpZXJhcmNoeSBvZjoNCg0Kcncgcm91dGluZy1pbnN0YW5jZSogW25hbWVdDQogICAgICB8
ICArLS1ydyBhZGRyZXNzLWZhbWlseQ0KICAgICAgfCAgfCAgKy0tcncgZGVmYXVsdC1yaWIqIFth
ZGRyZXNzLWZhbWlseV0NCiAgICAgIHwgIHwgICAgICstLXJ3IG5vbi1kZWZhdWx0LXJpYnMgKGZl
YXR1cmUpDQp8ICArLS1ydyByb3V0aW5nLXByb3RvY29scw0KICAgICAgfCAgICAgK6GqLS1ydyBy
b3V0aW5nLXByb3RvY29sKiBbdHlwZSBuYW1lXQ0KDQpJIGludGVuc2lvbmFsbHkgbGVmdCBvdXQg
dGhlIGludGVyZmFjZXMgc2luY2UgSSBkb26hr3QgbGlrZSBzb21lIG1vZGVscw0KYXVnbWVudGlu
ZyBvciByZWZlcmVuY2luZyB0aGUgaWV0Zi1pbnRlcmZhY2UgbGlzdCBhbmQgb3RoZXJzIGF1Z21l
bnRpbmcgb3INCnJlZmVyZW5jaW5nIHRoZSBsaXN0IGluIG91ciBydGctY2ZnIGRyYWZ0Lg0KDQpU
aGFua3MsDQpBY2VlDQoNCg0KDQoNCk9uIDIvMTgvMTUsIDY6MzYgQU0sICJUaG9tYXMgTW9yaW4i
IDx0aG9tYXMubW9yaW5Ab3JhbmdlLmNvbT4gd3JvdGU6DQoNCj5IaSBBY2VlLCBMYWRhLA0KPg0K
Pkl0IHNlZW1zIHRoYXQgbXkgY29tbWVudCB0aGF0IHlvdSBxdW90ZSB3YXMgbW9yZSByZWxhdGVk
IHRvIGZpbHRlcnMgdGhhbg0KPnRvIHJvdXRpbmcgdGFibGVzLCBhbmQgaW5kZWVkLCAqZmlsdGVy
cyogd2VyZSBtb3ZlZCBmcm9tICJyb3V0ZXIiIHRvDQo+Imdsb2JhbCIgaW4gcmV2aXNpb24gLTAz
IHRoYXQgZm9sbG93ZWQgbXkgcmV2aWV3Lg0KPg0KPkFkZGl0aW9uYWxseSwgTGFkYSwgeW91IHNh
eSB0aGF0IGJhc2VkIG9uIG15IGNvbW1lbnRzICJpbiByZXYuIC0wMyB0aGUNCj5saXN0IG9mIFJJ
QnMgKHRoZW4gY2FsbGVkICJyb3V0aW5nLXRhYmxlIikgd2FzIHRoZSBtb3ZlZCBvdXQgb2YgdGhl
DQo+cm91dGluZyBpbnN0YW5jZSAodGhlbiBjYWxsZWQgInJvdXRlciIpIGFuZCBiZWNhbWUgZ2xv
YmFsLiIuIEJ1dCBpZiBJDQo+bG9vayBhdCAtMDMsICJyb3V0aW5nLXRhYmxlIiBpcyBzdGlsbCBh
IGNoaWxkIG9mICJyb3V0ZXIiLiAgVGhlIGNoYW5nZQ0KPnRvIG1ha2UgInJvdXRpbmctdGFibGUi
IGdsb2JhbCB3YXMgbWFkZSBpbiAtMDUuDQo+DQo+SSBndWVzcyB5b3UgbmVlZCB0byBmaW5kIG91
dCB3aGF0IHdhcyB0aGUgbW90aXZhdGlvbiBmb3IgdGhlIGNoYW5nZSBpbg0KPi0wNSwgYSBmZXcg
bW9udGhzIGFmdGVyIG15IGluaXRpYWwgY29tbWVudHMgd2VyZSBhZGRyZXNzLg0KPg0KPkJlc3Qs
DQo+DQo+LVRob21hcw0KPg0KPg0KPg0KPg0KPg0KPjIwMTUtMDItMTMsIEFjZWUgTGluZGVtIChh
Y2VlKToNCj4+DQo+PiBIaSBMYWRhLCBUaG9tYXMsDQo+Pg0KPj4gT24gMi8xMy8xNSwgNToxMCBB
TSwgIkxhZGlzbGF2IExob3RrYSIgPGxob3RrYUBuaWMuY3o+IHdyb3RlOg0KPj4NCj4+PiBIaSwN
Cj4+Pg0KPj4+ICJBY2VlIExpbmRlbSAoYWNlZSkiIDxhY2VlQGNpc2NvLmNvbT4gd3JpdGVzOg0K
Pj4+DQo+Pj4+IEhpIFRob21hcywNCj4+Pj4NCj4+Pj4gSXQgaXMgbXkgdW5kZXJzdGFuZGluZyB0
aGF0IHRoZSBSSUJzIHdlcmUgbW92ZWQgb3V0IG9mIHRoZQ0KPj4+PiByb3V0aW5nLWluc3RhbmNl
IGluIHJlc3BvbnNlIHRvIHlvdXIgY29tbWVudCB0aGF0IGEgUklCIHdvdWxkIG5lZWQgdG8NCj4+
Pj5iZQ0KPj4+PiBhdHRhY2hlZCB0byBtdWx0aXBsZSByb3V0aW5nIGluc3RhbmNlcy4gSSBkb26p
9nQgYWdyZWUgd2l0aCB0aGlzDQo+Pj4+IG1vZGVsLiBJDQo+Pj4NCj4+PiBBY2VlIHJlZmVycyB0
byB0aGlzIGNvbW1lbnQgdGhhdCBUaG9tYXMgbWFkZSBpbiBoaXMgcmV2aWV3IG9mDQo+Pj4gZHJh
ZnQtaWV0Zi1uZXRtb2Qtcm91dGluZy1jZmctMDIgb24gMjAxMi0wMy0yMzoNCj4+Pg0KPj4+ICJB
bGxvd2luZyBtdWx0aXBsZSAicm91dGVycyIgaXMgYSBnb29kIHN0YXJ0aW5nIHBvaW50IGZvciB1
c2luZyB0aGVzZQ0KPj4+IHNwZWNzIGluIHRoZSBjb250ZXh0IG9mIFJGQzQzNjQgKE1QTFMvQkdQ
IElQIFZQTnMpLiBIb3dldmVyLCBpZiBJDQo+Pj4gdW5kZXJzdGFuZCBjb3JyZWN0bHkgWWFuZyBz
eW50YXgsIHRoZSB3YXkgdGhlIGZpbHRlcnMgYXJlIGRlZmluZWQgd291bGQNCj4+PiBub3Qgd29y
ayBpbiB0aGUgY29udGV4dCBvZiBSRkM0MzY0LCB3aGVyZSBhIEJHUCByb3V0aW5nIGluc3RhbmNl
IGluIHRoZQ0KPj4+IG1hc3RlciAicm91dGVyIiBleHBvcnRzIHNlbGVjdGVkIHJvdXRlcyBpbiBl
YWNoIG9mIHRoZSByb3V0aW5nIHRhYmxlIG9mDQo+Pj4gZWFjaCBWUE4gKFZSRikuICBUaGUgVlJG
IGFsc28gZXhwb3J0IHJvdXRlcyB0byB0aGUgbWFzdGVyIGluc3RhbmNlLiINCj4+Pg0KPj4+IEFu
ZCBpbmRlZWQsIGluIHJldi4gLTAzIHRoZSBsaXN0IG9mIFJJQnMgKHRoZW4gY2FsbGVkICJyb3V0
aW5nLXRhYmxlIikNCj4+PiB3YXMgdGhlIG1vdmVkIG91dCBvZiB0aGUgcm91dGluZyBpbnN0YW5j
ZSAodGhlbiBjYWxsZWQgInJvdXRlciIpIGFuZA0KPj4+IGJlY2FtZSBnbG9iYWwuDQo+Pg0KPj4g
VGhlbiBkbyB5b3UgYWdyZWUgdG8gbW92ZSB0aGUgUklCcyBiYWNrIGludG8gdGhlIHJvdXRpbmct
aW5zdGFuY2U/IEJvdGgNCj4+IHRoZSBCR1AgWUFORyBkcmFmdHMgbW9kZWwgTDNWUE4gZGVmaW5p
dGlvbnMgdW5kZXIgdGhlIGNvcnJlc3BvbmRpbmcNCj4+IGFkZHJlc3MgZmFtaWx5IGluIEJHUC4N
Cj4+DQo+PiBodHRwOi8vd3d3LmlldGYub3JnL2lkL2RyYWZ0LXNoYWlraC1pZHItYmdwLW1vZGVs
LTAwLnR4dA0KPj4gaHR0cDovL3d3dy5pZXRmLm9yZy9pZC9kcmFmdC16aGRhbmtpbi1pZHItYmdw
LWNmZy0wMC50eHQNCj4+DQo+PiBUaGFua3MsDQo+PiBBY2VlDQo+Pg0KPj4NCj4+DQo+Pj4NCj4+
PiBMYWRhDQo+Pj4NCj4+Pj4gYmVsaWV2ZSB0aGF0IGEgcm91dGluZyBpbnN0YW5jZSBpbXBsaWVz
IGEgVlJGLCB2aXJ0dWFsIHJvdXRlciBvcg0KPj4+PiBzb21ldGhpbmcNCj4+Pj4gaW4gYmV0d2Vl
biBhbmQgdGhhdCBhIFJJQiBzaG91bGQgYmUgYXNzb2NpYXRlZCB3aXRoIG9uZSBhbmQgb25seSBv
bmUNCj4+Pj4gcm91dGluZyBpbnN0YW5jZS4gQWRkaXRpb25hbGx5LCBJIGZlZWwgdGhhdCBSSUJz
IGFyZSBiYXNpY2FsbHkgcGFzc2l2ZQ0KPj4+PiBlbnRpdGllcyB3aXRoIHJlc3BlY3QgdG8gaW1w
b3J0L2V4cG9ydCBvZiByb3V0ZXMgYmV0d2VlbiBSSUJzIGluIHRoZQ0KPj4+PiBzYW1lDQo+Pj4+
IG9yIG90aGVyIHJvdXRpbmctaW5zdGFuY2VzLiBSYXRoZXIsIGFsbCBpbXBvcnQvZXhwb3J0IGlz
IHVuZGVyIHRoZQ0KPj4+PiBjb250cm9sDQo+Pj4+IG9mIGEgcm91dGluZy1wcm90b2NvbC4gRm9y
IGV4YW1wbGUsIHRoaXMgd291bGQgYmUgaGFuZGxlZCBieSBhIEJHUA0KPj4+PiByb3V0aW5nLXBy
b3RvY29sIGluc3RhbmNlIGZvciBMM1ZQTnMuDQo+Pj4+DQo+Pj4+IEmp9mQgbGlrZSB0byBnZXQg
dGhlIG9waW5pb25zIG9mIG90aGVycyBvbiB0aGlzIGZ1bmRhbWVudGFsIGFzcGVjdCBvZg0KPj4+
PnRoZQ0KPj4+PiBydGctY2ZnIG1vZGVsLg0KPj4+Pg0KPj4+PiBUaGFua3MsDQo+Pj4+IEFjZWUN
Cj4+Pj4NCj4+Pj4NCj4+Pg0KPj4+IC0tDQo+Pj4gTGFkaXNsYXYgTGhvdGthLCBDWi5OSUMgTGFi
cw0KPj4+IFBHUCBLZXkgSUQ6IEU3NEU4QzBDDQo+Pg0KPj4NCj4+DQo+DQoNCg==


From nobody Wed Feb 18 13:01:53 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 492BA1A1A9B; Wed, 18 Feb 2015 13:01:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.911
X-Spam-Level: 
X-Spam-Status: No, score=-13.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_14=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 Pr5iugaklKQ0; Wed, 18 Feb 2015 13:01:50 -0800 (PST)
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 1DD0F1A1A8A; Wed, 18 Feb 2015 13:01:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6154; q=dns/txt; s=iport; t=1424293311; x=1425502911; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=UfemtHEs9dl/ye2EBCWx4IkliEfHje63Cw1s70boShA=; b=Mh5Gf1fw0GqcbTmsp7zlpIYX8+6H5NzzB7a2qlbcxJvUy054W194aGza sMD5CXF0KQGlohmYvo8Czev6wezPcOGt7RIhcM5M8hwOz+r3jimS106XU lyKlWRmlETMQsWscAwmQsw8zB05TnknAQ9CBk2MRUBA8+LdHCsMH7euHg E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BhBQDw/ORU/40NJK1bgwZSWgSDBL9Zhg+BA0MBAQEBAQF8hA0BAQQ0VwEIGAQoBDAnBAESCYgmDZ1HnGQGmEEBAQgigRuJdIdXgUgFj0OJPIEZiU2EboM+IoIHF4FQbwGBQ38BAQE
X-IronPort-AV: E=Sophos;i="5.09,604,1418083200"; d="scan'208";a="394126037"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-1.cisco.com with ESMTP; 18 Feb 2015 21:01:50 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t1IL1n71019793 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 18 Feb 2015 21:01:49 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.175]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0195.001; Wed, 18 Feb 2015 15:01:49 -0600
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Thomas Morin <thomas.morin@orange.com>, Ladislav Lhotka <lhotka@nic.cz>, Routing YANG <rtg-yang-coord@ietf.org>, Routing WG <rtgwg@ietf.org>
Subject: Re: rtg-cfg hierachy    (Indentation in hierarchy corrected) 
Thread-Topic: rtg-cfg hierachy    (Indentation in hierarchy corrected) 
Thread-Index: AQHQS74c5g8pGC6LyU+IJwKVns4gSA==
Date: Wed, 18 Feb 2015 21:01:48 +0000
Message-ID: <D10A678C.EB2C%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.152.197]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <CF0FA5A797C2AF499FD07647E19D0FE9@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/Q4XJp6506XlM6tU0Hfx2Ezd5lPY>
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, 18 Feb 2015 21:01:52 -0000

VGhhbmtzIFRob21hcyBmb3IgdGhlIGNsYXJpZmljYXRpb24uDQoNCkmhr2QgbGlrZSB0byB0aGVu
IHN1Z2dlc3Qgd2UgY2hhbmdlIHRoZSBydGctY2ZnIG1vZGVsIGhpZXJhcmNoeSB0byByZWZsZWN0
DQp3aGF0IG1vc3Qgcm91dGluZyBkZXZpY2UgaW1wbGVtZW50YXRpb25zLg0KVGhlcmUgaXMgYSBS
SUIgKHlvdSBjYW4gY2FsbCBpdCBhIGRlZmF1bHQtUklCIGlmIHlvdSBsaWtlKSBmb3IgZXZlcnkN
CkFkZHJlc3MgRmFtaWx5IChBRikuIE11bHRpcGxlIFJJQnMgcGVyIEFGIGlzIG5vdCB3aWRlbHkg
aW1wbGVtZW50ZWQgYW5kIEkNCmRvbqGvdCBzZWUgaXQgYmVjb21pbmcgbW9yZSBwcmV2YWxlbnQu
IEhlbmNlLCBJIGFncmVlIGl0IHNob3VsZCBiZSBhDQpmZWF0dXJlLiBUaGUgb25lIGltcGxlbWVu
dGF0aW9uIEmhr20gZmFtaWxpYXIgd2l0aCBpcyBtdWx0aXBsZSB0b3BvbG9neQ0Kcm91dGluZyAo
ZS5nLiwgUkZDIDQ5MTUpLCB3aGVyZSBSSUIgY29ycmVzcG9uZHMgdG8gYSBGSUIgdGhhdCBpcyBz
ZWxlY3RlZA0KYmFzZWQgb24gcGFja2V0IG1hcmtpbmcuIERvZXMgYW55b25lIGhhdmUgYW55IG90
aGVyIGV4YW1wbGVzPw0KDQpUaGlzIHdvdWxkIGltcGx5IHRoYXQgUklCcyBhcmUgd2l0aGluIGEg
cm91dGluZy1pbnN0YW5jZSBhbmQgdGhhdA0Kcm91dGluZy1wcm90b2NvbHMgd2l0aGluIHRoZSBy
b3V0aW5nLWluc3RhbmNlIGNhbiBvcGVyYXRlIG9uIHRoZXNlIFJJQnMuDQpUaGVyZSBpcyBubyBy
ZXF1aXJlbWVudCBjb25uZWN0IFJJQnMgdG8gcm91dGluZy1wcm90b2NvbHMgb3IgdG8gZm9ybQ0K
Y29ubmVjdGlvbnMgYmV0d2VlbiBSSUJzLg0KDQpUaGlzIHdvdWxkIGdpdmUgdXMgYSBoaWdoLWxl
dmVsIGhpZXJhcmNoeSBvZjoNCg0Kcncgcm91dGluZy1pbnN0YW5jZSogW25hbWVdDQogICAgICB8
ICArLS1ydyBhZGRyZXNzLWZhbWlseQ0KICAgICAgfCAgfCAgfC0tcncgZGVmYXVsdC1yaWIqIFth
ZGRyZXNzLWZhbWlseV0NCiAgICAgIHwgIHwgICstLXJ3IG5vbi1kZWZhdWx0LXJpYnMgKGZlYXR1
cmUpDQogICAgICB8ICArLS1ydyByb3V0aW5nLXByb3RvY29scw0KICAgICAgfCAgICAgK6GqLS1y
dyByb3V0aW5nLXByb3RvY29sKiBbdHlwZSBuYW1lXQ0KDQpJIGludGVuc2lvbmFsbHkgbGVmdCBv
dXQgdGhlIGludGVyZmFjZXMgc2luY2UgSSBkb26hr3QgbGlrZSBzb21lIG1vZGVscw0KYXVnbWVu
dGluZyBvciByZWZlcmVuY2luZyB0aGUgaWV0Zi1pbnRlcmZhY2UgbGlzdCBhbmQgb3RoZXJzIGF1
Z21lbnRpbmcgb3INCnJlZmVyZW5jaW5nIHRoZSBsaXN0IGluIG91ciBydGctY2ZnIGRyYWZ0Lg0K
DQpUaGFua3MsDQpBY2VlDQoNCg0KDQoNCk9uIDIvMTgvMTUsIDY6MzYgQU0sICJUaG9tYXMgTW9y
aW4iIDx0aG9tYXMubW9yaW5Ab3JhbmdlLmNvbT4gd3JvdGU6DQoNCj5IaSBBY2VlLCBMYWRhLA0K
Pg0KPkl0IHNlZW1zIHRoYXQgbXkgY29tbWVudCB0aGF0IHlvdSBxdW90ZSB3YXMgbW9yZSByZWxh
dGVkIHRvIGZpbHRlcnMgdGhhbg0KPnRvIHJvdXRpbmcgdGFibGVzLCBhbmQgaW5kZWVkLCAqZmls
dGVycyogd2VyZSBtb3ZlZCBmcm9tICJyb3V0ZXIiIHRvDQo+Imdsb2JhbCIgaW4gcmV2aXNpb24g
LTAzIHRoYXQgZm9sbG93ZWQgbXkgcmV2aWV3Lg0KPg0KPkFkZGl0aW9uYWxseSwgTGFkYSwgeW91
IHNheSB0aGF0IGJhc2VkIG9uIG15IGNvbW1lbnRzICJpbiByZXYuIC0wMyB0aGUNCj5saXN0IG9m
IFJJQnMgKHRoZW4gY2FsbGVkICJyb3V0aW5nLXRhYmxlIikgd2FzIHRoZSBtb3ZlZCBvdXQgb2Yg
dGhlDQo+cm91dGluZyBpbnN0YW5jZSAodGhlbiBjYWxsZWQgInJvdXRlciIpIGFuZCBiZWNhbWUg
Z2xvYmFsLiIuIEJ1dCBpZiBJDQo+bG9vayBhdCAtMDMsICJyb3V0aW5nLXRhYmxlIiBpcyBzdGls
bCBhIGNoaWxkIG9mICJyb3V0ZXIiLiAgVGhlIGNoYW5nZQ0KPnRvIG1ha2UgInJvdXRpbmctdGFi
bGUiIGdsb2JhbCB3YXMgbWFkZSBpbiAtMDUuDQo+DQo+SSBndWVzcyB5b3UgbmVlZCB0byBmaW5k
IG91dCB3aGF0IHdhcyB0aGUgbW90aXZhdGlvbiBmb3IgdGhlIGNoYW5nZSBpbg0KPi0wNSwgYSBm
ZXcgbW9udGhzIGFmdGVyIG15IGluaXRpYWwgY29tbWVudHMgd2VyZSBhZGRyZXNzLg0KPg0KPkJl
c3QsDQo+DQo+LVRob21hcw0KPg0KPg0KPg0KPg0KPg0KPjIwMTUtMDItMTMsIEFjZWUgTGluZGVt
IChhY2VlKToNCj4+DQo+PiBIaSBMYWRhLCBUaG9tYXMsDQo+Pg0KPj4gT24gMi8xMy8xNSwgNTox
MCBBTSwgIkxhZGlzbGF2IExob3RrYSIgPGxob3RrYUBuaWMuY3o+IHdyb3RlOg0KPj4NCj4+PiBI
aSwNCj4+Pg0KPj4+ICJBY2VlIExpbmRlbSAoYWNlZSkiIDxhY2VlQGNpc2NvLmNvbT4gd3JpdGVz
Og0KPj4+DQo+Pj4+IEhpIFRob21hcywNCj4+Pj4NCj4+Pj4gSXQgaXMgbXkgdW5kZXJzdGFuZGlu
ZyB0aGF0IHRoZSBSSUJzIHdlcmUgbW92ZWQgb3V0IG9mIHRoZQ0KPj4+PiByb3V0aW5nLWluc3Rh
bmNlIGluIHJlc3BvbnNlIHRvIHlvdXIgY29tbWVudCB0aGF0IGEgUklCIHdvdWxkIG5lZWQgdG8N
Cj4+Pj5iZQ0KPj4+PiBhdHRhY2hlZCB0byBtdWx0aXBsZSByb3V0aW5nIGluc3RhbmNlcy4gSSBk
b26p9nQgYWdyZWUgd2l0aCB0aGlzDQo+Pj4+IG1vZGVsLiBJDQo+Pj4NCj4+PiBBY2VlIHJlZmVy
cyB0byB0aGlzIGNvbW1lbnQgdGhhdCBUaG9tYXMgbWFkZSBpbiBoaXMgcmV2aWV3IG9mDQo+Pj4g
ZHJhZnQtaWV0Zi1uZXRtb2Qtcm91dGluZy1jZmctMDIgb24gMjAxMi0wMy0yMzoNCj4+Pg0KPj4+
ICJBbGxvd2luZyBtdWx0aXBsZSAicm91dGVycyIgaXMgYSBnb29kIHN0YXJ0aW5nIHBvaW50IGZv
ciB1c2luZyB0aGVzZQ0KPj4+IHNwZWNzIGluIHRoZSBjb250ZXh0IG9mIFJGQzQzNjQgKE1QTFMv
QkdQIElQIFZQTnMpLiBIb3dldmVyLCBpZiBJDQo+Pj4gdW5kZXJzdGFuZCBjb3JyZWN0bHkgWWFu
ZyBzeW50YXgsIHRoZSB3YXkgdGhlIGZpbHRlcnMgYXJlIGRlZmluZWQgd291bGQNCj4+PiBub3Qg
d29yayBpbiB0aGUgY29udGV4dCBvZiBSRkM0MzY0LCB3aGVyZSBhIEJHUCByb3V0aW5nIGluc3Rh
bmNlIGluIHRoZQ0KPj4+IG1hc3RlciAicm91dGVyIiBleHBvcnRzIHNlbGVjdGVkIHJvdXRlcyBp
biBlYWNoIG9mIHRoZSByb3V0aW5nIHRhYmxlIG9mDQo+Pj4gZWFjaCBWUE4gKFZSRikuICBUaGUg
VlJGIGFsc28gZXhwb3J0IHJvdXRlcyB0byB0aGUgbWFzdGVyIGluc3RhbmNlLiINCj4+Pg0KPj4+
IEFuZCBpbmRlZWQsIGluIHJldi4gLTAzIHRoZSBsaXN0IG9mIFJJQnMgKHRoZW4gY2FsbGVkICJy
b3V0aW5nLXRhYmxlIikNCj4+PiB3YXMgdGhlIG1vdmVkIG91dCBvZiB0aGUgcm91dGluZyBpbnN0
YW5jZSAodGhlbiBjYWxsZWQgInJvdXRlciIpIGFuZA0KPj4+IGJlY2FtZSBnbG9iYWwuDQo+Pg0K
Pj4gVGhlbiBkbyB5b3UgYWdyZWUgdG8gbW92ZSB0aGUgUklCcyBiYWNrIGludG8gdGhlIHJvdXRp
bmctaW5zdGFuY2U/IEJvdGgNCj4+IHRoZSBCR1AgWUFORyBkcmFmdHMgbW9kZWwgTDNWUE4gZGVm
aW5pdGlvbnMgdW5kZXIgdGhlIGNvcnJlc3BvbmRpbmcNCj4+IGFkZHJlc3MgZmFtaWx5IGluIEJH
UC4NCj4+DQo+PiBodHRwOi8vd3d3LmlldGYub3JnL2lkL2RyYWZ0LXNoYWlraC1pZHItYmdwLW1v
ZGVsLTAwLnR4dA0KPj4gaHR0cDovL3d3dy5pZXRmLm9yZy9pZC9kcmFmdC16aGRhbmtpbi1pZHIt
YmdwLWNmZy0wMC50eHQNCj4+DQo+PiBUaGFua3MsDQo+PiBBY2VlDQo+Pg0KPj4NCj4+DQo+Pj4N
Cj4+PiBMYWRhDQo+Pj4NCj4+Pj4gYmVsaWV2ZSB0aGF0IGEgcm91dGluZyBpbnN0YW5jZSBpbXBs
aWVzIGEgVlJGLCB2aXJ0dWFsIHJvdXRlciBvcg0KPj4+PiBzb21ldGhpbmcNCj4+Pj4gaW4gYmV0
d2VlbiBhbmQgdGhhdCBhIFJJQiBzaG91bGQgYmUgYXNzb2NpYXRlZCB3aXRoIG9uZSBhbmQgb25s
eSBvbmUNCj4+Pj4gcm91dGluZyBpbnN0YW5jZS4gQWRkaXRpb25hbGx5LCBJIGZlZWwgdGhhdCBS
SUJzIGFyZSBiYXNpY2FsbHkgcGFzc2l2ZQ0KPj4+PiBlbnRpdGllcyB3aXRoIHJlc3BlY3QgdG8g
aW1wb3J0L2V4cG9ydCBvZiByb3V0ZXMgYmV0d2VlbiBSSUJzIGluIHRoZQ0KPj4+PiBzYW1lDQo+
Pj4+IG9yIG90aGVyIHJvdXRpbmctaW5zdGFuY2VzLiBSYXRoZXIsIGFsbCBpbXBvcnQvZXhwb3J0
IGlzIHVuZGVyIHRoZQ0KPj4+PiBjb250cm9sDQo+Pj4+IG9mIGEgcm91dGluZy1wcm90b2NvbC4g
Rm9yIGV4YW1wbGUsIHRoaXMgd291bGQgYmUgaGFuZGxlZCBieSBhIEJHUA0KPj4+PiByb3V0aW5n
LXByb3RvY29sIGluc3RhbmNlIGZvciBMM1ZQTnMuDQo+Pj4+DQo+Pj4+IEmp9mQgbGlrZSB0byBn
ZXQgdGhlIG9waW5pb25zIG9mIG90aGVycyBvbiB0aGlzIGZ1bmRhbWVudGFsIGFzcGVjdCBvZg0K
Pj4+PnRoZQ0KPj4+PiBydGctY2ZnIG1vZGVsLg0KPj4+Pg0KPj4+PiBUaGFua3MsDQo+Pj4+IEFj
ZWUNCj4+Pj4NCj4+Pj4NCj4+Pg0KPj4+IC0tDQo+Pj4gTGFkaXNsYXYgTGhvdGthLCBDWi5OSUMg
TGFicw0KPj4+IFBHUCBLZXkgSUQ6IEU3NEU4QzBDDQo+Pg0KPj4NCj4+DQo+DQoNCg0K


From nobody Thu Feb 19 23:21:16 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 55B7C1A3BA7 for <rtgwg@ietfa.amsl.com>; Thu, 19 Feb 2015 23:21:14 -0800 (PST)
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 gMWQRsgIH15L for <rtgwg@ietfa.amsl.com>; Thu, 19 Feb 2015 23:21:11 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8F091A1F70 for <rtgwg@ietf.org>; Thu, 19 Feb 2015 23:21:10 -0800 (PST)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id C08E33B455E for <rtgwg@ietf.org>; Fri, 20 Feb 2015 08:21:08 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.16]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 9B97627C08D for <rtgwg@ietf.org>; Fri, 20 Feb 2015 08:21:08 +0100 (CET)
Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.142]) by OPEXCLILH05.corporate.adroot.infra.ftgroup ([10.114.31.16]) with mapi id 14.03.0224.002; Fri, 20 Feb 2015 08:21:08 +0100
From: <stephane.litkowski@orange.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AdBM3SH2oNl2urLXSA+s5ntM7pKOsA==
Date: Fri, 20 Feb 2015 07:21:07 +0000
Message-ID: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: multipart/related; boundary="_004_9E32478DFA9976438E7A22F69B08FF9215C13D54OPEXCLILM34corp_"; type="multipart/alternative"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.2.20.13033
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/JGr3KK62Jzoog4ePCZGKlSleI4g>
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, 20 Feb 2015 07:21:14 -0000

--_004_9E32478DFA9976438E7A22F69B08FF9215C13D54OPEXCLILM34corp_
Content-Type: multipart/alternative;
	boundary="_000_9E32478DFA9976438E7A22F69B08FF9215C13D54OPEXCLILM34corp_"


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

Hi Folks,

As you know, LFA manageability draft is in final phasis ...
The current document states per AF granularity activation as a SHOULD.
"
5.1<https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#secti=
on-5.1>.  LFA enabling/disabling scope





   The granularity of LFA activation should be controlled (as alternate

   nexthop consume memory in forwarding plane).



   An implementation of LFA SHOULD allow its activation with the

   following criteria:



   o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,

      LDP IPv6 unicast ...



   o  Per routing context : VRF, virtual/logical router, global routing

      table, ...


"

In the framework of ISIS/OSPF yang modelization, we are challenging this st=
atement, do we really need to force implementation to support this "per AF"=
 granularity ?

Please provide as soon as possible your feedback on this and also provide c=
lear drivers to support or not per AF activation of LFA.


Thanks for your help !


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/IBNF/ENDD/NDE
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>



___________________________________________________________________________=
______________________________________________

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_9E32478DFA9976438E7A22F69B08FF9215C13D54OPEXCLILM34corp_
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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:0in;
	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:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
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;
	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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Folks,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As you know, LFA manageability draft is in final pha=
sis &#8230;<o:p></o:p></p>
<p class=3D"MsoNormal">The current document states per AF granularity activ=
ation as a SHOULD.<o:p></o:p></p>
<p class=3D"MsoNormal">&#8220;<o:p></o:p></p>
<h3 style=3D"page-break-before:always"><a name=3D"section-5.1"></a><a href=
=3D"https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#secti=
on-5.1"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black;text-decora=
tion:none">5.1</span></a><span lang=3D"EN" style=3D"font-size:10.0pt">.&nbs=
p;
 LFA enabling/disabling scope<o:p></o:p></span></h3>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; The granularity of LFA activation should be controll=
ed (as alternate<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; nexthop consume memory in forwarding plane).<o:p></o=
:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; An implementation of LFA SHOULD allow its activation=
 with the<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; following criteria:<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; o&nbsp; Per address-family : ipv4 unicast, ipv6 unic=
ast, LDP IPv4 unicast,<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LDP IPv6 unicast ...<o:p></o:p></s=
pan></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; o&nbsp; Per routing context : VRF, virtual/logical r=
outer, global routing<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; table, ...<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<p class=3D"MsoNormal">&#8220;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In the framework of ISIS/OSPF yang modelization, we =
are challenging this statement, do we really need to force implementation t=
o support this &#8220;per AF&#8221; granularity ?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please provide as soon as possible your feedback on =
this and also provide clear drivers to support or not per AF activation of =
LFA.<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">Thanks for your help !<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"><a href=3D"http://www.orange.com/"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;co=
lor:blue;text-decoration:none"><img border=3D"0" width=3D"40" height=3D"40"=
 id=3D"Picture_x0020_1" src=3D"cid:image001.gif@01D04CE5.FA95AFC0" alt=3D"O=
range logo"></span></a><span lang=3D"FR" style=3D"font-size:12.0pt;font-fam=
ily:&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;">&nbsp;<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:black">Stephane Litkowski
</span></b><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Network Architect
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Orange/SCE/EQUANT/IBNF/ENDD/NDE
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Orange Expert Fut=
ure Networks</span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:=
&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<span style=3D"color:black;text-decoration:none">&#43;33 2 23 28 49 83 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;"><br>
</span><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:black">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<span style=3D"color:black;text-decoration:none">&#43;33 6 37 86 97 52 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><span style=3D"font-size:1=
0.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#FF6600;te=
xt-decoration:none">stephane.litkowski@orange.com</span></a>
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span lang=3D"FR" style=
=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&qu=
ot;">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</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_9E32478DFA9976438E7A22F69B08FF9215C13D54OPEXCLILM34corp_--

--_004_9E32478DFA9976438E7A22F69B08FF9215C13D54OPEXCLILM34corp_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: inline; filename="image001.gif"; size=381;
	creation-date="Fri, 20 Feb 2015 07:21:07 GMT";
	modification-date="Fri, 20 Feb 2015 07:21:07 GMT"
Content-ID: <image001.gif@01D04CE5.FA95AFC0>
Content-Transfer-Encoding: base64

R0lGODlhKAAoAMQAAP+MQP+zgP/17//s3/+DMP/iz/+fYP+8j/9wEP95IP/Gn/+WUP/Pr/+pcP/Z
v/////9mAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAAA
AAAALAAAAAAoACgAAAX6oAONZGmeaEqKauum7Cu/8Wyj9a2P+X73vhkwSCPuhkYVMolj2pbOEjTK
oxatrSlVG+U6vUxwUmwkE81BtE99xGbdSjhMPgo4BAoA+wUICAR6IwQODwMNEAcOigAFhQYQDgoD
DwcQBJOKBIOFDQmaCCyTB416hQcBBQuTEA8Cow8EBQINpHcGhAkrEAkPChAAD3YPCLuSDw+sIgEP
wCILzK0OjY9VBJS/wYQjfwaNyRDLzRAG0AMB5wC6ENyEt8jWDAsCyA/KzJN+zLILqLlVv/OuaYPU
alU9cMwuPSCl8AEDYv8EQbwRgAEABcziJFl2bMmeEQgATEwRAgA7

--_004_9E32478DFA9976438E7A22F69B08FF9215C13D54OPEXCLILM34corp_--


From nobody Thu Feb 19 23:29:41 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 884461A3BA7 for <rtgwg@ietfa.amsl.com>; Thu, 19 Feb 2015 23:29:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 RyP0hevzH2UA for <rtgwg@ietfa.amsl.com>; Thu, 19 Feb 2015 23:29:36 -0800 (PST)
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 932661A038C for <rtgwg@ietf.org>; Thu, 19 Feb 2015 23:29:36 -0800 (PST)
X-AuditID: c6180641-f79916d00000623a-88-54e682224c32
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 76.A0.25146.22286E45; Fri, 20 Feb 2015 01:38:59 +0100 (CET)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0210.002; Fri, 20 Feb 2015 02:29:34 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AdBM3SH2oNl2urLXSA+s5ntM7pKOsP//0WCA
Date: Fri, 20 Feb 2015 07:29:34 +0000
Message-ID: <D10C20F9.8EB79%jeff.tantsura@ericsson.com>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup>
In-Reply-To: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.4.140807
x-originating-ip: [147.117.188.12]
Content-Type: multipart/mixed; boundary="_004_D10C20F98EB79jefftantsuraericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrPIsWRmVeSWpSXmKPExsUyuXRPoK5y07MQg9v93BYX3vxmtvi69yGr A5PHkiU/mTxanp1kC2CK4rJJSc3JLEst0rdL4Mo42D2TqWBLD2PFvb4etgbGAzVdjJwcEgIm Eq8e3maGsMUkLtxbz9bFyMUhJHCEUWLXq28sEM5yRomlX54wglSxCRhI/P92nAXEFhHIkHi9 fjc7iC0s4Cwxadoadoi4i8Sp592sELaRROOktUA2BweLgKpEyz0RkDCvgLlE49ZGdoj5HYwS pzY9B1vGKdDJKDH77luwQYxAJ30/tYYJxGYWEJe49WQ+E8SpIhIPL55mg7BFJV4+/ge2TFRA T+LZhs3sEHEliTmvrzFD9IZJ/H93iAlis6DEyZlPWCYwis5CMnYWkrJZSMog4jESDxveM0PY BhLvz82HsrUlli18DWXrS2z8cpYRwraW2DujhQlTjY7E5ks7oWYqSrR1zgaq4QKyVzBK3N/w AKiZA6xo5WYNmJop3Q/ZFzDyrWLkKC1OLctNNzLcxAhMAcck2Bx3MC74ZHmIUYCDUYmH90PW sxAh1sSy4srcQ4zSHCxK4rxlVw6GCAmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamB09b/646zM 2pkHZ0c4az5JOsHLtOXXnVuvCkMalqfmdnOsOMAdfTzK0236Lb7Gr3N33PkhL73MpeuLWOx7 x7Bd34tu905rObBObEr44qlR105z2b7hyeQN99F2iWtXZAieyb2o5eLDhwxrlHMZd9yumuT7 xWlaXsaiaQs3bLf8dHCRfOuq2tStSizFGYmGWsxFxYkAHsKsVuICAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/IoXxGKJvHKF0kgFuXyy3Eksn0Ng>
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, 20 Feb 2015 07:29:39 -0000

--_004_D10C20F98EB79jefftantsuraericssoncom_
Content-Type: multipart/alternative;
	boundary="_000_D10C20F98EB79jefftantsuraericssoncom_"

--_000_D10C20F98EB79jefftantsuraericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi Stephane,

/chair hat off

IMO in disjoined topologies one should have flexibility to enable/disable L=
FA as per AF.


Cheers,
Jeff

From: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>"=
 <stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>
Date: Thursday, February 19, 2015 at 11:21 PM
To: "rtgwg@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ie=
tf.org>>
Subject: LFA manageability : per AF config =3D> feedback required

Hi Folks,

As you know, LFA manageability draft is in final phasis =85
The current document states per AF granularity activation as a SHOULD.
=93
5.1<https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#secti=
on-5.1>.  LFA enabling/disabling scope





   The granularity of LFA activation should be controlled (as alternate

   nexthop consume memory in forwarding plane).



   An implementation of LFA SHOULD allow its activation with the

   following criteria:



   o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,

      LDP IPv6 unicast ...



   o  Per routing context : VRF, virtual/logical router, global routing

      table, ...


=93

In the framework of ISIS/OSPF yang modelization, we are challenging this st=
atement, do we really need to force implementation to support this =93per A=
F=94 granularity ?

Please provide as soon as possible your feedback on this and also provide c=
lear drivers to support or not per AF activation of LFA.


Thanks for your help !


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/IBNF/ENDD/NDE
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>



___________________________________________________________________________=
______________________________________________

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_D10C20F98EB79jefftantsuraericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <0965E2D390FC504A8ADD4D005E189ECA@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<div>
<div><font face=3D"Calibri,sans-serif">Hi Stephane,</font></div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
/chair hat off</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
IMO in disjoined topologies one should have flexibility to enable/disable L=
FA as per AF.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<div><span style=3D"font-family: Calibri; "><br>
</span></div>
<div><span style=3D"font-family: Calibri; ">Cheers,</span></div>
<div><font class=3D"Apple-style-span" color=3D"#000000"><font class=3D"Appl=
e-style-span" face=3D"Calibri">Jeff</font></font></div>
</div>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>&quot;<a href=3D"mailto:steph=
ane.litkowski@orange.com">stephane.litkowski@orange.com</a>&quot; &lt;<a hr=
ef=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.com</=
a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Thursday, February 19, 2015 a=
t 11:21 PM<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:rtgwg@i=
etf.org">rtgwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.org">rtg=
wg@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>LFA manageability : per AF=
 config =3D&gt; feedback required<br>
</div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:0in;
	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:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
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;
	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]-->
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Folks,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As you know, LFA manageability draft is in final pha=
sis =85<o:p></o:p></p>
<p class=3D"MsoNormal">The current document states per AF granularity activ=
ation as a SHOULD.<o:p></o:p></p>
<p class=3D"MsoNormal">=93<o:p></o:p></p>
<h3 style=3D"page-break-before:always"><a name=3D"section-5.1"></a><a href=
=3D"https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#secti=
on-5.1"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black;text-decora=
tion:none">5.1</span></a><span lang=3D"EN" style=3D"font-size:10.0pt">.&nbs=
p;
 LFA enabling/disabling scope<o:p></o:p></span></h3>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; The granularity of LFA activation should be controll=
ed (as alternate<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; nexthop consume memory in forwarding plane).<o:p></o=
:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; An implementation of LFA SHOULD allow its activation=
 with the<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; following criteria:<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; o&nbsp; Per address-family : ipv4 unicast, ipv6 unic=
ast, LDP IPv4 unicast,<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LDP IPv6 unicast ...<o:p></o:p></s=
pan></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; o&nbsp; Per routing context : VRF, virtual/logical r=
outer, global routing<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; table, ...<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<p class=3D"MsoNormal">=93<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In the framework of ISIS/OSPF yang modelization, we =
are challenging this statement, do we really need to force implementation t=
o support this =93per AF=94 granularity ?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please provide as soon as possible your feedback on =
this and also provide clear drivers to support or not per AF activation of =
LFA.<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">Thanks for your help !<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"><a href=3D"http://www.orange.com/"><span style=3D"fo=
nt-size: 12pt; font-family: 'Times New Roman', serif; color: blue; text-dec=
oration: none;"><img border=3D"0" width=3D"40" height=3D"40" id=3D"Picture_=
x0020_1" src=3D"cid:image001.gif@01D04CE5.FA95AFC0" alt=3D"Orange logo"></s=
pan></a><span lang=3D"FR" style=3D"font-size: 12pt; font-family: 'Times New=
 Roman', serif;"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e: 12pt; font-family: 'Times New Roman', serif;">&nbsp;<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Aria=
l, sans-serif; color: black;">Stephane Litkowski
</span></b><span style=3D"font-size: 12pt; font-family: 'Times New Roman', =
serif;"><br>
</span><span style=3D"font-size: 10pt; font-family: Arial, sans-serif; colo=
r: black;">Network Architect
</span><span style=3D"font-size: 12pt; font-family: 'Times New Roman', seri=
f;"><br>
</span><span style=3D"font-size: 10pt; font-family: Arial, sans-serif; colo=
r: black;">Orange/SCE/EQUANT/IBNF/ENDD/NDE
</span><span style=3D"font-size: 12pt; font-family: 'Times New Roman', seri=
f;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size: 10pt; font-fam=
ily: Arial, sans-serif; color: black;">Orange Expert Future Networks</span>=
<span lang=3D"FR" style=3D"font-size: 12pt; font-family: 'Times New Roman',=
 serif;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size: 10pt; font-fam=
ily: Arial, sans-serif; color: black;">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<span style=3D"color:black;text-decoration:none">&#43;33 2 23 28 49 83 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size: 12pt; font-family: 'Tim=
es New Roman', serif;"><br>
</span><span lang=3D"FR" style=3D"font-size: 10pt; font-family: Arial, sans=
-serif; color: black;">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<span style=3D"color:black;text-decoration:none">&#43;33 6 37 86 97 52 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size: 12pt; font-family: 'Tim=
es New Roman', serif;"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><span style=3D"font-size: =
10pt; font-family: Arial, sans-serif; color: rgb(255, 102, 0); text-decorat=
ion: none;">stephane.litkowski@orange.com</span></a><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span lang=3D"FR" style=
=3D"font-size: 12pt; font-family: 'Times New Roman', serif;">&nbsp;<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</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>
</div>
</div>
</blockquote>
</span>
</body>
</html>

--_000_D10C20F98EB79jefftantsuraericssoncom_--

--_004_D10C20F98EB79jefftantsuraericssoncom_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: attachment; filename="image001.gif"; size=381;
	creation-date="Fri, 20 Feb 2015 07:29:34 GMT";
	modification-date="Fri, 20 Feb 2015 07:29:34 GMT"
Content-ID: <image001.gif@01D04CE5.FA95AFC0>
Content-Transfer-Encoding: base64

R0lGODlhKAAoAMQAAP+MQP+zgP/17//s3/+DMP/iz/+fYP+8j/9wEP95IP/Gn/+WUP/Pr/+pcP/Z
v/////9mAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAAA
AAAALAAAAAAoACgAAAX6oAONZGmeaEqKauum7Cu/8Wyj9a2P+X73vhkwSCPuhkYVMolj2pbOEjTK
oxatrSlVG+U6vUxwUmwkE81BtE99xGbdSjhMPgo4BAoA+wUICAR6IwQODwMNEAcOigAFhQYQDgoD
DwcQBJOKBIOFDQmaCCyTB416hQcBBQuTEA8Cow8EBQINpHcGhAkrEAkPChAAD3YPCLuSDw+sIgEP
wCILzK0OjY9VBJS/wYQjfwaNyRDLzRAG0AMB5wC6ENyEt8jWDAsCyA/KzJN+zLILqLlVv/OuaYPU
alU9cMwuPSCl8AEDYv8EQbwRgAEABcziJFl2bMmeEQgATEwRAgA7

--_004_D10C20F98EB79jefftantsuraericssoncom_--


From nobody Fri Feb 20 01:17:12 2015
Return-Path: <asmirnov@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 C9BCD1A8747 for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 01:17:10 -0800 (PST)
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 IFMhK4_QOyaf for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 01:17:08 -0800 (PST)
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 383B61A8742 for <rtgwg@ietf.org>; Fri, 20 Feb 2015 01:17:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3842; q=dns/txt; s=iport; t=1424423828; x=1425633428; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=3tm8tjpZEgN7MXwHMPMeCZEq63ERAaX/tV8vlvOzAYE=; b=l8EyLfIDmuaRgaBCKrvwGnBc+xl5mWfMs3h+PywIoWBaxrvXTzIS6V51 yzbruKkRbbqEDpXABm8SWue7VFvGlVe6kZfnrlu8pMHICWCdtRRkGeCMr beK03gciBi5y3b1SiFeNlvK8CcY0QdqZIkgM2yHtvNv9LjpoK9HdskNXg 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D/BAC0+uZU/xbLJq1bg1VawDaCMweFdAKBWAEBAQEBAXyEEAEBBAEBAS8BBTMDCg8CCwcRCRYIBwkDAgECAQkMHxEGAQwGAgEBF4gAAxENzigDhTwBAQEBAQEBAQEBAQEBAQEBAQEBAQEXBIsLgU+CPREBSwyEKgEEkyqFZYEZOIJbi0GDPiKDbz0xAQEBAYEHgTgBAQE
X-IronPort-AV: E=Sophos;i="5.09,613,1418083200"; d="scan'208";a="355431939"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 20 Feb 2015 09:17:05 +0000
Received: from as-lnx.cisco.com (ams-asmirnov-8713.cisco.com [10.55.140.84]) (authenticated bits=0) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t1K9H5ZV010842 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 20 Feb 2015 09:17:05 GMT
Message-ID: <54E6FB8F.8000601@cisco.com>
Date: Fri, 20 Feb 2015 10:17:03 +0100
From: Anton Smirnov <asmirnov@cisco.com>
Organization: Cisco Systems
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: stephane.litkowski@orange.com, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: LFA manageability : per AF config => feedback required
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup>
In-Reply-To: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Authenticated-User: asmirnov
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/3qQcynv3NtKk_wjD5dfBQ18Nme4>
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, 20 Feb 2015 09:17:10 -0000

    Hi Stephane,
    I think concern of "alternate nexthops consume resources in the 
forwarding plane" is generally a valid one. But if you want to solve 
*this* problem then solution is to give to operator great flexibility to 
select set of prefixes which are allowed to have protection and this 
flexibility should go beyond of just per-AF selection.

    Per-context selection would actually solve different problem - CPU 
resources needed to compute LFAs (which are spent per-topology 
independent of number of nexthops which end up being protected).

    So IMO per-AF granularity might be useful (especially in disjoint 
topologies) but reason given in the draft does not connect with the 
solution.

Anton


On 02/20/2015 08:21 AM, stephane.litkowski@orange.com wrote:
> Hi Folks,
>
> As you know, LFA manageability draft is in final phasis …
>
> The current document states per AF granularity activation as a SHOULD.
>
> “
>
>
>       5.1
>       <https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#section-5.1>.
>       LFA enabling/disabling scope
>
>
>
>
>
>     The granularity of LFA activation should be controlled (as alternate
>
>     nexthop consume memory in forwarding plane).
>
>
>
>     An implementation of LFA SHOULD allow its activation with the
>
>     following criteria:
>
>
>
>     o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,
>
>        LDP IPv6 unicast ...
>
>
>
>     o  Per routing context : VRF, virtual/logical router, global routing
>
>        table, ...
>
>
>
> “
>
> In the framework of ISIS/OSPF yang modelization, we are challenging this
> statement, do we really need to force implementation to support this
> “per AF” granularity ?
>
> Please provide as soon as possible your feedback on this and also
> provide clear drivers to support or not per AF activation of LFA.
>
> Thanks for your help !
>
> Orange logo <http://www.orange.com/>
>
> *Stephane Litkowski *
> Network Architect
> Orange/SCE/EQUANT/IBNF/ENDD/NDE
>
> Orange Expert Future Networks
>
> phone: +33 2 23 28 49 83
> <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20>
> mobile: +33 6 37 86 97 52
> <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20>
> stephane.litkowski@orange.com <mailto:stephane.litkowski@orange.com>
>
> _________________________________________________________________________________________________________________________
>
> 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 Fri Feb 20 01:27:01 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 9F6D91A8749 for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 01:26:59 -0800 (PST)
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 8v2VHfCcCQb5 for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 01:26:57 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0141.outbound.protection.outlook.com [207.46.100.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19FB91A874B for <rtgwg@ietf.org>; Fri, 20 Feb 2015 01:26:57 -0800 (PST)
Received: from hannes-mba.local (193.110.55.10) by BN1PR05MB439.namprd05.prod.outlook.com (10.141.58.22) with Microsoft SMTP Server (TLS) id 15.1.81.19; Fri, 20 Feb 2015 09:26:55 +0000
Received: from hannes-mba.local (localhost [IPv6:::1]) by hannes-mba.local (Postfix) with ESMTP id 37E9BF048F5; Fri, 20 Feb 2015 10:26:46 +0100 (CET)
Date: Fri, 20 Feb 2015 10:26:46 +0100
From: Hannes Gredler <hannes@juniper.net>
To: Anton Smirnov <asmirnov@cisco.com>
Subject: Re: LFA manageability : per AF config => feedback required
Message-ID: <20150220092646.GB77308@hannes-mba.local>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <54E6FB8F.8000601@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <54E6FB8F.8000601@cisco.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Originating-IP: [193.110.55.10]
X-ClientProxiedBy: DB4PR06CA0042.eurprd06.prod.outlook.com (25.160.40.170) To BN1PR05MB439.namprd05.prod.outlook.com (10.141.58.22)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=hannes@juniper.net; 
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB439;
X-Microsoft-Antispam-PRVS: <BN1PR05MB4394E361958AAD3409862B0FA2A0@BN1PR05MB439.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005003); SRVR:BN1PR05MB439; 
X-Forefront-PRVS: 0493852DA9
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(199003)(479174004)(377454003)(40764003)(24454002)(83506001)(92566002)(87976001)(122386002)(40100003)(33656002)(98436002)(19580395003)(76176999)(19580405001)(76506005)(5890100001)(54356999)(50466002)(50986999)(122856001)(68736005)(47776003)(101416001)(86362001)(64706001)(97736003)(23676002)(105586002)(77096005)(46102003)(15975445007)(77156002)(66066001)(110136001)(2950100001)(62966003)(106356001)(579124003); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR05MB439; H:hannes-mba.local; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB439;
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 20 Feb 2015 09:26:55.6565 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN1PR05MB439
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/C9vVMhucwT4PDkidlVQpSI8bx4w>
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, 20 Feb 2015 09:26:59 -0000

hi anton, et al,

there is one more quirk to this:

i have never heard of _LDP_ adress families:

| >    o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,
| >       LDP IPv6 unicast ...
| >

so we're referring to something which does not exist - please see latest IANA registry:

http://www.iana.org/assignments/address-family-numbers/address-family-numbers.xhtml

/hannes

On Fri, Feb 20, 2015 at 10:17:03AM +0100, Anton Smirnov wrote:
|    Hi Stephane,
|    I think concern of "alternate nexthops consume resources in the
| forwarding plane" is generally a valid one. But if you want to solve *this*
| problem then solution is to give to operator great flexibility to select set
| of prefixes which are allowed to have protection and this flexibility should
| go beyond of just per-AF selection.
| 
|    Per-context selection would actually solve different problem - CPU
| resources needed to compute LFAs (which are spent per-topology independent
| of number of nexthops which end up being protected).
| 
|    So IMO per-AF granularity might be useful (especially in disjoint
| topologies) but reason given in the draft does not connect with the
| solution.
| 
| Anton
| 
| 
| On 02/20/2015 08:21 AM, stephane.litkowski@orange.com wrote:
| >Hi Folks,
| >
| >As you know, LFA manageability draft is in final phasis â€¦
| >
| >The current document states per AF granularity activation as a SHOULD.
| >
| >â€œ
| >
| >
| >      5.1
| >      <https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#section-5.1>.
| >      LFA enabling/disabling scope
| >
| >
| >
| >
| >
| >    The granularity of LFA activation should be controlled (as alternate
| >
| >    nexthop consume memory in forwarding plane).
| >
| >
| >
| >    An implementation of LFA SHOULD allow its activation with the
| >
| >    following criteria:
| >
| >
| >
| >    o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,
| >
| >       LDP IPv6 unicast ...
| >
| >
| >
| >    o  Per routing context : VRF, virtual/logical router, global routing
| >
| >       table, ...
| >
| >
| >
| >â€œ
| >
| >In the framework of ISIS/OSPF yang modelization, we are challenging this
| >statement, do we really need to force implementation to support this
| >â€œper AFâ€� granularity ?
| >
| >Please provide as soon as possible your feedback on this and also
| >provide clear drivers to support or not per AF activation of LFA.
| >
| >Thanks for your help !
| >
| >Orange logo <http://www.orange.com/>
| >
| >*Stephane Litkowski *
| >Network Architect
| >Orange/SCE/EQUANT/IBNF/ENDD/NDE
| >
| >Orange Expert Future Networks
| >
| >phone: +33 2 23 28 49 83
| ><https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20>
| >mobile: +33 6 37 86 97 52
| ><https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20>
| >stephane.litkowski@orange.com <mailto:stephane.litkowski@orange.com>
| >
| >_________________________________________________________________________________________________________________________
| >
| >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
| >
| 
| _______________________________________________
| rtgwg mailing list
| rtgwg@ietf.org
| https://www.ietf.org/mailman/listinfo/rtgwg


From nobody Fri Feb 20 02:36:42 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 D44A41A872B for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 02:36:40 -0800 (PST)
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 KG42LCdayKIT for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 02:36:33 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1527F1A1DE2 for <rtgwg@ietf.org>; Fri, 20 Feb 2015 02:36:33 -0800 (PST)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda11.si.francetelecom.fr (ESMTP service) with ESMTP id BDC1B1B8196; Fri, 20 Feb 2015 11:36:30 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.56]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id 94304C80BC; Fri, 20 Feb 2015 11:36:30 +0100 (CET)
Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.142]) by OPEXCLILH04.corporate.adroot.infra.ftgroup ([10.114.31.56]) with mapi id 14.03.0224.002; Fri, 20 Feb 2015 11:36:30 +0100
From: <stephane.litkowski@orange.com>
To: Jeff Tantsura <jeff.tantsura@ericsson.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AdBM3SH2oNl2urLXSA+s5ntM7pKOsP//0WCA//+Z0wA=
Date: Fri, 20 Feb 2015 10:36:29 +0000
Message-ID: <23625_1424428590_54E70E2E_23625_14638_1_9E32478DFA9976438E7A22F69B08FF9215C1401F@OPEXCLILM34.corporate.adroot.infra.ftgroup>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com>
In-Reply-To: <D10C20F9.8EB79%jeff.tantsura@ericsson.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: multipart/related; boundary="_004_9E32478DFA9976438E7A22F69B08FF9215C1401FOPEXCLILM34corp_"; type="multipart/alternative"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.2.20.20027
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/MFcx9huz-nvAGIHjunoKfLfgFYU>
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, 20 Feb 2015 10:36:41 -0000

--_004_9E32478DFA9976438E7A22F69B08FF9215C1401FOPEXCLILM34corp_
Content-Type: multipart/alternative;
	boundary="_000_9E32478DFA9976438E7A22F69B08FF9215C1401FOPEXCLILM34corp_"


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

Hi Jeff,

Thanks for your feedback.

In case of disjoined topology, this is another subject, it's per topology a=
ctivation, not really per AF.
Per topology activation is also mentioned in the draft as granularity.

Does it make sense ?

Best regards,


From: Jeff Tantsura [mailto:jeff.tantsura@ericsson.com]
Sent: Friday, February 20, 2015 08:30
To: LITKOWSKI Stephane SCE/IBNF; rtgwg@ietf.org
Subject: Re: LFA manageability : per AF config =3D> feedback required

Hi Stephane,

/chair hat off

IMO in disjoined topologies one should have flexibility to enable/disable L=
FA as per AF.


Cheers,
Jeff

From: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>"=
 <stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>
Date: Thursday, February 19, 2015 at 11:21 PM
To: "rtgwg@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ie=
tf.org>>
Subject: LFA manageability : per AF config =3D> feedback required

Hi Folks,

As you know, LFA manageability draft is in final phasis ...
The current document states per AF granularity activation as a SHOULD.
"
5.1<https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#secti=
on-5.1>.  LFA enabling/disabling scope





   The granularity of LFA activation should be controlled (as alternate

   nexthop consume memory in forwarding plane).



   An implementation of LFA SHOULD allow its activation with the

   following criteria:



   o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,

      LDP IPv6 unicast ...



   o  Per routing context : VRF, virtual/logical router, global routing

      table, ...


"

In the framework of ISIS/OSPF yang modelization, we are challenging this st=
atement, do we really need to force implementation to support this "per AF"=
 granularity ?

Please provide as soon as possible your feedback on this and also provide c=
lear drivers to support or not per AF activation of LFA.


Thanks for your help !


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/IBNF/ENDD/NDE
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>



___________________________________________________________________________=
______________________________________________



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_9E32478DFA9976438E7A22F69B08FF9215C1401FOPEXCLILM34corp_
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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:0in;
	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:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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.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";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Jeff,<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">Thanks for your feedba=
ck.<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 case of disjoined t=
opology, this is another subject, it&#8217;s per topology activation, not r=
eally per AF.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Per topology activatio=
n is also mentioned in the draft as granularity.<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">Does it make sense ?<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">Best regards,<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>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<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;"> Jeff Tan=
tsura [mailto:jeff.tantsura@ericsson.com]
<br>
<b>Sent:</b> Friday, February 20, 2015 08:30<br>
<b>To:</b> LITKOWSKI Stephane SCE/IBNF; rtgwg@ietf.org<br>
<b>Subject:</b> Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">Hi Stephane,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">/chair =
hat off<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">IMO in =
disjoined topologies one should have flexibility to enable/disable LFA as p=
er AF.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Cheers,=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Jeff<o:=
p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">&quot;<a href=3D"mailto:stephane.litkowski@orange.c=
om">stephane.litkowski@orange.com</a>&quot; &lt;<a href=3D"mailto:stephane.=
litkowski@orange.com">stephane.litkowski@orange.com</a>&gt;<br>
<b>Date: </b>Thursday, February 19, 2015 at 11:21 PM<br>
<b>To: </b>&quot;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&quot;=
 &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>LFA manageability : per AF config =3D&gt; feedback required=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<blockquote style=3D"border:none;border-left:solid #B5C4DF 4.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id=3D"MAC_OUTLOOK_ATTR=
IBUTION_BLOCKQUOTE">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Hi Folks,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">As you know, LFA managea=
bility draft is in final phasis &#8230;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">The current document sta=
tes per AF granularity activation as a SHOULD.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&#8220;<o:p></o:p></span=
></p>
<h3 style=3D"page-break-before:always"><a name=3D"section-5.1"></a><span st=
yle=3D"color:black"><a href=3D"https://tools.ietf.org/html/draft-ietf-rtgwg=
-lfa-manageability-07#section-5.1"><span lang=3D"EN" style=3D"font-size:10.=
0pt;color:black;text-decoration:none">5.1</span></a></span><span lang=3D"EN=
" style=3D"font-size:10.0pt;color:black">.&nbsp;
 LFA enabling/disabling scope</span><span style=3D"color:black"><o:p></o:p>=
</span></h3>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; The granularity of LFA activation should=
 be controlled (as alternate</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; nexthop consume memory in forwarding pla=
ne).</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; An implementation of LFA SHOULD allow it=
s activation with the</span><span style=3D"color:black"><o:p></o:p></span><=
/pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; following criteria:</span><span style=3D=
"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; o&nbsp; Per address-family : ipv4 unicas=
t, ipv6 unicast, LDP IPv4 unicast,</span><span style=3D"color:black"><o:p><=
/o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LDP IPv6 unicast ...</=
span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; o&nbsp; Per routing context : VRF, virtu=
al/logical router, global routing</span><span style=3D"color:black"><o:p></=
o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; table, ...</span><span=
 style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<p class=3D"MsoNormal"><span style=3D"color:black">&#8220;<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">In the framework of ISIS=
/OSPF yang modelization, we are challenging this statement, do we really ne=
ed to force implementation to support this &#8220;per AF&#8221; granularity=
 ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Please provide as soon a=
s possible your feedback on this and also provide clear drivers to support =
or not per AF activation of LFA.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Thanks for your help !<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black"><a href=3D"http://www.or=
ange.com/"><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;;text-decoration:none"><img border=3D"0" width=3D"=
40" height=3D"40" id=3D"Picture_x0020_1" src=3D"cid:image001.gif@01D04D01.7=
7A2FA20" alt=3D"Orange logo"></span></a><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;color:bl=
ack">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:black">Stephane Litkowski
</span></b><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Network Architect
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Orange/SCE/EQUANT/IBNF/ENDD/NDE
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Orange Expert Fut=
ure Networks</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<span style=3D"color:black;text-decoration:none">&#43;33 2 23 28 49 83 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;;color:black"><br>
</span><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:black">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<span style=3D"color:black;text-decoration:none">&#43;33 6 37 86 97 52 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;;color:black"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><span style=3D"font-size:1=
0.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#FF6600;te=
xt-decoration:none">stephane.litkowski@orange.com</span></a></span><span st=
yle=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span lang=3D"FR" style=
=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<pre><span style=3D"color:black">__________________________________________=
___________________________________________________________________________=
____<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Ce message et ses pieces jointes peuvent c=
ontenir des informations confidentielles ou privilegiees et ne doivent donc=
<o:p></o:p></span></pre>
<pre><span style=3D"color:black">pas etre diffuses, exploites ou copies san=
s autorisation. Si vous avez recu ce message par erreur, veuillez le signal=
er<o:p></o:p></span></pre>
<pre><span style=3D"color:black">a l'expediteur et le detruire ainsi que le=
s pieces jointes. Les messages electroniques etant susceptibles d'alteratio=
n,<o:p></o:p></span></pre>
<pre><span style=3D"color:black">Orange decline toute responsabilite si ce =
message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">This message and its attachments may conta=
in confidential or privileged information that may be protected by law;<o:p=
></o:p></span></pre>
<pre><span style=3D"color:black">they should not be distributed, used or co=
pied without authorisation.<o:p></o:p></span></pre>
<pre><span style=3D"color:black">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 style=3D"color:black">As emails may be altered, Orange is not li=
able for messages that have been modified, changed or falsified.<o:p></o:p>=
</span></pre>
<pre><span style=3D"color:black">Thank you.<o:p></o:p></span></pre>
</div>
</div>
</blockquote>
</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_9E32478DFA9976438E7A22F69B08FF9215C1401FOPEXCLILM34corp_--

--_004_9E32478DFA9976438E7A22F69B08FF9215C1401FOPEXCLILM34corp_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: inline; filename="image001.gif"; size=381;
	creation-date="Fri, 20 Feb 2015 10:36:29 GMT";
	modification-date="Fri, 20 Feb 2015 10:36:29 GMT"
Content-ID: <image001.gif@01D04D01.77A2FA20>
Content-Transfer-Encoding: base64

R0lGODlhKAAoAMQAAP+MQP+zgP/17//s3/+DMP/iz/+fYP+8j/9wEP95IP/Gn/+WUP/Pr/+pcP/Z
v/////9mAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAAA
AAAALAAAAAAoACgAAAX6oAONZGmeaEqKauum7Cu/8Wyj9a2P+X73vhkwSCPuhkYVMolj2pbOEjTK
oxatrSlVG+U6vUxwUmwkE81BtE99xGbdSjhMPgo4BAoA+wUICAR6IwQODwMNEAcOigAFhQYQDgoD
DwcQBJOKBIOFDQmaCCyTB416hQcBBQuTEA8Cow8EBQINpHcGhAkrEAkPChAAD3YPCLuSDw+sIgEP
wCILzK0OjY9VBJS/wYQjfwaNyRDLzRAG0AMB5wC6ENyEt8jWDAsCyA/KzJN+zLILqLlVv/OuaYPU
alU9cMwuPSCl8AEDYv8EQbwRgAEABcziJFl2bMmeEQgATEwRAgA7

--_004_9E32478DFA9976438E7A22F69B08FF9215C1401FOPEXCLILM34corp_--


From nobody Fri Feb 20 02:40:08 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 C092A1A883D for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 02:40:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-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 2CoKfyuGAxCg for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 02:40:05 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F22311A883C for <rtgwg@ietf.org>; Fri, 20 Feb 2015 02:40:04 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id BF87222C709; Fri, 20 Feb 2015 11:40:02 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.5]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 96CC74C08A; Fri, 20 Feb 2015 11:40:02 +0100 (CET)
Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.142]) by OPEXCLILH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0224.002; Fri, 20 Feb 2015 11:40:02 +0100
From: <stephane.litkowski@orange.com>
To: Hannes Gredler <hannes@juniper.net>, Anton Smirnov <asmirnov@cisco.com>
Subject: RE: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AdBM3SH2oNl2urLXSA+s5ntM7pKOsAACHlOAAABW4AAABJCIQA==
Date: Fri, 20 Feb 2015 10:40:01 +0000
Message-ID: <28764_1424428802_54E70F02_28764_4210_1_9E32478DFA9976438E7A22F69B08FF9215C1404A@OPEXCLILM34.corporate.adroot.infra.ftgroup>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <54E6FB8F.8000601@cisco.com> <20150220092646.GB77308@hannes-mba.local>
In-Reply-To: <20150220092646.GB77308@hannes-mba.local>
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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.2.20.20027
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/ihuEr-x3ngOfc3ssCgF84CrFRMw>
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, 20 Feb 2015 10:40:07 -0000

SGkgSGFubmVzLA0KDQpZb3UgYXJlIHJpZ2h0LCBtYXliZSB0aGUgdGV4dCBzaG91bGQgYmUgY2xh
cmlmaWVkLiBUbyBiZSBob25lc3QsIHRoaXMgdGV4dCBwYXJ0IGlzIG9sZCBhbmQgSSB0b29rIGEg
c2hvcnRjdXQgYW5kIG1peGluZyB0d28gdGhpbmdzIDopDQoNCkZpcnN0IHRoaW5nIGlzIHJlYWxs
eSBhIHBlciBBRiBhY3RpdmF0aW9uIChpcHY0IHVuaWNhc3QsIGlwdjYgdW5pY2FzdCAuLi4pLg0K
DQpUaGUgc2Vjb25kIGlzIGRvIEkgbmVlZCB0byBwcm90ZWN0ICJMRFAgcm91dGVzIiB0aGF0IGFy
ZSBpbmhlcml0aW5nIHNvbWUgSUdQIHByb3BlcnRpZXMgb3IgZG8gSSBjb25zaWRlciB0aGF0IExE
UCBpcyBwcm90ZWN0ZWQgYnkgc29tZXRoaW5nIGVsc2UgKFJTVlAtVEUgOikgKS4NCg0KQmVzdCBy
ZWdhcmRzLA0KDQpTdGVwaGFuZQ0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9t
OiBIYW5uZXMgR3JlZGxlciBbbWFpbHRvOmhhbm5lc0BqdW5pcGVyLm5ldF0gDQpTZW50OiBGcmlk
YXksIEZlYnJ1YXJ5IDIwLCAyMDE1IDEwOjI3DQpUbzogQW50b24gU21pcm5vdg0KQ2M6IExJVEtP
V1NLSSBTdGVwaGFuZSBTQ0UvSUJORjsgcnRnd2dAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBMRkEg
bWFuYWdlYWJpbGl0eSA6IHBlciBBRiBjb25maWcgPT4gZmVlZGJhY2sgcmVxdWlyZWQNCg0KaGkg
YW50b24sIGV0IGFsLA0KDQp0aGVyZSBpcyBvbmUgbW9yZSBxdWlyayB0byB0aGlzOg0KDQppIGhh
dmUgbmV2ZXIgaGVhcmQgb2YgX0xEUF8gYWRyZXNzIGZhbWlsaWVzOg0KDQp8ID4gICAgbyAgUGVy
IGFkZHJlc3MtZmFtaWx5IDogaXB2NCB1bmljYXN0LCBpcHY2IHVuaWNhc3QsIExEUCBJUHY0IHVu
aWNhc3QsDQp8ID4gICAgICAgTERQIElQdjYgdW5pY2FzdCAuLi4NCnwgPg0KDQpzbyB3ZSdyZSBy
ZWZlcnJpbmcgdG8gc29tZXRoaW5nIHdoaWNoIGRvZXMgbm90IGV4aXN0IC0gcGxlYXNlIHNlZSBs
YXRlc3QgSUFOQSByZWdpc3RyeToNCg0KaHR0cDovL3d3dy5pYW5hLm9yZy9hc3NpZ25tZW50cy9h
ZGRyZXNzLWZhbWlseS1udW1iZXJzL2FkZHJlc3MtZmFtaWx5LW51bWJlcnMueGh0bWwNCg0KL2hh
bm5lcw0KDQpPbiBGcmksIEZlYiAyMCwgMjAxNSBhdCAxMDoxNzowM0FNICswMTAwLCBBbnRvbiBT
bWlybm92IHdyb3RlOg0KfCAgICBIaSBTdGVwaGFuZSwNCnwgICAgSSB0aGluayBjb25jZXJuIG9m
ICJhbHRlcm5hdGUgbmV4dGhvcHMgY29uc3VtZSByZXNvdXJjZXMgaW4gdGhlIA0KfCBmb3J3YXJk
aW5nIHBsYW5lIiBpcyBnZW5lcmFsbHkgYSB2YWxpZCBvbmUuIEJ1dCBpZiB5b3Ugd2FudCB0byBz
b2x2ZSANCnwgKnRoaXMqIHByb2JsZW0gdGhlbiBzb2x1dGlvbiBpcyB0byBnaXZlIHRvIG9wZXJh
dG9yIGdyZWF0IGZsZXhpYmlsaXR5IA0KfCB0byBzZWxlY3Qgc2V0IG9mIHByZWZpeGVzIHdoaWNo
IGFyZSBhbGxvd2VkIHRvIGhhdmUgcHJvdGVjdGlvbiBhbmQgDQp8IHRoaXMgZmxleGliaWxpdHkg
c2hvdWxkIGdvIGJleW9uZCBvZiBqdXN0IHBlci1BRiBzZWxlY3Rpb24uDQp8IA0KfCAgICBQZXIt
Y29udGV4dCBzZWxlY3Rpb24gd291bGQgYWN0dWFsbHkgc29sdmUgZGlmZmVyZW50IHByb2JsZW0g
LSBDUFUgDQp8IHJlc291cmNlcyBuZWVkZWQgdG8gY29tcHV0ZSBMRkFzICh3aGljaCBhcmUgc3Bl
bnQgcGVyLXRvcG9sb2d5IA0KfCBpbmRlcGVuZGVudCBvZiBudW1iZXIgb2YgbmV4dGhvcHMgd2hp
Y2ggZW5kIHVwIGJlaW5nIHByb3RlY3RlZCkuDQp8IA0KfCAgICBTbyBJTU8gcGVyLUFGIGdyYW51
bGFyaXR5IG1pZ2h0IGJlIHVzZWZ1bCAoZXNwZWNpYWxseSBpbiBkaXNqb2ludA0KfCB0b3BvbG9n
aWVzKSBidXQgcmVhc29uIGdpdmVuIGluIHRoZSBkcmFmdCBkb2VzIG5vdCBjb25uZWN0IHdpdGgg
dGhlIA0KfCBzb2x1dGlvbi4NCnwgDQp8IEFudG9uDQp8IA0KfCANCnwgT24gMDIvMjAvMjAxNSAw
ODoyMSBBTSwgc3RlcGhhbmUubGl0a293c2tpQG9yYW5nZS5jb20gd3JvdGU6DQp8ID5IaSBGb2xr
cywNCnwgPg0KfCA+QXMgeW91IGtub3csIExGQSBtYW5hZ2VhYmlsaXR5IGRyYWZ0IGlzIGluIGZp
bmFsIHBoYXNpcyDigKYNCnwgPg0KfCA+VGhlIGN1cnJlbnQgZG9jdW1lbnQgc3RhdGVzIHBlciBB
RiBncmFudWxhcml0eSBhY3RpdmF0aW9uIGFzIGEgU0hPVUxELg0KfCA+DQp8ID7igJwNCnwgPg0K
fCA+DQp8ID4gICAgICA1LjENCnwgPiAgICAgIDxodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQtaWV0Zi1ydGd3Zy1sZmEtbWFuYWdlYWJpbGl0eS0wNyNzZWN0aW9uLTUuMT4uDQp8ID4g
ICAgICBMRkEgZW5hYmxpbmcvZGlzYWJsaW5nIHNjb3BlDQp8ID4NCnwgPg0KfCA+DQp8ID4NCnwg
Pg0KfCA+ICAgIFRoZSBncmFudWxhcml0eSBvZiBMRkEgYWN0aXZhdGlvbiBzaG91bGQgYmUgY29u
dHJvbGxlZCAoYXMgDQp8ID4gYWx0ZXJuYXRlDQp8ID4NCnwgPiAgICBuZXh0aG9wIGNvbnN1bWUg
bWVtb3J5IGluIGZvcndhcmRpbmcgcGxhbmUpLg0KfCA+DQp8ID4NCnwgPg0KfCA+ICAgIEFuIGlt
cGxlbWVudGF0aW9uIG9mIExGQSBTSE9VTEQgYWxsb3cgaXRzIGFjdGl2YXRpb24gd2l0aCB0aGUN
CnwgPg0KfCA+ICAgIGZvbGxvd2luZyBjcml0ZXJpYToNCnwgPg0KfCA+DQp8ID4NCnwgPiAgICBv
ICBQZXIgYWRkcmVzcy1mYW1pbHkgOiBpcHY0IHVuaWNhc3QsIGlwdjYgdW5pY2FzdCwgTERQIElQ
djQgDQp8ID4gdW5pY2FzdCwNCnwgPg0KfCA+ICAgICAgIExEUCBJUHY2IHVuaWNhc3QgLi4uDQp8
ID4NCnwgPg0KfCA+DQp8ID4gICAgbyAgUGVyIHJvdXRpbmcgY29udGV4dCA6IFZSRiwgdmlydHVh
bC9sb2dpY2FsIHJvdXRlciwgZ2xvYmFsIA0KfCA+IHJvdXRpbmcNCnwgPg0KfCA+ICAgICAgIHRh
YmxlLCAuLi4NCnwgPg0KfCA+DQp8ID4NCnwgPuKAnA0KfCA+DQp8ID5JbiB0aGUgZnJhbWV3b3Jr
IG9mIElTSVMvT1NQRiB5YW5nIG1vZGVsaXphdGlvbiwgd2UgYXJlIGNoYWxsZW5naW5nIA0KfCA+
dGhpcyBzdGF0ZW1lbnQsIGRvIHdlIHJlYWxseSBuZWVkIHRvIGZvcmNlIGltcGxlbWVudGF0aW9u
IHRvIHN1cHBvcnQgDQp8ID50aGlzIOKAnHBlciBBRuKAnSBncmFudWxhcml0eSA/DQp8ID4NCnwg
PlBsZWFzZSBwcm92aWRlIGFzIHNvb24gYXMgcG9zc2libGUgeW91ciBmZWVkYmFjayBvbiB0aGlz
IGFuZCBhbHNvIA0KfCA+cHJvdmlkZSBjbGVhciBkcml2ZXJzIHRvIHN1cHBvcnQgb3Igbm90IHBl
ciBBRiBhY3RpdmF0aW9uIG9mIExGQS4NCnwgPg0KfCA+VGhhbmtzIGZvciB5b3VyIGhlbHAgIQ0K
fCA+DQp8ID5PcmFuZ2UgbG9nbyA8aHR0cDovL3d3dy5vcmFuZ2UuY29tLz4NCnwgPg0KfCA+KlN0
ZXBoYW5lIExpdGtvd3NraSAqDQp8ID5OZXR3b3JrIEFyY2hpdGVjdA0KfCA+T3JhbmdlL1NDRS9F
UVVBTlQvSUJORi9FTkREL05ERQ0KfCA+DQp8ID5PcmFuZ2UgRXhwZXJ0IEZ1dHVyZSBOZXR3b3Jr
cw0KfCA+DQp8ID5waG9uZTogKzMzIDIgMjMgMjggNDkgODMNCnwgPjxodHRwczovL21vbnNpLnNz
by5mcmFuY2V0ZWxlY29tLmZyL2luZGV4LmFzcD90YXJnZXQ9aHR0cCUzQSUyRiUyRmNsaQ0KfCA+
Y3ZvaWNlLnNzby5mcmFuY2V0ZWxlY29tLmZyJTJGQ2xpY3ZvaWNlVjIlMkZUb29sQmFyLmRvJTNG
YWN0aW9uJTNEZGVmDQp8ID5hdWx0JTI2cm9vdHNlcnZpY2UlM0RTSUdOQVRVUkUlMjZ0byUzRCsz
MyUyMDIlMjAyMyUyMDI4JTIwNDklMjA4MyUyMD4NCnwgPm1vYmlsZTogKzMzIDYgMzcgODYgOTcg
NTINCnwgPjxodHRwczovL21vbnNpLnNzby5mcmFuY2V0ZWxlY29tLmZyL2luZGV4LmFzcD90YXJn
ZXQ9aHR0cCUzQSUyRiUyRmNsaQ0KfCA+Y3ZvaWNlLnNzby5mcmFuY2V0ZWxlY29tLmZyJTJGQ2xp
Y3ZvaWNlVjIlMkZUb29sQmFyLmRvJTNGYWN0aW9uJTNEZGVmDQp8ID5hdWx0JTI2cm9vdHNlcnZp
Y2UlM0RTSUdOQVRVUkUlMjZ0byUzRCszMyUyMDYlMjAzNyUyMDg2JTIwOTclMjA1MiUyMD4NCnwg
PnN0ZXBoYW5lLmxpdGtvd3NraUBvcmFuZ2UuY29tIDxtYWlsdG86c3RlcGhhbmUubGl0a293c2tp
QG9yYW5nZS5jb20+DQp8ID4NCnwgPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KfCA+X19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KfCA+DQp8ID5DZSBtZXNzYWdlIGV0
IHNlcyBwaWVjZXMgam9pbnRlcyBwZXV2ZW50IGNvbnRlbmlyIGRlcyBpbmZvcm1hdGlvbnMgDQp8
ID5jb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVzIGV0IG5lIGRvaXZlbnQgZG9uYyBwYXMg
ZXRyZSBkaWZmdXNlcywgDQp8ID5leHBsb2l0ZXMgb3UgY29waWVzIHNhbnMgYXV0b3Jpc2F0aW9u
LiBTaSB2b3VzIGF2ZXogcmVjdSBjZSBtZXNzYWdlIA0KfCA+cGFyIGVycmV1ciwgdmV1aWxsZXog
bGUgc2lnbmFsZXIgYSBsJ2V4cGVkaXRldXIgZXQgbGUgZGV0cnVpcmUgYWluc2kgcXVlIGxlcyBw
aWVjZXMgam9pbnRlcy4gTGVzIG1lc3NhZ2VzIGVsZWN0cm9uaXF1ZXMgZXRhbnQgc3VzY2VwdGli
bGVzIGQnYWx0ZXJhdGlvbiwgT3JhbmdlIGRlY2xpbmUgdG91dGUgcmVzcG9uc2FiaWxpdGUgc2kg
Y2UgbWVzc2FnZSBhIGV0ZSBhbHRlcmUsIGRlZm9ybWUgb3UgZmFsc2lmaWUuIE1lcmNpLg0KfCA+
DQp8ID5UaGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBjb25maWRl
bnRpYWwgb3IgDQp8ID5wcml2aWxlZ2VkIGluZm9ybWF0aW9uIHRoYXQgbWF5IGJlIHByb3RlY3Rl
ZCBieSBsYXc7IHRoZXkgc2hvdWxkIG5vdCBiZSBkaXN0cmlidXRlZCwgdXNlZCBvciBjb3BpZWQg
d2l0aG91dCBhdXRob3Jpc2F0aW9uLg0KfCA+SWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFp
bCBpbiBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBtZXNz
YWdlIGFuZCBpdHMgYXR0YWNobWVudHMuDQp8ID5BcyBlbWFpbHMgbWF5IGJlIGFsdGVyZWQsIE9y
YW5nZSBpcyBub3QgbGlhYmxlIGZvciBtZXNzYWdlcyB0aGF0IGhhdmUgYmVlbiBtb2RpZmllZCwg
Y2hhbmdlZCBvciBmYWxzaWZpZWQuDQp8ID5UaGFuayB5b3UuDQp8ID4NCnwgPg0KfCA+DQp8ID5f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KfCA+cnRnd2cg
bWFpbGluZyBsaXN0DQp8ID5ydGd3Z0BpZXRmLm9yZw0KfCA+aHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9ydGd3Zw0KfCA+DQp8IA0KfCBfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KfCBydGd3ZyBtYWlsaW5nIGxpc3QNCnwgcnRnd2dA
aWV0Zi5vcmcNCnwgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9ydGd3Zw0K
Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18KCkNlIG1lc3NhZ2UgZXQgc2VzIHBpZWNlcyBqb2ludGVzIHBldXZlbnQgY29udGVu
aXIgZGVzIGluZm9ybWF0aW9ucyBjb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVzIGV0IG5l
IGRvaXZlbnQgZG9uYwpwYXMgZXRyZSBkaWZmdXNlcywgZXhwbG9pdGVzIG91IGNvcGllcyBzYW5z
IGF1dG9yaXNhdGlvbi4gU2kgdm91cyBhdmV6IHJlY3UgY2UgbWVzc2FnZSBwYXIgZXJyZXVyLCB2
ZXVpbGxleiBsZSBzaWduYWxlcgphIGwnZXhwZWRpdGV1ciBldCBsZSBkZXRydWlyZSBhaW5zaSBx
dWUgbGVzIHBpZWNlcyBqb2ludGVzLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25pcXVlcyBldGFudCBz
dXNjZXB0aWJsZXMgZCdhbHRlcmF0aW9uLApPcmFuZ2UgZGVjbGluZSB0b3V0ZSByZXNwb25zYWJp
bGl0ZSBzaSBjZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBmYWxzaWZpZS4gTWVy
Y2kuCgpUaGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBjb25maWRl
bnRpYWwgb3IgcHJpdmlsZWdlZCBpbmZvcm1hdGlvbiB0aGF0IG1heSBiZSBwcm90ZWN0ZWQgYnkg
bGF3Owp0aGV5IHNob3VsZCBub3QgYmUgZGlzdHJpYnV0ZWQsIHVzZWQgb3IgY29waWVkIHdpdGhv
dXQgYXV0aG9yaXNhdGlvbi4KSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJv
ciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBtZXNzYWdlIGFuZCBp
dHMgYXR0YWNobWVudHMuCkFzIGVtYWlscyBtYXkgYmUgYWx0ZXJlZCwgT3JhbmdlIGlzIG5vdCBs
aWFibGUgZm9yIG1lc3NhZ2VzIHRoYXQgaGF2ZSBiZWVuIG1vZGlmaWVkLCBjaGFuZ2VkIG9yIGZh
bHNpZmllZC4KVGhhbmsgeW91LgoK


From nobody Fri Feb 20 02:43:06 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 1D5031A882C for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 02:43:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-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 bPETUaVPufyl for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 02:43:03 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F9531A882B for <rtgwg@ietf.org>; Fri, 20 Feb 2015 02:43:02 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 3A73B3B44DE; Fri, 20 Feb 2015 11:43:01 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.30]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 158D64C06B; Fri, 20 Feb 2015 11:43:01 +0100 (CET)
Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.142]) by OPEXCLILH02.corporate.adroot.infra.ftgroup ([10.114.31.30]) with mapi id 14.03.0224.002; Fri, 20 Feb 2015 11:43:00 +0100
From: <stephane.litkowski@orange.com>
To: Anton Smirnov <asmirnov@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AdBM3SH2oNl2urLXSA+s5ntM7pKOsAACHlOAAAUAWcA=
Date: Fri, 20 Feb 2015 10:43:01 +0000
Message-ID: <28764_1424428981_54E70FB5_28764_4382_1_9E32478DFA9976438E7A22F69B08FF9215C14080@OPEXCLILM34.corporate.adroot.infra.ftgroup>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <54E6FB8F.8000601@cisco.com>
In-Reply-To: <54E6FB8F.8000601@cisco.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.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.2.20.20027
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/VadGJ0v-X3jD9lGICjS-FSL56b0>
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, 20 Feb 2015 10:43:05 -0000

Hi Anton,

As I replied to Jeff, in case of disjoint topologies, we are no more relate=
d to per AF activation but more to a per topology activation which is diffe=
rent.

Regarding the "per-prefix" control, this is also proposed in the draft. Per=
-AF was added in order to have a simple mechanism to exclude a family of pr=
efixes (sort of subset of per prefix).

Best Regards,

Stephane


-----Original Message-----
From: Anton Smirnov [mailto:asmirnov@cisco.com]=20
Sent: Friday, February 20, 2015 10:17
To: LITKOWSKI Stephane SCE/IBNF; rtgwg@ietf.org
Subject: Re: LFA manageability : per AF config =3D> feedback required

    Hi Stephane,
    I think concern of "alternate nexthops consume resources in the forward=
ing plane" is generally a valid one. But if you want to solve
*this* problem then solution is to give to operator great flexibility to se=
lect set of prefixes which are allowed to have protection and this flexibil=
ity should go beyond of just per-AF selection.

    Per-context selection would actually solve different problem - CPU reso=
urces needed to compute LFAs (which are spent per-topology independent of n=
umber of nexthops which end up being protected).

    So IMO per-AF granularity might be useful (especially in disjoint
topologies) but reason given in the draft does not connect with the solutio=
n.

Anton


On 02/20/2015 08:21 AM, stephane.litkowski@orange.com wrote:
> Hi Folks,
>
> As you know, LFA manageability draft is in final phasis ...
>
> The current document states per AF granularity activation as a SHOULD.
>
> "
>
>
>       5.1
>       <https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#=
section-5.1>.
>       LFA enabling/disabling scope
>
>
>
>
>
>     The granularity of LFA activation should be controlled (as=20
> alternate
>
>     nexthop consume memory in forwarding plane).
>
>
>
>     An implementation of LFA SHOULD allow its activation with the
>
>     following criteria:
>
>
>
>     o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4=20
> unicast,
>
>        LDP IPv6 unicast ...
>
>
>
>     o  Per routing context : VRF, virtual/logical router, global=20
> routing
>
>        table, ...
>
>
>
> "
>
> In the framework of ISIS/OSPF yang modelization, we are challenging=20
> this statement, do we really need to force implementation to support=20
> this "per AF" granularity ?
>
> Please provide as soon as possible your feedback on this and also=20
> provide clear drivers to support or not per AF activation of LFA.
>
> Thanks for your help !
>
> Orange logo <http://www.orange.com/>
>
> *Stephane Litkowski *
> Network Architect
> Orange/SCE/EQUANT/IBNF/ENDD/NDE
>
> Orange Expert Future Networks
>
> phone: +33 2 23 28 49 83
> <https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F%2Fclic
> voice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefau
> lt%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20>
> mobile: +33 6 37 86 97 52
> <https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F%2Fclic
> voice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefau
> lt%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20>
> stephane.litkowski@orange.com <mailto:stephane.litkowski@orange.com>
>
> ______________________________________________________________________
> ___________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations=20
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses,=20
> exploites ou copies sans autorisation. Si vous avez recu ce message=20
> par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que =
les pieces jointes. Les messages electroniques etant susceptibles d'alterat=
ion, Orange decline toute responsabilite si ce message a ete altere, deform=
e ou falsifie. Merci.
>
> This message and its attachments may contain confidential or=20
> privileged information that may be protected by law; they should not be d=
istributed, 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
>

___________________________________________________________________________=
______________________________________________

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 Feb 20 03:28:21 2015
Return-Path: <psarkar@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 B580E1A1BB3 for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 03:28:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level: 
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_84=0.6, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 xMZPLKZSKcV1 for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 03:28:16 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0102.outbound.protection.outlook.com [65.55.169.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 366341A037E for <rtgwg@ietf.org>; Fri, 20 Feb 2015 03:28:12 -0800 (PST)
Received: from BY1PR0501MB1240.namprd05.prod.outlook.com (25.160.200.139) by BY1PR0501MB1239.namprd05.prod.outlook.com (25.160.200.13) with Microsoft SMTP Server (TLS) id 15.1.87.18; Fri, 20 Feb 2015 11:28:10 +0000
Received: from BY1PR0501MB1240.namprd05.prod.outlook.com ([25.160.200.139]) by BY1PR0501MB1240.namprd05.prod.outlook.com ([25.160.200.139]) with mapi id 15.01.0087.013; Fri, 20 Feb 2015 11:28:09 +0000
From: Pushpasis Sarkar <psarkar@juniper.net>
To: Jeff Tantsura <jeff.tantsura@ericsson.com>, "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AQHQTQBNBq/j0INnIEmx2R0yGZwTWA==
Date: Fri, 20 Feb 2015 11:28:09 +0000
Message-ID: <D10D0F95.20C04%psarkar@juniper.net>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com>
In-Reply-To: <D10C20F9.8EB79%jeff.tantsura@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-originating-ip: [116.197.184.14]
authentication-results: spf=none (sender IP is ) smtp.mailfrom=psarkar@juniper.net; 
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1239;
x-microsoft-antispam-prvs: <BY1PR0501MB1239AD0B07908A1EEC09E40EBB2A0@BY1PR0501MB1239.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1239; 
x-forefront-prvs: 0493852DA9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(189002)(40764003)(377454003)(199003)(19300405004)(64706001)(15975445007)(2900100001)(2950100001)(122556002)(36756003)(19625215002)(102836002)(46102003)(92566002)(66066001)(40100003)(68736005)(5890100001)(19613025002)(101416001)(76176999)(54356999)(97736003)(50986999)(99286002)(83506001)(107886001)(19618635001)(2656002)(87936001)(19627595001)(19617315012)(62966003)(106116001)(77156002)(19580405001)(106356001)(105586002)(99936001)(19580395003)(17760045003)(2501002)(16236675004)(2201001)(86362001)(18206015028); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1239; H:BY1PR0501MB1240.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
Content-Type: multipart/mixed; boundary="_004_D10D0F9520C04psarkarjunipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Feb 2015 11:28:09.5337 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0501MB1239
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/xlhHg7o4dhai6i7UccesQHDeCmg>
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, 20 Feb 2015 11:28:19 -0000

--_004_D10D0F9520C04psarkarjunipernet_
Content-Type: multipart/alternative;
	boundary="_000_D10D0F9520C04psarkarjunipernet_"

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

HI Jeff et al,

I can think of a reason to have a knob per-level(or per-area) or per ISIS t=
opology(note in ISIS a topology in ISIS always corresponds to a single AF,)=
 and per realm and topology in OSPF. But I cannot think of a reason of why =
within the same topology we need another set of knobs for each AF. Here, by=
 AF I understand IPV4 or IPv6.

When both IPV4 and IPV6 are part of the same IGP topology, there is only on=
e set of backup computations needed to protect both IPV4 and IPv6 traffic.

Also I cannot think of any motivation for an operator to turn on protection=
 on only one AF and does not want to turn on for the other even if both AFs=
 has been deployed for normal forwarding.

Thanks
-Pushpasis

From: Jeff Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericss=
on.com>>
Date: Friday, February 20, 2015 at 12:59 PM
To: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>" <=
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, "rtgw=
g@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: Re: LFA manageability : per AF config =3D> feedback required

Hi Stephane,

/chair hat off

IMO in disjoined topologies one should have flexibility to enable/disable L=
FA as per AF.


Cheers,
Jeff

From: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>"=
 <stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>
Date: Thursday, February 19, 2015 at 11:21 PM
To: "rtgwg@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ie=
tf.org>>
Subject: LFA manageability : per AF config =3D> feedback required

Hi Folks,

As you know, LFA manageability draft is in final phasis ...
The current document states per AF granularity activation as a SHOULD.
"
5.1<https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#secti=
on-5.1>.  LFA enabling/disabling scope





   The granularity of LFA activation should be controlled (as alternate

   nexthop consume memory in forwarding plane).



   An implementation of LFA SHOULD allow its activation with the

   following criteria:



   o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,

      LDP IPv6 unicast ...



   o  Per routing context : VRF, virtual/logical router, global routing

      table, ...


"

In the framework of ISIS/OSPF yang modelization, we are challenging this st=
atement, do we really need to force implementation to support this "per AF"=
 granularity ?

Please provide as soon as possible your feedback on this and also provide c=
lear drivers to support or not per AF activation of LFA.


Thanks for your help !


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/IBNF/ENDD/NDE
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>



___________________________________________________________________________=
______________________________________________

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_D10D0F9520C04psarkarjunipernet_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <A66D66CEB502034F911FD4D0A63E53BE@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>HI Jeff et al,</div>
<div><br>
</div>
<div>I can think of a reason to have a knob per-level(or per-area) or per I=
SIS topology(note in ISIS a topology in ISIS always corresponds to a single=
 AF,) and per realm and topology in OSPF. But I cannot think of a reason of=
 why within the same topology we
 need another set of knobs for each AF. Here, by AF I understand IPV4 or IP=
v6.</div>
<div><br>
</div>
<div>When both IPV4 and IPV6 are part of the same IGP topology, there is on=
ly one set of backup computations needed to protect both IPV4 and IPv6 traf=
fic.</div>
<div><br>
</div>
<div>Also I cannot think of any motivation for an operator to turn on prote=
ction on only one AF and does not want to turn on for the other even if bot=
h AFs has been deployed for normal forwarding.&nbsp;</div>
<div><br>
</div>
<div>Thanks</div>
<div>-Pushpasis</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Jeff Tantsura &lt;<a href=3D"=
mailto:jeff.tantsura@ericsson.com">jeff.tantsura@ericsson.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday, February 20, 2015 at =
12:59 PM<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:stephan=
e.litkowski@orange.com">stephane.litkowski@orange.com</a>&quot; &lt;<a href=
=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.com</a>=
&gt;, &quot;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&quot;
 &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: LFA manageability : pe=
r AF config =3D&gt; feedback required<br>
</div>
<div><br>
</div>
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;">
<div>
<div><font face=3D"Calibri,sans-serif">Hi Stephane,</font></div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
/chair hat off</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
IMO in disjoined topologies one should have flexibility to enable/disable L=
FA as per AF.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<div><span style=3D"font-family: Calibri; "><br>
</span></div>
<div><span style=3D"font-family: Calibri; ">Cheers,</span></div>
<div><font class=3D"Apple-style-span" color=3D"#000000"><font class=3D"Appl=
e-style-span" face=3D"Calibri">Jeff</font></font></div>
</div>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>&quot;<a href=3D"mailto:steph=
ane.litkowski@orange.com">stephane.litkowski@orange.com</a>&quot; &lt;<a hr=
ef=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.com</=
a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Thursday, February 19, 2015 a=
t 11:21 PM<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:rtgwg@i=
etf.org">rtgwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.org">rtg=
wg@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>LFA manageability : per AF=
 config =3D&gt; feedback required<br>
</div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:0in;
	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:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
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;
	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]-->
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Folks,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As you know, LFA manageability draft is in final pha=
sis &#8230;<o:p></o:p></p>
<p class=3D"MsoNormal">The current document states per AF granularity activ=
ation as a SHOULD.<o:p></o:p></p>
<p class=3D"MsoNormal">&#8220;<o:p></o:p></p>
<h3 style=3D"page-break-before:always"><a name=3D"section-5.1"></a><a href=
=3D"https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#secti=
on-5.1"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black;text-decora=
tion:none">5.1</span></a><span lang=3D"EN" style=3D"font-size:10.0pt">.&nbs=
p;
 LFA enabling/disabling scope<o:p></o:p></span></h3>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; The granularity of LFA activation should be controll=
ed (as alternate<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; nexthop consume memory in forwarding plane).<o:p></o=
:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; An implementation of LFA SHOULD allow its activation=
 with the<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; following criteria:<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; o&nbsp; Per address-family : ipv4 unicast, ipv6 unic=
ast, LDP IPv4 unicast,<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LDP IPv6 unicast ...<o:p></o:p></s=
pan></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp; o&nbsp; Per routing context : VRF, virtual/logical r=
outer, global routing<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; table, ...<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt"><o:p>&nbsp;</o:p></span></pre>
<p class=3D"MsoNormal">&#8220;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In the framework of ISIS/OSPF yang modelization, we =
are challenging this statement, do we really need to force implementation t=
o support this &#8220;per AF&#8221; granularity ?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please provide as soon as possible your feedback on =
this and also provide clear drivers to support or not per AF activation of =
LFA.<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">Thanks for your help !<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"><a href=3D"http://www.orange.com/"><span style=3D"fo=
nt-size: 12pt; font-family: 'Times New Roman', serif; color: blue; text-dec=
oration: none;"><img border=3D"0" width=3D"40" height=3D"40" id=3D"Picture_=
x0020_1" src=3D"cid:image001.gif@01D04CE5.FA95AFC0" alt=3D"Orange logo"></s=
pan></a><span lang=3D"FR" style=3D"font-size: 12pt; font-family: 'Times New=
 Roman', serif;"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e: 12pt; font-family: 'Times New Roman', serif;">&nbsp;<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Aria=
l, sans-serif; color: black;">Stephane Litkowski
</span></b><span style=3D"font-size: 12pt; font-family: 'Times New Roman', =
serif;"><br>
</span><span style=3D"font-size: 10pt; font-family: Arial, sans-serif; colo=
r: black;">Network Architect
</span><span style=3D"font-size: 12pt; font-family: 'Times New Roman', seri=
f;"><br>
</span><span style=3D"font-size: 10pt; font-family: Arial, sans-serif; colo=
r: black;">Orange/SCE/EQUANT/IBNF/ENDD/NDE
</span><span style=3D"font-size: 12pt; font-family: 'Times New Roman', seri=
f;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size: 10pt; font-fam=
ily: Arial, sans-serif; color: black;">Orange Expert Future Networks</span>=
<span lang=3D"FR" style=3D"font-size: 12pt; font-family: 'Times New Roman',=
 serif;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size: 10pt; font-fam=
ily: Arial, sans-serif; color: black;">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<span style=3D"color:black;text-decoration:none">&#43;33 2 23 28 49 83 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size: 12pt; font-family: 'Tim=
es New Roman', serif;"><br>
</span><span lang=3D"FR" style=3D"font-size: 10pt; font-family: Arial, sans=
-serif; color: black;">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<span style=3D"color:black;text-decoration:none">&#43;33 6 37 86 97 52 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size: 12pt; font-family: 'Tim=
es New Roman', serif;"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><span style=3D"font-size: =
10pt; font-family: Arial, sans-serif; color: rgb(255, 102, 0); text-decorat=
ion: none;">stephane.litkowski@orange.com</span></a><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span lang=3D"FR" style=
=3D"font-size: 12pt; font-family: 'Times New Roman', serif;">&nbsp;<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</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>
</div>
</div>
</blockquote>
</span></div>
</div>
</span>
</body>
</html>

--_000_D10D0F9520C04psarkarjunipernet_--

--_004_D10D0F9520C04psarkarjunipernet_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: attachment; filename="image001.gif"; size=381;
	creation-date="Fri, 20 Feb 2015 11:28:09 GMT";
	modification-date="Fri, 20 Feb 2015 11:28:09 GMT"
Content-ID: <image001.gif@01D04CE5.FA95AFC0>
Content-Transfer-Encoding: base64

R0lGODlhKAAoAMQAAP+MQP+zgP/17//s3/+DMP/iz/+fYP+8j/9wEP95IP/Gn/+WUP/Pr/+pcP/Z
v/////9mAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAAA
AAAALAAAAAAoACgAAAX6oAONZGmeaEqKauum7Cu/8Wyj9a2P+X73vhkwSCPuhkYVMolj2pbOEjTK
oxatrSlVG+U6vUxwUmwkE81BtE99xGbdSjhMPgo4BAoA+wUICAR6IwQODwMNEAcOigAFhQYQDgoD
DwcQBJOKBIOFDQmaCCyTB416hQcBBQuTEA8Cow8EBQINpHcGhAkrEAkPChAAD3YPCLuSDw+sIgEP
wCILzK0OjY9VBJS/wYQjfwaNyRDLzRAG0AMB5wC6ENyEt8jWDAsCyA/KzJN+zLILqLlVv/OuaYPU
alU9cMwuPSCl8AEDYv8EQbwRgAEABcziJFl2bMmeEQgATEwRAgA7

--_004_D10D0F9520C04psarkarjunipernet_--


From nobody Fri Feb 20 06:31:27 2015
Return-Path: <psarkar@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 3B0401A8AFE for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 06:31:24 -0800 (PST)
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 0lAwv9SuBOoE for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 06:31:17 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0111.outbound.protection.outlook.com [65.55.169.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DB3A1A037A for <rtgwg@ietf.org>; Fri, 20 Feb 2015 06:31:15 -0800 (PST)
Received: from BY1PR0501MB1240.namprd05.prod.outlook.com (25.160.200.139) by BY1PR0501MB1239.namprd05.prod.outlook.com (25.160.200.13) with Microsoft SMTP Server (TLS) id 15.1.87.18; Fri, 20 Feb 2015 14:31:12 +0000
Received: from BY1PR0501MB1240.namprd05.prod.outlook.com ([25.160.200.139]) by BY1PR0501MB1240.namprd05.prod.outlook.com ([25.160.200.139]) with mapi id 15.01.0087.013; Fri, 20 Feb 2015 14:31:12 +0000
From: Pushpasis Sarkar <psarkar@juniper.net>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: New Version Notification for draft-psarkar-rtgwg-multihomed-prefix-lfa-01.txt
Thread-Topic: New Version Notification for draft-psarkar-rtgwg-multihomed-prefix-lfa-01.txt
Thread-Index: AQHQTRngewTac9W0rUuELRMvToDIcg==
Date: Fri, 20 Feb 2015 14:31:12 +0000
Message-ID: <D10D42AC.20CAE%psarkar@juniper.net>
References: <20150220142915.16826.86855.idtracker@ietfa.amsl.com>
In-Reply-To: <20150220142915.16826.86855.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-originating-ip: [116.197.184.14]
authentication-results: spf=none (sender IP is ) smtp.mailfrom=psarkar@juniper.net; 
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1239;
x-microsoft-antispam-prvs: <BY1PR0501MB1239852FF7C62CA64B9CCB7EC12A0@BY1PR0501MB1239.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1239; 
x-forefront-prvs: 0493852DA9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(24454002)(51704005)(377454003)(199003)(377424004)(479174004)(53754006)(64706001)(2900100001)(102836002)(2950100001)(15975445007)(122556002)(36756003)(46102003)(1720100001)(66066001)(40100003)(92566002)(68736005)(2420400003)(101416001)(76176999)(54356999)(450100001)(97736003)(50986999)(99286002)(83506001)(230783001)(2351001)(107886001)(2656002)(87936001)(106116001)(62966003)(105586002)(77156002)(19580405001)(106356001)(19580395003)(110136001)(2501002)(86362001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1239; H:BY1PR0501MB1240.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B2D86B82222F7C48BA0788EF94FBAD35@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Feb 2015 14:31:12.3999 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0501MB1239
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/YU3jp2-eThX8RF3Nc44HXMZKoFE>
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, 20 Feb 2015 14:31:24 -0000

Hi Everyone,

Just posted an updated version with few additions. Request you all to
please review it and provide your valuable feedback.

Thanks and Regards,
-Pushpasis

On 2/20/15, 7:59 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
wrote:

>
>A new version of I-D, draft-psarkar-rtgwg-multihomed-prefix-lfa-01.txt
>has been successfully submitted by Pushpasis Sarkar and posted to the
>IETF repository.
>
>Name:		draft-psarkar-rtgwg-multihomed-prefix-lfa
>Revision:	01
>Title:		LFA selection for Multi-Homed Prefixes
>Document date:	2015-02-20
>Group:		Individual Submission
>Pages:		10
>URL:           =20
>http://www.ietf.org/internet-drafts/draft-psarkar-rtgwg-multihomed-prefix-
>lfa-01.txt
>Status:        =20
>https://datatracker.ietf.org/doc/draft-psarkar-rtgwg-multihomed-prefix-lfa
>/
>Htmlized:      =20
>http://tools.ietf.org/html/draft-psarkar-rtgwg-multihomed-prefix-lfa-01
>Diff:          =20
>http://www.ietf.org/rfcdiff?url2=3Ddraft-psarkar-rtgwg-multihomed-prefix-l=
fa
>-01
>
>Abstract:
>   This document shares experience gained from implementing algorithms
>   to determine Loop-Free Alternates for multi-homed prefixes.  In
>   particular, this document provides explicit inequalities that can be
>   used to evaluate neighbors as a potential alternates for multi-homed
>   prefixes.  It also provides detailed criteria for evaluating
>   potential alternates for external prefixes advertised by OSPF ASBRs.
>
>
>                 =20
>       =20
>
>
>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.
>
>The IETF Secretariat
>


From nobody Fri Feb 20 06:38:17 2015
Return-Path: <psarkar@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 159131A8AF8 for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 06:38:16 -0800 (PST)
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, 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 8YMBFgEWf8qG for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 06:38:09 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0774.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::774]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B63B81A883B for <rtgwg@ietf.org>; Fri, 20 Feb 2015 06:38:08 -0800 (PST)
Received: from BY1PR0501MB1240.namprd05.prod.outlook.com (25.160.200.139) by BY1PR0501MB1112.namprd05.prod.outlook.com (25.160.103.146) with Microsoft SMTP Server (TLS) id 15.1.87.18; Fri, 20 Feb 2015 14:37:50 +0000
Received: from BY1PR0501MB1240.namprd05.prod.outlook.com (25.160.200.139) by BY1PR0501MB1240.namprd05.prod.outlook.com (25.160.200.139) with Microsoft SMTP Server (TLS) id 15.1.87.18; Fri, 20 Feb 2015 14:37:47 +0000
Received: from BY1PR0501MB1240.namprd05.prod.outlook.com ([25.160.200.139]) by BY1PR0501MB1240.namprd05.prod.outlook.com ([25.160.200.139]) with mapi id 15.01.0087.013; Fri, 20 Feb 2015 14:37:47 +0000
From: Pushpasis Sarkar <psarkar@juniper.net>
To: Jeff Tantsura <jeff.tantsura@ericsson.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>
Subject: Re: RTGWG timeslots for Dallas
Thread-Topic: RTGWG timeslots for Dallas
Thread-Index: AQHQTRrLY9gy5eV1GkK7YhcB3dSUtg==
Date: Fri, 20 Feb 2015 14:37:47 +0000
Message-ID: <D10D4408.20CB8%psarkar@juniper.net>
References: <D106CE03.8E10D%jeff.tantsura@ericsson.com>
In-Reply-To: <D106CE03.8E10D%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.8.150116
x-originating-ip: [116.197.184.14]
authentication-results: spf=none (sender IP is ) smtp.mailfrom=psarkar@juniper.net; 
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1240;UriScan:;
x-microsoft-antispam-prvs: <BY1PR0501MB1240613D3B60098614341FB9FF2A0@BY1PR0501MB1240.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1240; 
x-forefront-prvs: 0493852DA9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(479174004)(41574002)(189002)(377454003)(199003)(51704005)(62966003)(106356001)(87936001)(99286002)(2656002)(68736005)(102836002)(2950100001)(2900100001)(77156002)(66066001)(105586002)(106116001)(122556002)(40100003)(36756003)(64706001)(97736003)(19580405001)(19580395003)(92566002)(101416001)(83506001)(46102003)(50986999)(76176999)(54356999)(86362001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1240; H:BY1PR0501MB1240.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EB7B146AF1195342AB6FEF7845B82146@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Feb 2015 14:37:47.4078 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0501MB1240
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1112;
X-OriginatorOrg: juniper.net
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/STtgIWfoYeJS_-kqpFLp17UeqCw>
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, 20 Feb 2015 14:38:16 -0000

Hi Jeff and Alvaro,

Request a slot for presenting an update on
draft-psarkar-rtgwg-multihomed-prefix-lfa-01.

Thanks
-Pushpasis

On 2/16/15, 11:58 AM, "Jeff Tantsura" <jeff.tantsura@ericsson.com> wrote:

>Hi RTGWG,
>
>IETF92 is approaching, please request a timeslot if you are planning to
>present, usual disclaimer applies - no draft/no time.
>
>Thanks!
>
>Cheers,
>Jeff
>
>


From nobody Fri Feb 20 06:46:49 2015
Return-Path: <psarkar@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 3BAA51A8791 for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 06:46:48 -0800 (PST)
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 27B4MkGtwgnL for <rtgwg@ietfa.amsl.com>; Fri, 20 Feb 2015 06:46:46 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0138.outbound.protection.outlook.com [207.46.100.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9F581A87A3 for <rtgwg@ietf.org>; Fri, 20 Feb 2015 06:46:36 -0800 (PST)
Received: from BY1PR0501MB1240.namprd05.prod.outlook.com (25.160.200.139) by BY1PR0501MB1238.namprd05.prod.outlook.com (25.160.200.12) with Microsoft SMTP Server (TLS) id 15.1.87.18; Fri, 20 Feb 2015 14:46:35 +0000
Received: from BY1PR0501MB1240.namprd05.prod.outlook.com ([25.160.200.139]) by BY1PR0501MB1240.namprd05.prod.outlook.com ([25.160.200.139]) with mapi id 15.01.0087.013; Fri, 20 Feb 2015 14:46:35 +0000
From: Pushpasis Sarkar <psarkar@juniper.net>
To: Jeff Tantsura <jeff.tantsura@ericsson.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>
Subject: Re: RTGWG timeslots for Dallas
Thread-Topic: RTGWG timeslots for Dallas
Thread-Index: AQHQTRwFpP9TymMhaEmD0H6IRThbGQ==
Date: Fri, 20 Feb 2015 14:46:34 +0000
Message-ID: <D10D465C.20CCA%psarkar@juniper.net>
References: <D106CE03.8E10D%jeff.tantsura@ericsson.com> <D10D4408.20CB8%psarkar@juniper.net>
In-Reply-To: <D10D4408.20CB8%psarkar@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-originating-ip: [116.197.184.14]
authentication-results: spf=none (sender IP is ) smtp.mailfrom=psarkar@juniper.net; 
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1238;
x-microsoft-antispam-prvs: <BY1PR0501MB1238DF4752624557A0ABC0E5FF2A0@BY1PR0501MB1238.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1238; 
x-forefront-prvs: 0493852DA9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(41574002)(51704005)(377454003)(199003)(24454002)(479174004)(189002)(99286002)(83506001)(2656002)(19580395003)(68736005)(92566002)(2950100001)(101416001)(19580405001)(87936001)(64706001)(86362001)(2900100001)(97736003)(54356999)(50986999)(76176999)(62966003)(77156002)(40100003)(106356001)(102836002)(122556002)(105586002)(106116001)(66066001)(36756003)(46102003); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1238; H:BY1PR0501MB1240.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <2B11AED10A8E1D448E2DEC8BBF39FBE8@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Feb 2015 14:46:34.9183 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0501MB1238
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/4fDKisufApAbYGM0w9BWNfgwPSU>
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, 20 Feb 2015 14:46:48 -0000

Forgot to mention=8A 10 min slot should be enough.. :)

On 2/20/15, 8:07 PM, "Pushpasis Sarkar" <psarkar@juniper.net> wrote:

>Hi Jeff and Alvaro,
>
>Request a slot for presenting an update on
>draft-psarkar-rtgwg-multihomed-prefix-lfa-01.
>
>Thanks
>-Pushpasis
>
>On 2/16/15, 11:58 AM, "Jeff Tantsura" <jeff.tantsura@ericsson.com> wrote:
>
>>Hi RTGWG,
>>
>>IETF92 is approaching, please request a timeslot if you are planning to
>>present, usual disclaimer applies - no draft/no time.
>>
>>Thanks!
>>
>>Cheers,
>>Jeff
>>
>>
>


From nobody Sun Feb 22 10:42:48 2015
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 509AA1A6EE0; Sun, 22 Feb 2015 10:42:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.788
X-Spam-Level: 
X-Spam-Status: No, score=0.788 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_HELO_PASS=-0.001, 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 qKW5S7q3nzuI; Sun, 22 Feb 2015 10:42:44 -0800 (PST)
Received: from maildrop31.somerville.occnc.com (maildrop31.somerville.occnc.com [IPv6:2001:550:3800:203::3131]) (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 060C01A039D; Sun, 22 Feb 2015 10:42:43 -0800 (PST)
Received: from harbor31.somerville.occnc.com (harbor31.somerville.occnc.com [IPv6:2001:550:3800:203::3231]) (authenticated bits=128) by maildrop31.somerville.occnc.com (8.14.9/8.14.9) with ESMTP id t1MIgTDI024468; Sun, 22 Feb 2015 13:42:29 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201502221842.t1MIgTDI024468@maildrop31.somerville.occnc.com>
To: curtis@ipv6.occnc.com
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: RtgDir review: draft-ietf-rtgwg-cl-use-cases-06.txt
In-reply-to: Your message of "Thu, 12 Feb 2015 10:02:15 -0500." <201502121502.t1CF2Ffd099176@maildrop31.somerville.occnc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <24466.1424630549.1@harbor31.somerville.occnc.com>
Date: Sun, 22 Feb 2015 13:42:29 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/CnB8OoA1VjfzgqMyj68QX0NYsIk>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "Joel M. Halpern" <jmh@joelhalpern.com>, "draft-ietf-rtgwg-cl-use-cases@tools.ietf.org" <draft-ietf-rtgwg-cl-use-cases@tools.ietf.org>, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>, "<rtgwg@ietf.org>" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Feb 2015 18:42:46 -0000

All,

Two weeks would be Feb 26, four days from now.

So far I've only heard from Ning (positive response).  Are the other
co-authors too disinterested to reply?  If so, perhaps at best the
author list needs to be pruned and some names moved to "contributor"
so we don't get hung up later in AUTH48.

At worst, we just say "never mind".  Still waiting to hear from Dave,
Lucy, and Andy.

Curtis


In message <201502121502.t1CF2Ffd099176@maildrop31.somerville.occnc.com>
Curtis Villamizar writes:
> 
> So far I got one message from a co-author and its not encouraging:
>  
>   ning.so@tatacommunications.com
>     (generated from draft-ietf-rtgwg-cl-use-cases@tools.ietf.org)
>     SMTP error from remote mail server \
>       after RCPT TO:<ning.so@tatacommunications.com>:
>     host mx5.tatacommunications.com [115.114.148.135]:
>     550 #5.1.0 Address rejected.
>  
> At best that counts as an address change at least temporarily to
> "unknown".
>  
> This has been idle for very long.  Lets give it a week or two and if
> no responses, then move use-cases and framework to abandoned state.
> If there is interest in the topic later, a new individual submission
> can be started (possibly just a framework) and the WG can decide if
> there is enough interest to make that new draft a WG item.
>  
> Curtis
>  
>  
> In message <D10108C4.8DB10%jeff.tantsura@ericsson.com>
> Jeff Tantsura writes:
> > 
> > Hi Curtis,
> >  
> > Please let me know how would you like to proceed with the draft.
> > If you feel it should progress and since Routing Directorate is done with
> > no issues found - please resubmit, I'll provide writeup and submit to the
> > IESG.
> >  
> > Thanks!
> >  
> > Cheers,
> > Jeff
> >  
> >  
> >  
> >  
> > -----Original Message-----
> > From: Curtis Villamizar <curtis@ipv6.occnc.com>
> > Reply-To: "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
> > Date: Wednesday, February 11, 2015 at 12:06 PM
> > To: Joel Halpern <jmh@joelhalpern.com>
> > Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "<rtgwg@ietf.org>"
> > <rtgwg@ietf.org>, "draft-ietf-rtgwg-cl-use-cases@tools.ietf.org"
> > <draft-ietf-rtgwg-cl-use-cases@tools.ietf.org>, "rtg-ads@tools.ietf.org"
> > <rtg-ads@tools.ietf.org>
> > Subject: Re: RtgDir review: draft-ietf-rtgwg-cl-use-cases-06.txt
> >  
> > >In message <54C2B86A.6010607@joelhalpern.com>
> > >"Joel M. Halpern" writes:
> > >> 
> > >> Hello,
> > >>  
> > >> I have been selected as the Routing Directorate reviewer for this
> > >>draft. 
> > >> The Routing Directorate seeks to review all routing or routing-related
> > >> drafts as they pass through IETF last call and IESG review, and
> > >> sometimes on special request. The purpose of the review is to provide
> > >> assistance to the Routing ADs. For more information about the Routing
> > >> Directorate, please see
> > >> http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir
> > >>  
> > >> Although these comments are primarily for the use of the Routing ADs,
> > >>it 
> > >> would be helpful if you could consider them along with any other IETF
> > >> Last Call comments that you receive, and strive to resolve them through
> > >> discussion or by updating the draft.
> > >>  
> > >> Document: draft-ietf-rtgwg-cl-use-cases-06.txt
> > >>      Advanced Multipath Use Cases and Design Considerations
> > >> Reviewer: Joel M. Halpern
> > >> Review Date: 23-January-2015
> > >> IETF LC End Date: N/A
> > >> Intended Status: Informational
> > >>  
> > >> Summary: No issues found. This document is ready for publication.
> > >>  
> > >> Minor note: This draft appears to have expired.
> > >
> > >
> > >Hello again Joel,
> > >
> > >FYI - to the Cc.  I emailed Joel off list about this.  This draft lay
> > >dormant in "AD review" for a long time.  Apparently the AD shepard had
> > >a change of heart about this .. or something.
> > >
> > >The draft itself could be described as inconsequential but contains
> > >parts of earlier CL requirements draft and CL framework that more
> > >closely resembled use cases.  This draft exists both to be
> > >informational and to unclutter the requirements and framework.
> > >
> > >At this point I can submit another draft.  But ...
> > >
> > >I would like to know from the co-authors two things:
> > >
> > >  1.  Is there still interest in CL aka Advanced Multipath?
> > >  2.  Any changes in contact information?
> > >
> > >I'm particularly interested in whether there is interest at Verizon
> > >since they were the potential user driving this in the first place.
> > >However two of the three Verizon co-authors to the CL drafts are no
> > >longer at Verizon.
> > >
> > >No further replies should be interpreted as "no interest" although an
> > >explicit "no interest" would be preferred if that is the case.
> > >
> > >If there is interest I'll resubmit this.  If there is still interest
> > >in the framework, we can resurrect that document as well but the
> > >framework needs work and discussion had fallen off to nothing by the
> > >time it expired.
> > >
> > >Curtis
> > >
> > >_______________________________________________
> > >rtgwg mailing list
> > >rtgwg@ietf.org
> > >https://www.ietf.org/mailman/listinfo/rtgwg


From nobody Sun Feb 22 20:01:00 2015
Return-Path: <ginsberg@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 A79A21A0163 for <rtgwg@ietfa.amsl.com>; Sun, 22 Feb 2015 20:00:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.21
X-Spam-Level: 
X-Spam-Status: No, score=-11.21 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, J_CHICKENPOX_84=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 KpAWQW1RCKJT for <rtgwg@ietfa.amsl.com>; Sun, 22 Feb 2015 20:00:54 -0800 (PST)
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 247801A00F0 for <rtgwg@ietf.org>; Sun, 22 Feb 2015 20:00:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=29062; q=dns/txt; s=iport; t=1424664054; x=1425873654; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=MY2ECydFLt6fekTSjO0HeVOIFfOjvSf6wr3SOZ+WSXo=; b=Gxpx5zN4O3u2oaSoQb3mSUrB87EAQ/pVP9bn25Lsg18frtalgavG3iJT uHAUpRQQdUL0lHn3ZgbZE+wd2W2JNYE4ShCl1qqAkiCYSFNY2D70y0BQ3 5VI3UGhexpGWT5waWh/AWMu2oxXoyhBQHyA6RjevTZbevah/QC2R8p1yN 0=;
X-Files: image001.gif : 381
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BLBQC9pOpU/4UNJK1bgkNDUloEwFOCOoVzAoEgQwEBAQEBAXyEDwEBAQQFIAgBNgccAgIBCAcHAwMBAQEGAQICFgcHAgUQAQMCCQwUCQgBAQQBEQEGAgaIDQMRDcx3A4U2AQEBAQEBAQEBAQEBAQEBAQEBAQEBFwSLD4FPgjQJEQEfBREKDAEKAQaDEYEUBYYVhA2DP4EnSoMNAVCHADiCXYtFgz4iggIcgVBvAQEBAYEHOX8BAQE
X-IronPort-AV: E=Sophos;i="5.09,629,1418083200";  d="gif'147?scan'147,208,217,147";a="125944806"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-2.cisco.com with ESMTP; 23 Feb 2015 04:00:52 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t1N40qj8018235 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 23 Feb 2015 04:00:52 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.138]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0195.001; Sun, 22 Feb 2015 22:00:52 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Pushpasis Sarkar <psarkar@juniper.net>, Jeff Tantsura <jeff.tantsura@ericsson.com>, "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AdBM3SH2oNl2urLXSA+s5ntM7pKOsP//0WCAgADZjID//DGyQA==
Date: Mon, 23 Feb 2015 04:00:51 +0000
Message-ID: <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net>
In-Reply-To: <D10D0F95.20C04%psarkar@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.24.29.122]
Content-Type: multipart/related; boundary="_004_F3ADE4747C9E124B89F0ED2180CC814F4EF2D78Fxmbalnx02ciscoc_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/sHmy2xmc_49wjnmm4-Ab6TgfwW8>
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, 23 Feb 2015 04:00:58 -0000

--_004_F3ADE4747C9E124B89F0ED2180CC814F4EF2D78Fxmbalnx02ciscoc_
Content-Type: multipart/alternative;
	boundary="_000_F3ADE4747C9E124B89F0ED2180CC814F4EF2D78Fxmbalnx02ciscoc_"

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

Pushpassis -

From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Pushpasis Sarkar
Sent: Friday, February 20, 2015 3:28 AM
To: Jeff Tantsura; stephane.litkowski@orange.com; rtgwg@ietf.org
Subject: Re: LFA manageability : per AF config =3D> feedback required

HI Jeff et al,

I can think of a reason to have a knob per-level(or per-area) or per ISIS t=
opology(note in ISIS a topology in ISIS always corresponds to a single AF,)

[Les:] This is a common mistake to make. If one simply uses RFC 5308, then =
IPv6 prefixes can be advertised in the same topology as IPv4 (MTID #0) - an=
d there are implementations which support this. More generally, from the pr=
otocol's POV a given topology can support any combinations of address famil=
ies. It is only a convention because of the reserved MTIDs specified in RFC=
 5120 that certain MTIDs are "IPv6 only". But if one looks at the protocol =
capabilities such a restriction does not exist in general.

Interestingly you contradicted yourself below. :)
But I did want to set the record straight on this point - hopefully we are =
in agreement.

and per realm and topology in OSPF. But I cannot think of a reason of why w=
ithin the same topology we need another set of knobs for each AF. Here, by =
AF I understand IPV4 or IPv6.

When both IPV4 and IPV6 are part of the same IGP topology, there is only on=
e set of backup computations needed to protect both IPV4 and IPv6 traffic.

Also I cannot think of any motivation for an operator to turn on protection=
 on only one AF and does not want to turn on for the other even if both AFs=
 has been deployed for normal forwarding.

[Les:] I think your point here is that the LFA calculation is AF independen=
t within a given topology - but resources are consumed independent of how m=
any computations are required- giving an operator the ability to determine =
which prefixes are most critical seems useful. That could be per AF or per =
prefix.

   Les

Thanks
-Pushpasis

From: Jeff Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericss=
on.com>>
Date: Friday, February 20, 2015 at 12:59 PM
To: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>" <=
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, "rtgw=
g@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: Re: LFA manageability : per AF config =3D> feedback required

Hi Stephane,

/chair hat off

IMO in disjoined topologies one should have flexibility to enable/disable L=
FA as per AF.


Cheers,
Jeff

From: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>"=
 <stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>
Date: Thursday, February 19, 2015 at 11:21 PM
To: "rtgwg@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ie=
tf.org>>
Subject: LFA manageability : per AF config =3D> feedback required

Hi Folks,

As you know, LFA manageability draft is in final phasis ...
The current document states per AF granularity activation as a SHOULD.
"
5.1<https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#secti=
on-5.1>.  LFA enabling/disabling scope





   The granularity of LFA activation should be controlled (as alternate

   nexthop consume memory in forwarding plane).



   An implementation of LFA SHOULD allow its activation with the

   following criteria:



   o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,

      LDP IPv6 unicast ...



   o  Per routing context : VRF, virtual/logical router, global routing

      table, ...


"

In the framework of ISIS/OSPF yang modelization, we are challenging this st=
atement, do we really need to force implementation to support this "per AF"=
 granularity ?

Please provide as soon as possible your feedback on this and also provide c=
lear drivers to support or not per AF activation of LFA.


Thanks for your help !


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/IBNF/ENDD/NDE
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>



___________________________________________________________________________=
______________________________________________



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_F3ADE4747C9E124B89F0ED2180CC814F4EF2D78Fxmbalnx02ciscoc_
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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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.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";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Pushpassis -<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 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>Pushpasis Sarkar<br>
<b>Sent:</b> Friday, February 20, 2015 3:28 AM<br>
<b>To:</b> Jeff Tantsura; stephane.litkowski@orange.com; rtgwg@ietf.org<br>
<b>Subject:</b> Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">HI Jeff=
 et al,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I can t=
hink of a reason to have a knob per-level(or per-area) or per ISIS topology=
(note in ISIS a topology in ISIS always corresponds to a single AF,)</span>=
<span style=3D"font-size:10.5pt;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] This is a=
 common mistake to make. If one simply uses RFC 5308, then IPv6 prefixes ca=
n be advertised in the same topology as IPv4 (MTID #0) &#8211; and there ar=
e implementations which support this. More
 generally, from the protocol&#8217;s POV a given topology can support any =
combinations of address families. It is only a convention because of the re=
served MTIDs specified in RFC 5120 that certain MTIDs are &#8220;IPv6 only&=
#8221;. But if one looks at the protocol capabilities
 such a restriction does not exist in general.<o:p></o:p></span></i></b></p=
>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">Interestingly yo=
u contradicted yourself below.
</span></i></b><b><i><span style=3D"font-family:Wingdings;color:#1F497D">J<=
/span></i></b><b><i><span style=3D"color:#1F497D"><o:p></o:p></span></i></b=
></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">But I did want t=
o set the record straight on this point &#8211; hopefully we are in agreeme=
nt.<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">and per=
 realm and topology in OSPF. But I cannot think of a reason of why within t=
he same topology we need another set of knobs for each AF. Here, by AF I un=
derstand IPV4 or IPv6.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">When bo=
th IPV4 and IPV6 are part of the same IGP topology, there is only one set o=
f backup computations needed to protect both IPV4 and IPv6 traffic.<o:p></o=
:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Also I =
cannot think of any motivation for an operator to turn on protection on onl=
y one AF and does not want to turn on for the other even if both AFs has be=
en deployed for normal forwarding.&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] I think y=
our point here is that the LFA calculation is AF independent within a given=
 topology &#8211; but resources are consumed independent of how many comput=
ations are required- giving an operator the
 ability to determine which prefixes are most critical seems useful. That c=
ould be per AF or per prefix.<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">&nbsp;&nbsp; Les=
<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Thanks<=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">-Pushpa=
sis<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">Jeff Tantsura &lt;<a href=3D"mailto:jeff.tantsura@e=
ricsson.com">jeff.tantsura@ericsson.com</a>&gt;<br>
<b>Date: </b>Friday, February 20, 2015 at 12:59 PM<br>
<b>To: </b>&quot;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.=
litkowski@orange.com</a>&quot; &lt;<a href=3D"mailto:stephane.litkowski@ora=
nge.com">stephane.litkowski@orange.com</a>&gt;, &quot;<a href=3D"mailto:rtg=
wg@ietf.org">rtgwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.org"=
>rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Hi Step=
hane,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">/chair =
hat off<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">IMO in =
disjoined topologies one should have flexibility to enable/disable LFA as p=
er AF.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Cheers,=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Jeff<o:=
p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">&quot;<a href=3D"mailto:stephane.litkowski@orange.c=
om">stephane.litkowski@orange.com</a>&quot; &lt;<a href=3D"mailto:stephane.=
litkowski@orange.com">stephane.litkowski@orange.com</a>&gt;<br>
<b>Date: </b>Thursday, February 19, 2015 at 11:21 PM<br>
<b>To: </b>&quot;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&quot;=
 &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>LFA manageability : per AF config =3D&gt; feedback required=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<blockquote style=3D"border:none;border-left:solid #B5C4DF 4.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id=3D"MAC_OUTLOOK_ATTR=
IBUTION_BLOCKQUOTE">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Hi Folks,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">As you know, LFA managea=
bility draft is in final phasis &#8230;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">The current document sta=
tes per AF granularity activation as a SHOULD.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&#8220;<o:p></o:p></span=
></p>
<h3 style=3D"page-break-before:always"><a name=3D"section-5.1"></a><span st=
yle=3D"color:black"><a href=3D"https://tools.ietf.org/html/draft-ietf-rtgwg=
-lfa-manageability-07#section-5.1"><span lang=3D"EN" style=3D"font-size:10.=
0pt;color:black;text-decoration:none">5.1</span></a></span><span lang=3D"EN=
" style=3D"font-size:10.0pt;color:black">.&nbsp;
 LFA enabling/disabling scope</span><span style=3D"color:black"><o:p></o:p>=
</span></h3>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; The granularity of LFA activation should=
 be controlled (as alternate</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; nexthop consume memory in forwarding pla=
ne).</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; An implementation of LFA SHOULD allow it=
s activation with the</span><span style=3D"color:black"><o:p></o:p></span><=
/pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; following criteria:</span><span style=3D=
"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; o&nbsp; Per address-family : ipv4 unicas=
t, ipv6 unicast, LDP IPv4 unicast,</span><span style=3D"color:black"><o:p><=
/o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LDP IPv6 unicast ...</=
span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; o&nbsp; Per routing context : VRF, virtu=
al/logical router, global routing</span><span style=3D"color:black"><o:p></=
o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; table, ...</span><span=
 style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<p class=3D"MsoNormal"><span style=3D"color:black">&#8220;<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">In the framework of ISIS=
/OSPF yang modelization, we are challenging this statement, do we really ne=
ed to force implementation to support this &#8220;per AF&#8221; granularity=
 ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Please provide as soon a=
s possible your feedback on this and also provide clear drivers to support =
or not per AF activation of LFA.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Thanks for your help !<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black"><a href=3D"http://www.or=
ange.com/"><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;;text-decoration:none"><img border=3D"0" width=3D"=
40" height=3D"40" id=3D"Picture_x0020_1" src=3D"cid:image001.gif@01D04ED7.9=
FB99820" alt=3D"Orange logo"></span></a><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;color:bl=
ack">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:black">Stephane Litkowski
</span></b><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Network Architect
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Orange/SCE/EQUANT/IBNF/ENDD/NDE
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Orange Expert Fut=
ure Networks</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<span style=3D"color:black;text-decoration:none">&#43;33 2 23 28 49 83 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;;color:black"><br>
</span><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:black">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<span style=3D"color:black;text-decoration:none">&#43;33 6 37 86 97 52 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;;color:black"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><span style=3D"font-size:1=
0.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#FF6600;te=
xt-decoration:none">stephane.litkowski@orange.com</span></a></span><span st=
yle=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span lang=3D"FR" style=
=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<pre><span style=3D"color:black">__________________________________________=
___________________________________________________________________________=
____<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Ce message et ses pieces jointes peuvent c=
ontenir des informations confidentielles ou privilegiees et ne doivent donc=
<o:p></o:p></span></pre>
<pre><span style=3D"color:black">pas etre diffuses, exploites ou copies san=
s autorisation. Si vous avez recu ce message par erreur, veuillez le signal=
er<o:p></o:p></span></pre>
<pre><span style=3D"color:black">a l'expediteur et le detruire ainsi que le=
s pieces jointes. Les messages electroniques etant susceptibles d'alteratio=
n,<o:p></o:p></span></pre>
<pre><span style=3D"color:black">Orange decline toute responsabilite si ce =
message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">This message and its attachments may conta=
in confidential or privileged information that may be protected by law;<o:p=
></o:p></span></pre>
<pre><span style=3D"color:black">they should not be distributed, used or co=
pied without authorisation.<o:p></o:p></span></pre>
<pre><span style=3D"color:black">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 style=3D"color:black">As emails may be altered, Orange is not li=
able for messages that have been modified, changed or falsified.<o:p></o:p>=
</span></pre>
<pre><span style=3D"color:black">Thank you.<o:p></o:p></span></pre>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_F3ADE4747C9E124B89F0ED2180CC814F4EF2D78Fxmbalnx02ciscoc_--

--_004_F3ADE4747C9E124B89F0ED2180CC814F4EF2D78Fxmbalnx02ciscoc_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: inline; filename="image001.gif"; size=381;
	creation-date="Mon, 23 Feb 2015 04:00:51 GMT";
	modification-date="Mon, 23 Feb 2015 04:00:51 GMT"
Content-ID: <image001.gif@01D04ED7.9FB99820>
Content-Transfer-Encoding: base64

R0lGODlhKAAoAMQAAP+MQP+zgP/17//s3/+DMP/iz/+fYP+8j/9wEP95IP/Gn/+WUP/Pr/+pcP/Z
v/////9mAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAAA
AAAALAAAAAAoACgAAAX6oAONZGmeaEqKauum7Cu/8Wyj9a2P+X73vhkwSCPuhkYVMolj2pbOEjTK
oxatrSlVG+U6vUxwUmwkE81BtE99xGbdSjhMPgo4BAoA+wUICAR6IwQODwMNEAcOigAFhQYQDgoD
DwcQBJOKBIOFDQmaCCyTB416hQcBBQuTEA8Cow8EBQINpHcGhAkrEAkPChAAD3YPCLuSDw+sIgEP
wCILzK0OjY9VBJS/wYQjfwaNyRDLzRAG0AMB5wC6ENyEt8jWDAsCyA/KzJN+zLILqLlVv/OuaYPU
alU9cMwuPSCl8AEDYv8EQbwRgAEABcziJFl2bMmeEQgATEwRAgA7

--_004_F3ADE4747C9E124B89F0ED2180CC814F4EF2D78Fxmbalnx02ciscoc_--


From nobody Sun Feb 22 22:02:04 2015
Return-Path: <psarkar@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 CE7961A01F0 for <rtgwg@ietfa.amsl.com>; Sun, 22 Feb 2015 22:02:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level: 
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_84=0.6, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 q8GBAkJmnmhH for <rtgwg@ietfa.amsl.com>; Sun, 22 Feb 2015 22:02:00 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0143.outbound.protection.outlook.com [207.46.100.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0397D1A01EC for <rtgwg@ietf.org>; Sun, 22 Feb 2015 22:01:59 -0800 (PST)
Received: from BY1PR0501MB1240.namprd05.prod.outlook.com (25.160.200.139) by BY1PR0501MB1237.namprd05.prod.outlook.com (25.160.200.11) with Microsoft SMTP Server (TLS) id 15.1.93.16; Mon, 23 Feb 2015 06:01:58 +0000
Received: from BY1PR0501MB1240.namprd05.prod.outlook.com ([25.160.200.139]) by BY1PR0501MB1240.namprd05.prod.outlook.com ([25.160.200.139]) with mapi id 15.01.0093.004; Mon, 23 Feb 2015 06:01:57 +0000
From: Pushpasis Sarkar <psarkar@juniper.net>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, Jeff Tantsura <jeff.tantsura@ericsson.com>, "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AQHQTy46j+sfCCoua0y9ceXZcSm85A==
Date: Mon, 23 Feb 2015 06:01:57 +0000
Message-ID: <D110BDBB.20D32%psarkar@juniper.net>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com>
In-Reply-To: <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-originating-ip: [116.197.184.17]
authentication-results: spf=none (sender IP is ) smtp.mailfrom=psarkar@juniper.net; 
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1237;
x-microsoft-antispam-prvs: <BY1PR0501MB12375C884357860C56938848FB290@BY1PR0501MB1237.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1237; 
x-forefront-prvs: 0496DF6962
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(40764003)(377454003)(199003)(189002)(17760045003)(2900100001)(19300405004)(16236675004)(99286002)(19613025002)(19627595001)(36756003)(2950100001)(19617315012)(101416001)(68736005)(92566002)(2656002)(64706001)(19625215002)(2201001)(87936001)(19618635001)(107886001)(106116001)(106356001)(66066001)(105586002)(19580405001)(19580395003)(93886004)(2501002)(5890100001)(54356999)(122556002)(76176999)(50986999)(99936001)(97736003)(86362001)(40100003)(83506001)(46102003)(62966003)(102836002)(18206015028)(15975445007)(77156002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1237; H:BY1PR0501MB1240.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
Content-Type: multipart/mixed; boundary="_004_D110BDBB20D32psarkarjunipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Feb 2015 06:01:57.2105 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0501MB1237
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/A3VChD0x0L7KLD3Ycu5YpvNIpKo>
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, 23 Feb 2015 06:02:03 -0000

--_004_D110BDBB20D32psarkarjunipernet_
Content-Type: multipart/alternative;
	boundary="_000_D110BDBB20D32psarkarjunipernet_"

--_000_D110BDBB20D32psarkarjunipernet_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi Les,

Some comments inline.

Thanks
-Pushpasis

From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com<mailto:ginsberg@cisco.c=
om>>
Date: Monday, February 23, 2015 at 9:30 AM
To: Pushpasis Sarkar <psarkar@juniper.net<mailto:psarkar@juniper.net>>, Jef=
f Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericsson.com>>,=
 "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>" <ste=
phane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, "rtgwg@i=
etf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: RE: LFA manageability : per AF config =3D> feedback required

Pushpassis -

From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Pushpasis Sarkar
Sent: Friday, February 20, 2015 3:28 AM
To: Jeff Tantsura; stephane.litkowski@orange.com<mailto:stephane.litkowski@=
orange.com>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Subject: Re: LFA manageability : per AF config =3D> feedback required

HI Jeff et al,

I can think of a reason to have a knob per-level(or per-area) or per ISIS t=
opology(note in ISIS a topology in ISIS always corresponds to a single AF,)

[Les:] This is a common mistake to make. If one simply uses RFC 5308, then =
IPv6 prefixes can be advertised in the same topology as IPv4 (MTID #0) =96 =
and there are implementations which support this. More generally, from the =
protocol=92s POV a given topology can support any combinations of address f=
amilies. It is only a convention because of the reserved MTIDs specified in=
 RFC 5120 that certain MTIDs are =93IPv6 only=94. But if one looks at the p=
rotocol capabilities such a restriction does not exist in general.
[Pushpasis] The statement was made in the case where MT has been deployed. =
When MT is deployed, assumption is always that there is another topology co=
nfigured other than MTID[0] for carrying the IPV6 topology. Isn=92t it? In =
such cases MTID[0] still carries only IPV4 prefixes only. Right? :) One can=
 argue that there can be a topology for just IPv4 mcast and not IPv6-ucast.=
 But then what is the real usecase for that then?


Interestingly you contradicted yourself below. :)
But I did want to set the record straight on this point =96 hopefully we ar=
e in agreement.
[Pushpasis] Actually I did not, coz by topology I meant when MT has been de=
ployed.  :)


and per realm and topology in OSPF. But I cannot think of a reason of why w=
ithin the same topology we need another set of knobs for each AF. Here, by =
AF I understand IPV4 or IPv6.

When both IPV4 and IPV6 are part of the same IGP topology, there is only on=
e set of backup computations needed to protect both IPV4 and IPv6 traffic.

Also I cannot think of any motivation for an operator to turn on protection=
 on only one AF and does not want to turn on for the other even if both AFs=
 has been deployed for normal forwarding.

[Les:] I think your point here is that the LFA calculation is AF independen=
t within a given topology =96 but resources are consumed independent of how=
 many computations are required- giving an operator the ability to determin=
e which prefixes are most critical seems useful. That could be per AF or pe=
r prefix.
[Pushpasis] Yes exactly. Even if IPV4 and IPV6 prefixes are carried in same=
 topology I am assuming the LFA knobs being discussed here is not the same =
as the backup selection policy described in draft-rtgwg-lfa-manageability. =
Coz, what you mentioned as per-prefix/per-AF can be easily controlled by th=
e backup-selection-policy, which should have separate configurations than o=
ne discussed on this thread.


   Les

Thanks
-Pushpasis

From: Jeff Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericss=
on.com>>
Date: Friday, February 20, 2015 at 12:59 PM
To: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>" <=
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, "rtgw=
g@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: Re: LFA manageability : per AF config =3D> feedback required

Hi Stephane,

/chair hat off

IMO in disjoined topologies one should have flexibility to enable/disable L=
FA as per AF.


Cheers,
Jeff

From: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>"=
 <stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>
Date: Thursday, February 19, 2015 at 11:21 PM
To: "rtgwg@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ie=
tf.org>>
Subject: LFA manageability : per AF config =3D> feedback required

Hi Folks,

As you know, LFA manageability draft is in final phasis =85
The current document states per AF granularity activation as a SHOULD.
=93
5.1<https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#secti=
on-5.1>.  LFA enabling/disabling scope





   The granularity of LFA activation should be controlled (as alternate

   nexthop consume memory in forwarding plane).



   An implementation of LFA SHOULD allow its activation with the

   following criteria:



   o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,

      LDP IPv6 unicast ...



   o  Per routing context : VRF, virtual/logical router, global routing

      table, ...


=93

In the framework of ISIS/OSPF yang modelization, we are challenging this st=
atement, do we really need to force implementation to support this =93per A=
F=94 granularity ?

Please provide as soon as possible your feedback on this and also provide c=
lear drivers to support or not per AF activation of LFA.


Thanks for your help !


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/IBNF/ENDD/NDE
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>



___________________________________________________________________________=
______________________________________________



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_D110BDBB20D32psarkarjunipernet_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <1A1571B7C6EA814AB6EAE05D5920114B@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Hi Les,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Some comments inline.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Thanks</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
-Pushpasis</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>&quot;Les Ginsberg (ginsberg)=
&quot; &lt;<a href=3D"mailto:ginsberg@cisco.com">ginsberg@cisco.com</a>&gt;=
<br>
<span style=3D"font-weight:bold">Date: </span>Monday, February 23, 2015 at =
9:30 AM<br>
<span style=3D"font-weight:bold">To: </span>Pushpasis Sarkar &lt;<a href=3D=
"mailto:psarkar@juniper.net">psarkar@juniper.net</a>&gt;, Jeff Tantsura &lt=
;<a href=3D"mailto:jeff.tantsura@ericsson.com">jeff.tantsura@ericsson.com</=
a>&gt;, &quot;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.lit=
kowski@orange.com</a>&quot;
 &lt;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@or=
ange.com</a>&gt;, &quot;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a=
>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>RE: LFA manageability : pe=
r AF config =3D&gt; feedback required<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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.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";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Pushpassis -<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 style=3D"font-size: 10pt; font-family: Taho=
ma, sans-serif;">From:</span></b><span style=3D"font-size: 10pt; font-famil=
y: Tahoma, sans-serif;"> rtgwg [<a href=3D"mailto:rtgwg-bounces@ietf.org">m=
ailto:rtgwg-bounces@ietf.org</a>]
<b>On Behalf Of </b>Pushpasis Sarkar<br>
<b>Sent:</b> Friday, February 20, 2015 3:28 AM<br>
<b>To:</b> Jeff Tantsura; <a href=3D"mailto:stephane.litkowski@orange.com">=
stephane.litkowski@orange.com</a>;
<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
<b>Subject:</b> Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">HI Jeff=
 et al,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I can t=
hink of a reason to have a knob per-level(or per-area) or per ISIS topology=
(note in ISIS a topology in ISIS always corresponds to a single AF,)</span>=
<span style=3D"font-size:10.5pt;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] This is a=
 common mistake to make. If one simply uses RFC 5308, then IPv6 prefixes ca=
n be advertised in the same topology as IPv4 (MTID #0) =96 and there are im=
plementations which support this. More
 generally, from the protocol=92s POV a given topology can support any comb=
inations of address families. It is only a convention because of the reserv=
ed MTIDs specified in RFC 5120 that certain MTIDs are =93IPv6 only=94. But =
if one looks at the protocol capabilities
 such a restriction does not exist in general.</span></i></b></p>
</div>
</div>
</div>
</div>
</div>
</span>
<div><b><font face=3D"Calibri,sans-serif">[Pushpasis] The statement was mad=
e in the case where MT has been deployed. When MT is deployed, assumption i=
s always that there is another topology configured other than MTID[0] for c=
arrying the IPV6 topology. Isn=92t it?
 In such cases MTID[0] still carries only IPV4 prefixes only. Right? :) One=
 can argue that&nbsp;there can be a topology for just IPv4 mcast and not IP=
v6-ucast. But then what is the real usecase for that then?</font></b></div>
<div><b><font face=3D"Calibri,sans-serif"><br>
</font></b></div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p></o:p></spa=
n></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">Interestingly yo=
u contradicted yourself below.
</span></i></b><b><i><span style=3D"font-family:Wingdings;color:#1F497D">J<=
/span></i></b><b><i><span style=3D"color:#1F497D"><o:p></o:p></span></i></b=
></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">But I did want t=
o set the record straight on this point =96 hopefully we are in agreement.<=
/span></i></b></p>
</div>
</div>
</div>
</div>
</div>
</span>
<div><b><font face=3D"Calibri,sans-serif">[Pushpasis] Actually&nbsp;I did n=
ot, coz by topology&nbsp;I meant when MT has been deployed. &nbsp;:)</font>=
</b></div>
<div><b><font face=3D"Calibri,sans-serif"><br>
</font></b></div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p></o:p></spa=
n></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">and per=
 realm and topology in OSPF. But I cannot think of a reason of why within t=
he same topology we need another set of knobs for each AF. Here, by AF I un=
derstand IPV4 or IPv6.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">When bo=
th IPV4 and IPV6 are part of the same IGP topology, there is only one set o=
f backup computations needed to protect both IPV4 and IPv6 traffic.<o:p></o=
:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Also I =
cannot think of any motivation for an operator to turn on protection on onl=
y one AF and does not want to turn on for the other even if both AFs has be=
en deployed for normal forwarding.&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] I think y=
our point here is that the LFA calculation is AF independent within a given=
 topology =96 but resources are consumed independent of how many computatio=
ns are required- giving an operator the
 ability to determine which prefixes are most critical seems useful. That c=
ould be per AF or per prefix.</span></i></b></p>
</div>
</div>
</div>
</div>
</div>
</span>
<div><b><font face=3D"Calibri,sans-serif">[Pushpasis] Yes exactly. Even if =
IPV4 and IPV6 prefixes are carried in same topology I am assuming the LFA k=
nobs being discussed here is not the same as the backup selection policy de=
scribed in draft-rtgwg-lfa-manageability.
 Coz, what you mentioned as per-prefix/per-AF can be easily controlled by t=
he backup-selection-policy,&nbsp;which should have separate configurations =
than one discussed on this thread.</font></b></div>
<div><b><font face=3D"Calibri,sans-serif"><br>
</font></b></div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p></o:p></spa=
n></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">&nbsp;&nbsp; Les=
<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Thanks<=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">-Pushpa=
sis<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">Jeff Tantsura &lt;<a href=3D"mailto:jeff.tantsura@e=
ricsson.com">jeff.tantsura@ericsson.com</a>&gt;<br>
<b>Date: </b>Friday, February 20, 2015 at 12:59 PM<br>
<b>To: </b>&quot;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.=
litkowski@orange.com</a>&quot; &lt;<a href=3D"mailto:stephane.litkowski@ora=
nge.com">stephane.litkowski@orange.com</a>&gt;, &quot;<a href=3D"mailto:rtg=
wg@ietf.org">rtgwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.org"=
>rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Hi Step=
hane,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">/chair =
hat off<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">IMO in =
disjoined topologies one should have flexibility to enable/disable LFA as p=
er AF.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Cheers,=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Jeff<o:=
p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">&quot;<a href=3D"mailto:stephane.litkowski@orange.c=
om">stephane.litkowski@orange.com</a>&quot; &lt;<a href=3D"mailto:stephane.=
litkowski@orange.com">stephane.litkowski@orange.com</a>&gt;<br>
<b>Date: </b>Thursday, February 19, 2015 at 11:21 PM<br>
<b>To: </b>&quot;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&quot;=
 &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>LFA manageability : per AF config =3D&gt; feedback required=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<blockquote style=3D"border:none;border-left:solid #B5C4DF 4.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id=3D"MAC_OUTLOOK_ATTR=
IBUTION_BLOCKQUOTE">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Hi Folks,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">As you know, LFA managea=
bility draft is in final phasis =85<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">The current document sta=
tes per AF granularity activation as a SHOULD.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">=93<o:p></o:p></span></p=
>
<h3 style=3D"page-break-before:always"><a name=3D"section-5.1"></a><span st=
yle=3D"color:black"><a href=3D"https://tools.ietf.org/html/draft-ietf-rtgwg=
-lfa-manageability-07#section-5.1"><span lang=3D"EN" style=3D"font-size:10.=
0pt;color:black;text-decoration:none">5.1</span></a></span><span lang=3D"EN=
" style=3D"font-size:10.0pt;color:black">.&nbsp;
 LFA enabling/disabling scope</span><span style=3D"color:black"><o:p></o:p>=
</span></h3>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; The granularity of LFA activation should=
 be controlled (as alternate</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; nexthop consume memory in forwarding pla=
ne).</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; An implementation of LFA SHOULD allow it=
s activation with the</span><span style=3D"color:black"><o:p></o:p></span><=
/pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; following criteria:</span><span style=3D=
"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; o&nbsp; Per address-family : ipv4 unicas=
t, ipv6 unicast, LDP IPv4 unicast,</span><span style=3D"color:black"><o:p><=
/o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LDP IPv6 unicast ...</=
span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; o&nbsp; Per routing context : VRF, virtu=
al/logical router, global routing</span><span style=3D"color:black"><o:p></=
o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; table, ...</span><span=
 style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<p class=3D"MsoNormal"><span style=3D"color:black">=93<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">In the framework of ISIS=
/OSPF yang modelization, we are challenging this statement, do we really ne=
ed to force implementation to support this =93per AF=94 granularity ?<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Please provide as soon a=
s possible your feedback on this and also provide clear drivers to support =
or not per AF activation of LFA.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Thanks for your help !<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black"><a href=3D"http://www.or=
ange.com/"><span style=3D"font-size: 12pt; font-family: 'Times New Roman', =
serif; text-decoration: none;"><img border=3D"0" width=3D"40" height=3D"40"=
 id=3D"Picture_x0020_1" src=3D"cid:image001.gif@01D04ED7.9FB99820" alt=3D"O=
range logo"></span></a><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e: 12pt; font-family: 'Times New Roman', serif; color: black;">&nbsp;</span=
><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Aria=
l, sans-serif; color: black;">Stephane Litkowski
</span></b><span style=3D"font-size: 12pt; font-family: 'Times New Roman', =
serif; color: black;"><br>
</span><span style=3D"font-size: 10pt; font-family: Arial, sans-serif; colo=
r: black;">Network Architect
</span><span style=3D"font-size: 12pt; font-family: 'Times New Roman', seri=
f; color: black;"><br>
</span><span style=3D"font-size: 10pt; font-family: Arial, sans-serif; colo=
r: black;">Orange/SCE/EQUANT/IBNF/ENDD/NDE
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size: 10pt; font-fam=
ily: Arial, sans-serif; color: black;">Orange Expert Future Networks</span>=
<span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size: 10pt; font-fam=
ily: Arial, sans-serif; color: black;">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<span style=3D"color:black;text-decoration:none">&#43;33 2 23 28 49 83 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size: 12pt; font-family: 'Tim=
es New Roman', serif; color: black;"><br>
</span><span lang=3D"FR" style=3D"font-size: 10pt; font-family: Arial, sans=
-serif; color: black;">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<span style=3D"color:black;text-decoration:none">&#43;33 6 37 86 97 52 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size: 12pt; font-family: 'Tim=
es New Roman', serif; color: black;"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><span style=3D"font-size: =
10pt; font-family: Arial, sans-serif; color: rgb(255, 102, 0); text-decorat=
ion: none;">stephane.litkowski@orange.com</span></a></span><span style=3D"c=
olor:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span lang=3D"FR" style=
=3D"font-size: 12pt; font-family: 'Times New Roman', serif; color: black;">=
&nbsp;</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<pre><span style=3D"color:black">__________________________________________=
___________________________________________________________________________=
____<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Ce message et ses pieces jointes peuvent c=
ontenir des informations confidentielles ou privilegiees et ne doivent donc=
<o:p></o:p></span></pre>
<pre><span style=3D"color:black">pas etre diffuses, exploites ou copies san=
s autorisation. Si vous avez recu ce message par erreur, veuillez le signal=
er<o:p></o:p></span></pre>
<pre><span style=3D"color:black">a l'expediteur et le detruire ainsi que le=
s pieces jointes. Les messages electroniques etant susceptibles d'alteratio=
n,<o:p></o:p></span></pre>
<pre><span style=3D"color:black">Orange decline toute responsabilite si ce =
message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">This message and its attachments may conta=
in confidential or privileged information that may be protected by law;<o:p=
></o:p></span></pre>
<pre><span style=3D"color:black">they should not be distributed, used or co=
pied without authorisation.<o:p></o:p></span></pre>
<pre><span style=3D"color:black">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 style=3D"color:black">As emails may be altered, Orange is not li=
able for messages that have been modified, changed or falsified.<o:p></o:p>=
</span></pre>
<pre><span style=3D"color:black">Thank you.<o:p></o:p></span></pre>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D110BDBB20D32psarkarjunipernet_--

--_004_D110BDBB20D32psarkarjunipernet_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: attachment; filename="image001.gif"; size=381;
	creation-date="Mon, 23 Feb 2015 06:01:56 GMT";
	modification-date="Mon, 23 Feb 2015 06:01:56 GMT"
Content-ID: <image001.gif@01D04ED7.9FB99820>
Content-Transfer-Encoding: base64

R0lGODlhKAAoAMQAAP+MQP+zgP/17//s3/+DMP/iz/+fYP+8j/9wEP95IP/Gn/+WUP/Pr/+pcP/Z
v/////9mAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAAA
AAAALAAAAAAoACgAAAX6oAONZGmeaEqKauum7Cu/8Wyj9a2P+X73vhkwSCPuhkYVMolj2pbOEjTK
oxatrSlVG+U6vUxwUmwkE81BtE99xGbdSjhMPgo4BAoA+wUICAR6IwQODwMNEAcOigAFhQYQDgoD
DwcQBJOKBIOFDQmaCCyTB416hQcBBQuTEA8Cow8EBQINpHcGhAkrEAkPChAAD3YPCLuSDw+sIgEP
wCILzK0OjY9VBJS/wYQjfwaNyRDLzRAG0AMB5wC6ENyEt8jWDAsCyA/KzJN+zLILqLlVv/OuaYPU
alU9cMwuPSCl8AEDYv8EQbwRgAEABcziJFl2bMmeEQgATEwRAgA7

--_004_D110BDBB20D32psarkarjunipernet_--


From nobody Sun Feb 22 22:16:39 2015
Return-Path: <ginsberg@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 03C991A01F6 for <rtgwg@ietfa.amsl.com>; Sun, 22 Feb 2015 22:16:39 -0800 (PST)
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_84=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 vi0t_f9DUQv2 for <rtgwg@ietfa.amsl.com>; Sun, 22 Feb 2015 22:16:33 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 539361A0179 for <rtgwg@ietf.org>; Sun, 22 Feb 2015 22:16:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=39922; q=dns/txt; s=iport; t=1424672193; x=1425881793; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=UiMI3tVZGIlGq6wg3rX/ql870zKlYoWKcihU58nEtjM=; b=E/2d4NUd25vFfkezXgCOgA5aKXjlfyczjvxNhc1F9/ExmosNF0kgs/nO 0bfWQp2qJ1zY8Rk1b0qkK3nQh6YvvIT7vapM3k4ILrzrsETwFH6QLUHF/ 5Sf6WOP6bxxZ1hnrSh61HiZ4L0MeRz+ejjMinaH8kkHkP0hw5XLGRtenY 0=;
X-Files: image001.gif : 381
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CJBQCqaeJU/4cNJK1bgkNDUloEv39EgXaFdAKBGEMBAQEBAQF8hAwBAQEEBSAIATYDBBwCAgEIBwcDAwEBAQYBAgIWAQYHAgUQAQMCCQwUCQgBAQQBEQEGAgaICwMRDchjA4VCAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwSLCIFPgjMJCgcBHwURCgwBCgEGgxCBFAWGDYQFgzqBIkqDCAFOhng4glWLKoM+IoICHIFQbwEBAQF+CRcifwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,629,1418083200";  d="gif'147?scan'147,208,217,147";a="398076473"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-8.cisco.com with ESMTP; 23 Feb 2015 06:16:30 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t1N6GUhO030912 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 23 Feb 2015 06:16:30 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.138]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0195.001; Mon, 23 Feb 2015 00:16:30 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Pushpasis Sarkar <psarkar@juniper.net>, Jeff Tantsura <jeff.tantsura@ericsson.com>, "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AdBM3SH2oNl2urLXSA+s5ntM7pKOsP//0WCAgADZjID//DGyQIAIKimAgABibmA=
Date: Mon, 23 Feb 2015 06:16:29 +0000
Message-ID: <F3ADE4747C9E124B89F0ED2180CC814F4EF2E9BD@xmb-aln-x02.cisco.com>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <D110BDBB.20D32%psarkar@juniper.net>
In-Reply-To: <D110BDBB.20D32%psarkar@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.24.29.122]
Content-Type: multipart/related; boundary="_004_F3ADE4747C9E124B89F0ED2180CC814F4EF2E9BDxmbalnx02ciscoc_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/JcqCDvU3D1GTOLRlpTdstv-NseE>
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, 23 Feb 2015 06:16:39 -0000

--_004_F3ADE4747C9E124B89F0ED2180CC814F4EF2E9BDxmbalnx02ciscoc_
Content-Type: multipart/alternative;
	boundary="_000_F3ADE4747C9E124B89F0ED2180CC814F4EF2E9BDxmbalnx02ciscoc_"

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

Pushpassis -

From: Pushpasis Sarkar [mailto:psarkar@juniper.net]
Sent: Sunday, February 22, 2015 10:02 PM
To: Les Ginsberg (ginsberg); Jeff Tantsura; stephane.litkowski@orange.com; =
rtgwg@ietf.org
Subject: Re: LFA manageability : per AF config =3D> feedback required

Hi Les,

Some comments inline.

Thanks
-Pushpasis

From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com<mailto:ginsberg@cisco.c=
om>>
Date: Monday, February 23, 2015 at 9:30 AM
To: Pushpasis Sarkar <psarkar@juniper.net<mailto:psarkar@juniper.net>>, Jef=
f Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericsson.com>>,=
 "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>" <ste=
phane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, "rtgwg@i=
etf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: RE: LFA manageability : per AF config =3D> feedback required

Pushpassis -

From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Pushpasis Sarkar
Sent: Friday, February 20, 2015 3:28 AM
To: Jeff Tantsura; stephane.litkowski@orange.com<mailto:stephane.litkowski@=
orange.com>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Subject: Re: LFA manageability : per AF config =3D> feedback required

HI Jeff et al,

I can think of a reason to have a knob per-level(or per-area) or per ISIS t=
opology(note in ISIS a topology in ISIS always corresponds to a single AF,)

[Les:] This is a common mistake to make. If one simply uses RFC 5308, then =
IPv6 prefixes can be advertised in the same topology as IPv4 (MTID #0) - an=
d there are implementations which support this. More generally, from the pr=
otocol's POV a given topology can support any combinations of address famil=
ies. It is only a convention because of the reserved MTIDs specified in RFC=
 5120 that certain MTIDs are "IPv6 only". But if one looks at the protocol =
capabilities such a restriction does not exist in general.
[Pushpasis] The statement was made in the case where MT has been deployed. =
When MT is deployed, assumption is always that there is another topology co=
nfigured other than MTID[0] for carrying the IPV6 topology. Isn't it? In su=
ch cases MTID[0] still carries only IPV4 prefixes only. Right? :) One can a=
rgue that there can be a topology for just IPv4 mcast and not IPv6-ucast. B=
ut then what is the real usecase for that then?

[Les:] You are talking about the way MT is commonly used- that is NOT the s=
ame as saying that a topology MUST always be limited to supporting one AF. =
There is no such restriction in the protocol definition.


Interestingly you contradicted yourself below. :)
But I did want to set the record straight on this point - hopefully we are =
in agreement.
[Pushpasis] Actually I did not, coz by topology I meant when MT has been de=
ployed.  :)

[Les:] Well, I was hoping...:)

and per realm and topology in OSPF. But I cannot think of a reason of why w=
ithin the same topology we need another set of knobs for each AF. Here, by =
AF I understand IPV4 or IPv6.

When both IPV4 and IPV6 are part of the same IGP topology, there is only on=
e set of backup computations needed to protect both IPV4 and IPv6 traffic.

Also I cannot think of any motivation for an operator to turn on protection=
 on only one AF and does not want to turn on for the other even if both AFs=
 has been deployed for normal forwarding.

[Les:] I think your point here is that the LFA calculation is AF independen=
t within a given topology - but resources are consumed independent of how m=
any computations are required- giving an operator the ability to determine =
which prefixes are most critical seems useful. That could be per AF or per =
prefix.
[Pushpasis] Yes exactly. Even if IPV4 and IPV6 prefixes are carried in same=
 topology I am assuming the LFA knobs being discussed here is not the same =
as the backup selection policy described in draft-rtgwg-lfa-manageability. =
Coz, what you mentioned as per-prefix/per-AF can be easily controlled by th=
e backup-selection-policy, which should have separate configurations than o=
ne discussed on this thread.

[Les:] "backup-selection-policy" specifies which member of an LFA set shoul=
d be preferred when there are multiple candidates for protecting a given pr=
efix. What we are discussing here is controlling which prefixes are eligibl=
e for protection. These ae two different concepts.

    Les


   Les

Thanks
-Pushpasis

From: Jeff Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericss=
on.com>>
Date: Friday, February 20, 2015 at 12:59 PM
To: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>" <=
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, "rtgw=
g@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: Re: LFA manageability : per AF config =3D> feedback required

Hi Stephane,

/chair hat off

IMO in disjoined topologies one should have flexibility to enable/disable L=
FA as per AF.


Cheers,
Jeff

From: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>"=
 <stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>
Date: Thursday, February 19, 2015 at 11:21 PM
To: "rtgwg@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ie=
tf.org>>
Subject: LFA manageability : per AF config =3D> feedback required

Hi Folks,

As you know, LFA manageability draft is in final phasis ...
The current document states per AF granularity activation as a SHOULD.
"
5.1<https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#secti=
on-5.1>.  LFA enabling/disabling scope





   The granularity of LFA activation should be controlled (as alternate

   nexthop consume memory in forwarding plane).



   An implementation of LFA SHOULD allow its activation with the

   following criteria:



   o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,

      LDP IPv6 unicast ...



   o  Per routing context : VRF, virtual/logical router, global routing

      table, ...


"

In the framework of ISIS/OSPF yang modelization, we are challenging this st=
atement, do we really need to force implementation to support this "per AF"=
 granularity ?

Please provide as soon as possible your feedback on this and also provide c=
lear drivers to support or not per AF activation of LFA.


Thanks for your help !


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/IBNF/ENDD/NDE
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>



___________________________________________________________________________=
______________________________________________



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_F3ADE4747C9E124B89F0ED2180CC814F4EF2E9BDxmbalnx02ciscoc_
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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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.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";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
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;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Pushpassis -<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 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;"> Pushpasi=
s Sarkar [mailto:psarkar@juniper.net]
<br>
<b>Sent:</b> Sunday, February 22, 2015 10:02 PM<br>
<b>To:</b> Les Ginsberg (ginsberg); Jeff Tantsura; stephane.litkowski@orang=
e.com; rtgwg@ietf.org<br>
<b>Subject:</b> Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Hi Les,=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Some co=
mments inline.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Thanks<=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">-Pushpa=
sis<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">&quot;Les Ginsberg (ginsberg)&quot; &lt;<a href=3D"=
mailto:ginsberg@cisco.com">ginsberg@cisco.com</a>&gt;<br>
<b>Date: </b>Monday, February 23, 2015 at 9:30 AM<br>
<b>To: </b>Pushpasis Sarkar &lt;<a href=3D"mailto:psarkar@juniper.net">psar=
kar@juniper.net</a>&gt;, Jeff Tantsura &lt;<a href=3D"mailto:jeff.tantsura@=
ericsson.com">jeff.tantsura@ericsson.com</a>&gt;, &quot;<a href=3D"mailto:s=
tephane.litkowski@orange.com">stephane.litkowski@orange.com</a>&quot;
 &lt;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@or=
ange.com</a>&gt;, &quot;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a=
>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>RE: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Pushpassis -</span><sp=
an style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span sty=
le=3D"color:black"><o:p></o:p></span></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 style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:black">From:</span></b><span sty=
le=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot=
;;color:black"> rtgwg [<a href=3D"mailto:rtgwg-bounces@ietf.org">mailto:rtg=
wg-bounces@ietf.org</a>]
<b>On Behalf Of </b>Pushpasis Sarkar<br>
<b>Sent:</b> Friday, February 20, 2015 3:28 AM<br>
<b>To:</b> Jeff Tantsura; <a href=3D"mailto:stephane.litkowski@orange.com">=
stephane.litkowski@orange.com</a>;
<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
<b>Subject:</b> Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">HI Jeff=
 et al,</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I can t=
hink of a reason to have a knob per-level(or per-area) or per ISIS topology=
(note in ISIS a topology in ISIS always corresponds to a single AF,)</span>=
<span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">&nbsp;</span></i=
></b><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] This is a=
 common mistake to make. If one simply uses RFC 5308, then IPv6 prefixes ca=
n be advertised in the same topology as IPv4 (MTID #0) &#8211; and there ar=
e implementations which support this. More
 generally, from the protocol&#8217;s POV a given topology can support any =
combinations of address families. It is only a convention because of the re=
served MTIDs specified in RFC 5120 that certain MTIDs are &#8220;IPv6 only&=
#8221;. But if one looks at the protocol capabilities
 such a restriction does not exist in general.</span></i></b><span style=3D=
"color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:12.0pt">[Pushpasis] The =
statement was made in the case where MT has been deployed. When MT is deplo=
yed, assumption is always that there is another topology configured other t=
han MTID[0] for carrying the IPV6 topology.
 Isn&#8217;t it? In such cases MTID[0] still carries only IPV4 prefixes onl=
y. Right? :) One can argue that&nbsp;there can be a topology for just IPv4 =
mcast and not IPv6-ucast. But then what is the real usecase for that then?<=
o:p></o:p></span></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] You are t=
alking about the way MT is commonly used- that is NOT the same as saying th=
at a topology MUST always be limited to supporting one AF. There is no such=
 restriction in the protocol definition.</span></i></b><span style=3D"color=
:#1F497D"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<div>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">&nbsp;</span></i=
></b><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">Interestingly yo=
u contradicted yourself below.
</span></i></b><b><i><span style=3D"font-family:Wingdings;color:#1F497D">J<=
/span></i></b><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">But I did want t=
o set the record straight on this point &#8211; hopefully we are in agreeme=
nt.</span></i></b><span style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:12.0pt">[Pushpasis] Actu=
ally&nbsp;I did not, coz by topology&nbsp;I meant when MT has been deployed=
. &nbsp;:)</span></b><span style=3D"font-size:12.0pt;font-family:&quot;Time=
s New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] Well, I w=
as hoping&#8230;</span></i></b><b><i><span style=3D"font-family:Wingdings;c=
olor:#1F497D">J</span></i></b><b><i><span style=3D"color:#1F497D">
</span></i></b><span style=3D"color:#1F497D"><o:p></o:p></span></p>
</div>
<div>
<div>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">&nbsp;</span></i=
></b><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">and per=
 realm and topology in OSPF. But I cannot think of a reason of why within t=
he same topology we need another set of knobs for each AF. Here, by AF I un=
derstand IPV4 or IPv6.</span><span style=3D"color:black"><o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:#1F497D">&nbsp=
;</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">When bo=
th IPV4 and IPV6 are part of the same IGP topology, there is only one set o=
f backup computations needed to protect both IPV4 and IPv6 traffic.</span><=
span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Also I =
cannot think of any motivation for an operator to turn on protection on onl=
y one AF and does not want to turn on for the other even if both AFs has be=
en deployed for normal forwarding.&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:#1F497D">&nbsp=
;</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] I think y=
our point here is that the LFA calculation is AF independent within a given=
 topology &#8211; but resources are consumed independent of how many comput=
ations are required- giving an operator the
 ability to determine which prefixes are most critical seems useful. That c=
ould be per AF or per prefix.</span></i></b><span style=3D"color:black"><o:=
p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:12.0pt">[Pushpasis] Yes =
exactly. Even if IPV4 and IPV6 prefixes are carried in same topology I am a=
ssuming the LFA knobs being discussed here is not the same as the backup se=
lection policy described in draft-rtgwg-lfa-manageability.
 Coz, what you mentioned as per-prefix/per-AF can be easily controlled by t=
he backup-selection-policy,&nbsp;which should have separate configurations =
than one discussed on this thread.</span></b><span style=3D"font-size:12.0p=
t;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] &#8220;ba=
ckup-selection-policy&#8221; specifies which member of an LFA set should be=
 preferred when there are multiple candidates for protecting a given prefix=
. What we are discussing here is controlling which
 prefixes are eligible for protection. These ae two different concepts.<o:p=
></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbs=
p; Les<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<div>
<div>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">&nbsp;</span></i=
></b><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">&nbsp;&nbsp; Les=
</span></i></b><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span sty=
le=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Thanks<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">-Pushpa=
sis</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">Jeff Tantsura &lt;<a href=3D"mailto:jeff.tantsura@e=
ricsson.com">jeff.tantsura@ericsson.com</a>&gt;<br>
<b>Date: </b>Friday, February 20, 2015 at 12:59 PM<br>
<b>To: </b>&quot;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.=
litkowski@orange.com</a>&quot; &lt;<a href=3D"mailto:stephane.litkowski@ora=
nge.com">stephane.litkowski@orange.com</a>&gt;, &quot;<a href=3D"mailto:rtg=
wg@ietf.org">rtgwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.org"=
>rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Hi Step=
hane,</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">/chair =
hat off</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">IMO in =
disjoined topologies one should have flexibility to enable/disable LFA as p=
er AF.</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Cheers,=
</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Jeff</s=
pan><span style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">&quot;<a href=3D"mailto:stephane.litkowski@orange.c=
om">stephane.litkowski@orange.com</a>&quot; &lt;<a href=3D"mailto:stephane.=
litkowski@orange.com">stephane.litkowski@orange.com</a>&gt;<br>
<b>Date: </b>Thursday, February 19, 2015 at 11:21 PM<br>
<b>To: </b>&quot;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&quot;=
 &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>LFA manageability : per AF config =3D&gt; feedback required=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<blockquote style=3D"border:none;border-left:solid #B5C4DF 4.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin=
-bottom:5.0pt" id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Hi Folks,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">As you know, LFA managea=
bility draft is in final phasis &#8230;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">The current document sta=
tes per AF granularity activation as a SHOULD.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&#8220;<o:p></o:p></span=
></p>
<h3 style=3D"page-break-before:always"><a name=3D"section-5.1"></a><span st=
yle=3D"color:black"><a href=3D"https://tools.ietf.org/html/draft-ietf-rtgwg=
-lfa-manageability-07#section-5.1"><span lang=3D"EN" style=3D"font-size:10.=
0pt;color:black;text-decoration:none">5.1</span></a></span><span lang=3D"EN=
" style=3D"font-size:10.0pt;color:black">.&nbsp;
 LFA enabling/disabling scope</span><span style=3D"color:black"><o:p></o:p>=
</span></h3>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; The granularity of LFA activation should=
 be controlled (as alternate</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; nexthop consume memory in forwarding pla=
ne).</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; An implementation of LFA SHOULD allow it=
s activation with the</span><span style=3D"color:black"><o:p></o:p></span><=
/pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; following criteria:</span><span style=3D=
"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; o&nbsp; Per address-family : ipv4 unicas=
t, ipv6 unicast, LDP IPv4 unicast,</span><span style=3D"color:black"><o:p><=
/o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LDP IPv6 unicast ...</=
span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; o&nbsp; Per routing context : VRF, virtu=
al/logical router, global routing</span><span style=3D"color:black"><o:p></=
o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; table, ...</span><span=
 style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<p class=3D"MsoNormal"><span style=3D"color:black">&#8220;<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">In the framework of ISIS=
/OSPF yang modelization, we are challenging this statement, do we really ne=
ed to force implementation to support this &#8220;per AF&#8221; granularity=
 ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Please provide as soon a=
s possible your feedback on this and also provide clear drivers to support =
or not per AF activation of LFA.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Thanks for your help !<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black"><a href=3D"http://www.or=
ange.com/"><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;;text-decoration:none"><img border=3D"0" width=3D"=
40" height=3D"40" id=3D"Picture_x0020_1" src=3D"cid:image001.gif@01D04EEC.B=
1F49930" alt=3D"Orange logo"></span></a><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;color:bl=
ack">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:black">Stephane Litkowski
</span></b><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Network Architect
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Orange/SCE/EQUANT/IBNF/ENDD/NDE
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Orange Expert Fut=
ure Networks</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<span style=3D"color:black;text-decoration:none">&#43;33 2 23 28 49 83 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;;color:black"><br>
</span><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:black">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<span style=3D"color:black;text-decoration:none">&#43;33 6 37 86 97 52 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;;color:black"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><span style=3D"font-size:1=
0.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#FF6600;te=
xt-decoration:none">stephane.litkowski@orange.com</span></a></span><span st=
yle=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span lang=3D"FR" style=
=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<pre><span style=3D"color:black">__________________________________________=
___________________________________________________________________________=
____<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;<o:p></o:p></span></pre>
<pre><span style=3D"color:black">Ce message et ses pieces jointes peuvent c=
ontenir des informations confidentielles ou privilegiees et ne doivent donc=
<o:p></o:p></span></pre>
<pre><span style=3D"color:black">pas etre diffuses, exploites ou copies san=
s autorisation. Si vous avez recu ce message par erreur, veuillez le signal=
er<o:p></o:p></span></pre>
<pre><span style=3D"color:black">a l'expediteur et le detruire ainsi que le=
s pieces jointes. Les messages electroniques etant susceptibles d'alteratio=
n,<o:p></o:p></span></pre>
<pre><span style=3D"color:black">Orange decline toute responsabilite si ce =
message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;<o:p></o:p></span></pre>
<pre><span style=3D"color:black">This message and its attachments may conta=
in confidential or privileged information that may be protected by law;<o:p=
></o:p></span></pre>
<pre><span style=3D"color:black">they should not be distributed, used or co=
pied without authorisation.<o:p></o:p></span></pre>
<pre><span style=3D"color:black">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 style=3D"color:black">As emails may be altered, Orange is not li=
able for messages that have been modified, changed or falsified.<o:p></o:p>=
</span></pre>
<pre><span style=3D"color:black">Thank you.<o:p></o:p></span></pre>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_F3ADE4747C9E124B89F0ED2180CC814F4EF2E9BDxmbalnx02ciscoc_--

--_004_F3ADE4747C9E124B89F0ED2180CC814F4EF2E9BDxmbalnx02ciscoc_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: inline; filename="image001.gif"; size=381;
	creation-date="Mon, 23 Feb 2015 06:16:29 GMT";
	modification-date="Mon, 23 Feb 2015 06:16:29 GMT"
Content-ID: <image001.gif@01D04EEC.B1F49930>
Content-Transfer-Encoding: base64

R0lGODlhKAAoAMQAAP+MQP+zgP/17//s3/+DMP/iz/+fYP+8j/9wEP95IP/Gn/+WUP/Pr/+pcP/Z
v/////9mAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAAA
AAAALAAAAAAoACgAAAX6oAONZGmeaEqKauum7Cu/8Wyj9a2P+X73vhkwSCPuhkYVMolj2pbOEjTK
oxatrSlVG+U6vUxwUmwkE81BtE99xGbdSjhMPgo4BAoA+wUICAR6IwQODwMNEAcOigAFhQYQDgoD
DwcQBJOKBIOFDQmaCCyTB416hQcBBQuTEA8Cow8EBQINpHcGhAkrEAkPChAAD3YPCLuSDw+sIgEP
wCILzK0OjY9VBJS/wYQjfwaNyRDLzRAG0AMB5wC6ENyEt8jWDAsCyA/KzJN+zLILqLlVv/OuaYPU
alU9cMwuPSCl8AEDYv8EQbwRgAEABcziJFl2bMmeEQgATEwRAgA7

--_004_F3ADE4747C9E124B89F0ED2180CC814F4EF2E9BDxmbalnx02ciscoc_--


From nobody Sun Feb 22 22:33:19 2015
Return-Path: <psarkar@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 574D21A0231 for <rtgwg@ietfa.amsl.com>; Sun, 22 Feb 2015 22:33:17 -0800 (PST)
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 aJ6oo9XftBrt for <rtgwg@ietfa.amsl.com>; Sun, 22 Feb 2015 22:33:15 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0144.outbound.protection.outlook.com [207.46.100.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C44AD1A0218 for <rtgwg@ietf.org>; Sun, 22 Feb 2015 22:33:15 -0800 (PST)
Received: from BY1PR0501MB1240.namprd05.prod.outlook.com (25.160.200.139) by BY1PR0501MB1239.namprd05.prod.outlook.com (25.160.200.13) with Microsoft SMTP Server (TLS) id 15.1.93.16; Mon, 23 Feb 2015 06:33:14 +0000
Received: from BY1PR0501MB1240.namprd05.prod.outlook.com ([25.160.200.139]) by BY1PR0501MB1240.namprd05.prod.outlook.com ([25.160.200.139]) with mapi id 15.01.0093.004; Mon, 23 Feb 2015 06:33:14 +0000
From: Pushpasis Sarkar <psarkar@juniper.net>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, Jeff Tantsura <jeff.tantsura@ericsson.com>, "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AQHQTzKZ1fP/wH6RXEmmzZloMnvj0A==
Date: Mon, 23 Feb 2015 06:33:13 +0000
Message-ID: <D110C66B.20D87%psarkar@juniper.net>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <D110BDBB.20D32%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2E9BD@xmb-aln-x02.cisco.com>
In-Reply-To: <F3ADE4747C9E124B89F0ED2180CC814F4EF2E9BD@xmb-aln-x02.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-originating-ip: [116.197.184.12]
authentication-results: spf=none (sender IP is ) smtp.mailfrom=psarkar@juniper.net; 
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1239;
x-microsoft-antispam-prvs: <BY1PR0501MB12395961831E5E21AB12AD58FB290@BY1PR0501MB1239.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1239; 
x-forefront-prvs: 0496DF6962
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(199003)(377454003)(189002)(36756003)(87936001)(76176999)(66066001)(2656002)(50986999)(62966003)(46102003)(19580405001)(83506001)(77156002)(19580395003)(101416001)(106356001)(64706001)(93886004)(92566002)(107886001)(99286002)(2501002)(86362001)(105586002)(54356999)(2900100001)(2950100001)(16236675004)(122556002)(40100003)(106116001)(2201001)(97736003)(102836002)(68736005); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1239; H:BY1PR0501MB1240.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
Content-Type: multipart/alternative; boundary="_000_D110C66B20D87psarkarjunipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Feb 2015 06:33:13.5865 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0501MB1239
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/bn247UXChHOjYp0q4xRF8_Nom04>
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, 23 Feb 2015 06:33:17 -0000

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

Hi Les,

From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com<mailto:ginsberg@cisco.c=
om>>
Date: Monday, February 23, 2015 at 11:46 AM
To: Pushpasis Sarkar <psarkar@juniper.net<mailto:psarkar@juniper.net>>, Jef=
f Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericsson.com>>,=
 "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>" <ste=
phane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, "rtgwg@i=
etf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: RE: LFA manageability : per AF config =3D> feedback required

[Les:] "backup-selection-policy" specifies which member of an LFA set shoul=
d be preferred when there are multiple candidates for protecting a given pr=
efix. What we are discussing here is controlling which prefixes are eligibl=
e for protection. These ae two different concepts.

[Pushpasis] Well, it is not only preferring. It can also be not-preferring-=
any (or pruning). So if no protection for any IPv6 is required, it can be a=
chieved by a policy as belows:

Destination ipv6-all {
{
   Interface all
   {
       Neighbor exclude all;
   }
}


--_000_D110C66B20D87psarkarjunipernet_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <C5DC5D77C61910469DB0CE674351FAAD@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi Les,</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>&quot;Les Ginsberg (ginsberg)=
&quot; &lt;<a href=3D"mailto:ginsberg@cisco.com">ginsberg@cisco.com</a>&gt;=
<br>
<span style=3D"font-weight:bold">Date: </span>Monday, February 23, 2015 at =
11:46 AM<br>
<span style=3D"font-weight:bold">To: </span>Pushpasis Sarkar &lt;<a href=3D=
"mailto:psarkar@juniper.net">psarkar@juniper.net</a>&gt;, Jeff Tantsura &lt=
;<a href=3D"mailto:jeff.tantsura@ericsson.com">jeff.tantsura@ericsson.com</=
a>&gt;, &quot;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.lit=
kowski@orange.com</a>&quot;
 &lt;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@or=
ange.com</a>&gt;, &quot;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a=
>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>RE: LFA manageability : pe=
r AF config =3D&gt; feedback required<br>
</div>
<div><br>
</div>
<b style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-siz=
e: 15px; font-style: normal; font-variant: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; te=
xt-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -=
webkit-text-stroke-width: 0px;"><i><span style=3D"color: rgb(31, 73, 125);"=
>[Les:]
 &#8220;backup-selection-policy&#8221; specifies which member of an LFA set=
 should be preferred when there are multiple candidates for protecting a gi=
ven prefix. What we are discussing here is controlling which prefixes are e=
ligible for protection. These ae two different
 concepts.</span></i></b></span>
<div><br>
</div>
<div>[Pushpasis] Well, it is not only preferring. It can also be not-prefer=
ring-any (or pruning). So if no protection for any IPv6 is required, it can=
 be achieved by a policy as belows:</div>
<div><br>
</div>
<div>Destination ipv6-all {</div>
<div>{</div>
<div>&nbsp;&nbsp; Interface all</div>
<div>&nbsp; &nbsp;{</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp;Neighbor exclude all;</div>
<div>&nbsp; &nbsp;}</div>
<div>}</div>
<div><br>
</div>
</body>
</html>

--_000_D110C66B20D87psarkarjunipernet_--


From nobody Sun Feb 22 22:42:17 2015
Return-Path: <ginsberg@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 33E311A0231 for <rtgwg@ietfa.amsl.com>; Sun, 22 Feb 2015 22:42:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 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_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 2i3BQZlyCT3L for <rtgwg@ietfa.amsl.com>; Sun, 22 Feb 2015 22:42:14 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA9AD1A0218 for <rtgwg@ietf.org>; Sun, 22 Feb 2015 22:42:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12301; q=dns/txt; s=iport; t=1424673733; x=1425883333; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=pHjvatFjhu4vtcMld5oEo+Qe4BgEzU/rgu7toIjB1ok=; b=UocCIRBZHDL23VZ87NUgPQqmAgy8/TXWCwiMD0Vi68TH0FDK3F+p2pu6 xfGecEkZ4Y64qeOEUSMgFjGebS3QfB2OLX21PyhVao3fYFAqR9JpbsOAG 3b8JPsb4MesXN3RyomgPVDBKZkeVFAb+7dcWKQcsBXkTWn7o/OXUDlHwW g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BCBQBpyupU/4gNJK1bgkNDUloEyQICgR9DAQEBAQEBfIQPAQEBBC1cAgEIDgMDAQEBCx0HMhQJCAIEARIIiCfSTQEBAQEBAQEBAQEBAQEBAQEBAQEBAReLE4FPgjQUJiAXAYMXgRQFj1KcdiKDbm+BA0F/AQEB
X-IronPort-AV: E=Sophos;i="5.09,629,1418083200";  d="scan'208,217";a="125965993"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-3.cisco.com with ESMTP; 23 Feb 2015 06:42:12 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t1N6gC5f008305 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 23 Feb 2015 06:42:12 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.138]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0195.001; Mon, 23 Feb 2015 00:42:12 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Pushpasis Sarkar <psarkar@juniper.net>, Jeff Tantsura <jeff.tantsura@ericsson.com>, "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AdBM3SH2oNl2urLXSA+s5ntM7pKOsP//0WCAgADZjID//DGyQIAIKimAgABibmD//6ZOgIAAZARA
Date: Mon, 23 Feb 2015 06:42:11 +0000
Message-ID: <F3ADE4747C9E124B89F0ED2180CC814F4EF2EA28@xmb-aln-x02.cisco.com>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <D110BDBB.20D32%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2E9BD@xmb-aln-x02.cisco.com> <D110C66B.20D87%psarkar@juniper.net>
In-Reply-To: <D110C66B.20D87%psarkar@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.24.29.122]
Content-Type: multipart/alternative; boundary="_000_F3ADE4747C9E124B89F0ED2180CC814F4EF2EA28xmbalnx02ciscoc_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/ACpKKTF2B15o6viyj17Y68onw3w>
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, 23 Feb 2015 06:42:16 -0000

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

Pushpassis -

Conceptually, there are two different functionalities being discussed:

1)Supporting selection of what prefixes are eligible for protection. This i=
s what Section 5.1 of the draft discusses.

2)For the set of prefixes which are eligible for protection, supporting pol=
icy to choose between multiple LFA candidates. This is discussed in Section=
 5.2 of the draft.

How you choose to implement this support is outside the scope of both the d=
raft and this discussion.

    Les


From: Pushpasis Sarkar [mailto:psarkar@juniper.net]
Sent: Sunday, February 22, 2015 10:33 PM
To: Les Ginsberg (ginsberg); Jeff Tantsura; stephane.litkowski@orange.cothe=
<mailto:stephane.litkowski@orange.cothe> abiloity to limit the set of prefi=
xes m; rtgwg@ietf.org
Subject: Re: LFA manageability : per AF config =3D> feedback required

Hi Les,

From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com<mailto:ginsberg@cisco.c=
om>>
Date: Monday, February 23, 2015 at 11:46 AM
To: Pushpasis Sarkar <psarkar@juniper.net<mailto:psarkar@juniper.net>>, Jef=
f Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericsson.com>>,=
 "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>" <ste=
phane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, "rtgwg@i=
etf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: RE: LFA manageability : per AF config =3D> feedback required

[Les:] "backup-selection-policy" specifies which member of an LFA set shoul=
d be preferred when there are multiple candidates for protecting a given pr=
efix. What we are discussing here is controlling which prefixes are eligibl=
e for protection. These ae two different concepts.

[Pushpasis] Well, it is not only preferring. It can also be not-preferring-=
any (or pruning). So if no protection for any IPv6 is required, it can be a=
chieved by a policy as belows:

Destination ipv6-all {
{
   Interface all
   {
       Neighbor exclude all;
   }
}


--_000_F3ADE4747C9E124B89F0ED2180CC814F4EF2EA28xmbalnx02ciscoc_
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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
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.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Pushpassis &#8211;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Conceptually, there are t=
wo different functionalities being discussed:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">1)Supporting selection of=
 what prefixes are eligible for protection. This is what Section 5.1 of the=
 draft discusses.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">2)For the set of prefixes=
 which are eligible for protection, supporting policy to choose between mul=
tiple LFA candidates. This is discussed in Section 5.2 of
 the draft.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">How you choose to impleme=
nt this support is outside the scope of both the draft and this discussion.=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp; Les<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/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 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;"> Pushpasi=
s Sarkar [mailto:psarkar@juniper.net]
<br>
<b>Sent:</b> Sunday, February 22, 2015 10:33 PM<br>
<b>To:</b> Les Ginsberg (ginsberg); Jeff Tantsura; <a href=3D"mailto:stepha=
ne.litkowski@orange.cothe">
stephane.litkowski@orange.cothe</a> abiloity to limit the set of prefixes m=
; rtgwg@ietf.org<br>
<b>Subject:</b> Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Hi Les,<o:p></o:p></span></=
p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:black">From:
</span></b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,=
&quot;sans-serif&quot;;color:black">&quot;Les Ginsberg (ginsberg)&quot; &lt=
;<a href=3D"mailto:ginsberg@cisco.com">ginsberg@cisco.com</a>&gt;<br>
<b>Date: </b>Monday, February 23, 2015 at 11:46 AM<br>
<b>To: </b>Pushpasis Sarkar &lt;<a href=3D"mailto:psarkar@juniper.net">psar=
kar@juniper.net</a>&gt;, Jeff Tantsura &lt;<a href=3D"mailto:jeff.tantsura@=
ericsson.com">jeff.tantsura@ericsson.com</a>&gt;, &quot;<a href=3D"mailto:s=
tephane.litkowski@orange.com">stephane.litkowski@orange.com</a>&quot;
 &lt;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@or=
ange.com</a>&gt;, &quot;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a=
>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>RE: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size:11.5pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[Les:] &#8220;backu=
p-selection-policy&#8221; specifies which member of an LFA set should be pr=
eferred when there are multiple candidates for protecting a given prefix.
 What we are discussing here is controlling which prefixes are eligible for=
 protection. These ae two different concepts.</span></i></b><span style=3D"=
font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;col=
or:black">
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">[Pushpasis] Well, it is not=
 only preferring. It can also be not-preferring-any (or pruning). So if no =
protection for any IPv6 is required, it can be achieved
 by a policy as belows:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Destination ipv6-all {<o:p>=
</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">{<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">&nbsp;&nbsp; Interface all<=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">&nbsp; &nbsp;{<o:p></o:p></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">&nbsp; &nbsp; &nbsp; &nbsp;=
Neighbor exclude all;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">&nbsp; &nbsp;}<o:p></o:p></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">}<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
</div>
</div>
</body>
</html>

--_000_F3ADE4747C9E124B89F0ED2180CC814F4EF2EA28xmbalnx02ciscoc_--


From nobody Sun Feb 22 23:09:33 2015
Return-Path: <psarkar@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 39C0F1A014E for <rtgwg@ietfa.amsl.com>; Sun, 22 Feb 2015 23:09:32 -0800 (PST)
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, 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 BSePDJssJnIm for <rtgwg@ietfa.amsl.com>; Sun, 22 Feb 2015 23:09:28 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0701.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::701]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71CFD1A0118 for <rtgwg@ietf.org>; Sun, 22 Feb 2015 23:09:28 -0800 (PST)
Received: from BY1PR0501MB1240.namprd05.prod.outlook.com (25.160.200.139) by BN1PR05MB439.namprd05.prod.outlook.com (10.141.58.22) with Microsoft SMTP Server (TLS) id 15.1.93.16; Mon, 23 Feb 2015 07:09:11 +0000
Received: from BY1PR0501MB1240.namprd05.prod.outlook.com ([25.160.200.139]) by BY1PR0501MB1240.namprd05.prod.outlook.com ([25.160.200.139]) with mapi id 15.01.0093.004; Mon, 23 Feb 2015 07:09:11 +0000
From: Pushpasis Sarkar <psarkar@juniper.net>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, Jeff Tantsura <jeff.tantsura@ericsson.com>, "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AQHQTzefDKMBvdyPHUq0FYIj0Byysg==
Date: Mon, 23 Feb 2015 07:09:10 +0000
Message-ID: <D110CD4B.20D9C%psarkar@juniper.net>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <D110BDBB.20D32%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2E9BD@xmb-aln-x02.cisco.com> <D110C66B.20D87%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2EA28@xmb-aln-x02.cisco.com>
In-Reply-To: <F3ADE4747C9E124B89F0ED2180CC814F4EF2EA28@xmb-aln-x02.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-originating-ip: [116.197.184.17]
authentication-results: spf=none (sender IP is ) smtp.mailfrom=psarkar@juniper.net; 
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB439;
x-microsoft-antispam-prvs: <BN1PR05MB439FCD56176F25F161C1206FB290@BN1PR05MB439.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB439;
x-forefront-prvs: 0496DF6962
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(377454003)(189002)(199003)(92566002)(99286002)(2501002)(19625215002)(93886004)(19300405004)(86362001)(101416001)(64706001)(106356001)(2950100001)(97736003)(2201001)(15975445007)(40100003)(102836002)(2900100001)(68736005)(16236675004)(106116001)(105586002)(54356999)(122556002)(2656002)(76176999)(66066001)(50986999)(87936001)(36756003)(83506001)(19580405001)(77156002)(19580395003)(62966003)(46102003); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR05MB439; H:BY1PR0501MB1240.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
Content-Type: multipart/alternative; boundary="_000_D110CD4B20D9Cpsarkarjunipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Feb 2015 07:09:10.9355 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN1PR05MB439
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/pkBtLVs9j77BtMXeoa3_4gaBpyY>
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, 23 Feb 2015 07:09:32 -0000

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

Hi Les,

The point I am trying to make is that the following in section 5.1 does not=
 make any sense to me anymore. And hence a per AF LFA knob too does not mak=
es sense.

"An implementation of LFA SHOULD allow its activation with the

   following criteria:

   o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,

      LDP IPv6 unicast ..."

I have mentioned this to Stephane as well.

Why will a operator choose to not protect an entire AF (IPV4/IPV6) when nor=
mal forwarding for both AF has been enabled. As long as a single AF is usin=
g protection the same backup computations can be used for other AFs as well=
 without any extra cost. When operator is choosing protection only for sub-=
set of prefixes, backup computations still needs to be done for entire topo=
logy irrespective of the AF.

Thanks
-Pushpasis

From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com<mailto:ginsberg@cisco.c=
om>>
Date: Monday, February 23, 2015 at 12:12 PM
To: Pushpasis Sarkar <psarkar@juniper.net<mailto:psarkar@juniper.net>>, Jef=
f Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericsson.com>>,=
 "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>" <ste=
phane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, "rtgwg@i=
etf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: RE: LFA manageability : per AF config =3D> feedback required

Pushpassis -

Conceptually, there are two different functionalities being discussed:

1)Supporting selection of what prefixes are eligible for protection. This i=
s what Section 5.1 of the draft discusses.

2)For the set of prefixes which are eligible for protection, supporting pol=
icy to choose between multiple LFA candidates. This is discussed in Section=
 5.2 of the draft.

How you choose to implement this support is outside the scope of both the d=
raft and this discussion.

    Les


From: Pushpasis Sarkar [mailto:psarkar@juniper.net]
Sent: Sunday, February 22, 2015 10:33 PM
To: Les Ginsberg (ginsberg); Jeff Tantsura; stephane.litkowski@orange.cothe=
<mailto:stephane.litkowski@orange.cothe> abiloity to limit the set of prefi=
xes m; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Subject: Re: LFA manageability : per AF config =3D> feedback required

Hi Les,

From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com<mailto:ginsberg@cisco.c=
om>>
Date: Monday, February 23, 2015 at 11:46 AM
To: Pushpasis Sarkar <psarkar@juniper.net<mailto:psarkar@juniper.net>>, Jef=
f Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericsson.com>>,=
 "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>" <ste=
phane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, "rtgwg@i=
etf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: RE: LFA manageability : per AF config =3D> feedback required

[Les:] "backup-selection-policy" specifies which member of an LFA set shoul=
d be preferred when there are multiple candidates for protecting a given pr=
efix. What we are discussing here is controlling which prefixes are eligibl=
e for protection. These ae two different concepts.

[Pushpasis] Well, it is not only preferring. It can also be not-preferring-=
any (or pruning). So if no protection for any IPv6 is required, it can be a=
chieved by a policy as belows:

Destination ipv6-all {
{
   Interface all
   {
       Neighbor exclude all;
   }
}


--_000_D110CD4B20D9Cpsarkarjunipernet_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <807EACAA4BB91148A75632F1901611DE@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi Les,</div>
<div><br>
</div>
<div>The point I am trying to make is that the following in section 5.1 doe=
s not make any sense to me anymore. And hence a per AF LFA knob too does no=
t makes sense.</div>
<div><br>
</div>
<div>&#8220;<span style=3D"font-size: 13px; line-height: 1.2em;">An impleme=
ntation of LFA SHOULD allow its activation with the</span></div>
<pre style=3D"line-height: 1.2em; margin-top: 0px; margin-bottom: 0px; font=
-size: 13px;">   following criteria:

   o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,&nb=
sp;</pre>
<div><span style=3D"font-size: 13px; line-height: 1.2em;">&nbsp; &nbsp; &nb=
sp; LDP IPv6 unicast ...</span>&#8221;</div>
<div><br>
</div>
<div>I have mentioned this to Stephane as well.&nbsp;</div>
<div><br>
</div>
<div>Why will a operator choose to not protect an entire AF (IPV4/IPV6) whe=
n normal forwarding for both AF has been enabled. As long as a single AF is=
 using protection the same backup computations can be used for other AFs as=
 well without any extra cost. When
 operator is choosing protection only for sub-set of prefixes, backup compu=
tations still needs to be done for entire topology irrespective of the AF.<=
/div>
<div><br>
</div>
<div>Thanks</div>
<div>-Pushpasis</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>&quot;Les Ginsberg (ginsberg)=
&quot; &lt;<a href=3D"mailto:ginsberg@cisco.com">ginsberg@cisco.com</a>&gt;=
<br>
<span style=3D"font-weight:bold">Date: </span>Monday, February 23, 2015 at =
12:12 PM<br>
<span style=3D"font-weight:bold">To: </span>Pushpasis Sarkar &lt;<a href=3D=
"mailto:psarkar@juniper.net">psarkar@juniper.net</a>&gt;, Jeff Tantsura &lt=
;<a href=3D"mailto:jeff.tantsura@ericsson.com">jeff.tantsura@ericsson.com</=
a>&gt;, &quot;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.lit=
kowski@orange.com</a>&quot;
 &lt;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@or=
ange.com</a>&gt;, &quot;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a=
>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>RE: LFA manageability : pe=
r AF config =3D&gt; feedback required<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
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.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Pushpassis &#8211;<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Conceptually, there are two differe=
nt functionalities being discussed:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">1)Supporting selection of what pref=
ixes are eligible for protection. This is what Section 5.1 of the draft dis=
cusses.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">2)For the set of prefixes which are=
 eligible for protection, supporting policy to choose between multiple LFA =
candidates. This is discussed in Section
 5.2 of the draft.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">How you choose to implement this su=
pport is outside the scope of both the draft and this discussion.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;&nbsp;&nbsp; Les<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></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 style=3D"font-size: 10pt; font-family: Taho=
ma, sans-serif;">From:</span></b><span style=3D"font-size: 10pt; font-famil=
y: Tahoma, sans-serif;"> Pushpasis Sarkar [<a href=3D"mailto:psarkar@junipe=
r.net">mailto:psarkar@juniper.net</a>]
<br>
<b>Sent:</b> Sunday, February 22, 2015 10:33 PM<br>
<b>To:</b> Les Ginsberg (ginsberg); Jeff Tantsura; <a href=3D"mailto:stepha=
ne.litkowski@orange.cothe">
stephane.litkowski@orange.cothe</a> abiloity to limit the set of prefixes m=
; <a href=3D"mailto:rtgwg@ietf.org">
rtgwg@ietf.org</a><br>
<b>Subject:</b> Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;">Hi Les,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;"><o:p>&nbsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 11pt; font-family: Cali=
bri, sans-serif; color: black;">From:
</span></b><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif=
; color: black;">&quot;Les Ginsberg (ginsberg)&quot; &lt;<a href=3D"mailto:=
ginsberg@cisco.com">ginsberg@cisco.com</a>&gt;<br>
<b>Date: </b>Monday, February 23, 2015 at 11:46 AM<br>
<b>To: </b>Pushpasis Sarkar &lt;<a href=3D"mailto:psarkar@juniper.net">psar=
kar@juniper.net</a>&gt;, Jeff Tantsura &lt;<a href=3D"mailto:jeff.tantsura@=
ericsson.com">jeff.tantsura@ericsson.com</a>&gt;, &quot;<a href=3D"mailto:s=
tephane.litkowski@orange.com">stephane.litkowski@orange.com</a>&quot;
 &lt;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@or=
ange.com</a>&gt;, &quot;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a=
>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>RE: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;"><o:p>&nbsp;</o:p></span></p>
</div>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size: 11.5pt; font-family:=
 Calibri, sans-serif; color: rgb(31, 73, 125);">[Les:] &#8220;backup-select=
ion-policy&#8221; specifies which member of an LFA set should be preferred =
when there are multiple candidates for protecting
 a given prefix. What we are discussing here is controlling which prefixes =
are eligible for protection. These ae two different concepts.</span></i></b=
><span style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color:=
 black;"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;">[Pushpasis] Well, it is not only preferring.=
 It can also be not-preferring-any (or pruning). So if no protection for an=
y IPv6 is required, it can be achieved
 by a policy as belows:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;">Destination ipv6-all {<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;">{<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;">&nbsp;&nbsp; Interface all<o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;">&nbsp; &nbsp;{<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;">&nbsp; &nbsp; &nbsp; &nbsp;Neighbor exclude =
all;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;">&nbsp; &nbsp;}<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;">}<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D110CD4B20D9Cpsarkarjunipernet_--


From nobody Sun Feb 22 23:10:10 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 A01BA1A0118 for <rtgwg@ietfa.amsl.com>; Sun, 22 Feb 2015 23:10:09 -0800 (PST)
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 XKoeTWflN-ih for <rtgwg@ietfa.amsl.com>; Sun, 22 Feb 2015 23:10:06 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40DA71A024E for <rtgwg@ietf.org>; Sun, 22 Feb 2015 23:10:04 -0800 (PST)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 225963B41D3; Mon, 23 Feb 2015 08:10:02 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.16]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id E9C2C35C08C; Mon, 23 Feb 2015 08:10:01 +0100 (CET)
Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.142]) by OPEXCLILH05.corporate.adroot.infra.ftgroup ([10.114.31.16]) with mapi id 14.03.0224.002; Mon, 23 Feb 2015 08:10:01 +0100
From: <stephane.litkowski@orange.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, Pushpasis Sarkar <psarkar@juniper.net>, Jeff Tantsura <jeff.tantsura@ericsson.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AdBM3SH2oNl2urLXSA+s5ntM7pKOsP//0WCAgABkM4CABDoFgIAAIdaAgAAED4CAAAStgIAAAoKA///oX3A=
Date: Mon, 23 Feb 2015 07:10:00 +0000
Message-ID: <14016_1424675402_54EAD249_14016_364_1_9E32478DFA9976438E7A22F69B08FF9215C157B3@OPEXCLILM34.corporate.adroot.infra.ftgroup>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <D110BDBB.20D32%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2E9BD@xmb-aln-x02.cisco.com> <D110C66B.20D87%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2EA28@xmb-aln-x02.cisco.com>
In-Reply-To: <F3ADE4747C9E124B89F0ED2180CC814F4EF2EA28@xmb-aln-x02.cisco.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: multipart/alternative; boundary="_000_9E32478DFA9976438E7A22F69B08FF9215C157B3OPEXCLILM34corp_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.12.16.112421
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/GeSVjRtQ7rSHIqu8aESgLBD5mao>
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, 23 Feb 2015 07:10:09 -0000

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

+1, I confirm the two different goals to achieve in the draft. As Les menti=
oned, implementing it both in a common policy framework or in two different=
 features is implementation dependent.


From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
Sent: Monday, February 23, 2015 07:42
To: Pushpasis Sarkar; Jeff Tantsura; LITKOWSKI Stephane SCE/IBNF; rtgwg@iet=
f.org
Subject: RE: LFA manageability : per AF config =3D> feedback required

Pushpassis -

Conceptually, there are two different functionalities being discussed:

1)Supporting selection of what prefixes are eligible for protection. This i=
s what Section 5.1 of the draft discusses.

2)For the set of prefixes which are eligible for protection, supporting pol=
icy to choose between multiple LFA candidates. This is discussed in Section=
 5.2 of the draft.

How you choose to implement this support is outside the scope of both the d=
raft and this discussion.

    Les


From: Pushpasis Sarkar [mailto:psarkar@juniper.net]
Sent: Sunday, February 22, 2015 10:33 PM
To: Les Ginsberg (ginsberg); Jeff Tantsura; stephane.litkowski@orange.cothe=
<mailto:stephane.litkowski@orange.cothe> abiloity to limit the set of prefi=
xes m; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Subject: Re: LFA manageability : per AF config =3D> feedback required

Hi Les,

From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com<mailto:ginsberg@cisco.c=
om>>
Date: Monday, February 23, 2015 at 11:46 AM
To: Pushpasis Sarkar <psarkar@juniper.net<mailto:psarkar@juniper.net>>, Jef=
f Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericsson.com>>,=
 "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>" <ste=
phane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, "rtgwg@i=
etf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: RE: LFA manageability : per AF config =3D> feedback required

[Les:] "backup-selection-policy" specifies which member of an LFA set shoul=
d be preferred when there are multiple candidates for protecting a given pr=
efix. What we are discussing here is controlling which prefixes are eligibl=
e for protection. These ae two different concepts.

[Pushpasis] Well, it is not only preferring. It can also be not-preferring-=
any (or pruning). So if no protection for any IPv6 is required, it can be a=
chieved by a policy as belows:

Destination ipv6-all {
{
   Interface all
   {
       Neighbor exclude all;
   }
}


___________________________________________________________________________=
______________________________________________

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_9E32478DFA9976438E7A22F69B08FF9215C157B3OPEXCLILM34corp_
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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
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.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#43;1, I confirm the two=
 different goals to achieve in the draft. As Les mentioned, implementing it=
 both in a common policy framework or in two different features
 is implementation dependent.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<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;"> Les Gins=
berg (ginsberg) [mailto:ginsberg@cisco.com]
<br>
<b>Sent:</b> Monday, February 23, 2015 07:42<br>
<b>To:</b> Pushpasis Sarkar; Jeff Tantsura; LITKOWSKI Stephane SCE/IBNF; rt=
gwg@ietf.org<br>
<b>Subject:</b> RE: LFA manageability : per AF config =3D&gt; feedback requ=
ired<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"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Pushpassis &#8211;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Conceptually, there are t=
wo different functionalities being discussed:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">1)Supporting selection of=
 what prefixes are eligible for protection. This is what Section 5.1 of the=
 draft discusses.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">2)For the set of prefixes=
 which are eligible for protection, supporting policy to choose between mul=
tiple LFA candidates. This is discussed in Section 5.2 of
 the draft.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">How you choose to impleme=
nt this support is outside the scope of both the draft and this discussion.=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp; Les<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/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 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;"> Pushpasi=
s Sarkar [<a href=3D"mailto:psarkar@juniper.net">mailto:psarkar@juniper.net=
</a>]
<br>
<b>Sent:</b> Sunday, February 22, 2015 10:33 PM<br>
<b>To:</b> Les Ginsberg (ginsberg); Jeff Tantsura; <a href=3D"mailto:stepha=
ne.litkowski@orange.cothe">
stephane.litkowski@orange.cothe</a> abiloity to limit the set of prefixes m=
; <a href=3D"mailto:rtgwg@ietf.org">
rtgwg@ietf.org</a><br>
<b>Subject:</b> Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Hi Les,<o:p></o:p></span></=
p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:black">From:
</span></b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,=
&quot;sans-serif&quot;;color:black">&quot;Les Ginsberg (ginsberg)&quot; &lt=
;<a href=3D"mailto:ginsberg@cisco.com">ginsberg@cisco.com</a>&gt;<br>
<b>Date: </b>Monday, February 23, 2015 at 11:46 AM<br>
<b>To: </b>Pushpasis Sarkar &lt;<a href=3D"mailto:psarkar@juniper.net">psar=
kar@juniper.net</a>&gt;, Jeff Tantsura &lt;<a href=3D"mailto:jeff.tantsura@=
ericsson.com">jeff.tantsura@ericsson.com</a>&gt;, &quot;<a href=3D"mailto:s=
tephane.litkowski@orange.com">stephane.litkowski@orange.com</a>&quot;
 &lt;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@or=
ange.com</a>&gt;, &quot;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a=
>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>RE: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size:11.5pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[Les:] &#8220;backu=
p-selection-policy&#8221; specifies which member of an LFA set should be pr=
eferred when there are multiple candidates for protecting a given prefix.
 What we are discussing here is controlling which prefixes are eligible for=
 protection. These ae two different concepts.</span></i></b><span style=3D"=
font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;col=
or:black">
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">[Pushpasis] Well, it is not=
 only preferring. It can also be not-preferring-any (or pruning). So if no =
protection for any IPv6 is required, it can be achieved
 by a policy as belows:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Destination ipv6-all {<o:p>=
</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">{<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">&nbsp;&nbsp; Interface all<=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">&nbsp; &nbsp;{<o:p></o:p></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">&nbsp; &nbsp; &nbsp; &nbsp;=
Neighbor exclude all;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">&nbsp; &nbsp;}<o:p></o:p></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">}<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</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_9E32478DFA9976438E7A22F69B08FF9215C157B3OPEXCLILM34corp_--


From nobody Sun Feb 22 23:10:23 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 B00D51A024E for <rtgwg@ietfa.amsl.com>; Sun, 22 Feb 2015 23:10:11 -0800 (PST)
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_84=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 lkclIz017z2z for <rtgwg@ietfa.amsl.com>; Sun, 22 Feb 2015 23:10:06 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1C5F1A014E for <rtgwg@ietf.org>; Sun, 22 Feb 2015 23:10:03 -0800 (PST)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id 2BA432DC0A4; Mon, 23 Feb 2015 08:10:01 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.55]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 0073027C12C; Mon, 23 Feb 2015 08:10:01 +0100 (CET)
Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.142]) by OPEXCLILH03.corporate.adroot.infra.ftgroup ([10.114.31.55]) with mapi id 14.03.0224.002; Mon, 23 Feb 2015 08:10:00 +0100
From: <stephane.litkowski@orange.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, Pushpasis Sarkar <psarkar@juniper.net>, Jeff Tantsura <jeff.tantsura@ericsson.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AdBM3SH2oNl2urLXSA+s5ntM7pKOsP//0WCAgABkM4CABDoFgP//vAlw
Date: Mon, 23 Feb 2015 07:10:00 +0000
Message-ID: <5876_1424675401_54EAD249_5876_2527_11_9E32478DFA9976438E7A22F69B08FF9215C157AC@OPEXCLILM34.corporate.adroot.infra.ftgroup>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com>
In-Reply-To: <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: multipart/related; boundary="_004_9E32478DFA9976438E7A22F69B08FF9215C157ACOPEXCLILM34corp_"; type="multipart/alternative"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.2.23.23029
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/dNy1wVz0PHfoaPQeB0qmdlgkP1c>
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, 23 Feb 2015 07:10:11 -0000

--_004_9E32478DFA9976438E7A22F69B08FF9215C157ACOPEXCLILM34corp_
Content-Type: multipart/alternative;
	boundary="_000_9E32478DFA9976438E7A22F69B08FF9215C157ACOPEXCLILM34corp_"


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

[Les:] I think your point here is that the LFA calculation is AF independen=
t within a given topology - but resources are consumed independent of how m=
any computations are required- giving an operator the ability to determine =
which prefixes are most critical seems useful. That could be per AF or per =
prefix.

[SLI] Agree but is the "resource saving" point strong enough to mandate per=
 AF activation ?

From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
Sent: Monday, February 23, 2015 05:01
To: Pushpasis Sarkar; Jeff Tantsura; LITKOWSKI Stephane SCE/IBNF; rtgwg@iet=
f.org
Subject: RE: LFA manageability : per AF config =3D> feedback required

Pushpassis -

From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Pushpasis Sarkar
Sent: Friday, February 20, 2015 3:28 AM
To: Jeff Tantsura; stephane.litkowski@orange.com<mailto:stephane.litkowski@=
orange.com>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Subject: Re: LFA manageability : per AF config =3D> feedback required

HI Jeff et al,

I can think of a reason to have a knob per-level(or per-area) or per ISIS t=
opology(note in ISIS a topology in ISIS always corresponds to a single AF,)

[Les:] This is a common mistake to make. If one simply uses RFC 5308, then =
IPv6 prefixes can be advertised in the same topology as IPv4 (MTID #0) - an=
d there are implementations which support this. More generally, from the pr=
otocol's POV a given topology can support any combinations of address famil=
ies. It is only a convention because of the reserved MTIDs specified in RFC=
 5120 that certain MTIDs are "IPv6 only". But if one looks at the protocol =
capabilities such a restriction does not exist in general.

Interestingly you contradicted yourself below. :)
But I did want to set the record straight on this point - hopefully we are =
in agreement.

and per realm and topology in OSPF. But I cannot think of a reason of why w=
ithin the same topology we need another set of knobs for each AF. Here, by =
AF I understand IPV4 or IPv6.

When both IPV4 and IPV6 are part of the same IGP topology, there is only on=
e set of backup computations needed to protect both IPV4 and IPv6 traffic.

Also I cannot think of any motivation for an operator to turn on protection=
 on only one AF and does not want to turn on for the other even if both AFs=
 has been deployed for normal forwarding.

[Les:] I think your point here is that the LFA calculation is AF independen=
t within a given topology - but resources are consumed independent of how m=
any computations are required- giving an operator the ability to determine =
which prefixes are most critical seems useful. That could be per AF or per =
prefix.

   Les

Thanks
-Pushpasis

From: Jeff Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericss=
on.com>>
Date: Friday, February 20, 2015 at 12:59 PM
To: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>" <=
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, "rtgw=
g@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: Re: LFA manageability : per AF config =3D> feedback required

Hi Stephane,

/chair hat off

IMO in disjoined topologies one should have flexibility to enable/disable L=
FA as per AF.


Cheers,
Jeff

From: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>"=
 <stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>
Date: Thursday, February 19, 2015 at 11:21 PM
To: "rtgwg@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ie=
tf.org>>
Subject: LFA manageability : per AF config =3D> feedback required

Hi Folks,

As you know, LFA manageability draft is in final phasis ...
The current document states per AF granularity activation as a SHOULD.
"
5.1<https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#secti=
on-5.1>.  LFA enabling/disabling scope





   The granularity of LFA activation should be controlled (as alternate

   nexthop consume memory in forwarding plane).



   An implementation of LFA SHOULD allow its activation with the

   following criteria:



   o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,

      LDP IPv6 unicast ...



   o  Per routing context : VRF, virtual/logical router, global routing

      table, ...


"

In the framework of ISIS/OSPF yang modelization, we are challenging this st=
atement, do we really need to force implementation to support this "per AF"=
 granularity ?

Please provide as soon as possible your feedback on this and also provide c=
lear drivers to support or not per AF activation of LFA.


Thanks for your help !


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/IBNF/ENDD/NDE
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>



___________________________________________________________________________=
______________________________________________



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_9E32478DFA9976438E7A22F69B08FF9215C157ACOPEXCLILM34corp_
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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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.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";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
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;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] I think y=
our point here is that the LFA calculation is AF independent within a given=
 topology &#8211; but resources are consumed independent of how many comput=
ations are required- giving an operator the
 ability to determine which prefixes are most critical seems useful. That c=
ould be per AF or per prefix.<o:p></o:p></span></i></b></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">[SLI] Agree but is the=
 &#8220;resource saving&#8221; point strong enough to mandate per AF activa=
tion ?<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 0in =
0in 0in">
<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;"> Les Gins=
berg (ginsberg) [mailto:ginsberg@cisco.com]
<br>
<b>Sent:</b> Monday, February 23, 2015 05:01<br>
<b>To:</b> Pushpasis Sarkar; Jeff Tantsura; LITKOWSKI Stephane SCE/IBNF; rt=
gwg@ietf.org<br>
<b>Subject:</b> RE: LFA manageability : per AF config =3D&gt; feedback requ=
ired<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">Pushpassis -<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 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>Pushpasis Sarkar<br>
<b>Sent:</b> Friday, February 20, 2015 3:28 AM<br>
<b>To:</b> Jeff Tantsura; <a href=3D"mailto:stephane.litkowski@orange.com">=
stephane.litkowski@orange.com</a>;
<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
<b>Subject:</b> Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">HI Jeff=
 et al,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I can t=
hink of a reason to have a knob per-level(or per-area) or per ISIS topology=
(note in ISIS a topology in ISIS always corresponds to a single AF,)</span>=
<span style=3D"font-size:10.5pt;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] This is a=
 common mistake to make. If one simply uses RFC 5308, then IPv6 prefixes ca=
n be advertised in the same topology as IPv4 (MTID #0) &#8211; and there ar=
e implementations which support this. More
 generally, from the protocol&#8217;s POV a given topology can support any =
combinations of address families. It is only a convention because of the re=
served MTIDs specified in RFC 5120 that certain MTIDs are &#8220;IPv6 only&=
#8221;. But if one looks at the protocol capabilities
 such a restriction does not exist in general.<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">Interestingly yo=
u contradicted yourself below.
</span></i></b><b><i><span style=3D"font-family:Wingdings;color:#1F497D">J<=
/span><span style=3D"color:#1F497D"><o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">But I did want t=
o set the record straight on this point &#8211; hopefully we are in agreeme=
nt.<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">and per=
 realm and topology in OSPF. But I cannot think of a reason of why within t=
he same topology we need another set of knobs for each AF. Here, by AF I un=
derstand IPV4 or IPv6.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">When bo=
th IPV4 and IPV6 are part of the same IGP topology, there is only one set o=
f backup computations needed to protect both IPV4 and IPv6 traffic.<o:p></o=
:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Also I =
cannot think of any motivation for an operator to turn on protection on onl=
y one AF and does not want to turn on for the other even if both AFs has be=
en deployed for normal forwarding.&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] I think y=
our point here is that the LFA calculation is AF independent within a given=
 topology &#8211; but resources are consumed independent of how many comput=
ations are required- giving an operator the
 ability to determine which prefixes are most critical seems useful. That c=
ould be per AF or per prefix.<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">&nbsp;&nbsp; Les=
<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Thanks<=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">-Pushpa=
sis<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">Jeff Tantsura &lt;<a href=3D"mailto:jeff.tantsura@e=
ricsson.com">jeff.tantsura@ericsson.com</a>&gt;<br>
<b>Date: </b>Friday, February 20, 2015 at 12:59 PM<br>
<b>To: </b>&quot;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.=
litkowski@orange.com</a>&quot; &lt;<a href=3D"mailto:stephane.litkowski@ora=
nge.com">stephane.litkowski@orange.com</a>&gt;, &quot;<a href=3D"mailto:rtg=
wg@ietf.org">rtgwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.org"=
>rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Hi Step=
hane,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">/chair =
hat off<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">IMO in =
disjoined topologies one should have flexibility to enable/disable LFA as p=
er AF.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Cheers,=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Jeff<o:=
p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">&quot;<a href=3D"mailto:stephane.litkowski@orange.c=
om">stephane.litkowski@orange.com</a>&quot; &lt;<a href=3D"mailto:stephane.=
litkowski@orange.com">stephane.litkowski@orange.com</a>&gt;<br>
<b>Date: </b>Thursday, February 19, 2015 at 11:21 PM<br>
<b>To: </b>&quot;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&quot;=
 &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>LFA manageability : per AF config =3D&gt; feedback required=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<blockquote style=3D"border:none;border-left:solid #B5C4DF 4.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin=
-bottom:5.0pt" id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Hi Folks,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">As you know, LFA managea=
bility draft is in final phasis &#8230;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">The current document sta=
tes per AF granularity activation as a SHOULD.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&#8220;<o:p></o:p></span=
></p>
<h3 style=3D"page-break-before:always"><a name=3D"section-5.1"></a><span st=
yle=3D"color:black"><a href=3D"https://tools.ietf.org/html/draft-ietf-rtgwg=
-lfa-manageability-07#section-5.1"><span lang=3D"EN" style=3D"font-size:10.=
0pt;color:black;text-decoration:none">5.1</span></a></span><span lang=3D"EN=
" style=3D"font-size:10.0pt;color:black">.&nbsp;
 LFA enabling/disabling scope</span><span style=3D"color:black"><o:p></o:p>=
</span></h3>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; The granularity of LFA activation should=
 be controlled (as alternate</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; nexthop consume memory in forwarding pla=
ne).</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; An implementation of LFA SHOULD allow it=
s activation with the</span><span style=3D"color:black"><o:p></o:p></span><=
/pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; following criteria:</span><span style=3D=
"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; o&nbsp; Per address-family : ipv4 unicas=
t, ipv6 unicast, LDP IPv4 unicast,</span><span style=3D"color:black"><o:p><=
/o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LDP IPv6 unicast ...</=
span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; o&nbsp; Per routing context : VRF, virtu=
al/logical router, global routing</span><span style=3D"color:black"><o:p></=
o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; table, ...</span><span=
 style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<p class=3D"MsoNormal"><span style=3D"color:black">&#8220;<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">In the framework of ISIS=
/OSPF yang modelization, we are challenging this statement, do we really ne=
ed to force implementation to support this &#8220;per AF&#8221; granularity=
 ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Please provide as soon a=
s possible your feedback on this and also provide clear drivers to support =
or not per AF activation of LFA.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Thanks for your help !<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black"><a href=3D"http://www.or=
ange.com/"><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;;text-decoration:none"><img border=3D"0" width=3D"=
40" height=3D"40" id=3D"Picture_x0020_1" src=3D"cid:image001.gif@01D04F3F.E=
1944930" alt=3D"Orange logo"></span></a><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;color:bl=
ack">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:black">Stephane Litkowski
</span></b><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Network Architect
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Orange/SCE/EQUANT/IBNF/ENDD/NDE
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Orange Expert Fut=
ure Networks</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<span style=3D"color:black;text-decoration:none">&#43;33 2 23 28 49 83 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;;color:black"><br>
</span><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:black">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<span style=3D"color:black;text-decoration:none">&#43;33 6 37 86 97 52 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;;color:black"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><span style=3D"font-size:1=
0.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#FF6600;te=
xt-decoration:none">stephane.litkowski@orange.com</span></a></span><span st=
yle=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span lang=3D"FR" style=
=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<pre><span style=3D"color:black">__________________________________________=
___________________________________________________________________________=
____<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Ce message et ses pieces jointes peuvent c=
ontenir des informations confidentielles ou privilegiees et ne doivent donc=
<o:p></o:p></span></pre>
<pre><span style=3D"color:black">pas etre diffuses, exploites ou copies san=
s autorisation. Si vous avez recu ce message par erreur, veuillez le signal=
er<o:p></o:p></span></pre>
<pre><span style=3D"color:black">a l'expediteur et le detruire ainsi que le=
s pieces jointes. Les messages electroniques etant susceptibles d'alteratio=
n,<o:p></o:p></span></pre>
<pre><span style=3D"color:black">Orange decline toute responsabilite si ce =
message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">This message and its attachments may conta=
in confidential or privileged information that may be protected by law;<o:p=
></o:p></span></pre>
<pre><span style=3D"color:black">they should not be distributed, used or co=
pied without authorisation.<o:p></o:p></span></pre>
<pre><span style=3D"color:black">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 style=3D"color:black">As emails may be altered, Orange is not li=
able for messages that have been modified, changed or falsified.<o:p></o:p>=
</span></pre>
<pre><span style=3D"color:black">Thank you.<o:p></o:p></span></pre>
</div>
</div>
</blockquote>
</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_9E32478DFA9976438E7A22F69B08FF9215C157ACOPEXCLILM34corp_--

--_004_9E32478DFA9976438E7A22F69B08FF9215C157ACOPEXCLILM34corp_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: inline; filename="image001.gif"; size=381;
	creation-date="Mon, 23 Feb 2015 07:09:59 GMT";
	modification-date="Mon, 23 Feb 2015 07:09:59 GMT"
Content-ID: <image001.gif@01D04F3F.E1944930>
Content-Transfer-Encoding: base64

R0lGODlhKAAoAMQAAP+MQP+zgP/17//s3/+DMP/iz/+fYP+8j/9wEP95IP/Gn/+WUP/Pr/+pcP/Z
v/////9mAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAAA
AAAALAAAAAAoACgAAAX6oAONZGmeaEqKauum7Cu/8Wyj9a2P+X73vhkwSCPuhkYVMolj2pbOEjTK
oxatrSlVG+U6vUxwUmwkE81BtE99xGbdSjhMPgo4BAoA+wUICAR6IwQODwMNEAcOigAFhQYQDgoD
DwcQBJOKBIOFDQmaCCyTB416hQcBBQuTEA8Cow8EBQINpHcGhAkrEAkPChAAD3YPCLuSDw+sIgEP
wCILzK0OjY9VBJS/wYQjfwaNyRDLzRAG0AMB5wC6ENyEt8jWDAsCyA/KzJN+zLILqLlVv/OuaYPU
alU9cMwuPSCl8AEDYv8EQbwRgAEABcziJFl2bMmeEQgATEwRAgA7

--_004_9E32478DFA9976438E7A22F69B08FF9215C157ACOPEXCLILM34corp_--


From nobody Mon Feb 23 04:45:30 2015
Return-Path: <lhotka@nic.cz>
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 93B151A1A88; Mon, 23 Feb 2015 04:45:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6] 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 Ibxv8KgXWyJ7; Mon, 23 Feb 2015 04:45:27 -0800 (PST)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id 3693B1A1A8B; Mon, 23 Feb 2015 04:45:27 -0800 (PST)
Received: from localhost (unknown [195.113.220.110]) by trail.lhotka.name (Postfix) with ESMTPSA id 0F3AE1CC0249; Mon, 23 Feb 2015 13:45:32 +0100 (CET)
From: Ladislav Lhotka <lhotka@nic.cz>
To: Thomas Morin <thomas.morin@orange.com>, "Acee Lindem \(acee\)" <acee@cisco.com>, Routing YANG <rtg-yang-coord@ietf.org>, Routing WG <rtgwg@ietf.org>
Subject: Re: rtg-cfg hierachy (PLEASE REPLY TO THIS ONE WITH THE CORRECT MAIL ALIASES)
In-Reply-To: <54E47928.8050108@orange.com>
References: <14011_1423852286_54DE42FE_14011_2207_1_D103AD28.E652%acee@cisco.com> <54E47928.8050108@orange.com>
User-Agent: Notmuch/0.19 (http://notmuchmail.org) Emacs/24.4.51.2 (x86_64-apple-darwin14.0.0)
Date: Mon, 23 Feb 2015 13:45:25 +0100
Message-ID: <m2a904zti2.fsf@birdie.labs.nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/mDMKpMwllG0n1jFlqC_azq3sYQk>
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, 23 Feb 2015 12:45:29 -0000

Hi Thomas,

I apologize for a late response, I was on holiday last week.

Thomas Morin <thomas.morin@orange.com> writes:

> Hi Acee, Lada,
>
> It seems that my comment that you quote was more related to filters than=
=20
> to routing tables, and indeed, *filters* were moved from "router" to=20
> "global" in revision -03 that followed my review.

Right, but each filter could then be specified for either
"connected-routing-table" or "recipient-routing-table", and if the
'remote' routing table is in a different routing instance, it IMO makes
more sense to have routing tables (RIBs) as global objects
accessible to all routing instances.

In fact, even if RIBs are routing-instance specific, it will still be
possible to access a RIB in a foreign routing instance, it will just be
more laborious - one will have to specify the target routing instance &
RIB. Also, names of RIBs will no more be unique system-wide.

>
> Additionally, Lada, you say that based on my comments "in rev. -03 the=20
> list of RIBs (then called "routing-table") was the moved out of the=20
> routing instance (then called "router") and became global.". But if I=20
> look at -03, "routing-table" is still a child of "router".  The change=20
> to make "routing-table" global was made in -05.
>
> I guess you need to find out what was the motivation for the change in=20
> -05, a few months after my initial comments were address.

Yes, you are right, it seems the immediate motivation for this change
was this review by Martin Bjorklund:

http://www.ietf.org/mail-archive/web/netmod/current/msg06962.html

Thanks, Lada

>
> Best,
>
> -Thomas
>
>
>
>
>
> 2015-02-13, Acee Lindem (acee):
>>
>> Hi Lada, Thomas,
>>
>> On 2/13/15, 5:10 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:
>>
>>> Hi,
>>>
>>> "Acee Lindem (acee)" <acee@cisco.com> writes:
>>>
>>>> Hi Thomas,
>>>>
>>>> It is my understanding that the RIBs were moved out of the
>>>> routing-instance in response to your comment that a RIB would need to =
be
>>>> attached to multiple routing instances. I don=C2=B9t agree with this
>>>> model. I
>>>
>>> Acee refers to this comment that Thomas made in his review of
>>> draft-ietf-netmod-routing-cfg-02 on 2012-03-23:
>>>
>>> "Allowing multiple "routers" is a good starting point for using these
>>> specs in the context of RFC4364 (MPLS/BGP IP VPNs). However, if I
>>> understand correctly Yang syntax, the way the filters are defined would
>>> not work in the context of RFC4364, where a BGP routing instance in the
>>> master "router" exports selected routes in each of the routing table of
>>> each VPN (VRF).  The VRF also export routes to the master instance."
>>>
>>> And indeed, in rev. -03 the list of RIBs (then called "routing-table")
>>> was the moved out of the routing instance (then called "router") and
>>> became global.
>>
>> Then do you agree to move the RIBs back into the routing-instance? Both
>> the BGP YANG drafts model L3VPN definitions under the corresponding
>> address family in BGP.
>>
>> http://www.ietf.org/id/draft-shaikh-idr-bgp-model-00.txt
>> http://www.ietf.org/id/draft-zhdankin-idr-bgp-cfg-00.txt
>>
>> Thanks,
>> Acee
>>
>>
>>
>>>
>>> Lada
>>>
>>>> believe that a routing instance implies a VRF, virtual router or
>>>> something
>>>> in between and that a RIB should be associated with one and only one
>>>> routing instance. Additionally, I feel that RIBs are basically passive
>>>> entities with respect to import/export of routes between RIBs in the
>>>> same
>>>> or other routing-instances. Rather, all import/export is under the
>>>> control
>>>> of a routing-protocol. For example, this would be handled by a BGP
>>>> routing-protocol instance for L3VPNs.
>>>>
>>>> I=C2=B9d like to get the opinions of others on this fundamental aspect=
 of the
>>>> rtg-cfg model.
>>>>
>>>> Thanks,
>>>> Acee
>>>>
>>>>
>>>
>>> --
>>> Ladislav Lhotka, CZ.NIC Labs
>>> PGP Key ID: E74E8C0C
>>
>>
>>
>

--=20
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C


From nobody Mon Feb 23 05:05:23 2015
Return-Path: <lhotka@nic.cz>
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 A3A271A1A9F; Mon, 23 Feb 2015 05:05:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6] 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 NCPGnZnzTJYt; Mon, 23 Feb 2015 05:05:16 -0800 (PST)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id 172111A1A9E; Mon, 23 Feb 2015 05:05:16 -0800 (PST)
Received: from localhost (unknown [195.113.220.110]) by trail.lhotka.name (Postfix) with ESMTPSA id 38C871CC0249; Mon, 23 Feb 2015 14:05:22 +0100 (CET)
From: Ladislav Lhotka <lhotka@nic.cz>
To: "Acee Lindem \(acee\)" <acee@cisco.com>, Thomas Morin <thomas.morin@orange.com>, Routing YANG <rtg-yang-coord@ietf.org>, Routing WG <rtgwg@ietf.org>
Subject: Re: rtg-cfg hierachy    (Indentation in hierarchy corrected)
In-Reply-To: <D10A678C.EB2C%acee@cisco.com>
References: <D10A678C.EB2C%acee@cisco.com>
User-Agent: Notmuch/0.19 (http://notmuchmail.org) Emacs/24.4.51.2 (x86_64-apple-darwin14.0.0)
Date: Mon, 23 Feb 2015 14:05:15 +0100
Message-ID: <m27fv8zsl0.fsf@birdie.labs.nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/Vkp2LwjrCfAm6k-GE9boOA99Xew>
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, 23 Feb 2015 13:05:18 -0000

"Acee Lindem (acee)" <acee@cisco.com> writes:

> Thanks Thomas for the clarification.
>
> I=E2=80=99d like to then suggest we change the rtg-cfg model hierarchy to=
 reflect
> what most routing device implementations.
> There is a RIB (you can call it a default-RIB if you like) for every
> Address Family (AF). Multiple RIBs per AF is not widely implemented and I
> don=E2=80=99t see it becoming more prevalent. Hence, I agree it should be=
 a
> feature. The one implementation I=E2=80=99m familiar with is multiple top=
ology
> routing (e.g., RFC 4915), where RIB corresponds to a FIB that is selected
> based on packet marking. Does anyone have any other examples?

Another example could be a separate RIB for RPF, to be used e.g. by PIM.

>
> This would imply that RIBs are within a routing-instance and that

It seems (Junos experts, please confirm) that in Junos user-defined
routing tables can be specified both globally and per routing-instance:

http://www.juniper.net/documentation/en_US/junos14.2/topics/reference/confi=
guration-statement/export-rib-edit-routing-options.html

>From the viewpoint of the data model, I think it is generally easier for
an implementation to restrict access to each RIB to a single routing
instance than allow different routing instances to share a RIB, if each
RIB would have to be inside a routing instance.


Lada

> routing-protocols within the routing-instance can operate on these RIBs.
> There is no requirement connect RIBs to routing-protocols or to form
> connections between RIBs.
>
> This would give us a high-level hierarchy of:
>
> rw routing-instance* [name]
>       |  +--rw address-family
>       |  |  |--rw default-rib* [address-family]
>       |  |  +--rw non-default-ribs (feature)
>       |  +--rw routing-protocols
>       |     +=E2=80=95--rw routing-protocol* [type name]
>
> I intensionally left out the interfaces since I don=E2=80=99t like some m=
odels
> augmenting or referencing the ietf-interface list and others augmenting or
> referencing the list in our rtg-cfg draft.
>
> Thanks,
> Acee
>
>
>
>
> On 2/18/15, 6:36 AM, "Thomas Morin" <thomas.morin@orange.com> wrote:
>
>>Hi Acee, Lada,
>>
>>It seems that my comment that you quote was more related to filters than
>>to routing tables, and indeed, *filters* were moved from "router" to
>>"global" in revision -03 that followed my review.
>>
>>Additionally, Lada, you say that based on my comments "in rev. -03 the
>>list of RIBs (then called "routing-table") was the moved out of the
>>routing instance (then called "router") and became global.". But if I
>>look at -03, "routing-table" is still a child of "router".  The change
>>to make "routing-table" global was made in -05.
>>
>>I guess you need to find out what was the motivation for the change in
>>-05, a few months after my initial comments were address.
>>
>>Best,
>>
>>-Thomas
>>
>>
>>
>>
>>
>>2015-02-13, Acee Lindem (acee):
>>>
>>> Hi Lada, Thomas,
>>>
>>> On 2/13/15, 5:10 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:
>>>
>>>> Hi,
>>>>
>>>> "Acee Lindem (acee)" <acee@cisco.com> writes:
>>>>
>>>>> Hi Thomas,
>>>>>
>>>>> It is my understanding that the RIBs were moved out of the
>>>>> routing-instance in response to your comment that a RIB would need to
>>>>>be
>>>>> attached to multiple routing instances. I don=C2=B9t agree with this
>>>>> model. I
>>>>
>>>> Acee refers to this comment that Thomas made in his review of
>>>> draft-ietf-netmod-routing-cfg-02 on 2012-03-23:
>>>>
>>>> "Allowing multiple "routers" is a good starting point for using these
>>>> specs in the context of RFC4364 (MPLS/BGP IP VPNs). However, if I
>>>> understand correctly Yang syntax, the way the filters are defined would
>>>> not work in the context of RFC4364, where a BGP routing instance in the
>>>> master "router" exports selected routes in each of the routing table of
>>>> each VPN (VRF).  The VRF also export routes to the master instance."
>>>>
>>>> And indeed, in rev. -03 the list of RIBs (then called "routing-table")
>>>> was the moved out of the routing instance (then called "router") and
>>>> became global.
>>>
>>> Then do you agree to move the RIBs back into the routing-instance? Both
>>> the BGP YANG drafts model L3VPN definitions under the corresponding
>>> address family in BGP.
>>>
>>> http://www.ietf.org/id/draft-shaikh-idr-bgp-model-00.txt
>>> http://www.ietf.org/id/draft-zhdankin-idr-bgp-cfg-00.txt
>>>
>>> Thanks,
>>> Acee
>>>
>>>
>>>
>>>>
>>>> Lada
>>>>
>>>>> believe that a routing instance implies a VRF, virtual router or
>>>>> something
>>>>> in between and that a RIB should be associated with one and only one
>>>>> routing instance. Additionally, I feel that RIBs are basically passive
>>>>> entities with respect to import/export of routes between RIBs in the
>>>>> same
>>>>> or other routing-instances. Rather, all import/export is under the
>>>>> control
>>>>> of a routing-protocol. For example, this would be handled by a BGP
>>>>> routing-protocol instance for L3VPNs.
>>>>>
>>>>> I=C2=B9d like to get the opinions of others on this fundamental aspec=
t of
>>>>>the
>>>>> rtg-cfg model.
>>>>>
>>>>> Thanks,
>>>>> Acee
>>>>>
>>>>>
>>>>
>>>> --
>>>> Ladislav Lhotka, CZ.NIC Labs
>>>> PGP Key ID: E74E8C0C
>>>
>>>
>>>
>>
>
>

--=20
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C


From nobody Mon Feb 23 07:55:43 2015
Return-Path: <ginsberg@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 EA17D1A1B4C for <rtgwg@ietfa.amsl.com>; Mon, 23 Feb 2015 07:55:41 -0800 (PST)
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_84=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 IEG5myF8Gmdv for <rtgwg@ietfa.amsl.com>; Mon, 23 Feb 2015 07:55:36 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2E4A1A1AAA for <rtgwg@ietf.org>; Mon, 23 Feb 2015 07:55:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=37166; q=dns/txt; s=iport; t=1424706936; x=1425916536; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=dAMgImkphQ1/WC44EfTtIQG5ATt68LcG6tkOJEIRtVo=; b=VxgbNsGGsI8DeCsL+3oEWRMZSN6DPUN3i7j21y3MWNI+YZ+k6zSci6Xo AKtz/Uw5JZ+oLFEvv8vG5/8uPxi36b6vUXjWGXurD6/efafVadQx19lyc pBoJIMwEyz8P2Xt92ArRIUyNWqtuB9N6ZYRjfcrNj+X2IxeRMjA5wWG+H A=;
X-Files: image001.gif : 381
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CsBQA+TOtU/4cNJK1bgkNDUloEwFeCOoVzAoEhQwEBAQEBAXyEDwEBAQQFIAgBNgccAgIBCAcKAwEBAQYBAgIWAQYHAgUQAQMCCQwUCQgBAQQBEQEGAgaIDQMRDc1NA4U2AQEBAQEBAQEBAQEBAQEBAQEBAQEBFwSLD4FPgjQJEQEfBREKDAEKAQaDEYEUBYYVhA2DP4EnSoMNAVCHADiCXYtFgz4iggIcgVBvAQEBAYEHOX8BAQE
X-IronPort-AV: E=Sophos;i="5.09,631,1418083200";  d="gif'147?scan'147,208,217,147";a="398367717"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-5.cisco.com with ESMTP; 23 Feb 2015 15:55:35 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t1NFtYRQ011881 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 23 Feb 2015 15:55:34 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.138]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0195.001; Mon, 23 Feb 2015 09:55:34 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "Pushpasis Sarkar" <psarkar@juniper.net>, Jeff Tantsura <jeff.tantsura@ericsson.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AdBM3SH2oNl2urLXSA+s5ntM7pKOsP//0WCAgADZjID//DGyQIAIPSwA///UY1A=
Date: Mon, 23 Feb 2015 15:55:32 +0000
Message-ID: <F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71@xmb-aln-x02.cisco.com>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <5876_1424675401_54EAD249_5876_2527_11_9E32478DFA9976438E7A22F69B08FF9215C157AC@OPEXCLILM34.corporate.adroot.infra.ftgroup>
In-Reply-To: <5876_1424675401_54EAD249_5876_2527_11_9E32478DFA9976438E7A22F69B08FF9215C157AC@OPEXCLILM34.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.24.29.122]
Content-Type: multipart/related; boundary="_004_F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71xmbalnx02ciscoc_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/C3NZHDRvYB-GEt3csxy7w8dUEhM>
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, 23 Feb 2015 15:55:42 -0000

--_004_F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71xmbalnx02ciscoc_
Content-Type: multipart/alternative;
	boundary="_000_F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71xmbalnx02ciscoc_"

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

Stephane -

I can imagine cases in which the per AF enabling might make sense (e.g. whe=
n the network associated w one address family is deemed non-critical).

Section 5.1 is a SHOULD - as is most of the document. It is therefore a sug=
gestion as to what an implementation should provide. If a given implementer=
 thinks this is either too onerous or not useful they can omit it w/o being=
 in violation. But I see no reason to eliminate this - and in actual practi=
ce I would expect the cost of supporting such a knob to be low cost. It is =
hard for me to see this as controversial.

   Les


From: stephane.litkowski@orange.com [mailto:stephane.litkowski@orange.com]
Sent: Sunday, February 22, 2015 11:10 PM
To: Les Ginsberg (ginsberg); Pushpasis Sarkar; Jeff Tantsura; rtgwg@ietf.or=
g
Subject: RE: LFA manageability : per AF config =3D> feedback required

[Les:] I think your point here is that the LFA calculation is AF independen=
t within a given topology - but resources are consumed independent of how m=
any computations are required- giving an operator the ability to determine =
which prefixes are most critical seems useful. That could be per AF or per =
prefix.

[SLI] Agree but is the "resource saving" point strong enough to mandate per=
 AF activation ?

From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
Sent: Monday, February 23, 2015 05:01
To: Pushpasis Sarkar; Jeff Tantsura; LITKOWSKI Stephane SCE/IBNF; rtgwg@iet=
f.org<mailto:rtgwg@ietf.org>
Subject: RE: LFA manageability : per AF config =3D> feedback required

Pushpassis -

From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Pushpasis Sarkar
Sent: Friday, February 20, 2015 3:28 AM
To: Jeff Tantsura; stephane.litkowski@orange.com<mailto:stephane.litkowski@=
orange.com>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Subject: Re: LFA manageability : per AF config =3D> feedback required

HI Jeff et al,

I can think of a reason to have a knob per-level(or per-area) or per ISIS t=
opology(note in ISIS a topology in ISIS always corresponds to a single AF,)

[Les:] This is a common mistake to make. If one simply uses RFC 5308, then =
IPv6 prefixes can be advertised in the same topology as IPv4 (MTID #0) - an=
d there are implementations which support this. More generally, from the pr=
otocol's POV a given topology can support any combinations of address famil=
ies. It is only a convention because of the reserved MTIDs specified in RFC=
 5120 that certain MTIDs are "IPv6 only". But if one looks at the protocol =
capabilities such a restriction does not exist in general.

Interestingly you contradicted yourself below. :)
But I did want to set the record straight on this point - hopefully we are =
in agreement.

and per realm and topology in OSPF. But I cannot think of a reason of why w=
ithin the same topology we need another set of knobs for each AF. Here, by =
AF I understand IPV4 or IPv6.

When both IPV4 and IPV6 are part of the same IGP topology, there is only on=
e set of backup computations needed to protect both IPV4 and IPv6 traffic.

Also I cannot think of any motivation for an operator to turn on protection=
 on only one AF and does not want to turn on for the other even if both AFs=
 has been deployed for normal forwarding.

[Les:] I think your point here is that the LFA calculation is AF independen=
t within a given topology - but resources are consumed independent of how m=
any computations are required- giving an operator the ability to determine =
which prefixes are most critical seems useful. That could be per AF or per =
prefix.

   Les

Thanks
-Pushpasis

From: Jeff Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericss=
on.com>>
Date: Friday, February 20, 2015 at 12:59 PM
To: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>" <=
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, "rtgw=
g@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: Re: LFA manageability : per AF config =3D> feedback required

Hi Stephane,

/chair hat off

IMO in disjoined topologies one should have flexibility to enable/disable L=
FA as per AF.


Cheers,
Jeff

From: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>"=
 <stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>
Date: Thursday, February 19, 2015 at 11:21 PM
To: "rtgwg@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ie=
tf.org>>
Subject: LFA manageability : per AF config =3D> feedback required

Hi Folks,

As you know, LFA manageability draft is in final phasis ...
The current document states per AF granularity activation as a SHOULD.
"
5.1<https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#secti=
on-5.1>.  LFA enabling/disabling scope





   The granularity of LFA activation should be controlled (as alternate

   nexthop consume memory in forwarding plane).



   An implementation of LFA SHOULD allow its activation with the

   following criteria:



   o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,

      LDP IPv6 unicast ...



   o  Per routing context : VRF, virtual/logical router, global routing

      table, ...


"

In the framework of ISIS/OSPF yang modelization, we are challenging this st=
atement, do we really need to force implementation to support this "per AF"=
 granularity ?

Please provide as soon as possible your feedback on this and also provide c=
lear drivers to support or not per AF activation of LFA.


Thanks for your help !


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/IBNF/ENDD/NDE
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>



___________________________________________________________________________=
______________________________________________



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_F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71xmbalnx02ciscoc_
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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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.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";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Stephane &#8211;<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 can imagine cases in=
 which the per AF enabling might make sense (e.g. when the network associat=
ed w one address family is deemed non-critical).<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">Section 5.1 is a SHOUL=
D &#8211; as is most of the document. It is therefore a suggestion as to wh=
at an implementation should provide. If a given implementer thinks this is =
either too onerous or not useful they can
 omit it w/o being in violation. But I see no reason to eliminate this &#82=
11; and in actual practice I would expect the cost of supporting such a kno=
b to be low cost. It is hard for me to see this as controversial.<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; Les<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 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;"> stephane=
.litkowski@orange.com [mailto:stephane.litkowski@orange.com]
<br>
<b>Sent:</b> Sunday, February 22, 2015 11:10 PM<br>
<b>To:</b> Les Ginsberg (ginsberg); Pushpasis Sarkar; Jeff Tantsura; rtgwg@=
ietf.org<br>
<b>Subject:</b> RE: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] I think y=
our point here is that the LFA calculation is AF independent within a given=
 topology &#8211; but resources are consumed independent of how many comput=
ations are required- giving an operator the
 ability to determine which prefixes are most critical seems useful. That c=
ould be per AF or per prefix.<o:p></o:p></span></i></b></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">[SLI] Agree but is the=
 &#8220;resource saving&#8221; point strong enough to mandate per AF activa=
tion ?<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 0in =
0in 0in">
<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;"> Les Gins=
berg (ginsberg) [<a href=3D"mailto:ginsberg@cisco.com">mailto:ginsberg@cisc=
o.com</a>]
<br>
<b>Sent:</b> Monday, February 23, 2015 05:01<br>
<b>To:</b> Pushpasis Sarkar; Jeff Tantsura; LITKOWSKI Stephane SCE/IBNF; <a=
 href=3D"mailto:rtgwg@ietf.org">
rtgwg@ietf.org</a><br>
<b>Subject:</b> RE: LFA manageability : per AF config =3D&gt; feedback requ=
ired<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">Pushpassis -<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 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>Pushpasis Sarkar<br>
<b>Sent:</b> Friday, February 20, 2015 3:28 AM<br>
<b>To:</b> Jeff Tantsura; <a href=3D"mailto:stephane.litkowski@orange.com">=
stephane.litkowski@orange.com</a>;
<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
<b>Subject:</b> Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">HI Jeff=
 et al,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I can t=
hink of a reason to have a knob per-level(or per-area) or per ISIS topology=
(note in ISIS a topology in ISIS always corresponds to a single AF,)</span>=
<span style=3D"font-size:10.5pt;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] This is a=
 common mistake to make. If one simply uses RFC 5308, then IPv6 prefixes ca=
n be advertised in the same topology as IPv4 (MTID #0) &#8211; and there ar=
e implementations which support this. More
 generally, from the protocol&#8217;s POV a given topology can support any =
combinations of address families. It is only a convention because of the re=
served MTIDs specified in RFC 5120 that certain MTIDs are &#8220;IPv6 only&=
#8221;. But if one looks at the protocol capabilities
 such a restriction does not exist in general.<o:p></o:p></span></i></b></p=
>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">Interestingly yo=
u contradicted yourself below.
</span></i></b><b><i><span style=3D"font-family:Wingdings;color:#1F497D">J<=
/span><span style=3D"color:#1F497D"><o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">But I did want t=
o set the record straight on this point &#8211; hopefully we are in agreeme=
nt.<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">and per=
 realm and topology in OSPF. But I cannot think of a reason of why within t=
he same topology we need another set of knobs for each AF. Here, by AF I un=
derstand IPV4 or IPv6.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">When bo=
th IPV4 and IPV6 are part of the same IGP topology, there is only one set o=
f backup computations needed to protect both IPV4 and IPv6 traffic.<o:p></o=
:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Also I =
cannot think of any motivation for an operator to turn on protection on onl=
y one AF and does not want to turn on for the other even if both AFs has be=
en deployed for normal forwarding.&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] I think y=
our point here is that the LFA calculation is AF independent within a given=
 topology &#8211; but resources are consumed independent of how many comput=
ations are required- giving an operator the
 ability to determine which prefixes are most critical seems useful. That c=
ould be per AF or per prefix.<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">&nbsp;&nbsp; Les=
<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Thanks<=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">-Pushpa=
sis<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">Jeff Tantsura &lt;<a href=3D"mailto:jeff.tantsura@e=
ricsson.com">jeff.tantsura@ericsson.com</a>&gt;<br>
<b>Date: </b>Friday, February 20, 2015 at 12:59 PM<br>
<b>To: </b>&quot;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.=
litkowski@orange.com</a>&quot; &lt;<a href=3D"mailto:stephane.litkowski@ora=
nge.com">stephane.litkowski@orange.com</a>&gt;, &quot;<a href=3D"mailto:rtg=
wg@ietf.org">rtgwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.org"=
>rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Hi Step=
hane,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">/chair =
hat off<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">IMO in =
disjoined topologies one should have flexibility to enable/disable LFA as p=
er AF.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Cheers,=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Jeff<o:=
p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">&quot;<a href=3D"mailto:stephane.litkowski@orange.c=
om">stephane.litkowski@orange.com</a>&quot; &lt;<a href=3D"mailto:stephane.=
litkowski@orange.com">stephane.litkowski@orange.com</a>&gt;<br>
<b>Date: </b>Thursday, February 19, 2015 at 11:21 PM<br>
<b>To: </b>&quot;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&quot;=
 &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>LFA manageability : per AF config =3D&gt; feedback required=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<blockquote style=3D"border:none;border-left:solid #B5C4DF 4.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin=
-bottom:5.0pt" id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Hi Folks,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">As you know, LFA managea=
bility draft is in final phasis &#8230;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">The current document sta=
tes per AF granularity activation as a SHOULD.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&#8220;<o:p></o:p></span=
></p>
<h3 style=3D"page-break-before:always"><a name=3D"section-5.1"></a><span st=
yle=3D"color:black"><a href=3D"https://tools.ietf.org/html/draft-ietf-rtgwg=
-lfa-manageability-07#section-5.1"><span lang=3D"EN" style=3D"font-size:10.=
0pt;color:black;text-decoration:none">5.1</span></a></span><span lang=3D"EN=
" style=3D"font-size:10.0pt;color:black">.&nbsp;
 LFA enabling/disabling scope</span><span style=3D"color:black"><o:p></o:p>=
</span></h3>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; The granularity of LFA activation should=
 be controlled (as alternate</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; nexthop consume memory in forwarding pla=
ne).</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; An implementation of LFA SHOULD allow it=
s activation with the</span><span style=3D"color:black"><o:p></o:p></span><=
/pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; following criteria:</span><span style=3D=
"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; o&nbsp; Per address-family : ipv4 unicas=
t, ipv6 unicast, LDP IPv4 unicast,</span><span style=3D"color:black"><o:p><=
/o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LDP IPv6 unicast ...</=
span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; o&nbsp; Per routing context : VRF, virtu=
al/logical router, global routing</span><span style=3D"color:black"><o:p></=
o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; table, ...</span><span=
 style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<p class=3D"MsoNormal"><span style=3D"color:black">&#8220;<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">In the framework of ISIS=
/OSPF yang modelization, we are challenging this statement, do we really ne=
ed to force implementation to support this &#8220;per AF&#8221; granularity=
 ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Please provide as soon a=
s possible your feedback on this and also provide clear drivers to support =
or not per AF activation of LFA.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Thanks for your help !<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black"><a href=3D"http://www.or=
ange.com/"><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;;text-decoration:none"><img border=3D"0" width=3D"=
40" height=3D"40" id=3D"Picture_x0020_1" src=3D"cid:image001.gif@01D04F3D.8=
01259B0" alt=3D"Orange logo"></span></a><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;color:bl=
ack">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:black">Stephane Litkowski
</span></b><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Network Architect
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Orange/SCE/EQUANT/IBNF/ENDD/NDE
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Orange Expert Fut=
ure Networks</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<span style=3D"color:black;text-decoration:none">&#43;33 2 23 28 49 83 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;;color:black"><br>
</span><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:black">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<span style=3D"color:black;text-decoration:none">&#43;33 6 37 86 97 52 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;;color:black"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><span style=3D"font-size:1=
0.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#FF6600;te=
xt-decoration:none">stephane.litkowski@orange.com</span></a></span><span st=
yle=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span lang=3D"FR" style=
=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<pre><span style=3D"color:black">__________________________________________=
___________________________________________________________________________=
____<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Ce message et ses pieces jointes peuvent c=
ontenir des informations confidentielles ou privilegiees et ne doivent donc=
<o:p></o:p></span></pre>
<pre><span style=3D"color:black">pas etre diffuses, exploites ou copies san=
s autorisation. Si vous avez recu ce message par erreur, veuillez le signal=
er<o:p></o:p></span></pre>
<pre><span style=3D"color:black">a l'expediteur et le detruire ainsi que le=
s pieces jointes. Les messages electroniques etant susceptibles d'alteratio=
n,<o:p></o:p></span></pre>
<pre><span style=3D"color:black">Orange decline toute responsabilite si ce =
message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">This message and its attachments may conta=
in confidential or privileged information that may be protected by law;<o:p=
></o:p></span></pre>
<pre><span style=3D"color:black">they should not be distributed, used or co=
pied without authorisation.<o:p></o:p></span></pre>
<pre><span style=3D"color:black">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 style=3D"color:black">As emails may be altered, Orange is not li=
able for messages that have been modified, changed or falsified.<o:p></o:p>=
</span></pre>
<pre><span style=3D"color:black">Thank you.<o:p></o:p></span></pre>
</div>
</div>
</blockquote>
</div>
</div>
</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. Merci.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>This message and its attachments may contain confidential or privilege=
d information that may be protected by law;<o:p></o:p></pre>
<pre>they should not be distributed, used or copied without authorisation.<=
o:p></o:p></pre>
<pre>If you have received this email in error, please notify the sender and=
 delete this message and its attachments.<o:p></o:p></pre>
<pre>As emails may be altered, Orange is not liable for messages that have =
been modified, changed or falsified.<o:p></o:p></pre>
<pre>Thank you.<o:p></o:p></pre>
</div>
</div>
</body>
</html>

--_000_F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71xmbalnx02ciscoc_--

--_004_F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71xmbalnx02ciscoc_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: inline; filename="image001.gif"; size=381;
	creation-date="Mon, 23 Feb 2015 15:55:32 GMT";
	modification-date="Mon, 23 Feb 2015 15:55:32 GMT"
Content-ID: <image001.gif@01D04F3D.801259B0>
Content-Transfer-Encoding: base64

R0lGODlhKAAoAMQAAP+MQP+zgP/17//s3/+DMP/iz/+fYP+8j/9wEP95IP/Gn/+WUP/Pr/+pcP/Z
v/////9mAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAAA
AAAALAAAAAAoACgAAAX6oAONZGmeaEqKauum7Cu/8Wyj9a2P+X73vhkwSCPuhkYVMolj2pbOEjTK
oxatrSlVG+U6vUxwUmwkE81BtE99xGbdSjhMPgo4BAoA+wUICAR6IwQODwMNEAcOigAFhQYQDgoD
DwcQBJOKBIOFDQmaCCyTB416hQcBBQuTEA8Cow8EBQINpHcGhAkrEAkPChAAD3YPCLuSDw+sIgEP
wCILzK0OjY9VBJS/wYQjfwaNyRDLzRAG0AMB5wC6ENyEt8jWDAsCyA/KzJN+zLILqLlVv/OuaYPU
alU9cMwuPSCl8AEDYv8EQbwRgAEABcziJFl2bMmeEQgATEwRAgA7

--_004_F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71xmbalnx02ciscoc_--


From nobody Mon Feb 23 10:26:22 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 AF7941A1B4B for <rtgwg@ietfa.amsl.com>; Mon, 23 Feb 2015 10:26:20 -0800 (PST)
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_84=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 Wt04GT3nX2dn for <rtgwg@ietfa.amsl.com>; Mon, 23 Feb 2015 10:26:17 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3A8A1A1B7F for <rtgwg@ietf.org>; Mon, 23 Feb 2015 10:26:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=38962; q=dns/txt; s=iport; t=1424715977; x=1425925577; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=kzpEwJktt5gmLcLBUmRGzq9xUWEo1RXJ0BG0W8n8PnE=; b=SAzAN2nVtbAUQZuGE1hTOKr8yA3esy2LEhaVZBTkFVHnW2QyvL11ed+2 e2VY5ZSmb12qjrrYqjhdKukvu/ctVhYpeqHohEbTO8wOEZ6bVeemZLdoo Df8arFxytqKKei5eFBBuHtXdOgKxFvV56l5cYm+DYr2OAn0C8piqHaZdG A=;
X-Files: image001.gif : 381
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CrBQBpb+tU/4UNJK1bgkNDUloEwFmCOoVzAoElQwEBAQEBAXyEDwEBAQQFIAgBNgccAgIBCAcKAwEBAQYBAhgBBgcCFQEDAgkMFAkIAgQBEQEGCIgNAxENzXEDhS4BAQEBAQEBAQEBAQEBAQEBAQEBAQEXBIsPgU+CNAkRASQRCgwBCgEGhCUBBIYVhA2DP4EnSoFfgS4BUIVlgRs4gl2LRYM+IoICHIFQbwEBAQGBBzl/AQEB
X-IronPort-AV: E=Sophos;i="5.09,632,1418083200";  d="gif'147?scan'147,208,217,147";a="126147384"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-6.cisco.com with ESMTP; 23 Feb 2015 18:26:15 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t1NIQFM0021281 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 23 Feb 2015 18:26:15 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.175]) by xhc-rcd-x04.cisco.com ([173.37.183.78]) with mapi id 14.03.0195.001; Mon, 23 Feb 2015 12:26:15 -0600
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "Pushpasis Sarkar" <psarkar@juniper.net>, Jeff Tantsura <jeff.tantsura@ericsson.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AdBM3SH2oNl2urLXSA+s5ntM7pKOsP//0WCAgADZjID//DGyQIAIPSwA///UY1CAAJS6gA==
Date: Mon, 23 Feb 2015 18:26:15 +0000
Message-ID: <D110DAB2.EEDA%acee@cisco.com>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <5876_1424675401_54EAD249_5876_2527_11_9E32478DFA9976438E7A22F69B08FF9215C157AC@OPEXCLILM34.corporate.adroot.infra.ftgroup> <F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71@xmb-aln-x02.cisco.com>
In-Reply-To: <F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71@xmb-aln-x02.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.152.197]
Content-Type: multipart/mixed; boundary="_004_D110DAB2EEDAaceeciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/YRQxipK9Zo3_VyMoJ-UOvAwb1M4>
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, 23 Feb 2015 18:26:20 -0000

--_004_D110DAB2EEDAaceeciscocom_
Content-Type: multipart/alternative;
	boundary="_000_D110DAB2EEDAaceeciscocom_"

--_000_D110DAB2EEDAaceeciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

I agree with Les.
Acee

From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com<mailto:ginsberg@cisco.c=
om>>
Date: Monday, February 23, 2015 at 10:55 AM
To: Stephane Litkowski <stephane.litkowski@orange.com<mailto:stephane.litko=
wski@orange.com>>, Pushpasis Sarkar <psarkar@juniper.net<mailto:psarkar@jun=
iper.net>>, Jeff Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@=
ericsson.com>>, Routing WG <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: RE: LFA manageability : per AF config =3D> feedback required

Stephane =96

I can imagine cases in which the per AF enabling might make sense (e.g. whe=
n the network associated w one address family is deemed non-critical).

Section 5.1 is a SHOULD =96 as is most of the document. It is therefore a s=
uggestion as to what an implementation should provide. If a given implement=
er thinks this is either too onerous or not useful they can omit it w/o bei=
ng in violation. But I see no reason to eliminate this =96 and in actual pr=
actice I would expect the cost of supporting such a knob to be low cost. It=
 is hard for me to see this as controversial.

   Les


From: stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com> [=
mailto:stephane.litkowski@orange.com]
Sent: Sunday, February 22, 2015 11:10 PM
To: Les Ginsberg (ginsberg); Pushpasis Sarkar; Jeff Tantsura; rtgwg@ietf.or=
g<mailto:rtgwg@ietf.org>
Subject: RE: LFA manageability : per AF config =3D> feedback required

[Les:] I think your point here is that the LFA calculation is AF independen=
t within a given topology =96 but resources are consumed independent of how=
 many computations are required- giving an operator the ability to determin=
e which prefixes are most critical seems useful. That could be per AF or pe=
r prefix.

[SLI] Agree but is the =93resource saving=94 point strong enough to mandate=
 per AF activation ?

From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
Sent: Monday, February 23, 2015 05:01
To: Pushpasis Sarkar; Jeff Tantsura; LITKOWSKI Stephane SCE/IBNF; rtgwg@iet=
f.org<mailto:rtgwg@ietf.org>
Subject: RE: LFA manageability : per AF config =3D> feedback required

Pushpassis -

From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Pushpasis Sarkar
Sent: Friday, February 20, 2015 3:28 AM
To: Jeff Tantsura; stephane.litkowski@orange.com<mailto:stephane.litkowski@=
orange.com>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Subject: Re: LFA manageability : per AF config =3D> feedback required

HI Jeff et al,

I can think of a reason to have a knob per-level(or per-area) or per ISIS t=
opology(note in ISIS a topology in ISIS always corresponds to a single AF,)

[Les:] This is a common mistake to make. If one simply uses RFC 5308, then =
IPv6 prefixes can be advertised in the same topology as IPv4 (MTID #0) =96 =
and there are implementations which support this. More generally, from the =
protocol=92s POV a given topology can support any combinations of address f=
amilies. It is only a convention because of the reserved MTIDs specified in=
 RFC 5120 that certain MTIDs are =93IPv6 only=94. But if one looks at the p=
rotocol capabilities such a restriction does not exist in general.

Interestingly you contradicted yourself below. :)
But I did want to set the record straight on this point =96 hopefully we ar=
e in agreement.

and per realm and topology in OSPF. But I cannot think of a reason of why w=
ithin the same topology we need another set of knobs for each AF. Here, by =
AF I understand IPV4 or IPv6.

When both IPV4 and IPV6 are part of the same IGP topology, there is only on=
e set of backup computations needed to protect both IPV4 and IPv6 traffic.

Also I cannot think of any motivation for an operator to turn on protection=
 on only one AF and does not want to turn on for the other even if both AFs=
 has been deployed for normal forwarding.

[Les:] I think your point here is that the LFA calculation is AF independen=
t within a given topology =96 but resources are consumed independent of how=
 many computations are required- giving an operator the ability to determin=
e which prefixes are most critical seems useful. That could be per AF or pe=
r prefix.

   Les

Thanks
-Pushpasis

From: Jeff Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericss=
on.com>>
Date: Friday, February 20, 2015 at 12:59 PM
To: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>" <=
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, "rtgw=
g@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: Re: LFA manageability : per AF config =3D> feedback required

Hi Stephane,

/chair hat off

IMO in disjoined topologies one should have flexibility to enable/disable L=
FA as per AF.


Cheers,
Jeff

From: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>"=
 <stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>
Date: Thursday, February 19, 2015 at 11:21 PM
To: "rtgwg@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ie=
tf.org>>
Subject: LFA manageability : per AF config =3D> feedback required

Hi Folks,

As you know, LFA manageability draft is in final phasis =85
The current document states per AF granularity activation as a SHOULD.
=93
5.1<https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#secti=
on-5.1>.  LFA enabling/disabling scope





   The granularity of LFA activation should be controlled (as alternate

   nexthop consume memory in forwarding plane).



   An implementation of LFA SHOULD allow its activation with the

   following criteria:



   o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,

      LDP IPv6 unicast ...



   o  Per routing context : VRF, virtual/logical router, global routing

      table, ...


=93

In the framework of ISIS/OSPF yang modelization, we are challenging this st=
atement, do we really need to force implementation to support this =93per A=
F=94 granularity ?

Please provide as soon as possible your feedback on this and also provide c=
lear drivers to support or not per AF activation of LFA.


Thanks for your help !


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/IBNF/ENDD/NDE
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>



___________________________________________________________________________=
______________________________________________



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_D110DAB2EEDAaceeciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <C526150C81549B45904BD1A4A49FCBF1@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>I agree with Les.&nbsp;</div>
<div>Acee&nbsp;</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>&quot;Les Ginsberg (ginsberg)=
&quot; &lt;<a href=3D"mailto:ginsberg@cisco.com">ginsberg@cisco.com</a>&gt;=
<br>
<span style=3D"font-weight:bold">Date: </span>Monday, February 23, 2015 at =
10:55 AM<br>
<span style=3D"font-weight:bold">To: </span>Stephane Litkowski &lt;<a href=
=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.com</a>=
&gt;, Pushpasis Sarkar &lt;<a href=3D"mailto:psarkar@juniper.net">psarkar@j=
uniper.net</a>&gt;, Jeff Tantsura &lt;<a href=3D"mailto:jeff.tantsura@erics=
son.com">jeff.tantsura@ericsson.com</a>&gt;,
 Routing WG &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br=
>
<span style=3D"font-weight:bold">Subject: </span>RE: LFA manageability : pe=
r AF config =3D&gt; feedback required<br>
</div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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.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";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Stephane =96<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 can imagine cases in=
 which the per AF enabling might make sense (e.g. when the network associat=
ed w one address family is deemed non-critical).<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">Section 5.1 is a SHOUL=
D =96 as is most of the document. It is therefore a suggestion as to what a=
n implementation should provide. If a given implementer thinks this is eith=
er too onerous or not useful they can
 omit it w/o being in violation. But I see no reason to eliminate this =96 =
and in actual practice I would expect the cost of supporting such a knob to=
 be low cost. It is hard for me to see this as controversial.<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; Les<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 style=3D"font-size: 10pt; font-family: Taho=
ma, sans-serif;">From:</span></b><span style=3D"font-size: 10pt; font-famil=
y: Tahoma, sans-serif;">
<a href=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.=
com</a> [<a href=3D"mailto:stephane.litkowski@orange.com">mailto:stephane.l=
itkowski@orange.com</a>]
<br>
<b>Sent:</b> Sunday, February 22, 2015 11:10 PM<br>
<b>To:</b> Les Ginsberg (ginsberg); Pushpasis Sarkar; Jeff Tantsura; <a hre=
f=3D"mailto:rtgwg@ietf.org">
rtgwg@ietf.org</a><br>
<b>Subject:</b> RE: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] I think y=
our point here is that the LFA calculation is AF independent within a given=
 topology =96 but resources are consumed independent of how many computatio=
ns are required- giving an operator the
 ability to determine which prefixes are most critical seems useful. That c=
ould be per AF or per prefix.<o:p></o:p></span></i></b></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">[SLI] Agree but is the=
 =93resource saving=94 point strong enough to mandate per AF activation ?<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 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Taho=
ma, sans-serif;">From:</span></b><span style=3D"font-size: 10pt; font-famil=
y: Tahoma, sans-serif;"> Les Ginsberg (ginsberg) [<a href=3D"mailto:ginsber=
g@cisco.com">mailto:ginsberg@cisco.com</a>]
<br>
<b>Sent:</b> Monday, February 23, 2015 05:01<br>
<b>To:</b> Pushpasis Sarkar; Jeff Tantsura; LITKOWSKI Stephane SCE/IBNF; <a=
 href=3D"mailto:rtgwg@ietf.org">
rtgwg@ietf.org</a><br>
<b>Subject:</b> RE: LFA manageability : per AF config =3D&gt; feedback requ=
ired<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">Pushpassis -<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 style=3D"font-size: 10pt; font-family: Taho=
ma, sans-serif;">From:</span></b><span style=3D"font-size: 10pt; font-famil=
y: Tahoma, sans-serif;"> rtgwg [<a href=3D"mailto:rtgwg-bounces@ietf.org">m=
ailto:rtgwg-bounces@ietf.org</a>]
<b>On Behalf Of </b>Pushpasis Sarkar<br>
<b>Sent:</b> Friday, February 20, 2015 3:28 AM<br>
<b>To:</b> Jeff Tantsura; <a href=3D"mailto:stephane.litkowski@orange.com">=
stephane.litkowski@orange.com</a>;
<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
<b>Subject:</b> Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">HI Jeff=
 et al,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I can t=
hink of a reason to have a knob per-level(or per-area) or per ISIS topology=
(note in ISIS a topology in ISIS always corresponds to a single AF,)</span>=
<span style=3D"font-size:10.5pt;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] This is a=
 common mistake to make. If one simply uses RFC 5308, then IPv6 prefixes ca=
n be advertised in the same topology as IPv4 (MTID #0) =96 and there are im=
plementations which support this. More
 generally, from the protocol=92s POV a given topology can support any comb=
inations of address families. It is only a convention because of the reserv=
ed MTIDs specified in RFC 5120 that certain MTIDs are =93IPv6 only=94. But =
if one looks at the protocol capabilities
 such a restriction does not exist in general.<o:p></o:p></span></i></b></p=
>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">Interestingly yo=
u contradicted yourself below.
</span></i></b><b><i><span style=3D"font-family:Wingdings;color:#1F497D">J<=
/span><span style=3D"color:#1F497D"><o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">But I did want t=
o set the record straight on this point =96 hopefully we are in agreement.<=
o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">and per=
 realm and topology in OSPF. But I cannot think of a reason of why within t=
he same topology we need another set of knobs for each AF. Here, by AF I un=
derstand IPV4 or IPv6.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">When bo=
th IPV4 and IPV6 are part of the same IGP topology, there is only one set o=
f backup computations needed to protect both IPV4 and IPv6 traffic.<o:p></o=
:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Also I =
cannot think of any motivation for an operator to turn on protection on onl=
y one AF and does not want to turn on for the other even if both AFs has be=
en deployed for normal forwarding.&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Les:] I think y=
our point here is that the LFA calculation is AF independent within a given=
 topology =96 but resources are consumed independent of how many computatio=
ns are required- giving an operator the
 ability to determine which prefixes are most critical seems useful. That c=
ould be per AF or per prefix.<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">&nbsp;&nbsp; Les=
<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Thanks<=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">-Pushpa=
sis<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">Jeff Tantsura &lt;<a href=3D"mailto:jeff.tantsura@e=
ricsson.com">jeff.tantsura@ericsson.com</a>&gt;<br>
<b>Date: </b>Friday, February 20, 2015 at 12:59 PM<br>
<b>To: </b>&quot;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.=
litkowski@orange.com</a>&quot; &lt;<a href=3D"mailto:stephane.litkowski@ora=
nge.com">stephane.litkowski@orange.com</a>&gt;, &quot;<a href=3D"mailto:rtg=
wg@ietf.org">rtgwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.org"=
>rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>Re: LFA manageability : per AF config =3D&gt; feedback requ=
ired<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Hi Step=
hane,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">/chair =
hat off<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">IMO in =
disjoined topologies one should have flexibility to enable/disable LFA as p=
er AF.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Cheers,=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Jeff<o:=
p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">&quot;<a href=3D"mailto:stephane.litkowski@orange.c=
om">stephane.litkowski@orange.com</a>&quot; &lt;<a href=3D"mailto:stephane.=
litkowski@orange.com">stephane.litkowski@orange.com</a>&gt;<br>
<b>Date: </b>Thursday, February 19, 2015 at 11:21 PM<br>
<b>To: </b>&quot;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&quot;=
 &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br>
<b>Subject: </b>LFA manageability : per AF config =3D&gt; feedback required=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<blockquote style=3D"border:none;border-left:solid #B5C4DF 4.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin=
-bottom:5.0pt" id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Hi Folks,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">As you know, LFA managea=
bility draft is in final phasis =85<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">The current document sta=
tes per AF granularity activation as a SHOULD.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">=93<o:p></o:p></span></p=
>
<h3 style=3D"page-break-before:always"><a name=3D"section-5.1"></a><span st=
yle=3D"color:black"><a href=3D"https://tools.ietf.org/html/draft-ietf-rtgwg=
-lfa-manageability-07#section-5.1"><span lang=3D"EN" style=3D"font-size:10.=
0pt;color:black;text-decoration:none">5.1</span></a></span><span lang=3D"EN=
" style=3D"font-size:10.0pt;color:black">.&nbsp;
 LFA enabling/disabling scope</span><span style=3D"color:black"><o:p></o:p>=
</span></h3>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; The granularity of LFA activation should=
 be controlled (as alternate</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; nexthop consume memory in forwarding pla=
ne).</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; An implementation of LFA SHOULD allow it=
s activation with the</span><span style=3D"color:black"><o:p></o:p></span><=
/pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; following criteria:</span><span style=3D=
"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; o&nbsp; Per address-family : ipv4 unicas=
t, ipv6 unicast, LDP IPv4 unicast,</span><span style=3D"color:black"><o:p><=
/o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LDP IPv6 unicast ...</=
span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp; o&nbsp; Per routing context : VRF, virtu=
al/logical router, global routing</span><span style=3D"color:black"><o:p></=
o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; table, ...</span><span=
 style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-siz=
e:10.0pt;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<p class=3D"MsoNormal"><span style=3D"color:black">=93<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">In the framework of ISIS=
/OSPF yang modelization, we are challenging this statement, do we really ne=
ed to force implementation to support this =93per AF=94 granularity ?<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Please provide as soon a=
s possible your feedback on this and also provide clear drivers to support =
or not per AF activation of LFA.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Thanks for your help !<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black"><a href=3D"http://www.or=
ange.com/"><span style=3D"font-size: 12pt; font-family: 'Times New Roman', =
serif; text-decoration: none;"><img border=3D"0" width=3D"40" height=3D"40"=
 id=3D"Picture_x0020_1" src=3D"cid:image001.gif@01D04F3D.801259B0" alt=3D"O=
range logo"></span></a><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e: 12pt; font-family: 'Times New Roman', serif; color: black;">&nbsp;</span=
><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Aria=
l, sans-serif; color: black;">Stephane Litkowski
</span></b><span style=3D"font-size: 12pt; font-family: 'Times New Roman', =
serif; color: black;"><br>
</span><span style=3D"font-size: 10pt; font-family: Arial, sans-serif; colo=
r: black;">Network Architect
</span><span style=3D"font-size: 12pt; font-family: 'Times New Roman', seri=
f; color: black;"><br>
</span><span style=3D"font-size: 10pt; font-family: Arial, sans-serif; colo=
r: black;">Orange/SCE/EQUANT/IBNF/ENDD/NDE
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size: 10pt; font-fam=
ily: Arial, sans-serif; color: black;">Orange Expert Future Networks</span>=
<span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size: 10pt; font-fam=
ily: Arial, sans-serif; color: black;">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<span style=3D"color:black;text-decoration:none">&#43;33 2 23 28 49 83 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size: 12pt; font-family: 'Tim=
es New Roman', serif; color: black;"><br>
</span><span lang=3D"FR" style=3D"font-size: 10pt; font-family: Arial, sans=
-serif; color: black;">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<span style=3D"color:black;text-decoration:none">&#43;33 6 37 86 97 52 </sp=
an></a></span><span lang=3D"FR" style=3D"font-size: 12pt; font-family: 'Tim=
es New Roman', serif; color: black;"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><span style=3D"font-size: =
10pt; font-family: Arial, sans-serif; color: rgb(255, 102, 0); text-decorat=
ion: none;">stephane.litkowski@orange.com</span></a></span><span style=3D"c=
olor:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span lang=3D"FR" style=
=3D"font-size: 12pt; font-family: 'Times New Roman', serif; color: black;">=
&nbsp;</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<pre><span style=3D"color:black">__________________________________________=
___________________________________________________________________________=
____<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Ce message et ses pieces jointes peuvent c=
ontenir des informations confidentielles ou privilegiees et ne doivent donc=
<o:p></o:p></span></pre>
<pre><span style=3D"color:black">pas etre diffuses, exploites ou copies san=
s autorisation. Si vous avez recu ce message par erreur, veuillez le signal=
er<o:p></o:p></span></pre>
<pre><span style=3D"color:black">a l'expediteur et le detruire ainsi que le=
s pieces jointes. Les messages electroniques etant susceptibles d'alteratio=
n,<o:p></o:p></span></pre>
<pre><span style=3D"color:black">Orange decline toute responsabilite si ce =
message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">This message and its attachments may conta=
in confidential or privileged information that may be protected by law;<o:p=
></o:p></span></pre>
<pre><span style=3D"color:black">they should not be distributed, used or co=
pied without authorisation.<o:p></o:p></span></pre>
<pre><span style=3D"color:black">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 style=3D"color:black">As emails may be altered, Orange is not li=
able for messages that have been modified, changed or falsified.<o:p></o:p>=
</span></pre>
<pre><span style=3D"color:black">Thank you.<o:p></o:p></span></pre>
</div>
</div>
</blockquote>
</div>
</div>
</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. Merci.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>This message and its attachments may contain confidential or privilege=
d information that may be protected by law;<o:p></o:p></pre>
<pre>they should not be distributed, used or copied without authorisation.<=
o:p></o:p></pre>
<pre>If you have received this email in error, please notify the sender and=
 delete this message and its attachments.<o:p></o:p></pre>
<pre>As emails may be altered, Orange is not liable for messages that have =
been modified, changed or falsified.<o:p></o:p></pre>
<pre>Thank you.<o:p></o:p></pre>
</div>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>

--_000_D110DAB2EEDAaceeciscocom_--

--_004_D110DAB2EEDAaceeciscocom_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: attachment; filename="image001.gif"; size=381;
	creation-date="Mon, 23 Feb 2015 18:26:15 GMT";
	modification-date="Mon, 23 Feb 2015 18:26:15 GMT"
Content-ID: <image001.gif@01D04F3D.801259B0>
Content-Transfer-Encoding: base64

R0lGODlhKAAoAMQAAP+MQP+zgP/17//s3/+DMP/iz/+fYP+8j/9wEP95IP/Gn/+WUP/Pr/+pcP/Z
v/////9mAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAAA
AAAALAAAAAAoACgAAAX6oAONZGmeaEqKauum7Cu/8Wyj9a2P+X73vhkwSCPuhkYVMolj2pbOEjTK
oxatrSlVG+U6vUxwUmwkE81BtE99xGbdSjhMPgo4BAoA+wUICAR6IwQODwMNEAcOigAFhQYQDgoD
DwcQBJOKBIOFDQmaCCyTB416hQcBBQuTEA8Cow8EBQINpHcGhAkrEAkPChAAD3YPCLuSDw+sIgEP
wCILzK0OjY9VBJS/wYQjfwaNyRDLzRAG0AMB5wC6ENyEt8jWDAsCyA/KzJN+zLILqLlVv/OuaYPU
alU9cMwuPSCl8AEDYv8EQbwRgAEABcziJFl2bMmeEQgATEwRAgA7

--_004_D110DAB2EEDAaceeciscocom_--


From nobody Mon Feb 23 10:27:58 2015
Return-Path: <antoni.przygienda@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 25B221A1EF9 for <rtgwg@ietfa.amsl.com>; Mon, 23 Feb 2015 10:27:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.6
X-Spam-Level: 
X-Spam-Status: No, score=-3.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_84=0.6, 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 Lv-y0VzhsrNk for <rtgwg@ietfa.amsl.com>; Mon, 23 Feb 2015 10:27:50 -0800 (PST)
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 003061A1F20 for <rtgwg@ietf.org>; Mon, 23 Feb 2015 10:27:46 -0800 (PST)
X-AuditID: c6180641-f79916d00000623a-f8-54eb10b51f82
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id EE.D0.25146.5B01BE45; Mon, 23 Feb 2015 12:36:21 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0210.002; Mon, 23 Feb 2015 13:27:42 -0500
From: Antoni Przygienda <antoni.przygienda@ericsson.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, Pushpasis Sarkar <psarkar@juniper.net>, "Jeff Tantsura" <jeff.tantsura@ericsson.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AdBM3SH2oNl2urLXSA+s5ntM7pKOsP//0WCAgADIyICABDoFgIAANNkAgACS1gCAACocgIAAU3LQ
Date: Mon, 23 Feb 2015 18:27:41 +0000
Message-ID: <2E4BB27CAB87BF43B4207C0E55860F182602DC@eusaamb103.ericsson.se>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <5876_1424675401_54EAD249_5876_2527_11_9E32478DFA9976438E7A22F69B08FF9215C157AC@OPEXCLILM34.corporate.adroot.infra.ftgroup> <F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71@xmb-aln-x02.cisco.com> <D110DAB2.EEDA%acee@cisco.com>
In-Reply-To: <D110DAB2.EEDA%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: multipart/related; boundary="_004_2E4BB27CAB87BF43B4207C0E55860F182602DCeusaamb103ericsso_"; type="multipart/alternative"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKIsWRmVeSWpSXmKPExsUyuXRPuO5WgdchBv//aVtMfjuP2WLDn43s Flf2fGayuPDmN7PF170PWR1YPab83sjqsWTJTyaP601X2T1anp1kC2CJ4rJJSc3JLEst0rdL 4MrYNukiW8GfA8wV01/0sjcwLp3C3MXIySEhYCJx6dUVKFtM4sK99WxdjFwcQgJHGCVW3u+E cpYzSvS9P8MEUsUmYCFx+dtTZpCEiMBsJokn216wgySEBZwlLk2bzwJiiwi4SJx63s0KYUdJ 3L7/AKyGRUBV4sf9zYwgNq+At8Sk75+YIDY0sUj8674OtoFTQFuipfU8WBEj0E3fT60BizML iEvcejKfCeJWEYmHF0+zQdiiEi8f/2OFsJUk5ry+BnYds0A3o8TFPz+ZIbYJSpyc+YRlAqPI LCSzZiGrm4WkDqIoX6J/71koW0diwe5PbBC2tsSyha+ZYewzBx4zYYrrSGy+tBOqV1GirXM2 1LIljBK3XzWzwRTt/r6IHaZoSvdD9gWMvKsYOUqLU8ty040MNzEC08ExCTbHHYwLPlkeYhTg YFTi4TVQfxUixJpYVlyZe4hRmoNFSZy37MrBECGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2M yzNfiUg/5ghvuf/LsyNgWSr32Vn5dRkLKiwNO36Jm+l7/rT2r/54tm5xUv7n1rlNy7QlTkw1 uX792hKdAxEV4Te9bq4rOfj2f9clcbdPyg+PvWvaeq+0KTxJm6ekruFV+wSBlwsbK/y/Gj++ yyCgyLYo6+KD4h7PWfyP3wlu/r7W8pomV6ibEktxRqKhFnNRcSIAwe0tuegCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/cYToUtx1rpqzdVx8xdicKP-Sk2k>
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, 23 Feb 2015 18:27:57 -0000

--_004_2E4BB27CAB87BF43B4207C0E55860F182602DCeusaamb103ericsso_
Content-Type: multipart/alternative;
	boundary="_000_2E4BB27CAB87BF43B4207C0E55860F182602DCeusaamb103ericsso_"

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

+1

--- tony

From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: Monday, February 23, 2015 10:26 AM
To: Les Ginsberg (ginsberg); stephane.litkowski@orange.com; Pushpasis Sarka=
r; Jeff Tantsura; rtgwg@ietf.org
Subject: Re: LFA manageability : per AF config =3D> feedback required

I agree with Les.
Acee

From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com<mailto:ginsberg@cisco.c=
om>>
Date: Monday, February 23, 2015 at 10:55 AM
To: Stephane Litkowski <stephane.litkowski@orange.com<mailto:stephane.litko=
wski@orange.com>>, Pushpasis Sarkar <psarkar@juniper.net<mailto:psarkar@jun=
iper.net>>, Jeff Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@=
ericsson.com>>, Routing WG <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: RE: LFA manageability : per AF config =3D> feedback required

Stephane -

I can imagine cases in which the per AF enabling might make sense (e.g. whe=
n the network associated w one address family is deemed non-critical).

Section 5.1 is a SHOULD - as is most of the document. It is therefore a sug=
gestion as to what an implementation should provide. If a given implementer=
 thinks this is either too onerous or not useful they can omit it w/o being=
 in violation. But I see no reason to eliminate this - and in actual practi=
ce I would expect the cost of supporting such a knob to be low cost. It is =
hard for me to see this as controversial.

   Les


From: stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com> [=
mailto:stephane.litkowski@orange.com]
Sent: Sunday, February 22, 2015 11:10 PM
To: Les Ginsberg (ginsberg); Pushpasis Sarkar; Jeff Tantsura; rtgwg@ietf.or=
g<mailto:rtgwg@ietf.org>
Subject: RE: LFA manageability : per AF config =3D> feedback required

[Les:] I think your point here is that the LFA calculation is AF independen=
t within a given topology - but resources are consumed independent of how m=
any computations are required- giving an operator the ability to determine =
which prefixes are most critical seems useful. That could be per AF or per =
prefix.

[SLI] Agree but is the "resource saving" point strong enough to mandate per=
 AF activation ?

From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
Sent: Monday, February 23, 2015 05:01
To: Pushpasis Sarkar; Jeff Tantsura; LITKOWSKI Stephane SCE/IBNF; rtgwg@iet=
f.org<mailto:rtgwg@ietf.org>
Subject: RE: LFA manageability : per AF config =3D> feedback required

Pushpassis -

From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Pushpasis Sarkar
Sent: Friday, February 20, 2015 3:28 AM
To: Jeff Tantsura; stephane.litkowski@orange.com<mailto:stephane.litkowski@=
orange.com>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Subject: Re: LFA manageability : per AF config =3D> feedback required

HI Jeff et al,

I can think of a reason to have a knob per-level(or per-area) or per ISIS t=
opology(note in ISIS a topology in ISIS always corresponds to a single AF,)

[Les:] This is a common mistake to make. If one simply uses RFC 5308, then =
IPv6 prefixes can be advertised in the same topology as IPv4 (MTID #0) - an=
d there are implementations which support this. More generally, from the pr=
otocol's POV a given topology can support any combinations of address famil=
ies. It is only a convention because of the reserved MTIDs specified in RFC=
 5120 that certain MTIDs are "IPv6 only". But if one looks at the protocol =
capabilities such a restriction does not exist in general.

Interestingly you contradicted yourself below. :)
But I did want to set the record straight on this point - hopefully we are =
in agreement.

and per realm and topology in OSPF. But I cannot think of a reason of why w=
ithin the same topology we need another set of knobs for each AF. Here, by =
AF I understand IPV4 or IPv6.

When both IPV4 and IPV6 are part of the same IGP topology, there is only on=
e set of backup computations needed to protect both IPV4 and IPv6 traffic.

Also I cannot think of any motivation for an operator to turn on protection=
 on only one AF and does not want to turn on for the other even if both AFs=
 has been deployed for normal forwarding.

[Les:] I think your point here is that the LFA calculation is AF independen=
t within a given topology - but resources are consumed independent of how m=
any computations are required- giving an operator the ability to determine =
which prefixes are most critical seems useful. That could be per AF or per =
prefix.

   Les

Thanks
-Pushpasis

From: Jeff Tantsura <jeff.tantsura@ericsson.com<mailto:jeff.tantsura@ericss=
on.com>>
Date: Friday, February 20, 2015 at 12:59 PM
To: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>" <=
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, "rtgw=
g@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: Re: LFA manageability : per AF config =3D> feedback required

Hi Stephane,

/chair hat off

IMO in disjoined topologies one should have flexibility to enable/disable L=
FA as per AF.


Cheers,
Jeff

From: "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>"=
 <stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>
Date: Thursday, February 19, 2015 at 11:21 PM
To: "rtgwg@ietf.org<mailto:rtgwg@ietf.org>" <rtgwg@ietf.org<mailto:rtgwg@ie=
tf.org>>
Subject: LFA manageability : per AF config =3D> feedback required

Hi Folks,

As you know, LFA manageability draft is in final phasis ...
The current document states per AF granularity activation as a SHOULD.
"
5.1<https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#secti=
on-5.1>.  LFA enabling/disabling scope





   The granularity of LFA activation should be controlled (as alternate

   nexthop consume memory in forwarding plane).



   An implementation of LFA SHOULD allow its activation with the

   following criteria:



   o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,

      LDP IPv6 unicast ...



   o  Per routing context : VRF, virtual/logical router, global routing

      table, ...


"

In the framework of ISIS/OSPF yang modelization, we are challenging this st=
atement, do we really need to force implementation to support this "per AF"=
 granularity ?

Please provide as soon as possible your feedback on this and also provide c=
lear drivers to support or not per AF activation of LFA.


Thanks for your help !


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/IBNF/ENDD/NDE
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>



___________________________________________________________________________=
______________________________________________



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_2E4BB27CAB87BF43B4207C0E55860F182602DCeusaamb103ericsso_
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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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.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";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle26
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">&#43;1<o:p></o:p></span></fo=
nt></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D"><o:p>&nbsp;</o:p></span></fo=
nt></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">--- tony
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D"><o:p>&nbsp;</o:p></span></fo=
nt></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><font size=3D"2" face=3D"Tahoma"><span style=3D"f=
ont-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;font-=
weight:bold">From:</span></font></b><font size=3D"2" face=3D"Tahoma"><span =
style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&q=
uot;"> rtgwg
 [mailto:rtgwg-bounces@ietf.org] <b><span style=3D"font-weight:bold">On Beh=
alf Of </span>
</b>Acee Lindem (acee)<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Monday, February 23, 2=
015 10:26 AM<br>
<b><span style=3D"font-weight:bold">To:</span></b> Les Ginsberg (ginsberg);=
 stephane.litkowski@orange.com; Pushpasis Sarkar; Jeff Tantsura; rtgwg@ietf=
.org<br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Re: LFA manageabili=
ty : per AF config =3D&gt; feedback required<o:p></o:p></span></font></p>
</div>
</div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">I agree with Les.&nbsp;<o:p></o:=
p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">Acee&nbsp;<o:p></o:p></span></fo=
nt></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black"><o:p>&nbsp;</o:p></span></font><=
/p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><font size=3D"2" color=3D"black" face=3D"Calibri"=
><span style=3D"font-size:11.0pt;color:black;font-weight:bold">From:
</span></font></b><font color=3D"black"><span style=3D"color:black">&quot;L=
es Ginsberg (ginsberg)&quot; &lt;<a href=3D"mailto:ginsberg@cisco.com">gins=
berg@cisco.com</a>&gt;<br>
<b><span style=3D"font-weight:bold">Date: </span></b>Monday, February 23, 2=
015 at 10:55 AM<br>
<b><span style=3D"font-weight:bold">To: </span></b>Stephane Litkowski &lt;<=
a href=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.c=
om</a>&gt;, Pushpasis Sarkar &lt;<a href=3D"mailto:psarkar@juniper.net">psa=
rkar@juniper.net</a>&gt;, Jeff Tantsura &lt;<a href=3D"mailto:jeff.tantsura=
@ericsson.com">jeff.tantsura@ericsson.com</a>&gt;,
 Routing WG &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br=
>
<b><span style=3D"font-weight:bold">Subject: </span></b>RE: LFA manageabili=
ty : per AF config =3D&gt; feedback required<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black"><o:p>&nbsp;</o:p></span></font><=
/p>
</div>
<blockquote style=3D"border:none;border-left:solid #B5C4DF 4.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id=3D"MAC_OUTLOOK_ATTR=
IBUTION_BLOCKQUOTE">
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">Stephane &#8211;</span></fon=
t><font color=3D"black"><span style=3D"color:black"><o:p></o:p></span></fon=
t></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span></font><font co=
lor=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">I can imagine cases in which=
 the per AF enabling might make sense (e.g. when the network associated w o=
ne address family is deemed non-critical).</span></font><font color=3D"blac=
k"><span style=3D"color:black"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span></font><font co=
lor=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">Section 5.1 is a SHOULD &#82=
11; as is most of the document. It is therefore a suggestion as to what an =
implementation should provide. If a given implementer
 thinks this is either too onerous or not useful they can omit it w/o being=
 in violation. But I see no reason to eliminate this &#8211; and in actual =
practice I would expect the cost of supporting such a knob to be low cost. =
It is hard for me to see this as controversial.</span></font><font color=3D=
"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span></font><font co=
lor=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;&nbsp; Les</span></fon=
t><font color=3D"black"><span style=3D"color:black"><o:p></o:p></span></fon=
t></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span></font><font co=
lor=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span></font><font co=
lor=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></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><font size=3D"2" color=3D"black" face=3D"Tahoma">=
<span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;;color:black;font-weight:bold">From:</span></font></b><font size=
=3D"2" color=3D"black" face=3D"Tahoma"><span style=3D"font-size:10.0pt;font=
-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">
<a href=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.=
com</a> [<a href=3D"mailto:stephane.litkowski@orange.com">mailto:stephane.l=
itkowski@orange.com</a>]
<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Sunday, February 22, 2=
015 11:10 PM<br>
<b><span style=3D"font-weight:bold">To:</span></b> Les Ginsberg (ginsberg);=
 Pushpasis Sarkar; Jeff Tantsura;
<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
<b><span style=3D"font-weight:bold">Subject:</span></b> RE: LFA manageabili=
ty : per AF config =3D&gt; feedback required</span></font><font color=3D"bl=
ack"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
</div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">&nbsp;<o:p></o:p></span></font><=
/p>
<p class=3D"MsoNormal"><b><i><font size=3D"2" color=3D"#1f497d" face=3D"Cal=
ibri"><span style=3D"font-size:11.0pt;color:#1F497D;font-weight:bold;font-s=
tyle:italic">[Les:] I think your point here is that the LFA calculation is =
AF independent within a given topology &#8211; but
 resources are consumed independent of how many computations are required- =
giving an operator the ability to determine which prefixes are most critica=
l seems useful. That could be per AF or per prefix.</span></font></i></b><f=
ont color=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></=
p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span></font><font co=
lor=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">[SLI] Agree but is the &#822=
0;resource saving&#8221; point strong enough to mandate per AF activation ?=
</span></font><font color=3D"black"><span style=3D"color:black"><o:p></o:p>=
</span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span></font><font co=
lor=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><font size=3D"2" color=3D"black" face=3D"Tahoma">=
<span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;;color:black;font-weight:bold">From:</span></font></b><font size=
=3D"2" color=3D"black" face=3D"Tahoma"><span style=3D"font-size:10.0pt;font=
-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">
 Les Ginsberg (ginsberg) [<a href=3D"mailto:ginsberg@cisco.com">mailto:gins=
berg@cisco.com</a>]
<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Monday, February 23, 2=
015 05:01<br>
<b><span style=3D"font-weight:bold">To:</span></b> Pushpasis Sarkar; Jeff T=
antsura; LITKOWSKI Stephane SCE/IBNF;
<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
<b><span style=3D"font-weight:bold">Subject:</span></b> RE: LFA manageabili=
ty : per AF config =3D&gt; feedback required</span></font><font color=3D"bl=
ack"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
</div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">&nbsp;<o:p></o:p></span></font><=
/p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">Pushpassis -</span></font><f=
ont color=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></=
p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span></font><font co=
lor=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></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><font size=3D"2" color=3D"black" face=3D"Tahoma">=
<span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;;color:black;font-weight:bold">From:</span></font></b><font size=
=3D"2" color=3D"black" face=3D"Tahoma"><span style=3D"font-size:10.0pt;font=
-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">
 rtgwg [<a href=3D"mailto:rtgwg-bounces@ietf.org">mailto:rtgwg-bounces@ietf=
.org</a>]
<b><span style=3D"font-weight:bold">On Behalf Of </span></b>Pushpasis Sarka=
r<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Friday, February 20, 2=
015 3:28 AM<br>
<b><span style=3D"font-weight:bold">To:</span></b> Jeff Tantsura; <a href=
=3D"mailto:stephane.litkowski@orange.com">
stephane.litkowski@orange.com</a>; <a href=3D"mailto:rtgwg@ietf.org">rtgwg@=
ietf.org</a><br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Re: LFA manageabili=
ty : per AF config =3D&gt; feedback required</span></font><font color=3D"bl=
ack"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
</div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">&nbsp;<o:p></o:p></span></font><=
/p>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">HI Jeff et al,</span></font><fon=
t color=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">&nbsp;</span></font><font color=
=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">I can think of a reason to have =
a knob per-level(or per-area) or per ISIS topology(note in ISIS a topology =
in ISIS always corresponds to a single AF,)</span></font><font color=3D"bla=
ck"><span style=3D"color:black"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><b><i><font size=3D"2" color=3D"#1f497d" face=3D"Cal=
ibri"><span style=3D"font-size:11.0pt;color:#1F497D;font-weight:bold;font-s=
tyle:italic">&nbsp;</span></font></i></b><font color=3D"black"><span style=
=3D"color:black"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><b><i><font size=3D"2" color=3D"#1f497d" face=3D"Cal=
ibri"><span style=3D"font-size:11.0pt;color:#1F497D;font-weight:bold;font-s=
tyle:italic">[Les:] This is a common mistake to make. If one simply uses RF=
C 5308, then IPv6 prefixes can be advertised
 in the same topology as IPv4 (MTID #0) &#8211; and there are implementatio=
ns which support this. More generally, from the protocol&#8217;s POV a give=
n topology can support any combinations of address families. It is only a c=
onvention because of the reserved MTIDs specified
 in RFC 5120 that certain MTIDs are &#8220;IPv6 only&#8221;. But if one loo=
ks at the protocol capabilities such a restriction does not exist in genera=
l.</span></font></i></b><font color=3D"black"><span style=3D"color:black"><=
o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><b><i><font size=3D"2" color=3D"#1f497d" face=3D"Cal=
ibri"><span style=3D"font-size:11.0pt;color:#1F497D;font-weight:bold;font-s=
tyle:italic">&nbsp;</span></font></i></b><font color=3D"black"><span style=
=3D"color:black"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><b><i><font size=3D"2" color=3D"#1f497d" face=3D"Cal=
ibri"><span style=3D"font-size:11.0pt;color:#1F497D;font-weight:bold;font-s=
tyle:italic">Interestingly you contradicted yourself below.
</span></font></i></b><b><i><font color=3D"#1f497d" face=3D"Wingdings"><spa=
n style=3D"font-family:Wingdings;color:#1F497D;font-weight:bold;font-style:=
italic">J</span></font></i></b><font color=3D"black"><span style=3D"color:b=
lack"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><b><i><font size=3D"2" color=3D"#1f497d" face=3D"Cal=
ibri"><span style=3D"font-size:11.0pt;color:#1F497D;font-weight:bold;font-s=
tyle:italic">But I did want to set the record straight on this point &#8211=
; hopefully we are in agreement.</span></font></i></b><font color=3D"black"=
><span style=3D"color:black"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><b><i><font size=3D"2" color=3D"#1f497d" face=3D"Cal=
ibri"><span style=3D"font-size:11.0pt;color:#1F497D;font-weight:bold;font-s=
tyle:italic">&nbsp;</span></font></i></b><font color=3D"black"><span style=
=3D"color:black"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">and per realm and topology in OS=
PF. But I cannot think of a reason of why within the same topology we need =
another set of knobs for each AF. Here, by
 AF I understand IPV4 or IPv6.</span></font><font color=3D"black"><span sty=
le=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:10.5pt;color:#1F497D">&nbsp;</span></font><font co=
lor=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">When both IPV4 and IPV6 are part=
 of the same IGP topology, there is only one set of backup computations nee=
ded to protect both IPV4 and IPv6 traffic.</span></font><font color=3D"blac=
k"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">&nbsp;</span></font><font color=
=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">Also I cannot think of any motiv=
ation for an operator to turn on protection on only one AF and does not wan=
t to turn on for the other even if both AFs
 has been deployed for normal forwarding.&nbsp;</span></font><font color=3D=
"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:10.5pt;color:#1F497D">&nbsp;</span></font><font co=
lor=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><b><i><font size=3D"2" color=3D"#1f497d" face=3D"Cal=
ibri"><span style=3D"font-size:11.0pt;color:#1F497D;font-weight:bold;font-s=
tyle:italic">[Les:] I think your point here is that the LFA calculation is =
AF independent within a given topology &#8211; but
 resources are consumed independent of how many computations are required- =
giving an operator the ability to determine which prefixes are most critica=
l seems useful. That could be per AF or per prefix.</span></font></i></b><f=
ont color=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></=
p>
<p class=3D"MsoNormal"><b><i><font size=3D"2" color=3D"#1f497d" face=3D"Cal=
ibri"><span style=3D"font-size:11.0pt;color:#1F497D;font-weight:bold;font-s=
tyle:italic">&nbsp;</span></font></i></b><font color=3D"black"><span style=
=3D"color:black"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><b><i><font size=3D"2" color=3D"#1f497d" face=3D"Cal=
ibri"><span style=3D"font-size:11.0pt;color:#1F497D;font-weight:bold;font-s=
tyle:italic">&nbsp;&nbsp; Les</span></font></i></b><font color=3D"black"><s=
pan style=3D"color:black"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"#1f497d" face=3D"Calibri">=
<span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span></font><font co=
lor=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">Thanks</span></font><font color=
=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">-Pushpasis</span></font><font co=
lor=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">&nbsp;</span></font><font color=
=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><font size=3D"2" color=3D"black" face=3D"Calibri"=
><span style=3D"font-size:11.0pt;color:black;font-weight:bold">From:
</span></font></b><font color=3D"black"><span style=3D"color:black">Jeff Ta=
ntsura &lt;<a href=3D"mailto:jeff.tantsura@ericsson.com">jeff.tantsura@eric=
sson.com</a>&gt;<br>
<b><span style=3D"font-weight:bold">Date: </span></b>Friday, February 20, 2=
015 at 12:59 PM<br>
<b><span style=3D"font-weight:bold">To: </span></b>&quot;<a href=3D"mailto:=
stephane.litkowski@orange.com">stephane.litkowski@orange.com</a>&quot; &lt;=
<a href=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.=
com</a>&gt;, &quot;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&quo=
t;
 &lt;<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>&gt;<br>
<b><span style=3D"font-weight:bold">Subject: </span></b>Re: LFA manageabili=
ty : per AF config =3D&gt; feedback required<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">&nbsp;</span></font><font color=
=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">Hi Stephane,</span></font><font =
color=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">&nbsp;</span></font><font color=
=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">/chair hat off</span></font><fon=
t color=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">&nbsp;</span></font><font color=
=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">IMO in disjoined topologies one =
should have flexibility to enable/disable LFA as per AF.</span></font><font=
 color=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">&nbsp;</span></font><font color=
=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">&nbsp;</span></font><font color=
=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">Cheers,</span></font><font color=
=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">Jeff</span></font><font color=3D=
"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">&nbsp;</span></font><font color=
=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><font size=3D"2" color=3D"black" face=3D"Calibri"=
><span style=3D"font-size:11.0pt;color:black;font-weight:bold">From:
</span></font></b><font color=3D"black"><span style=3D"color:black">&quot;<=
a href=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.c=
om</a>&quot; &lt;<a href=3D"mailto:stephane.litkowski@orange.com">stephane.=
litkowski@orange.com</a>&gt;<br>
<b><span style=3D"font-weight:bold">Date: </span></b>Thursday, February 19,=
 2015 at 11:21 PM<br>
<b><span style=3D"font-weight:bold">To: </span></b>&quot;<a href=3D"mailto:=
rtgwg@ietf.org">rtgwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:rtgwg@ietf.o=
rg">rtgwg@ietf.org</a>&gt;<br>
<b><span style=3D"font-weight:bold">Subject: </span></b>LFA manageability :=
 per AF config =3D&gt; feedback required<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:10.5pt;color:black">&nbsp;</span></font><font color=
=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p>
</div>
<blockquote style=3D"border:none;border-left:solid #B5C4DF 4.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin=
-bottom:5.0pt" id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">Hi Folks,<o:p></o:p></span></fon=
t></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">&nbsp;<o:p></o:p></span></font><=
/p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">As you know, LFA manageability d=
raft is in final phasis &#8230;<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">The current document states per =
AF granularity activation as a SHOULD.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">&#8220;<o:p></o:p></span></font>=
</p>
<h3 style=3D"page-break-before:always"><a name=3D"section-5.1"></a><b><font=
 size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"font-size:1=
2.0pt;color:black"><a href=3D"https://tools.ietf.org/html/draft-ietf-rtgwg-=
lfa-manageability-07#section-5.1"><font size=3D"2" color=3D"black"><span la=
ng=3D"EN" style=3D"font-size:10.0pt;color:black;text-decoration:none">5.1</=
span></font></a></span></font></b><font size=3D"2" color=3D"black"><span la=
ng=3D"EN" style=3D"font-size:10.0pt;color:black">.&nbsp;
 LFA enabling/disabling scope</span></font><font color=3D"black"><span styl=
e=3D"color:black"><o:p></o:p></span></font></h3>
<pre style=3D"page-break-before:always"><font size=3D"2" color=3D"black" fa=
ce=3D"Courier New"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black"=
>&nbsp;</span></font><font color=3D"black"><span style=3D"color:black"><o:p=
></o:p></span></font></pre>
<pre style=3D"page-break-before:always"><font size=3D"2" color=3D"black" fa=
ce=3D"Courier New"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black"=
>&nbsp;</span></font><font color=3D"black"><span style=3D"color:black"><o:p=
></o:p></span></font></pre>
<pre style=3D"page-break-before:always"><font size=3D"2" color=3D"black" fa=
ce=3D"Courier New"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black"=
>&nbsp;&nbsp; The granularity of LFA activation should be controlled (as al=
ternate</span></font><font color=3D"black"><span style=3D"color:black"><o:p=
></o:p></span></font></pre>
<pre style=3D"page-break-before:always"><font size=3D"2" color=3D"black" fa=
ce=3D"Courier New"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black"=
>&nbsp;&nbsp; nexthop consume memory in forwarding plane).</span></font><fo=
nt color=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></p=
re>
<pre style=3D"page-break-before:always"><font size=3D"2" color=3D"black" fa=
ce=3D"Courier New"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black"=
>&nbsp;</span></font><font color=3D"black"><span style=3D"color:black"><o:p=
></o:p></span></font></pre>
<pre style=3D"page-break-before:always"><font size=3D"2" color=3D"black" fa=
ce=3D"Courier New"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black"=
>&nbsp;&nbsp; An implementation of LFA SHOULD allow its activation with the=
</span></font><font color=3D"black"><span style=3D"color:black"><o:p></o:p>=
</span></font></pre>
<pre style=3D"page-break-before:always"><font size=3D"2" color=3D"black" fa=
ce=3D"Courier New"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black"=
>&nbsp;&nbsp; following criteria:</span></font><font color=3D"black"><span =
style=3D"color:black"><o:p></o:p></span></font></pre>
<pre style=3D"page-break-before:always"><font size=3D"2" color=3D"black" fa=
ce=3D"Courier New"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black"=
>&nbsp;</span></font><font color=3D"black"><span style=3D"color:black"><o:p=
></o:p></span></font></pre>
<pre style=3D"page-break-before:always"><font size=3D"2" color=3D"black" fa=
ce=3D"Courier New"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black"=
>&nbsp;&nbsp; o&nbsp; Per address-family : ipv4 unicast, ipv6 unicast, LDP =
IPv4 unicast,</span></font><font color=3D"black"><span style=3D"color:black=
"><o:p></o:p></span></font></pre>
<pre style=3D"page-break-before:always"><font size=3D"2" color=3D"black" fa=
ce=3D"Courier New"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LDP IPv6 unicast ...</span></font><font col=
or=3D"black"><span style=3D"color:black"><o:p></o:p></span></font></pre>
<pre style=3D"page-break-before:always"><font size=3D"2" color=3D"black" fa=
ce=3D"Courier New"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black"=
>&nbsp;</span></font><font color=3D"black"><span style=3D"color:black"><o:p=
></o:p></span></font></pre>
<pre style=3D"page-break-before:always"><font size=3D"2" color=3D"black" fa=
ce=3D"Courier New"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black"=
>&nbsp;&nbsp; o&nbsp; Per routing context : VRF, virtual/logical router, gl=
obal routing</span></font><font color=3D"black"><span style=3D"color:black"=
><o:p></o:p></span></font></pre>
<pre style=3D"page-break-before:always"><font size=3D"2" color=3D"black" fa=
ce=3D"Courier New"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; table, ...</span></font><font color=3D"blac=
k"><span style=3D"color:black"><o:p></o:p></span></font></pre>
<pre style=3D"page-break-before:always"><font size=3D"2" color=3D"black" fa=
ce=3D"Courier New"><span lang=3D"EN" style=3D"font-size:10.0pt;color:black"=
>&nbsp;</span></font><font color=3D"black"><span style=3D"color:black"><o:p=
></o:p></span></font></pre>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">&#8220;<o:p></o:p></span></font>=
</p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">&nbsp;<o:p></o:p></span></font><=
/p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">In the framework of ISIS/OSPF ya=
ng modelization, we are challenging this statement, do we really need to fo=
rce implementation to support this &#8220;per AF&#8221;
 granularity ?<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">&nbsp;<o:p></o:p></span></font><=
/p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">Please provide as soon as possib=
le your feedback on this and also provide clear drivers to support or not p=
er AF activation of LFA.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">&nbsp;<o:p></o:p></span></font><=
/p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">&nbsp;<o:p></o:p></span></font><=
/p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">Thanks for your help !<o:p></o:p=
></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">&nbsp;<o:p></o:p></span></font><=
/p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">&nbsp;<o:p></o:p></span></font><=
/p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black"><a href=3D"http://www.orange.com=
/"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size:12.0p=
t;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;text-decoration=
:none"><img border=3D"0" width=3D"40" height=3D"40" id=3D"Picture_x0020_1" =
src=3D"cid:image001.gif@01D04F53.59D16780" alt=3D"Orange logo"></span></fon=
t></a><o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><font size=3D"3" color=
=3D"black" face=3D"Times New Roman"><span style=3D"font-size:12.0pt;font-fa=
mily:&quot;Times New Roman&quot;,&quot;serif&quot;;color:black">&nbsp;</spa=
n></font><font color=3D"black"><span style=3D"color:black"><o:p></o:p></spa=
n></font></p>
<p class=3D"MsoNormal"><b><font size=3D"2" color=3D"black" face=3D"Arial"><=
span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-ser=
if&quot;;color:black;font-weight:bold">Stephane Litkowski
</span></font></b><font size=3D"3" color=3D"black" face=3D"Times New Roman"=
><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&q=
uot;serif&quot;;color:black"><br>
</span></font><font size=3D"2" color=3D"black" face=3D"Arial"><span style=
=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;c=
olor:black">Network Architect
</span></font><font size=3D"3" color=3D"black" face=3D"Times New Roman"><sp=
an style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;=
serif&quot;;color:black"><br>
</span></font><font size=3D"2" color=3D"black" face=3D"Arial"><span style=
=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;c=
olor:black">Orange/SCE/EQUANT/IBNF/ENDD/NDE
</span></font><font color=3D"black"><span style=3D"color:black"><o:p></o:p>=
</span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Arial"><spa=
n lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot=
;sans-serif&quot;;color:black">Orange Expert Future Networks</span></font><=
font color=3D"black"><span style=3D"color:black"><o:p></o:p></span></font><=
/p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Arial"><spa=
n lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot=
;sans-serif&quot;;color:black">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<font color=3D"black"><span style=3D"color:black;text-decoration:none">&#43=
;33 2 23 28 49 83
</span></font></a></span></font><font size=3D"3" color=3D"black" face=3D"Ti=
mes New Roman"><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quo=
t;Times New Roman&quot;,&quot;serif&quot;;color:black"><br>
</span></font><font size=3D"2" color=3D"black" face=3D"Arial"><span lang=3D=
"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-ser=
if&quot;;color:black">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<font color=3D"black"><span style=3D"color:black;text-decoration:none">&#43=
;33 6 37 86 97 52
</span></font></a></span></font><font size=3D"3" color=3D"black" face=3D"Ti=
mes New Roman"><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quo=
t;Times New Roman&quot;,&quot;serif&quot;;color:black"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><font size=3D"2" color=3D"=
#ff6600" face=3D"Arial"><span style=3D"font-size:10.0pt;font-family:&quot;A=
rial&quot;,&quot;sans-serif&quot;;color:#FF6600;text-decoration:none">steph=
ane.litkowski@orange.com</span></font></a></span></font><font color=3D"blac=
k"><span style=3D"color:black"><o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><font size=3D"3" color=
=3D"black" face=3D"Times New Roman"><span lang=3D"FR" style=3D"font-size:12=
.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;color:black"=
>&nbsp;</span></font><font color=3D"black"><span style=3D"color:black"><o:p=
></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"black" face=3D"Calibri"><s=
pan style=3D"font-size:11.0pt;color:black">&nbsp;<o:p></o:p></span></font><=
/p>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">______________________________________________=
___________________________________________________________________________=
<o:p></o:p></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">&nbsp;<o:p></o:p></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">Ce message et ses pieces jointes peuvent conte=
nir des informations confidentielles ou privilegiees et ne doivent donc<o:p=
></o:p></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">pas etre diffuses, exploites ou copies sans au=
torisation. Si vous avez recu ce message par erreur, veuillez le signaler<o=
:p></o:p></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">a l'expediteur et le detruire ainsi que les pi=
eces jointes. Les messages electroniques etant susceptibles d'alteration,<o=
:p></o:p></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">Orange decline toute responsabilite si ce mess=
age a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></font></pre=
>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">&nbsp;<o:p></o:p></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">This message and its attachments may contain c=
onfidential or privileged information that may be protected by law;<o:p></o=
:p></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">they should not be distributed, used or copied=
 without authorisation.<o:p></o:p></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">If you have received this email in error, plea=
se notify the sender and delete this message and its attachments.<o:p></o:p=
></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">As emails may be altered, Orange is not liable=
 for messages that have been modified, changed or falsified.<o:p></o:p></sp=
an></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">Thank you.<o:p></o:p></span></font></pre>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">______________________________________________=
___________________________________________________________________________=
<o:p></o:p></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">&nbsp;<o:p></o:p></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">Ce message et ses pieces jointes peuvent conte=
nir des informations confidentielles ou privilegiees et ne doivent donc<o:p=
></o:p></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">pas etre diffuses, exploites ou copies sans au=
torisation. Si vous avez recu ce message par erreur, veuillez le signaler<o=
:p></o:p></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">a l'expediteur et le detruire ainsi que les pi=
eces jointes. Les messages electroniques etant susceptibles d'alteration,<o=
:p></o:p></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">Orange decline toute responsabilite si ce mess=
age a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></font></pre=
>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">&nbsp;<o:p></o:p></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">This message and its attachments may contain c=
onfidential or privileged information that may be protected by law;<o:p></o=
:p></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">they should not be distributed, used or copied=
 without authorisation.<o:p></o:p></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">If you have received this email in error, plea=
se notify the sender and delete this message and its attachments.<o:p></o:p=
></span></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">As emails may be altered, Orange is not liable=
 for messages that have been modified, changed or falsified.<o:p></o:p></sp=
an></font></pre>
<pre><font size=3D"3" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:12.0pt;color:black">Thank you.<o:p></o:p></span></font></pre>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</body>
</html>

--_000_2E4BB27CAB87BF43B4207C0E55860F182602DCeusaamb103ericsso_--

--_004_2E4BB27CAB87BF43B4207C0E55860F182602DCeusaamb103ericsso_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: inline; filename="image001.gif"; size=381;
	creation-date="Mon, 23 Feb 2015 18:27:40 GMT";
	modification-date="Mon, 23 Feb 2015 18:27:40 GMT"
Content-ID: <image001.gif@01D04F53.59D16780>
Content-Transfer-Encoding: base64

R0lGODlhKAAoAMQAAP+MQP+zgP/17//s3/+DMP/iz/+fYP+8j/9wEP95IP/Gn/+WUP/Pr/+pcP/Z
v/////9mAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAAA
AAAALAAAAAAoACgAAAX6oAONZGmeaEqKauum7Cu/8Wyj9a2P+X73vhkwSCPuhkYVMolj2pbOEjTK
oxatrSlVG+U6vUxwUmwkE81BtE99xGbdSjhMPgo4BAoA+wUICAR6IwQODwMNEAcOigAFhQYQDgoD
DwcQBJOKBIOFDQmaCCyTB416hQcBBQuTEA8Cow8EBQINpHcGhAkrEAkPChAAD3YPCLuSDw+sIgEP
wCILzK0OjY9VBJS/wYQjfwaNyRDLzRAG0AMB5wC6ENyEt8jWDAsCyA/KzJN+zLILqLlVv/OuaYPU
alU9cMwuPSCl8AEDYv8EQbwRgAEABcziJFl2bMmeEQgATEwRAgA7

--_004_2E4BB27CAB87BF43B4207C0E55860F182602DCeusaamb103ericsso_--


From nobody Mon Feb 23 11:51:49 2015
Return-Path: <lhotka@nic.cz>
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 2FC771A6EF0; Mon, 23 Feb 2015 11:51:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.361
X-Spam-Level: 
X-Spam-Status: No, score=-0.361 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 VBF_9nHeOI8y; Mon, 23 Feb 2015 11:51:44 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A9AF1A6EE8; Mon, 23 Feb 2015 11:51:44 -0800 (PST)
Received: from [IPv6:2a01:5e0:29:ffff:54ad:feb6:3ad3:9330] (unknown [IPv6:2a01:5e0:29:ffff:54ad:feb6:3ad3:9330]) by mail.nic.cz (Postfix) with ESMTPSA id 24D461439D9; Mon, 23 Feb 2015 20:51:43 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nic.cz; s=default; t=1424721103; bh=SNw2gcIa7oYnKAB02JsliocrcuQ84snZamQwe/53F7g=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=Nx8yAY9sr/S5RpEv1APTo782NZc0H8NIrgGawZ6IfS81fzf6c9IXqyssPwjXiVP4d BhoMjMRXMna/NtURJsVA35GFy4EpqWHl8PrIOdi5W1Tzwmole983/1qcxXs0YvpZVE t+dM+2SHMsyTCfSPMI6TTMC6oyj1/4z3+PzBwyJY=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Subject: Re: [Rtg-yang-coord] rtg-cfg hierachy (PLEASE REPLY TO THIS ONE WITH THE CORRECT MAIL ALIASES)
From: Ladislav Lhotka <lhotka@nic.cz>
In-Reply-To: <20150223.203140.655664249325530031.mbj@tail-f.com>
Date: Mon, 23 Feb 2015 20:51:44 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A0379E8-AFA9-4DCB-B5D5-1148985778E0@nic.cz>
References: <14011_1423852286_54DE42FE_14011_2207_1_D103AD28.E652%acee@cisco.com> <54E47928.8050108@orange.com> <m2a904zti2.fsf@birdie.labs.nic.cz> <20150223.203140.655664249325530031.mbj@tail-f.com>
To: =?utf-8?Q?Martin_Bj=C3=B6rklund?= <mbj@tail-f.com>
X-Mailer: Apple Mail (2.2070.6)
X-Virus-Scanned: clamav-milter 0.98.1 at mail
X-Virus-Status: Clean
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/iL8BhvxGkEfKyT59Qypm5qb9MZM>
Cc: rtg-yang-coord@ietf.org, thomas.morin@orange.com, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2015 19:51:46 -0000

> On 23 Feb 2015, at 20:31, Martin Bjorklund <mbj@tail-f.com> wrote:
>=20
> Ladislav Lhotka <lhotka@nic.cz> wrote:
>> Thomas Morin <thomas.morin@orange.com> writes:
>>> Additionally, Lada, you say that based on my comments "in rev. -03 =
the=20
>>> list of RIBs (then called "routing-table") was the moved out of the=20=

>>> routing instance (then called "router") and became global.". But if =
I=20
>>> look at -03, "routing-table" is still a child of "router".  The =
change=20
>>> to make "routing-table" global was made in -05.
>>>=20
>>> I guess you need to find out what was the motivation for the change =
in=20
>>> -05, a few months after my initial comments were address.
>>=20
>> Yes, you are right, it seems the immediate motivation for this change
>> was this review by Martin Bjorklund:
>>=20
>> http://www.ietf.org/mail-archive/web/netmod/current/msg06962.html
>=20
> I don't really understand what exactly in this review led to that
> change?

Last bullet about sec. 5.2:

o  5.2

               list recipient-routing-table {
                 ...
                 leaf name {
                   type leafref {
                     path "/routing/router/routing-tables/"
                        + "routing-table/name";
                   }

  This should also be a relative path.

A relative path would make sense only if the leafref points within the =
same router (later renamed to routing-instance). Consequently, it would =
be impossible to pass routes between tables in different routers.

On the other hand, the global path as shown above could lead to =
ambiguous references, because different routers could have =
routing-tables with identical names.

I therefore decided to keep the global path but make sure the names of =
routing tables are globally unique. Having a single list of =
routing-tables was the most straightforward way to achieve this.

Lada

>=20
>=20
> /martin

--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C





From nobody Mon Feb 23 12:15:43 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 0F2E41A6F01 for <rtgwg@ietfa.amsl.com>; Mon, 23 Feb 2015 12:15:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.999 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, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2aiKndRX9sjm for <rtgwg@ietfa.amsl.com>; Mon, 23 Feb 2015 12:15:40 -0800 (PST)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) (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 EF5861A6EF9 for <rtgwg@ietf.org>; Mon, 23 Feb 2015 12:15:39 -0800 (PST)
Received: by mail-ob0-f169.google.com with SMTP id wp4so39036510obc.0 for <rtgwg@ietf.org>; Mon, 23 Feb 2015 12:15:39 -0800 (PST)
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=1iOZWmW528vjB9y5NVmzTOFDUfA0pMv4trGKo+w6G3M=; b=oFTP5eQWzxq8prG03wJM9MjGIeSk34hJCs7O0slT3PLXFcNPIjbeTzBgYMt5j4rpJL 7xqpJWhmEItm6EGE021UdinGOQ4Mj1JsH0mVr9nHhcPtPgbMeOlIANzjscjG+3gwPl7i GHHE1+klClWqwVARoi7HYsVtmLYQfJUoaJEkaWXatpwFkpSKsR/4CqzZu5mQjghMusNo BpEJPwoNCZ3wNC4J78P6V0PiFoIhMKrU5W7GBVM3VKAlXW0sQgTWDGSTM/IkpK51rX06 hOM3AAaW4X0oFoHiSizXD2AIAJXXz0q0iCpSzDswKdSdW+cAOsEx6igEKOIUoDG1xgFP /25g==
MIME-Version: 1.0
X-Received: by 10.182.1.202 with SMTP id 10mr8799444obo.56.1424722539279; Mon, 23 Feb 2015 12:15:39 -0800 (PST)
Received: by 10.60.94.20 with HTTP; Mon, 23 Feb 2015 12:15:38 -0800 (PST)
Date: Mon, 23 Feb 2015 15:15:38 -0500
Message-ID: <CAG4d1rfMo=BBgq3WCRphRJFvX9B1e_kozgJ+XGhC9HVsRi8Ksw@mail.gmail.com>
Subject: RTGWG chairs
From: Alia Atlas <akatlas@gmail.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>, Chris Bowers <cbowers@juniper.net>
Content-Type: multipart/alternative; boundary=001a11347aacdb7947050fc710a5
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/N6T11NfmvuWWKYijFdDmEznXyqg>
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, 23 Feb 2015 20:15:42 -0000

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

Hi RTGWG,

>From Weds evening of IETF-92, Alvaro will be serving as Routing AD so it
isn't appropriate for him to continue to chair a WG in the Routing Area.
Thus, Alvaro is stepping down as co-chair of RTGWG.  I really appreciate
the hard work that Alvaro has done as RTGWG co-chair.

I have consulted with Alvaro, Deborah, Adrian, and Jeff, and have decided
to appoint Chris Bowers to serve in this role.  Chris will be busy ramping
up.  I expect the handover to be finished in Dallas.

Chris can be reached at cbowers@juniper.net.

Thanks,
Alia

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

<div dir=3D"ltr"><div>Hi RTGWG,</div><div><br></div><div>From Weds evening =
of IETF-92, Alvaro will be serving as Routing AD so it isn&#39;t appropriat=
e for him to continue to chair a WG in the Routing Area.=C2=A0 Thus, Alvaro=
 is stepping down as co-chair of RTGWG.=C2=A0 I really appreciate the hard =
work that Alvaro has done as RTGWG co-chair.</div><div><br></div><div>I hav=
e consulted with Alvaro, Deborah, Adrian, and Jeff, and have decided to app=
oint Chris Bowers to serve in this role.=C2=A0 Chris will be busy ramping u=
p.=C2=A0 I expect the handover to be finished in Dallas.</div><div><br></di=
v><div>Chris can be reached at <a href=3D"mailto:cbowers@juniper.net">cbowe=
rs@juniper.net</a>.</div><div><br></div><div>Thanks,</div><div>Alia</div><d=
iv><br></div></div>

--001a11347aacdb7947050fc710a5--


From nobody Tue Feb 24 06:59:30 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 6D13A1A1A51 for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 06:59:29 -0800 (PST)
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, 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 OAzoEi2bftIF for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 06:59:27 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0743.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:743]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 768E71A0203 for <rtgwg@ietf.org>; Tue, 24 Feb 2015 06:59:27 -0800 (PST)
Received: from hannes-mba.local (193.110.55.11) by CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) with Microsoft SMTP Server (TLS) id 15.1.93.16; Tue, 24 Feb 2015 14:59:00 +0000
Received: from hannes-mba.local (localhost [IPv6:::1]) by hannes-mba.local (Postfix) with ESMTP id 07A0AF5334F; Tue, 24 Feb 2015 15:58:45 +0100 (CET)
Date: Tue, 24 Feb 2015 15:58:44 +0100
From: Hannes Gredler <hannes@juniper.net>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
Subject: Re: LFA manageability : per AF config => feedback required
Message-ID: <20150224145844.GA2688@hannes-mba.local>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <D110BDBB.20D32%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2E9BD@xmb-aln-x02.cisco.com> <D110C66B.20D87%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2EA28@xmb-aln-x02.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <F3ADE4747C9E124B89F0ED2180CC814F4EF2EA28@xmb-aln-x02.cisco.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Originating-IP: [193.110.55.11]
X-ClientProxiedBy: AM3PR06CA027.eurprd06.prod.outlook.com (10.141.192.145) To CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=hannes@juniper.net; 
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB443;
X-Microsoft-Antispam-PRVS: <CO1PR05MB443DA005569AB64B45E3671FB160@CO1PR05MB443.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005004); SRVR:CO1PR05MB443; 
X-Forefront-PRVS: 04976078F0
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(377454003)(24454002)(189002)(199003)(92566002)(19580395003)(110136001)(19580405001)(83506001)(93886004)(105586002)(106356001)(66066001)(2950100001)(77096005)(68736005)(15975445007)(64706001)(47776003)(87976001)(77156002)(62966003)(23726002)(46102003)(101416001)(76506005)(86362001)(98436002)(97736003)(46406003)(40100003)(122386002)(122856001)(50986999)(54356999)(76176999)(33656002)(97756001)(50466002)(579124003); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB443; H:hannes-mba.local; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB443;
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Feb 2015 14:59:00.0315 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB443
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/pR2OE6rNSJmCcQWknF7lH7EzF68>
Cc: Pushpasis Sarkar <psarkar@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: Tue, 24 Feb 2015 14:59:29 -0000

hi les,

HG> inline.

On Mon, Feb 23, 2015 at 06:42:11AM +0000, Les Ginsberg (ginsberg) wrote:
|    Pushpassis -
| 
| 
| 
|    Conceptually, there are two different functionalities being discussed:
| 
| 
| 
|    1)Supporting selection of what prefixes are eligible for protection. This
|    is what Section 5.1 of the draft discusses.
| 
| 
| 
|    2)For the set of prefixes which are eligible for protection, supporting
|    policy to choose between multiple LFA candidates. This is discussed in
|    Section 5.2 of the draft.
| 
| 
| 
|    How you choose to implement this support is outside the scope of both the
|    draft and this discussion.
| 

yes and no; -

the troubling thing is that this document serves as a blueprint for the YANG
modeling. - as soon as we keep the optional nature of things in the yang model
itself i am fine, but then derek has to stop insisting on this in YANG.


| 
|    From: Pushpasis Sarkar [mailto:psarkar@juniper.net]
|    Sent: Sunday, February 22, 2015 10:33 PM
|    To: Les Ginsberg (ginsberg); Jeff Tantsura;
|    [1]stephane.litkowski@orange.cothe abiloity to limit the set of prefixes
|    m; rtgwg@ietf.org
|    Subject: Re: LFA manageability : per AF config => feedback required
| 
| 
| 
|    Hi Les,
| 
| 
| 
|    From: "Les Ginsberg (ginsberg)" <[2]ginsberg@cisco.com>
|    Date: Monday, February 23, 2015 at 11:46 AM
|    To: Pushpasis Sarkar <[3]psarkar@juniper.net>, Jeff Tantsura
|    <[4]jeff.tantsura@ericsson.com>, "[5]stephane.litkowski@orange.com"
|    <[6]stephane.litkowski@orange.com>, "[7]rtgwg@ietf.org"
|    <[8]rtgwg@ietf.org>
|    Subject: RE: LFA manageability : per AF config => feedback required
| 
| 
| 
|    [Les:] "backup-selection-policy" specifies which member of an LFA set
|    should be preferred when there are multiple candidates for protecting a
|    given prefix. What we are discussing here is controlling which prefixes
|    are eligible for protection. These ae two different concepts.
| 
| 
| 
|    [Pushpasis] Well, it is not only preferring. It can also be
|    not-preferring-any (or pruning). So if no protection for any IPv6 is
|    required, it can be achieved by a policy as belows:
| 
| 
| 
|    Destination ipv6-all {
| 
|    {
| 
|       Interface all
| 
|       {
| 
|           Neighbor exclude all;
| 
|       }
| 
|    }
| 
| 
| 
| References
| 
|    Visible links
|    1. mailto:stephane.litkowski@orange.cothe
|    2. mailto:ginsberg@cisco.com
|    3. mailto:psarkar@juniper.net
|    4. mailto:jeff.tantsura@ericsson.com
|    5. mailto:stephane.litkowski@orange.com
|    6. mailto:stephane.litkowski@orange.com
|    7. mailto:rtgwg@ietf.org
|    8. mailto:rtgwg@ietf.org

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


From nobody Tue Feb 24 07:03:17 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 9E4F91A1BD9 for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 07:03:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.998
X-Spam-Level: 
X-Spam-Status: No, score=0.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_84=0.6, MANGLED_BELOW=2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 UGM4IUbyxtBO for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 07:03:00 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0726.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::726]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DBC01A1B1E for <rtgwg@ietf.org>; Tue, 24 Feb 2015 07:03:00 -0800 (PST)
Received: from hannes-mba.local (193.110.55.11) by DM2PR05MB448.namprd05.prod.outlook.com (10.141.104.152) with Microsoft SMTP Server (TLS) id 15.1.93.16; Tue, 24 Feb 2015 15:02:43 +0000
Received: from hannes-mba.local (localhost [IPv6:::1]) by hannes-mba.local (Postfix) with ESMTP id 2BB9EF533EC; Tue, 24 Feb 2015 16:02:28 +0100 (CET)
Date: Tue, 24 Feb 2015 16:02:28 +0100
From: Hannes Gredler <hannes@juniper.net>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
Subject: Re: LFA manageability : per AF config => feedback required
Message-ID: <20150224150228.GB2688@hannes-mba.local>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <5876_1424675401_54EAD249_5876_2527_11_9E32478DFA9976438E7A22F69B08FF9215C157AC@OPEXCLILM34.corporate.adroot.infra.ftgroup> <F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71@xmb-aln-x02.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71@xmb-aln-x02.cisco.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Originating-IP: [193.110.55.11]
X-ClientProxiedBy: DB4PR04CA0031.eurprd04.prod.outlook.com (25.160.41.41) To DM2PR05MB448.namprd05.prod.outlook.com (10.141.104.152)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=hannes@juniper.net; 
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR05MB448;
X-Microsoft-Antispam-PRVS: <DM2PR05MB448B620057F56A7DD0426DBFB160@DM2PR05MB448.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005004); SRVR:DM2PR05MB448; 
X-Forefront-PRVS: 04976078F0
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(199003)(24454002)(377454003)(40764003)(23726002)(92566002)(5890100001)(62966003)(77156002)(2950100001)(15975445007)(87976001)(77096005)(122856001)(68736005)(83506001)(76506005)(93886004)(19580405001)(122386002)(19580395003)(47776003)(46102003)(105586002)(110136001)(33656002)(98436002)(97756001)(46406003)(101416001)(106356001)(97736003)(54356999)(76176999)(40100003)(64706001)(50466002)(50986999)(66066001)(86362001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR05MB448; H:hannes-mba.local; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:DM2PR05MB448;
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Feb 2015 15:02:43.7940 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR05MB448
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/dIUKn8kusblQfLvKc76Gyvye6gY>
Cc: Pushpasis Sarkar <psarkar@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: Tue, 24 Feb 2015 15:03:07 -0000

On Mon, Feb 23, 2015 at 03:55:32PM +0000, Les Ginsberg (ginsberg) wrote:
|    I can imagine cases in which the per AF enabling might make sense (e.g.
|    when the network associated w one address family is deemed non-critical).


HG> as it is unlikely that operators will tun off IPv4 protection,
    may i have a ask that you repeat that quote above in the 6man
    meeting ;-) ? - effectifely you're saying "IPv6 may be considered
    as less critical", and therefore we SHOULD provide a knob
    to turn protection off.

| 
| 
|    Section 5.1 is a SHOULD - as is most of the document. It is therefore a
|    suggestion as to what an implementation should provide. If a given
|    implementer thinks this is either too onerous or not useful they can omit
|    it w/o being in violation. But I see no reason to eliminate this - and in
|    actual practice I would expect the cost of supporting such a knob to be
|    low cost. It is hard for me to see this as controversial.
| 
| 
| 
|       Les
| 
| 
| 
| 
| 
|    From: stephane.litkowski@orange.com [mailto:stephane.litkowski@orange.com]
|    Sent: Sunday, February 22, 2015 11:10 PM
|    To: Les Ginsberg (ginsberg); Pushpasis Sarkar; Jeff Tantsura;
|    rtgwg@ietf.org
|    Subject: RE: LFA manageability : per AF config => feedback required
| 
| 
| 
|    [Les:] I think your point here is that the LFA calculation is AF
|    independent within a given topology - but resources are consumed
|    independent of how many computations are required- giving an operator the
|    ability to determine which prefixes are most critical seems useful. That
|    could be per AF or per prefix.
| 
| 
| 
|    [SLI] Agree but is the "resource saving" point strong enough to mandate
|    per AF activation ?
| 
| 
| 
|    From: Les Ginsberg (ginsberg) [[1]mailto:ginsberg@cisco.com]
|    Sent: Monday, February 23, 2015 05:01
|    To: Pushpasis Sarkar; Jeff Tantsura; LITKOWSKI Stephane SCE/IBNF;
|    [2]rtgwg@ietf.org
|    Subject: RE: LFA manageability : per AF config => feedback required
| 
| 
| 
|    Pushpassis -
| 
| 
| 
|    From: rtgwg [[3]mailto:rtgwg-bounces@ietf.org] On Behalf Of Pushpasis
|    Sarkar
|    Sent: Friday, February 20, 2015 3:28 AM
|    To: Jeff Tantsura; [4]stephane.litkowski@orange.com; [5]rtgwg@ietf.org
|    Subject: Re: LFA manageability : per AF config => feedback required
| 
| 
| 
|    HI Jeff et al,
| 
| 
| 
|    I can think of a reason to have a knob per-level(or per-area) or per ISIS
|    topology(note in ISIS a topology in ISIS always corresponds to a single
|    AF,)
| 
| 
| 
|    [Les:] This is a common mistake to make. If one simply uses RFC 5308, then
|    IPv6 prefixes can be advertised in the same topology as IPv4 (MTID #0) -
|    and there are implementations which support this. More generally, from the
|    protocol's POV a given topology can support any combinations of address
|    families. It is only a convention because of the reserved MTIDs specified
|    in RFC 5120 that certain MTIDs are "IPv6 only". But if one looks at the
|    protocol capabilities such a restriction does not exist in general.
| 
| 
| 
|    Interestingly you contradicted yourself below. J
| 
|    But I did want to set the record straight on this point - hopefully we are
|    in agreement.
| 
| 
| 
|    and per realm and topology in OSPF. But I cannot think of a reason of why
|    within the same topology we need another set of knobs for each AF. Here,
|    by AF I understand IPV4 or IPv6.
| 
| 
| 
|    When both IPV4 and IPV6 are part of the same IGP topology, there is only
|    one set of backup computations needed to protect both IPV4 and IPv6
|    traffic.
| 
| 
| 
|    Also I cannot think of any motivation for an operator to turn on
|    protection on only one AF and does not want to turn on for the other even
|    if both AFs has been deployed for normal forwarding.
| 
| 
| 
|    [Les:] I think your point here is that the LFA calculation is AF
|    independent within a given topology - but resources are consumed
|    independent of how many computations are required- giving an operator the
|    ability to determine which prefixes are most critical seems useful. That
|    could be per AF or per prefix.
| 
| 
| 
|       Les
| 
| 
| 
|    Thanks
| 
|    -Pushpasis
| 
| 
| 
|    From: Jeff Tantsura <[6]jeff.tantsura@ericsson.com>
|    Date: Friday, February 20, 2015 at 12:59 PM
|    To: "[7]stephane.litkowski@orange.com" <[8]stephane.litkowski@orange.com>,
|    "[9]rtgwg@ietf.org" <[10]rtgwg@ietf.org>
|    Subject: Re: LFA manageability : per AF config => feedback required
| 
| 
| 
|    Hi Stephane,
| 
| 
| 
|    /chair hat off
| 
| 
| 
|    IMO in disjoined topologies one should have flexibility to enable/disable
|    LFA as per AF.
| 
| 
| 
| 
| 
|    Cheers,
| 
|    Jeff
| 
| 
| 
|    From: "[11]stephane.litkowski@orange.com"
|    <[12]stephane.litkowski@orange.com>
|    Date: Thursday, February 19, 2015 at 11:21 PM
|    To: "[13]rtgwg@ietf.org" <[14]rtgwg@ietf.org>
|    Subject: LFA manageability : per AF config => feedback required
| 
| 
| 
|      Hi Folks,
| 
| 
| 
|      As you know, LFA manageability draft is in final phasis ...
| 
|      The current document states per AF granularity activation as a SHOULD.
| 
|      "
| 
|   [15]5.1.  LFA enabling/disabling scope
| 
| 
| 
| 
| 
|     The granularity of LFA activation should be controlled (as alternate
| 
|     nexthop consume memory in forwarding plane).
| 
| 
| 
|     An implementation of LFA SHOULD allow its activation with the
| 
|     following criteria:
| 
| 
| 
|     o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,
| 
|        LDP IPv6 unicast ...
| 
| 
| 
|     o  Per routing context : VRF, virtual/logical router, global routing
| 
|        table, ...
| 
| 
| 
|      "
| 
| 
| 
|      In the framework of ISIS/OSPF yang modelization, we are challenging this
|      statement, do we really need to force implementation to support this
|      "per AF" granularity ?
| 
| 
| 
|      Please provide as soon as possible your feedback on this and also
|      provide clear drivers to support or not per AF activation of LFA.
| 
| 
| 
| 
| 
|      Thanks for your help !
| 
| 
| 
| 
| 
|      [16]Orange logo
| 
| 
| 
|      Stephane Litkowski
|      Network Architect
|      Orange/SCE/EQUANT/IBNF/ENDD/NDE
| 
|      Orange Expert Future Networks
| 
|      phone: [17]+33 2 23 28 49 83
|      mobile: [18]+33 6 37 86 97 52
|      [19]stephane.litkowski@orange.com
| 
| 
| 
| 
| 
|  _________________________________________________________________________________________________________________________
| 
| 
| 
|  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.
| 
|  _________________________________________________________________________________________________________________________
| 
| 
| 
|  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.
| 
| References
| 
|    Visible links
|    1. mailto:ginsberg@cisco.com
|    2. mailto:rtgwg@ietf.org
|    3. mailto:rtgwg-bounces@ietf.org
|    4. mailto:stephane.litkowski@orange.com
|    5. mailto:rtgwg@ietf.org
|    6. mailto:jeff.tantsura@ericsson.com
|    7. mailto:stephane.litkowski@orange.com
|    8. mailto:stephane.litkowski@orange.com
|    9. mailto:rtgwg@ietf.org
|   10. mailto:rtgwg@ietf.org
|   11. mailto:stephane.litkowski@orange.com
|   12. mailto:stephane.litkowski@orange.com
|   13. mailto:rtgwg@ietf.org
|   14. mailto:rtgwg@ietf.org
|   15. https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#section-5.1
|   16. http://www.orange.com/
|   17. https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20
|   18. https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20
|   19. mailto:stephane.litkowski@orange.com



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


From nobody Tue Feb 24 07:04:14 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 1076F1A1A57 for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 07:04:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.302
X-Spam-Level: 
X-Spam-Status: No, score=-1.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_84=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 PjGOCBNqhbQY for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 07:04:10 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0751.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::751]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96A0B1A003B for <rtgwg@ietf.org>; Tue, 24 Feb 2015 07:04:09 -0800 (PST)
Received: from hannes-mba.local (193.110.55.11) by DM2PR05MB447.namprd05.prod.outlook.com (10.141.104.150) with Microsoft SMTP Server (TLS) id 15.1.93.16; Tue, 24 Feb 2015 15:03:47 +0000
Received: from hannes-mba.local (localhost [IPv6:::1]) by hannes-mba.local (Postfix) with ESMTP id 04ACEF53465; Tue, 24 Feb 2015 16:03:32 +0100 (CET)
Date: Tue, 24 Feb 2015 16:03:32 +0100
From: Hannes Gredler <hannes@juniper.net>
To: "Acee Lindem (acee)" <acee@cisco.com>
Subject: Re: LFA manageability : per AF config => feedback required
Message-ID: <20150224150331.GC2688@hannes-mba.local>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <5876_1424675401_54EAD249_5876_2527_11_9E32478DFA9976438E7A22F69B08FF9215C157AC@OPEXCLILM34.corporate.adroot.infra.ftgroup> <F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71@xmb-aln-x02.cisco.com> <D110DAB2.EEDA%acee@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <D110DAB2.EEDA%acee@cisco.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Originating-IP: [193.110.55.11]
X-ClientProxiedBy: AM3PR06CA049.eurprd06.prod.outlook.com (10.141.192.167) To DM2PR05MB447.namprd05.prod.outlook.com (10.141.104.150)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=hannes@juniper.net; 
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR05MB447;
X-Microsoft-Antispam-PRVS: <DM2PR05MB447E6896053452E1A879DDEB8160@DM2PR05MB447.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005004); SRVR:DM2PR05MB447; 
X-Forefront-PRVS: 04976078F0
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(40764003)(199003)(377454003)(189002)(98436002)(2950100001)(105586002)(87976001)(47776003)(76506005)(122386002)(50466002)(106356001)(62966003)(77156002)(19580405001)(122856001)(101416001)(54356999)(46102003)(50986999)(33656002)(68736005)(97736003)(93886004)(76176999)(15975445007)(83506001)(92566002)(64706001)(77096005)(5890100001)(86362001)(40100003)(66066001)(23676002)(19580395003)(110136001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR05MB447; H:hannes-mba.local; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:DM2PR05MB447;
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Feb 2015 15:03:47.7754 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR05MB447
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/R-wuitDndE3U8ljZSRrgHF6_Ce8>
Cc: "Les Ginsberg \(ginsberg\)" <ginsberg@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>, Pushpasis Sarkar <psarkar@juniper.net>
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, 24 Feb 2015 15:04:12 -0000

HG> that IPv6 is less critical than IPv4 ? -
    the IESG review will be a lot of fun then - i'll make some popcorn ...

On Mon, Feb 23, 2015 at 06:26:15PM +0000, Acee Lindem (acee) wrote:
|    I agree with Les.
|    Acee
|    From: "Les Ginsberg (ginsberg)" <[1]ginsberg@cisco.com>
|    Date: Monday, February 23, 2015 at 10:55 AM
|    To: Stephane Litkowski <[2]stephane.litkowski@orange.com>, Pushpasis
|    Sarkar <[3]psarkar@juniper.net>, Jeff Tantsura
|    <[4]jeff.tantsura@ericsson.com>, Routing WG <[5]rtgwg@ietf.org>
|    Subject: RE: LFA manageability : per AF config => feedback required
| 
|      Stephane â€“
| 
| 
| 
|      I can imagine cases in which the per AF enabling might make sense (e.g.
|      when the network associated w one address family is deemed
|      non-critical).
| 
| 
| 
|      Section 5.1 is a SHOULD â€“ as is most of the document. It is therefore
|      a suggestion as to what an implementation should provide. If a given
|      implementer thinks this is either too onerous or not useful they can
|      omit it w/o being in violation. But I see no reason to eliminate this
|      â€“ and in actual practice I would expect the cost of supporting such a
|      knob to be low cost. It is hard for me to see this as controversial.
| 
| 
| 
|         Les
| 
| 
| 
| 
| 
|      From: [6]stephane.litkowski@orange.com
|      [[7]mailto:stephane.litkowski@orange.com]
|      Sent: Sunday, February 22, 2015 11:10 PM
|      To: Les Ginsberg (ginsberg); Pushpasis Sarkar; Jeff Tantsura;
|      [8]rtgwg@ietf.org
|      Subject: RE: LFA manageability : per AF config => feedback required
| 
| 
| 
|      [Les:] I think your point here is that the LFA calculation is AF
|      independent within a given topology â€“ but resources are consumed
|      independent of how many computations are required- giving an operator
|      the ability to determine which prefixes are most critical seems useful.
|      That could be per AF or per prefix.
| 
| 
| 
|      [SLI] Agree but is the â€œresource savingâ€� point strong enough to
|      mandate per AF activation ?
| 
| 
| 
|      From: Les Ginsberg (ginsberg) [[9]mailto:ginsberg@cisco.com]
|      Sent: Monday, February 23, 2015 05:01
|      To: Pushpasis Sarkar; Jeff Tantsura; LITKOWSKI Stephane SCE/IBNF;
|      [10]rtgwg@ietf.org
|      Subject: RE: LFA manageability : per AF config => feedback required
| 
| 
| 
|      Pushpassis -
| 
| 
| 
|      From: rtgwg [[11]mailto:rtgwg-bounces@ietf.org] On Behalf Of Pushpasis
|      Sarkar
|      Sent: Friday, February 20, 2015 3:28 AM
|      To: Jeff Tantsura; [12]stephane.litkowski@orange.com; [13]rtgwg@ietf.org
|      Subject: Re: LFA manageability : per AF config => feedback required
| 
| 
| 
|      HI Jeff et al,
| 
| 
| 
|      I can think of a reason to have a knob per-level(or per-area) or per
|      ISIS topology(note in ISIS a topology in ISIS always corresponds to a
|      single AF,)
| 
| 
| 
|      [Les:] This is a common mistake to make. If one simply uses RFC 5308,
|      then IPv6 prefixes can be advertised in the same topology as IPv4 (MTID
|      #0) â€“ and there are implementations which support this. More
|      generally, from the protocolâ€™s POV a given topology can support any
|      combinations of address families. It is only a convention because of the
|      reserved MTIDs specified in RFC 5120 that certain MTIDs are â€œIPv6
|      onlyâ€�. But if one looks at the protocol capabilities such a
|      restriction does not exist in general.
| 
| 
| 
|      Interestingly you contradicted yourself below. J
| 
|      But I did want to set the record straight on this point â€“ hopefully we
|      are in agreement.
| 
| 
| 
|      and per realm and topology in OSPF. But I cannot think of a reason of
|      why within the same topology we need another set of knobs for each AF.
|      Here, by AF I understand IPV4 or IPv6.
| 
| 
| 
|      When both IPV4 and IPV6 are part of the same IGP topology, there is only
|      one set of backup computations needed to protect both IPV4 and IPv6
|      traffic.
| 
| 
| 
|      Also I cannot think of any motivation for an operator to turn on
|      protection on only one AF and does not want to turn on for the other
|      even if both AFs has been deployed for normal forwarding.
| 
| 
| 
|      [Les:] I think your point here is that the LFA calculation is AF
|      independent within a given topology â€“ but resources are consumed
|      independent of how many computations are required- giving an operator
|      the ability to determine which prefixes are most critical seems useful.
|      That could be per AF or per prefix.
| 
| 
| 
|         Les
| 
| 
| 
|      Thanks
| 
|      -Pushpasis
| 
| 
| 
|      From: Jeff Tantsura <[14]jeff.tantsura@ericsson.com>
|      Date: Friday, February 20, 2015 at 12:59 PM
|      To: "[15]stephane.litkowski@orange.com"
|      <[16]stephane.litkowski@orange.com>, "[17]rtgwg@ietf.org"
|      <[18]rtgwg@ietf.org>
|      Subject: Re: LFA manageability : per AF config => feedback required
| 
| 
| 
|      Hi Stephane,
| 
| 
| 
|      /chair hat off
| 
| 
| 
|      IMO in disjoined topologies one should have flexibility to
|      enable/disable LFA as per AF.
| 
| 
| 
| 
| 
|      Cheers,
| 
|      Jeff
| 
| 
| 
|      From: "[19]stephane.litkowski@orange.com"
|      <[20]stephane.litkowski@orange.com>
|      Date: Thursday, February 19, 2015 at 11:21 PM
|      To: "[21]rtgwg@ietf.org" <[22]rtgwg@ietf.org>
|      Subject: LFA manageability : per AF config => feedback required
| 
| 
| 
|        Hi Folks,
| 
| 
| 
|        As you know, LFA manageability draft is in final phasis
| 
|        The current document states per AF granularity activation as a SHOULD.
| 
|        â€œ
| 
|   [23]5.1.  LFA enabling/disabling scope
| 
| 
| 
| 
| 
|     The granularity of LFA activation should be controlled (as alternate
| 
|     nexthop consume memory in forwarding plane).
| 
| 
| 
|     An implementation of LFA SHOULD allow its activation with the
| 
|     following criteria:
| 
| 
| 
|     o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,
| 
|        LDP IPv6 unicast ...
| 
| 
| 
|     o  Per routing context : VRF, virtual/logical router, global routing
| 
|        table, ...
| 
| 
| 
|        â€œ
| 
| 
| 
|        In the framework of ISIS/OSPF yang modelization, we are challenging
|        this statement, do we really need to force implementation to support
|        this â€œper AFâ€� granularity ?
| 
| 
| 
|        Please provide as soon as possible your feedback on this and also
|        provide clear drivers to support or not per AF activation of LFA.
| 
| 
| 
| 
| 
|        Thanks for your help !
| 
| 
| 
| 
| 
|        [24]Orange logo
| 
| 
| 
|        Stephane Litkowski
|        Network Architect
|        Orange/SCE/EQUANT/IBNF/ENDD/NDE
| 
|        Orange Expert Future Networks
| 
|        phone: [25]+33 2 23 28 49 83
|        mobile: [26]+33 6 37 86 97 52
|        [27]stephane.litkowski@orange.com
| 
| 
| 
| 
| 
|  _________________________________________________________________________________________________________________________
| 
| 
| 
|  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.
| 
|  _________________________________________________________________________________________________________________________
| 
| 
| 
|  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.
| 
| References
| 
|    Visible links
|    1. mailto:ginsberg@cisco.com
|    2. mailto:stephane.litkowski@orange.com
|    3. mailto:psarkar@juniper.net
|    4. mailto:jeff.tantsura@ericsson.com
|    5. mailto:rtgwg@ietf.org
|    6. mailto:stephane.litkowski@orange.com
|    7. mailto:stephane.litkowski@orange.com
|    8. mailto:rtgwg@ietf.org
|    9. mailto:ginsberg@cisco.com
|   10. mailto:rtgwg@ietf.org
|   11. mailto:rtgwg-bounces@ietf.org
|   12. mailto:stephane.litkowski@orange.com
|   13. mailto:rtgwg@ietf.org
|   14. mailto:jeff.tantsura@ericsson.com
|   15. mailto:stephane.litkowski@orange.com
|   16. mailto:stephane.litkowski@orange.com
|   17. mailto:rtgwg@ietf.org
|   18. mailto:rtgwg@ietf.org
|   19. mailto:stephane.litkowski@orange.com
|   20. mailto:stephane.litkowski@orange.com
|   21. mailto:rtgwg@ietf.org
|   22. mailto:rtgwg@ietf.org
|   23. https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#section-5.1
|   24. http://www.orange.com/
|   25. https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20
|   26. https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20
|   27. mailto:stephane.litkowski@orange.com


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


From nobody Tue Feb 24 07:35:20 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 515461A87D2 for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 07:35:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.911
X-Spam-Level: 
X-Spam-Status: No, score=-13.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_84=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 dluZRYI1Y_uV for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 07:35:16 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0B1C1A87D7 for <rtgwg@ietf.org>; Tue, 24 Feb 2015 07:35:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12414; q=dns/txt; s=iport; t=1424792114; x=1426001714; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=6HFMR0DQInzw/FoBfAXWY1jPJX+WRGivMpxbBc6vcdw=; b=fTgPG2fUBD717z1RNO2tomb6ZgWNQ1Db7G9wEN/zEVElKDK4qasoa9xp /DhsysfLz2zJtJg1pn4HtTQfuBig2zKnC+HPhWoEKWHX5nZIuaH2A8FPK rDluBeJ0KpaDS4FN301jsPjMgSM/UYQfdmSO3GHYWc5AqUi/2gPrZnPLL M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BXBQCqaeJU/5NdJa1bgwZSWgTCMgyFbwKBGEMBAQEBAQF8hAwBAQEEAQEBaAMLDgICAQgHCgMBAQEBFRIHGwwLFAkIAgQOBYgZAxENyGMDhUIBAQEBAQEBAQEBAQEBAQEBAQEBAQEXBIsIgU+CMwkRAR0uBQcGBIQgBYoMhSyDV4VggRiDDYsqgz4iggIcgVBvAQGBCTl/AQEB
X-IronPort-AV: E=Sophos;i="5.09,639,1418083200"; d="scan'208";a="398510834"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-8.cisco.com with ESMTP; 24 Feb 2015 15:35:12 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t1OFZCBf011744 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 24 Feb 2015 15:35:12 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.175]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0195.001; Tue, 24 Feb 2015 09:35:12 -0600
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Hannes Gredler <hannes@juniper.net>
Subject: Re: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AdBM3SH2oNl2urLXSA+s5ntM7pKOsP//0WCAgADZjID//DGyQIAIPSwA///UY1CAAJS6gIABrYYA//+1BQA=
Date: Tue, 24 Feb 2015 15:35:11 +0000
Message-ID: <D11202F3.F003%acee@cisco.com>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <5876_1424675401_54EAD249_5876_2527_11_9E32478DFA9976438E7A22F69B08FF9215C157AC@OPEXCLILM34.corporate.adroot.infra.ftgroup> <F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71@xmb-aln-x02.cisco.com> <D110DAB2.EEDA%acee@cisco.com> <20150224150331.GC2688@hannes-mba.local>
In-Reply-To: <20150224150331.GC2688@hannes-mba.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.152.197]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <ABD1111AD19AA74DAE655279F75C9482@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/HzqJz-2Fp0jm4i5S4eUCepgxoac>
Cc: "Les Ginsberg \(ginsberg\)" <ginsberg@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>, Pushpasis Sarkar <psarkar@juniper.net>
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, 24 Feb 2015 15:35:20 -0000

Hannes - I don=B9t see how you can jump to this conclusion - pretty lame ;^=
)
Having the ability to enable or disable fast reroute protection by address
family by no means favors one address family over the other. There just
may be deployments where protection is just not desired for both and it is
not like it comes for free (since you must account for the topologies
being non-congruent).
Acee =20

On 2/24/15, 10:03 AM, "Hannes Gredler" <hannes@juniper.net> wrote:

>HG> that IPv6 is less critical than IPv4 ? -
>    the IESG review will be a lot of fun then - i'll make some popcorn ...
>
>On Mon, Feb 23, 2015 at 06:26:15PM +0000, Acee Lindem (acee) wrote:
>|    I agree with Les.
>|    Acee
>|    From: "Les Ginsberg (ginsberg)" <[1]ginsberg@cisco.com>
>|    Date: Monday, February 23, 2015 at 10:55 AM
>|    To: Stephane Litkowski <[2]stephane.litkowski@orange.com>, Pushpasis
>|    Sarkar <[3]psarkar@juniper.net>, Jeff Tantsura
>|    <[4]jeff.tantsura@ericsson.com>, Routing WG <[5]rtgwg@ietf.org>
>|    Subject: RE: LFA manageability : per AF config =3D> feedback required
>|=20
>|      Stephane =AD
>|=20
>|=20
>|=20
>|      I can imagine cases in which the per AF enabling might make sense
>(e.g.
>|      when the network associated w one address family is deemed
>|      non-critical).
>|=20
>|=20
>|=20
>|      Section 5.1 is a SHOULD =AD as is most of the document. It is
>therefore
>|      a suggestion as to what an implementation should provide. If a
>given
>|      implementer thinks this is either too onerous or not useful they
>can
>|      omit it w/o being in violation. But I see no reason to eliminate
>this
>|      =AD and in actual practice I would expect the cost of supporting
>such a
>|      knob to be low cost. It is hard for me to see this as
>controversial.
>|=20
>|=20
>|=20
>|         Les
>|=20
>|=20
>|=20
>|=20
>|=20
>|      From: [6]stephane.litkowski@orange.com
>|      [[7]mailto:stephane.litkowski@orange.com]
>|      Sent: Sunday, February 22, 2015 11:10 PM
>|      To: Les Ginsberg (ginsberg); Pushpasis Sarkar; Jeff Tantsura;
>|      [8]rtgwg@ietf.org
>|      Subject: RE: LFA manageability : per AF config =3D> feedback requir=
ed
>|=20
>|=20
>|=20
>|      [Les:] I think your point here is that the LFA calculation is AF
>|      independent within a given topology =AD but resources are consumed
>|      independent of how many computations are required- giving an
>operator
>|      the ability to determine which prefixes are most critical seems
>useful.
>|      That could be per AF or per prefix.
>|=20
>|=20
>|=20
>|      [SLI] Agree but is the =B3resource saving=B2 point strong enough to
>|      mandate per AF activation ?
>|=20
>|=20
>|=20
>|      From: Les Ginsberg (ginsberg) [[9]mailto:ginsberg@cisco.com]
>|      Sent: Monday, February 23, 2015 05:01
>|      To: Pushpasis Sarkar; Jeff Tantsura; LITKOWSKI Stephane SCE/IBNF;
>|      [10]rtgwg@ietf.org
>|      Subject: RE: LFA manageability : per AF config =3D> feedback requir=
ed
>|=20
>|=20
>|=20
>|      Pushpassis -
>|=20
>|=20
>|=20
>|      From: rtgwg [[11]mailto:rtgwg-bounces@ietf.org] On Behalf Of
>Pushpasis
>|      Sarkar
>|      Sent: Friday, February 20, 2015 3:28 AM
>|      To: Jeff Tantsura; [12]stephane.litkowski@orange.com;
>[13]rtgwg@ietf.org
>|      Subject: Re: LFA manageability : per AF config =3D> feedback requir=
ed
>|=20
>|=20
>|=20
>|      HI Jeff et al,
>|=20
>|=20
>|=20
>|      I can think of a reason to have a knob per-level(or per-area) or
>per
>|      ISIS topology(note in ISIS a topology in ISIS always corresponds
>to a
>|      single AF,)
>|=20
>|=20
>|=20
>|      [Les:] This is a common mistake to make. If one simply uses RFC
>5308,
>|      then IPv6 prefixes can be advertised in the same topology as IPv4
>(MTID
>|      #0) =AD and there are implementations which support this. More
>|      generally, from the protocol=B9s POV a given topology can support a=
ny
>|      combinations of address families. It is only a convention because
>of the
>|      reserved MTIDs specified in RFC 5120 that certain MTIDs are =B3IPv6
>|      only=B2. But if one looks at the protocol capabilities such a
>|      restriction does not exist in general.
>|=20
>|=20
>|=20
>|      Interestingly you contradicted yourself below. J
>|=20
>|      But I did want to set the record straight on this point =AD
>hopefully we
>|      are in agreement.
>|=20
>|=20
>|=20
>|      and per realm and topology in OSPF. But I cannot think of a reason
>of
>|      why within the same topology we need another set of knobs for each
>AF.
>|      Here, by AF I understand IPV4 or IPv6.
>|=20
>|=20
>|=20
>|      When both IPV4 and IPV6 are part of the same IGP topology, there
>is only
>|      one set of backup computations needed to protect both IPV4 and IPv6
>|      traffic.
>|=20
>|=20
>|=20
>|      Also I cannot think of any motivation for an operator to turn on
>|      protection on only one AF and does not want to turn on for the
>other
>|      even if both AFs has been deployed for normal forwarding.
>|=20
>|=20
>|=20
>|      [Les:] I think your point here is that the LFA calculation is AF
>|      independent within a given topology =AD but resources are consumed
>|      independent of how many computations are required- giving an
>operator
>|      the ability to determine which prefixes are most critical seems
>useful.
>|      That could be per AF or per prefix.
>|=20
>|=20
>|=20
>|         Les
>|=20
>|=20
>|=20
>|      Thanks
>|=20
>|      -Pushpasis
>|=20
>|=20
>|=20
>|      From: Jeff Tantsura <[14]jeff.tantsura@ericsson.com>
>|      Date: Friday, February 20, 2015 at 12:59 PM
>|      To: "[15]stephane.litkowski@orange.com"
>|      <[16]stephane.litkowski@orange.com>, "[17]rtgwg@ietf.org"
>|      <[18]rtgwg@ietf.org>
>|      Subject: Re: LFA manageability : per AF config =3D> feedback requir=
ed
>|=20
>|=20
>|=20
>|      Hi Stephane,
>|=20
>|=20
>|=20
>|      /chair hat off
>|=20
>|=20
>|=20
>|      IMO in disjoined topologies one should have flexibility to
>|      enable/disable LFA as per AF.
>|=20
>|=20
>|=20
>|=20
>|=20
>|      Cheers,
>|=20
>|      Jeff
>|=20
>|=20
>|=20
>|      From: "[19]stephane.litkowski@orange.com"
>|      <[20]stephane.litkowski@orange.com>
>|      Date: Thursday, February 19, 2015 at 11:21 PM
>|      To: "[21]rtgwg@ietf.org" <[22]rtgwg@ietf.org>
>|      Subject: LFA manageability : per AF config =3D> feedback required
>|=20
>|=20
>|=20
>|        Hi Folks,
>|=20
>|=20
>|=20
>|        As you know, LFA manageability draft is in final phasis
>|=20
>|        The current document states per AF granularity activation as a
>SHOULD.
>|=20
>|        =B3
>|=20
>|   [23]5.1.  LFA enabling/disabling scope
>|=20
>|=20
>|=20
>|=20
>|=20
>|     The granularity of LFA activation should be controlled (as alternate
>|=20
>|     nexthop consume memory in forwarding plane).
>|=20
>|=20
>|=20
>|     An implementation of LFA SHOULD allow its activation with the
>|=20
>|     following criteria:
>|=20
>|=20
>|=20
>|     o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4
>unicast,
>|=20
>|        LDP IPv6 unicast ...
>|=20
>|=20
>|=20
>|     o  Per routing context : VRF, virtual/logical router, global routing
>|=20
>|        table, ...
>|=20
>|=20
>|=20
>|        =B3
>|=20
>|=20
>|=20
>|        In the framework of ISIS/OSPF yang modelization, we are
>challenging
>|        this statement, do we really need to force implementation to
>support
>|        this =B3per AF=B2 granularity ?
>|=20
>|=20
>|=20
>|        Please provide as soon as possible your feedback on this and also
>|        provide clear drivers to support or not per AF activation of LFA.
>|=20
>|=20
>|=20
>|=20
>|=20
>|        Thanks for your help !
>|=20
>|=20
>|=20
>|=20
>|=20
>|        [24]Orange logo
>|=20
>|=20
>|=20
>|        Stephane Litkowski
>|        Network Architect
>|        Orange/SCE/EQUANT/IBNF/ENDD/NDE
>|=20
>|        Orange Expert Future Networks
>|=20
>|        phone: [25]+33 2 23 28 49 83
>|        mobile: [26]+33 6 37 86 97 52
>|        [27]stephane.litkowski@orange.com
>|=20
>|=20
>|=20
>|=20
>|=20
>| =20
>__________________________________________________________________________
>_______________________________________________
>|=20
>|=20
>|=20
>|  Ce message et ses pieces jointes peuvent contenir des informations
>confidentielles ou privilegiees et ne doivent donc
>|=20
>|  pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
>recu ce message par erreur, veuillez le signaler
>|=20
>|  a l'expediteur et le detruire ainsi que les pieces jointes. Les
>messages electroniques etant susceptibles d'alteration,
>|=20
>|  Orange decline toute responsabilite si ce message a ete altere,
>deforme ou falsifie. Merci.
>|=20
>|=20
>|=20
>|  This message and its attachments may contain confidential or
>privileged information that may be protected by law;
>|=20
>|  they should not be distributed, used or copied without authorisation.
>|=20
>|  If you have received this email in error, please notify the sender and
>delete this message and its attachments.
>|=20
>|  As emails may be altered, Orange is not liable for messages that have
>been modified, changed or falsified.
>|=20
>|  Thank you.
>|=20
>| =20
>__________________________________________________________________________
>_______________________________________________
>|=20
>|=20
>|=20
>|  Ce message et ses pieces jointes peuvent contenir des informations
>confidentielles ou privilegiees et ne doivent donc
>|=20
>|  pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
>recu ce message par erreur, veuillez le signaler
>|=20
>|  a l'expediteur et le detruire ainsi que les pieces jointes. Les
>messages electroniques etant susceptibles d'alteration,
>|=20
>|  Orange decline toute responsabilite si ce message a ete altere,
>deforme ou falsifie. Merci.
>|=20
>|=20
>|=20
>|  This message and its attachments may contain confidential or
>privileged information that may be protected by law;
>|=20
>|  they should not be distributed, used or copied without authorisation.
>|=20
>|  If you have received this email in error, please notify the sender and
>delete this message and its attachments.
>|=20
>|  As emails may be altered, Orange is not liable for messages that have
>been modified, changed or falsified.
>|=20
>|  Thank you.
>|=20
>| References
>|=20
>|    Visible links
>|    1. mailto:ginsberg@cisco.com
>|    2. mailto:stephane.litkowski@orange.com
>|    3. mailto:psarkar@juniper.net
>|    4. mailto:jeff.tantsura@ericsson.com
>|    5. mailto:rtgwg@ietf.org
>|    6. mailto:stephane.litkowski@orange.com
>|    7. mailto:stephane.litkowski@orange.com
>|    8. mailto:rtgwg@ietf.org
>|    9. mailto:ginsberg@cisco.com
>|   10. mailto:rtgwg@ietf.org
>|   11. mailto:rtgwg-bounces@ietf.org
>|   12. mailto:stephane.litkowski@orange.com
>|   13. mailto:rtgwg@ietf.org
>|   14. mailto:jeff.tantsura@ericsson.com
>|   15. mailto:stephane.litkowski@orange.com
>|   16. mailto:stephane.litkowski@orange.com
>|   17. mailto:rtgwg@ietf.org
>|   18. mailto:rtgwg@ietf.org
>|   19. mailto:stephane.litkowski@orange.com
>|   20. mailto:stephane.litkowski@orange.com
>|   21. mailto:rtgwg@ietf.org
>|   22. mailto:rtgwg@ietf.org
>|   23.=20
>https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#section-
>5.1
>|   24. http://www.orange.com/
>|   25.=20
>https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F%2Fclicvoi=
ce
>.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26root
>service%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20
>|   26.=20
>https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F%2Fclicvoi=
ce
>.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26root
>service%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20
>|   27. mailto:stephane.litkowski@orange.com
>
>
>| _______________________________________________
>| rtgwg mailing list
>| rtgwg@ietf.org
>| https://www.ietf.org/mailman/listinfo/rtgwg
>


From nobody Tue Feb 24 08:00:53 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 249661A1A0F for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 08:00:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.302
X-Spam-Level: 
X-Spam-Status: No, score=-1.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_84=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 FJ_0CIkSm6VC for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 08:00:49 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0778.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::778]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 455981A19FE for <rtgwg@ietf.org>; Tue, 24 Feb 2015 08:00:49 -0800 (PST)
Received: from hannes-mba.local (193.110.55.16) by CO1PR05MB444.namprd05.prod.outlook.com (10.141.73.140) with Microsoft SMTP Server (TLS) id 15.1.93.16; Tue, 24 Feb 2015 16:00:30 +0000
Received: from hannes-mba.local (localhost [IPv6:::1]) by hannes-mba.local (Postfix) with ESMTP id 039B6F541F3; Tue, 24 Feb 2015 17:00:17 +0100 (CET)
Date: Tue, 24 Feb 2015 17:00:17 +0100
From: Hannes Gredler <hannes@juniper.net>
To: "Acee Lindem (acee)" <acee@cisco.com>
Subject: Re: LFA manageability : per AF config => feedback required
Message-ID: <20150224160016.GB3289@hannes-mba.local>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <5876_1424675401_54EAD249_5876_2527_11_9E32478DFA9976438E7A22F69B08FF9215C157AC@OPEXCLILM34.corporate.adroot.infra.ftgroup> <F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71@xmb-aln-x02.cisco.com> <D110DAB2.EEDA%acee@cisco.com> <20150224150331.GC2688@hannes-mba.local> <D11202F3.F003%acee@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <D11202F3.F003%acee@cisco.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Originating-IP: [193.110.55.16]
X-ClientProxiedBy: DB3PR01CA0073.eurprd01.prod.exchangelabs.com (10.242.133.176) To CO1PR05MB444.namprd05.prod.outlook.com (10.141.73.140)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=hannes@juniper.net; 
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB444;
X-Microsoft-Antispam-PRVS: <CO1PR05MB444881F57EB9959E23F8057B8160@CO1PR05MB444.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005004); SRVR:CO1PR05MB444; 
X-Forefront-PRVS: 04976078F0
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(40764003)(24454002)(479174004)(377454003)(199003)(189002)(105586002)(106356001)(110136001)(64706001)(66066001)(40100003)(122386002)(76506005)(46102003)(122856001)(77156002)(47776003)(62966003)(68736005)(77096005)(2950100001)(86362001)(19580405001)(19580395003)(15975445007)(23756003)(54356999)(76176999)(50986999)(5890100001)(50466002)(92566002)(87976001)(101416001)(83506001)(33656002)(98436002)(97736003)(93886004); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB444; H:hannes-mba.local; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB444;
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Feb 2015 16:00:30.8597 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB444
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/uy4vRwVOtxU_iOnL0lYn5w8cBH8>
Cc: "Les Ginsberg \(ginsberg\)" <ginsberg@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>, Pushpasis Sarkar <psarkar@juniper.net>
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, 24 Feb 2015 16:00:52 -0000

On Tue, Feb 24, 2015 at 03:35:11PM +0000, Acee Lindem (acee) wrote:
| Hannes - I don¹t see how you can jump to this conclusion - pretty lame ;^)
| Having the ability to enable or disable fast reroute protection by address
| family by no means favors one address family over the other. There just
| may be deployments where protection is just not desired for both and it is
| not like it comes for free (since you must account for the topologies
| being non-congruent).

my point is that controlling LFA on a per-topology basis makes perfect sense.
(as per your example above (non-congruent topologies), to save some number crunching).

what does not make sense is: consider we've deployed IPv4/IPv6 in the default
topology (integrated IS-IS model) - to turn off LFA for V6 routes.

you have done already the number crunching, so why would you want
to make IPv6 routes a second class citizen here ? - 

can you highlight the use-case here ?

/hannes

| On 2/24/15, 10:03 AM, "Hannes Gredler" <hannes@juniper.net> wrote:
| 
| >HG> that IPv6 is less critical than IPv4 ? -
| >    the IESG review will be a lot of fun then - i'll make some popcorn ...
| >
| >On Mon, Feb 23, 2015 at 06:26:15PM +0000, Acee Lindem (acee) wrote:
| >|    I agree with Les.
| >|    Acee
| >|    From: "Les Ginsberg (ginsberg)" <[1]ginsberg@cisco.com>
| >|    Date: Monday, February 23, 2015 at 10:55 AM
| >|    To: Stephane Litkowski <[2]stephane.litkowski@orange.com>, Pushpasis
| >|    Sarkar <[3]psarkar@juniper.net>, Jeff Tantsura
| >|    <[4]jeff.tantsura@ericsson.com>, Routing WG <[5]rtgwg@ietf.org>
| >|    Subject: RE: LFA manageability : per AF config => feedback required
| >| 
| >|      Stephane ­
| >| 
| >| 
| >| 
| >|      I can imagine cases in which the per AF enabling might make sense
| >(e.g.
| >|      when the network associated w one address family is deemed
| >|      non-critical).
| >| 
| >| 
| >| 
| >|      Section 5.1 is a SHOULD ­ as is most of the document. It is
| >therefore
| >|      a suggestion as to what an implementation should provide. If a
| >given
| >|      implementer thinks this is either too onerous or not useful they
| >can
| >|      omit it w/o being in violation. But I see no reason to eliminate
| >this
| >|      ­ and in actual practice I would expect the cost of supporting
| >such a
| >|      knob to be low cost. It is hard for me to see this as
| >controversial.
| >| 
| >| 
| >| 
| >|         Les
| >| 
| >| 
| >| 
| >| 
| >| 
| >|      From: [6]stephane.litkowski@orange.com
| >|      [[7]mailto:stephane.litkowski@orange.com]
| >|      Sent: Sunday, February 22, 2015 11:10 PM
| >|      To: Les Ginsberg (ginsberg); Pushpasis Sarkar; Jeff Tantsura;
| >|      [8]rtgwg@ietf.org
| >|      Subject: RE: LFA manageability : per AF config => feedback required
| >| 
| >| 
| >| 
| >|      [Les:] I think your point here is that the LFA calculation is AF
| >|      independent within a given topology ­ but resources are consumed
| >|      independent of how many computations are required- giving an
| >operator
| >|      the ability to determine which prefixes are most critical seems
| >useful.
| >|      That could be per AF or per prefix.
| >| 
| >| 
| >| 
| >|      [SLI] Agree but is the ³resource saving² point strong enough to
| >|      mandate per AF activation ?
| >| 
| >| 
| >| 
| >|      From: Les Ginsberg (ginsberg) [[9]mailto:ginsberg@cisco.com]
| >|      Sent: Monday, February 23, 2015 05:01
| >|      To: Pushpasis Sarkar; Jeff Tantsura; LITKOWSKI Stephane SCE/IBNF;
| >|      [10]rtgwg@ietf.org
| >|      Subject: RE: LFA manageability : per AF config => feedback required
| >| 
| >| 
| >| 
| >|      Pushpassis -
| >| 
| >| 
| >| 
| >|      From: rtgwg [[11]mailto:rtgwg-bounces@ietf.org] On Behalf Of
| >Pushpasis
| >|      Sarkar
| >|      Sent: Friday, February 20, 2015 3:28 AM
| >|      To: Jeff Tantsura; [12]stephane.litkowski@orange.com;
| >[13]rtgwg@ietf.org
| >|      Subject: Re: LFA manageability : per AF config => feedback required
| >| 
| >| 
| >| 
| >|      HI Jeff et al,
| >| 
| >| 
| >| 
| >|      I can think of a reason to have a knob per-level(or per-area) or
| >per
| >|      ISIS topology(note in ISIS a topology in ISIS always corresponds
| >to a
| >|      single AF,)
| >| 
| >| 
| >| 
| >|      [Les:] This is a common mistake to make. If one simply uses RFC
| >5308,
| >|      then IPv6 prefixes can be advertised in the same topology as IPv4
| >(MTID
| >|      #0) ­ and there are implementations which support this. More
| >|      generally, from the protocol¹s POV a given topology can support any
| >|      combinations of address families. It is only a convention because
| >of the
| >|      reserved MTIDs specified in RFC 5120 that certain MTIDs are ³IPv6
| >|      only². But if one looks at the protocol capabilities such a
| >|      restriction does not exist in general.
| >| 
| >| 
| >| 
| >|      Interestingly you contradicted yourself below. J
| >| 
| >|      But I did want to set the record straight on this point ­
| >hopefully we
| >|      are in agreement.
| >| 
| >| 
| >| 
| >|      and per realm and topology in OSPF. But I cannot think of a reason
| >of
| >|      why within the same topology we need another set of knobs for each
| >AF.
| >|      Here, by AF I understand IPV4 or IPv6.
| >| 
| >| 
| >| 
| >|      When both IPV4 and IPV6 are part of the same IGP topology, there
| >is only
| >|      one set of backup computations needed to protect both IPV4 and IPv6
| >|      traffic.
| >| 
| >| 
| >| 
| >|      Also I cannot think of any motivation for an operator to turn on
| >|      protection on only one AF and does not want to turn on for the
| >other
| >|      even if both AFs has been deployed for normal forwarding.
| >| 
| >| 
| >| 
| >|      [Les:] I think your point here is that the LFA calculation is AF
| >|      independent within a given topology ­ but resources are consumed
| >|      independent of how many computations are required- giving an
| >operator
| >|      the ability to determine which prefixes are most critical seems
| >useful.
| >|      That could be per AF or per prefix.
| >| 
| >| 
| >| 
| >|         Les
| >| 
| >| 
| >| 
| >|      Thanks
| >| 
| >|      -Pushpasis
| >| 
| >| 
| >| 
| >|      From: Jeff Tantsura <[14]jeff.tantsura@ericsson.com>
| >|      Date: Friday, February 20, 2015 at 12:59 PM
| >|      To: "[15]stephane.litkowski@orange.com"
| >|      <[16]stephane.litkowski@orange.com>, "[17]rtgwg@ietf.org"
| >|      <[18]rtgwg@ietf.org>
| >|      Subject: Re: LFA manageability : per AF config => feedback required
| >| 
| >| 
| >| 
| >|      Hi Stephane,
| >| 
| >| 
| >| 
| >|      /chair hat off
| >| 
| >| 
| >| 
| >|      IMO in disjoined topologies one should have flexibility to
| >|      enable/disable LFA as per AF.
| >| 
| >| 
| >| 
| >| 
| >| 
| >|      Cheers,
| >| 
| >|      Jeff
| >| 
| >| 
| >| 
| >|      From: "[19]stephane.litkowski@orange.com"
| >|      <[20]stephane.litkowski@orange.com>
| >|      Date: Thursday, February 19, 2015 at 11:21 PM
| >|      To: "[21]rtgwg@ietf.org" <[22]rtgwg@ietf.org>
| >|      Subject: LFA manageability : per AF config => feedback required
| >| 
| >| 
| >| 
| >|        Hi Folks,
| >| 
| >| 
| >| 
| >|        As you know, LFA manageability draft is in final phasis
| >| 
| >|        The current document states per AF granularity activation as a
| >SHOULD.
| >| 
| >|        ³
| >| 
| >|   [23]5.1.  LFA enabling/disabling scope
| >| 
| >| 
| >| 
| >| 
| >| 
| >|     The granularity of LFA activation should be controlled (as alternate
| >| 
| >|     nexthop consume memory in forwarding plane).
| >| 
| >| 
| >| 
| >|     An implementation of LFA SHOULD allow its activation with the
| >| 
| >|     following criteria:
| >| 
| >| 
| >| 
| >|     o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4
| >unicast,
| >| 
| >|        LDP IPv6 unicast ...
| >| 
| >| 
| >| 
| >|     o  Per routing context : VRF, virtual/logical router, global routing
| >| 
| >|        table, ...
| >| 
| >| 
| >| 
| >|        ³
| >| 
| >| 
| >| 
| >|        In the framework of ISIS/OSPF yang modelization, we are
| >challenging
| >|        this statement, do we really need to force implementation to
| >support
| >|        this ³per AF² granularity ?
| >| 
| >| 
| >| 
| >|        Please provide as soon as possible your feedback on this and also
| >|        provide clear drivers to support or not per AF activation of LFA.
| >| 
| >| 
| >| 
| >| 
| >| 
| >|        Thanks for your help !
| >| 
| >| 
| >| 
| >| 
| >| 
| >|        [24]Orange logo
| >| 
| >| 
| >| 
| >|        Stephane Litkowski
| >|        Network Architect
| >|        Orange/SCE/EQUANT/IBNF/ENDD/NDE
| >| 
| >|        Orange Expert Future Networks
| >| 
| >|        phone: [25]+33 2 23 28 49 83
| >|        mobile: [26]+33 6 37 86 97 52
| >|        [27]stephane.litkowski@orange.com
| >| 
| >| 
| >| 
| >| 
| >| 
| >|  
| >__________________________________________________________________________
| >_______________________________________________
| >| 
| >| 
| >| 
| >|  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.
| >| 
| >|  
| >__________________________________________________________________________
| >_______________________________________________
| >| 
| >| 
| >| 
| >|  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.
| >| 
| >| References
| >| 
| >|    Visible links
| >|    1. mailto:ginsberg@cisco.com
| >|    2. mailto:stephane.litkowski@orange.com
| >|    3. mailto:psarkar@juniper.net
| >|    4. mailto:jeff.tantsura@ericsson.com
| >|    5. mailto:rtgwg@ietf.org
| >|    6. mailto:stephane.litkowski@orange.com
| >|    7. mailto:stephane.litkowski@orange.com
| >|    8. mailto:rtgwg@ietf.org
| >|    9. mailto:ginsberg@cisco.com
| >|   10. mailto:rtgwg@ietf.org
| >|   11. mailto:rtgwg-bounces@ietf.org
| >|   12. mailto:stephane.litkowski@orange.com
| >|   13. mailto:rtgwg@ietf.org
| >|   14. mailto:jeff.tantsura@ericsson.com
| >|   15. mailto:stephane.litkowski@orange.com
| >|   16. mailto:stephane.litkowski@orange.com
| >|   17. mailto:rtgwg@ietf.org
| >|   18. mailto:rtgwg@ietf.org
| >|   19. mailto:stephane.litkowski@orange.com
| >|   20. mailto:stephane.litkowski@orange.com
| >|   21. mailto:rtgwg@ietf.org
| >|   22. mailto:rtgwg@ietf.org
| >|   23. 
| >https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#section-
| >5.1
| >|   24. http://www.orange.com/
| >|   25. 
| >https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice
| >.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26root
| >service%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20
| >|   26. 
| >https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice
| >.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26root
| >service%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20
| >|   27. mailto:stephane.litkowski@orange.com
| >
| >
| >| _______________________________________________
| >| rtgwg mailing list
| >| rtgwg@ietf.org
| >| https://www.ietf.org/mailman/listinfo/rtgwg
| >
| 


From nobody Tue Feb 24 08:05:10 2015
Return-Path: <ginsberg@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 098071A8745 for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 08:05:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.911
X-Spam-Level: 
X-Spam-Status: No, score=-13.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_84=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 vVRRwQN2nJgD for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 08:05:06 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B0E31A1B4E for <rtgwg@ietf.org>; Tue, 24 Feb 2015 08:05:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16988; q=dns/txt; s=iport; t=1424793906; x=1426003506; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=AvTXAxIJJCrZ4OVeTN3uxPeAr0sNhwygk8qDJY4RwwU=; b=i1szOja51shvsnvEpE0N1EuBOW4OGRxrjgHS737B2jzXNlv7MMdv6vIs Iciqscqx+OSIg6+4vtvVBJ6ceFJ7/GS7gOi748k2K8hORRK1sKbGDwwY2 wc5Jo6+E9xVI+BYWcfSRjXqYZUKBietCsvQx8nz6pL/nF+c+SegOHUiv0 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C8BQDZoOxU/5hdJa1bgwZSWgSDBMAOCoVwAhyBC0MBAQEBAQF8hA8BAQEEAQEBIBE3AwsMAgICAQgHCgMBAQEBAgIGHQMCAgIZDAsUAQgIAgQBDQUIiBMDEQ27eJMzA4U5AQEBAQEBAQEBAQEBAQEBAQEBAQEBFwSBHYlygU+CNAkRAR8WFgUHBoJiL4EUBY9Wg2CHAIMVi0mDPiKCAhyBUG8BAYEJOX8BAQE
X-IronPort-AV: E=Sophos;i="5.09,639,1418083200"; d="scan'208";a="399057585"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-2.cisco.com with ESMTP; 24 Feb 2015 16:05:05 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t1OG541l010676 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 24 Feb 2015 16:05:05 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.138]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0195.001; Tue, 24 Feb 2015 10:05:04 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Hannes Gredler <hannes@juniper.net>, "Acee Lindem (acee)" <acee@cisco.com>
Subject: RE: LFA manageability : per AF config => feedback required
Thread-Topic: LFA manageability : per AF config => feedback required
Thread-Index: AdBM3SH2oNl2urLXSA+s5ntM7pKOsP//0WCAgADZjID//DGyQIAIPSwA///UY1CAAJS6gIABrYYAgABUjIA=
Date: Tue, 24 Feb 2015 16:05:03 +0000
Message-ID: <F3ADE4747C9E124B89F0ED2180CC814F4EF30329@xmb-aln-x02.cisco.com>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <5876_1424675401_54EAD249_5876_2527_11_9E32478DFA9976438E7A22F69B08FF9215C157AC@OPEXCLILM34.corporate.adroot.infra.ftgroup> <F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71@xmb-aln-x02.cisco.com> <D110DAB2.EEDA%acee@cisco.com> <20150224150331.GC2688@hannes-mba.local>
In-Reply-To: <20150224150331.GC2688@hannes-mba.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [128.107.163.86]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/ajL_h9csojHP1piF-p-eXessVOc>
Cc: Pushpasis Sarkar <psarkar@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: Tue, 24 Feb 2015 16:05:09 -0000

SGFubmVzIC0NCg0KSXQgd291bGQgYmUgZ29vZCBpZiB5b3UgZGlkIG5vdCBhdHRyaWJ1dGUgc3Rh
dGVtZW50cyB0byBtZSB0aGF0IEkgZGlkIG5vdCBtYWtlLiBJIG1hZGUgbm8gc3RhdGVtZW50IGFi
b3V0IHRoZSBpbXBvcnRhbmNlIG9mIG9uZSBhZGRyZXNzIGZhbWlseSBvdmVyIGFub3RoZXIuIFBs
ZWFzZSBkbyBub3QgYXR0ZW1wdCB0byBjcmVhdGUgY29udHJvdmVyc3kgYnkgbWlzcmVwcmVzZW50
aW5nIHdoYXQgSSB3cm90ZS4NCg0KSSBkbyBsaWtlIHBvcGNvcm4gdGhvdWdoIC0gc28gaWYgeW91
IHJlYWxseSBhcmUgZ29pbmcgdG8gbWFrZSBzb21lIC0gY291bnQgbWUgaW4uIDotKQ0KDQogICBM
ZXMNCg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEhhbm5lcyBHcmVk
bGVyIFttYWlsdG86aGFubmVzQGp1bmlwZXIubmV0XQ0KPiBTZW50OiBUdWVzZGF5LCBGZWJydWFy
eSAyNCwgMjAxNSA3OjA0IEFNDQo+IFRvOiBBY2VlIExpbmRlbSAoYWNlZSkNCj4gQ2M6IExlcyBH
aW5zYmVyZyAoZ2luc2JlcmcpOyBzdGVwaGFuZS5saXRrb3dza2lAb3JhbmdlLmNvbTsgUHVzaHBh
c2lzDQo+IFNhcmthcjsgSmVmZiBUYW50c3VyYTsgcnRnd2dAaWV0Zi5vcmcNCj4gU3ViamVjdDog
UmU6IExGQSBtYW5hZ2VhYmlsaXR5IDogcGVyIEFGIGNvbmZpZyA9PiBmZWVkYmFjayByZXF1aXJl
ZA0KPiANCj4gSEc+IHRoYXQgSVB2NiBpcyBsZXNzIGNyaXRpY2FsIHRoYW4gSVB2NCA/IC0NCj4g
ICAgIHRoZSBJRVNHIHJldmlldyB3aWxsIGJlIGEgbG90IG9mIGZ1biB0aGVuIC0gaSdsbCBtYWtl
IHNvbWUgcG9wY29ybiAuLi4NCj4gDQo+IE9uIE1vbiwgRmViIDIzLCAyMDE1IGF0IDA2OjI2OjE1
UE0gKzAwMDAsIEFjZWUgTGluZGVtIChhY2VlKSB3cm90ZToNCj4gfCAgICBJIGFncmVlIHdpdGgg
TGVzLg0KPiB8ICAgIEFjZWUNCj4gfCAgICBGcm9tOiAiTGVzIEdpbnNiZXJnIChnaW5zYmVyZyki
IDxbMV1naW5zYmVyZ0BjaXNjby5jb20+DQo+IHwgICAgRGF0ZTogTW9uZGF5LCBGZWJydWFyeSAy
MywgMjAxNSBhdCAxMDo1NSBBTQ0KPiB8ICAgIFRvOiBTdGVwaGFuZSBMaXRrb3dza2kgPFsyXXN0
ZXBoYW5lLmxpdGtvd3NraUBvcmFuZ2UuY29tPiwgUHVzaHBhc2lzDQo+IHwgICAgU2Fya2FyIDxb
M11wc2Fya2FyQGp1bmlwZXIubmV0PiwgSmVmZiBUYW50c3VyYQ0KPiB8ICAgIDxbNF1qZWZmLnRh
bnRzdXJhQGVyaWNzc29uLmNvbT4sIFJvdXRpbmcgV0cgPFs1XXJ0Z3dnQGlldGYub3JnPg0KPiB8
ICAgIFN1YmplY3Q6IFJFOiBMRkEgbWFuYWdlYWJpbGl0eSA6IHBlciBBRiBjb25maWcgPT4gZmVl
ZGJhY2sgcmVxdWlyZWQNCj4gfA0KPiB8ICAgICAgU3RlcGhhbmUg4oCTDQo+IHwNCj4gfA0KPiB8
DQo+IHwgICAgICBJIGNhbiBpbWFnaW5lIGNhc2VzIGluIHdoaWNoIHRoZSBwZXIgQUYgZW5hYmxp
bmcgbWlnaHQgbWFrZSBzZW5zZSAoZS5nLg0KPiB8ICAgICAgd2hlbiB0aGUgbmV0d29yayBhc3Nv
Y2lhdGVkIHcgb25lIGFkZHJlc3MgZmFtaWx5IGlzIGRlZW1lZA0KPiB8ICAgICAgbm9uLWNyaXRp
Y2FsKS4NCj4gfA0KPiB8DQo+IHwNCj4gfCAgICAgIFNlY3Rpb24gNS4xIGlzIGEgU0hPVUxEIOKA
kyBhcyBpcyBtb3N0IG9mIHRoZSBkb2N1bWVudC4gSXQgaXMgdGhlcmVmb3JlDQo+IHwgICAgICBh
IHN1Z2dlc3Rpb24gYXMgdG8gd2hhdCBhbiBpbXBsZW1lbnRhdGlvbiBzaG91bGQgcHJvdmlkZS4g
SWYgYSBnaXZlbg0KPiB8ICAgICAgaW1wbGVtZW50ZXIgdGhpbmtzIHRoaXMgaXMgZWl0aGVyIHRv
byBvbmVyb3VzIG9yIG5vdCB1c2VmdWwgdGhleSBjYW4NCj4gfCAgICAgIG9taXQgaXQgdy9vIGJl
aW5nIGluIHZpb2xhdGlvbi4gQnV0IEkgc2VlIG5vIHJlYXNvbiB0byBlbGltaW5hdGUgdGhpcw0K
PiB8ICAgICAg4oCTIGFuZCBpbiBhY3R1YWwgcHJhY3RpY2UgSSB3b3VsZCBleHBlY3QgdGhlIGNv
c3Qgb2Ygc3VwcG9ydGluZyBzdWNoIGENCj4gfCAgICAgIGtub2IgdG8gYmUgbG93IGNvc3QuIEl0
IGlzIGhhcmQgZm9yIG1lIHRvIHNlZSB0aGlzIGFzIGNvbnRyb3ZlcnNpYWwuDQo+IHwNCj4gfA0K
PiB8DQo+IHwgICAgICAgICBMZXMNCj4gfA0KPiB8DQo+IHwNCj4gfA0KPiB8DQo+IHwgICAgICBG
cm9tOiBbNl1zdGVwaGFuZS5saXRrb3dza2lAb3JhbmdlLmNvbQ0KPiB8ICAgICAgW1s3XW1haWx0
bzpzdGVwaGFuZS5saXRrb3dza2lAb3JhbmdlLmNvbV0NCj4gfCAgICAgIFNlbnQ6IFN1bmRheSwg
RmVicnVhcnkgMjIsIDIwMTUgMTE6MTAgUE0NCj4gfCAgICAgIFRvOiBMZXMgR2luc2JlcmcgKGdp
bnNiZXJnKTsgUHVzaHBhc2lzIFNhcmthcjsgSmVmZiBUYW50c3VyYTsNCj4gfCAgICAgIFs4XXJ0
Z3dnQGlldGYub3JnDQo+IHwgICAgICBTdWJqZWN0OiBSRTogTEZBIG1hbmFnZWFiaWxpdHkgOiBw
ZXIgQUYgY29uZmlnID0+IGZlZWRiYWNrIHJlcXVpcmVkDQo+IHwNCj4gfA0KPiB8DQo+IHwgICAg
ICBbTGVzOl0gSSB0aGluayB5b3VyIHBvaW50IGhlcmUgaXMgdGhhdCB0aGUgTEZBIGNhbGN1bGF0
aW9uIGlzIEFGDQo+IHwgICAgICBpbmRlcGVuZGVudCB3aXRoaW4gYSBnaXZlbiB0b3BvbG9neSDi
gJMgYnV0IHJlc291cmNlcyBhcmUgY29uc3VtZWQNCj4gfCAgICAgIGluZGVwZW5kZW50IG9mIGhv
dyBtYW55IGNvbXB1dGF0aW9ucyBhcmUgcmVxdWlyZWQtIGdpdmluZyBhbg0KPiBvcGVyYXRvcg0K
PiB8ICAgICAgdGhlIGFiaWxpdHkgdG8gZGV0ZXJtaW5lIHdoaWNoIHByZWZpeGVzIGFyZSBtb3N0
IGNyaXRpY2FsIHNlZW1zIHVzZWZ1bC4NCj4gfCAgICAgIFRoYXQgY291bGQgYmUgcGVyIEFGIG9y
IHBlciBwcmVmaXguDQo+IHwNCj4gfA0KPiB8DQo+IHwgICAgICBbU0xJXSBBZ3JlZSBidXQgaXMg
dGhlIOKAnHJlc291cmNlIHNhdmluZ+KAnSBwb2ludCBzdHJvbmcgZW5vdWdoIHRvDQo+IHwgICAg
ICBtYW5kYXRlIHBlciBBRiBhY3RpdmF0aW9uID8NCj4gfA0KPiB8DQo+IHwNCj4gfCAgICAgIEZy
b206IExlcyBHaW5zYmVyZyAoZ2luc2JlcmcpIFtbOV1tYWlsdG86Z2luc2JlcmdAY2lzY28uY29t
XQ0KPiB8ICAgICAgU2VudDogTW9uZGF5LCBGZWJydWFyeSAyMywgMjAxNSAwNTowMQ0KPiB8ICAg
ICAgVG86IFB1c2hwYXNpcyBTYXJrYXI7IEplZmYgVGFudHN1cmE7IExJVEtPV1NLSSBTdGVwaGFu
ZSBTQ0UvSUJORjsNCj4gfCAgICAgIFsxMF1ydGd3Z0BpZXRmLm9yZw0KPiB8ICAgICAgU3ViamVj
dDogUkU6IExGQSBtYW5hZ2VhYmlsaXR5IDogcGVyIEFGIGNvbmZpZyA9PiBmZWVkYmFjayByZXF1
aXJlZA0KPiB8DQo+IHwNCj4gfA0KPiB8ICAgICAgUHVzaHBhc3NpcyAtDQo+IHwNCj4gfA0KPiB8
DQo+IHwgICAgICBGcm9tOiBydGd3ZyBbWzExXW1haWx0bzpydGd3Zy1ib3VuY2VzQGlldGYub3Jn
XSBPbiBCZWhhbGYgT2YNCj4gUHVzaHBhc2lzDQo+IHwgICAgICBTYXJrYXINCj4gfCAgICAgIFNl
bnQ6IEZyaWRheSwgRmVicnVhcnkgMjAsIDIwMTUgMzoyOCBBTQ0KPiB8ICAgICAgVG86IEplZmYg
VGFudHN1cmE7IFsxMl1zdGVwaGFuZS5saXRrb3dza2lAb3JhbmdlLmNvbTsNCj4gWzEzXXJ0Z3dn
QGlldGYub3JnDQo+IHwgICAgICBTdWJqZWN0OiBSZTogTEZBIG1hbmFnZWFiaWxpdHkgOiBwZXIg
QUYgY29uZmlnID0+IGZlZWRiYWNrIHJlcXVpcmVkDQo+IHwNCj4gfA0KPiB8DQo+IHwgICAgICBI
SSBKZWZmIGV0IGFsLA0KPiB8DQo+IHwNCj4gfA0KPiB8ICAgICAgSSBjYW4gdGhpbmsgb2YgYSBy
ZWFzb24gdG8gaGF2ZSBhIGtub2IgcGVyLWxldmVsKG9yIHBlci1hcmVhKSBvciBwZXINCj4gfCAg
ICAgIElTSVMgdG9wb2xvZ3kobm90ZSBpbiBJU0lTIGEgdG9wb2xvZ3kgaW4gSVNJUyBhbHdheXMg
Y29ycmVzcG9uZHMgdG8gYQ0KPiB8ICAgICAgc2luZ2xlIEFGLCkNCj4gfA0KPiB8DQo+IHwNCj4g
fCAgICAgIFtMZXM6XSBUaGlzIGlzIGEgY29tbW9uIG1pc3Rha2UgdG8gbWFrZS4gSWYgb25lIHNp
bXBseSB1c2VzIFJGQyA1MzA4LA0KPiB8ICAgICAgdGhlbiBJUHY2IHByZWZpeGVzIGNhbiBiZSBh
ZHZlcnRpc2VkIGluIHRoZSBzYW1lIHRvcG9sb2d5IGFzIElQdjQgKE1USUQNCj4gfCAgICAgICMw
KSDigJMgYW5kIHRoZXJlIGFyZSBpbXBsZW1lbnRhdGlvbnMgd2hpY2ggc3VwcG9ydCB0aGlzLiBN
b3JlDQo+IHwgICAgICBnZW5lcmFsbHksIGZyb20gdGhlIHByb3RvY29s4oCZcyBQT1YgYSBnaXZl
biB0b3BvbG9neSBjYW4gc3VwcG9ydCBhbnkNCj4gfCAgICAgIGNvbWJpbmF0aW9ucyBvZiBhZGRy
ZXNzIGZhbWlsaWVzLiBJdCBpcyBvbmx5IGEgY29udmVudGlvbiBiZWNhdXNlIG9mIHRoZQ0KPiB8
ICAgICAgcmVzZXJ2ZWQgTVRJRHMgc3BlY2lmaWVkIGluIFJGQyA1MTIwIHRoYXQgY2VydGFpbiBN
VElEcyBhcmUg4oCcSVB2Ng0KPiB8ICAgICAgb25seeKAnS4gQnV0IGlmIG9uZSBsb29rcyBhdCB0
aGUgcHJvdG9jb2wgY2FwYWJpbGl0aWVzIHN1Y2ggYQ0KPiB8ICAgICAgcmVzdHJpY3Rpb24gZG9l
cyBub3QgZXhpc3QgaW4gZ2VuZXJhbC4NCj4gfA0KPiB8DQo+IHwNCj4gfCAgICAgIEludGVyZXN0
aW5nbHkgeW91IGNvbnRyYWRpY3RlZCB5b3Vyc2VsZiBiZWxvdy4gSg0KPiB8DQo+IHwgICAgICBC
dXQgSSBkaWQgd2FudCB0byBzZXQgdGhlIHJlY29yZCBzdHJhaWdodCBvbiB0aGlzIHBvaW50IOKA
kyBob3BlZnVsbHkgd2UNCj4gfCAgICAgIGFyZSBpbiBhZ3JlZW1lbnQuDQo+IHwNCj4gfA0KPiB8
DQo+IHwgICAgICBhbmQgcGVyIHJlYWxtIGFuZCB0b3BvbG9neSBpbiBPU1BGLiBCdXQgSSBjYW5u
b3QgdGhpbmsgb2YgYSByZWFzb24gb2YNCj4gfCAgICAgIHdoeSB3aXRoaW4gdGhlIHNhbWUgdG9w
b2xvZ3kgd2UgbmVlZCBhbm90aGVyIHNldCBvZiBrbm9icyBmb3IgZWFjaA0KPiBBRi4NCj4gfCAg
ICAgIEhlcmUsIGJ5IEFGIEkgdW5kZXJzdGFuZCBJUFY0IG9yIElQdjYuDQo+IHwNCj4gfA0KPiB8
DQo+IHwgICAgICBXaGVuIGJvdGggSVBWNCBhbmQgSVBWNiBhcmUgcGFydCBvZiB0aGUgc2FtZSBJ
R1AgdG9wb2xvZ3ksIHRoZXJlIGlzDQo+IG9ubHkNCj4gfCAgICAgIG9uZSBzZXQgb2YgYmFja3Vw
IGNvbXB1dGF0aW9ucyBuZWVkZWQgdG8gcHJvdGVjdCBib3RoIElQVjQgYW5kIElQdjYNCj4gfCAg
ICAgIHRyYWZmaWMuDQo+IHwNCj4gfA0KPiB8DQo+IHwgICAgICBBbHNvIEkgY2Fubm90IHRoaW5r
IG9mIGFueSBtb3RpdmF0aW9uIGZvciBhbiBvcGVyYXRvciB0byB0dXJuIG9uDQo+IHwgICAgICBw
cm90ZWN0aW9uIG9uIG9ubHkgb25lIEFGIGFuZCBkb2VzIG5vdCB3YW50IHRvIHR1cm4gb24gZm9y
IHRoZSBvdGhlcg0KPiB8ICAgICAgZXZlbiBpZiBib3RoIEFGcyBoYXMgYmVlbiBkZXBsb3llZCBm
b3Igbm9ybWFsIGZvcndhcmRpbmcuDQo+IHwNCj4gfA0KPiB8DQo+IHwgICAgICBbTGVzOl0gSSB0
aGluayB5b3VyIHBvaW50IGhlcmUgaXMgdGhhdCB0aGUgTEZBIGNhbGN1bGF0aW9uIGlzIEFGDQo+
IHwgICAgICBpbmRlcGVuZGVudCB3aXRoaW4gYSBnaXZlbiB0b3BvbG9neSDigJMgYnV0IHJlc291
cmNlcyBhcmUgY29uc3VtZWQNCj4gfCAgICAgIGluZGVwZW5kZW50IG9mIGhvdyBtYW55IGNvbXB1
dGF0aW9ucyBhcmUgcmVxdWlyZWQtIGdpdmluZyBhbg0KPiBvcGVyYXRvcg0KPiB8ICAgICAgdGhl
IGFiaWxpdHkgdG8gZGV0ZXJtaW5lIHdoaWNoIHByZWZpeGVzIGFyZSBtb3N0IGNyaXRpY2FsIHNl
ZW1zIHVzZWZ1bC4NCj4gfCAgICAgIFRoYXQgY291bGQgYmUgcGVyIEFGIG9yIHBlciBwcmVmaXgu
DQo+IHwNCj4gfA0KPiB8DQo+IHwgICAgICAgICBMZXMNCj4gfA0KPiB8DQo+IHwNCj4gfCAgICAg
IFRoYW5rcw0KPiB8DQo+IHwgICAgICAtUHVzaHBhc2lzDQo+IHwNCj4gfA0KPiB8DQo+IHwgICAg
ICBGcm9tOiBKZWZmIFRhbnRzdXJhIDxbMTRdamVmZi50YW50c3VyYUBlcmljc3Nvbi5jb20+DQo+
IHwgICAgICBEYXRlOiBGcmlkYXksIEZlYnJ1YXJ5IDIwLCAyMDE1IGF0IDEyOjU5IFBNDQo+IHwg
ICAgICBUbzogIlsxNV1zdGVwaGFuZS5saXRrb3dza2lAb3JhbmdlLmNvbSINCj4gfCAgICAgIDxb
MTZdc3RlcGhhbmUubGl0a293c2tpQG9yYW5nZS5jb20+LCAiWzE3XXJ0Z3dnQGlldGYub3JnIg0K
PiB8ICAgICAgPFsxOF1ydGd3Z0BpZXRmLm9yZz4NCj4gfCAgICAgIFN1YmplY3Q6IFJlOiBMRkEg
bWFuYWdlYWJpbGl0eSA6IHBlciBBRiBjb25maWcgPT4gZmVlZGJhY2sgcmVxdWlyZWQNCj4gfA0K
PiB8DQo+IHwNCj4gfCAgICAgIEhpIFN0ZXBoYW5lLA0KPiB8DQo+IHwNCj4gfA0KPiB8ICAgICAg
L2NoYWlyIGhhdCBvZmYNCj4gfA0KPiB8DQo+IHwNCj4gfCAgICAgIElNTyBpbiBkaXNqb2luZWQg
dG9wb2xvZ2llcyBvbmUgc2hvdWxkIGhhdmUgZmxleGliaWxpdHkgdG8NCj4gfCAgICAgIGVuYWJs
ZS9kaXNhYmxlIExGQSBhcyBwZXIgQUYuDQo+IHwNCj4gfA0KPiB8DQo+IHwNCj4gfA0KPiB8ICAg
ICAgQ2hlZXJzLA0KPiB8DQo+IHwgICAgICBKZWZmDQo+IHwNCj4gfA0KPiB8DQo+IHwgICAgICBG
cm9tOiAiWzE5XXN0ZXBoYW5lLmxpdGtvd3NraUBvcmFuZ2UuY29tIg0KPiB8ICAgICAgPFsyMF1z
dGVwaGFuZS5saXRrb3dza2lAb3JhbmdlLmNvbT4NCj4gfCAgICAgIERhdGU6IFRodXJzZGF5LCBG
ZWJydWFyeSAxOSwgMjAxNSBhdCAxMToyMSBQTQ0KPiB8ICAgICAgVG86ICJbMjFdcnRnd2dAaWV0
Zi5vcmciIDxbMjJdcnRnd2dAaWV0Zi5vcmc+DQo+IHwgICAgICBTdWJqZWN0OiBMRkEgbWFuYWdl
YWJpbGl0eSA6IHBlciBBRiBjb25maWcgPT4gZmVlZGJhY2sgcmVxdWlyZWQNCj4gfA0KPiB8DQo+
IHwNCj4gfCAgICAgICAgSGkgRm9sa3MsDQo+IHwNCj4gfA0KPiB8DQo+IHwgICAgICAgIEFzIHlv
dSBrbm93LCBMRkEgbWFuYWdlYWJpbGl0eSBkcmFmdCBpcyBpbiBmaW5hbCBwaGFzaXMNCj4gfA0K
PiB8ICAgICAgICBUaGUgY3VycmVudCBkb2N1bWVudCBzdGF0ZXMgcGVyIEFGIGdyYW51bGFyaXR5
IGFjdGl2YXRpb24gYXMgYSBTSE9VTEQuDQo+IHwNCj4gfCAgICAgICAg4oCcDQo+IHwNCj4gfCAg
IFsyM101LjEuICBMRkEgZW5hYmxpbmcvZGlzYWJsaW5nIHNjb3BlDQo+IHwNCj4gfA0KPiB8DQo+
IHwNCj4gfA0KPiB8ICAgICBUaGUgZ3JhbnVsYXJpdHkgb2YgTEZBIGFjdGl2YXRpb24gc2hvdWxk
IGJlIGNvbnRyb2xsZWQgKGFzIGFsdGVybmF0ZQ0KPiB8DQo+IHwgICAgIG5leHRob3AgY29uc3Vt
ZSBtZW1vcnkgaW4gZm9yd2FyZGluZyBwbGFuZSkuDQo+IHwNCj4gfA0KPiB8DQo+IHwgICAgIEFu
IGltcGxlbWVudGF0aW9uIG9mIExGQSBTSE9VTEQgYWxsb3cgaXRzIGFjdGl2YXRpb24gd2l0aCB0
aGUNCj4gfA0KPiB8ICAgICBmb2xsb3dpbmcgY3JpdGVyaWE6DQo+IHwNCj4gfA0KPiB8DQo+IHwg
ICAgIG8gIFBlciBhZGRyZXNzLWZhbWlseSA6IGlwdjQgdW5pY2FzdCwgaXB2NiB1bmljYXN0LCBM
RFAgSVB2NCB1bmljYXN0LA0KPiB8DQo+IHwgICAgICAgIExEUCBJUHY2IHVuaWNhc3QgLi4uDQo+
IHwNCj4gfA0KPiB8DQo+IHwgICAgIG8gIFBlciByb3V0aW5nIGNvbnRleHQgOiBWUkYsIHZpcnR1
YWwvbG9naWNhbCByb3V0ZXIsIGdsb2JhbCByb3V0aW5nDQo+IHwNCj4gfCAgICAgICAgdGFibGUs
IC4uLg0KPiB8DQo+IHwNCj4gfA0KPiB8ICAgICAgICDigJwNCj4gfA0KPiB8DQo+IHwNCj4gfCAg
ICAgICAgSW4gdGhlIGZyYW1ld29yayBvZiBJU0lTL09TUEYgeWFuZyBtb2RlbGl6YXRpb24sIHdl
IGFyZSBjaGFsbGVuZ2luZw0KPiB8ICAgICAgICB0aGlzIHN0YXRlbWVudCwgZG8gd2UgcmVhbGx5
IG5lZWQgdG8gZm9yY2UgaW1wbGVtZW50YXRpb24gdG8gc3VwcG9ydA0KPiB8ICAgICAgICB0aGlz
IOKAnHBlciBBRuKAnSBncmFudWxhcml0eSA/DQo+IHwNCj4gfA0KPiB8DQo+IHwgICAgICAgIFBs
ZWFzZSBwcm92aWRlIGFzIHNvb24gYXMgcG9zc2libGUgeW91ciBmZWVkYmFjayBvbiB0aGlzIGFu
ZCBhbHNvDQo+IHwgICAgICAgIHByb3ZpZGUgY2xlYXIgZHJpdmVycyB0byBzdXBwb3J0IG9yIG5v
dCBwZXIgQUYgYWN0aXZhdGlvbiBvZiBMRkEuDQo+IHwNCj4gfA0KPiB8DQo+IHwNCj4gfA0KPiB8
ICAgICAgICBUaGFua3MgZm9yIHlvdXIgaGVscCAhDQo+IHwNCj4gfA0KPiB8DQo+IHwNCj4gfA0K
PiB8ICAgICAgICBbMjRdT3JhbmdlIGxvZ28NCj4gfA0KPiB8DQo+IHwNCj4gfCAgICAgICAgU3Rl
cGhhbmUgTGl0a293c2tpDQo+IHwgICAgICAgIE5ldHdvcmsgQXJjaGl0ZWN0DQo+IHwgICAgICAg
IE9yYW5nZS9TQ0UvRVFVQU5UL0lCTkYvRU5ERC9OREUNCj4gfA0KPiB8ICAgICAgICBPcmFuZ2Ug
RXhwZXJ0IEZ1dHVyZSBOZXR3b3Jrcw0KPiB8DQo+IHwgICAgICAgIHBob25lOiBbMjVdKzMzIDIg
MjMgMjggNDkgODMNCj4gfCAgICAgICAgbW9iaWxlOiBbMjZdKzMzIDYgMzcgODYgOTcgNTINCj4g
fCAgICAgICAgWzI3XXN0ZXBoYW5lLmxpdGtvd3NraUBvcmFuZ2UuY29tDQo+IHwNCj4gfA0KPiB8
DQo+IHwNCj4gfA0KPiB8DQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBfX19fXw0KPiB8DQo+IHwNCj4gfA0KPiB8ICBD
ZSBtZXNzYWdlIGV0IHNlcyBwaWVjZXMgam9pbnRlcyBwZXV2ZW50IGNvbnRlbmlyIGRlcyBpbmZv
cm1hdGlvbnMNCj4gY29uZmlkZW50aWVsbGVzIG91IHByaXZpbGVnaWVlcyBldCBuZSBkb2l2ZW50
IGRvbmMNCj4gfA0KPiB8ICBwYXMgZXRyZSBkaWZmdXNlcywgZXhwbG9pdGVzIG91IGNvcGllcyBz
YW5zIGF1dG9yaXNhdGlvbi4gU2kgdm91cyBhdmV6IHJlY3UNCj4gY2UgbWVzc2FnZSBwYXIgZXJy
ZXVyLCB2ZXVpbGxleiBsZSBzaWduYWxlcg0KPiB8DQo+IHwgIGEgbCdleHBlZGl0ZXVyIGV0IGxl
IGRldHJ1aXJlIGFpbnNpIHF1ZSBsZXMgcGllY2VzIGpvaW50ZXMuIExlcyBtZXNzYWdlcw0KPiBl
bGVjdHJvbmlxdWVzIGV0YW50IHN1c2NlcHRpYmxlcyBkJ2FsdGVyYXRpb24sDQo+IHwNCj4gfCAg
T3JhbmdlIGRlY2xpbmUgdG91dGUgcmVzcG9uc2FiaWxpdGUgc2kgY2UgbWVzc2FnZSBhIGV0ZSBh
bHRlcmUsIGRlZm9ybWUgb3UNCj4gZmFsc2lmaWUuIE1lcmNpLg0KPiB8DQo+IHwNCj4gfA0KPiB8
ICBUaGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBjb25maWRlbnRp
YWwgb3IgcHJpdmlsZWdlZA0KPiBpbmZvcm1hdGlvbiB0aGF0IG1heSBiZSBwcm90ZWN0ZWQgYnkg
bGF3Ow0KPiB8DQo+IHwgIHRoZXkgc2hvdWxkIG5vdCBiZSBkaXN0cmlidXRlZCwgdXNlZCBvciBj
b3BpZWQgd2l0aG91dCBhdXRob3Jpc2F0aW9uLg0KPiB8DQo+IHwgIElmIHlvdSBoYXZlIHJlY2Vp
dmVkIHRoaXMgZW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBhbmQNCj4g
ZGVsZXRlIHRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRzLg0KPiB8DQo+IHwgIEFzIGVt
YWlscyBtYXkgYmUgYWx0ZXJlZCwgT3JhbmdlIGlzIG5vdCBsaWFibGUgZm9yIG1lc3NhZ2VzIHRo
YXQgaGF2ZSBiZWVuDQo+IG1vZGlmaWVkLCBjaGFuZ2VkIG9yIGZhbHNpZmllZC4NCj4gfA0KPiB8
ICBUaGFuayB5b3UuDQo+IHwNCj4gfA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gX19fX18NCj4gfA0KPiB8DQo+IHwN
Cj4gfCAgQ2UgbWVzc2FnZSBldCBzZXMgcGllY2VzIGpvaW50ZXMgcGV1dmVudCBjb250ZW5pciBk
ZXMgaW5mb3JtYXRpb25zDQo+IGNvbmZpZGVudGllbGxlcyBvdSBwcml2aWxlZ2llZXMgZXQgbmUg
ZG9pdmVudCBkb25jDQo+IHwNCj4gfCAgcGFzIGV0cmUgZGlmZnVzZXMsIGV4cGxvaXRlcyBvdSBj
b3BpZXMgc2FucyBhdXRvcmlzYXRpb24uIFNpIHZvdXMgYXZleiByZWN1DQo+IGNlIG1lc3NhZ2Ug
cGFyIGVycmV1ciwgdmV1aWxsZXogbGUgc2lnbmFsZXINCj4gfA0KPiB8ICBhIGwnZXhwZWRpdGV1
ciBldCBsZSBkZXRydWlyZSBhaW5zaSBxdWUgbGVzIHBpZWNlcyBqb2ludGVzLiBMZXMgbWVzc2Fn
ZXMNCj4gZWxlY3Ryb25pcXVlcyBldGFudCBzdXNjZXB0aWJsZXMgZCdhbHRlcmF0aW9uLA0KPiB8
DQo+IHwgIE9yYW5nZSBkZWNsaW5lIHRvdXRlIHJlc3BvbnNhYmlsaXRlIHNpIGNlIG1lc3NhZ2Ug
YSBldGUgYWx0ZXJlLCBkZWZvcm1lIG91DQo+IGZhbHNpZmllLiBNZXJjaS4NCj4gfA0KPiB8DQo+
IHwNCj4gfCAgVGhpcyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVudHMgbWF5IGNvbnRhaW4gY29u
ZmlkZW50aWFsIG9yIHByaXZpbGVnZWQNCj4gaW5mb3JtYXRpb24gdGhhdCBtYXkgYmUgcHJvdGVj
dGVkIGJ5IGxhdzsNCj4gfA0KPiB8ICB0aGV5IHNob3VsZCBub3QgYmUgZGlzdHJpYnV0ZWQsIHVz
ZWQgb3IgY29waWVkIHdpdGhvdXQgYXV0aG9yaXNhdGlvbi4NCj4gfA0KPiB8ICBJZiB5b3UgaGF2
ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIg
YW5kDQo+IGRlbGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cy4NCj4gfA0KPiB8
ICBBcyBlbWFpbHMgbWF5IGJlIGFsdGVyZWQsIE9yYW5nZSBpcyBub3QgbGlhYmxlIGZvciBtZXNz
YWdlcyB0aGF0IGhhdmUgYmVlbg0KPiBtb2RpZmllZCwgY2hhbmdlZCBvciBmYWxzaWZpZWQuDQo+
IHwNCj4gfCAgVGhhbmsgeW91Lg0KPiB8DQo+IHwgUmVmZXJlbmNlcw0KPiB8DQo+IHwgICAgVmlz
aWJsZSBsaW5rcw0KPiB8ICAgIDEuIG1haWx0bzpnaW5zYmVyZ0BjaXNjby5jb20NCj4gfCAgICAy
LiBtYWlsdG86c3RlcGhhbmUubGl0a293c2tpQG9yYW5nZS5jb20NCj4gfCAgICAzLiBtYWlsdG86
cHNhcmthckBqdW5pcGVyLm5ldA0KPiB8ICAgIDQuIG1haWx0bzpqZWZmLnRhbnRzdXJhQGVyaWNz
c29uLmNvbQ0KPiB8ICAgIDUuIG1haWx0bzpydGd3Z0BpZXRmLm9yZw0KPiB8ICAgIDYuIG1haWx0
bzpzdGVwaGFuZS5saXRrb3dza2lAb3JhbmdlLmNvbQ0KPiB8ICAgIDcuIG1haWx0bzpzdGVwaGFu
ZS5saXRrb3dza2lAb3JhbmdlLmNvbQ0KPiB8ICAgIDguIG1haWx0bzpydGd3Z0BpZXRmLm9yZw0K
PiB8ICAgIDkuIG1haWx0bzpnaW5zYmVyZ0BjaXNjby5jb20NCj4gfCAgIDEwLiBtYWlsdG86cnRn
d2dAaWV0Zi5vcmcNCj4gfCAgIDExLiBtYWlsdG86cnRnd2ctYm91bmNlc0BpZXRmLm9yZw0KPiB8
ICAgMTIuIG1haWx0bzpzdGVwaGFuZS5saXRrb3dza2lAb3JhbmdlLmNvbQ0KPiB8ICAgMTMuIG1h
aWx0bzpydGd3Z0BpZXRmLm9yZw0KPiB8ICAgMTQuIG1haWx0bzpqZWZmLnRhbnRzdXJhQGVyaWNz
c29uLmNvbQ0KPiB8ICAgMTUuIG1haWx0bzpzdGVwaGFuZS5saXRrb3dza2lAb3JhbmdlLmNvbQ0K
PiB8ICAgMTYuIG1haWx0bzpzdGVwaGFuZS5saXRrb3dza2lAb3JhbmdlLmNvbQ0KPiB8ICAgMTcu
IG1haWx0bzpydGd3Z0BpZXRmLm9yZw0KPiB8ICAgMTguIG1haWx0bzpydGd3Z0BpZXRmLm9yZw0K
PiB8ICAgMTkuIG1haWx0bzpzdGVwaGFuZS5saXRrb3dza2lAb3JhbmdlLmNvbQ0KPiB8ICAgMjAu
IG1haWx0bzpzdGVwaGFuZS5saXRrb3dza2lAb3JhbmdlLmNvbQ0KPiB8ICAgMjEuIG1haWx0bzpy
dGd3Z0BpZXRmLm9yZw0KPiB8ICAgMjIuIG1haWx0bzpydGd3Z0BpZXRmLm9yZw0KPiB8ICAgMjMu
IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXJ0Z3dnLWxmYS1tYW5hZ2Vh
YmlsaXR5LQ0KPiAwNyNzZWN0aW9uLTUuMQ0KPiB8ICAgMjQuIGh0dHA6Ly93d3cub3JhbmdlLmNv
bS8NCj4gfCAgIDI1Lg0KPiBodHRwczovL21vbnNpLnNzby5mcmFuY2V0ZWxlY29tLmZyL2luZGV4
LmFzcD90YXJnZXQ9aHR0cCUzQSUyRiUyRmNsaWN2bw0KPiBpY2Uuc3NvLmZyYW5jZXRlbGVjb20u
ZnIlMkZDbGljdm9pY2VWMiUyRlRvb2xCYXIuZG8lM0ZhY3Rpb24lM0RkZWZhdWx0DQo+ICUyNnJv
b3RzZXJ2aWNlJTNEU0lHTkFUVVJFJTI2dG8lM0QrMzMlMjAyJTIwMjMlMjAyOCUyMDQ5JTIwODMN
Cj4gJTIwDQo+IHwgICAyNi4NCj4gaHR0cHM6Ly9tb25zaS5zc28uZnJhbmNldGVsZWNvbS5mci9p
bmRleC5hc3A/dGFyZ2V0PWh0dHAlM0ElMkYlMkZjbGljdm8NCj4gaWNlLnNzby5mcmFuY2V0ZWxl
Y29tLmZyJTJGQ2xpY3ZvaWNlVjIlMkZUb29sQmFyLmRvJTNGYWN0aW9uJTNEZGVmYXVsdA0KPiAl
MjZyb290c2VydmljZSUzRFNJR05BVFVSRSUyNnRvJTNEKzMzJTIwNiUyMDM3JTIwODYlMjA5NyUy
MDUyDQo+ICUyMA0KPiB8ICAgMjcuIG1haWx0bzpzdGVwaGFuZS5saXRrb3dza2lAb3JhbmdlLmNv
bQ0KPiANCj4gDQo+IHwgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCj4gfCBydGd3ZyBtYWlsaW5nIGxpc3QNCj4gfCBydGd3Z0BpZXRmLm9yZw0KPiB8IGh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcnRnd2cNCg0K


From nobody Tue Feb 24 08:13:57 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 3A0A41A1A07 for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 08:13:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.302
X-Spam-Level: 
X-Spam-Status: No, score=-1.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_84=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 LOJV4Jpl8rpn for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 08:13:53 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0754.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::754]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 494621A1A48 for <rtgwg@ietf.org>; Tue, 24 Feb 2015 08:13:52 -0800 (PST)
Received: from BN1PR05MB438.namprd05.prod.outlook.com (10.141.58.12) by BN1PR05MB454.namprd05.prod.outlook.com (10.141.59.17) with Microsoft SMTP Server (TLS) id 15.1.93.16; Tue, 24 Feb 2015 16:13:29 +0000
Received: from hannes-mba.local (193.110.55.11) by BN1PR05MB438.namprd05.prod.outlook.com (10.141.58.12) with Microsoft SMTP Server (TLS) id 15.1.93.16; Tue, 24 Feb 2015 16:13:27 +0000
Received: from hannes-mba.local (localhost [IPv6:::1]) by hannes-mba.local (Postfix) with ESMTP id 1A85CF543F8; Tue, 24 Feb 2015 17:13:15 +0100 (CET)
Date: Tue, 24 Feb 2015 17:13:15 +0100
From: Hannes Gredler <hannes@juniper.net>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
Subject: Re: LFA manageability : per AF config => feedback required
Message-ID: <20150224161315.GD3289@hannes-mba.local>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <5876_1424675401_54EAD249_5876_2527_11_9E32478DFA9976438E7A22F69B08FF9215C157AC@OPEXCLILM34.corporate.adroot.infra.ftgroup> <F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71@xmb-aln-x02.cisco.com> <D110DAB2.EEDA%acee@cisco.com> <20150224150331.GC2688@hannes-mba.local> <F3ADE4747C9E124B89F0ED2180CC814F4EF30329@xmb-aln-x02.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <F3ADE4747C9E124B89F0ED2180CC814F4EF30329@xmb-aln-x02.cisco.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Originating-IP: [193.110.55.11]
X-ClientProxiedBy: DB4PR06CA0043.eurprd06.prod.outlook.com (25.160.40.171) To BN1PR05MB438.namprd05.prod.outlook.com (10.141.58.12)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=hannes@juniper.net; 
X-Microsoft-Antispam: UriScan:;UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB438;
X-Microsoft-Antispam-PRVS: <BN1PR05MB4384E9A7180BD9D9E855778B8160@BN1PR05MB438.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005004); SRVR:BN1PR05MB438; 
X-Forefront-PRVS: 04976078F0
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(40764003)(199003)(189002)(24454002)(13464003)(377454003)(98436002)(33656002)(92566002)(54356999)(76176999)(83506001)(77156002)(62966003)(19580395003)(105586002)(66066001)(47776003)(110136001)(15975445007)(77096005)(19580405001)(68736005)(2950100001)(40100003)(50986999)(23676002)(86362001)(93886004)(122856001)(101416001)(122386002)(87976001)(64706001)(5890100001)(76506005)(46102003)(106356001)(97736003)(50466002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR05MB438; H:hannes-mba.local; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB438;
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Feb 2015 16:13:27.6826 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN1PR05MB438
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB454;
X-OriginatorOrg: juniper.net
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/CuWPCubIjoYlpKoWqfXRs7ZRgvE>
Cc: Pushpasis Sarkar <psarkar@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: Tue, 24 Feb 2015 16:13:56 -0000

les,

there is explicit statement and implicit statements.

it is correct that you have not made an explicit statement that
IPv6 is less important than IPv4 and yet there is
your last quote which implicitly makes me think so.

|      I can imagine cases in which the per AF enabling might make sense (e.g.
|      when the network associated w one address family is deemed
|      non-critical).

so can you clarify this use-case where a SP wants to have IPv4 protected
and not IPv6 in the default topology.

why would this make sense / why would a knob for this make sense ?

/hannes

On Tue, Feb 24, 2015 at 04:05:03PM +0000, Les Ginsberg (ginsberg) wrote:
| Hannes -
| 
| It would be good if you did not attribute statements to me that I did not make. I made no statement about the importance of one address family over another. Please do not attempt to create controversy by misrepresenting what I wrote.
| 
| I do like popcorn though - so if you really are going to make some - count me in. :-)
| 
|    Les
| 
| 
| > -----Original Message-----
| > From: Hannes Gredler [mailto:hannes@juniper.net]
| > Sent: Tuesday, February 24, 2015 7:04 AM
| > To: Acee Lindem (acee)
| > Cc: Les Ginsberg (ginsberg); stephane.litkowski@orange.com; Pushpasis
| > Sarkar; Jeff Tantsura; rtgwg@ietf.org
| > Subject: Re: LFA manageability : per AF config => feedback required
| > 
| > HG> that IPv6 is less critical than IPv4 ? -
| >     the IESG review will be a lot of fun then - i'll make some popcorn ...
| > 
| > On Mon, Feb 23, 2015 at 06:26:15PM +0000, Acee Lindem (acee) wrote:
| > |    I agree with Les.
| > |    Acee
| > |    From: "Les Ginsberg (ginsberg)" <[1]ginsberg@cisco.com>
| > |    Date: Monday, February 23, 2015 at 10:55 AM
| > |    To: Stephane Litkowski <[2]stephane.litkowski@orange.com>, Pushpasis
| > |    Sarkar <[3]psarkar@juniper.net>, Jeff Tantsura
| > |    <[4]jeff.tantsura@ericsson.com>, Routing WG <[5]rtgwg@ietf.org>
| > |    Subject: RE: LFA manageability : per AF config => feedback required
| > |
| > |      Stephane â€“
| > |
| > |
| > |
| > |      I can imagine cases in which the per AF enabling might make sense (e.g.
| > |      when the network associated w one address family is deemed
| > |      non-critical).
| > |
| > |
| > |
| > |      Section 5.1 is a SHOULD â€“ as is most of the document. It is therefore
| > |      a suggestion as to what an implementation should provide. If a given
| > |      implementer thinks this is either too onerous or not useful they can
| > |      omit it w/o being in violation. But I see no reason to eliminate this
| > |      â€“ and in actual practice I would expect the cost of supporting such a
| > |      knob to be low cost. It is hard for me to see this as controversial.
| > |
| > |
| > |
| > |         Les
| > |
| > |
| > |
| > |
| > |
| > |      From: [6]stephane.litkowski@orange.com
| > |      [[7]mailto:stephane.litkowski@orange.com]
| > |      Sent: Sunday, February 22, 2015 11:10 PM
| > |      To: Les Ginsberg (ginsberg); Pushpasis Sarkar; Jeff Tantsura;
| > |      [8]rtgwg@ietf.org
| > |      Subject: RE: LFA manageability : per AF config => feedback required
| > |
| > |
| > |
| > |      [Les:] I think your point here is that the LFA calculation is AF
| > |      independent within a given topology â€“ but resources are consumed
| > |      independent of how many computations are required- giving an
| > operator
| > |      the ability to determine which prefixes are most critical seems useful.
| > |      That could be per AF or per prefix.
| > |
| > |
| > |
| > |      [SLI] Agree but is the â€œresource savingâ€� point strong enough to
| > |      mandate per AF activation ?
| > |
| > |
| > |
| > |      From: Les Ginsberg (ginsberg) [[9]mailto:ginsberg@cisco.com]
| > |      Sent: Monday, February 23, 2015 05:01
| > |      To: Pushpasis Sarkar; Jeff Tantsura; LITKOWSKI Stephane SCE/IBNF;
| > |      [10]rtgwg@ietf.org
| > |      Subject: RE: LFA manageability : per AF config => feedback required
| > |
| > |
| > |
| > |      Pushpassis -
| > |
| > |
| > |
| > |      From: rtgwg [[11]mailto:rtgwg-bounces@ietf.org] On Behalf Of
| > Pushpasis
| > |      Sarkar
| > |      Sent: Friday, February 20, 2015 3:28 AM
| > |      To: Jeff Tantsura; [12]stephane.litkowski@orange.com;
| > [13]rtgwg@ietf.org
| > |      Subject: Re: LFA manageability : per AF config => feedback required
| > |
| > |
| > |
| > |      HI Jeff et al,
| > |
| > |
| > |
| > |      I can think of a reason to have a knob per-level(or per-area) or per
| > |      ISIS topology(note in ISIS a topology in ISIS always corresponds to a
| > |      single AF,)
| > |
| > |
| > |
| > |      [Les:] This is a common mistake to make. If one simply uses RFC 5308,
| > |      then IPv6 prefixes can be advertised in the same topology as IPv4 (MTID
| > |      #0) â€“ and there are implementations which support this. More
| > |      generally, from the protocolâ€™s POV a given topology can support any
| > |      combinations of address families. It is only a convention because of the
| > |      reserved MTIDs specified in RFC 5120 that certain MTIDs are â€œIPv6
| > |      onlyâ€�. But if one looks at the protocol capabilities such a
| > |      restriction does not exist in general.
| > |
| > |
| > |
| > |      Interestingly you contradicted yourself below. J
| > |
| > |      But I did want to set the record straight on this point â€“ hopefully we
| > |      are in agreement.
| > |
| > |
| > |
| > |      and per realm and topology in OSPF. But I cannot think of a reason of
| > |      why within the same topology we need another set of knobs for each
| > AF.
| > |      Here, by AF I understand IPV4 or IPv6.
| > |
| > |
| > |
| > |      When both IPV4 and IPV6 are part of the same IGP topology, there is
| > only
| > |      one set of backup computations needed to protect both IPV4 and IPv6
| > |      traffic.
| > |
| > |
| > |
| > |      Also I cannot think of any motivation for an operator to turn on
| > |      protection on only one AF and does not want to turn on for the other
| > |      even if both AFs has been deployed for normal forwarding.
| > |
| > |
| > |
| > |      [Les:] I think your point here is that the LFA calculation is AF
| > |      independent within a given topology â€“ but resources are consumed
| > |      independent of how many computations are required- giving an
| > operator
| > |      the ability to determine which prefixes are most critical seems useful.
| > |      That could be per AF or per prefix.
| > |
| > |
| > |
| > |         Les
| > |
| > |
| > |
| > |      Thanks
| > |
| > |      -Pushpasis
| > |
| > |
| > |
| > |      From: Jeff Tantsura <[14]jeff.tantsura@ericsson.com>
| > |      Date: Friday, February 20, 2015 at 12:59 PM
| > |      To: "[15]stephane.litkowski@orange.com"
| > |      <[16]stephane.litkowski@orange.com>, "[17]rtgwg@ietf.org"
| > |      <[18]rtgwg@ietf.org>
| > |      Subject: Re: LFA manageability : per AF config => feedback required
| > |
| > |
| > |
| > |      Hi Stephane,
| > |
| > |
| > |
| > |      /chair hat off
| > |
| > |
| > |
| > |      IMO in disjoined topologies one should have flexibility to
| > |      enable/disable LFA as per AF.
| > |
| > |
| > |
| > |
| > |
| > |      Cheers,
| > |
| > |      Jeff
| > |
| > |
| > |
| > |      From: "[19]stephane.litkowski@orange.com"
| > |      <[20]stephane.litkowski@orange.com>
| > |      Date: Thursday, February 19, 2015 at 11:21 PM
| > |      To: "[21]rtgwg@ietf.org" <[22]rtgwg@ietf.org>
| > |      Subject: LFA manageability : per AF config => feedback required
| > |
| > |
| > |
| > |        Hi Folks,
| > |
| > |
| > |
| > |        As you know, LFA manageability draft is in final phasis
| > |
| > |        The current document states per AF granularity activation as a SHOULD.
| > |
| > |        â€œ
| > |
| > |   [23]5.1.  LFA enabling/disabling scope
| > |
| > |
| > |
| > |
| > |
| > |     The granularity of LFA activation should be controlled (as alternate
| > |
| > |     nexthop consume memory in forwarding plane).
| > |
| > |
| > |
| > |     An implementation of LFA SHOULD allow its activation with the
| > |
| > |     following criteria:
| > |
| > |
| > |
| > |     o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,
| > |
| > |        LDP IPv6 unicast ...
| > |
| > |
| > |
| > |     o  Per routing context : VRF, virtual/logical router, global routing
| > |
| > |        table, ...
| > |
| > |
| > |
| > |        â€œ
| > |
| > |
| > |
| > |        In the framework of ISIS/OSPF yang modelization, we are challenging
| > |        this statement, do we really need to force implementation to support
| > |        this â€œper AFâ€� granularity ?
| > |
| > |
| > |
| > |        Please provide as soon as possible your feedback on this and also
| > |        provide clear drivers to support or not per AF activation of LFA.
| > |
| > |
| > |
| > |
| > |
| > |        Thanks for your help !
| > |
| > |
| > |
| > |
| > |
| > |        [24]Orange logo
| > |
| > |
| > |
| > |        Stephane Litkowski
| > |        Network Architect
| > |        Orange/SCE/EQUANT/IBNF/ENDD/NDE
| > |
| > |        Orange Expert Future Networks
| > |
| > |        phone: [25]+33 2 23 28 49 83
| > |        mobile: [26]+33 6 37 86 97 52
| > |        [27]stephane.litkowski@orange.com
| > |
| > |
| > |
| > |
| > |
| > |
| > __________________________________________________________
| > __________________________________________________________
| > _____
| > |
| > |
| > |
| > |  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.
| > |
| > |
| > __________________________________________________________
| > __________________________________________________________
| > _____
| > |
| > |
| > |
| > |  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.
| > |
| > | References
| > |
| > |    Visible links
| > |    1. mailto:ginsberg@cisco.com
| > |    2. mailto:stephane.litkowski@orange.com
| > |    3. mailto:psarkar@juniper.net
| > |    4. mailto:jeff.tantsura@ericsson.com
| > |    5. mailto:rtgwg@ietf.org
| > |    6. mailto:stephane.litkowski@orange.com
| > |    7. mailto:stephane.litkowski@orange.com
| > |    8. mailto:rtgwg@ietf.org
| > |    9. mailto:ginsberg@cisco.com
| > |   10. mailto:rtgwg@ietf.org
| > |   11. mailto:rtgwg-bounces@ietf.org
| > |   12. mailto:stephane.litkowski@orange.com
| > |   13. mailto:rtgwg@ietf.org
| > |   14. mailto:jeff.tantsura@ericsson.com
| > |   15. mailto:stephane.litkowski@orange.com
| > |   16. mailto:stephane.litkowski@orange.com
| > |   17. mailto:rtgwg@ietf.org
| > |   18. mailto:rtgwg@ietf.org
| > |   19. mailto:stephane.litkowski@orange.com
| > |   20. mailto:stephane.litkowski@orange.com
| > |   21. mailto:rtgwg@ietf.org
| > |   22. mailto:rtgwg@ietf.org
| > |   23. https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-
| > 07#section-5.1
| > |   24. http://www.orange.com/
| > |   25.
| > https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvo
| > ice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault
| > %26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083
| > %20
| > |   26.
| > https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvo
| > ice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault
| > %26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052
| > %20
| > |   27. mailto:stephane.litkowski@orange.com
| > 
| > 
| > | _______________________________________________
| > | rtgwg mailing list
| > | rtgwg@ietf.org
| > | https://www.ietf.org/mailman/listinfo/rtgwg
| 


From nobody Tue Feb 24 08:54:51 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 8B7981A1B81 for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 08:54:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.088
X-Spam-Level: **
X-Spam-Status: No, score=2.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, J_CHICKENPOX_84=0.6, MANGLED_BELOW=2.3, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] 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 qO7z-M5z6njm for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 08:54:46 -0800 (PST)
Received: from owl.lab.dtag.de (Owl.lab.DTAG.DE [194.25.1.236]) by ietfa.amsl.com (Postfix) with ESMTP id 112941A1B07 for <rtgwg@ietf.org>; Tue, 24 Feb 2015 08:54:46 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by owl.lab.dtag.de (Postfix) with ESMTP id 8B778598060; Tue, 24 Feb 2015 17:54:44 +0100 (CET)
Received: from TSUNAMI-neu.95.lab.DTAG.de (o.Hippogryff.lab.dtag.de [194.25.10.166]) by owl.lab.dtag.de (Postfix) with ESMTPSA id 5FFC5597D4A; Tue, 24 Feb 2015 17:54:44 +0100 (CET)
Message-ID: <54ECACD4.2070409@nic.dtag.de>
Date: Tue, 24 Feb 2015 17:54:44 +0100
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.4.0
MIME-Version: 1.0
To: rtgwg@ietf.org
Subject: Re: LFA manageability : per AF config => feedback required
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <5876_1424675401_54EAD249_5876_2527_11_9E32478DFA9976438E7A22F69B08FF9215C157AC@OPEXCLILM34.corporate.adroot.infra.ftgroup> <F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71@xmb-aln-x02.cisco.com> <20150224150228.GB2688@hannes-mba.local>
In-Reply-To: <20150224150228.GB2688@hannes-mba.local>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/jR7xTj2uPgg37VaMKMg8186XIKg>
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, 24 Feb 2015 16:54:49 -0000

Hello everyone,

I really do see a good use-case for turning on IP-FRR protection for 
just one address family, and it does not have anything to do with making 
IPv6 customer better or worse than IPv4 customer traffic.

Consider the IP/MPLS network I have today. Several address families are 
active in the backbone, but all customer traffic is carried in MPLS 
packets guided by IPv4-signalled LDP. This holds for ANY customer 
traffic, whether it is public IPv4, public IPv6, VPNs in IPv4 or IPv6 or 
L2-VPNs. Unlabeled IPv4 traffic also exists in the same backbone, but 
only for routing protocols themselves, and/or network management. Thus 
there is no need to protect this unlabeled IPv4 traffic in the same way 
as the customer MPLS traffic.

In the future, I might activate IPv6 in the backbone and introduce more 
and more routing and management protocols with IPv6. Still no need to 
protect IPv6. Eventually I might shift LDP (or SR) from IPv4 controlled 
to IPv6 controlled. What was IPv6-over-IPv4-controlled-MPLS becomes 
plain IPv6-labeled traffic then, and IPv4-labeled traffic will become 
IPv4-over-IPv6-controlled-MPLS. At THAT point in time it becomes 
important to protect the IPv6 controlled MPLS traffic, and thus the IPv6 
address family in the IGP, but no earlier.

So please do not mix up control traffic and customer traffic, internal 
routing and customer routes. Thank you.

Best regards, Martin


Am 24.02.15 um 16:02 schrieb Hannes Gredler:
> On Mon, Feb 23, 2015 at 03:55:32PM +0000, Les Ginsberg (ginsberg) wrote:
> |    I can imagine cases in which the per AF enabling might make sense (e.g.
> |    when the network associated w one address family is deemed non-critical).
>
>
> HG> as it is unlikely that operators will tun off IPv4 protection,
>      may i have a ask that you repeat that quote above in the 6man
>      meeting ;-) ? - effectifely you're saying "IPv6 may be considered
>      as less critical", and therefore we SHOULD provide a knob
>      to turn protection off.
>
> |
> |
> |    Section 5.1 is a SHOULD - as is most of the document. It is therefore a
> |    suggestion as to what an implementation should provide. If a given
> |    implementer thinks this is either too onerous or not useful they can omit
> |    it w/o being in violation. But I see no reason to eliminate this - and in
> |    actual practice I would expect the cost of supporting such a knob to be
> |    low cost. It is hard for me to see this as controversial.
> |
> |
> |
> |       Les
> |
> |
> |
> |
> |
> |    From: stephane.litkowski@orange.com [mailto:stephane.litkowski@orange.com]
> |    Sent: Sunday, February 22, 2015 11:10 PM
> |    To: Les Ginsberg (ginsberg); Pushpasis Sarkar; Jeff Tantsura;
> |    rtgwg@ietf.org
> |    Subject: RE: LFA manageability : per AF config => feedback required
> |
> |
> |
> |    [Les:] I think your point here is that the LFA calculation is AF
> |    independent within a given topology - but resources are consumed
> |    independent of how many computations are required- giving an operator the
> |    ability to determine which prefixes are most critical seems useful. That
> |    could be per AF or per prefix.
> |
> |
> |
> |    [SLI] Agree but is the "resource saving" point strong enough to mandate
> |    per AF activation ?
> |
> |
> |
> |    From: Les Ginsberg (ginsberg) [[1]mailto:ginsberg@cisco.com]
> |    Sent: Monday, February 23, 2015 05:01
> |    To: Pushpasis Sarkar; Jeff Tantsura; LITKOWSKI Stephane SCE/IBNF;
> |    [2]rtgwg@ietf.org
> |    Subject: RE: LFA manageability : per AF config => feedback required
> |
> |
> |
> |    Pushpassis -
> |
> |
> |
> |    From: rtgwg [[3]mailto:rtgwg-bounces@ietf.org] On Behalf Of Pushpasis
> |    Sarkar
> |    Sent: Friday, February 20, 2015 3:28 AM
> |    To: Jeff Tantsura; [4]stephane.litkowski@orange.com; [5]rtgwg@ietf.org
> |    Subject: Re: LFA manageability : per AF config => feedback required
> |
> |
> |
> |    HI Jeff et al,
> |
> |
> |
> |    I can think of a reason to have a knob per-level(or per-area) or per ISIS
> |    topology(note in ISIS a topology in ISIS always corresponds to a single
> |    AF,)
> |
> |
> |
> |    [Les:] This is a common mistake to make. If one simply uses RFC 5308, then
> |    IPv6 prefixes can be advertised in the same topology as IPv4 (MTID #0) -
> |    and there are implementations which support this. More generally, from the
> |    protocol's POV a given topology can support any combinations of address
> |    families. It is only a convention because of the reserved MTIDs specified
> |    in RFC 5120 that certain MTIDs are "IPv6 only". But if one looks at the
> |    protocol capabilities such a restriction does not exist in general.
> |
> |
> |
> |    Interestingly you contradicted yourself below. J
> |
> |    But I did want to set the record straight on this point - hopefully we are
> |    in agreement.
> |
> |
> |
> |    and per realm and topology in OSPF. But I cannot think of a reason of why
> |    within the same topology we need another set of knobs for each AF. Here,
> |    by AF I understand IPV4 or IPv6.
> |
> |
> |
> |    When both IPV4 and IPV6 are part of the same IGP topology, there is only
> |    one set of backup computations needed to protect both IPV4 and IPv6
> |    traffic.
> |
> |
> |
> |    Also I cannot think of any motivation for an operator to turn on
> |    protection on only one AF and does not want to turn on for the other even
> |    if both AFs has been deployed for normal forwarding.
> |
> |
> |
> |    [Les:] I think your point here is that the LFA calculation is AF
> |    independent within a given topology - but resources are consumed
> |    independent of how many computations are required- giving an operator the
> |    ability to determine which prefixes are most critical seems useful. That
> |    could be per AF or per prefix.
> |
> |
> |
> |       Les
> |
> |
> |
> |    Thanks
> |
> |    -Pushpasis
> |
> |
> |
> |    From: Jeff Tantsura <[6]jeff.tantsura@ericsson.com>
> |    Date: Friday, February 20, 2015 at 12:59 PM
> |    To: "[7]stephane.litkowski@orange.com" <[8]stephane.litkowski@orange.com>,
> |    "[9]rtgwg@ietf.org" <[10]rtgwg@ietf.org>
> |    Subject: Re: LFA manageability : per AF config => feedback required
> |
> |
> |
> |    Hi Stephane,
> |
> |
> |
> |    /chair hat off
> |
> |
> |
> |    IMO in disjoined topologies one should have flexibility to enable/disable
> |    LFA as per AF.
> |
> |
> |
> |
> |
> |    Cheers,
> |
> |    Jeff
> |
> |
> |
> |    From: "[11]stephane.litkowski@orange.com"
> |    <[12]stephane.litkowski@orange.com>
> |    Date: Thursday, February 19, 2015 at 11:21 PM
> |    To: "[13]rtgwg@ietf.org" <[14]rtgwg@ietf.org>
> |    Subject: LFA manageability : per AF config => feedback required
> |
> |
> |
> |      Hi Folks,
> |
> |
> |
> |      As you know, LFA manageability draft is in final phasis ...
> |
> |      The current document states per AF granularity activation as a SHOULD.
> |
> |      "
> |
> |   [15]5.1.  LFA enabling/disabling scope
> |
> |
> |
> |
> |
> |     The granularity of LFA activation should be controlled (as alternate
> |
> |     nexthop consume memory in forwarding plane).
> |
> |
> |
> |     An implementation of LFA SHOULD allow its activation with the
> |
> |     following criteria:
> |
> |
> |
> |     o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,
> |
> |        LDP IPv6 unicast ...
> |
> |
> |
> |     o  Per routing context : VRF, virtual/logical router, global routing
> |
> |        table, ...
> |
> |
> |
> |      "
> |
> |
> |
> |      In the framework of ISIS/OSPF yang modelization, we are challenging this
> |      statement, do we really need to force implementation to support this
> |      "per AF" granularity ?
> |
> |
> |
> |      Please provide as soon as possible your feedback on this and also
> |      provide clear drivers to support or not per AF activation of LFA.
> |
> |
> |
> |
> |
> |      Thanks for your help !
> |
> |
> |
> |
> |
> |      [16]Orange logo
> |
> |
> |
> |      Stephane Litkowski
> |      Network Architect
> |      Orange/SCE/EQUANT/IBNF/ENDD/NDE
> |
> |      Orange Expert Future Networks
> |
> |      phone: [17]+33 2 23 28 49 83
> |      mobile: [18]+33 6 37 86 97 52
> |      [19]stephane.litkowski@orange.com
> |
> |
> |
> |
> |
> |  _________________________________________________________________________________________________________________________
> |
> |
> |
> |  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.
> |
> |  _________________________________________________________________________________________________________________________
> |
> |
> |
> |  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.
> |
> | References
> |
> |    Visible links
> |    1. mailto:ginsberg@cisco.com
> |    2. mailto:rtgwg@ietf.org
> |    3. mailto:rtgwg-bounces@ietf.org
> |    4. mailto:stephane.litkowski@orange.com
> |    5. mailto:rtgwg@ietf.org
> |    6. mailto:jeff.tantsura@ericsson.com
> |    7. mailto:stephane.litkowski@orange.com
> |    8. mailto:stephane.litkowski@orange.com
> |    9. mailto:rtgwg@ietf.org
> |   10. mailto:rtgwg@ietf.org
> |   11. mailto:stephane.litkowski@orange.com
> |   12. mailto:stephane.litkowski@orange.com
> |   13. mailto:rtgwg@ietf.org
> |   14. mailto:rtgwg@ietf.org
> |   15. https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#section-5.1
> |   16. http://www.orange.com/
> |   17. https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20
> |   18. https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20
> |   19. mailto:stephane.litkowski@orange.com
>
>
>
> | _______________________________________________
> | rtgwg mailing list
> | rtgwg@ietf.org
> | https://www.ietf.org/mailman/listinfo/rtgwg
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

##############################################

# Mail Account for technical purposes only

##############################################


From nobody Tue Feb 24 09:07:35 2015
Return-Path: <mbj@tail-f.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 A88301A3BA6; Mon, 23 Feb 2015 11:31:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 tPylhY1_D-Ph; Mon, 23 Feb 2015 11:31:50 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [83.241.162.140]) by ietfa.amsl.com (Postfix) with ESMTP id 0276B1A1B87; Mon, 23 Feb 2015 11:31:49 -0800 (PST)
Received: from localhost (host-90-237-135-209.mobileonline.telia.com [90.237.135.209]) by mail.tail-f.com (Postfix) with ESMTPSA id 198A9128048E; Mon, 23 Feb 2015 20:31:48 +0100 (CET)
Date: Mon, 23 Feb 2015 20:31:40 +0100 (CET)
Message-Id: <20150223.203140.655664249325530031.mbj@tail-f.com>
To: lhotka@nic.cz
Subject: Re: [Rtg-yang-coord] rtg-cfg hierachy (PLEASE REPLY TO THIS ONE WITH THE CORRECT MAIL ALIASES)
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <m2a904zti2.fsf@birdie.labs.nic.cz>
References: <14011_1423852286_54DE42FE_14011_2207_1_D103AD28.E652%acee@cisco.com> <54E47928.8050108@orange.com> <m2a904zti2.fsf@birdie.labs.nic.cz>
X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/w8kkf8TXP3OHPGJ5ZQq-LiR35WY>
X-Mailman-Approved-At: Tue, 24 Feb 2015 09:07:33 -0800
Cc: rtg-yang-coord@ietf.org, thomas.morin@orange.com, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2015 19:31:51 -0000

Ladislav Lhotka <lhotka@nic.cz> wrote:
> Thomas Morin <thomas.morin@orange.com> writes:
> > Additionally, Lada, you say that based on my comments "in rev. -03 the 
> > list of RIBs (then called "routing-table") was the moved out of the 
> > routing instance (then called "router") and became global.". But if I 
> > look at -03, "routing-table" is still a child of "router".  The change 
> > to make "routing-table" global was made in -05.
> >
> > I guess you need to find out what was the motivation for the change in 
> > -05, a few months after my initial comments were address.
> 
> Yes, you are right, it seems the immediate motivation for this change
> was this review by Martin Bjorklund:
> 
> http://www.ietf.org/mail-archive/web/netmod/current/msg06962.html

I don't really understand what exactly in this review led to that
change?


/martin


From nobody Tue Feb 24 09:30:41 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 3D3FB1A1B7D for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 09:30:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.302
X-Spam-Level: 
X-Spam-Status: No, score=-1.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_84=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 ZyavXDPeGZ_r for <rtgwg@ietfa.amsl.com>; Tue, 24 Feb 2015 09:30:37 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0733.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::733]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2110B1A00D0 for <rtgwg@ietf.org>; Tue, 24 Feb 2015 09:30:37 -0800 (PST)
Received: from hannes-mba.local (193.110.55.16) by DM2PR05MB446.namprd05.prod.outlook.com (10.141.104.142) with Microsoft SMTP Server (TLS) id 15.1.87.18; Tue, 24 Feb 2015 17:30:11 +0000
Received: from hannes-mba.local (localhost [IPv6:::1]) by hannes-mba.local (Postfix) with ESMTP id 016F0F5535F; Tue, 24 Feb 2015 18:29:54 +0100 (CET)
Date: Tue, 24 Feb 2015 18:29:54 +0100
From: Hannes Gredler <hannes@juniper.net>
To: Martin Horneffer <maho@nic.dtag.de>
Subject: Re: LFA manageability : per AF config => feedback required
Message-ID: <20150224172954.GA3901@hannes-mba.local>
References: <20313_1424416868_54E6E064_20313_5668_1_9E32478DFA9976438E7A22F69B08FF9215C13D54@OPEXCLILM34.corporate.adroot.infra.ftgroup> <D10C20F9.8EB79%jeff.tantsura@ericsson.com> <D10D0F95.20C04%psarkar@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F4EF2D78F@xmb-aln-x02.cisco.com> <5876_1424675401_54EAD249_5876_2527_11_9E32478DFA9976438E7A22F69B08FF9215C157AC@OPEXCLILM34.corporate.adroot.infra.ftgroup> <F3ADE4747C9E124B89F0ED2180CC814F4EF2EE71@xmb-aln-x02.cisco.com> <20150224150228.GB2688@hannes-mba.local> <54ECACD4.2070409@nic.dtag.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <54ECACD4.2070409@nic.dtag.de>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Originating-IP: [193.110.55.16]
X-ClientProxiedBy: DB3PR01CA0059.eurprd01.prod.exchangelabs.com (10.242.133.162) To DM2PR05MB446.namprd05.prod.outlook.com (10.141.104.142)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=hannes@juniper.net; 
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR05MB446;
X-Microsoft-Antispam-PRVS: <DM2PR05MB446168BE0E910C5FC7612BFC2160@DM2PR05MB446.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005004); SRVR:DM2PR05MB446; 
X-Forefront-PRVS: 04976078F0
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(40764003)(24454002)(199003)(53754006)(377454003)(23726002)(5890100001)(66066001)(76506005)(98436002)(93886004)(110136001)(122386002)(76176999)(33656002)(122856001)(40100003)(46102003)(97736003)(97756001)(62966003)(50466002)(86362001)(77156002)(64706001)(46406003)(83506001)(50986999)(68736005)(2950100001)(47776003)(105586002)(101416001)(54356999)(106356001)(19580395003)(19580405001)(77096005)(92566002)(87976001)(15975445007)(19627235001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR05MB446; H:hannes-mba.local; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:DM2PR05MB446;
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Feb 2015 17:30:11.1917 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR05MB446
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/wFtlw5IFa6KdspywYpVahsFGuW0>
Cc: 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, 24 Feb 2015 17:30:40 -0000

martin,

can you describe what are the pain points of FRR protecting
*all* your traffic (IPv4/IPv6/labeled/unlabeled) ?

why would you want your traffic not being protected ?

/hannes

On Tue, Feb 24, 2015 at 05:54:44PM +0100, Martin Horneffer wrote:
| Hello everyone,
| 
| I really do see a good use-case for turning on IP-FRR protection for just
| one address family, and it does not have anything to do with making IPv6
| customer better or worse than IPv4 customer traffic.
| 
| Consider the IP/MPLS network I have today. Several address families are
| active in the backbone, but all customer traffic is carried in MPLS packets
| guided by IPv4-signalled LDP. This holds for ANY customer traffic, whether
| it is public IPv4, public IPv6, VPNs in IPv4 or IPv6 or L2-VPNs. Unlabeled
| IPv4 traffic also exists in the same backbone, but only for routing
| protocols themselves, and/or network management. Thus there is no need to
| protect this unlabeled IPv4 traffic in the same way as the customer MPLS
| traffic.
| 
| In the future, I might activate IPv6 in the backbone and introduce more and
| more routing and management protocols with IPv6. Still no need to protect
| IPv6. Eventually I might shift LDP (or SR) from IPv4 controlled to IPv6
| controlled. What was IPv6-over-IPv4-controlled-MPLS becomes plain
| IPv6-labeled traffic then, and IPv4-labeled traffic will become
| IPv4-over-IPv6-controlled-MPLS. At THAT point in time it becomes important
| to protect the IPv6 controlled MPLS traffic, and thus the IPv6 address
| family in the IGP, but no earlier.
| 
| So please do not mix up control traffic and customer traffic, internal
| routing and customer routes. Thank you.
| 
| Best regards, Martin
| 
| 
| Am 24.02.15 um 16:02 schrieb Hannes Gredler:
| >On Mon, Feb 23, 2015 at 03:55:32PM +0000, Les Ginsberg (ginsberg) wrote:
| >|    I can imagine cases in which the per AF enabling might make sense (e.g.
| >|    when the network associated w one address family is deemed non-critical).
| >
| >
| >HG> as it is unlikely that operators will tun off IPv4 protection,
| >     may i have a ask that you repeat that quote above in the 6man
| >     meeting ;-) ? - effectifely you're saying "IPv6 may be considered
| >     as less critical", and therefore we SHOULD provide a knob
| >     to turn protection off.
| >
| >|
| >|
| >|    Section 5.1 is a SHOULD - as is most of the document. It is therefore a
| >|    suggestion as to what an implementation should provide. If a given
| >|    implementer thinks this is either too onerous or not useful they can omit
| >|    it w/o being in violation. But I see no reason to eliminate this - and in
| >|    actual practice I would expect the cost of supporting such a knob to be
| >|    low cost. It is hard for me to see this as controversial.
| >|
| >|
| >|
| >|       Les
| >|
| >|
| >|
| >|
| >|
| >|    From: stephane.litkowski@orange.com [mailto:stephane.litkowski@orange.com]
| >|    Sent: Sunday, February 22, 2015 11:10 PM
| >|    To: Les Ginsberg (ginsberg); Pushpasis Sarkar; Jeff Tantsura;
| >|    rtgwg@ietf.org
| >|    Subject: RE: LFA manageability : per AF config => feedback required
| >|
| >|
| >|
| >|    [Les:] I think your point here is that the LFA calculation is AF
| >|    independent within a given topology - but resources are consumed
| >|    independent of how many computations are required- giving an operator the
| >|    ability to determine which prefixes are most critical seems useful. That
| >|    could be per AF or per prefix.
| >|
| >|
| >|
| >|    [SLI] Agree but is the "resource saving" point strong enough to mandate
| >|    per AF activation ?
| >|
| >|
| >|
| >|    From: Les Ginsberg (ginsberg) [[1]mailto:ginsberg@cisco.com]
| >|    Sent: Monday, February 23, 2015 05:01
| >|    To: Pushpasis Sarkar; Jeff Tantsura; LITKOWSKI Stephane SCE/IBNF;
| >|    [2]rtgwg@ietf.org
| >|    Subject: RE: LFA manageability : per AF config => feedback required
| >|
| >|
| >|
| >|    Pushpassis -
| >|
| >|
| >|
| >|    From: rtgwg [[3]mailto:rtgwg-bounces@ietf.org] On Behalf Of Pushpasis
| >|    Sarkar
| >|    Sent: Friday, February 20, 2015 3:28 AM
| >|    To: Jeff Tantsura; [4]stephane.litkowski@orange.com; [5]rtgwg@ietf.org
| >|    Subject: Re: LFA manageability : per AF config => feedback required
| >|
| >|
| >|
| >|    HI Jeff et al,
| >|
| >|
| >|
| >|    I can think of a reason to have a knob per-level(or per-area) or per ISIS
| >|    topology(note in ISIS a topology in ISIS always corresponds to a single
| >|    AF,)
| >|
| >|
| >|
| >|    [Les:] This is a common mistake to make. If one simply uses RFC 5308, then
| >|    IPv6 prefixes can be advertised in the same topology as IPv4 (MTID #0) -
| >|    and there are implementations which support this. More generally, from the
| >|    protocol's POV a given topology can support any combinations of address
| >|    families. It is only a convention because of the reserved MTIDs specified
| >|    in RFC 5120 that certain MTIDs are "IPv6 only". But if one looks at the
| >|    protocol capabilities such a restriction does not exist in general.
| >|
| >|
| >|
| >|    Interestingly you contradicted yourself below. J
| >|
| >|    But I did want to set the record straight on this point - hopefully we are
| >|    in agreement.
| >|
| >|
| >|
| >|    and per realm and topology in OSPF. But I cannot think of a reason of why
| >|    within the same topology we need another set of knobs for each AF. Here,
| >|    by AF I understand IPV4 or IPv6.
| >|
| >|
| >|
| >|    When both IPV4 and IPV6 are part of the same IGP topology, there is only
| >|    one set of backup computations needed to protect both IPV4 and IPv6
| >|    traffic.
| >|
| >|
| >|
| >|    Also I cannot think of any motivation for an operator to turn on
| >|    protection on only one AF and does not want to turn on for the other even
| >|    if both AFs has been deployed for normal forwarding.
| >|
| >|
| >|
| >|    [Les:] I think your point here is that the LFA calculation is AF
| >|    independent within a given topology - but resources are consumed
| >|    independent of how many computations are required- giving an operator the
| >|    ability to determine which prefixes are most critical seems useful. That
| >|    could be per AF or per prefix.
| >|
| >|
| >|
| >|       Les
| >|
| >|
| >|
| >|    Thanks
| >|
| >|    -Pushpasis
| >|
| >|
| >|
| >|    From: Jeff Tantsura <[6]jeff.tantsura@ericsson.com>
| >|    Date: Friday, February 20, 2015 at 12:59 PM
| >|    To: "[7]stephane.litkowski@orange.com" <[8]stephane.litkowski@orange.com>,
| >|    "[9]rtgwg@ietf.org" <[10]rtgwg@ietf.org>
| >|    Subject: Re: LFA manageability : per AF config => feedback required
| >|
| >|
| >|
| >|    Hi Stephane,
| >|
| >|
| >|
| >|    /chair hat off
| >|
| >|
| >|
| >|    IMO in disjoined topologies one should have flexibility to enable/disable
| >|    LFA as per AF.
| >|
| >|
| >|
| >|
| >|
| >|    Cheers,
| >|
| >|    Jeff
| >|
| >|
| >|
| >|    From: "[11]stephane.litkowski@orange.com"
| >|    <[12]stephane.litkowski@orange.com>
| >|    Date: Thursday, February 19, 2015 at 11:21 PM
| >|    To: "[13]rtgwg@ietf.org" <[14]rtgwg@ietf.org>
| >|    Subject: LFA manageability : per AF config => feedback required
| >|
| >|
| >|
| >|      Hi Folks,
| >|
| >|
| >|
| >|      As you know, LFA manageability draft is in final phasis ...
| >|
| >|      The current document states per AF granularity activation as a SHOULD.
| >|
| >|      "
| >|
| >|   [15]5.1.  LFA enabling/disabling scope
| >|
| >|
| >|
| >|
| >|
| >|     The granularity of LFA activation should be controlled (as alternate
| >|
| >|     nexthop consume memory in forwarding plane).
| >|
| >|
| >|
| >|     An implementation of LFA SHOULD allow its activation with the
| >|
| >|     following criteria:
| >|
| >|
| >|
| >|     o  Per address-family : ipv4 unicast, ipv6 unicast, LDP IPv4 unicast,
| >|
| >|        LDP IPv6 unicast ...
| >|
| >|
| >|
| >|     o  Per routing context : VRF, virtual/logical router, global routing
| >|
| >|        table, ...
| >|
| >|
| >|
| >|      "
| >|
| >|
| >|
| >|      In the framework of ISIS/OSPF yang modelization, we are challenging this
| >|      statement, do we really need to force implementation to support this
| >|      "per AF" granularity ?
| >|
| >|
| >|
| >|      Please provide as soon as possible your feedback on this and also
| >|      provide clear drivers to support or not per AF activation of LFA.
| >|
| >|
| >|
| >|
| >|
| >|      Thanks for your help !
| >|
| >|
| >|
| >|
| >|
| >|      [16]Orange logo
| >|
| >|
| >|
| >|      Stephane Litkowski
| >|      Network Architect
| >|      Orange/SCE/EQUANT/IBNF/ENDD/NDE
| >|
| >|      Orange Expert Future Networks
| >|
| >|      phone: [17]+33 2 23 28 49 83
| >|      mobile: [18]+33 6 37 86 97 52
| >|      [19]stephane.litkowski@orange.com
| >|
| >|
| >|
| >|
| >|
| >|  _________________________________________________________________________________________________________________________
| >|
| >|
| >|
| >|  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.
| >|
| >|  _________________________________________________________________________________________________________________________
| >|
| >|
| >|
| >|  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.
| >|
| >| References
| >|
| >|    Visible links
| >|    1. mailto:ginsberg@cisco.com
| >|    2. mailto:rtgwg@ietf.org
| >|    3. mailto:rtgwg-bounces@ietf.org
| >|    4. mailto:stephane.litkowski@orange.com
| >|    5. mailto:rtgwg@ietf.org
| >|    6. mailto:jeff.tantsura@ericsson.com
| >|    7. mailto:stephane.litkowski@orange.com
| >|    8. mailto:stephane.litkowski@orange.com
| >|    9. mailto:rtgwg@ietf.org
| >|   10. mailto:rtgwg@ietf.org
| >|   11. mailto:stephane.litkowski@orange.com
| >|   12. mailto:stephane.litkowski@orange.com
| >|   13. mailto:rtgwg@ietf.org
| >|   14. mailto:rtgwg@ietf.org
| >|   15. https://tools.ietf.org/html/draft-ietf-rtgwg-lfa-manageability-07#section-5.1
| >|   16. http://www.orange.com/
| >|   17. https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20
| >|   18. https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20
| >|   19. mailto:stephane.litkowski@orange.com
| >
| >
| >
| >| _______________________________________________
| >| rtgwg mailing list
| >| rtgwg@ietf.org
| >| https://www.ietf.org/mailman/listinfo/rtgwg
| >
| >_______________________________________________
| >rtgwg mailing list
| >rtgwg@ietf.org
| >https://www.ietf.org/mailman/listinfo/rtgwg
| 
| ##############################################
| 
| # Mail Account for technical purposes only
| 
| ##############################################
| 
| _______________________________________________
| rtgwg mailing list
| rtgwg@ietf.org
| https://www.ietf.org/mailman/listinfo/rtgwg


From nobody Tue Feb 24 10:29:08 2015
Return-Path: <jhaas@slice.pfrc.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 1FFEC1A8790; Tue, 24 Feb 2015 10:29:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.578
X-Spam-Level: 
X-Spam-Status: No, score=-1.578 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 mlYhgKZ1_JwS; Tue, 24 Feb 2015 10:29:00 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 5CB401A1BE8; Tue, 24 Feb 2015 10:29:00 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 839DCC212; Tue, 24 Feb 2015 13:28:59 -0500 (EST)
Date: Tue, 24 Feb 2015 13:28:59 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Acee Lindem (acee)" <acee@cisco.com>
Subject: Re: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances
Message-ID: <20150224182859.GB13211@pfrc>
References: <20150114155450.GA3625@elstar.local> <AAB1CC9C17CBA440BDFA169056B93B9EB1139B@eusaamb107.ericsson.se> <CABCOCHSiWG=x0vTYKKxqhMqd69yK+Nuo0k_Y_=Y_KHkQBDi3FA@mail.gmail.com> <D0DBD855.889EB%jeff.tantsura@ericsson.com> <AAB1CC9C17CBA440BDFA169056B93B9EB11472@eusaamb107.ericsson.se> <20150114174655.GA3932@elstar.local> <D1029726.E4B5%acee@cisco.com> <m2k2zm9kg9.fsf@birdie.labs.nic.cz> <D103A0D5.E60D%acee@cisco.com> <D103A6D1.E624%acee@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <D103A6D1.E624%acee@cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/HZgwZqSJNZGbBRVHyx65rBzcLyI>
Cc: "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Andy Bierman <andy@yumaworks.com>, Xufeng Liu <xufeng.liu@ericsson.com>, Routing WG <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, 24 Feb 2015 18:29:01 -0000

[I'm behind as usual and this may have been discussed already.]

On Fri, Feb 13, 2015 at 06:07:11PM +0000, Acee Lindem (acee) wrote:
> Independent of the hierarchy, I think an interface should be associated
> with one and only routing-instance. I know of no implementation that
> allows this (including the use case of separate instances for IPv4 and
> IPv6). 

While junos does have the interface as part of the routing instance
interface hierarchy, you're also correct in that junos enforces that the
interface is only associated with one instance.

The question is with regard to generic modeling: Should a single unified
interface model with the ability to associate the interface with the
instance?  Should the instance refer to interfaces?

My concern with making the interface model point to associated instances is
how we handle versioning for unknown things that we may want to associate
that interface with.  The interface model is something we want to be rock
solid stable, not something that needs to be revised each time some new
instancing mechanism is created.

-- Jeff


From nobody Wed Feb 25 17:56:57 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 6DF631A92E6; Wed, 25 Feb 2015 17:56:54 -0800 (PST)
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 TtlqwSBZaBt4; Wed, 25 Feb 2015 17:56:53 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B57B1A92E8; Wed, 25 Feb 2015 17:56:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1907; q=dns/txt; s=iport; t=1424915812; x=1426125412; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ZbMIS/botL/nh6/b8r0vsuKWY7sfclEkr1g+d6jPJdo=; b=nLRY8MHx236ifj3qleVD13v7Bk3D8OijUo7Vptt3Ft3PCesPzNzJa93W JItRibFPCPqFdKmyqwO5idgpcGiNE9bFqH6130u21SEKSRLdjoa/gMnWj FZIEE9sFO//SLVo1Ej5vZbuRZx026FH4NQOxWwTc+/0Du886Nzmv4Gtjl o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C0BQBPfO5U/4YNJK1bgwKBLATJFAKBJ0MBAQEBAQF8hBABAQR5EAIBCA4KLjIlAgQOBYgv1V4BAQEBAQEBAQEBAQEBAQEBAQEBGYsThDszB4QrBYoihUGJRYEbjmiDPiKDbm+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.09,649,1418083200"; d="scan'208";a="127034622"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-4.cisco.com with ESMTP; 26 Feb 2015 01:56:52 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t1Q1upoq017226 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 26 Feb 2015 01:56:51 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.175]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0195.001; Wed, 25 Feb 2015 19:56:51 -0600
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Subject: Re: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances
Thread-Topic: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances
Thread-Index: AQHQRxj77tD6GUYxhkmEAnTuReZw3pzuxUwAgAAm/wCAAAYLAIARo4+AgAG7o4A=
Date: Thu, 26 Feb 2015 01:56:51 +0000
Message-ID: <D113E560.F484%acee@cisco.com>
References: <20150114155450.GA3625@elstar.local> <AAB1CC9C17CBA440BDFA169056B93B9EB1139B@eusaamb107.ericsson.se> <CABCOCHSiWG=x0vTYKKxqhMqd69yK+Nuo0k_Y_=Y_KHkQBDi3FA@mail.gmail.com> <D0DBD855.889EB%jeff.tantsura@ericsson.com> <AAB1CC9C17CBA440BDFA169056B93B9EB11472@eusaamb107.ericsson.se> <20150114174655.GA3932@elstar.local> <D1029726.E4B5%acee@cisco.com> <m2k2zm9kg9.fsf@birdie.labs.nic.cz> <D103A0D5.E60D%acee@cisco.com> <D103A6D1.E624%acee@cisco.com> <20150224182859.GB13211@pfrc>
In-Reply-To: <20150224182859.GB13211@pfrc>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.152.197]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <3AC23F9F9DD99644917DC9408F96BC75@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/z_iHWw7GSy-sgs7_V6gkimeBPoE>
Cc: "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Andy Bierman <andy@yumaworks.com>, Xufeng Liu <xufeng.liu@ericsson.com>, Routing WG <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, 26 Feb 2015 01:56:54 -0000

On 2/24/15, 1:28 PM, "Jeffrey Haas" <jhaas@pfrc.org> wrote:

>[I'm behind as usual and this may have been discussed already.]
>
>On Fri, Feb 13, 2015 at 06:07:11PM +0000, Acee Lindem (acee) wrote:
>> Independent of the hierarchy, I think an interface should be associated
>> with one and only routing-instance. I know of no implementation that
>> allows this (including the use case of separate instances for IPv4 and
>> IPv6).=20
>
>While junos does have the interface as part of the routing instance
>interface hierarchy, you're also correct in that junos enforces that the
>interface is only associated with one instance.
>
>The question is with regard to generic modeling: Should a single unified
>interface model with the ability to associate the interface with the
>instance?  Should the instance refer to interfaces?
>
>My concern with making the interface model point to associated instances
>is
>how we handle versioning for unknown things that we may want to associate
>that interface with.  The interface model is something we want to be rock
>solid stable, not something that needs to be revised each time some new
>instancing mechanism is created.

Since what I=B9m suggesting is having rtg-cfg augment the interface model, =
I
don=B9t understand your concern. Why is the new model having a separate lis=
t
of interfaces any more =B3rock solid=B2 than the existing interface to
reference the associated routing instance?

My concern is much easier to understand - with existing configuration
information augmenting the RFC 7223 model and some new subset of
configuration information augmenting the interface list, we have a
bifurcated extension model. Independent of which way we decide to proceed,
this issue needs to be addressed lest we have confusion every time a new
model needs to augment interface configuration.

Acee=20




>
>-- Jeff


From nobody Thu Feb 26 00:43:46 2015
Return-Path: <lhotka@nic.cz>
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 357061A1B4A; Thu, 26 Feb 2015 00:43:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_74=0.6] 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 hrMp4juXEcr7; Thu, 26 Feb 2015 00:43:42 -0800 (PST)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id 52CF51A1B17; Thu, 26 Feb 2015 00:43:41 -0800 (PST)
Received: from localhost (unknown [195.113.220.110]) by trail.lhotka.name (Postfix) with ESMTPSA id 5A4931CC006E; Thu, 26 Feb 2015 09:43:48 +0100 (CET)
From: Ladislav Lhotka <lhotka@nic.cz>
To: "Acee Lindem \(acee\)" <acee@cisco.com>, Jeffrey Haas <jhaas@pfrc.org>
Subject: Re: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances
In-Reply-To: <D113E560.F484%acee@cisco.com>
References: <20150114155450.GA3625@elstar.local> <AAB1CC9C17CBA440BDFA169056B93B9EB1139B@eusaamb107.ericsson.se> <CABCOCHSiWG=x0vTYKKxqhMqd69yK+Nuo0k_Y_=Y_KHkQBDi3FA@mail.gmail.com> <D0DBD855.889EB%jeff.tantsura@ericsson.com> <AAB1CC9C17CBA440BDFA169056B93B9EB11472@eusaamb107.ericsson.se> <20150114174655.GA3932@elstar.local> <D1029726.E4B5%acee@cisco.com> <m2k2zm9kg9.fsf@birdie.labs.nic.cz> <D103A0D5.E60D%acee@cisco.com> <D103A6D1.E624%acee@cisco.com> <20150224182859.GB13211@pfrc> <D113E560.F484%acee@cisco.com>
User-Agent: Notmuch/0.19 (http://notmuchmail.org) Emacs/24.4.51.2 (x86_64-apple-darwin14.0.0)
Date: Thu, 26 Feb 2015 09:43:37 +0100
Message-ID: <m2twy912rq.fsf@birdie.labs.nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/2xr7jn_BwuMFK8HGpF5Zy0YK3BQ>
Cc: "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>, Routing WG <rtgwg@ietf.org>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Andy Bierman <andy@yumaworks.com>, Xufeng Liu <xufeng.liu@ericsson.com>
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, 26 Feb 2015 08:43:44 -0000

"Acee Lindem (acee)" <acee@cisco.com> writes:

> On 2/24/15, 1:28 PM, "Jeffrey Haas" <jhaas@pfrc.org> wrote:
>
>>[I'm behind as usual and this may have been discussed already.]
>>
>>On Fri, Feb 13, 2015 at 06:07:11PM +0000, Acee Lindem (acee) wrote:
>>> Independent of the hierarchy, I think an interface should be associated
>>> with one and only routing-instance. I know of no implementation that
>>> allows this (including the use case of separate instances for IPv4 and
>>> IPv6).=20
>>
>>While junos does have the interface as part of the routing instance
>>interface hierarchy, you're also correct in that junos enforces that the
>>interface is only associated with one instance.
>>
>>The question is with regard to generic modeling: Should a single unified
>>interface model with the ability to associate the interface with the
>>instance?  Should the instance refer to interfaces?
>>
>>My concern with making the interface model point to associated instances
>>is
>>how we handle versioning for unknown things that we may want to associate
>>that interface with.  The interface model is something we want to be rock
>>solid stable, not something that needs to be revised each time some new
>>instancing mechanism is created.
>
> Since what I=C2=B9m suggesting is having rtg-cfg augment the interface mo=
del, I
> don=C2=B9t understand your concern. Why is the new model having a separat=
e list
> of interfaces any more =C2=B3rock solid=C2=B2 than the existing interface=
 to
> reference the associated routing instance?

Acee is right - it is an augment and its data belong to a different
namespace, so it really doesn't affect the interface model. Actually, I
think it would be done the same way (via an augment from another module)
even if we envisioned from the start that the assignment of interfaces
to routing instances will be done inside the interface hierarchy..

My concern regarding the change that Acee proposes is that this schema
extension cannot be made specific so that only a subset of interfaces
(L3) can be assigned to routing instances - at least I don't know how to
do it formally in the data model. The problem has to do with the fact
that interfaces of all layers and types are kept in the same flat list.

>
> My concern is much easier to understand - with existing configuration
> information augmenting the RFC 7223 model and some new subset of
> configuration information augmenting the interface list, we have a
> bifurcated extension model. Independent of which way we decide to

If it is the other way around, one could then argue that the
routing-instance configuration is bifurcated. I think both ways are
possible in principle, and are just a matter of taste, or perhaps legacy
CLI considerations.

> proceed,this issue needs to be addressed lest we have confusion every
> time a new model needs to augment interface configuration.

I agree, we have to make a choice.

Lada

>
> Acee=20
>
>
>
>
>>
>>-- Jeff
>

--=20
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C


From nobody Fri Feb 27 03:49:58 2015
Return-Path: <lhotka@nic.cz>
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 F1C8B1A9175; Fri, 27 Feb 2015 03:49:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6] 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 zJbOV2VJ0LxH; Fri, 27 Feb 2015 03:49:54 -0800 (PST)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id 6B0A41A00CA; Fri, 27 Feb 2015 03:49:54 -0800 (PST)
Received: from localhost (unknown [195.113.220.110]) by trail.lhotka.name (Postfix) with ESMTPSA id 432421CC0156; Fri, 27 Feb 2015 12:49:52 +0100 (CET)
From: Ladislav Lhotka <lhotka@nic.cz>
To: Dean Bogdanovic <deanb@juniper.net>
Subject: Re: [Rtg-yang-coord] rtg-cfg hierachy (Indentation in hierarchy	corrected)
In-Reply-To: <06F5B0A6-15D4-4AD2-8C74-A46AF5C84E46@juniper.net>
References: <D10A678C.EB2C%acee@cisco.com> <m27fv8zsl0.fsf@birdie.labs.nic.cz> <06F5B0A6-15D4-4AD2-8C74-A46AF5C84E46@juniper.net>
User-Agent: Notmuch/0.19 (http://notmuchmail.org) Emacs/24.4.51.2 (x86_64-apple-darwin14.0.0)
Date: Fri, 27 Feb 2015 12:49:53 +0100
Message-ID: <m2ioenvaji.fsf@birdie.labs.nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/RGGgOEYqoxWw5nw-MSKDvgQsA7E>
Cc: Routing YANG <rtg-yang-coord@ietf.org>, "EXT - thomas.morin@orange.com" <thomas.morin@orange.com>, Routing WG <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, 27 Feb 2015 11:49:57 -0000

Dean Bogdanovic <deanb@juniper.net> writes:

> On Feb 23, 2015, at 8:05 AM, Ladislav Lhotka <lhotka@nic.cz> wrote:
>>=20
>>>=20
>>> This would imply that RIBs are within a routing-instance and that
>>=20
>> It seems (Junos experts, please confirm) that in Junos user-defined
>> routing tables can be specified both globally and per routing-instance:
>>=20
>> http://www.juniper.net/documentation/en_US/junos14.2/topics/reference/co=
nfiguration-statement/export-rib-edit-routing-options.html
>
> Lada,
>
> Not sure what are you are getting at. In Junos you create rib-groups

I am trying to figure out whether it is absolutely safe to assume that
every RIB can be confined to a single routing instance - Acee proposed
to make "ribs" a child of "routing-instance" whereas now it is global (a
child of "routing").

Lada

> and within rib-groups multiple RIBs can be specified. A RIB group is a
> way to have a routing protocol, place information in multiple route
> tables. And then you are exporting from rib-group RIBs to RIBs within
> routing-instances. Or vice versa, importing from RIBs in
> routing-instances into rib-groups.

>
> This is a special case in my opinion.
>
> Dean
>>=20
>>> routing-protocols within the routing-instance can operate on these RIBs.
>>> There is no requirement connect RIBs to routing-protocols or to form
>>> connections between RIBs.
>>>=20
>>> This would give us a high-level hierarchy of:
>>>=20
>>> rw routing-instance* [name]
>>>      |  +--rw address-family
>>>      |  |  |--rw default-rib* [address-family]
>>>      |  |  +--rw non-default-ribs (feature)
>>>      |  +--rw routing-protocols
>>>      |     +=E2=80=95--rw routing-protocol* [type name]
>>>=20
>>> I intensionally left out the interfaces since I don=E2=80=99t like some=
 models
>>> augmenting or referencing the ietf-interface list and others augmenting=
 or
>>> referencing the list in our rtg-cfg draft.
>>>=20
>>> Thanks,
>>> Acee
>>>=20
>>>=20
>>>=20
>>>=20
>>> On 2/18/15, 6:36 AM, "Thomas Morin" <thomas.morin@orange.com> wrote:
>>>=20
>>>> Hi Acee, Lada,
>>>>=20
>>>> It seems that my comment that you quote was more related to filters th=
an
>>>> to routing tables, and indeed, *filters* were moved from "router" to
>>>> "global" in revision -03 that followed my review.
>>>>=20
>>>> Additionally, Lada, you say that based on my comments "in rev. -03 the
>>>> list of RIBs (then called "routing-table") was the moved out of the
>>>> routing instance (then called "router") and became global.". But if I
>>>> look at -03, "routing-table" is still a child of "router".  The change
>>>> to make "routing-table" global was made in -05.
>>>>=20
>>>> I guess you need to find out what was the motivation for the change in
>>>> -05, a few months after my initial comments were address.
>>>>=20
>>>> Best,
>>>>=20
>>>> -Thomas
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> 2015-02-13, Acee Lindem (acee):
>>>>>=20
>>>>> Hi Lada, Thomas,
>>>>>=20
>>>>> On 2/13/15, 5:10 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:
>>>>>=20
>>>>>> Hi,
>>>>>>=20
>>>>>> "Acee Lindem (acee)" <acee@cisco.com> writes:
>>>>>>=20
>>>>>>> Hi Thomas,
>>>>>>>=20
>>>>>>> It is my understanding that the RIBs were moved out of the
>>>>>>> routing-instance in response to your comment that a RIB would need =
to
>>>>>>> be
>>>>>>> attached to multiple routing instances. I don=C2=B9t agree with this
>>>>>>> model. I
>>>>>>=20
>>>>>> Acee refers to this comment that Thomas made in his review of
>>>>>> draft-ietf-netmod-routing-cfg-02 on 2012-03-23:
>>>>>>=20
>>>>>> "Allowing multiple "routers" is a good starting point for using these
>>>>>> specs in the context of RFC4364 (MPLS/BGP IP VPNs). However, if I
>>>>>> understand correctly Yang syntax, the way the filters are defined wo=
uld
>>>>>> not work in the context of RFC4364, where a BGP routing instance in =
the
>>>>>> master "router" exports selected routes in each of the routing table=
 of
>>>>>> each VPN (VRF).  The VRF also export routes to the master instance."
>>>>>>=20
>>>>>> And indeed, in rev. -03 the list of RIBs (then called "routing-table=
")
>>>>>> was the moved out of the routing instance (then called "router") and
>>>>>> became global.
>>>>>=20
>>>>> Then do you agree to move the RIBs back into the routing-instance? Bo=
th
>>>>> the BGP YANG drafts model L3VPN definitions under the corresponding
>>>>> address family in BGP.
>>>>>=20
>>>>> http://www.ietf.org/id/draft-shaikh-idr-bgp-model-00.txt
>>>>> http://www.ietf.org/id/draft-zhdankin-idr-bgp-cfg-00.txt
>>>>>=20
>>>>> Thanks,
>>>>> Acee
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>>=20
>>>>>> Lada
>>>>>>=20
>>>>>>> believe that a routing instance implies a VRF, virtual router or
>>>>>>> something
>>>>>>> in between and that a RIB should be associated with one and only one
>>>>>>> routing instance. Additionally, I feel that RIBs are basically pass=
ive
>>>>>>> entities with respect to import/export of routes between RIBs in the
>>>>>>> same
>>>>>>> or other routing-instances. Rather, all import/export is under the
>>>>>>> control
>>>>>>> of a routing-protocol. For example, this would be handled by a BGP
>>>>>>> routing-protocol instance for L3VPNs.
>>>>>>>=20
>>>>>>> I=C2=B9d like to get the opinions of others on this fundamental asp=
ect of
>>>>>>> the
>>>>>>> rtg-cfg model.
>>>>>>>=20
>>>>>>> Thanks,
>>>>>>> Acee
>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>> --
>>>>>> Ladislav Lhotka, CZ.NIC Labs
>>>>>> PGP Key ID: E74E8C0C
>>>>>=20
>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>>>=20
>>=20
>> --=20
>> Ladislav Lhotka, CZ.NIC Labs
>> PGP Key ID: E74E8C0C
>>=20
>> _______________________________________________
>> Rtg-yang-coord mailing list
>> Rtg-yang-coord@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtg-yang-coord
>

--=20
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C

