
From aretana@cisco.com  Wed Dec  4 05:35:42 2013
Return-Path: <aretana@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 C0A251AE144 for <rtgwg@ietfa.amsl.com>; Wed,  4 Dec 2013 05:35:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tHhBpXWkYU6g for <rtgwg@ietfa.amsl.com>; Wed,  4 Dec 2013 05:35:41 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 38DE91AE10A for <rtgwg@ietf.org>; Wed,  4 Dec 2013 05:35:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1973; q=dns/txt; s=iport; t=1386164138; x=1387373738; h=from:to:cc:subject:date:message-id:mime-version; bh=u3BYEZA1wgoajBRo2KmbRGCbPbF1Z9AHQ3j14jy9kTM=; b=aq4SwgZe1zR80FXobyZy1VEzvLVr+6XufNne6lS5e+W/hr+aqHhi1M93 OXmspwHeDnZQvwC4EkoJQUVrl4J7LLNzXsWL+A/0+XTC+VExIardev4qT AeJoobVyxr8fU35kqsqEOZBr75z6ZpV3VAOR5PWyPEeXsPzDKWHRqWu9q E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkMPAGQun1KtJV2c/2dsb2JhbABagkNEOFOwGBCIQYEjFm0HghwQbgsSAQsBdCcEDogHDcFLF45+hDoDmBSBMJBjgymCKg
X-IronPort-AV: E=Sophos;i="4.93,824,1378857600";  d="scan'208,217";a="289317464"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-8.cisco.com with ESMTP; 04 Dec 2013 13:35:38 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id rB4DZbkk021796 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 4 Dec 2013 13:35:38 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.70]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Wed, 4 Dec 2013 07:35:37 -0600
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: WGLC for draft-ietf-rtgwg-remote-lfa
Thread-Topic: WGLC for draft-ietf-rtgwg-remote-lfa
Thread-Index: AQHO8PW2Bdaax9+gRkGsLYqKlU97/Q==
Date: Wed, 4 Dec 2013 13:35:36 +0000
Message-ID: <CEC4C406.43593%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.238.58]
Content-Type: multipart/alternative; boundary="_000_CEC4C40643593aretanaciscocom_"
MIME-Version: 1.0
Cc: "draft-ietf-rtgwg-remote-lfa@tools.ietf.org" <draft-ietf-rtgwg-remote-lfa@tools.ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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, 04 Dec 2013 13:35:43 -0000

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

Hi!

After what I thought was a productive set of feedback and discussion relate=
d to this draft, both in the mailing list as well as at the meeting in Vanc=
ouver, I would like to start a Working Group Last Call.  This call will clo=
se by EOD (pick your favorite time zone) on December 19, 2013.

http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa

Please provide specific feedback as to why you support (or not) the advance=
ment of this draft.  Please avoid "+1"-type responses.

Thanks!

Alvaro.

--_000_CEC4C40643593aretanaciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <9996FFC1A3C2084DAEF6CC4AA2D044CC@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</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!</div>
<div><br>
</div>
<div>After what I thought was a productive set of feedback and discussion r=
elated to this draft, both in the mailing list as well as at the meeting in=
 Vancouver, I would like to start a Working Group Last Call. &nbsp;This cal=
l will close by EOD (pick your favorite
 time zone) on December 19, 2013.</div>
<div><br>
</div>
<div><a href=3D"http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa">htt=
p://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa</a></div>
<div><br>
</div>
<div>Please provide specific feedback as to why you support (or not) the ad=
vancement of this draft. &nbsp;Please avoid &quot;&#43;1&quot;-type respons=
es.</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>Alvaro.</div>
</body>
</html>

--_000_CEC4C40643593aretanaciscocom_--

From aretana@cisco.com  Wed Dec  4 05:37:57 2013
Return-Path: <aretana@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 6B0BE1AE144 for <rtgwg@ietfa.amsl.com>; Wed,  4 Dec 2013 05:37:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fpeNdMOAOs5d for <rtgwg@ietfa.amsl.com>; Wed,  4 Dec 2013 05:37:55 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id CB19C1AE11E for <rtgwg@ietf.org>; Wed,  4 Dec 2013 05:37:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1708; q=dns/txt; s=iport; t=1386164273; x=1387373873; h=from:to:cc:subject:date:message-id:mime-version; bh=CzTkTu9JaGxTHO9ytg/zH0cxi8qsBtFHqXOByEZIjdc=; b=WTCHGweSdbyAcoRNokZAm+3D9quB0ucx6hEoboHnVLiNhPcYmhxF1+W5 Kr8/eOULC7Hu6QUxhlNCXgpTjpFQr4sv8L8KShgsaNN5sJSGdzpLepXug wC4/gDLBrNmjK29L6D/v/IcfFzO6Jb1RegggjqasNTSva013r8ATzifv1 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4GAFMvn1KtJV2Y/2dsb2JhbABagkNEgQu4aYEjFm0HghwQeRIBCwF0JwQOiAfBWReOfoQ6A5gUkhODKYIq
X-IronPort-AV: E=Sophos;i="4.93,824,1378857600";  d="scan'208,217";a="289387462"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-4.cisco.com with ESMTP; 04 Dec 2013 13:37:53 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rB4Dbqhn028724 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 4 Dec 2013 13:37:52 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.70]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0123.003; Wed, 4 Dec 2013 07:37:52 -0600
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "draft-ietf-rtgwg-remote-lfa@tools.ietf.org" <draft-ietf-rtgwg-remote-lfa@tools.ietf.org>
Subject: IPR Claims related to draft-ietf-rtgwg-remote-lfa
Thread-Topic: IPR Claims related to draft-ietf-rtgwg-remote-lfa
Thread-Index: AQHO8PYHmsA0/dbvx0Odcj7SIoP6Eg==
Date: Wed, 4 Dec 2013 13:37:51 +0000
Message-ID: <CEC4C48C.4359C%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.238.58]
Content-Type: multipart/alternative; boundary="_000_CEC4C48C4359Caretanaciscocom_"
MIME-Version: 1.0
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Dec 2013 13:37:57 -0000

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

Hi!

In parallel to the WGLC for this draft, I want to formally ask the authors =
(no additional contributors are listed in the latest version of the draft) =
to please respond to this message indicating whether or not you are aware o=
f any relevant IPR beyond what has already been disclosed.  The draft will =
not progress (pending the results of the WGLC) until we have received a res=
ponse from each author.

Thanks!

Alvaro.


--_000_CEC4C48C4359Caretanaciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <019BA8934FC20242A24853704FA80B9B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</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>
<div>Hi!</div>
<div><br>
</div>
<div>In parallel to the WGLC for this draft,&nbsp;I want to formally ask th=
e authors (no additional contributors are listed in the latest version of t=
he draft) to please respond to this message indicating whether or not you a=
re aware of any relevant IPR beyond what
 has already been disclosed. &nbsp;The draft will not progress (pending the=
 results of the WGLC) until we have received a response from each author.</=
div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>Alvaro.</div>
</div>
<div><br>
</div>
</body>
</html>

--_000_CEC4C48C4359Caretanaciscocom_--

From Ning.So@tatacommunications.com  Wed Dec  4 06:03:44 2013
Return-Path: <Ning.So@tatacommunications.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 EEAEF1AE254 for <rtgwg@ietfa.amsl.com>; Wed,  4 Dec 2013 06:03:43 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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 4KTKAFFiztmS for <rtgwg@ietfa.amsl.com>; Wed,  4 Dec 2013 06:03:41 -0800 (PST)
Received: from vmx3.tatacommunications.com (vmx3.tatacommunications.com [66.198.167.208]) by ietfa.amsl.com (Postfix) with ESMTP id F3E3F1AE249 for <rtgwg@ietf.org>; Wed,  4 Dec 2013 06:03:39 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.93,824,1378872000"; d="scan'208,217";a="25616487"
Received: from unknown (HELO wv1-cas-02.vsnl.co.in) ([64.86.157.138]) by mx3-2.tatacommunications.com with ESMTP; 04 Dec 2013 09:03:33 -0500
Received: from USWV1VCAS01.vsnl.co.in (64.86.157.177) by wv1-cas-02.vsnl.co.in (64.86.157.138) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 4 Dec 2013 09:03:33 -0500
Received: from USWV1VDAG02.vsnl.co.in ([fe80::7c6a:fd71:7022:40b6]) by uswv1vcas01.vsnl.co.in ([fe80::6521:bbe2:f2e4:7b9b%11]) with mapi id 14.02.0342.003; Wed, 4 Dec 2013 09:03:33 -0500
From: Ning So <Ning.So@tatacommunications.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "draft-ietf-rtgwg-remote-lfa@tools.ietf.org" <draft-ietf-rtgwg-remote-lfa@tools.ietf.org>
Subject: RE: IPR Claims related to draft-ietf-rtgwg-remote-lfa
Thread-Topic: IPR Claims related to draft-ietf-rtgwg-remote-lfa
Thread-Index: AQHO8PYHmsA0/dbvx0Odcj7SIoP6EppEES/Q
Date: Wed, 4 Dec 2013 14:03:33 +0000
Message-ID: <F03A6CD051CB7946A6E58423E26D99A970FCB39E@uswv1vdag02.vsnl.co.in>
References: <CEC4C48C.4359C%aretana@cisco.com>
In-Reply-To: <CEC4C48C.4359C%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.86.157.8]
Content-Type: multipart/alternative; boundary="_000_F03A6CD051CB7946A6E58423E26D99A970FCB39Euswv1vdag02vsnl_"
MIME-Version: 1.0
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Dec 2013 14:03:44 -0000

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

I am not aware of any IPR beyond what has already been disclosed.

Best regards,

Ning So
Head of Network Architecture
Mobile Broadband Services
Tata Communications
(Cell) 972-955-0914

From: Alvaro Retana (aretana) [mailto:aretana@cisco.com]
Sent: Wednesday, December 04, 2013 7:38 AM
To: draft-ietf-rtgwg-remote-lfa@tools.ietf.org
Cc: rtgwg@ietf.org
Subject: IPR Claims related to draft-ietf-rtgwg-remote-lfa

Hi!

In parallel to the WGLC for this draft, I want to formally ask the authors =
(no additional contributors are listed in the latest version of the draft) =
to please respond to this message indicating whether or not you are aware o=
f any relevant IPR beyond what has already been disclosed.  The draft will =
not progress (pending the results of the WGLC) until we have received a res=
ponse from each author.

Thanks!

Alvaro.


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{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"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I am not aware of any IPR=
 beyond what has already been disclosed.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-CA" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best regar=
ds,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-CA" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-CA" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Ning So<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-CA" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Head of Ne=
twork Architecture<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-CA" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Mobile Bro=
adband Services<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-CA" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Tata Commu=
nications
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-CA" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">(Cell) 972=
-955-0914<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-=
size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"> Alvaro=
 Retana (aretana) [mailto:aretana@cisco.com]
<br>
<b>Sent:</b> Wednesday, December 04, 2013 7:38 AM<br>
<b>To:</b> draft-ietf-rtgwg-remote-lfa@tools.ietf.org<br>
<b>Cc:</b> rtgwg@ietf.org<br>
<b>Subject:</b> IPR Claims related to draft-ietf-rtgwg-remote-lfa<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></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">Hi!<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">In parallel to the WGLC for=
 this draft,&nbsp;I want to formally ask the authors (no additional contrib=
utors are listed in the latest version of the draft) to please
 respond to this message indicating whether or not you are aware of any rel=
evant IPR beyond what has already been disclosed. &nbsp;The draft will not =
progress (pending the results of the WGLC) until we have received a respons=
e from each author.<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">Thanks!<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">Alvaro.<o:p></o:p></span></=
p>
</div>
</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>
</body>
</html>

--_000_F03A6CD051CB7946A6E58423E26D99A970FCB39Euswv1vdag02vsnl_--

From psarkar@juniper.net  Wed Dec  4 12:26:25 2013
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 5B0551AD8F5 for <rtgwg@ietfa.amsl.com>; Wed,  4 Dec 2013 12:26:25 -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 71_l3syV_Qzn for <rtgwg@ietfa.amsl.com>; Wed,  4 Dec 2013 12:26:21 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe001.messaging.microsoft.com [65.55.88.11]) by ietfa.amsl.com (Postfix) with ESMTP id D1A051ADF46 for <rtgwg@ietf.org>; Wed,  4 Dec 2013 12:26:20 -0800 (PST)
Received: from mail213-tx2-R.bigfish.com (10.9.14.249) by TX2EHSOBE006.bigfish.com (10.9.40.26) with Microsoft SMTP Server id 14.1.225.22; Wed, 4 Dec 2013 20:26:17 +0000
Received: from mail213-tx2 (localhost [127.0.0.1])	by mail213-tx2-R.bigfish.com (Postfix) with ESMTP id 82D80980122;	Wed,  4 Dec 2013 20:26:17 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT003.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -22
X-BigFish: VPS-22(zz9371Ic85fh103dKzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah1fc6hzz1d7338h1de098h1033IL17326ah8275bh8275dh18c673h1de097h186068hz2fh109h2a8h839hd24hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1bceh224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h20f0h2216h22d0h2336h9a9j1155h)
Received-SPF: pass (mail213-tx2: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=psarkar@juniper.net; helo=BL2PRD0510HT003.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(377454003)(189002)(199002)(41574002)(76482001)(79102001)(81542001)(81342001)(47736001)(47976001)(50986001)(66066001)(65816001)(80022001)(69226001)(19609705001)(15202345003)(63696002)(87266001)(74876001)(46102001)(74316001)(19580395003)(19580405001)(74366001)(51856001)(80976001)(53806001)(49866001)(76576001)(15975445006)(54356001)(4396001)(2656002)(83322001)(81686001)(81816001)(74706001)(90146001)(54316002)(47446002)(56776001)(74502001)(56816005)(19300405004)(87936001)(83072001)(74662001)(85852002)(85306002)(31966008)(33646001)(77982001)(59766001)(76786001)(76796001)(16236675002)(77096001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BN1PR05MB519; H:BN1PR05MB520.namprd05.prod.outlook.com; CLIP:116.197.184.19; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail213-tx2 (localhost.localdomain [127.0.0.1]) by mail213-tx2 (MessageSwitch) id 1386188775426262_20740; Wed,  4 Dec 2013 20:26:15 +0000 (UTC)
Received: from TX2EHSMHS040.bigfish.com (unknown [10.9.14.229])	by mail213-tx2.bigfish.com (Postfix) with ESMTP id 62B5C1C0047; Wed,  4 Dec 2013 20:26:15 +0000 (UTC)
Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by TX2EHSMHS040.bigfish.com (10.9.99.140) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 4 Dec 2013 20:26:14 +0000
Received: from BN1PR05MB519.namprd05.prod.outlook.com (10.141.65.146) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.383.1; Wed, 4 Dec 2013 20:26:09 +0000
Received: from BN1PR05MB520.namprd05.prod.outlook.com (10.141.65.151) by BN1PR05MB519.namprd05.prod.outlook.com (10.141.65.146) with Microsoft SMTP Server (TLS) id 15.0.837.10; Wed, 4 Dec 2013 20:26:07 +0000
Received: from BN1PR05MB520.namprd05.prod.outlook.com ([169.254.14.188]) by BN1PR05MB520.namprd05.prod.outlook.com ([169.254.14.3]) with mapi id 15.00.0815.000; Wed, 4 Dec 2013 20:26:07 +0000
From: Pushpasis Sarkar <psarkar@juniper.net>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: WGLC for draft-ietf-rtgwg-remote-lfa
Thread-Topic: WGLC for draft-ietf-rtgwg-remote-lfa
Thread-Index: AQHO8SuSPPjgq6oFSke8un7cAQV59ZpEdR0g
Date: Wed, 4 Dec 2013 20:26:07 +0000
Message-ID: <c043b7fae6fc4aba9c98bbaad5eab388@BN1PR05MB520.namprd05.prod.outlook.com>
References: <CEC4C406.43593%aretana@cisco.com>
In-Reply-To: <CEC4C406.43593%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [116.197.184.19]
x-forefront-prvs: 0050CEFE70
Content-Type: multipart/alternative; boundary="_000_c043b7fae6fc4aba9c98bbaad5eab388BN1PR05MB520namprd05pro_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "draft-ietf-rtgwg-remote-lfa@tools.ietf.org" <draft-ietf-rtgwg-remote-lfa@tools.ietf.org>, Stewart Bryant <stbryant@cisco.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: Wed, 04 Dec 2013 20:26:25 -0000

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

Hi Stewart/Alvaro,

It maybe a very late, but I wanted to point the following issue with the al=
gorithm/psuedocode text provided in section 4.3.

      /////////////////////////////////////////////////////////////////
      //
      // Calculate extended P-space
      //
      // Note the strictly less than operator is needed to
      // avoid ECMP issues.

      Compute_Extended_P_Space(fail_intf)
          foreach node y in network
              y.in_extended_P_space =3D false
              // Extend P-space to the P-spaces of all reachable
              // neighbours
              foreach interface intf in self
[Pushpasis] From definition of intf.remote_node, there maybe multiple 'remo=
te_node's for a given 'intf' (specially if the 'intf' is a LAN intf. So the=
re should be another 'foreach intf.remote_node in intf' loop here in this a=
lgorithm text.
                  if (intf.remote_node !=3D fail_intf.remote_node)
                      if ( D_opt(intf.remote_node, y) <
                           D_opt(intf.remote_node, self) +
                           D_opt(self,fail_intf.remote_node) +
                           D_opt(fail_intf.remote_node,y) )
                       y.in_extended_P_space =3D true

      /////////////////////////////////////////////////////////////////
      //
      // Compute the nodes in Q-space
      //

      Compute_Q_Space(fail_intf)
          // Compute the cost from every node the network to the
          // node normally reachable across the failed link
          Compute_and_Store_Reverse_SPF(fail_intf.remote_node)

          // Compute the cost from every node the network to self
          Compute_and_Store_Reverse_SPF(self)

          foreach node y in network
[Pushpasis] Again from definition of intf.remote_node, there maybe multiple=
 'remote_node's for a given 'fail_intf' (specially if the 'fail_intf' is a =
LAN intf. So there should be another 'foreach intf.remote_node in intf' loo=
p here in this algorithm text. Also there is a question of which 'remote_no=
de' will the below inequality be evaluated on in this case. This needs to b=
e clarified.
              if ( D_opt(y,fail_intf.remote_node) < D_opt(y,self) +
                      D_opt(self,fail_intf.remote_node) )
                  y.in_Q_space =3D true
              else
                  y.in_Q_space =3D false

      /////////////////////////////////////////////////////////////////
      //
      // Compute set of nodes in both extended P-space and in Q-space

      Intersect_Extended_P_and_Q_Space()
[Pushpasis] The PQ-space is a function of the 'fail_intf'. One node maybe P=
Q-node for one 'fail_intf' and still not be the PQ-node for another 'fail_i=
ntf'. So the 'fail_intf' should be a input parameter for this procedure. Al=
so the flags in_extended_P_space and in_Q_space for node y should be define=
d per 'fail_intf'.
          foreach node y in network
              if ( y.in_extended_P_space && y.in_Q_space )
                  y.valid_tunnel_endpoint =3D true
              else
                  y.valid_tunnel_endpoint =3D false

The current text needs to be enhanced and clarified with more details to ac=
hieve completeness in my opinion. Once again regret the late response.

Thanks
-Pushpasis

From: Alvaro Retana (aretana) [mailto:aretana@cisco.com]
Sent: Wednesday, December 04, 2013 7:06 PM
To: rtgwg@ietf.org
Cc: draft-ietf-rtgwg-remote-lfa@tools.ietf.org
Subject: WGLC for draft-ietf-rtgwg-remote-lfa

Hi!

After what I thought was a productive set of feedback and discussion relate=
d to this draft, both in the mailing list as well as at the meeting in Vanc=
ouver, I would like to start a Working Group Last Call.  This call will clo=
se by EOD (pick your favorite time zone) on December 19, 2013.

http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa

Please provide specific feedback as to why you support (or not) the advance=
ment of this draft.  Please avoid "+1"-type responses.

Thanks!

Alvaro.

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.mftr
	{mso-style-name:m_ftr;}
span.mhdr
	{mso-style-name:m_hdr;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=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">Hi Stewart/Alvaro,<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">It maybe a very late, but=
 I wanted to point the following issue with the algorithm/psuedocode text p=
rovided in section 4.3.<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:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ///////////////////////////=
//////////////////////////////////////<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; //<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Calculate extended P-spa=
ce<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; //<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Note the strictly less t=
han operator is needed to<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // avoid ECMP issues.<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Compute_Extended_P_Space(fa=
il_intf)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for=
each node y in network<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; y.in_extended_P_space =3D false<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; // Extend P-space to the P-spaces of all reachable<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; // neighbours<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; foreach interface intf in self<o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Courier New&quot;;color:red">[Pushpasis] From definition of intf.remote_no=
de, there maybe multiple &#8216;remote_node&#8217;s for a given &#8216;intf=
&#8217; (specially if the &#8216;intf&#8217; is a LAN intf. So there should=
 be another
 &#8216;foreach intf.remote_node in intf&#8217; loop here in this algorithm=
 text.<o:p></o:p></span></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (intf.remote_node !=3D fail=
_intf.remote_node)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if ( D=
_opt(intf.remote_node, y) &lt;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; D_opt(intf.remote_node, self) &#43;<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; D_opt(self,fail_intf.remote_node) &#43;<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; D_opt(fail_intf.remote_node,y) )<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
y.in_extended_P_space =3D true<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ///////////////////////////=
//////////////////////////////////////<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; //<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Compute the nodes in Q-s=
pace<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; //<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Compute_Q_Space(fail_intf)<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // =
Compute the cost from every node the network to the<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // =
node normally reachable across the failed link<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Com=
pute_and_Store_Reverse_SPF(fail_intf.remote_node)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // =
Compute the cost from every node the network to self<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Com=
pute_and_Store_Reverse_SPF(self)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for=
each node y in network<o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Courier New&quot;;color:red">[Pushpasis] Again from definition of intf.rem=
ote_node, there maybe multiple &#8216;remote_node&#8217;s for a given &#821=
6;fail_intf&#8217; (specially if the &#8216;fail_intf&#8217; is a LAN intf.=
 So there
 should be another &#8216;foreach intf.remote_node in intf&#8217; loop here=
 in this algorithm text. Also there is a question of which &#8216;remote_no=
de&#8217; will the below inequality be evaluated on in this case. This need=
s to be clarified.
<o:p></o:p></span></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;if ( D_opt(y,fail_intf.remote_node) &lt; D_opt(y,=
self) &#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D_opt(=
self,fail_intf.remote_node) )<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; y.in_Q_space =3D true<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; else<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; y.in_Q_space =3D false<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ///////////////////////////=
//////////////////////////////////////<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; //<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Compute set of nodes in =
both extended P-space and in Q-space<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Intersect_Extended_P_and_Q_=
Space()<o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Courier New&quot;;color:red">[Pushpasis] The PQ-space is a function of the=
 &#8216;fail_intf&#8217;. One node maybe PQ-node for one &#8216;fail_intf&#=
8217; and still not be the PQ-node for another &#8216;fail_intf&#8217;. So =
the &#8216;fail_intf&#8217;
 should be a input parameter for this procedure. Also the flags in_extended=
_P_space and in_Q_space for node y should be defined per &#8216;fail_intf&#=
8217;.<o:p></o:p></span></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for=
each node y in network<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; if ( y.in_extended_P_space &amp;&amp; y.in_Q_space )<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; y.valid_tunnel_endpoint =3D tr=
ue<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; else<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; y.valid_tunnel_endpoint =3D fa=
lse<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">The current text needs to=
 be enhanced and clarified with more details to achieve completeness in my =
opinion. Once again regret the late response.<o:p></o:p></span></p>
<p class=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">Thanks<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">-Pushpasis<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-=
size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"> Alvaro=
 Retana (aretana) [mailto:aretana@cisco.com]
<br>
<b>Sent:</b> Wednesday, December 04, 2013 7:06 PM<br>
<b>To:</b> rtgwg@ietf.org<br>
<b>Cc:</b> draft-ietf-rtgwg-remote-lfa@tools.ietf.org<br>
<b>Subject:</b> WGLC for draft-ietf-rtgwg-remote-lfa<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!<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">After what I thought was a =
productive set of feedback and discussion related to this draft, both in th=
e mailing list as well as at the meeting in Vancouver, I
 would like to start a Working Group Last Call. &nbsp;This call will close =
by EOD (pick your favorite time zone) on December 19, 2013.<o:p></o:p></spa=
n></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"><a href=3D"http://tools.iet=
f.org/html/draft-ietf-rtgwg-remote-lfa">http://tools.ietf.org/html/draft-ie=
tf-rtgwg-remote-lfa</a><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">Please provide specific fee=
dback as to why you support (or not) the advancement of this draft. &nbsp;P=
lease avoid &quot;&#43;1&quot;-type responses.<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">Thanks!<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">Alvaro.<o:p></o:p></span></=
p>
</div>
</div>
</body>
</html>

--_000_c043b7fae6fc4aba9c98bbaad5eab388BN1PR05MB520namprd05pro_--

From imc.shand@gmail.com  Thu Dec  5 07:45:45 2013
Return-Path: <imc.shand@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 61ED71AE07B for <rtgwg@ietfa.amsl.com>; Thu,  5 Dec 2013 07:45:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.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] 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 ozxMm9fNzP-g for <rtgwg@ietfa.amsl.com>; Thu,  5 Dec 2013 07:45:43 -0800 (PST)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 7EDF81AE074 for <rtgwg@ietf.org>; Thu,  5 Dec 2013 07:45:43 -0800 (PST)
Received: by mail-wg0-f46.google.com with SMTP id m15so16713920wgh.25 for <rtgwg@ietf.org>; Thu, 05 Dec 2013 07:45:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=070kA8lq6NuPRe7Eqmq7S5LEkFnBupbeC8Td+sdIchY=; b=Cz4nCOxefFlNjZ/MlOxfBAAi1OLhHsfU3fo6BQki5Z8+7PxJ+p2BYzQbB4HaMyuiwW 23z/E/zTBnSyb5XxRQsGJYsT+ATv0IRAWhJaYgh8bTFICANfkwaxgcQvpwd0wV4NiRzM Djr8bGKkF3D9Nfw0wVHwjwHu6jG2uclxLwSCZmE6JoWogFntaVI3xELa93hW6E1ELHl4 SNv11rG8QWeXgV6W2owTK1ffLVkMRRgfvavE9sUy3OESPurVIU6m/LdK7C9Wy2quwMNc 0Cu1oRFj3If5um3ChtO3t7mdrYtbIGtoJBEVazYSghIKqRxIHqRaz74RqLgmf6Q0sP2v avBQ==
X-Received: by 10.180.90.65 with SMTP id bu1mr12727632wib.15.1386258339532; Thu, 05 Dec 2013 07:45:39 -0800 (PST)
Received: from [192.168.2.183] (46-65-61-13.zone16.bethere.co.uk. [46.65.61.13]) by mx.google.com with ESMTPSA id d2sm7331563wik.11.2013.12.05.07.45.38 for <rtgwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 05 Dec 2013 07:45:39 -0800 (PST)
Message-ID: <52A09F9A.6080105@gmail.com>
Date: Thu, 05 Dec 2013 15:45:30 +0000
From: Mike Shand <imc.shand@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: rtgwg@ietf.org
Subject: Re: IPR Claims related to draft-ietf-rtgwg-remote-lfa
References: <CEC4C48C.4359C%aretana@cisco.com>
In-Reply-To: <CEC4C48C.4359C%aretana@cisco.com>
Content-Type: multipart/alternative; boundary="------------060702000907070908060005"
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, 05 Dec 2013 15:45:45 -0000

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

I am not aware of any IPR beyond that which has already been disclosed.

     Mike

On 04/12/2013 13:37, Alvaro Retana (aretana) wrote:
> Hi!
>
> In parallel to the WGLC for this draft, I want to formally ask the 
> authors (no additional contributors are listed in the latest version 
> of the draft) to please respond to this message indicating whether or 
> not you are aware of any relevant IPR beyond what has already been 
> disclosed.  The draft will not progress (pending the results of the 
> WGLC) until we have received a response from each author.
>
> Thanks!
>
> Alvaro.
>
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">I am not aware of any IPR beyond that
      which has already been disclosed.<br>
      <br>
      &nbsp;&nbsp;&nbsp; Mike<br>
      <br>
      On 04/12/2013 13:37, Alvaro Retana (aretana) wrote:<br>
    </div>
    <blockquote cite="mid:CEC4C48C.4359C%25aretana@cisco.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div>
        <div>Hi!</div>
        <div><br>
        </div>
        <div>In parallel to the WGLC for this draft,&nbsp;I want to formally
          ask the authors (no additional contributors are listed in the
          latest version of the draft) to please respond to this message
          indicating whether or not you are aware of any relevant IPR
          beyond what has already been disclosed. &nbsp;The draft will not
          progress (pending the results of the WGLC) until we have
          received a response from each author.</div>
        <div><br>
        </div>
        <div>Thanks!</div>
        <div><br>
        </div>
        <div>Alvaro.</div>
      </div>
      <div><br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
rtgwg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/rtgwg">https://www.ietf.org/mailman/listinfo/rtgwg</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------060702000907070908060005--

From Andras.Csaszar@ericsson.com  Thu Dec  5 12:48:29 2013
Return-Path: <Andras.Csaszar@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 DE5641AE180 for <rtgwg@ietfa.amsl.com>; Thu,  5 Dec 2013 12:48:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.939
X-Spam-Level: 
X-Spam-Status: No, score=-0.939 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 vh32GejI773Z for <rtgwg@ietfa.amsl.com>; Thu,  5 Dec 2013 12:48:26 -0800 (PST)
Received: from sesbmg21.mgmt.ericsson.se (sesbmg21.ericsson.net [193.180.251.49]) by ietfa.amsl.com (Postfix) with ESMTP id 9265F1AE1C8 for <rtgwg@ietf.org>; Thu,  5 Dec 2013 12:47:14 -0800 (PST)
X-AuditID: c1b4fb31-b7f118e000003145-56-52a0e64e6a1c
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg21.mgmt.ericsson.se (Symantec Mail Security) with SMTP id AB.7B.12613.E46E0A25; Thu,  5 Dec 2013 21:47:10 +0100 (CET)
Received: from ESESSMB103.ericsson.se ([169.254.3.33]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.02.0347.000; Thu, 5 Dec 2013 21:47:09 +0100
From: =?utf-8?B?QW5kcsOhcyBDc8Ohc3rDoXI=?= <Andras.Csaszar@ericsson.com>
To: Alia Atlas <akatlas@gmail.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>
Subject: RE: IRP Claims related to draft-enyedi-rtgwg-mrt-frr-algorithm
Thread-Topic: IRP Claims related to draft-enyedi-rtgwg-mrt-frr-algorithm
Thread-Index: AQHOxFQejz6lsVRV/UKb2dqFz2SbTpoBHruA///yaqyAACyNKIABkwWA///RR4CAQ8mZMA==
Date: Thu, 5 Dec 2013 20:47:09 +0000
Message-ID: <7B294AC32E078045B1F292CBA8FA23F61C4F5A16@ESESSMB103.ericsson.se>
References: <3nnp0tksa44ug1ke5bx53og3.1382472669658@email.android.com> <BBD66FD99311804F80324E8139B3C94E396B86EB@xmb-aln-x15.cisco.com> <CAG4d1reXpfXygSCViiHESOy184=fxZnfVb4vJHfcGAT9dO1ANg@mail.gmail.com>
In-Reply-To: <CAG4d1reXpfXygSCViiHESOy184=fxZnfVb4vJHfcGAT9dO1ANg@mail.gmail.com>
Accept-Language: hu-HU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: multipart/alternative; boundary="_000_7B294AC32E078045B1F292CBA8FA23F61C4F5A16ESESSMB103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprKIsWRmVeSWpSXmKPExsUyM+Jvra7fswVBBsv3iVp8eniJ2eLrtTSL vz+3Mlo8bjzPbnHhzW9mB1aPKb83snrsnHWX3WPJkp9MHtebrrJ7fLn8mS2ANYrLJiU1J7Ms tUjfLoErY+3yXUwFNzYxVrxt3MHYwPhjLWMXIyeHhICJRNviNmYIW0ziwr31bCC2kMAJRokH O8O6GLmA7EWMEie/PAZLsAl4SNy//hesQUQgWGL+7a+sIEXMAjsYJV51PmQFSQgLuEvc/nIb qshD4kzPSnYIO0xiTmMX2CAWARWJ9092g9XwCvhKzLzYzASx7QKjxJ1jP8DO4xQIlOiacRmo iIODUUBW4uFaC5Aws4C4xK0n85kgrhaQWLLnPNQHohIvH/9jhbCVJFZsv8QIUZ8v0bGvgx1i l6DEyZlPWCYwis5CMmoWkrJZSMpmAW1mFtCUWL9LH6JEUWJK90N2CFtDonXOXHZk8QWM7KsY JYtTi5Ny040M9XLTc0v0Uosyk4uL8/P0ilM3MQKj9uCW34Y7GCdesz/EKM3BoiTOyzC9M0hI ID2xJDU7NbUgtSi+qDQntfgQIxMHp1QD47oPho1PA8ou8qYyyz7wOGvUy5Oz4bBH2cq7B64Z W0lHB79RFORyDGB37D7/T2+51IoWjg2xr8MbYl6nZ6VkHfFd8UJriluRB4Pun1htFgdux4jV Nid+fau/4ttsuntj66nCtC9LtyWfUN8X2/yq7HyohcLUBa27QzSKZ4W+Wdtr/bz07kRhJZbi jERDLeai4kQAmpJXFqgCAAA=
Cc: "draft-enyedi-rtgwg-mrt-frr-algorithm@tools.ietf.org" <draft-enyedi-rtgwg-mrt-frr-algorithm@tools.ietf.org>, Alia Atlas <akatlas@juniper.net>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Dec 2013 20:48:30 -0000

--_000_7B294AC32E078045B1F292CBA8FA23F61C4F5A16ESESSMB103erics_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

RGVhciBBbGwsDQpTb3JyeSBmb3IgYSBsYXRlIHJlc3BvbnNlIHRvIHRoaXMuIFRoZSBJUFJzIGFy
ZSByZXBvcnRlZCB0byB0aGUgYXJjaGl0ZWN0dXJlIGRyYWZ0Lg0KSSBhZ3JlZSB3aXRoIEFsaWHi
gJlzIGNvbW1lbnQgb24gYiksIGMpIGFuZCBkKS4NCg0KQXMgZm9yIGEpIHRoZSBJUFIgSSBrbm93
IGFib3V0IGlzIGNsYWltaW5nIHRoZSB1c2FnZSBvZiBvbmUgb2YgdGhlIHJlZHVuZGFudCB0cmVl
cyBpbiBjYXNlIG9mIGZhaWx1cmVzLCBidXQgdG8gdGhlIGJlc3Qgb2YgbXkgdW5kZXJzdGFuZGlu
ZyBkb2VzIG5vdCBjbGFpbSB0aGUgTVJUIGNhbGN1bGF0aW9uIGFsZ29yaXRobXMgZGVzY3JpYmVk
IGluIGRyYWZ0LWVueWVkaS1ydGd3Zy1tcnQtZnJyLWFsZ29yaXRobS4gKFNvLCB0byBtZSwgaXQg
aXMgbW9yZSByZWxhdGVkIHRvIHRoZSBhcmNoaXRlY3R1cmUgZHJhZnQuKQ0KDQpBbmRyw6FzDQoN
CkZyb206IHJ0Z3dnLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpydGd3Zy1ib3VuY2VzQGlldGYu
b3JnXSBPbiBCZWhhbGYgT2YgQWxpYSBBdGxhcw0KU2VudDogMjAxMy4gb2t0w7NiZXIgMjMuIDIx
OjI5DQpUbzogQWx2YXJvIFJldGFuYSAoYXJldGFuYSkNCkNjOiBkcmFmdC1lbnllZGktcnRnd2ct
bXJ0LWZyci1hbGdvcml0aG1AdG9vbHMuaWV0Zi5vcmc7IEFsaWEgQXRsYXM7IHJ0Z3dnQGlldGYu
b3JnDQpTdWJqZWN0OiBSZTogSVJQIENsYWltcyByZWxhdGVkIHRvIGRyYWZ0LWVueWVkaS1ydGd3
Zy1tcnQtZnJyLWFsZ29yaXRobQ0KDQpbV0cgQ2hhaXIgSGF0IG9mZl0NCg0KSGkgQWx2YXJvLA0K
DQpUbyBteSBrbm93bGVkZ2UsIHRoZXJlIGFyZSB2YXJpb3VzIElQUiBjbGFpbXMgb24gdGhlIGFy
Y2hpdGVjdHVyZSBkcmFmdC4gIE9idmlvdXNseSwgcGVvcGxlIG11c3QgcmVhZCB0aGUgdmFyaW91
cw0KSVBSIGNsYWltcyBhbmRpIG1ha2UgdGhlaXIgb3duIGRlY2lzaW9ucy4NCg0KYSkgT24gdXNp
bmcgdGhlIE1SVCBhbGdvcml0aG0gZm9yIGZhc3QtcmVyb3V0ZSB3aXRoIHRyeWluZyBNUlQtQkxV
RSBhbmQgZ29pbmcgdG8gTVJULVJFRCBpZiB0aGF0IGZhaWxzLiAgKEluaXRpYWwgYXBwcm9hY2gN
CiAgICBpbiB0aGUgZmlyc3QgdmVyc2lvbnMgb2YgdGhlIGRyYWZ0KS4NCmIpIE1SVCBmb3J3YXJk
aW5nIGVuY2Fwc3VsYXRpb25zDQpjKSBQYXJ0aWFsIGRlcGxveW1lbnQgY29tcHV0YXRpb25zIGZv
ciBNUlQtRlJSIC0gYnV0IHRoZSBwYXJ0IGluIHRoZSBhbGdvcml0aG0gZHJhZnQgaXMganVzdCBh
IHNpbXBsaWZpY2F0aW9uIG9mIHRoZSBNUlQgYWxnb3JpdGhtDQogICAgc28gaXQgY2FuIGJlIGNh
bGxlZC4NCmQpIFZhcmlvdXMgbXVsdGljYXN0LXJlbGF0ZWQgYXNwZWN0cy4NCg0KZHJhZnQtZW55
ZWRpLXJ0Z3dnLW1ydC1hbGdvcml0aG0gaXMgYmFzZWQgb24gR2Fib3IncyBkaXNzZXJ0YXRpb24g
d29yay4gIFRoZSBleHRlbnNpb25zIHRvIHRoYXQgZm9yIGNvbXB1dGluZyB3aGljaCBNUlQgdG8g
dXNlDQpmb3IgYW4gYWx0ZXJuYXRlIHdlcmUgZGV2ZWxvcGVkIGpvaW50bHkgaW4gdGhlIElFVEYg
Y29udGV4dC4NCg0KSSBkb24ndCBiZWxpZXZlIHRoYXQgKGIpLCAoYyksIG9yIChkKSBhcHBseSB0
byB0aGUgYWxnb3JpdGhtIGRyYWZ0LiAgQW5kcmFzIGFuZCBHYWJvciBjYW4gYW5zd2VyIG1vcmUg
d2hldGhlciB0aGV5IHRoaW5rIHRoYXQgKGEpDQphcHBsaWVzLg0KDQpBbGlhDQoNCk9uIFdlZCwg
T2N0IDIzLCAyMDEzIGF0IDM6MTYgUE0sIEFsdmFybyBSZXRhbmEgKGFyZXRhbmEpIDxhcmV0YW5h
QGNpc2NvLmNvbTxtYWlsdG86YXJldGFuYUBjaXNjby5jb20+PiB3cm90ZToNCk9uIDEwLzIyLzEz
IDQ6MTMgUE0sICJHw6Fib3IgU8OhbmRvciBFbnllZGkiIDxnYWJvci5zYW5kb3IuZW55ZWRpQGVy
aWNzc29uLmNvbTxtYWlsdG86Z2Fib3Iuc2FuZG9yLmVueWVkaUBlcmljc3Nvbi5jb20+PiB3cm90
ZToNCg0KW1dHIENoYWlyIEhhdCBPZmZdDQoNCkdhYm9yIChhbmQgQW5kcmFzLCBhbmQgQWxpYSBh
bmQgQ2hyaXMpOg0KDQoNCg0KSSBkb24ndCBrbm93IGFib3V0IGFueSBJUFIgLiAuIC4gaGlzIGRy
YWZ0IGlzIG9ubHkgZGVzY3JpYmluZyBhbGdvcml0aG1zLg0KSXQncyBpbnRlcmVzdGluZyB0byBt
ZSB0aGF0IHRoZXJlIGFyZSBJUFIgZGlzY2xvc3VyZXMgKGZyb20gYm90aCBFcmljc3NvbiBhbmQg
SnVuaXBlcikgYXR0YWNoZWQgdG8gdGhlIGFyY2hpdGVjdHVyZSBkcmFmdCwgYnV0IG5vdCB0byB0
aGlzIGRyYWZ0Lg0KDQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2lwci9zZWFyY2gvP29w
dGlvbj1kb2N1bWVudF9zZWFyY2gmZG9jdW1lbnRfc2VhcmNoPWRyYWZ0LWlldGYtcnRnd2ctbXJ0
LWZyci1hcmNoaXRlY3R1cmUNCg0KDQpJIHdvdWxkIGhhdmUgdGhvdWdodCB0aGF0IHRoZSBJUFIg
d291bGQgYmUgYXR0YWNoZWQgaGVyZSAoaW4gdGhlIGFsZ29yaXRobSBkcmFmdCkgc2luY2UgaXQg
cHJvdmlkZXMgdGhlIGRldGFpbHMgb2YgaG93IHRoZSBhcmNoaXRlY3R1cmUgY2FuIGJlIGltcGxl
bWVudGVkLg0KDQpHaXZlbiB0aGUgZGlzY3Vzc2lvbiAoaW4gdGhlIHRocmVhZCB3aGVyZSBJIG1h
ZGUgc29tZSBjb21tZW50cyB0byB0aGUgYWxnb3JpdGhtIGRyYWZ0KSBhYm91dCB3aGVyZSB0aGUg
bGltaXRzIG9mIHRoZSBhbGdvcml0aG0gdnMgdGhlIHByb2ZpbGUgYXJlLCBhbmQgd2hldGhlciBv
bmUgaXMgcGFydCBvZiB0aGUgb3RoZXIgb3Igbm90LCBpdCBzdXJwcmlzZXMgbWUgdGhhdCBubyBv
bmUgaGFzIGNsYWltZWQgYW55IElQUiBvbiB0aGlzIGRyYWZ0OiB0aGVyZSBzZWVtcyB0byBiZSBz
aWduaWZpY2FudCBsZWFrYWdlIGFuZCBvdmVybGFwICBiZXR3ZWVuIHdoYXQncyBpbiB0aGUgYXJj
aGl0ZWN0dXJlIGFuZCBob3cgdGhlIGFsZ29yaXRobSBvcGVyYXRlcy4gIEluIG15IG1pbmQsIHRo
YXQgZWl0aGVyIG1lYW5zIHRoYXQgdGhlIGNsYWltcyBvdmVyIHRoZSBhcmNoaXRlY3R1cmUgYXJl
IHZlcnkgbmFycm93LCBvciB0aGF0IHNvbWV0aGluZyBzaG91bGQgYmUgZGVjbGFyZWQgZm9yIHRo
ZSBhbGdvcml0aG0uDQoNCkl0IHdvdWxkIGJlIG5pY2UgaWYgeW91IGNoZWNrZWQgYWdhaW4gYWJv
dXQgdGhlIG92ZXJsYXAsIG9yIGlmIHlvdSBjbGFyaWZpZWQgd2hhdCBzcGVjaWZpY2FsbHkgaXMg
Y292ZXJlZCBpbiB0aGUgYXJjaGl0ZWN0dXJlIGRyYWZ0LiAgT2YgY29uY2VybiB0byBtZSBhcmUg
dGhlIHRlcm1zIGZyb20gRXJpY3Nzb24gKCJSZWFzb25hYmxlIGFuZCBOb24tRGlzY3JpbWluYXRv
cnkgTGljZW5zZSB0byBBbGwgSW1wbGVtZW50ZXJzIHdpdGggUG9zc2libGUgUm95YWx0eS9GZWUu
IikuICBJIHJlYWxpemUgdGhhdCBpdCBpcyBvdXQgb2YgdGhlIHNjb3BlIG9mIHRoZSBXRyB0byB0
YWxrIGFib3V0IHRoZSBhcHBsaWNhYmlsaXR5IG9mIHRlcm1zLCBidXQgdGhpcyBpcyBub3QgdGhl
IGZpcnN0IHRpbWUgdGhhdCB0aGlzIHRvcGljIGNvbWVzIHVwOyB0YWtlIGEgbG9vayBhdCB0aGUg
bWludXRlcyBmcm9tIElFVEYgODI6ICBodHRwOi8vd3d3LmlldGYub3JnL3Byb2NlZWRpbmdzLzgy
L21pbnV0ZXMvcnRnd2cudHh0DQoNClRoYW5rcyENCg0KQWx2YXJvLg0KDQpfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KcnRnd2cgbWFpbGluZyBsaXN0DQpy
dGd3Z0BpZXRmLm9yZzxtYWlsdG86cnRnd2dAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3J0Z3dnDQoNCg==

--_000_7B294AC32E078045B1F292CBA8FA23F61C4F5A16ESESSMB103erics_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIg
MiA0IDMgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNv
Tm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAw
MXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIs
InNlcmlmIjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0
eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNp
dGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsN
Cgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwcmUNCgl7bXNv
LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCBD
aGFyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6
MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0Kc3Bhbi5IVE1MUHJlZm9ybWF0
dGVkQ2hhcg0KCXttc28tc3R5bGUtbmFtZToiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbXNv
LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCI7
DQoJZm9udC1mYW1pbHk6Q29uc29sYXM7DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6SFU7fQ0Kc3Bh
bi5ob2VuemINCgl7bXNvLXN0eWxlLW5hbWU6aG9lbnpiO30NCnNwYW4uRW1haWxTdHlsZTIwDQoJ
e21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwi
c2Fucy1zZXJpZiI7DQoJY29sb3I6Z3JlZW47fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxl
LXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsN
Cgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6
ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9
DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEt
LVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlk
bWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+
DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0
YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxi
b2R5IGxhbmc9IkhVIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9Ildv
cmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1HQiIgc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmdyZWVuIj5EZWFyIEFsbCw8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1HQiIgc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7O2NvbG9yOmdyZWVuIj5Tb3JyeSBmb3IgYSBsYXRlIHJlc3BvbnNlIHRvIHRo
aXMuIFRoZSBJUFJzIGFyZSByZXBvcnRlZCB0byB0aGUgYXJjaGl0ZWN0dXJlIGRyYWZ0LjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLUdC
IiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6Z3JlZW4iPkkgYWdyZWUgd2l0aCBBbGlh4oCZ
cyBjb21tZW50IG9uIGIpLCBjKSBhbmQgZCkuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tR0IiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztj
b2xvcjpncmVlbiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tR0IiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpncmVl
biI+QXMgZm9yIGEpIHRoZSBJUFIgSSBrbm93IGFib3V0IGlzIGNsYWltaW5nIHRoZSB1c2FnZSBv
ZiBvbmUgb2YgdGhlIHJlZHVuZGFudCB0cmVlcyBpbiBjYXNlIG9mIGZhaWx1cmVzLCBidXQgdG8g
dGhlIGJlc3Qgb2YgbXkgdW5kZXJzdGFuZGluZyBkb2VzDQogbm90IGNsYWltIHRoZSBNUlQgY2Fs
Y3VsYXRpb24gYWxnb3JpdGhtcyBkZXNjcmliZWQgaW4gZHJhZnQtZW55ZWRpLXJ0Z3dnLW1ydC1m
cnItYWxnb3JpdGhtLiAoU28sIHRvIG1lLCBpdCBpcyBtb3JlIHJlbGF0ZWQgdG8gdGhlIGFyY2hp
dGVjdHVyZSBkcmFmdC4pPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRU4tR0IiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpncmVlbiI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmdyZWVuIj5BbmRyw6FzPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
O2NvbG9yOmdyZWVuIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJi
b3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAw
Y20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29s
aWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJv
bTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IHJ0
Z3dnLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpydGd3Zy1ib3VuY2VzQGlldGYub3JnXQ0KPGI+
T24gQmVoYWxmIE9mIDwvYj5BbGlhIEF0bGFzPGJyPg0KPGI+U2VudDo8L2I+IDIwMTMuIG9rdMOz
YmVyIDIzLiAyMToyOTxicj4NCjxiPlRvOjwvYj4gQWx2YXJvIFJldGFuYSAoYXJldGFuYSk8YnI+
DQo8Yj5DYzo8L2I+IGRyYWZ0LWVueWVkaS1ydGd3Zy1tcnQtZnJyLWFsZ29yaXRobUB0b29scy5p
ZXRmLm9yZzsgQWxpYSBBdGxhczsgcnRnd2dAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4g
UmU6IElSUCBDbGFpbXMgcmVsYXRlZCB0byBkcmFmdC1lbnllZGktcnRnd2ctbXJ0LWZyci1hbGdv
cml0aG08bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPltXRyBDaGFpciBIYXQgb2ZmXTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPkhpIEFsdmFybyw8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPlRvIG15IGtub3dsZWRnZSwgdGhlcmUgYXJlIHZhcmlvdXMgSVBS
IGNsYWltcyBvbiB0aGUgYXJjaGl0ZWN0dXJlIGRyYWZ0LiAmbmJzcDtPYnZpb3VzbHksIHBlb3Bs
ZSBtdXN0IHJlYWQgdGhlIHZhcmlvdXM8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPklQUiBjbGFpbXMgYW5kaSBtYWtlIHRoZWlyIG93biBkZWNpc2lv
bnMuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PmEpIE9uIHVzaW5nIHRoZSBNUlQgYWxnb3JpdGhtIGZvciBmYXN0LXJlcm91dGUgd2l0aCB0cnlp
bmcgTVJULUJMVUUgYW5kIGdvaW5nIHRvIE1SVC1SRUQgaWYgdGhhdCBmYWlscy4gJm5ic3A7KElu
aXRpYWwgYXBwcm9hY2g8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPiZuYnNwOyAmbmJzcDsgaW4gdGhlIGZpcnN0IHZlcnNpb25zIG9mIHRoZSBkcmFm
dCkuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5i
KSBNUlQgZm9yd2FyZGluZyBlbmNhcHN1bGF0aW9uczxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+YykgUGFydGlhbCBkZXBsb3ltZW50IGNvbXB1dGF0
aW9ucyBmb3IgTVJULUZSUiAtIGJ1dCB0aGUgcGFydCBpbiB0aGUgYWxnb3JpdGhtIGRyYWZ0IGlz
IGp1c3QgYSBzaW1wbGlmaWNhdGlvbiBvZiB0aGUgTVJUIGFsZ29yaXRobTxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwOyBzbyBp
dCBjYW4gYmUgY2FsbGVkLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+ZCkgVmFyaW91cyBtdWx0aWNhc3QtcmVsYXRlZCBhc3BlY3RzLjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5kcmFmdC1lbnll
ZGktcnRnd2ctbXJ0LWFsZ29yaXRobSBpcyBiYXNlZCBvbiBHYWJvcidzIGRpc3NlcnRhdGlvbiB3
b3JrLiAmbmJzcDtUaGUgZXh0ZW5zaW9ucyB0byB0aGF0IGZvciBjb21wdXRpbmcgd2hpY2ggTVJU
IHRvIHVzZTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+Zm9yIGFuIGFsdGVybmF0ZSB3ZXJlIGRldmVsb3BlZCBqb2ludGx5IGluIHRoZSBJRVRGIGNv
bnRleHQuICZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5JIGRvbid0IGJlbGlldmUgdGhhdCAoYiksIChjKSwgb3IgKGQpIGFwcGx5IHRv
IHRoZSBhbGdvcml0aG0gZHJhZnQuICZuYnNwO0FuZHJhcyBhbmQgR2Fib3IgY2FuIGFuc3dlciBt
b3JlIHdoZXRoZXIgdGhleSB0aGluayB0aGF0IChhKTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+YXBwbGllcy4mbmJzcDs8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QWxpYTxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFy
Z2luLWJvdHRvbToxMi4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPk9uIFdlZCwgT2N0IDIzLCAyMDEzIGF0IDM6MTYgUE0sIEFsdmFybyBSZXRh
bmEgKGFyZXRhbmEpICZsdDs8YSBocmVmPSJtYWlsdG86YXJldGFuYUBjaXNjby5jb20iIHRhcmdl
dD0iX2JsYW5rIj5hcmV0YW5hQGNpc2NvLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9w
Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2Vy
aWYmcXVvdDsiPk9uIDEwLzIyLzEzIDQ6MTMgUE0sICZxdW90O0fDoWJvciBTw6FuZG9yIEVueWVk
aSZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmdhYm9yLnNhbmRvci5lbnllZGlAZXJpY3Nzb24u
Y29tIiB0YXJnZXQ9Il9ibGFuayI+Z2Fib3Iuc2FuZG9yLmVueWVkaUBlcmljc3Nvbi5jb208L2E+
Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+W1dHIENoYWlyIEhhdCBPZmZdPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkdh
Ym9yIChhbmQgQW5kcmFzLCBhbmQgQWxpYSBhbmQgQ2hyaXMpOjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNv
bGlkICNCNUM0REYgNC41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdDttYXJnaW4tbGVmdDoz
Ljc1cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8cHJlIHN0eWxlPSJ0ZXh0LWFsaWduOi13ZWJraXQt
YXV0bzt3b3JkLXdyYXA6YnJlYWstd29yZDt3b3JkLXNwYWNpbmc6MHB4Ij48c3BhbiBzdHlsZT0i
Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkkgZG9uJ3Qga25v
dyBhYm91dCBhbnkgSVBSIC4gLiAuIGhpcyBkcmFmdCBpcyBvbmx5IGRlc2NyaWJpbmcgYWxnb3Jp
dGhtcy48bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkl0J3MgaW50ZXJl
c3RpbmcgdG8gbWUgdGhhdCB0aGVyZSBhcmUgSVBSIGRpc2Nsb3N1cmVzIChmcm9tIGJvdGggRXJp
Y3Nzb24gYW5kIEp1bmlwZXIpIGF0dGFjaGVkIHRvIHRoZSBhcmNoaXRlY3R1cmUgZHJhZnQsIGJ1
dCBub3QgdG8gdGhpcyBkcmFmdC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJh
Y2tlci5pZXRmLm9yZy9pcHIvc2VhcmNoLz9vcHRpb249ZG9jdW1lbnRfc2VhcmNoJmFtcDtkb2N1
bWVudF9zZWFyY2g9ZHJhZnQtaWV0Zi1ydGd3Zy1tcnQtZnJyLWFyY2hpdGVjdHVyZSIgdGFyZ2V0
PSJfYmxhbmsiPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvaXByL3NlYXJjaC8/b3B0aW9u
PWRvY3VtZW50X3NlYXJjaCZhbXA7ZG9jdW1lbnRfc2VhcmNoPWRyYWZ0LWlldGYtcnRnd2ctbXJ0
LWZyci1hcmNoaXRlY3R1cmU8L2E+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90OyI+SSB3b3VsZCBoYXZlIHRob3VnaHQgdGhhdCB0aGUgSVBSIHdvdWxkIGJl
IGF0dGFjaGVkIGhlcmUgKGluIHRoZSBhbGdvcml0aG0gZHJhZnQpIHNpbmNlIGl0IHByb3ZpZGVz
IHRoZSBkZXRhaWxzIG9mIGhvdyB0aGUgYXJjaGl0ZWN0dXJlIGNhbiBiZSBpbXBsZW1lbnRlZC48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90OyI+R2l2ZW4gdGhlIGRpc2N1c3Npb24gKGluIHRoZSB0aHJlYWQgd2hlcmUgSSBt
YWRlIHNvbWUgY29tbWVudHMgdG8gdGhlIGFsZ29yaXRobSBkcmFmdCkgYWJvdXQgd2hlcmUgdGhl
IGxpbWl0cyBvZiB0aGUgYWxnb3JpdGhtIHZzIHRoZSBwcm9maWxlIGFyZSwgYW5kIHdoZXRoZXIg
b25lIGlzIHBhcnQNCiBvZiB0aGUgb3RoZXIgb3Igbm90LCBpdCBzdXJwcmlzZXMgbWUgdGhhdCBu
byBvbmUgaGFzIGNsYWltZWQgYW55IElQUiBvbiB0aGlzIGRyYWZ0OiB0aGVyZSBzZWVtcyB0byBi
ZSBzaWduaWZpY2FudCBsZWFrYWdlIGFuZCBvdmVybGFwICZuYnNwO2JldHdlZW4gd2hhdCdzIGlu
IHRoZSBhcmNoaXRlY3R1cmUgYW5kIGhvdyB0aGUgYWxnb3JpdGhtIG9wZXJhdGVzLiAmbmJzcDtJ
biBteSBtaW5kLCB0aGF0IGVpdGhlciBtZWFucyB0aGF0IHRoZSBjbGFpbXMgb3ZlciB0aGUNCiBh
cmNoaXRlY3R1cmUgYXJlIDxiPnZlcnk8L2I+IG5hcnJvdywgb3IgdGhhdCBzb21ldGhpbmcgc2hv
dWxkIGJlIGRlY2xhcmVkIGZvciB0aGUgYWxnb3JpdGhtLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5JdCB3b3VsZCBi
ZSBuaWNlIGlmIHlvdSBjaGVja2VkIGFnYWluIGFib3V0IHRoZSBvdmVybGFwLCBvciBpZiB5b3Ug
Y2xhcmlmaWVkIHdoYXQgc3BlY2lmaWNhbGx5IGlzIGNvdmVyZWQgaW4gdGhlIGFyY2hpdGVjdHVy
ZSBkcmFmdC4gJm5ic3A7T2YgY29uY2VybiB0byBtZSBhcmUgdGhlIHRlcm1zIGZyb20NCiBFcmlj
c3NvbiAoJnF1b3Q7UmVhc29uYWJsZSBhbmQgTm9uLURpc2NyaW1pbmF0b3J5IExpY2Vuc2UgdG8g
QWxsIEltcGxlbWVudGVycyB3aXRoIFBvc3NpYmxlIFJveWFsdHkvRmVlLiZxdW90OykuICZuYnNw
O0kgcmVhbGl6ZSB0aGF0IGl0IGlzIG91dCBvZiB0aGUgc2NvcGUgb2YgdGhlIFdHIHRvIHRhbGsg
YWJvdXQgdGhlIGFwcGxpY2FiaWxpdHkgb2YgdGVybXMsIGJ1dCB0aGlzIGlzIG5vdCB0aGUgZmly
c3QgdGltZSB0aGF0IHRoaXMgdG9waWMgY29tZXMgdXA7IHRha2UNCiBhIGxvb2sgYXQgdGhlIG1p
bnV0ZXMgZnJvbSBJRVRGIDgyOiAmbmJzcDs8YSBocmVmPSJodHRwOi8vd3d3LmlldGYub3JnL3By
b2NlZWRpbmdzLzgyL21pbnV0ZXMvcnRnd2cudHh0IiB0YXJnZXQ9Il9ibGFuayI+aHR0cDovL3d3
dy5pZXRmLm9yZy9wcm9jZWVkaW5ncy84Mi9taW51dGVzL3J0Z3dnLnR4dDwvYT48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
NXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
OyI+VGhhbmtzITxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojODg4ODg4Ij48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6Izg4ODg4OCI+QWx2YXJv
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxicj4NCl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KcnRnd2cgbWFpbGluZyBsaXN0PGJy
Pg0KPGEgaHJlZj0ibWFpbHRvOnJ0Z3dnQGlldGYub3JnIj5ydGd3Z0BpZXRmLm9yZzwvYT48YnI+
DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3J0Z3dnIiB0
YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9ydGd3
ZzwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+
DQo=

--_000_7B294AC32E078045B1F292CBA8FA23F61C4F5A16ESESSMB103erics_--

From stbryant@cisco.com  Fri Dec  6 04:09:43 2013
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90A1F1ADED8 for <rtgwg@ietfa.amsl.com>; Fri,  6 Dec 2013 04:09:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.501
X-Spam-Level: 
X-Spam-Status: No, score=-9.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RFnMH9_ayJeR for <rtgwg@ietfa.amsl.com>; Fri,  6 Dec 2013 04:09:42 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id CF5A51ADF6B for <rtgwg@ietf.org>; Fri,  6 Dec 2013 04:09:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3267; q=dns/txt; s=iport; t=1386331778; x=1387541378; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=AZZDHWPvIs24tkGm/1mgyqY0Wx8MNQvudGZBEiSjuZU=; b=lwaRyNjM5VE/xpX3tkOkJ6Xb/e27yEBR+xBH1UHBtmYDwCF/vPwTSWR1 7G0xFbUU98h2xC8c1kFKGHjV0D0io+xYRuGjcGL7eTl3iQ3910iw9F9W0 XSz02YwTIScFZNVxduA1tf4JCmaUTWdDomtpIDy4ViaqkSFOyN4Mo7pnd M=;
X-IronPort-AV: E=Sophos;i="4.93,840,1378857600"; d="scan'208,217";a="1172087"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-2.cisco.com with ESMTP; 06 Dec 2013 12:09:37 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rB6C9YdT029626 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Dec 2013 12:09:34 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id rB6C9XSV005500; Fri, 6 Dec 2013 12:09:33 GMT
Message-ID: <52A1BE7D.8080805@cisco.com>
Date: Fri, 06 Dec 2013 12:09:33 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "draft-ietf-rtgwg-remote-lfa@tools.ietf.org" <draft-ietf-rtgwg-remote-lfa@tools.ietf.org>
Subject: Re: IPR Claims related to draft-ietf-rtgwg-remote-lfa
References: <CEC4C48C.4359C%aretana@cisco.com>
In-Reply-To: <CEC4C48C.4359C%aretana@cisco.com>
Content-Type: multipart/alternative; boundary="------------050902020408030503090402"
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Dec 2013 12:09:43 -0000

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

I have declared everything that I can think of that applies
to this draft.

Stewart

On 04/12/2013 13:37, Alvaro Retana (aretana) wrote:
> Hi!
>
> In parallel to the WGLC for this draft, I want to formally ask the 
> authors (no additional contributors are listed in the latest version 
> of the draft) to please respond to this message indicating whether or 
> not you are aware of any relevant IPR beyond what has already been 
> disclosed.  The draft will not progress (pending the results of the 
> WGLC) until we have received a response from each author.
>
> Thanks!
>
> Alvaro.
>
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


-- 
For corporate legal information go to:

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


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">I have declared everything that I can
      think of that applies<br>
      to this draft.<br>
      <br>
      Stewart<br>
      <br>
      On 04/12/2013 13:37, Alvaro Retana (aretana) wrote:<br>
    </div>
    <blockquote cite="mid:CEC4C48C.4359C%25aretana@cisco.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div>
        <div>Hi!</div>
        <div><br>
        </div>
        <div>In parallel to the WGLC for this draft,&nbsp;I want to formally
          ask the authors (no additional contributors are listed in the
          latest version of the draft) to please respond to this message
          indicating whether or not you are aware of any relevant IPR
          beyond what has already been disclosed. &nbsp;The draft will not
          progress (pending the results of the WGLC) until we have
          received a response from each author.</div>
        <div><br>
        </div>
        <div>Thanks!</div>
        <div><br>
        </div>
        <div>Alvaro.</div>
      </div>
      <div><br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
rtgwg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/rtgwg">https://www.ietf.org/mailman/listinfo/rtgwg</a>
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

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

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

--------------050902020408030503090402--

From akatlas@gmail.com  Fri Dec  6 15:03:17 2013
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 838601AE108 for <rtgwg@ietfa.amsl.com>; Fri,  6 Dec 2013 15:03:17 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=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 GJ0-Uqq1WM-O for <rtgwg@ietfa.amsl.com>; Fri,  6 Dec 2013 15:03:13 -0800 (PST)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 37B8E1AE0EA for <rtgwg@ietf.org>; Fri,  6 Dec 2013 15:03:13 -0800 (PST)
Received: by mail-ie0-f177.google.com with SMTP id tp5so2370957ieb.8 for <rtgwg@ietf.org>; Fri, 06 Dec 2013 15:03:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7sKcQ3lJseYvzWiN8lx5k+4prYnQsol/i+E6lRrFzM0=; b=C3xxYfB1/1EhkFYHvLHSK4FqV4NNdEou+BJ4RR7tU5lPu6f29CvcGfFEix/YAzpfo9 rlUkZ8s95G0afyTvje5gx0PrXPuUBSoD5Py7VDQLrqPpRr1luU8CoEqtoWfqR9VXgx2L q0ex8QvXm/AGYML7hfAcReqduDoMMJZnmlsjgMfq2VCQqpqg+eJ4BaQ+z/JuXNY/71Sy puOeULM+CW0qLjpi1j2rx34ncA+li8QIFuH0qsf4tJecClO0Dn9PAWxqFcFyAYEFywTC CRsN7Zxq1yCAaVjC6+HVimtB6NcYOy157iKa/r7Lh1DKjE1o8vuY+73JgHJGzYVIN3mL dFew==
MIME-Version: 1.0
X-Received: by 10.50.40.102 with SMTP id w6mr5119025igk.20.1386370989227; Fri, 06 Dec 2013 15:03:09 -0800 (PST)
Received: by 10.64.78.103 with HTTP; Fri, 6 Dec 2013 15:03:09 -0800 (PST)
In-Reply-To: <CEC4C406.43593%aretana@cisco.com>
References: <CEC4C406.43593%aretana@cisco.com>
Date: Fri, 6 Dec 2013 18:03:09 -0500
Message-ID: <CAG4d1rdnhaNgtJ8H9YpTSjg8u+3qF3SKkppzs2GM09e3cHMsWg@mail.gmail.com>
Subject: Re: WGLC for draft-ietf-rtgwg-remote-lfa
From: Alia Atlas <akatlas@gmail.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Content-Type: multipart/alternative; boundary=089e0112c7fe57053c04ece5a610
Cc: "draft-ietf-rtgwg-remote-lfa@tools.ietf.org" <draft-ietf-rtgwg-remote-lfa@tools.ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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 Dec 2013 23:03:17 -0000

--089e0112c7fe57053c04ece5a610
Content-Type: text/plain; charset=ISO-8859-1

I've given this draft a thorough reading (except for commenting on the
cost-based algorithm that Pushpasis already gave feedback on).

I have two major concerns.  First, I see no discussion at all about how
multipoint interfaces are handled.  Nothing indicates that they are out of
scope for protection nor does the discussion describe how to handle
avoiding the pseudo-nodes or related computation.  Second, as a
standards-track document, I see almost no description of what MUST or even
SHOULD be implemented.  What would conformance mean?

Here are my detailed comments - in going through the draft order, not by
priority.

0)Sec 2: Can you add a paragraph describing the extended-P space and
Q-space for the example in Figure 2?  It's fine to have the
definitions, but it is jarring to run into Q-space in Sec 4 without
any other reference.  For instance, just adding:

"In [Figure 1], S can reach A, B, and C without going via E; these
form S's extended P-space.  The routers that can reach E without going
through S-E will be E's Q-space; these are D and C.  B has equal-cost
paths via B-A-S-E and B-C-D-E and so may go through S-E.  The single
node in both S's P-space and E's Q-space is C; thus node C is selected
as the repair tunnel's end-point.  For more details on the reasoning
behind these calculations, please see [Sec 4.2]"

1) Sec 3, 2nd paragraph, 1 sentence:
  "A tunneled repair path tunnels traffic to some staging point in the
   network from which it is assumed that, in the absence of multiple
   failures, it will travel to its destination using normal forwarding
   without looping back."

First, can you replace "assumed" with precalculated or the like?  This
isn't an assumption - it is based on shortest-path forwarding and is
carefully determined.

Second, "in the absence of multiple failures" should be "in the
absence of a worse failure (e.g. node or SRLG) or multiple failures".

2) Sec 3.1: For clarity, could you add a sentence indicating that the
tunnel itself must also avoid going over the link S-E?

3) Sec 3.2, 2nd paragraph:  "In order for S to obtain
   the correct inner label it is necessary to establish a directed LDP
   session[RFC5036] to the tunnel end point."

Shouldn't that be a "targeted LDP session"?  I don't see directed at
all in RFC5036 and am personally only familiar with them being called
targeted LDP sessions.

4) Sec 3.2 3rd paragraph: "The performance of the encapsulation and
decapsulation is efficient as encapsulation is just a push of one
label (like conventional MPLS TE FRR) and the decapsulation occurs
naturally at the penultimate hop before the repair tunnel endpoint."

Decapsulation can occur at the penultimate hop, if the repair tunnel
endpoint so specifies.

5) Sec 3.2 3rd paragraph: "The time to establish the TLDP session and
acquire labels will limit the speed at which a new tunnel can be put
into service, but this will not be a problem in normal operation."

Can you please put some justification as to why this will not be a
problem in normal operation?  Is your assumption that the added delay
before the network is fully repaired acceptable because failure
analysis studies indicate the separation between failures is generally
at least X seconds and the time to establish a TLDP session and
exchange labels (how many) is no more than Y seconds (in a router that
is also dealing with reconvergence of all protocols beyond the IGP)?

The extra communication clearly adds some delay before protection is
available and a blanket assertion that it doesn't matter is more
marketing than engineering.

6) Given that this is a standards-track draft, is there a reason that
a minimum-to-implement tunnel type isn't specified?  I don't see/know
of any references for how a router can know if a remote router can
decapsulate IP-in-IP at speed or support GRE or even support a tLDP
session.

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

8) Sec 4.2.1, 2nd paragraph: "We will proceed as follows: we will
describe how to compute the set of routers which can be reached from S
without traversing S-E."

For clarity, can you change this to: "how to compute the set of
routers which can be reached from S on the shortest-path tree without
traversing S-E"?  That may help remove some of the confusion when you
then define extended P-space - where clearly S can reach as well."

Please make the same change in the first sentence of 4.2.1.1.

9) Sec 4.2.1.1: First, can you explain why you remove those nodes that
are ECMP in the draft?  I assume it is because such nodes require a
directed first hop to avoid accidentally going through S-E.

Second, after describing "excising the sub-tree" - what about a quick
clue such as: "For example, if an SPF computation stores at each node
the next-hops to be used to reach that node from S, then one can
simply add a node to P-space if none of its next-hops are S-E"

10) How are multi-point interfaces handled?  I see no discussion of
that in Sec 4.2.1.1 or Sec 4.2.1.2.

11) In Sec 5, I am confused by the example and I believe it is because
there are typos?

"When a failure occurs on the link between PE1 and P2, PE1 does not
have an LFA for traffic reachable via P1.  Similarly, by symmetry, if
the link between PE2 and P1 fails, PE2 does not have an LFA for
traffic reachable via P2."

But PE2->P1 has a cost of 1000 and PE1's path to P1 isn't affected by
the failure of the link PE1-P2...  Could you please correct or clarify?

12) Sec 6: Given that [I-D.bryant-ipfrr-tunnels] is expired and not
intended for publication and this draft is heading towards RFC, is
there a reason not to accurately and fully pull out the problem
description into this draft?

13) Sec 6: The same problems can occur with SRLG failures.  Can you
please add a brief paragraph decribing how the different cases apply
for SRLG failure?  Also, please expand on the analysis recommendation.

14) Sec 7, 2nd paragraph: reference is to "Section 2" instead of
"Figure 2".

15) Sec 8: please update the "date of this draft" to be an actual date
- as the draft is revised and progresses, this would falsely imply
more recent data than will be there.

16) Sec 8: Can you please define what is meant by "protected
destinations" and "guaranteed node-protected destinations"?  Is the
first if a destination is protected from all sources against all link
failures?  Is it something more limited such as PLR/dest pairs?

17) Sec 8.4: typo - "saleability" should be "scaleability".

18) Sec 8.4:  The end of this section

"In the very few cases where P and Q spaces have an empty
intersection, one could select the closest node in the Q space and
signal an explicitly-routed RSVP TE LSP to that Q node.  A directed
LDP session is then established with the selected Q node and the rest
of the solution is identical to that described elsewhere in this
document.  Alternatively the segment routing technology being defined
in the IETF may be used to carry the traffic between non-collocated P
and Q nodes [I-D.filsfils-rtgwg-segment-routing-use-cases],
[I-D.filsfils-rtgwg-segment-routing],
[I-D.gredler-rtgwg-igp-label-advertisement]."

seems to be describing functionality that isn't fully specified or
mentioned elsewhere in the draft and that doesn't fall within RTGWG's
charter.  If we include explicit routing rather than hop-by-hop, we've
known how to do that for years.  At a minimum, it'd be useful to put
this paragraph in a section by itself that is "Potential Coverage
Improvements Via Explicit Routing" or the like.





On Wed, Dec 4, 2013 at 8:35 AM, Alvaro Retana (aretana)
<aretana@cisco.com>wrote:

>  Hi!
>
>  After what I thought was a productive set of feedback and discussion
> related to this draft, both in the mailing list as well as at the meeting
> in Vancouver, I would like to start a Working Group Last Call.  This call
> will close by EOD (pick your favorite time zone) on December 19, 2013.
>
>  http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa
>
>  Please provide specific feedback as to why you support (or not) the
> advancement of this draft.  Please avoid "+1"-type responses.
>
>  Thanks!
>
>  Alvaro.
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>
>

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

<div dir=3D"ltr">I&#39;ve given this draft a thorough reading (except for c=
ommenting on the cost-based algorithm that Pushpasis already gave feedback =
on).<div><br></div><div>I have two major concerns. =A0First, I see no discu=
ssion at all about how multipoint interfaces are handled. =A0Nothing indica=
tes that they are out of scope for protection nor does the discussion descr=
ibe how to handle avoiding the pseudo-nodes or related computation. =A0Seco=
nd, as a standards-track document, I see almost no description of what MUST=
 or even SHOULD be implemented. =A0What would conformance mean?</div>
<div><br></div><div>Here are my detailed comments - in going through the dr=
aft order, not by priority.</div><div><br></div><div><div>0)Sec 2: Can you =
add a paragraph describing the extended-P space and</div><div>Q-space for t=
he example in Figure 2? =A0It&#39;s fine to have the</div>
<div>definitions, but it is jarring to run into Q-space in Sec 4 without</d=
iv><div>any other reference. =A0For instance, just adding:</div><div><br></=
div><div>&quot;In [Figure 1], S can reach A, B, and C without going via E; =
these</div>
<div>form S&#39;s extended P-space. =A0The routers that can reach E without=
 going</div><div>through S-E will be E&#39;s Q-space; these are D and C. =
=A0B has equal-cost</div><div>paths via B-A-S-E and B-C-D-E and so may go t=
hrough S-E. =A0The single</div>
<div>node in both S&#39;s P-space and E&#39;s Q-space is C; thus node C is =
selected</div><div>as the repair tunnel&#39;s end-point. =A0For more detail=
s on the reasoning</div><div>behind these calculations, please see [Sec 4.2=
]&quot;</div>
<div><br></div><div>1) Sec 3, 2nd paragraph, 1 sentence:</div><div>=A0 &quo=
t;A tunneled repair path tunnels traffic to some staging point in the</div>=
<div>=A0 =A0network from which it is assumed that, in the absence of multip=
le</div>
<div>=A0 =A0failures, it will travel to its destination using normal forwar=
ding</div><div>=A0 =A0without looping back.&quot;</div><div><br></div><div>=
First, can you replace &quot;assumed&quot; with precalculated or the like? =
=A0This</div>
<div>isn&#39;t an assumption - it is based on shortest-path forwarding and =
is</div><div>carefully determined.</div><div><br></div><div>Second, &quot;i=
n the absence of multiple failures&quot; should be &quot;in the</div><div>
absence of a worse failure (e.g. node or SRLG) or multiple failures&quot;.<=
/div><div><br></div><div>2) Sec 3.1: For clarity, could you add a sentence =
indicating that the</div><div>tunnel itself must also avoid going over the =
link S-E?</div>
<div><br></div><div>3) Sec 3.2, 2nd paragraph: =A0&quot;In order for S to o=
btain</div><div>=A0 =A0the correct inner label it is necessary to establish=
 a directed LDP</div><div>=A0 =A0session[RFC5036] to the tunnel end point.&=
quot;</div>
<div><br></div><div>Shouldn&#39;t that be a &quot;targeted LDP session&quot=
;? =A0I don&#39;t see directed at</div><div>all in RFC5036 and am personall=
y only familiar with them being called</div><div>targeted LDP sessions.</di=
v>
<div><br></div><div>4) Sec 3.2 3rd paragraph: &quot;The performance of the =
encapsulation and</div><div>decapsulation is efficient as encapsulation is =
just a push of one</div><div>label (like conventional MPLS TE FRR) and the =
decapsulation occurs</div>
<div>naturally at the penultimate hop before the repair tunnel endpoint.&qu=
ot;</div><div><br></div><div>Decapsulation can occur at the penultimate hop=
, if the repair tunnel</div><div>endpoint so specifies.</div><div><br></div=
>
<div>5) Sec 3.2 3rd paragraph: &quot;The time to establish the TLDP session=
 and</div><div>acquire labels will limit the speed at which a new tunnel ca=
n be put</div><div>into service, but this will not be a problem in normal o=
peration.&quot;</div>
<div><br></div><div>Can you please put some justification as to why this wi=
ll not be a</div><div>problem in normal operation? =A0Is your assumption th=
at the added delay</div><div>before the network is fully repaired acceptabl=
e because failure</div>
<div>analysis studies indicate the separation between failures is generally=
</div><div>at least X seconds and the time to establish a TLDP session and<=
/div><div>exchange labels (how many) is no more than Y seconds (in a router=
 that</div>
<div>is also dealing with reconvergence of all protocols beyond the IGP)?</=
div><div><br></div><div>The extra communication clearly adds some delay bef=
ore protection is</div><div>available and a blanket assertion that it doesn=
&#39;t matter is more</div>
<div>marketing than engineering.</div><div><br></div><div>6) Given that thi=
s is a standards-track draft, is there a reason that</div><div>a minimum-to=
-implement tunnel type isn&#39;t specified? =A0I don&#39;t see/know</div>
<div>of any references for how a router can know if a remote router can</di=
v><div>decapsulate IP-in-IP at speed or support GRE or even support a tLDP<=
/div><div>session.</div><div><br></div><div>7) Sec 4.1: This seems to be ig=
noring the protection of per-prefix</div>
<div>LFA, which is a superset of &quot;link LFA&quot;. =A0More critically, =
as you know,</div><div>doing per-prefix LFA can allow the protection of mul=
ti-homed prefixes.</div><div>Can you please update this section to indicate=
 how and if remote LFA</div>
<div>applies to multi-homed prefixes? =A0As written, it sounds like it does=
</div><div>not. =A0It also sounds as if remote LFA is required even if ther=
e is a</div><div>per-prefix LFA for all destinations going via S-E.</div><d=
iv>
<br></div><div>8) Sec 4.2.1, 2nd paragraph: &quot;We will proceed as follow=
s: we will</div><div>describe how to compute the set of routers which can b=
e reached from S</div><div>without traversing S-E.&quot;</div><div><br>
</div><div>For clarity, can you change this to: &quot;how to compute the se=
t of</div><div>routers which can be reached from S on the shortest-path tre=
e without</div><div>traversing S-E&quot;? =A0That may help remove some of t=
he confusion when you</div>
<div>then define extended P-space - where clearly S can reach as well.&quot=
;</div><div><br></div><div>Please make the same change in the first sentenc=
e of 4.2.1.1.</div><div><br></div><div>9) Sec <a href=3D"http://4.2.1.1">4.=
2.1.1</a>: First, can you explain why you remove those nodes that</div>
<div>are ECMP in the draft? =A0I assume it is because such nodes require a<=
/div><div>directed first hop to avoid accidentally going through S-E.</div>=
<div><br></div><div>Second, after describing &quot;excising the sub-tree&qu=
ot; - what about a quick</div>
<div>clue such as: &quot;For example, if an SPF computation stores at each =
node</div><div>the next-hops to be used to reach that node from S, then one=
 can</div><div>simply add a node to P-space if none of its next-hops are S-=
E&quot;</div>
<div><br></div><div>10) How are multi-point interfaces handled? =A0I see no=
 discussion of</div><div>that in Sec 4.2.1.1 or Sec 4.2.1.2.</div><div><br>=
</div><div>11) In Sec 5, I am confused by the example and I believe it is b=
ecause</div>
<div>there are typos?</div><div><br></div><div>&quot;When a failure occurs =
on the link between PE1 and P2, PE1 does not</div><div>have an LFA for traf=
fic reachable via P1. =A0Similarly, by symmetry, if</div><div>the link betw=
een PE2 and P1 fails, PE2 does not have an LFA for</div>
<div>traffic reachable via P2.&quot;</div><div><br></div><div>But PE2-&gt;P=
1 has a cost of 1000 and PE1&#39;s path to P1 isn&#39;t affected by</div><d=
iv>the failure of the link PE1-P2... =A0Could you please correct or clarify=
?</div>
<div><br></div><div>12) Sec 6: Given that [I-D.bryant-ipfrr-tunnels] is exp=
ired and not</div><div>intended for publication and this draft is heading t=
owards RFC, is</div><div>there a reason not to accurately and fully pull ou=
t the problem</div>
<div>description into this draft?</div><div><br></div><div>13) Sec 6: The s=
ame problems can occur with SRLG failures. =A0Can you</div><div>please add =
a brief paragraph decribing how the different cases apply</div><div>for SRL=
G failure? =A0Also, please expand on the analysis recommendation.</div>
<div><br></div><div>14) Sec 7, 2nd paragraph: reference is to &quot;Section=
 2&quot; instead of</div><div>&quot;Figure 2&quot;.</div><div><br></div><di=
v>15) Sec 8: please update the &quot;date of this draft&quot; to be an actu=
al date</div>
<div>- as the draft is revised and progresses, this would falsely imply</di=
v><div>more recent data than will be there.</div><div><br></div><div>16) Se=
c 8: Can you please define what is meant by &quot;protected</div><div>desti=
nations&quot; and &quot;guaranteed node-protected destinations&quot;? =A0Is=
 the</div>
<div>first if a destination is protected from all sources against all link<=
/div><div>failures? =A0Is it something more limited such as PLR/dest pairs?=
</div><div><br></div><div>17) Sec 8.4: typo - &quot;saleability&quot; shoul=
d be &quot;scaleability&quot;.</div>
<div><br></div><div>18) Sec 8.4: =A0The end of this section</div><div><br><=
/div><div>&quot;In the very few cases where P and Q spaces have an empty</d=
iv><div>intersection, one could select the closest node in the Q space and<=
/div>
<div>signal an explicitly-routed RSVP TE LSP to that Q node. =A0A directed<=
/div><div>LDP session is then established with the selected Q node and the =
rest</div><div>of the solution is identical to that described elsewhere in =
this</div>
<div>document. =A0Alternatively the segment routing technology being define=
d</div><div>in the IETF may be used to carry the traffic between non-colloc=
ated P</div><div>and Q nodes [I-D.filsfils-rtgwg-segment-routing-use-cases]=
,</div>
<div>[I-D.filsfils-rtgwg-segment-routing],</div><div>[I-D.gredler-rtgwg-igp=
-label-advertisement].&quot;</div><div><br></div><div>seems to be describin=
g functionality that isn&#39;t fully specified or</div><div>mentioned elsew=
here in the draft and that doesn&#39;t fall within RTGWG&#39;s</div>
<div>charter. =A0If we include explicit routing rather than hop-by-hop, we&=
#39;ve</div><div>known how to do that for years. =A0At a minimum, it&#39;d =
be useful to put</div><div>this paragraph in a section by itself that is &q=
uot;Potential Coverage</div>
<div>Improvements Via Explicit Routing&quot; or the like.</div></div><div><=
br></div><div><br></div><div><br></div></div><div class=3D"gmail_extra"><br=
><br><div class=3D"gmail_quote">On Wed, Dec 4, 2013 at 8:35 AM, Alvaro Reta=
na (aretana) <span dir=3D"ltr">&lt;<a href=3D"mailto:aretana@cisco.com" tar=
get=3D"_blank">aretana@cisco.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">



<div style=3D"font-size:14px;font-family:Calibri,sans-serif;word-wrap:break=
-word">
<div>Hi!</div>
<div><br>
</div>
<div>After what I thought was a productive set of feedback and discussion r=
elated to this draft, both in the mailing list as well as at the meeting in=
 Vancouver, I would like to start a Working Group Last Call. =A0This call w=
ill close by EOD (pick your favorite
 time zone) on December 19, 2013.</div>
<div><br>
</div>
<div><a href=3D"http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa" tar=
get=3D"_blank">http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa</a></=
div>
<div><br>
</div>
<div>Please provide specific feedback as to why you support (or not) the ad=
vancement of this draft. =A0Please avoid &quot;+1&quot;-type responses.</di=
v>
<div><br>
</div>
<div>Thanks!</div><span class=3D"HOEnZb"><font color=3D"#888888">
<div><br>
</div>
<div>Alvaro.</div>
</font></span></div>

<br>_______________________________________________<br>
rtgwg mailing list<br>
<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/rtgwg" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/rtgwg</a><br>
<br></blockquote></div><br></div>

--089e0112c7fe57053c04ece5a610--

From lberger@labn.net  Wed Dec 11 10:57:57 2013
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 EEFC71ADFCA for <rtgwg@ietfa.amsl.com>; Wed, 11 Dec 2013 10:57:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.654
X-Spam-Level: 
X-Spam-Status: No, score=-0.654 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_BL_SPAMCOP_NET=1.347, 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 L3nhkond8qa8 for <rtgwg@ietfa.amsl.com>; Wed, 11 Dec 2013 10:57:55 -0800 (PST)
Received: from alt-proxy11.mail.unifiedlayer.com (alt-proxy11.mail.unifiedlayer.com [74.220.211.241]) by ietfa.amsl.com (Postfix) with SMTP id 0E9D71ADF74 for <rtgwg@ietf.org>; Wed, 11 Dec 2013 10:57:54 -0800 (PST)
Received: (qmail 16684 invoked by uid 0); 11 Dec 2013 18:57:48 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy4.mail.unifiedlayer.com with SMTP; 11 Dec 2013 18:57:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=KtiiThZQIFG/HolH1D6RdGpKLloZAWWQGWj4armCVUE=;  b=XxmvNnXjY3cNn3ewS1PqJoW+PUmtPgYyhXRdEQFmxGnqzp+6tgsVODcE+CBd2MHPgbljyoqkJS/46FTw/mOLtZ0GwUrOSxtC+eOy8gf1igP3tJJXzRdtoBGOBwtpXFQ3;
Received: from box313.bluehost.com ([69.89.31.113]:43504 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1Vqoyi-0001OY-AH; Wed, 11 Dec 2013 11:57:48 -0700
Message-ID: <52A8B5AB.4040708@labn.net>
Date: Wed, 11 Dec 2013 13:57:47 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: rtg-dir@ietf.org
Subject: RtgDir review: draft-ietf-rtgwg-cl-requirement-13
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: draft-ietf-rtgwg-cl-requirement.all@tools.ietf.org, rtgwg@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
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 Dec 2013 18:57:57 -0000

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. The purpose
of the review is to provide assistance to the Routing ADs. For more
information about the Routing Directorate, please see
http://www.ietf.org/iesg/directorate/routing.html

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-requirement-13.txt
Reviewer: Lou Berger
Review Date: 2013-12-11
IETF LC End Date: 2013-12-09
Intended Status: Informational

Summary:

        I have some minor concerns about this document that I think
should be resolved before publication.

Comments:

    I think the document is greatly improved since the previous last
call.  I have some comments and reservations on the document that are
described below.  As discussed on the list, I remain concerned about the
value of defining requirements in terms of nebulous "Performance
Objectives", but as this is acceptable to the WG I will not elaborate on
this concern further.

Major Issues:

   No major issues found.

Minor Issues:

1. Terminology & consistency: the document coins the term "Advanced
Multipath":
       Advanced Multipath is a formalization of multipath techniques

Do you see this term as a new noun, like LSP, or as an adjective?  I
expected the latter, i.e. that it be used like "multipath" is used in
the above sentence, but it seems to be used as a new noun.  I'm not sure
coining a new noun really makes sense, but if this the intent then the
last paragraph of section 2 needs to be revised as "Advanced Multipath"
will now have a specific definition as opposed to a generic term. Also I
suggest always capitalizing it (or even using the abbreviation "AM")
will clarify this distinction.

2. Editorial: server and client layer vs upper and lower layer.

The document uses server and client layer networks and LSPs and,
sometimes interchangeably or redundantly, upper and lower layer networks
and LSPs.  I think this issue can be resolved by avoiding the term
client/server when referring to network layers and just using the
lower/upper terminology.  The one exception to this is in the definition
Client LSP which should simply be defined in the context of a multipath,
i.e.:
OLD
A client LSP is an LSP which has been set up over a server layer.
NEW
A client LSP is an LSP which has been set up over Advanced Multipath.

I think this also means that usage of the term "Client" is limited to
"Client LSP".

3. Technical: The document should make it clear that LSPs can provide
paths from an Advanced Multipath.  I suggest adding something like the
the following at the end of page 3
   d. a lower layer LSP.
and at the end of the Component Link definition:
   A component link may be provided via an LSP.

4. Editorial: Unless I'm mistaken, the requirements in this document
apply to the Advanced Multipath solution.  In most cases the document
states requirements in the form of "The solution", but in a few cases it
just says "advanced multipath".  I think these cases should be changed
to apply to an "Advanced Multipath solution".  I think this comment
applies to FR1, FR7, FR18, FR23, GR3-5, and MR1-9.

5. Technical: use of "indicate" in FR10-13, FR14, FR15:
In these cases it is unclear if the requirements apply to
(a) a client's ability to indicate a desired service/LSP constraint or
(b) a selected component link's attribute that will be used by a client
LSP,
(c) both, or
(d) something completely different
The requirements should be clear to which entity the requirement applies.

6. The last paragraph in section 3.3. strikes me as both odd and out of
place.  There are so many possible decisions that must be considered by
network operators relative to disruption and optimization.  Why mention
just "power reduction"?  Is there something special about the
interactions of multipath and power reduction?  What value / information
does this paragraph add?

7. Terminology: In GR4&5: what is a "MPLS network topology"? Do you mean AS?

Nits:

- References should be provided in all cases when referring to
  "existing ... techniques"

Using line numbers from
http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-rtgwg-cl-requirement-13.txt

Line 112
s/SHOULD/should

Line 118
s/MAY/may

Line 149, match intro:
s/Advanced Multipath meets/Advanced Multipath is a formalization of
multipath techniques that meet

Lines 251-254, beginning with "The" through the end of the paragraph.
This should be an FR.

That's it,
Lou



From curtis@ipv6.occnc.com  Tue Dec 17 19:36:36 2013
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 BF1451AE04F; Tue, 17 Dec 2013 19:36:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, 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 QBGZ-3I2Vkuc; Tue, 17 Dec 2013 19:36:32 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 48D5F1AE038; Tue, 17 Dec 2013 19:36:31 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id rBI3aTOu079410; Tue, 17 Dec 2013 22:36:29 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201312180336.rBI3aTOu079410@maildrop2.v6ds.occnc.com>
To: Lou Berger <lberger@labn.net>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: RtgDir review: draft-ietf-rtgwg-cl-requirement-13
In-reply-to: Your message of "Wed, 11 Dec 2013 13:57:47 -0500." <52A8B5AB.4040708@labn.net>
Date: Tue, 17 Dec 2013 22:36:29 -0500
Cc: rtg-dir@ietf.org, draft-ietf-rtgwg-cl-requirement.all@tools.ietf.org, "rtg-ads@tools.ietf.org" <rtg-ads@tools.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: Wed, 18 Dec 2013 03:36:36 -0000

In message <52A8B5AB.4040708@labn.net>
Lou Berger 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. The purpose
> of the review is to provide assistance to the Routing ADs. For more
> information about the Routing Directorate, please see
> http://www.ietf.org/iesg/directorate/routing.html
>  
> 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-requirement-13.txt
> Reviewer: Lou Berger
> Review Date: 2013-12-11
> IETF LC End Date: 2013-12-09
> Intended Status: Informational
>  
> Summary:
>  
>         I have some minor concerns about this document that I think
> should be resolved before publication.
>  
> Comments:
>  
>     I think the document is greatly improved since the previous last
> call.  I have some comments and reservations on the document that are
> described below.  As discussed on the list, I remain concerned about the
> value of defining requirements in terms of nebulous "Performance
> Objectives", but as this is acceptable to the WG I will not elaborate on
> this concern further.
>  
> Major Issues:
>  
>    No major issues found.
>  
> Minor Issues:
>  
> 1. Terminology & consistency: the document coins the term "Advanced
> Multipath":
>        Advanced Multipath is a formalization of multipath techniques
>  
> Do you see this term as a new noun, like LSP, or as an adjective?  I
> expected the latter, i.e. that it be used like "multipath" is used in
> the above sentence, but it seems to be used as a new noun.  I'm not sure
> coining a new noun really makes sense, but if this the intent then the
> last paragraph of section 2 needs to be revised as "Advanced Multipath"
> will now have a specific definition as opposed to a generic term. Also I
> suggest always capitalizing it (or even using the abbreviation "AM")
> will clarify this distinction.

I see multipath as a noun and therefore advanced multipath as a noun.
Advanced is an adjective, multipath as a noun.  Advanced Multipath is
the set of techniques that form a solution.  An advanced multipath is
a collection of componet links.  The former is capitalized, the latter
is not.  I'll check to see if I got that right in all occurances.  If
you would like I can also add this to the definition making it:

 OLD

   Advanced Multipath
       Advanced Multipath meets the requirements defined in this
       document.  A key capability of advanced multipath is the support
       of non-homogeneous component links.

 NEW

   Advanced Multipath
       Advanced Multipath is a formalization of multipath techniques
       that meets the requirements defined in this document.  A key
       capability of Advanced Multipath is the support of
       non-homogeneous component links.  An "advanced multipath" is a
       collection of component links.  In this document the former is
       capitalized and the latter is not.

If we agree on this I'll just search for "advanced" and make
capitalization consistent with the above statements.

I don't think the phrase "advanced multipath technique" makes it an
adjective any more than a statement such as make-before-break is an
MPLS technique" makes MPLS an adjective in normal use.  The phrase "an
X technique" is simply a shorthand for indicating a "technique
applicable to X".  Even if that makes it an adjective the phrase "MPLS
technique" is common and so that should not be a problem.  The
paragraph in question might be the following.  It seems benign to me.

   The term Advanced Multipath is intended to be used within the context
   of this document and the related documents,
   [I-D.ietf-rtgwg-cl-use-cases] and [I-D.ietf-rtgwg-cl-framework] and
   any other related document.  Other advanced multipath techniques may
   in the future arise.  If the capabilities defined in this document
   become commonplace, they would no longer be considered "advanced".
   Use of the term "advanced multipath" outside this document, if
   referring to the term as defined here, should indicate Advanced
   Multipath as defined by this document, citing the current document
   name.  If using another definition of "advanced multipath", documents
   may optionally clarify that they are not using the term "advanced
   multipath" as defined by this document if clarification is deemed
   helpful.

I see no problem with this.  Please be more specific if you think
there are places where advanced multipath is used as an adjective or
where its use is confusing.

> 2. Editorial: server and client layer vs upper and lower layer.
>  
> The document uses server and client layer networks and LSPs and,
> sometimes interchangeably or redundantly, upper and lower layer networks
> and LSPs.  I think this issue can be resolved by avoiding the term
> client/server when referring to network layers and just using the
> lower/upper terminology.  The one exception to this is in the definition
> Client LSP which should simply be defined in the context of a multipath,
> i.e.:
> OLD
> A client LSP is an LSP which has been set up over a server layer.
> NEW
> A client LSP is an LSP which has been set up over Advanced Multipath.

A client LSP can be set up over a server layer MPLS-TP LSP or any
server layer MPLS LSP or over a link layer or over a pseudowire ... or
over an advanced multipath.

> I think this also means that usage of the term "Client" is limited to
> "Client LSP".

I searched for all occurances of the word client.  All occurances are
"client LSP" excexpt the phrase "client of a client LSP" and that is
used only in the following paragraph.

   The ingress and egress of a multipath may be midpoint LSRs with
   respect to a given client LSP.  A midpoint LSR does not participate
   in the signaling of any clients of the client LSP.  Therefore, in
   general, multipath endpoints cannot determine requirements of clients
   of a client LSP through participation in the signaling of the clients
   of the client LSP.

THe point is that "A midpoint LSR does not participate in the
signaling of any clients of the client LSP" and that non-participation
in client (or higher layer) signaling applies to any "client of a
client LSP", not just other LSP running over it.

I then searched for all occurances of the words upper and lower and
higher.  There are no occurances of "upper".

There were a few occurances of "lower latency" and "higher latency".
Other than that, all occurances of lower and higher except one are in
the follwoing text:

 3.2.  Component Links Provided by Lower Layer Networks

   A component link may be supported by a lower layer network.  For
   example, the lower layer may be a circuit switched network or another
   MPLS network (e.g., MPLS-TP)).  The lower layer network may change
   the latency (and/or other performance parameters) seen by the client
   layer.  Currently, there is no protocol for the lower layer network
   to inform the higher layer network of a change in a performance
   parameter.  Communication of the latency performance parameter is a
   very important requirement.  Communication of other performance
   parameters (e.g., delay variation) is desirable.

   FR#8  The solution SHALL specify a protocol means to allow a lower
       layer server network to communicate latency to the higher layer
       client network.

The exception is this sentence:

     FR#22 The solution SHOULD support the use case where an advanced
       multipath itself is a component link for a higher order advanced
       multipath.  For example, an advanced multipath comprised of MPLS-
       TP bi-directional tunnels viewed as logical links could then be
       used as a component link in yet another advanced multipath that
       connects MPLS routers.

The terms lower layer and higher layer go all the way back to the ISO
seven layer model of ancient times (1970s?, 1980s?) and maybe further
back but that is before even my time.

I don't think this is unclear but I could add the following in
definitions:

   Higher Layers
      A client layer is the one immediately above a server layer.  The
      client layer and all layers above that layer are higher layers.

   Lower Layers
      A server layer is the later immediately below a client laer.
      The server layer and all layers below are lower layers.

Do I really need to put this in the definitions section?  If yoy think
it is necessary, I will add it.

> 3. Technical: The document should make it clear that LSPs can provide
> paths from an Advanced Multipath.  I suggest adding something like the
> the following at the end of page 3
>    d. a lower layer LSP.

Case "b." is intended to include LSP but is not specifically limited
to LSP.  Multipath (not Advanced Multipath) includes IGP ECMP,
Ethernet Link Aggregation, and all sorts of things that don't involve
MPLS at all.  For example, a path in Ethernet Link Aggregation Group
(LAG) could be supported by a pseudowires or ODU2e or GFP-F, though
this would be unknown to the LAG, or in the simplest case each path in
the set of LAG members could be supported by a plain Ethernet cable.

> and at the end of the Component Link definition:
>    A component link may be provided via an LSP.

I think this is covered in "3.2.  Component Links Provided by Lower
Layer Networks".

 3.2.  Component Links Provided by Lower Layer Networks

   A component link may be supported by a lower layer network.  For
   example, the lower layer may be a circuit switched network or another
   MPLS network (e.g., MPLS-TP)).

This sort of statement could be made earlier.  For example in the
discussion following the definitions (on page 5) the document covers
one case (where a component link is not an LSP) but it is not until
later that the other case is mentioned.

I could add a paragraph in the discussion following the definitions
that mentions that a component link can also be another LSP.

 OLD:

   A Component Link may be a point-to-point physical link (where a
   "physical link" includes one or more link layer plus a physical
   layer) or a logical link that preserves ordering in the steady state.
   A component link may have transient out of order events, but such
   events must not exceed the network's Performance Objectives.  For
   example, a component link may be comprised of any supportable
   combination of link layers over a physical layer or over logical sub-
   layers, including those providing physical layer emulation.

 NEW:

   A Component Link may be a point-to-point physical link (where a
   "physical link" includes one or more link layer plus a physical
   layer) or a logical link that preserves ordering in the steady state.
   A component link may have transient out of order events, but such
   events must not exceed the network's Performance Objectives.  For
   example, a component link may be comprised of any supportable
   combination of link layers over a physical layer or over logical sub-
   layers, including those providing physical layer emulation, or over
    MPLS server layer LSP.

These are identical except the phrase ", or over MPLS server layer
LSP" added to the end of the last sentence.

> 4. Editorial: Unless I'm mistaken, the requirements in this document
> apply to the Advanced Multipath solution.  In most cases the document
> states requirements in the form of "The solution", but in a few cases it
> just says "advanced multipath".  I think these cases should be changed
> to apply to an "Advanced Multipath solution".  I think this comment
> applies to FR1, FR7, FR18, FR23, GR3-5, and MR1-9.

That is not correct.  For example:

   FR#1  An advanced multipath MAY be announced in conjunction with
       detailed parameters about its component links, such as bandwidth
       and latency.  The advanced multipath SHALL behave as a single IGP
       adjacency.

In this requirement the "advanced multipath" is a specific collection
of component links that is announced by way of an MPLS Forwarding
Adjaccency (FA) in the IGP.  The same is true for the other
requirements cited.  In all of these cases an advanced multipath is a
specific collection of component links.  There is a typo in MR#1.

 OLD

   MR#1  Management Plane MUST support polling of the status and
       configuration of an advanced multipath and its individual
       advanced multipath and support notification of status change.

 NEW

   MR#1  Management Plane MUST support polling of the status and
       configuration of an advanced multipath and its individual
       component links and support notification of status change.

In the last line
s/advanced multipath/component links/

> 5. Technical: use of "indicate" in FR10-13, FR14, FR15:
> In these cases it is unclear if the requirements apply to
> (a) a client's ability to indicate a desired service/LSP constraint or
> (b) a selected component link's attribute that will be used by a client
> LSP,
> (c) both, or
> (d) something completely different
> The requirements should be clear to which entity the requirement applies.

This "indication" can be through signaling or the management plane and
both must be supported in later framework and protocol definitions and
we can argue then whether both must be supported or if one or the
other is a "should" in RFC 2119 speak.

There was concern that the word "signal" would exclude providing the
same informantion through the management plane and therefore the word
"indicate" is used.

Rather than spell this out many times we hoped this would be clear.  I
could add clarifying text up front if you think this is necessary.  For
example, I could add the following before FR#1.

   FR#0  In requirements that follow in this document the word
      "indicate" is used where information may be provided by either
      the combination of link state IGP advertisement and MPLS LSP
      signaling or via management plane protocols.  In later documents
      providing framework and protocol definitions both signaling and
      management plane mechanisms MUST be defined.

It would be trivial to make this FR#1 and renumber the rest.

Should I add it and renumber?

> 6. The last paragraph in section 3.3. strikes me as both odd and out of
> place.  There are so many possible decisions that must be considered by
> network operators relative to disruption and optimization.  Why mention
> just "power reduction"?  Is there something special about the
> interactions of multipath and power reduction?  What value / information
> does this paragraph add?

The last paragraph in section 3.3 is:

   Allowing multipath to contain component links with different
   characteristics can improve the overall load balance and can be
   accomplished while still accommodating the more strict requirements
   of a subset of client LSP.

I'm not sure if this is the "odd and out of place" paragraph you refer
to.  It summarizes the purpose of the requirements in this section.  I
think you mean section 3.5 and not 3.3.

The remainder of your paragraph above discusses power reducetion and
this is only mentioned in section 3.5 so I think you mean this
paragraph.

   As with any load balancing change, a change initiated for the purpose
   of power reduction may be minimally disruptive.  Typically the
   disruption is limited to a change in delay characteristics and the
   potential for a very brief period with traffic reordering.  The
   network operator when configuring a network for power reduction
   should weigh the benefit of power reduction against the disadvantage
   of a minimal disruption.

The paragraphs following a set of requirements provide discussion
related to that set of requirements.  I don't see this as out of
place.  The prior two paragraphs discuss delay discontinuity.  This
paragraph is a reminder that "As with any load balancing change, a
change initiated for the purpose of power reduction may be minimally
disruptive."  I don't see this as out of place.

For example, to compensate for a less than perfect load balance a
subset of LSPs may need to be moved and that subset can be chosen from
those which will be least affected (and there are plenty of
requirements that compell the fussy LSP to tell the network abour
their specifial needs).  To power down a component link, *all* LSP on
that component link need to be moved, even the very fussy ones.
Therefore I think mentioning that disruption should be considered is
not out of place in the discussion following these requirements.  We
like to keep the discussion brief so this level of detail was not
included.

> 7. Terminology: In GR4&5: what is a "MPLS network topology"? Do you mean AS?

At the very least it means something similar to same administrative
domain.  An AS can be subdivided within an organization.  Do you have
a better way to define intra-domain and inter-domain without going
down the rat hole of defining the term "domain"?  No on in the WG had
an issue with this so far but I'm open for a suggestion for better
wording.

> Nits:
>  
> - References should be provided in all cases when referring to
>   "existing ... techniques"

References are not allowed in the abstract.  In section 3.3 is the sentence:

   Refer to the Appendices in [I-D.ietf-rtgwg-cl-use-cases] for a
   description of existing techniques and a set of references.

Much of that document is dedicated to describing existing techniques
and it contains quite a few references.

I can move this sentence.  Where in the document would you like to see
it moved to?

> Using line numbers from
> http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-rtgwg-cl-requirement-13.txt

Using line number is a text editor counts the page headers.  What tool
are you using?  I didn't see anything on tools.ietf.org.

So I'll guess.  Looks like add 10 lines per page.

> Line 112
> s/SHOULD/should

s/keywords, SHOULD be interpreted/keywords SHOULD be interpreted/

Also remove stray comma.

> Line 118
> s/MAY/may

s/deployment MAY choose to/deployment may choose to/

OK.  Could go either way but s/MAY chose to/MAY/ would work too.

> Line 149, match intro:
> s/Advanced Multipath meets/Advanced Multipath is a formalization of
> multipath techniques that meet

OK.

> Lines 251-254, beginning with "The" through the end of the paragraph.
> This should be an FR.

Looks like you mean this:

   The transient period between some service disrupting
   event and the convergence of the routing and/or signaling protocols
   MUST occur within a time frame specified by Performance Objective
   values.

OK.  I'll add this as FR#6++.

> That's it,
> Lou

There are a few suggestions for changes to the text based on your
comments and a few questions for you.  Based on your response to this
email I will edit the document.

Thanks for the thorough review.

Curtis
