
From nobody Tue Dec  2 17:17:11 2014
Return-Path: <acee@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D4071A1AF1 for <rtgwg@ietfa.amsl.com>; Tue,  2 Dec 2014 17:17:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1sF2rZ8_Ebcu for <rtgwg@ietfa.amsl.com>; Tue,  2 Dec 2014 17:17:06 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EC151A1AFE for <rtgwg@ietf.org>; Tue,  2 Dec 2014 17:17:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1850; q=dns/txt; s=iport; t=1417569427; x=1418779027; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=YKL88yuM8Aam15+pbASC3ODaUlHnCS5vACsg3w1xJlM=; b=InZUPTM0Wm9+qyvAPoGf+VvGIcJSBbQZ9iIwGxviSSRDN9G2HjOavpiV 7zgY/x05mmwQ8uxSxpNYUH43F79Mz3CPTWDMdpwA1yCDqJx6Jd/5iFjO1 p/WHH55lAj6WB5g4MJcM9Agox4SrAyDmsQWO5ftFveA/PtiEBHhWfkohx w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAFACpkflStJV2c/2dsb2JhbABbgwdSWQTHFYYdAoEWFgEBAQEBfYQDAQEEOj0SAgEINhAyGwEGAwIEEwmINw3WIAEBAQEBAQQBAQEBAQEBG5B2hEgFkGGEPoZngSw6gn6QPYN7bwGBRYEBAQEB
X-IronPort-AV: E=Sophos;i="5.07,504,1413244800"; d="scan'208";a="102102184"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-7.cisco.com with ESMTP; 03 Dec 2014 01:16:52 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id sB31Gqb6005426 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtgwg@ietf.org>; Wed, 3 Dec 2014 01:16:52 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.12]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0195.001; Tue, 2 Dec 2014 19:16:52 -0600
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: New Version Notification for draft-acee-rtg-yang-key-chain-00.txt
Thread-Topic: New Version Notification for draft-acee-rtg-yang-key-chain-00.txt
Thread-Index: AQHQDXlppJIGOHb3MkOOLU0Jn1KW1Jx9I3EA
Date: Wed, 3 Dec 2014 01:16:51 +0000
Message-ID: <D0A3CE15.9D5A%acee@cisco.com>
References: <20141201151342.4614.49312.idtracker@ietfa.amsl.com>
In-Reply-To: <20141201151342.4614.49312.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.152.199]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6DB46C8720E7D741B1EA77485F4D8EC8@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/-ks3cF-yoRQ2WN-I2KKY1XLAuaQ
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, 03 Dec 2014 01:17:08 -0000

FYI - This draft describes the key-chain YANG data model. Key-chains have
been implemented by most networking vendors and are used for routing
protocol authentication. One of the authors will be presenting the draft
in Dallas.=20
Thanks,
Acee

On 12/1/14, 10:13 AM, "internet-drafts@ietf.org"
<internet-drafts@ietf.org> wrote:

>
>A new version of I-D, draft-acee-rtg-yang-key-chain-00.txt
>has been successfully submitted by Acee Lindem and posted to the
>IETF repository.
>
>Name:		draft-acee-rtg-yang-key-chain
>Revision:	00
>Title:		Key Chain YANG Data Model
>Document date:	2014-12-01
>Group:		Individual Submission
>Pages:		17
>URL:           =20
>http://www.ietf.org/internet-drafts/draft-acee-rtg-yang-key-chain-00.txt
>Status:        =20
>https://datatracker.ietf.org/doc/draft-acee-rtg-yang-key-chain/
>Htmlized:      =20
>http://tools.ietf.org/html/draft-acee-rtg-yang-key-chain-00
>
>
>Abstract:
>   This document describes the key chain YANG data model.  Industry
>   standard key chains are lists of keys, send lifetimes, accept
>   lifetimes, and algorithms.  By properly overlapping the send and
>   accept lifetimes of multiple key chain entries, keys and algorithms
>   may be gracefully updated.  By representing them in a YANG data
>   model, key distribution can be automated.  Key chains are commonly
>   used for routing protocol authentication and other applications.  In
>   some applications, the protocols do not directly use the key chain
>   entry keys, but rather a key derivation function is used to derive a
>   short-lived key from the key-chain key.
>
>                 =20
>       =20
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>The IETF Secretariat
>


From nobody Tue Dec  2 23:32:53 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 558DA1A00F0; Tue,  2 Dec 2014 23:32:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HafvC8skRPdy; Tue,  2 Dec 2014 23:32:44 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4D371A0022; Tue,  2 Dec 2014 23:32:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=33983; q=dns/txt; s=iport; t=1417591963; x=1418801563; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=kfbdfdUlO3VhERPcjApafYtrw4JlnDm8zeYd8WK9/Wo=; b=VWycUZt5fyt843rSkag13CmsMghw8YSkDS6A/5VaalaYpQdPzrwvXWhz idV+JlAJdppLMVZuhvJd9REf9Q5tZ69JknS0uAxOA98zn/9ekPtvWI6kU VXPKsBooi8RdQAZyxHtgi23HqrKqhkE0iqD+LJ6r3HIBXpm97z2csFh1V c=;
X-IronPort-AV: E=Sophos;i="5.07,506,1413244800";  d="scan'208,217";a="258830877"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 03 Dec 2014 07:32:39 +0000
Received: from [64.103.108.91] (dhcp-bdlk10-data-vlan301-64-103-108-91.cisco.com [64.103.108.91]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id sB37Wc5M016442; Wed, 3 Dec 2014 07:32:39 GMT
Message-ID: <547EBC95.6020608@cisco.com>
Date: Wed, 03 Dec 2014 07:32:37 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: stephane.litkowski@orange.com, Uma Chunduri <uma.chunduri@ericsson.com>, Alia Atlas <akatlas@gmail.com>, Loa Andersson <loa@pi.nu>
Subject: Re: maturity of the MRT technology
References: <546BDF65.2030203@pi.nu> <CAG4d1rfRuyzJS9HjHN_yH69PGa_V=iPeyvxxxFUyKMK_gUqBhA@mail.gmail.com> <3682_1416561775_546F046F_3682_717_1_9E32478DFA9976438E7A22F69B08FF92177BF0@OPEXCLILM34.corporate.adroot.infra.ftgroup> <1B502206DFA0C544B7A60469152008633F44A97E@eusaamb105.ericsson.se> <18727_1416732463_54719F2F_18727_12486_1_9E32478DFA9976438E7A22F69B08FF92178256@OPEXCLILM34.corporate.adroot.infra.ftgroup>
In-Reply-To: <18727_1416732463_54719F2F_18727_12486_1_9E32478DFA9976438E7A22F69B08FF92178256@OPEXCLILM34.corporate.adroot.infra.ftgroup>
Content-Type: multipart/alternative; boundary="------------090208080800000303090409"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/J53XGBxiVaTwRgtVfPPAMBGPPOc
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "draft-atlas-mpls-ldp-mrt@tools.ietf.org" <draft-atlas-mpls-ldp-mrt@tools.ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 07:32:49 -0000

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

I have been mulling this over for a while and I am wondering
how the current industry debate on SDN vs traditional distributed
routing plays into this.

You could build a  case that whilst there always needs to be a base
topology that needs to be calculated using a traditional distributed
routing protocol (for absolute resilience and bootstrapping) any
domain wide repair topology could be better implemented through
SDN since it benefits from a global perspective.

That would suggest that whilst we might benefit from standardizing
the advertisement of some IPFRR related parameters, and would
certainly benefit from standardization of the YANG models needed
to control the IPFRR subsystem, the method of calculating the
repair topology itself ought to be private to the orchestrator.

The classical argument against this is concern with the time to
reinstate the repair topology after a failure, but I am not sure
how significant this is since (a) normally this would be an incremental
change, and (b) given that we would normally be computing this
on some high end platform it could have the results of any single
failure (or restore) pre-computed.

- Stewart

On 23/11/2014 08:47, stephane.litkowski@orange.com wrote:
>
> HI Uma,
>
> >Is this because of domain wide deployment requirements MRT brings-in 
> (as elaborated by Stewart?) or you are ok with LFA/rLFA coverage in 
> the network?
>
> No, domain-wide deployment is not an issue. The issue I see in MRT 
> (for my use case) is unoptimality of the FRR path (at least using 
> lowpoint algorithm). But anyway, as I mentioned, I'm not opposed to 
> make MRT progressing at all. It's good to have multiple tools.
>
> Best Regards,
>
> *From:*Uma Chunduri [mailto:uma.chunduri@ericsson.com]
> *Sent:* Friday, November 21, 2014 20:37
> *To:* LITKOWSKI Stephane SCE/IBNF; Alia Atlas; Loa Andersson
> *Cc:* mpls@ietf.org; mpls-chairs@tools.ietf.org; 
> draft-atlas-mpls-ldp-mrt@tools.ietf.org; rtgwg@ietf.org
> *Subject:* RE: maturity of the MRT technology
>
> >I'm not a great supporter of MRT implementation in my network, because it 
> does not address correctly my use cases but despite of this,
>
> Is this because of domain wide deployment requirements MRT brings-in 
> (as elaborated by Stewart?) or you are ok with LFA/rLFA coverage in 
> the network?
>
> > I deeply think that it's another item in the FRR toolchest (like LFA, 
> remote LFA ...),
>
> >it will be up to each Service Provider to choose the appropriate 
> technology based on its own use case/constraints.
>
> I agree with above.  It depends on the particular deployment scenario 
> and applicability for that network.
>
> --
>
> Uma C.
>
> *From:*mpls [mailto:mpls-bounces@ietf.org] *On Behalf Of 
> *stephane.litkowski@orange.com <mailto:stephane.litkowski@orange.com>
> *Sent:* Friday, November 21, 2014 1:23 AM
> *To:* Alia Atlas; Loa Andersson
> *Cc:* mpls@ietf.org <mailto:mpls@ietf.org>; mpls-chairs@tools.ietf.org 
> <mailto:mpls-chairs@tools.ietf.org>; 
> draft-atlas-mpls-ldp-mrt@tools.ietf.org 
> <mailto:draft-atlas-mpls-ldp-mrt@tools.ietf.org>; rtgwg@ietf.org 
> <mailto:rtgwg@ietf.org>
> *Subject:* Re: [mpls] maturity of the MRT technology
>
> +1
>
> As for all FRR technologies, MRT has pros and cons, and this does not 
> influence the maturity of the technical solutions. We already had 
> multiple discussions online and offline on technical details leading 
> now to documents that are quite detailed and well understood 
> technology (with pros and cons as I mentioned). I'm not a great 
> supporter of MRT implementation in my network, because it does not 
> address correctly my use cases but despite of this, I deeply think 
> that it's another item in the FRR toolchest (like LFA, remote LFA 
> ...), it will be up to each Service Provider to choose the appropriate 
> technology based on its own use case/constraints. Processing of MRT , 
> IMHO, should be done as LFA and other similar technologies so standard 
> track sounds good to me.
>
> We already seen much less mature technologies going to standard track 
> and being RFC without any running code after ...
>
> Best Regards,
>
> Stephane
>
> *From:*rtgwg [mailto:rtgwg-bounces@ietf.org] *On Behalf Of *Alia Atlas
> *Sent:* Thursday, November 20, 2014 19:17
> *To:* Loa Andersson
> *Cc:* mpls@ietf.org <mailto:mpls@ietf.org>; mpls-chairs@tools.ietf.org 
> <mailto:mpls-chairs@tools.ietf.org>; 
> draft-atlas-mpls-ldp-mrt@tools.ietf.org 
> <mailto:draft-atlas-mpls-ldp-mrt@tools.ietf.org>; VIGOUREUX, MARTIN 
> (MARTIN); rtgwg@ietf.org <mailto:rtgwg@ietf.org>
> *Subject:* Re: maturity of the MRT technology
>
> Loa,
>
> Without any hats on, I would note:
>
> a) As far as I'm aware, this has seen two independent prototypes 
> implemented.
>
> b) I have not heard any concrete technical concerns.  Stewart and I 
> did specificallly
>
> discuss MRT this past IETF.  I am, of course, quite interested in 
> hearing any
>
> concrete technical concerns.
>
> c) I'd be happy seeing this question asked of more drafts :-)
>
> Regards,
>
> Alia
>
> On Tue, Nov 18, 2014 at 7:08 PM, Loa Andersson <loa@pi.nu 
> <mailto:loa@pi.nu>> wrote:
>
> Working Groups,
>
> We have don an MPLS-RT of draft-atlas-mpls-ldp-mrt, the reviews has been
> posted to the mpls wg mailing list.
>
> In his MPLS-RT review Stewart Bryant says:
>
> "I have concerns about whether or not MRT technology has the  maturity
>  expected in the standards track. However that decision needs to be
>  taken in RTGWG and MPLS needs to follow their and lead in determining
>  the fate and track of this draft. This draft should not be published
>  ahead of the drafts that define the technology that it is supporting."
>
> He also says that he see no reason not to go ahead and start the poll to
> see if we have consensus to adopt the document as an mpls wg document.
>
> The question Stewart ask is valid, and we'd like input from the rtgwg
> and rtgwg chairs (copied on this mail). We will also copy both the
> poll for adoption and the wglc to the rtgwg mailing list.
>
> /Loa
> mpls wg co-chair
> -- 
>
>
> Loa Andersson   email: loa@mail01.huawei.com 
> <mailto:loa@mail01.huawei.com>
> Senior MPLS Expert loa@pi.nu <mailto:loa@pi.nu>
> Huawei Technologies (consultant)  phone: +46 739 81 21 64 
> <tel:%2B46%20739%2081%2021%2064>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org <mailto:rtgwg@ietf.org>
> https://www.ietf.org/mailman/listinfo/rtgwg
>
> _________________________________________________________________________________________________________________________
>   
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>   
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


-- 
For corporate legal information go to:

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


--------------090208080800000303090409
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 have been mulling this over for a
      while and I am wondering<br>
      how the current industry debate on SDN vs traditional distributed<br>
      routing plays into this.<br>
      <br>
      You could build a&nbsp; case that whilst there always needs to be a
      base <br>
      topology that needs to be calculated using a traditional
      distributed <br>
      routing protocol (for absolute resilience and bootstrapping) any <br>
      domain wide repair topology could be better implemented through <br>
      SDN since it benefits from a global perspective.<br>
      <br>
      That would suggest that whilst we might benefit from standardizing<br>
      the advertisement of some IPFRR related parameters, and would<br>
      certainly benefit from standardization of the YANG models needed <br>
      to control the IPFRR subsystem, the method of calculating the <br>
      repair topology itself ought to be private to the orchestrator.<br>
      <br>
      The classical argument against this is concern with the time to <br>
      reinstate the repair topology after a failure, but I am not sure<br>
      how significant this is since (a) normally this would be an
      incremental<br>
      change, and (b) given that we would normally be computing this <br>
      on some high end platform it could have the results of any single<br>
      failure (or restore) pre-computed.<br>
      <br>
      - Stewart<br>
      <br>
      On 23/11/2014 08:47, <a class="moz-txt-link-abbreviated" href="mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.com</a> wrote:<br>
    </div>
    <blockquote
cite="mid:18727_1416732463_54719F2F_18727_12486_1_9E32478DFA9976438E7A22F69B08FF92178256@OPEXCLILM34.corporate.adroot.infra.ftgroup"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin: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";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">HI
            Uma,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;</span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
            Is this because of domain wide deployment requirements MRT
            brings-in (as elaborated by Stewart?) or you are ok with
            LFA/rLFA coverage in the network?<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">No,
            domain-wide deployment is not an issue. The issue I see in
            MRT (for my use case) is unoptimality of the FRR path (at
            least using lowpoint algorithm). But anyway, as I mentioned,
            I&#8217;m not opposed to make MRT progressing at all. It&#8217;s good to
            have multiple tools.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best
            Regards,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0in 0in 0in">
            <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                Uma Chunduri [<a class="moz-txt-link-freetext" href="mailto:uma.chunduri@ericsson.com">mailto:uma.chunduri@ericsson.com</a>]
                <br>
                <b>Sent:</b> Friday, November 21, 2014 20:37<br>
                <b>To:</b> LITKOWSKI Stephane SCE/IBNF; Alia Atlas; Loa
                Andersson<br>
                <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:mpls@ietf.org">mpls@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:mpls-chairs@tools.ietf.org">mpls-chairs@tools.ietf.org</a>;
                <a class="moz-txt-link-abbreviated" href="mailto:draft-atlas-mpls-ldp-mrt@tools.ietf.org">draft-atlas-mpls-ldp-mrt@tools.ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
                <b>Subject:</b> RE: maturity of the MRT technology<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;I&#8217;m
            not a great supporter of MRT implementation in my network,
            because it does not address correctly my use cases but
            despite of this,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Is
            this because of domain wide deployment requirements MRT
            brings-in (as elaborated by Stewart?) or you are ok with
            LFA/rLFA coverage in the network?<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;
            I deeply think that it&#8217;s another item in the FRR toolchest
            (like LFA, remote LFA &#8230;),
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;it
            will be up to each Service Provider to choose the
            appropriate technology based on its own use
            case/constraints.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">I
            agree with above. &nbsp;It depends on the particular deployment
            scenario and applicability for that network.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">--<o:p></o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Uma
              C.<o:p></o:p></span></p>
        </div>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0in 0in 0in">
            <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                mpls [<a moz-do-not-send="true"
                  href="mailto:mpls-bounces@ietf.org">mailto:mpls-bounces@ietf.org</a>]
                <b>On Behalf Of </b><a moz-do-not-send="true"
                  href="mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.com</a><br>
                <b>Sent:</b> Friday, November 21, 2014 1:23 AM<br>
                <b>To:</b> Alia Atlas; Loa Andersson<br>
                <b>Cc:</b> <a moz-do-not-send="true"
                  href="mailto:mpls@ietf.org">mpls@ietf.org</a>; <a
                  moz-do-not-send="true"
                  href="mailto:mpls-chairs@tools.ietf.org">
                  mpls-chairs@tools.ietf.org</a>; <a
                  moz-do-not-send="true"
                  href="mailto:draft-atlas-mpls-ldp-mrt@tools.ietf.org">
                  draft-atlas-mpls-ldp-mrt@tools.ietf.org</a>; <a
                  moz-do-not-send="true" href="mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
                <b>Subject:</b> Re: [mpls] maturity of the MRT
                technology<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">+1<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">As
            for all FRR technologies, MRT has pros and cons, and this
            does not influence the maturity of the technical solutions.
            We already had multiple discussions online and offline on
            technical details leading now to documents that are quite
            detailed and well understood technology (with pros and cons
            as I mentioned). I&#8217;m not a great supporter of MRT
            implementation in my network, because it does not address
            correctly my use cases but despite of this, I deeply think
            that it&#8217;s another item in the FRR toolchest (like LFA,
            remote LFA &#8230;), it will be up to each Service Provider to
            choose the appropriate technology based on its own use
            case/constraints. Processing of MRT , IMHO, should be done
            as LFA and other similar technologies so standard track
            sounds good to me.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">We
            already seen much less mature technologies going to standard
            track and being RFC without any running code after &#8230;<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best
            Regards,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Stephane<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
            rtgwg [<a moz-do-not-send="true"
              href="mailto:rtgwg-bounces@ietf.org">mailto:rtgwg-bounces@ietf.org</a>]
            <b>On Behalf Of </b>Alia Atlas<br>
            <b>Sent:</b> Thursday, November 20, 2014 19:17<br>
            <b>To:</b> Loa Andersson<br>
            <b>Cc:</b> <a moz-do-not-send="true"
              href="mailto:mpls@ietf.org">mpls@ietf.org</a>; <a
              moz-do-not-send="true"
              href="mailto:mpls-chairs@tools.ietf.org">
              mpls-chairs@tools.ietf.org</a>; <a moz-do-not-send="true"
              href="mailto:draft-atlas-mpls-ldp-mrt@tools.ietf.org">
              draft-atlas-mpls-ldp-mrt@tools.ietf.org</a>; VIGOUREUX,
            MARTIN (MARTIN); <a moz-do-not-send="true"
              href="mailto:rtgwg@ietf.org">
              rtgwg@ietf.org</a><br>
            <b>Subject:</b> Re: maturity of the MRT technology<o:p></o:p></span></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <div>
          <p class="MsoNormal">Loa,<o:p></o:p></p>
          <div>
            <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          </div>
          <div>
            <p class="MsoNormal">Without any hats on, I would note:<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          </div>
          <div>
            <p class="MsoNormal">a) As far as I'm aware, this has seen
              two independent prototypes implemented.<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal">b) I have not heard any concrete
              technical concerns.&nbsp; Stewart and I did specificallly<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal">discuss MRT this past IETF.&nbsp; I am, of
              course, quite interested in hearing any<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal">concrete technical concerns.<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          </div>
          <div>
            <p class="MsoNormal">c) I'd be happy seeing this question
              asked of more drafts :-)<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          </div>
          <div>
            <p class="MsoNormal">Regards,<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal">Alia<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          </div>
        </div>
        <div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          <div>
            <p class="MsoNormal">On Tue, Nov 18, 2014 at 7:08 PM, Loa
              Andersson &lt;<a moz-do-not-send="true"
                href="mailto:loa@pi.nu" target="_blank">loa@pi.nu</a>&gt;
              wrote:<o:p></o:p></p>
            <p class="MsoNormal">Working Groups,<br>
              <br>
              We have don an MPLS-RT of draft-atlas-mpls-ldp-mrt, the
              reviews has been<br>
              posted to the mpls wg mailing list.<br>
              <br>
              In his MPLS-RT review Stewart Bryant says:<br>
              <br>
              "I have concerns about whether or not MRT technology has
              the&nbsp; maturity<br>
              &nbsp;expected in the standards track. However that decision
              needs to be<br>
              &nbsp;taken in RTGWG and MPLS needs to follow their and lead in
              determining<br>
              &nbsp;the fate and track of this draft. This draft should not
              be published<br>
              &nbsp;ahead of the drafts that define the technology that it is
              supporting."<br>
              <br>
              He also says that he see no reason not to go ahead and
              start the poll to<br>
              see if we have consensus to adopt the document as an mpls
              wg document.<br>
              <br>
              The question Stewart ask is valid, and we'd like input
              from the rtgwg<br>
              and rtgwg chairs (copied on this mail). We will also copy
              both the<br>
              poll for adoption and the wglc to the rtgwg mailing list.<br>
              <br>
              /Loa<br>
              mpls wg co-chair<span style="color:#888888"><br>
                <span class="hoenzb">-- </span><br>
                <br>
                <br>
                <span class="hoenzb">Loa Andersson&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
                  &nbsp; email: <a moz-do-not-send="true"
                    href="mailto:loa@mail01.huawei.com" target="_blank">
                    loa@mail01.huawei.com</a></span><br>
                <span class="hoenzb">Senior MPLS Expert&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
                  &nbsp; &nbsp; &nbsp; &nbsp; <a moz-do-not-send="true"
                    href="mailto:loa@pi.nu" target="_blank">
                    loa@pi.nu</a></span><br>
                <span class="hoenzb">Huawei Technologies (consultant)&nbsp; &nbsp;
                  &nbsp;phone: <a moz-do-not-send="true"
                    href="tel:%2B46%20739%2081%2021%2064"
                    target="_blank">
                    +46 739 81 21 64</a></span><br>
                <br>
                <span class="hoenzb">_______________________________________________</span><br>
                <span class="hoenzb">rtgwg mailing list</span><br>
                <span class="hoenzb"><a moz-do-not-send="true"
                    href="mailto:rtgwg@ietf.org" target="_blank">rtgwg@ietf.org</a></span><br>
                <span class="hoenzb"><a moz-do-not-send="true"
                    href="https://www.ietf.org/mailman/listinfo/rtgwg"
                    target="_blank">https://www.ietf.org/mailman/listinfo/rtgwg</a></span></span><o:p></o:p></p>
          </div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
        <pre>_________________________________________________________________________________________________________________________<o:p></o:p></pre>
        <pre><o:p>&nbsp;</o:p></pre>
        <pre>Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc<o:p></o:p></pre>
        <pre>pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o:p></pre>
        <pre>a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,<o:p></o:p></pre>
        <pre>Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></pre>
        <pre><o:p>&nbsp;</o:p></pre>
        <pre>This message and its attachments may contain confidential or privileged information that may be protected by law;<o:p></o:p></pre>
        <pre>they should not be distributed, used or copied without authorisation.<o:p></o:p></pre>
        <pre>If you have received this email in error, please notify the sender and delete this message and its attachments.<o:p></o:p></pre>
        <pre>As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.<o:p></o:p></pre>
        <pre>Thank you.<o:p></o:p></pre>
      </div>
      <pre>_________________________________________________________________________________________________________________________

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

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</pre>
      <br>
      <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>

--------------090208080800000303090409--


From nobody Wed Dec  3 00:06:28 2014
Return-Path: <uma.chunduri@ericsson.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 210271A00E6; Wed,  3 Dec 2014 00:06:26 -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 h7AS0qPpFV9j; Wed,  3 Dec 2014 00:06:19 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB45B1A00DF; Wed,  3 Dec 2014 00:06:18 -0800 (PST)
X-AuditID: c6180641-f79916d00000623a-01-547e6847c93e
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id AE.E3.25146.7486E745; Wed,  3 Dec 2014 02:32:56 +0100 (CET)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.03.0195.001; Wed, 3 Dec 2014 03:06:16 -0500
From: Uma Chunduri <uma.chunduri@ericsson.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, Alia Atlas <akatlas@gmail.com>, "Loa Andersson" <loa@pi.nu>
Subject: RE: maturity of the MRT technology
Thread-Topic: maturity of the MRT technology
Thread-Index: AQHQA4z1PNuAPA+Nnk6RopB29XnlN5xqKS2AgAD9AACAAFZlEIACxG8AgA+iVYD//6+tUA==
Date: Wed, 3 Dec 2014 08:06:16 +0000
Message-ID: <1B502206DFA0C544B7A60469152008633F47FA39@eusaamb105.ericsson.se>
References: <546BDF65.2030203@pi.nu> <CAG4d1rfRuyzJS9HjHN_yH69PGa_V=iPeyvxxxFUyKMK_gUqBhA@mail.gmail.com> <3682_1416561775_546F046F_3682_717_1_9E32478DFA9976438E7A22F69B08FF92177BF0@OPEXCLILM34.corporate.adroot.infra.ftgroup> <1B502206DFA0C544B7A60469152008633F44A97E@eusaamb105.ericsson.se> <18727_1416732463_54719F2F_18727_12486_1_9E32478DFA9976438E7A22F69B08FF92178256@OPEXCLILM34.corporate.adroot.infra.ftgroup> <547EBC95.6020608@cisco.com>
In-Reply-To: <547EBC95.6020608@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: multipart/alternative; boundary="_000_1B502206DFA0C544B7A60469152008633F47FA39eusaamb105erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrPIsWRmVeSWpSXmKPExsUyuXRPiK5HRl2IweRHyhafHl5itnh2fhmj xb+5c5gtvl9awmJxa+lKVosLb34zW5x7OofR4uveh6wOHB5Tfm9k9dg56y67x5IlP5k8Wp6d ZPOYNb2NzePL5c9sAWxRXDYpqTmZZalF+nYJXBknHjxkLVi+hqni6g6xBsbrbUxdjJwcEgIm EnNXfWGFsMUkLtxbz9bFyMUhJHCEUeLKk53MEM4yRonNr1czglSxCehJfJz6kx0kISKwnlFi wf7fLCAOs8AtRokvk+aBVQkLaEscvLgPbK6IgI7Ehbvz2CHsMImFl6aA2SwCKhJHz5wCs3kF fCXedH+E2n2MWWLN9qtsIAlOAU2JtZt2gRUxAh34/dQasMOZBcQlbj2ZD/WEgMSSPeeZIWxR iZeP/0E9pCTx8fd8doj6fInOxR+YIZYJSpyc+YRlAqPoLCSjZiEpm4WkDCKuI7Fg9yc2CFtb YtnC18ww9pkDj5mQxRcwsq9i5CgtTi3LTTcy3MQIjOFjEmyOOxgXfLI8xCjAwajEw2vAUxci xJpYVlyZe4hRmoNFSZxXs3pesJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQbGGX7tu9MXCLaX JzImBa7vUmV/uS6c9W7gNobVGs5evj6sob7BnVklZ7nCQ9m9uA62q8mvW+SS/m/D3av/OxJY nWp6D7ecSFIzUxKQlFeoePCranKT1rKAm1eU1rb8r71QpCsfdL1ON3HptsIXHN99E6pF33R/ Pj2rfTqD0qRJdxifFp2cKqzEUpyRaKjFXFScCADarqb0wgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/mRtY1K_s6ulS0LrXDPhdknIU70I
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "draft-atlas-mpls-ldp-mrt@tools.ietf.org" <draft-atlas-mpls-ldp-mrt@tools.ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 08:06:26 -0000

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

Hi Stewart,

Great thoughts..

Essentially you are saying use X algorithm  (LFA/rLFA/MRT/combination-o- th=
ese/some-great-alternate-path-hunting-algorithm) to
compute alternate paths by a controller  for each node and program these fo=
r link/node failures as per operator choice.

Perhaps  it's futuristic but that future may not be that far!!

>The classical argument against this is concern with the time to
>reinstate the repair topology after a failure, but I am not sure
>how significant this is since (a) normally this would be an incremental
>change, and (b) given that we would normally be computing this
>on some high end platform it could have the results of any single
>failure (or restore) pre-computed.


Given a typical 1000 node network with bunch of links at each node every to=
pology change has to be factored to compute and distribute alternates to al=
l the nodes.
If we really put the alternate computation off from each node and centraliz=
ed at a controller (which is really powerful) we still need to factor the d=
istribution (and delays surrounding it) part of
computed results for all the nodes

This is an interesting thing to model. Else the concern will continue to li=
nger given the local computation/protection experience in a non-SDN routing=
 model.
Again, in any case some delay MAY  be tolerable as these are alternatives c=
omputed for getting ready for next failure any ways.
--
Uma C.

From: Stewart Bryant [mailto:stbryant@cisco.com]
Sent: Tuesday, December 02, 2014 11:33 PM
To: stephane.litkowski@orange.com; Uma Chunduri; Alia Atlas; Loa Andersson
Cc: mpls@ietf.org; mpls-chairs@tools.ietf.org; draft-atlas-mpls-ldp-mrt@too=
ls.ietf.org; rtgwg@ietf.org
Subject: Re: maturity of the MRT technology

I have been mulling this over for a while and I am wondering
how the current industry debate on SDN vs traditional distributed
routing plays into this.

You could build a  case that whilst there always needs to be a base
topology that needs to be calculated using a traditional distributed
routing protocol (for absolute resilience and bootstrapping) any
domain wide repair topology could be better implemented through
SDN since it benefits from a global perspective.

That would suggest that whilst we might benefit from standardizing
the advertisement of some IPFRR related parameters, and would
certainly benefit from standardization of the YANG models needed
to control the IPFRR subsystem, the method of calculating the
repair topology itself ought to be private to the orchestrator.

The classical argument against this is concern with the time to
reinstate the repair topology after a failure, but I am not sure
how significant this is since (a) normally this would be an incremental
change, and (b) given that we would normally be computing this
on some high end platform it could have the results of any single
failure (or restore) pre-computed.

- Stewart

On 23/11/2014 08:47, stephane.litkowski@orange.com<mailto:stephane.litkowsk=
i@orange.com> wrote:
HI Uma,

> Is this because of domain wide deployment requirements MRT brings-in (as =
elaborated by Stewart?) or you are ok with LFA/rLFA coverage in the network=
?

No, domain-wide deployment is not an issue. The issue I see in MRT (for my =
use case) is unoptimality of the FRR path (at least using lowpoint algorith=
m). But anyway, as I mentioned, I'm not opposed to make MRT progressing at =
all. It's good to have multiple tools.

Best Regards,


From: Uma Chunduri [mailto:uma.chunduri@ericsson.com]
Sent: Friday, November 21, 2014 20:37
To: LITKOWSKI Stephane SCE/IBNF; Alia Atlas; Loa Andersson
Cc: mpls@ietf.org<mailto:mpls@ietf.org>; mpls-chairs@tools.ietf.org<mailto:=
mpls-chairs@tools.ietf.org>; draft-atlas-mpls-ldp-mrt@tools.ietf.org<mailto=
:draft-atlas-mpls-ldp-mrt@tools.ietf.org>; rtgwg@ietf.org<mailto:rtgwg@ietf=
.org>
Subject: RE: maturity of the MRT technology

>I'm not a great supporter of MRT implementation in my network, because it =
does not address correctly my use cases but despite of this,

Is this because of domain wide deployment requirements MRT brings-in (as el=
aborated by Stewart?) or you are ok with LFA/rLFA coverage in the network?

> I deeply think that it's another item in the FRR toolchest (like LFA, rem=
ote LFA ...),
>it will be up to each Service Provider to choose the appropriate technolog=
y based on its own use case/constraints.

I agree with above.  It depends on the particular deployment scenario and a=
pplicability for that network.

--
Uma C.

From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of stephane.litkowski@o=
range.com<mailto:stephane.litkowski@orange.com>
Sent: Friday, November 21, 2014 1:23 AM
To: Alia Atlas; Loa Andersson
Cc: mpls@ietf.org<mailto:mpls@ietf.org>; mpls-chairs@tools.ietf.org<mailto:=
mpls-chairs@tools.ietf.org>; draft-atlas-mpls-ldp-mrt@tools.ietf.org<mailto=
:draft-atlas-mpls-ldp-mrt@tools.ietf.org>; rtgwg@ietf.org<mailto:rtgwg@ietf=
.org>
Subject: Re: [mpls] maturity of the MRT technology

+1

As for all FRR technologies, MRT has pros and cons, and this does not influ=
ence the maturity of the technical solutions. We already had multiple discu=
ssions online and offline on technical details leading now to documents tha=
t are quite detailed and well understood technology (with pros and cons as =
I mentioned). I'm not a great supporter of MRT implementation in my network=
, because it does not address correctly my use cases but despite of this, I=
 deeply think that it's another item in the FRR toolchest (like LFA, remote=
 LFA ...), it will be up to each Service Provider to choose the appropriate=
 technology based on its own use case/constraints. Processing of MRT , IMHO=
, should be done as LFA and other similar technologies so standard track so=
unds good to me.

We already seen much less mature technologies going to standard track and b=
eing RFC without any running code after ...

Best Regards,

Stephane


From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Alia Atlas
Sent: Thursday, November 20, 2014 19:17
To: Loa Andersson
Cc: mpls@ietf.org<mailto:mpls@ietf.org>; mpls-chairs@tools.ietf.org<mailto:=
mpls-chairs@tools.ietf.org>; draft-atlas-mpls-ldp-mrt@tools.ietf.org<mailto=
:draft-atlas-mpls-ldp-mrt@tools.ietf.org>; VIGOUREUX, MARTIN (MARTIN); rtgw=
g@ietf.org<mailto:rtgwg@ietf.org>
Subject: Re: maturity of the MRT technology

Loa,

Without any hats on, I would note:

a) As far as I'm aware, this has seen two independent prototypes implemente=
d.
b) I have not heard any concrete technical concerns.  Stewart and I did spe=
cificallly
discuss MRT this past IETF.  I am, of course, quite interested in hearing a=
ny
concrete technical concerns.

c) I'd be happy seeing this question asked of more drafts :-)

Regards,
Alia


On Tue, Nov 18, 2014 at 7:08 PM, Loa Andersson <loa@pi.nu<mailto:loa@pi.nu>=
> wrote:
Working Groups,

We have don an MPLS-RT of draft-atlas-mpls-ldp-mrt, the reviews has been
posted to the mpls wg mailing list.

In his MPLS-RT review Stewart Bryant says:

"I have concerns about whether or not MRT technology has the  maturity
 expected in the standards track. However that decision needs to be
 taken in RTGWG and MPLS needs to follow their and lead in determining
 the fate and track of this draft. This draft should not be published
 ahead of the drafts that define the technology that it is supporting."

He also says that he see no reason not to go ahead and start the poll to
see if we have consensus to adopt the document as an mpls wg document.

The question Stewart ask is valid, and we'd like input from the rtgwg
and rtgwg chairs (copied on this mail). We will also copy both the
poll for adoption and the wglc to the rtgwg mailing list.

/Loa
mpls wg co-chair
--


Loa Andersson                        email: loa@mail01.huawei.com<mailto:lo=
a@mail01.huawei.com>
Senior MPLS Expert                          loa@pi.nu<mailto:loa@pi.nu>
Huawei Technologies (consultant)     phone: +46 739 81 21 64<tel:%2B46%2073=
9%2081%2021%2064>

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


___________________________________________________________________________=
______________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.



This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and dele=
te this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.

Thank you.

___________________________________________________________________________=
______________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.



This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and dele=
te this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.

Thank you.




_______________________________________________

rtgwg mailing list

rtgwg@ietf.org<mailto: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



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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color: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";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle26
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" 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,<o:p></o:p></s=
pan></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">Great thoughts..<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">Essentially you are sayin=
g use X algorithm &nbsp;(LFA/rLFA/MRT/combination-o- these/some-great-alter=
nate-path-hunting-algorithm) to
<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">compute alternate paths b=
y a controller &nbsp;for each node and program these for link/node failures=
 as per operator choice.<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">Perhaps &nbsp;it&#8217;s =
futuristic but that future may not be that far!!<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">&gt;The classical argument against this is concern w=
ith the time to
<br>
&gt;reinstate the repair topology after a failure, but I am not sure<br>
&gt;how significant this is since (a) normally this would be an incremental=
<br>
&gt;change, and (b) given that we would normally be computing this <br>
&gt;on some high end platform it could have the results of any single<br>
&gt;failure (or restore) pre-computed.<br>
<br>
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1F497D"><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">Given a typical 1000 node=
 network with bunch of links at each node every topology change has to be f=
actored to compute and distribute alternates to all the
 nodes. <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">If we really put the alte=
rnate computation off from each node and centralized at a controller (which=
 is really powerful) we still need to factor the distribution
 (and delays surrounding it) part of <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">computed results for all =
the nodes<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">This is an interesting th=
ing to model. Else the concern will continue to linger given the local comp=
utation/protection experience in a non-SDN routing model.<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">Again, in any case some d=
elay MAY &nbsp;be tolerable as these are alternatives computed for getting =
ready for next failure any ways.<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></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">Uma C.<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 #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;;color:windowtext"> Stewart Bryant [mailto:stbryant@cisco.com]
<br>
<b>Sent:</b> Tuesday, December 02, 2014 11:33 PM<br>
<b>To:</b> stephane.litkowski@orange.com; Uma Chunduri; Alia Atlas; Loa And=
ersson<br>
<b>Cc:</b> mpls@ietf.org; mpls-chairs@tools.ietf.org; draft-atlas-mpls-ldp-=
mrt@tools.ietf.org; rtgwg@ietf.org<br>
<b>Subject:</b> Re: maturity of the MRT technology<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">I have been mulling this over for a while and I am w=
ondering<br>
how the current industry debate on SDN vs traditional distributed<br>
routing plays into this.<br>
<br>
You could build a&nbsp; case that whilst there always needs to be a base <b=
r>
topology that needs to be calculated using a traditional distributed <br>
routing protocol (for absolute resilience and bootstrapping) any <br>
domain wide repair topology could be better implemented through <br>
SDN since it benefits from a global perspective.<br>
<br>
That would suggest that whilst we might benefit from standardizing<br>
the advertisement of some IPFRR related parameters, and would<br>
certainly benefit from standardization of the YANG models needed <br>
to control the IPFRR subsystem, the method of calculating the <br>
repair topology itself ought to be private to the orchestrator.<br>
<br>
The classical argument against this is concern with the time to <br>
reinstate the repair topology after a failure, but I am not sure<br>
how significant this is since (a) normally this would be an incremental<br>
change, and (b) given that we would normally be computing this <br>
on some high end platform it could have the results of any single<br>
failure (or restore) pre-computed.<br>
<br>
- Stewart<br>
<br>
On 23/11/2014 08:47, <a href=3D"mailto:stephane.litkowski@orange.com">steph=
ane.litkowski@orange.com</a> wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">HI Uma,</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt; Is this because of d=
omain wide deployment requirements MRT brings-in (as elaborated by Stewart?=
) or you are ok with LFA/rLFA coverage in the network?</span><o:p></o:p></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">No, domain-wide deploymen=
t is not an issue. The issue I see in MRT (for my use case) is unoptimality=
 of the FRR path (at least using lowpoint algorithm). But
 anyway, as I mentioned, I&#8217;m not opposed to make MRT progressing at a=
ll. It&#8217;s good to have multiple tools.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best Regards,</span><o:p>=
</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Uma Chun=
duri [<a href=3D"mailto:uma.chunduri@ericsson.com">mailto:uma.chunduri@eric=
sson.com</a>]
<br>
<b>Sent:</b> Friday, November 21, 2014 20:37<br>
<b>To:</b> LITKOWSKI Stephane SCE/IBNF; Alia Atlas; Loa Andersson<br>
<b>Cc:</b> <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>; <a href=3D"m=
ailto:mpls-chairs@tools.ietf.org">
mpls-chairs@tools.ietf.org</a>; <a href=3D"mailto:draft-atlas-mpls-ldp-mrt@=
tools.ietf.org">
draft-atlas-mpls-ldp-mrt@tools.ietf.org</a>; <a href=3D"mailto:rtgwg@ietf.o=
rg">rtgwg@ietf.org</a><br>
<b>Subject:</b> RE: maturity of the MRT technology</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;I&#8217;m not a great=
 supporter of MRT implementation in my network, because it does not address=
 correctly my use cases but despite of this,</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Is this because of domain=
 wide deployment requirements MRT brings-in (as elaborated by Stewart?) or =
you are ok with LFA/rLFA coverage in the network?</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt; I deeply think that =
it&#8217;s another item in the FRR toolchest (like LFA, remote LFA &#8230;)=
,
</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;it will be up to each=
 Service Provider to choose the appropriate technology based on its own use=
 case/constraints.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I agree with above. &nbsp=
;It depends on the particular deployment scenario and applicability for tha=
t network.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/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">--</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Uma C.</span><o:p></o:p><=
/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">&nbsp;</span><o:p></o:p><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> mpls [<a=
 href=3D"mailto:mpls-bounces@ietf.org">mailto:mpls-bounces@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:stephane.litkowski@orange.com">stepha=
ne.litkowski@orange.com</a><br>
<b>Sent:</b> Friday, November 21, 2014 1:23 AM<br>
<b>To:</b> Alia Atlas; Loa Andersson<br>
<b>Cc:</b> <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>; <a href=3D"m=
ailto:mpls-chairs@tools.ietf.org">
mpls-chairs@tools.ietf.org</a>; <a href=3D"mailto:draft-atlas-mpls-ldp-mrt@=
tools.ietf.org">
draft-atlas-mpls-ldp-mrt@tools.ietf.org</a>; <a href=3D"mailto:rtgwg@ietf.o=
rg">rtgwg@ietf.org</a><br>
<b>Subject:</b> Re: [mpls] maturity of the MRT technology</span><o:p></o:p>=
</p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#43;1</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">As for all FRR technologi=
es, MRT has pros and cons, and this does not influence the maturity of the =
technical solutions. We already had multiple discussions
 online and offline on technical details leading now to documents that are =
quite detailed and well understood technology (with pros and cons as I ment=
ioned). I&#8217;m not a great supporter of MRT implementation in my network=
, because it does not address correctly
 my use cases but despite of this, I deeply think that it&#8217;s another i=
tem in the FRR toolchest (like LFA, remote LFA &#8230;), it will be up to e=
ach Service Provider to choose the appropriate technology based on its own =
use case/constraints. Processing of MRT , IMHO,
 should be done as LFA and other similar technologies so standard track sou=
nds good to me.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">We already seen much less=
 mature technologies going to standard track and being RFC without any runn=
ing code after &#8230;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best Regards,</span><o:p>=
</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Stephane</span><o:p></o:p=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> rtgwg [<=
a href=3D"mailto:rtgwg-bounces@ietf.org">mailto:rtgwg-bounces@ietf.org</a>]
<b>On Behalf Of </b>Alia Atlas<br>
<b>Sent:</b> Thursday, November 20, 2014 19:17<br>
<b>To:</b> Loa Andersson<br>
<b>Cc:</b> <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>; <a href=3D"m=
ailto:mpls-chairs@tools.ietf.org">
mpls-chairs@tools.ietf.org</a>; <a href=3D"mailto:draft-atlas-mpls-ldp-mrt@=
tools.ietf.org">
draft-atlas-mpls-ldp-mrt@tools.ietf.org</a>; VIGOUREUX, MARTIN (MARTIN); <a=
 href=3D"mailto:rtgwg@ietf.org">
rtgwg@ietf.org</a><br>
<b>Subject:</b> Re: maturity of the MRT technology</span><o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">Loa,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Without any hats on, I would note:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">a) As far as I'm aware, this has seen two independen=
t prototypes implemented.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">b) I have not heard any concrete technical concerns.=
&nbsp; Stewart and I did specificallly<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">discuss MRT this past IETF.&nbsp; I am, of course, q=
uite interested in hearing any<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">concrete technical concerns.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">c) I'd be happy seeing this question asked of more d=
rafts :-)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Alia<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On Tue, Nov 18, 2014 at 7:08 PM, Loa Andersson &lt;<=
a href=3D"mailto:loa@pi.nu" target=3D"_blank">loa@pi.nu</a>&gt; wrote:<o:p>=
</o:p></p>
<p class=3D"MsoNormal">Working Groups,<br>
<br>
We have don an MPLS-RT of draft-atlas-mpls-ldp-mrt, the reviews has been<br=
>
posted to the mpls wg mailing list.<br>
<br>
In his MPLS-RT review Stewart Bryant says:<br>
<br>
&quot;I have concerns about whether or not MRT technology has the&nbsp; mat=
urity<br>
&nbsp;expected in the standards track. However that decision needs to be<br=
>
&nbsp;taken in RTGWG and MPLS needs to follow their and lead in determining=
<br>
&nbsp;the fate and track of this draft. This draft should not be published<=
br>
&nbsp;ahead of the drafts that define the technology that it is supporting.=
&quot;<br>
<br>
He also says that he see no reason not to go ahead and start the poll to<br=
>
see if we have consensus to adopt the document as an mpls wg document.<br>
<br>
The question Stewart ask is valid, and we'd like input from the rtgwg<br>
and rtgwg chairs (copied on this mail). We will also copy both the<br>
poll for adoption and the wglc to the rtgwg mailing list.<br>
<br>
/Loa<br>
mpls wg co-chair<span style=3D"color:#888888"><br>
<span class=3D"hoenzb">-- </span><br>
<br>
<br>
<span class=3D"hoenzb">Loa Andersson&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; email: <a href=3D"mailto:loa@m=
ail01.huawei.com" target=3D"_blank">
loa@mail01.huawei.com</a></span><br>
<span class=3D"hoenzb">Senior MPLS Expert&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a href=3D"mailto:=
loa@pi.nu" target=3D"_blank">
loa@pi.nu</a></span><br>
<span class=3D"hoenzb">Huawei Technologies (consultant)&nbsp; &nbsp; &nbsp;=
phone: <a href=3D"tel:%2B46%20739%2081%2021%2064" target=3D"_blank">
&#43;46 739 81 21 64</a></span><br>
<br>
<span class=3D"hoenzb">_______________________________________________</spa=
n><br>
<span class=3D"hoenzb">rtgwg mailing list</span><br>
<span class=3D"hoenzb"><a href=3D"mailto:rtgwg@ietf.org" target=3D"_blank">=
rtgwg@ietf.org</a></span><br>
<span class=3D"hoenzb"><a href=3D"https://www.ietf.org/mailman/listinfo/rtg=
wg" target=3D"_blank">https://www.ietf.org/mailman/listinfo/rtgwg</a></span=
></span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<pre>______________________________________________________________________=
___________________________________________________<o:p></o:p></pre>
<pre>&nbsp;<o:p></o:p></pre>
<pre>Ce message et ses pieces jointes peuvent contenir des informations con=
fidentielles ou privilegiees et ne doivent donc<o:p></o:p></pre>
<pre>pas etre diffuses, exploites ou copies sans autorisation. Si vous avez=
 recu ce message par erreur, veuillez le signaler<o:p></o:p></pre>
<pre>a l'expediteur et le detruire ainsi que les pieces jointes. Les messag=
es electroniques etant susceptibles d'alteration,<o:p></o:p></pre>
<pre>Orange decline toute responsabilite si ce message a ete altere, deform=
e ou falsifie. Merci.<o:p></o:p></pre>
<pre>&nbsp;<o:p></o:p></pre>
<pre>This message and its attachments may contain confidential or privilege=
d information that may be protected by law;<o:p></o:p></pre>
<pre>they should not be distributed, used or copied without authorisation.<=
o:p></o:p></pre>
<pre>If you have received this email in error, please notify the sender and=
 delete this message and its attachments.<o:p></o:p></pre>
<pre>As emails may be altered, Orange is not liable for messages that have =
been modified, changed or falsified.<o:p></o:p></pre>
<pre>Thank you.<o:p></o:p></pre>
<pre>______________________________________________________________________=
___________________________________________________<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Ce message et ses pieces jointes peuvent contenir des informations con=
fidentielles ou privilegiees et ne doivent donc<o:p></o:p></pre>
<pre>pas etre diffuses, exploites ou copies sans autorisation. Si vous avez=
 recu ce message par erreur, veuillez le signaler<o:p></o:p></pre>
<pre>a l'expediteur et le detruire ainsi que les pieces jointes. Les messag=
es electroniques etant susceptibles d'alteration,<o:p></o:p></pre>
<pre>Orange decline toute responsabilite si ce message a ete altere, deform=
e ou falsifie. Merci.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>This message and its attachments may contain confidential or privilege=
d information that may be protected by law;<o:p></o:p></pre>
<pre>they should not be distributed, used or copied without authorisation.<=
o:p></o:p></pre>
<pre>If you have received this email in error, please notify the sender and=
 delete this message and its attachments.<o:p></o:p></pre>
<pre>As emails may be altered, Orange is not liable for messages that have =
been modified, changed or falsified.<o:p></o:p></pre>
<pre>Thank you.<o:p></o:p></pre>
<p class=3D"MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>rtgwg mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><o:p></o:p></pre>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/rtgwg">https://www.ie=
tf.org/mailman/listinfo/rtgwg</a><o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>For corporate legal information go to:<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre><a href=3D"http://www.cisco.com/web/about/doing_business/legal/cri/ind=
ex.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html=
</a><o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
</div>
</body>
</html>

--_000_1B502206DFA0C544B7A60469152008633F47FA39eusaamb105erics_--


From nobody Wed Dec  3 06:48:46 2014
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 D61DF1A1B01; Wed,  3 Dec 2014 06:48:44 -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 VyYz4Ur8UFoY; Wed,  3 Dec 2014 06:48:40 -0800 (PST)
Received: from mail-yk0-x230.google.com (mail-yk0-x230.google.com [IPv6:2607:f8b0:4002:c07::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46E5D1A1B22; Wed,  3 Dec 2014 06:48:40 -0800 (PST)
Received: by mail-yk0-f176.google.com with SMTP id q200so6932898ykb.35 for <multiple recipients>; Wed, 03 Dec 2014 06:48:39 -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=NClGK0epbcUAVdkFN16cuX0d7lU9wNo/enpw9CpOqYE=; b=FnLEmaJE9xfveQkNJwyzzAwZxut/6qrX/V2KH/DFbVY20YhToo2ORMdNPUcrkT6Wb1 dEYU5uJ5PB8/VzTbwSW+PgyYUC0xvs1nY7fz/aPLQIvZz6A7ZZ2tbtXVMElTx7ww6gZC ciNCSfZhEcilmAlr+hrRRWZ1V4nXStreyj+4I/Ql1yHhzLJGP66fZzzEZe3NQQCPXoVI sorBOhkmBz1uz5i86tCVdbuypy97FxZ8b9dHW01k5SrGfBnJ/4AVoX7TP//L3dHzW5wv vNJSWapInCEzVhQoYB6EGj64X7axuFaQqADfOHA9ikYtjffePuwH1Lxc13qlqhFeaS/z 8zDQ==
MIME-Version: 1.0
X-Received: by 10.170.202.196 with SMTP id t187mr7357695yke.36.1417618119424;  Wed, 03 Dec 2014 06:48:39 -0800 (PST)
Received: by 10.170.172.86 with HTTP; Wed, 3 Dec 2014 06:48:39 -0800 (PST)
In-Reply-To: <547EBC95.6020608@cisco.com>
References: <546BDF65.2030203@pi.nu> <CAG4d1rfRuyzJS9HjHN_yH69PGa_V=iPeyvxxxFUyKMK_gUqBhA@mail.gmail.com> <3682_1416561775_546F046F_3682_717_1_9E32478DFA9976438E7A22F69B08FF92177BF0@OPEXCLILM34.corporate.adroot.infra.ftgroup> <1B502206DFA0C544B7A60469152008633F44A97E@eusaamb105.ericsson.se> <18727_1416732463_54719F2F_18727_12486_1_9E32478DFA9976438E7A22F69B08FF92178256@OPEXCLILM34.corporate.adroot.infra.ftgroup> <547EBC95.6020608@cisco.com>
Date: Wed, 3 Dec 2014 09:48:39 -0500
Message-ID: <CAG4d1rehdWJchjGPwT8_LS_n92tg0KCVYcR9Cp35qjQfbKMSiQ@mail.gmail.com>
Subject: Re: maturity of the MRT technology
From: Alia Atlas <akatlas@gmail.com>
To: Stewart Bryant <stbryant@cisco.com>
Content-Type: multipart/alternative; boundary=001a1139d06a6f8337050950f03c
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/c_PEo6lwhRRLhLPIigAE5cetyzc
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "draft-atlas-mpls-ldp-mrt@tools.ietf.org" <draft-atlas-mpls-ldp-mrt@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, 03 Dec 2014 14:48:45 -0000

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

Stewart,

It's always fun to speculate about what technology the future may hold.
Certainly a way to ease deployment of a new technology like MRT could
include using a single device to compute and distribute the alternates;
partially
deployment is also quite reasonable to handle parts of the network topology
that don't have full LFA protection.

The question of needing to distribute alternates from a centralized locatio=
n
ties back to how reasonable is the single failure assumption?  I haven't
seen
any recent studies indicating that the mean time between failures has
increased.
So - there's the question of whether fast-reroute provides enough
protection to
be worth the added complexity if the protection can't be reapplied within,
say,
5 seconds.

Regards,
Alia

On Wed, Dec 3, 2014 at 2:32 AM, Stewart Bryant <stbryant@cisco.com> wrote:

>  I have been mulling this over for a while and I am wondering
> how the current industry debate on SDN vs traditional distributed
> routing plays into this.
>
> You could build a  case that whilst there always needs to be a base
> topology that needs to be calculated using a traditional distributed
> routing protocol (for absolute resilience and bootstrapping) any
> domain wide repair topology could be better implemented through
> SDN since it benefits from a global perspective.
>
> That would suggest that whilst we might benefit from standardizing
> the advertisement of some IPFRR related parameters, and would
> certainly benefit from standardization of the YANG models needed
> to control the IPFRR subsystem, the method of calculating the
> repair topology itself ought to be private to the orchestrator.
>
> The classical argument against this is concern with the time to
> reinstate the repair topology after a failure, but I am not sure
> how significant this is since (a) normally this would be an incremental
> change, and (b) given that we would normally be computing this
> on some high end platform it could have the results of any single
> failure (or restore) pre-computed.
>
> - Stewart
>
>
> On 23/11/2014 08:47, stephane.litkowski@orange.com wrote:
>
>  HI Uma,
>
>
>
> > Is this because of domain wide deployment requirements MRT brings-in
> (as elaborated by Stewart?) or you are ok with LFA/rLFA coverage in the
> network?
>
>
>
> No, domain-wide deployment is not an issue. The issue I see in MRT (for m=
y
> use case) is unoptimality of the FRR path (at least using lowpoint
> algorithm). But anyway, as I mentioned, I=E2=80=99m not opposed to make M=
RT
> progressing at all. It=E2=80=99s good to have multiple tools.
>
>
>
> Best Regards,
>
>
>
>
>
> *From:* Uma Chunduri [mailto:uma.chunduri@ericsson.com
> <uma.chunduri@ericsson.com>]
> *Sent:* Friday, November 21, 2014 20:37
> *To:* LITKOWSKI Stephane SCE/IBNF; Alia Atlas; Loa Andersson
> *Cc:* mpls@ietf.org; mpls-chairs@tools.ietf.org;
> draft-atlas-mpls-ldp-mrt@tools.ietf.org; rtgwg@ietf.org
> *Subject:* RE: maturity of the MRT technology
>
>
>
> >I=E2=80=99m not a great supporter of MRT implementation in my network, b=
ecause it
> does not address correctly my use cases but despite of this,
>
>
>
> Is this because of domain wide deployment requirements MRT brings-in (as
> elaborated by Stewart?) or you are ok with LFA/rLFA coverage in the netwo=
rk?
>
>
>
> > I deeply think that it=E2=80=99s another item in the FRR toolchest (lik=
e LFA,
> remote LFA =E2=80=A6),
>
> >it will be up to each Service Provider to choose the appropriate
> technology based on its own use case/constraints.
>
>
>
> I agree with above.  It depends on the particular deployment scenario and
> applicability for that network.
>
>
>
> --
>
> Uma C.
>
>
>
> *From:* mpls [mailto:mpls-bounces@ietf.org <mpls-bounces@ietf.org>] *On
> Behalf Of *stephane.litkowski@orange.com
> *Sent:* Friday, November 21, 2014 1:23 AM
> *To:* Alia Atlas; Loa Andersson
> *Cc:* mpls@ietf.org; mpls-chairs@tools.ietf.org;
> draft-atlas-mpls-ldp-mrt@tools.ietf.org; rtgwg@ietf.org
> *Subject:* Re: [mpls] maturity of the MRT technology
>
>
>
> +1
>
>
>
> As for all FRR technologies, MRT has pros and cons, and this does not
> influence the maturity of the technical solutions. We already had multipl=
e
> discussions online and offline on technical details leading now to
> documents that are quite detailed and well understood technology (with pr=
os
> and cons as I mentioned). I=E2=80=99m not a great supporter of MRT implem=
entation
> in my network, because it does not address correctly my use cases but
> despite of this, I deeply think that it=E2=80=99s another item in the FRR=
 toolchest
> (like LFA, remote LFA =E2=80=A6), it will be up to each Service Provider =
to choose
> the appropriate technology based on its own use case/constraints.
> Processing of MRT , IMHO, should be done as LFA and other similar
> technologies so standard track sounds good to me.
>
>
>
> We already seen much less mature technologies going to standard track and
> being RFC without any running code after =E2=80=A6
>
>
>
> Best Regards,
>
>
>
> Stephane
>
>
>
>
>
> *From:* rtgwg [mailto:rtgwg-bounces@ietf.org <rtgwg-bounces@ietf.org>] *O=
n
> Behalf Of *Alia Atlas
> *Sent:* Thursday, November 20, 2014 19:17
> *To:* Loa Andersson
> *Cc:* mpls@ietf.org; mpls-chairs@tools.ietf.org;
> draft-atlas-mpls-ldp-mrt@tools.ietf.org; VIGOUREUX, MARTIN (MARTIN);
> rtgwg@ietf.org
> *Subject:* Re: maturity of the MRT technology
>
>
>
> Loa,
>
>
>
> Without any hats on, I would note:
>
>
>
> a) As far as I'm aware, this has seen two independent prototypes
> implemented.
>
> b) I have not heard any concrete technical concerns.  Stewart and I did
> specificallly
>
> discuss MRT this past IETF.  I am, of course, quite interested in hearing
> any
>
> concrete technical concerns.
>
>
>
> c) I'd be happy seeing this question asked of more drafts :-)
>
>
>
> Regards,
>
> Alia
>
>
>
>
>
> On Tue, Nov 18, 2014 at 7:08 PM, Loa Andersson <loa@pi.nu> wrote:
>
> Working Groups,
>
> We have don an MPLS-RT of draft-atlas-mpls-ldp-mrt, the reviews has been
> posted to the mpls wg mailing list.
>
> In his MPLS-RT review Stewart Bryant says:
>
> "I have concerns about whether or not MRT technology has the  maturity
>  expected in the standards track. However that decision needs to be
>  taken in RTGWG and MPLS needs to follow their and lead in determining
>  the fate and track of this draft. This draft should not be published
>  ahead of the drafts that define the technology that it is supporting."
>
> He also says that he see no reason not to go ahead and start the poll to
> see if we have consensus to adopt the document as an mpls wg document.
>
> The question Stewart ask is valid, and we'd like input from the rtgwg
> and rtgwg chairs (copied on this mail). We will also copy both the
> poll for adoption and the wglc to the rtgwg mailing list.
>
> /Loa
> mpls wg co-chair
> --
>
>
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>
>
>
> _________________________________________________________________________=
________________________________________________
>
>
>
> Ce message et ses pieces jointes peuvent contenir des informations confid=
entielles ou privilegiees et ne doivent donc
>
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez re=
cu ce message par erreur, veuillez le signaler
>
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages =
electroniques etant susceptibles d'alteration,
>
> Orange decline toute responsabilite si ce message a ete altere, deforme o=
u falsifie. Merci.
>
>
>
> This message and its attachments may contain confidential or privileged i=
nformation that may be protected by law;
>
> they should not be distributed, used or copied without authorisation.
>
> If you have received this email in error, please notify the sender and de=
lete this message and its attachments.
>
> As emails may be altered, Orange is not liable for messages that have bee=
n modified, changed or falsified.
>
> Thank you.
>
>  ________________________________________________________________________=
_________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confid=
entielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez re=
cu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages =
electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme o=
u falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged i=
nformation that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and de=
lete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have bee=
n modified, changed or falsified.
> Thank you.
>
>
>
> _______________________________________________
> rtgwg mailing listrtgwg@ietf.orghttps://www.ietf.org/mailman/listinfo/rtg=
wg
>
>
>
> --
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>

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

<div dir=3D"ltr">Stewart,<div><br></div><div>It&#39;s always fun to specula=
te about what technology the future may hold.</div><div>Certainly a way to =
ease deployment of a new technology like MRT could</div><div>include using =
a single device to compute and distribute the alternates; partially</div><d=
iv>deployment is also quite reasonable to handle parts of the network topol=
ogy</div><div>that don&#39;t have full LFA protection.</div><div><br></div>=
<div>The question of needing to distribute alternates from a centralized lo=
cation</div><div>ties back to how reasonable is the single failure assumpti=
on?=C2=A0 I haven&#39;t seen</div><div>any recent studies indicating that t=
he mean time between failures has increased.</div><div>So - there&#39;s the=
 question of whether fast-reroute provides enough protection to</div><div>b=
e worth the added complexity if the protection can&#39;t be reapplied withi=
n, say,</div><div>5 seconds.</div><div><br></div><div>Regards,</div><div>Al=
ia</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, D=
ec 3, 2014 at 2:32 AM, Stewart Bryant <span dir=3D"ltr">&lt;<a href=3D"mail=
to:stbryant@cisco.com" target=3D"_blank">stbryant@cisco.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div>I have been mulling this over for a
      while and I am wondering<br>
      how the current industry debate on SDN vs traditional distributed<br>
      routing plays into this.<br>
      <br>
      You could build a=C2=A0 case that whilst there always needs to be a
      base <br>
      topology that needs to be calculated using a traditional
      distributed <br>
      routing protocol (for absolute resilience and bootstrapping) any <br>
      domain wide repair topology could be better implemented through <br>
      SDN since it benefits from a global perspective.<br>
      <br>
      That would suggest that whilst we might benefit from standardizing<br=
>
      the advertisement of some IPFRR related parameters, and would<br>
      certainly benefit from standardization of the YANG models needed <br>
      to control the IPFRR subsystem, the method of calculating the <br>
      repair topology itself ought to be private to the orchestrator.<br>
      <br>
      The classical argument against this is concern with the time to <br>
      reinstate the repair topology after a failure, but I am not sure<br>
      how significant this is since (a) normally this would be an
      incremental<br>
      change, and (b) given that we would normally be computing this <br>
      on some high end platform it could have the results of any single<br>
      failure (or restore) pre-computed.<span class=3D"HOEnZb"><font color=
=3D"#888888"><br>
      <br>
      - Stewart</font></span><div><div class=3D"h5"><br>
      <br>
      On 23/11/2014 08:47, <a href=3D"mailto:stephane.litkowski@orange.com"=
 target=3D"_blank">stephane.litkowski@orange.com</a> wrote:<br>
    </div></div></div><div><div class=3D"h5">
    <blockquote type=3D"cite">
     =20
     =20
     =20
      <div>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">HI
            Uma,<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&gt;</span><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&=
quot;;color:#1f497d">
            Is this because of domain wide deployment requirements MRT
            brings-in (as elaborated by Stewart?) or you are ok with
            LFA/rLFA coverage in the network?<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">No,
            domain-wide deployment is not an issue. The issue I see in
            MRT (for my use case) is unoptimality of the FRR path (at
            least using lowpoint algorithm). But anyway, as I mentioned,
            I=E2=80=99m not opposed to make MRT progressing at all. It=E2=
=80=99s good to
            have multiple tools.<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Best
            Regards,<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <div>
          <div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:=
3.0pt 0in 0in 0in">
            <p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span sty=
le=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot=
;">
                Uma Chunduri [<a href=3D"mailto:uma.chunduri@ericsson.com" =
target=3D"_blank">mailto:uma.chunduri@ericsson.com</a>]
                <br>
                <b>Sent:</b> Friday, November 21, 2014 20:37<br>
                <b>To:</b> LITKOWSKI Stephane SCE/IBNF; Alia Atlas; Loa
                Andersson<br>
                <b>Cc:</b> <a href=3D"mailto:mpls@ietf.org" target=3D"_blan=
k">mpls@ietf.org</a>; <a href=3D"mailto:mpls-chairs@tools.ietf.org" target=
=3D"_blank">mpls-chairs@tools.ietf.org</a>;
                <a href=3D"mailto:draft-atlas-mpls-ldp-mrt@tools.ietf.org" =
target=3D"_blank">draft-atlas-mpls-ldp-mrt@tools.ietf.org</a>; <a href=3D"m=
ailto:rtgwg@ietf.org" target=3D"_blank">rtgwg@ietf.org</a><br>
                <b>Subject:</b> RE: maturity of the MRT technology<u></u><u=
></u></span></p>
          </div>
        </div>
        <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&gt;I=E2=80=99m
            not a great supporter of MRT implementation in my network,
            because it does not address correctly my use cases but
            despite of this,<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Is
            this because of domain wide deployment requirements MRT
            brings-in (as elaborated by Stewart?) or you are ok with
            LFA/rLFA coverage in the network?<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&gt;
            I deeply think that it=E2=80=99s another item in the FRR toolch=
est
            (like LFA, remote LFA =E2=80=A6),
            <u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&gt;it
            will be up to each Service Provider to choose the
            appropriate technology based on its own use
            case/constraints.<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">I
            agree with above.=C2=A0 It depends on the particular deployment
            scenario and applicability for that network.<u></u><u></u></spa=
n></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <div>
          <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">--<u></u><u></u=
></span></p>
          <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Uma
              C.<u></u><u></u></span></p>
        </div>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <div>
          <div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:=
3.0pt 0in 0in 0in">
            <p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span sty=
le=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot=
;">
                mpls [<a href=3D"mailto:mpls-bounces@ietf.org" target=3D"_b=
lank">mailto:mpls-bounces@ietf.org</a>]
                <b>On Behalf Of </b><a href=3D"mailto:stephane.litkowski@or=
ange.com" target=3D"_blank">stephane.litkowski@orange.com</a><br>
                <b>Sent:</b> Friday, November 21, 2014 1:23 AM<br>
                <b>To:</b> Alia Atlas; Loa Andersson<br>
                <b>Cc:</b> <a href=3D"mailto:mpls@ietf.org" target=3D"_blan=
k">mpls@ietf.org</a>; <a href=3D"mailto:mpls-chairs@tools.ietf.org" target=
=3D"_blank">
                  mpls-chairs@tools.ietf.org</a>; <a href=3D"mailto:draft-a=
tlas-mpls-ldp-mrt@tools.ietf.org" target=3D"_blank">
                  draft-atlas-mpls-ldp-mrt@tools.ietf.org</a>; <a href=3D"m=
ailto:rtgwg@ietf.org" target=3D"_blank">rtgwg@ietf.org</a><br>
                <b>Subject:</b> Re: [mpls] maturity of the MRT
                technology<u></u><u></u></span></p>
          </div>
        </div>
        <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">+1<u></u><u></u><=
/span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">As
            for all FRR technologies, MRT has pros and cons, and this
            does not influence the maturity of the technical solutions.
            We already had multiple discussions online and offline on
            technical details leading now to documents that are quite
            detailed and well understood technology (with pros and cons
            as I mentioned). I=E2=80=99m not a great supporter of MRT
            implementation in my network, because it does not address
            correctly my use cases but despite of this, I deeply think
            that it=E2=80=99s another item in the FRR toolchest (like LFA,
            remote LFA =E2=80=A6), it will be up to each Service Provider t=
o
            choose the appropriate technology based on its own use
            case/constraints. Processing of MRT , IMHO, should be done
            as LFA and other similar technologies so standard track
            sounds good to me.<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">We
            already seen much less mature technologies going to standard
            track and being RFC without any running code after =E2=80=A6<u>=
</u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Best
            Regards,<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Stephane<u></u><u=
></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-fami=
ly:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=
=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"=
>
            rtgwg [<a href=3D"mailto:rtgwg-bounces@ietf.org" target=3D"_bla=
nk">mailto:rtgwg-bounces@ietf.org</a>]
            <b>On Behalf Of </b>Alia Atlas<br>
            <b>Sent:</b> Thursday, November 20, 2014 19:17<br>
            <b>To:</b> Loa Andersson<br>
            <b>Cc:</b> <a href=3D"mailto:mpls@ietf.org" target=3D"_blank">m=
pls@ietf.org</a>; <a href=3D"mailto:mpls-chairs@tools.ietf.org" target=3D"_=
blank">
              mpls-chairs@tools.ietf.org</a>; <a href=3D"mailto:draft-atlas=
-mpls-ldp-mrt@tools.ietf.org" target=3D"_blank">
              draft-atlas-mpls-ldp-mrt@tools.ietf.org</a>; VIGOUREUX,
            MARTIN (MARTIN); <a href=3D"mailto:rtgwg@ietf.org" target=3D"_b=
lank">
              rtgwg@ietf.org</a><br>
            <b>Subject:</b> Re: maturity of the MRT technology<u></u><u></u=
></span></p>
        <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
        <div>
          <p class=3D"MsoNormal">Loa,<u></u><u></u></p>
          <div>
            <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
          </div>
          <div>
            <p class=3D"MsoNormal">Without any hats on, I would note:<u></u=
><u></u></p>
          </div>
          <div>
            <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
          </div>
          <div>
            <p class=3D"MsoNormal">a) As far as I&#39;m aware, this has see=
n
              two independent prototypes implemented.<u></u><u></u></p>
          </div>
          <div>
            <p class=3D"MsoNormal">b) I have not heard any concrete
              technical concerns.=C2=A0 Stewart and I did specificallly<u><=
/u><u></u></p>
          </div>
          <div>
            <p class=3D"MsoNormal">discuss MRT this past IETF.=C2=A0 I am, =
of
              course, quite interested in hearing any<u></u><u></u></p>
          </div>
          <div>
            <p class=3D"MsoNormal">concrete technical concerns.<u></u><u></=
u></p>
          </div>
          <div>
            <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
          </div>
          <div>
            <p class=3D"MsoNormal">c) I&#39;d be happy seeing this question
              asked of more drafts :-)<u></u><u></u></p>
          </div>
          <div>
            <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
          </div>
          <div>
            <p class=3D"MsoNormal">Regards,<u></u><u></u></p>
          </div>
          <div>
            <p class=3D"MsoNormal">Alia<u></u><u></u></p>
          </div>
          <div>
            <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
          </div>
        </div>
        <div>
          <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
          <div>
            <p class=3D"MsoNormal">On Tue, Nov 18, 2014 at 7:08 PM, Loa
              Andersson &lt;<a href=3D"mailto:loa@pi.nu" target=3D"_blank">=
loa@pi.nu</a>&gt;
              wrote:<u></u><u></u></p>
            <p class=3D"MsoNormal">Working Groups,<br>
              <br>
              We have don an MPLS-RT of draft-atlas-mpls-ldp-mrt, the
              reviews has been<br>
              posted to the mpls wg mailing list.<br>
              <br>
              In his MPLS-RT review Stewart Bryant says:<br>
              <br>
              &quot;I have concerns about whether or not MRT technology has
              the=C2=A0 maturity<br>
              =C2=A0expected in the standards track. However that decision
              needs to be<br>
              =C2=A0taken in RTGWG and MPLS needs to follow their and lead =
in
              determining<br>
              =C2=A0the fate and track of this draft. This draft should not
              be published<br>
              =C2=A0ahead of the drafts that define the technology that it =
is
              supporting.&quot;<br>
              <br>
              He also says that he see no reason not to go ahead and
              start the poll to<br>
              see if we have consensus to adopt the document as an mpls
              wg document.<br>
              <br>
              The question Stewart ask is valid, and we&#39;d like input
              from the rtgwg<br>
              and rtgwg chairs (copied on this mail). We will also copy
              both the<br>
              poll for adoption and the wglc to the rtgwg mailing list.<br>
              <br>
              /Loa<br>
              mpls wg co-chair<span style=3D"color:#888888"><br>
                <span>-- </span><br>
                <br>
                <br>
                <span>Loa Andersson=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0
                  =C2=A0 email: <a href=3D"mailto:loa@mail01.huawei.com" ta=
rget=3D"_blank">
                    loa@mail01.huawei.com</a></span><br>
                <span>Senior MPLS Expert=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0
                  =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:loa@pi.nu" =
target=3D"_blank">
                    loa@pi.nu</a></span><br>
                <span>Huawei Technologies (consultant)=C2=A0 =C2=A0
                  =C2=A0phone: <a href=3D"tel:%2B46%20739%2081%2021%2064" t=
arget=3D"_blank">
                    +46 739 81 21 64</a></span><br>
                <br>
                <span>_______________________________________________</span=
><br>
                <span>rtgwg mailing list</span><br>
                <span><a href=3D"mailto:rtgwg@ietf.org" target=3D"_blank">r=
tgwg@ietf.org</a></span><br>
                <span><a href=3D"https://www.ietf.org/mailman/listinfo/rtgw=
g" target=3D"_blank">https://www.ietf.org/mailman/listinfo/rtgwg</a></span>=
</span><u></u><u></u></p>
          </div>
          <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
        </div>
        <pre>______________________________________________________________=
___________________________________________________________<u></u><u></u></=
pre>
        <pre><u></u>=C2=A0<u></u></pre>
        <pre>Ce message et ses pieces jointes peuvent contenir des informat=
ions confidentielles ou privilegiees et ne doivent donc<u></u><u></u></pre>
        <pre>pas etre diffuses, exploites ou copies sans autorisation. Si v=
ous avez recu ce message par erreur, veuillez le signaler<u></u><u></u></pr=
e>
        <pre>a l&#39;expediteur et le detruire ainsi que les pieces jointes=
. Les messages electroniques etant susceptibles d&#39;alteration,<u></u><u>=
</u></pre>
        <pre>Orange decline toute responsabilite si ce message a ete altere=
, deforme ou falsifie. Merci.<u></u><u></u></pre>
        <pre><u></u>=C2=A0<u></u></pre>
        <pre>This message and its attachments may contain confidential or p=
rivileged information that may be protected by law;<u></u><u></u></pre>
        <pre>they should not be distributed, used or copied without authori=
sation.<u></u><u></u></pre>
        <pre>If you have received this email in error, please notify the se=
nder and delete this message and its attachments.<u></u><u></u></pre>
        <pre>As emails may be altered, Orange is not liable for messages th=
at have been modified, changed or falsified.<u></u><u></u></pre>
        <pre>Thank you.<u></u><u></u></pre>
      </div>
      <pre>________________________________________________________________=
_________________________________________________________

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

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.
</pre>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
rtgwg mailing list
<a href=3D"mailto:rtgwg@ietf.org" target=3D"_blank">rtgwg@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/rtgwg" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/rtgwg</a>
</pre>
    </blockquote>
    <br>
    <br>
    </div></div><span class=3D""><pre cols=3D"72">--=20
For corporate legal information go to:

<a href=3D"http://www.cisco.com/web/about/doing_business/legal/cri/index.ht=
ml" target=3D"_blank">http://www.cisco.com/web/about/doing_business/legal/c=
ri/index.html</a>

</pre>
  </span></div>

</blockquote></div><br></div></div>

--001a1139d06a6f8337050950f03c--


From nobody Wed Dec  3 08:25:39 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3AA11A89A7; Wed,  3 Dec 2014 08:25:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PFwq6Jm9vsA7; Wed,  3 Dec 2014 08:25:24 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 923A81A87D0; Wed,  3 Dec 2014 08:23:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=45173; q=dns/txt; s=iport; t=1417623801; x=1418833401; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=mcFhFfsgNb24TRh/uSolTjREHp54DOjWweGyjXbCs0o=; b=hHHf2RTIqj70ym2gzAdULEpwPeIecKYSjNFS/Fjw9ZYmTRGOHFNlpk2p YmI8bJ0EgsY+KulLzkknKzq4IiBsyJUhaskzIdfC4dZxHb9hYpZcVGpBu 9EyFifNP5SxLj3xJ4iW5T3Xpzo4mh3eFbo1RKUczspe0HcsVqnlqbwnet M=;
X-IronPort-AV: E=Sophos;i="5.07,508,1413244800";  d="scan'208,217";a="259276322"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 03 Dec 2014 16:23:17 +0000
Received: from [64.103.108.91] (dhcp-bdlk10-data-vlan301-64-103-108-91.cisco.com [64.103.108.91]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id sB3GNGwt018764; Wed, 3 Dec 2014 16:23:16 GMT
Message-ID: <547F38F4.3030908@cisco.com>
Date: Wed, 03 Dec 2014 16:23:16 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Alia Atlas <akatlas@gmail.com>
Subject: Re: maturity of the MRT technology
References: <546BDF65.2030203@pi.nu>	<CAG4d1rfRuyzJS9HjHN_yH69PGa_V=iPeyvxxxFUyKMK_gUqBhA@mail.gmail.com>	<3682_1416561775_546F046F_3682_717_1_9E32478DFA9976438E7A22F69B08FF92177BF0@OPEXCLILM34.corporate.adroot.infra.ftgroup>	<1B502206DFA0C544B7A60469152008633F44A97E@eusaamb105.ericsson.se>	<18727_1416732463_54719F2F_18727_12486_1_9E32478DFA9976438E7A22F69B08FF92178256@OPEXCLILM34.corporate.adroot.infra.ftgroup>	<547EBC95.6020608@cisco.com> <CAG4d1rehdWJchjGPwT8_LS_n92tg0KCVYcR9Cp35qjQfbKMSiQ@mail.gmail.com>
In-Reply-To: <CAG4d1rehdWJchjGPwT8_LS_n92tg0KCVYcR9Cp35qjQfbKMSiQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------040601010802080000030908"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/kSm1-n6a74FQbEXxvcEbvra2qo8
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "draft-atlas-mpls-ldp-mrt@tools.ietf.org" <draft-atlas-mpls-ldp-mrt@tools.ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 16:25:32 -0000

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

On 03/12/2014 14:48, Alia Atlas wrote:
> Stewart,
>
> It's always fun to speculate about what technology the future may hold.
Well SDN is more current design phase than future, although it could be
redesign of old technology since this is the way that transport networks
have always worked.

> Certainly a way to ease deployment of a new technology like MRT could
> include using a single device to compute and distribute the 
> alternates; partially
> deployment is also quite reasonable to handle parts of the network 
> topology
> that don't have full LFA protection.
Of course this does not just apply to MRT, it applies to any/all of the
algorithms.
>
> The question of needing to distribute alternates from a centralized 
> location
> ties back to how reasonable is the single failure assumption?
Are you talking about failure of the SDN controller or the need to deal 
with
multiple concurrent network failures? SDN controller reliability is a
subject in itself, which I assume to be getting focus by the SDN teams.
> I haven't seen
> any recent studies indicating that the mean time between failures has 
> increased.
> So - there's the question of whether fast-reroute provides enough 
> protection to
> be worth the added complexity if the protection can't be reapplied 
> within, say,
> 5 seconds.

How realistic is that requirement?

My understanding is that MRFB in the types of networks that need IPFRR 
is weeks
rather than seconds, and large parts of the network are disjoint WRT to 
repair
strategy, so the first priority is to remove any repairs that would loop 
as a result
of invocation of a repair in the presence of a missing link,  second is to
replace those repairs and third is to re-optimize the repairs, but I 
would be
surprised if that needed to be completed in seconds.

We have an existence proof for some of the above in transport networks which
can't react in that sort of time and rely use an SDN approach.

- Stewart

>
> Regards,
> Alia
>
> On Wed, Dec 3, 2014 at 2:32 AM, Stewart Bryant <stbryant@cisco.com 
> <mailto:stbryant@cisco.com>> wrote:
>
>     I have been mulling this over for a while and I am wondering
>     how the current industry debate on SDN vs traditional distributed
>     routing plays into this.
>
>     You could build a  case that whilst there always needs to be a base
>     topology that needs to be calculated using a traditional distributed
>     routing protocol (for absolute resilience and bootstrapping) any
>     domain wide repair topology could be better implemented through
>     SDN since it benefits from a global perspective.
>
>     That would suggest that whilst we might benefit from standardizing
>     the advertisement of some IPFRR related parameters, and would
>     certainly benefit from standardization of the YANG models needed
>     to control the IPFRR subsystem, the method of calculating the
>     repair topology itself ought to be private to the orchestrator.
>
>     The classical argument against this is concern with the time to
>     reinstate the repair topology after a failure, but I am not sure
>     how significant this is since (a) normally this would be an
>     incremental
>     change, and (b) given that we would normally be computing this
>     on some high end platform it could have the results of any single
>     failure (or restore) pre-computed.
>
>     - Stewart
>
>
>     On 23/11/2014 08:47, stephane.litkowski@orange.com
>     <mailto:stephane.litkowski@orange.com> wrote:
>>
>>     HI Uma,
>>
>>     >Is this because of domain wide deployment requirements MRT
>>     brings-in (as elaborated by Stewart?) or you are ok with LFA/rLFA
>>     coverage in the network?
>>
>>     No, domain-wide deployment is not an issue. The issue I see in
>>     MRT (for my use case) is unoptimality of the FRR path (at least
>>     using lowpoint algorithm). But anyway, as I mentioned, I’m not
>>     opposed to make MRT progressing at all. It’s good to have
>>     multiple tools.
>>
>>     Best Regards,
>>
>>     *From:*Uma Chunduri [mailto:uma.chunduri@ericsson.com]
>>     *Sent:* Friday, November 21, 2014 20:37
>>     *To:* LITKOWSKI Stephane SCE/IBNF; Alia Atlas; Loa Andersson
>>     *Cc:* mpls@ietf.org <mailto:mpls@ietf.org>;
>>     mpls-chairs@tools.ietf.org <mailto:mpls-chairs@tools.ietf.org>;
>>     draft-atlas-mpls-ldp-mrt@tools.ietf.org
>>     <mailto:draft-atlas-mpls-ldp-mrt@tools.ietf.org>; rtgwg@ietf.org
>>     <mailto:rtgwg@ietf.org>
>>     *Subject:* RE: maturity of the MRT technology
>>
>>     >I’m not a great supporter of MRT implementation in my network,
>>     because it does not address correctly my use cases but despite of
>>     this,
>>
>>     Is this because of domain wide deployment requirements MRT
>>     brings-in (as elaborated by Stewart?) or you are ok with LFA/rLFA
>>     coverage in the network?
>>
>>     > I deeply think that it’s another item in the FRR toolchest (like
>>     LFA, remote LFA …),
>>
>>     >it will be up to each Service Provider to choose the appropriate
>>     technology based on its own use case/constraints.
>>
>>     I agree with above.  It depends on the particular deployment
>>     scenario and applicability for that network.
>>
>>     --
>>
>>     Uma C.
>>
>>     *From:*mpls [mailto:mpls-bounces@ietf.org] *On Behalf Of
>>     *stephane.litkowski@orange.com <mailto:stephane.litkowski@orange.com>
>>     *Sent:* Friday, November 21, 2014 1:23 AM
>>     *To:* Alia Atlas; Loa Andersson
>>     *Cc:* mpls@ietf.org <mailto:mpls@ietf.org>;
>>     mpls-chairs@tools.ietf.org <mailto:mpls-chairs@tools.ietf.org>;
>>     draft-atlas-mpls-ldp-mrt@tools.ietf.org
>>     <mailto:draft-atlas-mpls-ldp-mrt@tools.ietf.org>; rtgwg@ietf.org
>>     <mailto:rtgwg@ietf.org>
>>     *Subject:* Re: [mpls] maturity of the MRT technology
>>
>>     +1
>>
>>     As for all FRR technologies, MRT has pros and cons, and this does
>>     not influence the maturity of the technical solutions. We already
>>     had multiple discussions online and offline on technical details
>>     leading now to documents that are quite detailed and well
>>     understood technology (with pros and cons as I mentioned). I’m
>>     not a great supporter of MRT implementation in my network,
>>     because it does not address correctly my use cases but despite of
>>     this, I deeply think that it’s another item in the FRR toolchest
>>     (like LFA, remote LFA …), it will be up to each Service Provider
>>     to choose the appropriate technology based on its own use
>>     case/constraints. Processing of MRT , IMHO, should be done as LFA
>>     and other similar technologies so standard track sounds good to me.
>>
>>     We already seen much less mature technologies going to standard
>>     track and being RFC without any running code after …
>>
>>     Best Regards,
>>
>>     Stephane
>>
>>     *From:*rtgwg [mailto:rtgwg-bounces@ietf.org] *On Behalf Of *Alia
>>     Atlas
>>     *Sent:* Thursday, November 20, 2014 19:17
>>     *To:* Loa Andersson
>>     *Cc:* mpls@ietf.org <mailto:mpls@ietf.org>;
>>     mpls-chairs@tools.ietf.org <mailto:mpls-chairs@tools.ietf.org>;
>>     draft-atlas-mpls-ldp-mrt@tools.ietf.org
>>     <mailto:draft-atlas-mpls-ldp-mrt@tools.ietf.org>; VIGOUREUX,
>>     MARTIN (MARTIN); rtgwg@ietf.org <mailto:rtgwg@ietf.org>
>>     *Subject:* Re: maturity of the MRT technology
>>
>>     Loa,
>>
>>     Without any hats on, I would note:
>>
>>     a) As far as I'm aware, this has seen two independent prototypes
>>     implemented.
>>
>>     b) I have not heard any concrete technical concerns.  Stewart and
>>     I did specificallly
>>
>>     discuss MRT this past IETF.  I am, of course, quite interested in
>>     hearing any
>>
>>     concrete technical concerns.
>>
>>     c) I'd be happy seeing this question asked of more drafts :-)
>>
>>     Regards,
>>
>>     Alia
>>
>>     On Tue, Nov 18, 2014 at 7:08 PM, Loa Andersson <loa@pi.nu
>>     <mailto:loa@pi.nu>> wrote:
>>
>>     Working Groups,
>>
>>     We have don an MPLS-RT of draft-atlas-mpls-ldp-mrt, the reviews
>>     has been
>>     posted to the mpls wg mailing list.
>>
>>     In his MPLS-RT review Stewart Bryant says:
>>
>>     "I have concerns about whether or not MRT technology has the 
>>     maturity
>>      expected in the standards track. However that decision needs to be
>>      taken in RTGWG and MPLS needs to follow their and lead in
>>     determining
>>      the fate and track of this draft. This draft should not be published
>>      ahead of the drafts that define the technology that it is
>>     supporting."
>>
>>     He also says that he see no reason not to go ahead and start the
>>     poll to
>>     see if we have consensus to adopt the document as an mpls wg
>>     document.
>>
>>     The question Stewart ask is valid, and we'd like input from the rtgwg
>>     and rtgwg chairs (copied on this mail). We will also copy both the
>>     poll for adoption and the wglc to the rtgwg mailing list.
>>
>>     /Loa
>>     mpls wg co-chair
>>     -- 
>>
>>
>>     Loa Andersson   email: loa@mail01.huawei.com
>>     <mailto:loa@mail01.huawei.com>
>>     Senior MPLS Expert loa@pi.nu <mailto:loa@pi.nu>
>>     Huawei Technologies (consultant)    phone: +46 739 81 21 64
>>     <tel:%2B46%20739%2081%2021%2064>
>>
>>     _______________________________________________
>>     rtgwg mailing list
>>     rtgwg@ietf.org <mailto:rtgwg@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/rtgwg
>>
>>     _________________________________________________________________________________________________________________________
>>       
>>     Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>>     pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>>     a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>>     Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>>       
>>     This message and its attachments may contain confidential or privileged information that may be protected by law;
>>     they should not be distributed, used or copied without authorisation.
>>     If you have received this email in error, please notify the sender and delete this message and its attachments.
>>     As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>>     Thank you.
>>     _________________________________________________________________________________________________________________________
>>
>>     Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>>     pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>>     a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>>     Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>>
>>     This message and its attachments may contain confidential or privileged information that may be protected by law;
>>     they should not be distributed, used or copied without authorisation.
>>     If you have received this email in error, please notify the sender and delete this message and its attachments.
>>     As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>>     Thank you.
>>
>>
>>     _______________________________________________
>>     rtgwg mailing list
>>     rtgwg@ietf.org  <mailto: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
>
>


-- 
For corporate legal information go to:

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


--------------040601010802080000030908
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 03/12/2014 14:48, Alia Atlas wrote:<br>
    </div>
    <blockquote
cite="mid:CAG4d1rehdWJchjGPwT8_LS_n92tg0KCVYcR9Cp35qjQfbKMSiQ@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div dir="ltr">Stewart,
        <div><br>
        </div>
        <div>It's always fun to speculate about what technology the
          future may hold.</div>
      </div>
    </blockquote>
    Well SDN is more current design phase than future, although it could
    be<br>
    redesign of old technology since this is the way that transport
    networks<br>
    have always worked.<br>
    <br>
    <blockquote
cite="mid:CAG4d1rehdWJchjGPwT8_LS_n92tg0KCVYcR9Cp35qjQfbKMSiQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>Certainly a way to ease deployment of a new technology like
          MRT could</div>
        <div>include using a single device to compute and distribute the
          alternates; partially</div>
        <div>deployment is also quite reasonable to handle parts of the
          network topology</div>
        <div>that don't have full LFA protection.</div>
      </div>
    </blockquote>
    Of course this does not just apply to MRT, it applies to any/all of
    the <br>
    algorithms.<br>
    <blockquote
cite="mid:CAG4d1rehdWJchjGPwT8_LS_n92tg0KCVYcR9Cp35qjQfbKMSiQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br>
        </div>
        <div>The question of needing to distribute alternates from a
          centralized location</div>
        <div>ties back to how reasonable is the single failure
          assumption?  </div>
      </div>
    </blockquote>
    Are you talking about failure of the SDN controller or the need to
    deal with <br>
    multiple concurrent network failures? SDN controller reliability is
    a <br>
    subject in itself, which I assume to be getting focus by the SDN
    teams.<br>
    <blockquote
cite="mid:CAG4d1rehdWJchjGPwT8_LS_n92tg0KCVYcR9Cp35qjQfbKMSiQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>I haven't seen</div>
        <div>any recent studies indicating that the mean time between
          failures has increased.</div>
        <div>So - there's the question of whether fast-reroute provides
          enough protection to</div>
        <div>be worth the added complexity if the protection can't be
          reapplied within, say,</div>
        <div>5 seconds.</div>
      </div>
    </blockquote>
    <br>
    How realistic is that requirement?<br>
    <br>
    My understanding is that MRFB in the types of networks that need
    IPFRR is weeks <br>
    rather than seconds, and large parts of the network are disjoint WRT
    to repair<br>
    strategy, so the first priority is to remove any repairs that would
    loop as a result<br>
    of invocation of a repair in the presence of a missing link,  second
    is to<br>
    replace those repairs and third is to re-optimize the repairs, but I
    would be<br>
    surprised if that needed to be completed in seconds.<br>
    <br>
    We have an existence proof for some of the above in transport
    networks which<br>
    can't react in that sort of time and rely use an SDN approach.<br>
    <br>
    - Stewart<br>
    <br>
    <blockquote
cite="mid:CAG4d1rehdWJchjGPwT8_LS_n92tg0KCVYcR9Cp35qjQfbKMSiQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br>
        </div>
        <div>Regards,</div>
        <div>Alia</div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Wed, Dec 3, 2014 at 2:32 AM,
            Stewart Bryant <span dir="ltr">&lt;<a
                moz-do-not-send="true" href="mailto:stbryant@cisco.com"
                target="_blank">stbryant@cisco.com</a>&gt;</span> wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF">
                <div>I have been mulling this over for a while and I am
                  wondering<br>
                  how the current industry debate on SDN vs traditional
                  distributed<br>
                  routing plays into this.<br>
                  <br>
                  You could build a  case that whilst there always needs
                  to be a base <br>
                  topology that needs to be calculated using a
                  traditional distributed <br>
                  routing protocol (for absolute resilience and
                  bootstrapping) any <br>
                  domain wide repair topology could be better
                  implemented through <br>
                  SDN since it benefits from a global perspective.<br>
                  <br>
                  That would suggest that whilst we might benefit from
                  standardizing<br>
                  the advertisement of some IPFRR related parameters,
                  and would<br>
                  certainly benefit from standardization of the YANG
                  models needed <br>
                  to control the IPFRR subsystem, the method of
                  calculating the <br>
                  repair topology itself ought to be private to the
                  orchestrator.<br>
                  <br>
                  The classical argument against this is concern with
                  the time to <br>
                  reinstate the repair topology after a failure, but I
                  am not sure<br>
                  how significant this is since (a) normally this would
                  be an incremental<br>
                  change, and (b) given that we would normally be
                  computing this <br>
                  on some high end platform it could have the results of
                  any single<br>
                  failure (or restore) pre-computed.<span class="HOEnZb"><font
                      color="#888888"><br>
                      <br>
                      - Stewart</font></span>
                  <div>
                    <div class="h5"><br>
                      <br>
                      On 23/11/2014 08:47, <a moz-do-not-send="true"
                        href="mailto:stephane.litkowski@orange.com"
                        target="_blank">stephane.litkowski@orange.com</a>
                      wrote:<br>
                    </div>
                  </div>
                </div>
                <div>
                  <div class="h5">
                    <blockquote type="cite">
                      <div>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">HI

                            Uma,</span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&gt;</span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">
                            Is this because of domain wide deployment
                            requirements MRT brings-in (as elaborated by
                            Stewart?) or you are ok with LFA/rLFA
                            coverage in the network?</span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">No,

                            domain-wide deployment is not an issue. The
                            issue I see in MRT (for my use case) is
                            unoptimality of the FRR path (at least using
                            lowpoint algorithm). But anyway, as I
                            mentioned, I’m not opposed to make MRT
                            progressing at all. It’s good to have
                            multiple tools.</span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Best

                            Regards,</span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                        <div>
                          <div style="border:none;border-top:solid
                            #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
                            <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                                Uma Chunduri [<a moz-do-not-send="true"
href="mailto:uma.chunduri@ericsson.com" target="_blank">mailto:uma.chunduri@ericsson.com</a>]
                                <br>
                                <b>Sent:</b> Friday, November 21, 2014
                                20:37<br>
                                <b>To:</b> LITKOWSKI Stephane SCE/IBNF;
                                Alia Atlas; Loa Andersson<br>
                                <b>Cc:</b> <a moz-do-not-send="true"
                                  href="mailto:mpls@ietf.org"
                                  target="_blank">mpls@ietf.org</a>; <a
                                  moz-do-not-send="true"
                                  href="mailto:mpls-chairs@tools.ietf.org"
                                  target="_blank">mpls-chairs@tools.ietf.org</a>;
                                <a moz-do-not-send="true"
                                  href="mailto:draft-atlas-mpls-ldp-mrt@tools.ietf.org"
                                  target="_blank">draft-atlas-mpls-ldp-mrt@tools.ietf.org</a>;
                                <a moz-do-not-send="true"
                                  href="mailto:rtgwg@ietf.org"
                                  target="_blank">rtgwg@ietf.org</a><br>
                                <b>Subject:</b> RE: maturity of the MRT
                                technology</span></p>
                          </div>
                        </div>
                        <p class="MsoNormal"> </p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&gt;I’m

                            not a great supporter of MRT implementation
                            in my network, because it does not address
                            correctly my use cases but despite of this,</span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Is

                            this because of domain wide deployment
                            requirements MRT brings-in (as elaborated by
                            Stewart?) or you are ok with LFA/rLFA
                            coverage in the network?</span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&gt;

                            I deeply think that it’s another item in the
                            FRR toolchest (like LFA, remote LFA …), </span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&gt;it

                            will be up to each Service Provider to
                            choose the appropriate technology based on
                            its own use case/constraints.</span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">I
                            agree with above.  It depends on the
                            particular deployment scenario and
                            applicability for that network.</span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                        <div>
                          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">--</span></p>
                          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Uma

                              C.</span></p>
                        </div>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                        <div>
                          <div style="border:none;border-top:solid
                            #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
                            <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                                mpls [<a moz-do-not-send="true"
                                  href="mailto:mpls-bounces@ietf.org"
                                  target="_blank">mailto:mpls-bounces@ietf.org</a>]
                                <b>On Behalf Of </b><a
                                  moz-do-not-send="true"
                                  href="mailto:stephane.litkowski@orange.com"
                                  target="_blank">stephane.litkowski@orange.com</a><br>
                                <b>Sent:</b> Friday, November 21, 2014
                                1:23 AM<br>
                                <b>To:</b> Alia Atlas; Loa Andersson<br>
                                <b>Cc:</b> <a moz-do-not-send="true"
                                  href="mailto:mpls@ietf.org"
                                  target="_blank">mpls@ietf.org</a>; <a
                                  moz-do-not-send="true"
                                  href="mailto:mpls-chairs@tools.ietf.org"
                                  target="_blank">
                                  mpls-chairs@tools.ietf.org</a>; <a
                                  moz-do-not-send="true"
                                  href="mailto:draft-atlas-mpls-ldp-mrt@tools.ietf.org"
                                  target="_blank">
                                  draft-atlas-mpls-ldp-mrt@tools.ietf.org</a>;
                                <a moz-do-not-send="true"
                                  href="mailto:rtgwg@ietf.org"
                                  target="_blank">rtgwg@ietf.org</a><br>
                                <b>Subject:</b> Re: [mpls] maturity of
                                the MRT technology</span></p>
                          </div>
                        </div>
                        <p class="MsoNormal"> </p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">+1</span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">As

                            for all FRR technologies, MRT has pros and
                            cons, and this does not influence the
                            maturity of the technical solutions. We
                            already had multiple discussions online and
                            offline on technical details leading now to
                            documents that are quite detailed and well
                            understood technology (with pros and cons as
                            I mentioned). I’m not a great supporter of
                            MRT implementation in my network, because it
                            does not address correctly my use cases but
                            despite of this, I deeply think that it’s
                            another item in the FRR toolchest (like LFA,
                            remote LFA …), it will be up to each Service
                            Provider to choose the appropriate
                            technology based on its own use
                            case/constraints. Processing of MRT , IMHO,
                            should be done as LFA and other similar
                            technologies so standard track sounds good
                            to me.</span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">We

                            already seen much less mature technologies
                            going to standard track and being RFC
                            without any running code after …</span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Best

                            Regards,</span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Stephane</span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                        <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                            rtgwg [<a moz-do-not-send="true"
                              href="mailto:rtgwg-bounces@ietf.org"
                              target="_blank">mailto:rtgwg-bounces@ietf.org</a>]
                            <b>On Behalf Of </b>Alia Atlas<br>
                            <b>Sent:</b> Thursday, November 20, 2014
                            19:17<br>
                            <b>To:</b> Loa Andersson<br>
                            <b>Cc:</b> <a moz-do-not-send="true"
                              href="mailto:mpls@ietf.org"
                              target="_blank">mpls@ietf.org</a>; <a
                              moz-do-not-send="true"
                              href="mailto:mpls-chairs@tools.ietf.org"
                              target="_blank">
                              mpls-chairs@tools.ietf.org</a>; <a
                              moz-do-not-send="true"
                              href="mailto:draft-atlas-mpls-ldp-mrt@tools.ietf.org"
                              target="_blank">
                              draft-atlas-mpls-ldp-mrt@tools.ietf.org</a>;
                            VIGOUREUX, MARTIN (MARTIN); <a
                              moz-do-not-send="true"
                              href="mailto:rtgwg@ietf.org"
                              target="_blank"> rtgwg@ietf.org</a><br>
                            <b>Subject:</b> Re: maturity of the MRT
                            technology</span></p>
                        <p class="MsoNormal"> </p>
                        <div>
                          <p class="MsoNormal">Loa,</p>
                          <div>
                            <p class="MsoNormal"> </p>
                          </div>
                          <div>
                            <p class="MsoNormal">Without any hats on, I
                              would note:</p>
                          </div>
                          <div>
                            <p class="MsoNormal"> </p>
                          </div>
                          <div>
                            <p class="MsoNormal">a) As far as I'm aware,
                              this has seen two independent prototypes
                              implemented.</p>
                          </div>
                          <div>
                            <p class="MsoNormal">b) I have not heard any
                              concrete technical concerns.  Stewart and
                              I did specificallly</p>
                          </div>
                          <div>
                            <p class="MsoNormal">discuss MRT this past
                              IETF.  I am, of course, quite interested
                              in hearing any</p>
                          </div>
                          <div>
                            <p class="MsoNormal">concrete technical
                              concerns.</p>
                          </div>
                          <div>
                            <p class="MsoNormal"> </p>
                          </div>
                          <div>
                            <p class="MsoNormal">c) I'd be happy seeing
                              this question asked of more drafts :-)</p>
                          </div>
                          <div>
                            <p class="MsoNormal"> </p>
                          </div>
                          <div>
                            <p class="MsoNormal">Regards,</p>
                          </div>
                          <div>
                            <p class="MsoNormal">Alia</p>
                          </div>
                          <div>
                            <p class="MsoNormal"> </p>
                          </div>
                        </div>
                        <div>
                          <p class="MsoNormal"> </p>
                          <div>
                            <p class="MsoNormal">On Tue, Nov 18, 2014 at
                              7:08 PM, Loa Andersson &lt;<a
                                moz-do-not-send="true"
                                href="mailto:loa@pi.nu" target="_blank">loa@pi.nu</a>&gt;

                              wrote:</p>
                            <p class="MsoNormal">Working Groups,<br>
                              <br>
                              We have don an MPLS-RT of
                              draft-atlas-mpls-ldp-mrt, the reviews has
                              been<br>
                              posted to the mpls wg mailing list.<br>
                              <br>
                              In his MPLS-RT review Stewart Bryant says:<br>
                              <br>
                              "I have concerns about whether or not MRT
                              technology has the  maturity<br>
                               expected in the standards track. However
                              that decision needs to be<br>
                               taken in RTGWG and MPLS needs to follow
                              their and lead in determining<br>
                               the fate and track of this draft. This
                              draft should not be published<br>
                               ahead of the drafts that define the
                              technology that it is supporting."<br>
                              <br>
                              He also says that he see no reason not to
                              go ahead and start the poll to<br>
                              see if we have consensus to adopt the
                              document as an mpls wg document.<br>
                              <br>
                              The question Stewart ask is valid, and
                              we'd like input from the rtgwg<br>
                              and rtgwg chairs (copied on this mail). We
                              will also copy both the<br>
                              poll for adoption and the wglc to the
                              rtgwg mailing list.<br>
                              <br>
                              /Loa<br>
                              mpls wg co-chair<span
                                style="color:#888888"><br>
                                <span>-- </span><br>
                                <br>
                                <br>
                                <span>Loa Andersson                     
                                    email: <a moz-do-not-send="true"
                                    href="mailto:loa@mail01.huawei.com"
                                    target="_blank">
                                    loa@mail01.huawei.com</a></span><br>
                                <span>Senior MPLS Expert               
                                            <a moz-do-not-send="true"
                                    href="mailto:loa@pi.nu"
                                    target="_blank"> loa@pi.nu</a></span><br>
                                <span>Huawei Technologies (consultant) 
                                     phone: <a moz-do-not-send="true"
                                    href="tel:%2B46%20739%2081%2021%2064"
                                    target="_blank"> +46 739 81 21 64</a></span><br>
                                <br>
                                <span>_______________________________________________</span><br>
                                <span>rtgwg mailing list</span><br>
                                <span><a moz-do-not-send="true"
                                    href="mailto:rtgwg@ietf.org"
                                    target="_blank">rtgwg@ietf.org</a></span><br>
                                <span><a moz-do-not-send="true"
                                    href="https://www.ietf.org/mailman/listinfo/rtgwg"
                                    target="_blank">https://www.ietf.org/mailman/listinfo/rtgwg</a></span></span></p>
                          </div>
                          <p class="MsoNormal"> </p>
                        </div>
                        <pre>_________________________________________________________________________________________________________________________</pre>
                        <pre> </pre>
                        <pre>Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc</pre>
                        <pre>pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler</pre>
                        <pre>a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,</pre>
                        <pre>Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.</pre>
                        <pre> </pre>
                        <pre>This message and its attachments may contain confidential or privileged information that may be protected by law;</pre>
                        <pre>they should not be distributed, used or copied without authorisation.</pre>
                        <pre>If you have received this email in error, please notify the sender and delete this message and its attachments.</pre>
                        <pre>As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.</pre>
                        <pre>Thank you.</pre>
                      </div>
                      <pre>_________________________________________________________________________________________________________________________

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

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</pre>
                      <br>
                      <fieldset></fieldset>
                      <br>
                      <pre>_______________________________________________
rtgwg mailing list
<a moz-do-not-send="true" href="mailto:rtgwg@ietf.org" target="_blank">rtgwg@ietf.org</a>
<a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/rtgwg" target="_blank">https://www.ietf.org/mailman/listinfo/rtgwg</a>
</pre>
                    </blockquote>
                    <br>
                    <br>
                  </div>
                </div>
                <span class="">
                  <pre cols="72">-- 
For corporate legal information go to:

<a moz-do-not-send="true" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html" target="_blank">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a>

</pre>
                </span></div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

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

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

--------------040601010802080000030908--


From nobody Wed Dec  3 09:27:46 2014
Return-Path: <cfilsfil@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 A6E031A1DBE for <rtgwg@ietfa.amsl.com>; Wed,  3 Dec 2014 09:27:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WX4i79yjxUpe for <rtgwg@ietfa.amsl.com>; Wed,  3 Dec 2014 09:27:41 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09D291A6FD8 for <rtgwg@ietf.org>; Wed,  3 Dec 2014 09:27:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5002; q=dns/txt; s=iport; t=1417627659; x=1418837259; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=33ZETW3rFDznEBJECsMuSsVzw0QvZ145UNUkwgwEamg=; b=A/qpQo1zf/F0asCfTES22wKsaOcbgKEQ10KAs0Jft9SA1NZ6Lp/KtWU4 aRG9E1YSUmGG1GmCqqC+x1FjGkxgFaMU0sN3AWJR5nX5yonAN6IQFy4WX aHqRdjVK4IeKZ82UM861N9cYc4sUOnOsLjVQxIUF6r0R/g/N3ZJ7oP5/N w=;
X-IronPort-AV: E=Sophos;i="5.07,509,1413244800"; d="scan'208";a="255186283"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 03 Dec 2014 17:27:36 +0000
Received: from [10.61.194.205] ([10.61.194.205]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id sB3HRZjl003632; Wed, 3 Dec 2014 17:27:35 GMT
Message-ID: <547F4807.3010300@cisco.com>
Date: Wed, 03 Dec 2014 18:27:35 +0100
From: Clarence Filsfils <cfilsfil@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: stephane.litkowski@orange.com, "skraza@cisco.com" <skraza@cisco.com>, "Jeff.Tantsura@ericsson.com" <Jeff.Tantsura@ericsson.com>, rtgwg@ietf.org
Subject: Re: FW: Working Group last call on draft-ietf-rtgwg-lfa-manageability - IPR
References: <D08664E9.78999%jeff.tantsura@ericsson.com> <9614_1415780667_5463193A_9614_11139_1_9E32478DFA9976438E7A22F69B08FF921751B1@OPEXCLILM34.corporate.adroot.infra.ftgroup> <21070_1417605291_547EF0AB_21070_2612_1_9E32478DFA9976438E7A22F69B08FF920C73A3BD@OPEXCLILM34.corporate.adroot.infra.ftgroup> <547F3B54.5010709@cisco.com>
In-Reply-To: <547F3B54.5010709@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/h7-8DfrT3euIgKQMq8iGqn7TOsA
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, 03 Dec 2014 17:27:43 -0000

Jeff,

I am aware of this disclosure:

https://datatracker.ietf.org/ipr/2196/

Cheers,
Clarence


>> -----Original Message-----
>> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of
>> stephane.litkowski@orange.com
>> Sent: Wednesday, November 12, 2014 09:24
>> To: Jeff Tantsura; rtgwg@ietf.org
>> Subject: RE: Working Group last call on
>> draft-ietf-rtgwg-lfa-manageability - IPR
>>
>> Hi Jeff,
>>
>> I'm not aware of any IPR related to this draft.
>>
>> Stephane
>>
>>
>> -----Original Message-----
>> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Jeff Tantsura
>> Sent: Monday, November 10, 2014 21:54
>> To: rtgwg@ietf.org
>> Subject: Working Group last call on draft-ietf-rtgwg-lfa-manageability
>> - IPR
>>
>> All,
>>
>> 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.  The draft will not progress
>> (pending the results of the WGLC) until we have received a response
>> from each author.
>>
>>
>> In addition, we wanted to take this opportunity to remind the entire
>> WG that the duty of disclosure is NOT limited to authors:
>>
>>     (c) in order for the working group and the rest of the IETF to have
>>         the information needed to make an informed decision about the use
>>         of a particular technology, all those contributing to the working
>>         group's discussions must disclose the existence of any IPR the
>>         Contributor or other IETF participant believes Covers or may
>>         ultimately Cover the technology under discussion.  This applies
>>         to both Contributors and other participants, and applies whether
>>         they contribute in person, via email or by other means.  The
>>         requirement applies to all IPR of the participant, the
>>         participant's employer, sponsor, or others represented by the
>>         participants, that is reasonably and personally known to the
>>         participant.  No patent search is required.
>>
>> RFC 3979 also points out disclosure must be "as soon as reasonably
>> possible":
>>
>>     The IPR disclosure required pursuant to section 6.1.1 must be made as
>>     soon as reasonably possible after the Contribution is published in an
>>     Internet Draft unless the required disclosure is already on file.
>>
>> Thank you!
>>
>>
>>
>> Cheers,
>> Jeff
>>
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
>>
>> _________________________________________________________________________________________________________________________
>>
>>
>> Ce message et ses pieces jointes peuvent contenir des informations
>> confidentielles ou privilegiees et ne doivent donc pas etre diffuses,
>> exploites ou copies sans autorisation. Si vous avez recu ce message
>> par erreur, veuillez le signaler a l'expediteur et le detruire ainsi
>> que les pieces jointes. Les messages electroniques etant susceptibles
>> d'alteration, Orange decline toute responsabilite si ce message a ete
>> altere, deforme ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or
>> privileged information that may be protected by law; they should not
>> be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and
>> delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have
>> been modified, changed or falsified.
>> Thank you.
>>
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
>>
>> _________________________________________________________________________________________________________________________
>>
>>
>> Ce message et ses pieces jointes peuvent contenir des informations
>> confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
>> recu ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les
>> messages electroniques etant susceptibles d'alteration,
>> Orange decline toute responsabilite si ce message a ete altere,
>> deforme ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or
>> privileged information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and
>> delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have
>> been modified, changed or falsified.
>> Thank you.
>>
>> .
>>


From nobody Wed Dec  3 10:01:52 2014
Return-Path: <yakov@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 EE5121A1B35; Wed,  3 Dec 2014 06:25:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RgCLB7Fcg8XF; Wed,  3 Dec 2014 06:25:35 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0763.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::763]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28EBA1A1B2A; Wed,  3 Dec 2014 06:25:35 -0800 (PST)
Received: from CO2PR05CA024.namprd05.prod.outlook.com (10.141.241.152) by DM2PR05MB446.namprd05.prod.outlook.com (10.141.104.142) with Microsoft SMTP Server (TLS) id 15.1.26.15; Wed, 3 Dec 2014 14:25:11 +0000
Received: from BL2FFO11FD051.protection.gbl (2a01:111:f400:7c09::131) by CO2PR05CA024.outlook.office365.com (2a01:111:e400:1429::24) with Microsoft SMTP Server (TLS) id 15.1.31.17 via Frontend Transport; Wed, 3 Dec 2014 14:25:11 +0000
Received: from P-EMF03-SAC.jnpr.net (66.129.239.17) by BL2FFO11FD051.mail.protection.outlook.com (10.173.161.213) with Microsoft SMTP Server (TLS) id 15.1.6.13 via Frontend Transport; Wed, 3 Dec 2014 14:25:11 +0000
Received: from magenta.juniper.net (172.17.27.123) by P-EMF03-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 3 Dec 2014 06:24:56 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id sB3EOtR80359;	Wed, 3 Dec 2014 06:24:55 -0800 (PST)	(envelope-from yakov@juniper.net)
Message-ID: <201412031424.sB3EOtR80359@magenta.juniper.net>
To: <stephane.litkowski@orange.com>
Subject: Re: [mpls] maturity of the MRT technology 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <54478.1417616694.1@juniper.net>
Date: Wed, 3 Dec 2014 06:24:55 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:66.129.239.17; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(52314003)(189002)(24454002)(199003)(51704005)(479174003)(120916001)(99396003)(84676001)(23726002)(87936001)(47776003)(20776003)(64706001)(110136001)(46102003)(77096005)(68736005)(21056001)(102836001)(50986999)(77156002)(62966003)(50466002)(6806004)(19580395003)(19580405001)(44976005)(54356999)(97736003)(46406003)(105596002)(95666004)(86362001)(69596002)(97756001)(16796002)(81156004)(31966008)(106466001)(2351001)(107046002)(92566001)(4396001)(92726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR05MB446; H:P-EMF03-SAC.jnpr.net; FPR:; SPF:SoftFail; MLV:sfv; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR05MB446;
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:DM2PR05MB446;
X-Forefront-PRVS: 0414DF926F
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.17 as permitted sender)
Authentication-Results: spf=softfail (sender IP is 66.129.239.17) smtp.mailfrom=yakov@juniper.net; 
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:DM2PR05MB446;
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/VC52Sa96-JizAxFAJhKbv2g_XDU
X-Mailman-Approved-At: Wed, 03 Dec 2014 10:01:48 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "draft-atlas-mpls-ldp-mrt@tools.ietf.org" <draft-atlas-mpls-ldp-mrt@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, 03 Dec 2014 14:25:37 -0000

Stephane,

On 23/11/2014 08:47, stephane.litkowski@orange.com wrote:
 
> Hi Uma,
>
> >Is this because of domain wide deployment requirements MRT brings-in 
> (as elaborated by Stewart?) or you are ok with LFA/rLFA coverage in 
> the network?
>
> No, domain-wide deployment is not an issue. The issue I see in MRT 
> (for my use case) is unoptimality of the FRR path (at least using 
> lowpoint algorithm). But anyway, as I mentioned, I'm not opposed to 
> make MRT progressing at all. It's good to have multiple tools.

While MRT may result in "unoptimality of the FRR path", why this
unoptimality really matters that much, given that FRR suppose to
be used for only a short period of time until IGP convergence?

Yakov.


From nobody Wed Dec  3 11:59:36 2014
Return-Path: <uma.chunduri@ericsson.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 255911A6FF5; Wed,  3 Dec 2014 11:59:29 -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 CbHy8A_eMryn; Wed,  3 Dec 2014 11:59:26 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E81E31A8998; Wed,  3 Dec 2014 11:59:24 -0800 (PST)
X-AuditID: c6180641-f79916d00000623a-68-547f0f6486af
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 23.24.25146.46F0F745; Wed,  3 Dec 2014 14:25:56 +0100 (CET)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0195.001; Wed, 3 Dec 2014 14:59:23 -0500
From: Uma Chunduri <uma.chunduri@ericsson.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>
Subject: RE: maturity of the MRT technology
Thread-Topic: maturity of the MRT technology
Thread-Index: AQHQA4z1PNuAPA+Nnk6RopB29XnlN5xqKS2AgAD9AACAAFZlEIACxG8AgA+iVYCAAHnUgIAAGm8A///hs7A=
Date: Wed, 3 Dec 2014 19:59:22 +0000
Message-ID: <1B502206DFA0C544B7A60469152008633F48215B@eusaamb105.ericsson.se>
References: <546BDF65.2030203@pi.nu> <CAG4d1rfRuyzJS9HjHN_yH69PGa_V=iPeyvxxxFUyKMK_gUqBhA@mail.gmail.com> <3682_1416561775_546F046F_3682_717_1_9E32478DFA9976438E7A22F69B08FF92177BF0@OPEXCLILM34.corporate.adroot.infra.ftgroup> <1B502206DFA0C544B7A60469152008633F44A97E@eusaamb105.ericsson.se> <18727_1416732463_54719F2F_18727_12486_1_9E32478DFA9976438E7A22F69B08FF92178256@OPEXCLILM34.corporate.adroot.infra.ftgroup> <547EBC95.6020608@cisco.com> <CAG4d1rehdWJchjGPwT8_LS_n92tg0KCVYcR9Cp35qjQfbKMSiQ@mail.gmail.com> <547F38F4.3030908@cisco.com>
In-Reply-To: <547F38F4.3030908@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: multipart/alternative; boundary="_000_1B502206DFA0C544B7A60469152008633F48215Beusaamb105erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrNIsWRmVeSWpSXmKPExsUyuXRPoG4Kf32IwcKJuhafHl5itnh2fhmj xb+5c5gtvl9awmJxa+lKVosLb34zW5x7OofR4uveh6wOHB5Tfm9k9dg56y67x5IlP5k8Wp6d ZPOYNb2NzePL5c9sAWxRXDYpqTmZZalF+nYJXBlNLzYxFWwIqng+4StTA2NPQBcjJ4eEgInE v/v3GCFsMYkL99azgdhCAkcYJR4/4uti5AKylzFKrGu4zQSSYBPQk/g49Sc7iC0ioCsxe8MN RpAiZoGzTBINky+CTRIW0JY4eHEfK0SRjsSFu/OgGpIk3t/ZABZnEVCReLzgENg2XgFfiS9P 9jJBbFvDIrFoy3tmkASngKbE2eeLwYoYgc77fmoN2BXMAuISt57MZ4I4W0BiyZ7zzBC2qMTL x/9YIWwliUlLz7FC1OdL/N/0nx1imaDEyZlPWCYwis5CMmoWkrJZSMpmMXIAxTUl1u/ShyhR lJjS/ZAdwtaQaJ0zlx1ZfAEj+ypGjtLi1LLcdCPDTYzA2D0mwea4g3HBJ8tDjAIcjEo8vAY8 dSFCrIllxZW5hxilOViUxHk1q+cFCwmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamBco3A75sqt d6f3nAj8nfzHNbuwR/WVq8Akjy2R7yMnpq3ZctFtcnASb2q0DtPUM082RJk0xvQxctXVp3IU Xb4VYlfSWxxu4BQyK31dW0ukzqvdnt0mJ1Vt+nvyEwz//4pnDM0Ty5lbvps/fNl3TiXm17m/ OW7s++75+tE6zocJm6eeX3//wV0lluKMREMt5qLiRAAUKZaivgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/JlTBrF8UeowprSICCe2mCEOqyTQ
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "draft-atlas-mpls-ldp-mrt@tools.ietf.org" <draft-atlas-mpls-ldp-mrt@tools.ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 19:59:29 -0000

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

R2V0dGluZyBiYWNrIG9uIHlvdXIgb3JpZ2luYWwgcG9zdCwgYWZ0ZXIgYSBiaXQgb2YgbW9yZSB0
aGlua2luZzoNCg0KUGVyaGFwcyBjZW50cmFsaXplZCBvciBkaXN0cmlidXRlZCBjb21wdXRpbmcg
b2YgcmVwYWlyIHBhdGggYXBwcm9hY2ggcHJvcy9jb25zIGFyZSBpbnRlcmVzdGluZyB0byBkaXNj
dXNzIDsNCg0KPlRoYXQgd291bGQgc3VnZ2VzdCB0aGF0IHdoaWxzdCB3ZSBtaWdodCBiZW5lZml0
IGZyb20gc3RhbmRhcmRpemluZw0KPnRoZSBhZHZlcnRpc2VtZW50IG9mIHNvbWUgSVBGUlIgcmVs
YXRlZCBwYXJhbWV0ZXJzLCBhbmQgd291bGQNCj5jZXJ0YWlubHkgYmVuZWZpdCBmcm9tIHN0YW5k
YXJkaXphdGlvbiBvZiB0aGUgWUFORyBtb2RlbHMgbmVlZGVkDQo+dG8gY29udHJvbCB0aGUgSVBG
UlIgc3Vic3lzdGVtLA0KDQpTdXJlLg0KDQo+dGhlIG1ldGhvZCBvZiBjYWxjdWxhdGluZyB0aGUN
Cj5yZXBhaXIgdG9wb2xvZ3kgaXRzZWxmIG91Z2h0IHRvIGJlIHByaXZhdGUgdG8gdGhlIG9yY2hl
c3RyYXRvci4NCg0KV2hlbiB3ZSBhZ3JlZSB0byBzdGFuZGFyZGl6ZSB0aGUgSVBGUlIgcmVsYXRl
ZCBwYXJhbWV0ZXJzLCBJTU8gaXTigJlzIGltcG9ydGFudCB0byBzdGFuZGFyZGl6ZSB0aGUgcmVs
ZXZhbnQgYWxnb3JpdGhtIHRvbyByZWdhcmRsZXNzIG9mIHdoZXJlIGl04oCZcyB1c2VkLg0KDQpJ
ZiBpdCBpcyB1c2VkIGluIGEgZGlzdHJpYnV0ZWQgbWFubmVyIHRoaXMgcXVlc3Rpb24gaXMgbGVz
cyByZWxldmFudCBhcyBpdOKAmXMgbW9zdGx5ICBtdWx0aS12ZW5kb3IgZGVwbG95bWVudHMuDQoN
CkV2ZW4gd2hlbiBhbiBvcmNoZXN0cmF0b3IgaXMgY29tcHV0aW5nIHVzaW5nIGEgcGFydGljdWxh
ciBhbGdvcml0aG0gSU1PLCBpdOKAmXMgaW1wb3J0YW50IFZlbmRvciBYIGFuZCBWZW5kb3IgWSBv
ZiB0aGUgY29udHJvbGxlciBkbyB0aGUgc2FtZSB0aGluZyBhbmQNCmFsc28gdGhpcyBoYXMgdG8g
YmUgKmNsZWFybHkqIHVuZGVyc3Rvb2QgdG8gdmFsaWRhdGUgKHRvIHNlZSB0aGUgY29ybmVyIGNh
c2VzIGFyZSB3b3JraW5nIGNvcnJlY3QpICBhbmQgZGVidWcgc3R1ZmYsIG9uY2UgZGVwbG95ZWQu
DQoNClByb3ByaWV0YXJ5IHN0dWZmIG1heSBjb21lIHdpdGggdGhlaXIgb3duIGNvc3Qvcmlzay4N
Cg0KLS0NClVtYSBDLg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIg
MiA0IDMgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNv
Tm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAw
MXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIs
InNlcmlmIjsNCgljb2xvcjpibGFjazt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21z
by1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRl
cmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHls
ZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGlu
ZTt9DQpwcmUNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1M
IFByZWZvcm1hdHRlZCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFw
dDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29s
b3I6YmxhY2s7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBkaXYuTXNvQWNldGF0ZQ0K
CXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxvb24gVGV4dCBD
aGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6
OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOmJsYWNr
O30NCnNwYW4uaG9lbnpiDQoJe21zby1zdHlsZS1uYW1lOmhvZW56Yjt9DQpzcGFuLkhUTUxQcmVm
b3JtYXR0ZWRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsN
Cgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0
dGVkIjsNCglmb250LWZhbWlseTpDb25zb2xhczsNCgljb2xvcjpibGFjazt9DQpzcGFuLkJhbGxv
b25UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiQmFsbG9vbiBUZXh0IENoYXIiOw0KCW1zby1z
dHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiQmFsbG9vbiBUZXh0IjsNCglmb250
LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6YmxhY2s7fQ0Kc3Bhbi5FbWFp
bFN0eWxlMjINCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6
IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0
DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBh
Z2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBp
biAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30N
Ci0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6
ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBn
dGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2
OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0t
LT4NCjwvaGVhZD4NCjxib2R5IGJnY29sb3I9IndoaXRlIiBsYW5nPSJFTi1VUyIgbGluaz0iYmx1
ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkdl
dHRpbmcgYmFjayBvbiB5b3VyIG9yaWdpbmFsIHBvc3QsIGFmdGVyIGEgYml0IG9mIG1vcmUgdGhp
bmtpbmc6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjojMUY0OTdEIj5QZXJoYXBzIGNlbnRyYWxpemVkIG9yIGRpc3RyaWJ1dGVkIGNvbXB1
dGluZyBvZiByZXBhaXIgcGF0aCBhcHByb2FjaCBwcm9zL2NvbnMgYXJlIGludGVyZXN0aW5nIHRv
IGRpc2N1c3MgOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxi
cj4NCiZndDtUaGF0IHdvdWxkIHN1Z2dlc3QgdGhhdCB3aGlsc3Qgd2UgbWlnaHQgYmVuZWZpdCBm
cm9tIHN0YW5kYXJkaXppbmc8YnI+DQomZ3Q7dGhlIGFkdmVydGlzZW1lbnQgb2Ygc29tZSBJUEZS
UiByZWxhdGVkIHBhcmFtZXRlcnMsIGFuZCB3b3VsZDxicj4NCiZndDtjZXJ0YWlubHkgYmVuZWZp
dCBmcm9tIHN0YW5kYXJkaXphdGlvbiBvZiB0aGUgWUFORyBtb2RlbHMgbmVlZGVkIDxicj4NCiZn
dDt0byBjb250cm9sIHRoZSBJUEZSUiBzdWJzeXN0ZW0sIDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+U3VyZS48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZndDt0aGUgbWV0aG9kIG9mIGNhbGN1bGF0aW5nIHRo
ZSA8YnI+DQomZ3Q7cmVwYWlyIHRvcG9sb2d5IGl0c2VsZiBvdWdodCB0byBiZSBwcml2YXRlIHRv
IHRoZSBvcmNoZXN0cmF0b3IuPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5
N0QiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6IzFGNDk3RCI+V2hlbiB3ZSBhZ3JlZSB0byBzdGFuZGFyZGl6ZSB0aGUgSVBGUlIgcmVs
YXRlZCBwYXJhbWV0ZXJzLCBJTU8gaXTigJlzIGltcG9ydGFudCB0byBzdGFuZGFyZGl6ZSB0aGUg
cmVsZXZhbnQgYWxnb3JpdGhtIHRvbyByZWdhcmRsZXNzIG9mIHdoZXJlIGl04oCZcyB1c2VkLjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6
IzFGNDk3RCI+SWYgaXQgaXMgdXNlZCBpbiBhIGRpc3RyaWJ1dGVkIG1hbm5lciB0aGlzIHF1ZXN0
aW9uIGlzIGxlc3MgcmVsZXZhbnQgYXMgaXTigJlzIG1vc3RseSAmbmJzcDttdWx0aS12ZW5kb3Ig
ZGVwbG95bWVudHMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90Oztjb2xvcjojMUY0OTdEIj5FdmVuIHdoZW4gYW4gb3JjaGVzdHJhdG9yIGlzIGNvbXB1
dGluZyB1c2luZyBhIHBhcnRpY3VsYXIgYWxnb3JpdGhtIElNTywgaXTigJlzIGltcG9ydGFudCBW
ZW5kb3IgWCBhbmQgVmVuZG9yIFkgb2YgdGhlIGNvbnRyb2xsZXIgZG8gdGhlIHNhbWUgdGhpbmcg
YW5kDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+YWxzbyB0aGlzIGhhcyB0byBiZSAq
PGI+Y2xlYXJseTwvYj4qIHVuZGVyc3Rvb2QgdG8gdmFsaWRhdGUgKHRvIHNlZSB0aGUgY29ybmVy
IGNhc2VzIGFyZSB3b3JraW5nIGNvcnJlY3QpICZuYnNwO2FuZCBkZWJ1ZyBzdHVmZiwgb25jZSBk
ZXBsb3llZC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7O2NvbG9yOiMxRjQ5N0QiPlByb3ByaWV0YXJ5IHN0dWZmIG1heSBjb21lIHdpdGggdGhlaXIg
b3duIGNvc3Qvcmlzay48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4tLTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjoj
MUY0OTdEIj5VbWEgQy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9i
b2R5Pg0KPC9odG1sPg0K

--_000_1B502206DFA0C544B7A60469152008633F48215Beusaamb105erics_--


From nobody Thu Dec  4 02:37:15 2014
Return-Path: <stephane.litkowski@orange.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9589E1A01AA; Thu,  4 Dec 2014 02:37:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OtrPPNTYSfl0; Thu,  4 Dec 2014 02:37:10 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D79D71A0146; Thu,  4 Dec 2014 02:37:09 -0800 (PST)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id EFAD03B4529; Thu,  4 Dec 2014 11:37:07 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.55]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id C36A82380A0; Thu,  4 Dec 2014 11:37:07 +0100 (CET)
Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.149]) by OPEXCLILH03.corporate.adroot.infra.ftgroup ([10.114.31.55]) with mapi id 14.03.0210.002; Thu, 4 Dec 2014 11:37:07 +0100
From: <stephane.litkowski@orange.com>
To: Yakov Rekhter <yakov@juniper.net>
Subject: RE: [mpls] maturity of the MRT technology 
Thread-Topic: [mpls] maturity of the MRT technology 
Thread-Index: AQHQDwT05s13BieLpE2AHYP0TmNrfpx/Oe4w
Date: Thu, 4 Dec 2014 10:37:07 +0000
Message-ID: <29576_1417689427_54803953_29576_3299_1_9E32478DFA9976438E7A22F69B08FF920C73E8FF@OPEXCLILM34.corporate.adroot.infra.ftgroup>
References: <201412031424.sB3EOtR80359@magenta.juniper.net>
In-Reply-To: <201412031424.sB3EOtR80359@magenta.juniper.net>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.12.4.95723
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/y_0oU_MkAT7iAU7CEsn8ZjlwqVw
Cc: "mpls@ietf.org" <mpls@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "draft-atlas-mpls-ldp-mrt@tools.ietf.org" <draft-atlas-mpls-ldp-mrt@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: Thu, 04 Dec 2014 10:37:12 -0000

Hi Yakov,

Thanks to point this important subject.

Consider the case where you have a link failure, it is easy for our custome=
rs to understand that their traffic have been impacted because the traffic =
was crossing the link that has failed.
Now, if to protect this link, we enable FRR and FRR path uses an "uncontrol=
led" path. When the link fails, traffic is switched to FRR path and may use=
 some paths that is not well sized to handle this traffic.
This may create congestion on some links. Congestion will affect traffic th=
at is not directly concerned by the failure, so customer will loss some tra=
ffic. For sure, the congestion duration will be bound to the convergence ti=
me (~seconds), but for some critical applications (that are not essential r=
equiring LLQ -> so QoS may not fully help in this, in customer data class i=
s congestionned), this is not acceptable. And customers cannot understand t=
hat they are impacted by an issue in another region of the world. (It's lik=
e the well known "Butterfly effect" :) )
This problematic is quite similar to the microloop one. Microloops are impa=
cting traffic which is not directly concerned by the failure. And globally =
we already had complains for both issues (FRR using bad path and microloops=
).

Hope it helps to understand our concern.

Best Regards,

Stephane

-----Original Message-----
From: Yakov Rekhter [mailto:yakov@juniper.net]=20
Sent: Wednesday, December 03, 2014 15:25
To: LITKOWSKI Stephane SCE/IBNF
Cc: Uma Chunduri; Alia Atlas; Loa Andersson; mpls@ietf.org; mpls-chairs@too=
ls.ietf.org; draft-atlas-mpls-ldp-mrt@tools.ietf.org; rtgwg@ietf.org
Subject: Re: [mpls] maturity of the MRT technology=20

Stephane,

On 23/11/2014 08:47, stephane.litkowski@orange.com wrote:
=20
> Hi Uma,
>
> >Is this because of domain wide deployment requirements MRT brings-in
> (as elaborated by Stewart?) or you are ok with LFA/rLFA coverage in=20
> the network?
>
> No, domain-wide deployment is not an issue. The issue I see in MRT=20
> (for my use case) is unoptimality of the FRR path (at least using=20
> lowpoint algorithm). But anyway, as I mentioned, I'm not opposed to=20
> make MRT progressing at all. It's good to have multiple tools.

While MRT may result in "unoptimality of the FRR path", why this unoptimali=
ty really matters that much, given that FRR suppose to be used for only a s=
hort period of time until IGP convergence?

Yakov.

___________________________________________________________________________=
______________________________________________

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

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


From nobody Thu Dec  4 05:26:13 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB33A1A1A6D; Thu,  4 Dec 2014 05:26:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sHc9CNlx-_sI; Thu,  4 Dec 2014 05:26:08 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFF611A1A50; Thu,  4 Dec 2014 05:26:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7129; q=dns/txt; s=iport; t=1417699568; x=1418909168; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=K2KkHerU8Z1RR0DQge5LKgJnxK6kuLUEUqEdeZUytu4=; b=FBpvU3o7qurI3I4wWSRjJGMO/yY1Gy5d6ypdp8WQu3i4gxeiMbFSLDQ8 aJJ7PWgDmHq+6TxrT1m4iewj95fq2qddS7j4us4hnKZH2J/pGcav/tOVg NBO5OGlPqYQoUdrQnwQ4o/KK1w8em9kwKGQV3fudSNM0F/lVnRIE48n2m 0=;
X-IronPort-AV: E=Sophos;i="5.07,515,1413244800";  d="scan'208,217";a="261092785"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 04 Dec 2014 13:26:06 +0000
Received: from [64.103.108.115] (dhcp-bdlk10-data-vlan301-64-103-108-115.cisco.com [64.103.108.115]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id sB4DQ2je016433; Thu, 4 Dec 2014 13:26:05 GMT
Message-ID: <548060EA.6070500@cisco.com>
Date: Thu, 04 Dec 2014 13:26:02 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Uma Chunduri <uma.chunduri@ericsson.com>
Subject: Re: maturity of the MRT technology
References: <546BDF65.2030203@pi.nu>	<CAG4d1rfRuyzJS9HjHN_yH69PGa_V=iPeyvxxxFUyKMK_gUqBhA@mail.gmail.com>	<3682_1416561775_546F046F_3682_717_1_9E32478DFA9976438E7A22F69B08FF92177BF0@OPEXCLILM34.corporate.adroot.infra.ftgroup>	<1B502206DFA0C544B7A60469152008633F44A97E@eusaamb105.ericsson.se>	<18727_1416732463_54719F2F_18727_12486_1_9E32478DFA9976438E7A22F69B08FF92178256@OPEXCLILM34.corporate.adroot.infra.ftgroup>	<547EBC95.6020608@cisco.com> <CAG4d1rehdWJchjGPwT8_LS_n92tg0KCVYcR9Cp35qjQfbKMSiQ@mail.gmail.com> <547F38F4.3030908@cisco.com> <1B502206DFA0C544B7A60469152008633F48215B@eusaamb105.ericsson.se>
In-Reply-To: <1B502206DFA0C544B7A60469152008633F48215B@eusaamb105.ericsson.se>
Content-Type: multipart/alternative; boundary="------------070307020802060702090804"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/BgoD_Wl-PG1SwxEcMx7ELVeKN8Y
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "draft-atlas-mpls-ldp-mrt@tools.ietf.org" <draft-atlas-mpls-ldp-mrt@tools.ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 13:26:10 -0000

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

On 03/12/2014 19:59, Uma Chunduri wrote:
>
> >the method of calculating the
> >repair topology itself ought to be private to the orchestrator.
>
> When we agree to standardize the IPFRR related parameters, IMO it’s 
> important to standardize the relevant algorithm too regardless of 
> where it’s used.
>
> If it is used in a distributed manner this question is less relevant 
> as it’s mostly  multi-vendor deployments.
>
> Even when an orchestrator is computing using a particular algorithm 
> IMO, it’s important Vendor X and Vendor Y of the controller do the 
> same thing and
>
> also this has to be **clearly** understood to validate (to see the 
> corner cases are working correct)  and debug stuff, once deployed.
>
> Proprietary stuff may come with their own cost/risk.
>
I would appreciate hearing the operator's perspective(s) on this.

Will we see two vendor's controllers operate over the same set of nodes 
such that identical behaviour is required, or is this an area where we 
are likely to see customization to execute the repair in a way that best 
suits the specifics of the network and the applicable business model?

Stewart

--------------070307020802060702090804
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 03/12/2014 19:59, Uma Chunduri
      wrote:<br>
    </div>
    <blockquote
cite="mid:1B502206DFA0C544B7A60469152008633F48215B@eusaamb105.ericsson.se"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color: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";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.hoenzb
	{mso-style-name:hoenzb;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">&gt;the method of calculating the <br>
          &gt;repair topology itself ought to be private to the
          orchestrator.<span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">When
            we agree to standardize the IPFRR related parameters, IMO
            it’s important to standardize the relevant algorithm too
            regardless of where it’s used.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">If
            it is used in a distributed manner this question is less
            relevant as it’s mostly  multi-vendor deployments.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Even
            when an orchestrator is computing using a particular
            algorithm IMO, it’s important Vendor X and Vendor Y of the
            controller do the same thing and
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">also
            this has to be *<b>clearly</b>* understood to validate (to
            see the corner cases are working correct)  and debug stuff,
            once deployed.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Proprietary
            stuff may come with their own cost/risk.<o:p></o:p></span></p>
      </div>
    </blockquote>
    I would appreciate hearing the operator's perspective(s) on this.<br>
    <br>
    Will we see two vendor's controllers operate over the same set of
    nodes such that identical behaviour is required, or is this an area
    where we are likely to see customization to execute the repair in a
    way that best suits the specifics of the network and the applicable
    business model?<br>
    <br>
    Stewart<br>
  </body>
</html>

--------------070307020802060702090804--


From nobody Mon Dec  8 11:29:44 2014
Return-Path: <skraza@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 0B0461ACDE3 for <rtgwg@ietfa.amsl.com>; Mon,  8 Dec 2014 11:29:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L6gwg8dvGoGZ for <rtgwg@ietfa.amsl.com>; Mon,  8 Dec 2014 11:29:39 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A36FE1A8851 for <rtgwg@ietf.org>; Mon,  8 Dec 2014 11:29:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5342; q=dns/txt; s=iport; t=1418066980; x=1419276580; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=FvKbkUPiWskOi47sNslujkLgiVY9vhJNTROuDYag8x0=; b=Wtw71cQPuIPpuJSwws5e28XfpB9z6zsLh4gD9LzAti04UCbtLGEF0Q8G uDL3kBL2w4cgkl9CZ6IEb2NFkROq9TvDRPX5cUTtdTtTZROsqZwC+4iBi foqelB0rj0CDxsN4rrOMDJkpQ25zemf9cFjnkW7hPRgf/WhEyXwdmsGol I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAPv6hVStJA2M/2dsb2JhbABZgwZSXMVlCoYJAoExFgEBAQEBfYQCAQEBBAEBATc0FwYBCBEEAQEfCS4LFAkKBAESiDgN1jQBAQEBAQEBAQEBAQEBAQEBAQEBARQEjRWCRQoHAV2EMAWMM4Fag1mBfoM+gQ2CX41+g25vgQMJFyJ+AQEB
X-IronPort-AV: E=Sophos;i="5.07,540,1413244800"; d="scan'208";a="103758149"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-6.cisco.com with ESMTP; 08 Dec 2014 19:29:39 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id sB8JTcRE010314 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 8 Dec 2014 19:29:38 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.207]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0195.001; Mon, 8 Dec 2014 13:29:38 -0600
From: "Kamran Raza (skraza)" <skraza@cisco.com>
To: "Clarence Filsfils (cfilsfil)" <cfilsfil@cisco.com>, "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "Jeff.Tantsura@ericsson.com" <Jeff.Tantsura@ericsson.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: Working Group last call on draft-ietf-rtgwg-lfa-manageability - IPR
Thread-Topic: Working Group last call on draft-ietf-rtgwg-lfa-manageability - IPR
Thread-Index: AQHQEx1NGy6xWv9Ud0mRjlbJ9+pWvg==
Date: Mon, 8 Dec 2014 19:29:38 +0000
Message-ID: <D0AB661D.26A00%skraza@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.4.140807
x-originating-ip: [161.44.212.165]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BA507CE035FACA4D94631227BB43B330@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/yJ-E0Xd0wP3YZBj9_JMyxWloHEA
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Dec 2014 19:29:42 -0000

I am also aware of the IPR disclosure already pointed by Clarence.

Thanks.

On 2014-12-03, 12:27 PM, "Clarence Filsfils (cfilsfil)"
<cfilsfil@cisco.com> wrote:

>Jeff,
>
>I am aware of this disclosure:
>
>https://datatracker.ietf.org/ipr/2196/
>
>Cheers,
>Clarence
>
>
>>> -----Original Message-----
>>> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of
>>> stephane.litkowski@orange.com
>>> Sent: Wednesday, November 12, 2014 09:24
>>> To: Jeff Tantsura; rtgwg@ietf.org
>>> Subject: RE: Working Group last call on
>>> draft-ietf-rtgwg-lfa-manageability - IPR
>>>
>>> Hi Jeff,
>>>
>>> I'm not aware of any IPR related to this draft.
>>>
>>> Stephane
>>>
>>>
>>> -----Original Message-----
>>> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Jeff Tantsura
>>> Sent: Monday, November 10, 2014 21:54
>>> To: rtgwg@ietf.org
>>> Subject: Working Group last call on draft-ietf-rtgwg-lfa-manageability
>>> - IPR
>>>
>>> All,
>>>
>>> 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.  The draft will not progress
>>> (pending the results of the WGLC) until we have received a response
>>> from each author.
>>>
>>>
>>> In addition, we wanted to take this opportunity to remind the entire
>>> WG that the duty of disclosure is NOT limited to authors:
>>>
>>>     (c) in order for the working group and the rest of the IETF to have
>>>         the information needed to make an informed decision about the
>>>use
>>>         of a particular technology, all those contributing to the
>>>working
>>>         group's discussions must disclose the existence of any IPR the
>>>         Contributor or other IETF participant believes Covers or may
>>>         ultimately Cover the technology under discussion.  This applies
>>>         to both Contributors and other participants, and applies
>>>whether
>>>         they contribute in person, via email or by other means.  The
>>>         requirement applies to all IPR of the participant, the
>>>         participant's employer, sponsor, or others represented by the
>>>         participants, that is reasonably and personally known to the
>>>         participant.  No patent search is required.
>>>
>>> RFC 3979 also points out disclosure must be "as soon as reasonably
>>> possible":
>>>
>>>     The IPR disclosure required pursuant to section 6.1.1 must be made
>>>as
>>>     soon as reasonably possible after the Contribution is published in
>>>an
>>>     Internet Draft unless the required disclosure is already on file.
>>>
>>> Thank you!
>>>
>>>
>>>
>>> Cheers,
>>> Jeff
>>>
>>> _______________________________________________
>>> rtgwg mailing list
>>> rtgwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>>
>>>=20
>>>________________________________________________________________________
>>>_________________________________________________
>>>
>>>
>>> Ce message et ses pieces jointes peuvent contenir des informations
>>> confidentielles ou privilegiees et ne doivent donc pas etre diffuses,
>>> exploites ou copies sans autorisation. Si vous avez recu ce message
>>> par erreur, veuillez le signaler a l'expediteur et le detruire ainsi
>>> que les pieces jointes. Les messages electroniques etant susceptibles
>>> d'alteration, Orange decline toute responsabilite si ce message a ete
>>> altere, deforme ou falsifie. Merci.
>>>
>>> This message and its attachments may contain confidential or
>>> privileged information that may be protected by law; they should not
>>> be distributed, used or copied without authorisation.
>>> If you have received this email in error, please notify the sender and
>>> delete this message and its attachments.
>>> As emails may be altered, Orange is not liable for messages that have
>>> been modified, changed or falsified.
>>> Thank you.
>>>
>>> _______________________________________________
>>> rtgwg mailing list
>>> rtgwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>>
>>>=20
>>>________________________________________________________________________
>>>_________________________________________________
>>>
>>>
>>> Ce message et ses pieces jointes peuvent contenir des informations
>>> confidentielles ou privilegiees et ne doivent donc
>>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
>>> recu ce message par erreur, veuillez le signaler
>>> a l'expediteur et le detruire ainsi que les pieces jointes. Les
>>> messages electroniques etant susceptibles d'alteration,
>>> Orange decline toute responsabilite si ce message a ete altere,
>>> deforme ou falsifie. Merci.
>>>
>>> This message and its attachments may contain confidential or
>>> privileged information that may be protected by law;
>>> they should not be distributed, used or copied without authorisation.
>>> If you have received this email in error, please notify the sender and
>>> delete this message and its attachments.
>>> As emails may be altered, Orange is not liable for messages that have
>>> been modified, changed or falsified.
>>> Thank you.
>>>
>>> .
>>>


From nobody Wed Dec 10 08:48:56 2014
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 CECFD1A8785 for <rtgwg@ietfa.amsl.com>; Tue,  9 Dec 2014 14:46:36 -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=unavailable
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 NwGawTj0aT-E for <rtgwg@ietfa.amsl.com>; Tue,  9 Dec 2014 14:46:34 -0800 (PST)
Received: from mail-yk0-x233.google.com (mail-yk0-x233.google.com [IPv6:2607:f8b0:4002:c07::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D4BE1A6F41 for <rtgwg@ietf.org>; Tue,  9 Dec 2014 14:46:30 -0800 (PST)
Received: by mail-yk0-f179.google.com with SMTP id 19so707333ykq.24 for <rtgwg@ietf.org>; Tue, 09 Dec 2014 14:46:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=EkX7xIn5A5fSVVo2TU5F/ZsOCqZuRIMXxh0NLFxK24k=; b=kmvrw4pvlhPyfktJbJeX/Tm+Euj2zzvVkNmmLfnTWF8QBUNC0Dh1VnWruyD9TE7uKU X1X91/zIApyVNeGgxxHlUJL0paGC8apVthCcnW3bsZcWelMwQdHqU0uP55pEi7zH5LeU OTxWXYuaPQSg+35wXnjj7ynBtJZ6z+JB1PFjOPZb+VLbwLH35Kac0n8GuBSLyR/smPGd EGdyeWxeZOkwdnz6TqM6EP8ipgrtzvZmnEcNB7m7eOfUAZZ+8mpnIU9x2bwA+1U82D3T /l7Xs1gd7Z2STOmFbtOwSckiuJdE5lgRvB1gzID4n32sUs4u6iPNaAzRZc9yGnm+aFBy NFkg==
MIME-Version: 1.0
X-Received: by 10.170.164.193 with SMTP id g184mr643304ykd.72.1418165190135; Tue, 09 Dec 2014 14:46:30 -0800 (PST)
Received: by 10.170.136.132 with HTTP; Tue, 9 Dec 2014 14:46:30 -0800 (PST)
Date: Tue, 9 Dec 2014 17:46:30 -0500
Message-ID: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>
Subject: routing area design team on dataplane encapsulation considerations
From: Alia Atlas <akatlas@gmail.com>
To: "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Content-Type: multipart/alternative; boundary=001a113936b46414e80509d05081
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/GFs8q99kj2A_P7OgZ7kv3mnyGqc
X-Mailman-Approved-At: Wed, 10 Dec 2014 08:48:55 -0800
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Dec 2014 22:46:37 -0000

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

I have chartered a Routing Area Design Team to work on data-plane
encapsulation considerations.

I've bcc'd nvo3, sfc, bier, and rtgwg as the most directly relevant.
Please keep any conversation in one place on routing-discussion.

Erik Nordmark has kindly agreed to lead this design team.  The members of
the design
team are:

  Albert Tian <albert.tian@ericsson.com>
  Erik Nordmark <nordmark@sonic.net>
  Jesse Gross <jgross@vmware.com>
  Jon Hudson <jon.hudson@gmail.com>
  Larry Kreeger (kreeger) <kreeger@cisco.com>
  Pankaj Garg <Garg.Pankaj@microsoft.com>
  Pat Thaler <pthaler@broadcom.com>
  Tom Herbert <therbert@google.com>

The mailing list, rgt-dt-encap-considerations@ietf.org, is closed but the
archives are
publicly available at:

http://www.ietf.org/mail-archive/web/rtg-dt-encap-considerations/current/ma=
illist.html

The Design Team is chartered as follows:

There have been multiple efforts over the years that have resulted in new
or modified data plane behaviors involving encapsulations. That includes
IETF efforts like MPLS, LISP, and TRILL but also industry efforts like
Vxlan and NVGRE.  These collectively can be seen as a source of insight
into the properties that data planes need to meet.  The IETF is currently
working on potentially new encapsulations in NVO3 and SFC and considering
working on BIER. In addition there is work on tunneling in the INT area.

This is a short term design team chartered to collect and construct useful
advice to parties working on new or modified data plane behaviors that
include additional encapsulations.  The goal is for the group to document
useful advice gathered from interacting with ongoing efforts.  An Internet
Draft will be produced for IETF92 to capture that advice, which will be
discussed in RTGWG.

Data plane encapsulations face a set of common issues such as:

  * How to provide entropy for ECMP
  * Issues around packet size and fragmentation/reassembly
  * OAM - what support is needed in an encapsulation format?
  * Security and privacy.
  * QoS
  * Congestion Considerations
  * IPv6 header protection (non-zero UDP checksum over IPv6 issue)
  * Extensibility - e.g., for evolving OAM, security, and/or congestion
control
  * Layering of multiple encapsulations e.g., SFC over NVO3 over BIER

The design team will provide advice on those issues. The intention is that
even where we have different encapsulations for different purposes carrying
different data, each such encapsulation doesn=E2=80=99t have to reinvent th=
e wheel
for the above common issues.

The design team will look across the routing area in particular at SFC,
NVO3 and BIER. It will not be involved in comparing or analyzing any
particular encapsulation formats proposed in those WGs and BoFs but instead
focus on common advice.

Regards,
Alia

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

<div dir=3D"ltr">I have chartered a Routing Area Design Team to work on dat=
a-plane encapsulation considerations.<div><br></div><div>I&#39;ve bcc&#39;d=
 nvo3, sfc, bier, and rtgwg as the most directly relevant.=C2=A0 Please kee=
p any conversation in one place on routing-discussion.<br><div><br></div><d=
iv>Erik Nordmark has kindly agreed to lead this design team.=C2=A0 The memb=
ers of the design</div><div>team are:</div><div><br></div><div><div style=
=3D"font-size:13px">=C2=A0 Albert Tian &lt;<a href=3D"mailto:albert.tian@er=
icsson.com" target=3D"_blank">albert.tian@ericsson.com</a>&gt;<br></div><di=
v style=3D"font-size:13px">=C2=A0 Erik Nordmark &lt;<a href=3D"mailto:nordm=
ark@sonic.net" target=3D"_blank">nordmark@sonic.net</a>&gt;<br>=C2=A0 Jesse=
 Gross &lt;<a href=3D"mailto:jgross@vmware.com" target=3D"_blank">jgross@vm=
ware.com</a>&gt;<br>=C2=A0 Jon Hudson &lt;<a href=3D"mailto:jon.hudson@gmai=
l.com" target=3D"_blank">jon.hudson@gmail.com</a>&gt;<br>=C2=A0 Larry Kreeg=
er (kreeger) &lt;<a href=3D"mailto:kreeger@cisco.com" target=3D"_blank">kre=
eger@cisco.com</a>&gt;<br>=C2=A0 Pankaj Garg &lt;<a href=3D"mailto:Garg.Pan=
kaj@microsoft.com" target=3D"_blank">Garg.Pankaj@microsoft.com</a>&gt;<br>=
=C2=A0 Pat Thaler &lt;<a href=3D"mailto:pthaler@broadcom.com" target=3D"_bl=
ank">pthaler@broadcom.com</a>&gt;<br>=C2=A0 Tom Herbert &lt;<a href=3D"mail=
to:therbert@google.com" target=3D"_blank">therbert@google.com</a>&gt;</div>=
</div><div style=3D"font-size:13px"><br></div><div style=3D"font-size:13px"=
>The mailing list, <a href=3D"mailto:rgt-dt-encap-considerations@ietf.org">=
rgt-dt-encap-considerations@ietf.org</a>, is closed but the archives are</d=
iv><div style=3D"font-size:13px">publicly available at:</div><div style=3D"=
font-size:13px">=C2=A0 =C2=A0<a href=3D"http://www.ietf.org/mail-archive/we=
b/rtg-dt-encap-considerations/current/maillist.html">http://www.ietf.org/ma=
il-archive/web/rtg-dt-encap-considerations/current/maillist.html</a></div><=
div style=3D"font-size:13px"><br></div><div style=3D"font-size:13px">The De=
sign Team is chartered as follows:</div><div style=3D"font-size:13px"><br><=
/div><div><span id=3D"docs-internal-guid-9bcbf1a5-3132-1b2d-c12f-3ac55f1d82=
65">There have been multiple efforts over the years that have resulted in n=
ew or modified data plane behaviors involving encapsulations. That includes=
 IETF efforts like MPLS, LISP, and TRILL but also industry efforts like Vxl=
an and NVGRE.=C2=A0 These collectively can be seen as a source of insight i=
nto the properties that data planes need to meet.=C2=A0 The IETF is current=
ly working on potentially new encapsulations in NVO3 and SFC and considerin=
g working on BIER. In addition there is work on tunneling in the INT area.<=
br><br>This is a short term design team chartered to collect and construct =
useful advice to parties working on new or modified data plane behaviors th=
at include additional encapsulations.=C2=A0 The goal is for the group to do=
cument useful advice gathered from interacting with ongoing efforts.=C2=A0 =
An Internet Draft will be produced for IETF92 to capture that advice, which=
 will be discussed in RTGWG.<br><br>Data plane encapsulations face a set of=
 common issues such as:<br><br>=C2=A0 * How to provide entropy for ECMP<br>=
=C2=A0 * Issues around packet size and fragmentation/reassembly<br>=C2=A0 *=
 OAM - what support is needed in an encapsulation format?<br>=C2=A0 * Secur=
ity and privacy.<br>=C2=A0 *=C2=A0QoS<br>=C2=A0 *=C2=A0Congestion Considera=
tions<br>=C2=A0 *=C2=A0IPv6 header protection (non-zero UDP checksum over I=
Pv6 issue)<br>=C2=A0 * Extensibility - e.g., for evolving OAM, security, an=
d/or congestion control<br>=C2=A0 * Layering of multiple encapsulations e.g=
., SFC over NVO3 over BIER</span></div><div><span><br></span></div><div><sp=
an>The design team will provide advice on those issues. The intention is th=
at even where we have different encapsulations for different purposes carry=
ing different data, each such encapsulation doesn=E2=80=99t have to reinven=
t the wheel for the above common issues.<br><br></span></div><div><span>The=
 design team will look across the routing area in particular at SFC, NVO3 a=
nd BIER. It will not be involved in comparing or analyzing any particular e=
ncapsulation formats proposed in those WGs and BoFs but instead focus on co=
mmon advice.</span></div><div><span><br></span></div><div><span>Regards,</s=
pan></div><div><span>Alia</span></div></div></div>

--001a113936b46414e80509d05081--


From nobody Thu Dec 11 16:00:08 2014
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 182DC1A9094 for <rtgwg@ietfa.amsl.com>; Thu, 11 Dec 2014 16:00:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.71
X-Spam-Level: **
X-Spam-Status: No, score=2.71 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.886, RAZOR2_CHECK=0.922, 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 nfz-4U0nslZH for <rtgwg@ietfa.amsl.com>; Thu, 11 Dec 2014 16:00:01 -0800 (PST)
Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A01A1A909F for <rtgwg@ietf.org>; Thu, 11 Dec 2014 16:00:01 -0800 (PST)
Received: by mail-yh0-f53.google.com with SMTP id i57so2765001yha.26 for <rtgwg@ietf.org>; Thu, 11 Dec 2014 16:00:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:cc:content-type;  bh=CnYIAJwBh92LhaWGmaCQgBrZhJt0rP+cg4OO12PFXpU=; b=CBK/v4jQTl6sLNATN/pD17DdR4isaaI3LkuUCHktIJtSHpR6CMHcWtrFjfC76uKqVG aO6zzrDLbZQsVeVbxKYvopfAKuj/ITTWKfUQHH/VBHGZ/fAzIogygw4kBkOZE8FCJg9U JrzOVOhNLSuTCK5lWy18odjAlC6IjGgdVXE69YrrhvlJqCMR4zQZfzIVEnIdD0+eN5Pe W562UrpaypkiGIvfK0Er3gUeIVNMZNMP4ukUl5K2RxIColwDCYYOApomUf1YoI/v6vJE nR8FNYc19oqrEUzoJk5gKuEOwPBxZWZDQCLvBYgwpI6vyDKS7mfNSebO6Yh5kDP5HU+h lBQw==
MIME-Version: 1.0
X-Received: by 10.170.39.70 with SMTP id 67mr9335212ykh.36.1418342400422; Thu, 11 Dec 2014 16:00:00 -0800 (PST)
Received: by 10.170.136.132 with HTTP; Thu, 11 Dec 2014 16:00:00 -0800 (PST)
Date: Thu, 11 Dec 2014 19:00:00 -0500
Message-ID: <CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com>
Subject: AD review comments on draft-ietf-rtgwg-remote-lfa-08
From: Alia Atlas <akatlas@gmail.com>
To: "draft-ietf-rtgwg-remote-lfa@tools.ietf.org" <draft-ietf-rtgwg-remote-lfa@tools.ietf.org>
Content-Type: multipart/alternative; boundary=001a11379da2f27c200509f992ab
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/yhgn0xFqJCoV_GQyAlo-XTK21d4
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Dec 2014 00:00:05 -0000

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

I have done my usual AD review of this draft before progressing it.
Thanks for the hard work on this!

I have a number of different comments on the draft, as given below.
None of them are sufficient for me to be concerned about starting the
IETF Last Call, but please address them as soon as possible.

Assuming an updated draft will appear and a quiet IETF Last Call, I expect
this to be on the IESG telechat in early Jan.


Minor Comments:

1) In Sec 2, 3rd paragraph, in the sentence:
"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."
it should be "S's extended P-space"

2) In Sec 2, it says: "The non-failure traffic distribution is not
disrupted by the provision of such a tunnel since it is only used for
repair traffic and MUST NOT be used for normal traffic."
This is obviously correct and good - but I think it would be very useful to
clarify that OAM traffic to test the rLFA may transit the tunnel at any
time.  Otherwise, the MUST NOT could cause some confusion - depending on
how one thinks about "normal traffic".

3) In Sec 3:  I can't parse "Examples of worse failures are node failures
(see Section 6 ), and through the failure of a shared risk link group
(SRLG), the through the independent concurrent failure of multiple links,
and these are out of scope for this specification."

I think you mean "Examples of worse failures are node failures (see Section
6), the failure of a shared risk link group (SRLG), the independent
concurrent failures of multiple links; protecting against such worse
failures is out of scope for this specification."  I would add in the
failure of broadcast interfaces and NBMA interfaces for completeness, even
though that was mentioned in Sec 2.

4) In Sec 4.2: " Provided both these requirements are met, packets
forwarded over the repair tunnel will reach their destination and will not
loop."  Please change to:
"will not loop after the single link failure".  Of course, looping can
happen if a worse failure than protected against occurs - as with LFA.
This could also be mitigated by requiring that the PQ node is downstream of
the PLR, as  is mentioned in Sec 4.2.2.

5) In Sec 4.2.1.2: "This may be calculated by computing an SPT at each of
S's neighbors (excluding E) and excising the subtree reached via the path
N->S->E."
As described here, a node Y that is reached via N->S->A would be considered
to be in S's extended P-space.  I realize that one would assume that Y
would be in S's P-space anyway and thus it is safe to not care about this
edge case.  However, the ECMP considerations make it more complex so please
at a minimum add in the same caveat as in Sec 4.2.1.2  "(including those
routers which are members of an ECMP that includes link S-E)" suitably
modified.  In the cost-based version in Compute_Extended_P_Space, this is
handled by ignoring any potential node from N whose shortest path goes back
through S.  It'd be nice if the two methods were consistent.

6) In Sec 4.2.2: "As described in [RFC5286], always selecting a PQ node
that is downstream with respect to the repairing node, prevents the
formation of loops when the failure is worse than expected."  Could you
clarify that the PQ node is downstream with respect to the repairing node
and the destination - rather than the proxy destination E?  I'm fairly
certain that the latter wouldn't work (but don't have an example topology
created).  If you disagree, let me know and I'll work on creating one.
This is the constraint that is expressed in Apply_Downstream_Constraint().

7) In Sec 4.3: "The reader is referred to
[I-D.psarkar-rtgwg-rlfa-node-protection]
for further information on the use of RLFA for node repairs." Can you add
"and broadcast or NBMA link repairs"?   Do you feel that is accurate?

8) In Sec 6: s/"When the failure is a node failure rather than a link
failure"/"When the failure is a node failure rather than a point-to-point
link failure"

9) In Sec 6: "Alternatively one might choose to assume that the probability
of a node failure and microloops forming is sufficiently rare that the case
can be ignored."  Can you please clarify from microloops to "microloops
forming due to use of alternates"?  We know that in cases where a rLFA is
necessary, that neighbor isn't loop-free and so regular microloops due to
reconvergence will form.

10) In Sec 7: "In the absence of a protocol to learn the preferred IP
address for targeted LDP, an LSR should attempt a targeted LDP session with
the Router ID [RFC2328] [RFC5305] [RFC5340], unless it is configured
otherwise."
 Can you please add in some text for how this would work for IPv6?  I
believe that there are current drafts discussing carrying Routable IP
addresses (e.g.
http://datatracker.ietf.org/doc/draft-ietf-ospf-routable-ip-address/ ).  We
know that there is interest in having IPv6 only networks with MPLS - so
it'd be good not to create new gaps.

11) In Sec 8.4: "In an MPLS network, this is achieved without any
scaleability impact, as the tunnels to the PQ nodes are always present as a
property of an LDP-based deployment."  The targeted LDP sessions don't have
a scaleability impact?  That the repair tunnels don't need to be
specifically created as new tunnels, I agree with - but this statement is
overselling.  Please make the technical point more clearly.

12) In Sec 9:  I feel like here is a good place at least mention the issues
with microloops from reconvergence.  Since reconvergence after rLFA is
going to result in a local microloop (depending on timing), at least a
reference to
https://tools.ietf.org/html/draft-litkowski-rtgwg-uloop-delay-03 with a
recommendation to consider it is important.  Otherwise, the rLFA repair
happens and then traffic microloops and is lost.  The fact that these local
microloops occur with real impact much more with rLFA (or any advanced FRR
technique) is an important management consideration.

13) Sec 12:  Saying "To prevent their use as an attack vector the repair
tunnel endpoints SHOULD be assigned from a set of addresses that are not
reachable from outside the routing domain." is basically empty words
without more behind Sec 7 default of using Router IDs.  Can you find a
reference that talks about a BCP for Router IDs not being reachable
addresses outside the routing domain?  Can you describe how to use the IGP
extensions?

Nits:

a) In Sec 4.2.1.1: "The exclusion of routers reachable via an ECMP that
includes S-E prevents the forwarding subsystem attempting to a repair
endpoint via the failed link S-E."
s/attempting to a repair/from attempting to use a repair

b) In Sec 10: "We propose "Remote LFA" as a natural second step."  This is
going to be an RFC - so rather than propose, try specify.

Thanks,
Alia

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

<div dir=3D"ltr"><div>I have done my usual AD review of this draft before p=
rogressing it.</div><div>Thanks for the hard work on this!</div><div><br></=
div><div>I have a number of different comments on the draft, as given below=
.</div><div>None of them are sufficient for me to be concerned about starti=
ng the=C2=A0</div><div>IETF Last Call, but please address them as soon as p=
ossible.</div><div><br></div><div>Assuming an updated draft will appear and=
 a quiet IETF Last Call, I expect</div><div>this to be on the IESG telechat=
 in early Jan.</div><div><br></div><br><div>Minor Comments:</div><div><br><=
/div><div>1) In Sec 2, 3rd paragraph, in the sentence:=C2=A0</div><div>&quo=
t;<span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">The sin=
gle node in both S&#39;s P-space and E&#39;s Q-space is C; thus</span><span=
 style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">=C2=A0node C i=
s selected as the repair tunnel&#39;s end-point.&quot;</span></div><div><sp=
an style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">it should be=
 &quot;S&#39;s extended P-space&quot;</span></div><div><span style=3D"color=
:rgb(0,0,0);font-size:13px;line-height:1.2em"><br></span></div><div><span s=
tyle=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">2) In Sec 2, it =
says: &quot;</span><span style=3D"color:rgb(0,0,0);font-size:13px;line-heig=
ht:1.2em">The non-failure traffic distribution is not disrupted by the=C2=
=A0</span><span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em"=
>provision of such a tunnel since it is only used for repair traffic</span>=
<span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">=C2=A0and=
 MUST NOT be used for normal traffic.&quot;</span></div><div>This is obviou=
sly correct and good - but I think it would be very useful to clarify that =
OAM traffic to test the rLFA may transit the tunnel at any time.=C2=A0 Othe=
rwise, the MUST NOT could cause some confusion - depending on how one think=
s about &quot;normal traffic&quot;.</div><div><br></div><div>3) In Sec 3: =
=C2=A0I can&#39;t parse &quot;<span style=3D"color:rgb(0,0,0);font-size:13p=
x;line-height:1.2em">Examples of worse failures are node failures (see Sect=
ion 6 ), and=C2=A0</span><span style=3D"color:rgb(0,0,0);font-size:13px;lin=
e-height:1.2em">through the failure of a shared risk link group (SRLG), the=
 through=C2=A0</span><span style=3D"color:rgb(0,0,0);font-size:13px;line-he=
ight:1.2em">the independent concurrent failure of multiple links, and these=
 are</span><span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em=
">=C2=A0out of scope for this specification.&quot;</span></div><div><br></d=
iv><div>I think you mean &quot;Examples of worse failures are node failures=
 (see Section 6), the failure of a shared risk link group (SRLG), the indep=
endent concurrent failures of multiple links; protecting against such worse=
 failures is out of scope for this specification.&quot; =C2=A0I would add i=
n the failure of broadcast interfaces and NBMA interfaces for completeness,=
 even though that was mentioned in Sec 2.</div><div><br></div><div>4) In Se=
c 4.2: &quot;<span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2=
em">   Provided both these requirements are met, packets forwarded over the=
=C2=A0</span><span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2=
em">repair tunnel will reach their destination and will not loop.&quot; =C2=
=A0Please change to:</span></div><div>&quot;will not loop after the single =
link failure&quot;.=C2=A0 Of course, looping can happen if a worse failure =
than protected against occurs - as with LFA.=C2=A0 This could also be mitig=
ated by requiring that the PQ node is downstream of the PLR, as =C2=A0is me=
ntioned in Sec 4.2.2.</div><div><br></div><div>5) In Sec <a href=3D"http://=
4.2.1.2">4.2.1.2</a>: &quot;<span style=3D"color:rgb(0,0,0);font-size:13px;=
line-height:1.2em">This may be calculated by computing an SPT at=C2=A0</spa=
n><span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">each of=
 S&#39;s neighbors (excluding E) and excising the subtree reached</span><sp=
an style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">=C2=A0via th=
e path N-&gt;S-&gt;E.&quot; =C2=A0</span></div><div>As described here, a no=
de Y that is reached via N-&gt;S-&gt;A would be considered to be in S&#39;s=
 extended P-space.=C2=A0 I realize that one would assume that Y would be in=
 S&#39;s P-space anyway and thus it is safe to not care about this edge cas=
e.=C2=A0 However, the ECMP considerations make it more complex so please at=
 a minimum add in the same caveat as in Sec 4.2.1.2=C2=A0<span style=3D"col=
or:rgb(0,0,0);font-size:13px;line-height:1.2em">=C2=A0&quot;(including thos=
e routers which are members of an ECMP that=C2=A0</span><span style=3D"colo=
r:rgb(0,0,0);font-size:13px;line-height:1.2em">includes link S-E)&quot; sui=
tably modified.=C2=A0 In the cost-based version in Compute_Extended_P_Space=
, this is handled by ignoring any potential node from N whose shortest path=
=C2=A0</span><span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2=
em">goes back through S.=C2=A0 It&#39;d be nice if the two methods were con=
sistent.</span></div><div><br></div><div>6) In Sec 4.2.2: &quot;<span style=
=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">As described in [RFC=
5286], always selecting a PQ node that is=C2=A0</span><span style=3D"color:=
rgb(0,0,0);font-size:13px;line-height:1.2em">downstream with respect to the=
 repairing node, prevents the formation</span><span style=3D"color:rgb(0,0,=
0);font-size:13px;line-height:1.2em">=C2=A0of loops when the failure is wor=
se than expected.&quot; =C2=A0Could you clarify that the PQ node is downstr=
eam with respect to the repairing node and the destination - rather than th=
e proxy destination E?=C2=A0 I&#39;m fairly certain that the latter wouldn&=
#39;t work (but don&#39;t have an example topology created).=C2=A0 If you d=
isagree, let me know and I&#39;ll work on creating one. =C2=A0 This is the =
constraint that is expressed in Apply_Downstream_Constraint().</span></div>=
<div><br></div><div>7) In Sec 4.3: &quot;<span style=3D"color:rgb(0,0,0);fo=
nt-size:13px;line-height:1.2em">The reader is referred to=C2=A0</span><span=
 style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">[I-D.psarkar-r=
tgwg-rlfa-node-protection] for further information on</span><span style=3D"=
color:rgb(0,0,0);font-size:13px;line-height:1.2em">=C2=A0the use of RLFA fo=
r node repairs.&quot; Can you add &quot;and broadcast or NBMA link repairs&=
quot;? =C2=A0 Do you feel that is accurate?=C2=A0</span></div><div><span st=
yle=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em"><br></span></div>=
<div><span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">8) I=
n Sec 6: s/&quot;</span><span style=3D"color:rgb(0,0,0);font-size:13px;line=
-height:1.2em">When the failure is a node failure rather than a link failur=
e&quot;/&quot;</span><span style=3D"color:rgb(0,0,0);font-size:13px;line-he=
ight:1.2em">When the failure is a node failure rather than a point-to-point=
 link failure&quot;</span></div><div><br></div><div>9) In Sec 6: &quot;<spa=
n style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">Alternatively=
 one might choose to assume that the probability of a=C2=A0</span><span sty=
le=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">node failure and m=
icroloops forming is sufficiently rare that the</span><span style=3D"color:=
rgb(0,0,0);font-size:13px;line-height:1.2em">=C2=A0case can be ignored.&quo=
t; =C2=A0Can you please clarify from microloops to &quot;microloops forming=
 due to use of alternates&quot;?=C2=A0 We know that in cases where a rLFA i=
s necessary, that neighbor isn&#39;t loop-free and so regular microloops du=
e to reconvergence will form.</span></div><div><br></div><div>10) In Sec 7:=
 &quot;<span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">In=
 the absence of a protocol to learn the preferred IP address for=C2=A0</spa=
n><span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">targete=
d LDP, an LSR should attempt a targeted LDP session with the</span><span st=
yle=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">=C2=A0Router ID [=
RFC2328] [RFC5305] [RFC5340], unless it is configured</span><span style=3D"=
color:rgb(0,0,0);font-size:13px;line-height:1.2em">=C2=A0otherwise.&quot; =
=C2=A0Can you please add in some text for how this would work for IPv6?=C2=
=A0 I believe that there are current drafts discussing carrying Routable IP=
 addresses (e.g.=C2=A0</span><font color=3D"#000000"><span style=3D"line-he=
ight:15.6000003814697px"><a href=3D"http://datatracker.ietf.org/doc/draft-i=
etf-ospf-routable-ip-address/">http://datatracker.ietf.org/doc/draft-ietf-o=
spf-routable-ip-address/</a> ).=C2=A0 We know that there is interest in hav=
ing IPv6 only networks with MPLS - so it&#39;d be good not to create new ga=
ps.</span></font></div><div><span style=3D"color:rgb(0,0,0);font-size:13px;=
line-height:1.2em"><br></span></div><div><span style=3D"color:rgb(0,0,0);fo=
nt-size:13px;line-height:1.2em">11) In Sec 8.4: &quot;</span><span style=3D=
"color:rgb(0,0,0);font-size:13px;line-height:1.2em">In an MPLS network, thi=
s is achieved without any scaleability=C2=A0</span><span style=3D"color:rgb=
(0,0,0);font-size:13px;line-height:1.2em">impact, as the tunnels to the PQ =
nodes are always present as a</span><span style=3D"color:rgb(0,0,0);font-si=
ze:13px;line-height:1.2em">=C2=A0 property of an LDP-based deployment.&quot=
; =C2=A0The targeted LDP sessions don&#39;t have a scaleability impact?=C2=
=A0 That the repair tunnels don&#39;t need to be specifically created as ne=
w tunnels, I agree with - but this statement is overselling.=C2=A0 Please m=
ake the technical point more clearly.</span></div><div><span style=3D"color=
:rgb(0,0,0);font-size:13px;line-height:1.2em"><br></span></div><div><span s=
tyle=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">12) In Sec 9: =
=C2=A0I feel like here is a good place at least mention the issues with mic=
roloops from reconvergence.=C2=A0 Since reconvergence after rLFA is going t=
o result in a local microloop (depending on timing), at least a reference t=
o=C2=A0</span><font color=3D"#000000"><span style=3D"line-height:15.6000003=
814697px"><a href=3D"https://tools.ietf.org/html/draft-litkowski-rtgwg-uloo=
p-delay-03">https://tools.ietf.org/html/draft-litkowski-rtgwg-uloop-delay-0=
3</a> with a recommendation to consider it is important.=C2=A0 Otherwise, t=
he rLFA repair happens and then traffic microloops and is lost.=C2=A0 The f=
act that these local microloops occur with real impact much more with rLFA =
(or any advanced FRR technique) is an important management consideration.</=
span></font></div><div><font color=3D"#000000"><span style=3D"line-height:1=
5.6000003814697px"><br></span></font></div><div><font color=3D"#000000"><sp=
an style=3D"line-height:15.6000003814697px">13) Sec 12: =C2=A0Saying &quot;=
</span></font><span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.=
2em">To prevent their use as an attack vector the repair tunnel endpoints=
=C2=A0</span><span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2=
em">SHOULD be assigned from a set of addresses that are not reachable=C2=A0=
</span><span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">fr=
om outside the routing domain.&quot; is basically empty words without more =
behind Sec 7 default of using Router IDs.=C2=A0 Can you find a reference th=
at talks about a BCP for Router IDs not being reachable addresses outside t=
he routing domain?=C2=A0 Can you describe how to use the IGP extensions?</s=
pan></div><div><br></div><div>Nits:</div><div><br></div><div>a) In Sec <a h=
ref=3D"http://4.2.1.1">4.2.1.1</a>: &quot;<span style=3D"color:rgb(0,0,0);f=
ont-size:13px;line-height:1.2em">The exclusion of routers reachable via an =
ECMP=C2=A0</span><span style=3D"color:rgb(0,0,0);font-size:13px;line-height=
:1.2em">that includes S-E prevents the forwarding subsystem attempting to a=
</span><span style=3D"color:rgb(0,0,0);font-size:13px;line-height:1.2em">=
=C2=A0repair endpoint via the failed link S-E.&quot;</span></div><div>s/att=
empting to a repair/from attempting to use a repair</div><div><br></div><di=
v>b) In Sec 10: &quot;<span style=3D"color:rgb(0,0,0);font-size:13px;line-h=
eight:1.2em">We propose &quot;Remote=C2=A0</span><span style=3D"color:rgb(0=
,0,0);font-size:13px;line-height:1.2em">LFA&quot; as a natural second step.=
&quot; =C2=A0This is going to be an RFC - so rather than propose, try speci=
fy.</span></div><div><span style=3D"color:rgb(0,0,0);font-size:13px;line-he=
ight:1.2em"><br></span></div><div><span style=3D"color:rgb(0,0,0);font-size=
:13px;line-height:1.2em">Thanks,</span></div><div><span style=3D"color:rgb(=
0,0,0);font-size:13px;line-height:1.2em">Alia</span></div><div><br></div></=
div>

--001a11379da2f27c200509f992ab--


From nobody Thu Dec 11 16:09:36 2014
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9A761A90DE; Thu, 11 Dec 2014 16:09:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1qoKjhPpxAeV; Thu, 11 Dec 2014 16:09:26 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 796351A90D7; Thu, 11 Dec 2014 16:09:26 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-rtgwg-remote-lfa-08.txt> (Remote LFA FRR) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20141212000926.29370.3594.idtracker@ietfa.amsl.com>
Date: Thu, 11 Dec 2014 16:09:26 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/16B1pa2z0X2RWKzHGHR7qhepnL8
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Dec 2014 00:09:30 -0000

The IESG has received a request from the Routing Area Working Group WG
(rtgwg) to consider the following document:
- 'Remote LFA FRR'
  <draft-ietf-rtgwg-remote-lfa-08.txt> as Proposed Standard

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

Abstract


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





The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa/

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


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

   http://datatracker.ietf.org/ipr/2009/
   http://datatracker.ietf.org/ipr/1770/
   http://datatracker.ietf.org/ipr/2071/




From nobody Mon Dec 15 07:11:12 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6E2A1A6FDE; Mon, 15 Dec 2014 07:11:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g402R1HBwxht; Mon, 15 Dec 2014 07:11:09 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 99AC31A1EFD; Mon, 15 Dec 2014 07:11:09 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-rtgwg-rlfa-node-protection-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141215151109.31754.65702.idtracker@ietfa.amsl.com>
Date: Mon, 15 Dec 2014 07:11:09 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/5evL7-_AMbqdTAJgOLXHLwmWgzA
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Dec 2014 15:11:11 -0000

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

        Title           : Remote-LFA Node Protection and Manageability
        Authors         : Pushpasis Sarkar
                          Hannes Gredler
                          Shraddha Hegde
                          Chris Bowers
                          Stephane Litkowski
                          Harish Raghuveer
	Filename        : draft-ietf-rtgwg-rlfa-node-protection-01.txt
	Pages           : 16
	Date            : 2014-12-15

Abstract:
   The loop-free alternates computed following the current Remote-LFA
   [I-D.ietf-rtgwg-remote-lfa] specification gaurantees only link-
   protection.  The resulting Remote-LFA nexthops (also called PQ-
   nodes), may not gaurantee node-protection for all destinations being
   protected by it.

   This document describes procedures for determining if a given PQ-node
   provides node-protection for a specific destination or not.  The
   document also shows how the same procedure can be utilised for
   collection of complete characteristics for alternate paths.
   Knowledge about the characteristics of all alternate path is
   precursory to apply operator defined policy for eliminating paths not
   fitting constraints.



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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rtgwg-rlfa-node-protection-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-rlfa-node-protection-01


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

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


From nobody Mon Dec 15 22:02:32 2014
Return-Path: <loa@pi.nu>
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 ABF5F1ACD0F for <rtgwg@ietfa.amsl.com>; Mon, 15 Dec 2014 22:02:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QrCENCXqdIJU for <rtgwg@ietfa.amsl.com>; Mon, 15 Dec 2014 22:02:28 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51FF71AC3AF for <rtgwg@ietf.org>; Mon, 15 Dec 2014 22:02:28 -0800 (PST)
Received: from [192.168.1.12] (unknown [112.205.93.13]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 017EC180155B for <rtgwg@ietf.org>; Tue, 16 Dec 2014 07:02:25 +0100 (CET)
Message-ID: <548FCAEE.3000007@pi.nu>
Date: Tue, 16 Dec 2014 14:02:22 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Notification: [mpls] poll to see if we have consensus to adopt draft-atlas-mpls-ldp-mrt
References: <548FC870.3090901@pi.nu>
In-Reply-To: <548FC870.3090901@pi.nu>
X-Forwarded-Message-Id: <548FC870.3090901@pi.nu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/OYEBRYBNA6gJfwbJAOFUXHyqm9E
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Dec 2014 06:02:29 -0000

Working Group,

You should be aware of that the mpls working has started a working group
adoption poll on draft-atlas-mpls-ldp-mrt.

Please send comments to the mpls wg mailing list (mpls@ietf.org).

/Loa
mpls wg co-chair


-------- Original Message --------
Subject: [mpls] poll to see if we have consensus to adopt 
draft-atlas-mpls-ldp-mrt
Date: Tue, 16 Dec 2014 13:51:44 +0800
From: Loa Andersson <loa@pi.nu>
To: mpls@ietf.org <mpls@ietf.org>
CC: mpls-chairs@tools.ietf.org <mpls-chairs@tools.ietf.org>, 
draft-atlas-mpls-ldp-mrt@tools.ietf.org

Working Group,

This is to start a two week poll on adopting
draft-atlas-mpls-ldp-mrt-03 as an MPLS working group document.

Please send your comments (support/not support) to the mpls working
group mailing list (mpls@ietf.org). Please give a technical
motivation for your support/not support, especially if you think that
the document should not be adopted as a working group document.

There is no IPR disclosures directly against this document. An IPR
poll will be done in parallel to the adoption poll, and the adoption
poll will not be closed before we have responses from all authors.

If you are on the the mpls working group mailing list and
aware of IPR that relates to this draft, you should respond to the
IPR poll.

This poll ends January 2, 2015.

/Loa

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

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



From nobody Tue Dec 16 09:56:06 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7AC91A86E2; Tue, 16 Dec 2014 09:55:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CczDfCYvPvKw; Tue, 16 Dec 2014 09:55:56 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8125A1A7013; Tue, 16 Dec 2014 09:55:56 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-rtgwg-remote-lfa-09.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141216175556.26149.33865.idtracker@ietfa.amsl.com>
Date: Tue, 16 Dec 2014 09:55:56 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/0sBaZ1pyzstcGemhOPjNa4T0cfQ
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Dec 2014 17:55:58 -0000

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

        Title           : Remote LFA FRR
        Authors         : Stewart Bryant
                          Clarence Filsfils
                          Stefano Previdi
                          Mike Shand
                          Ning So
	Filename        : draft-ietf-rtgwg-remote-lfa-09.txt
	Pages           : 29
	Date            : 2014-12-16

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



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

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

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


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

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


From nobody Tue Dec 16 09:57:38 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B64C01A86EC for <rtgwg@ietfa.amsl.com>; Tue, 16 Dec 2014 09:57:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.201
X-Spam-Level: 
X-Spam-Status: No, score=-11.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.886, RAZOR2_CHECK=0.922, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ost3Q33iZmgX for <rtgwg@ietfa.amsl.com>; Tue, 16 Dec 2014 09:57:28 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBA991A86DF for <rtgwg@ietf.org>; Tue, 16 Dec 2014 09:57:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=37865; q=dns/txt; s=iport; t=1418752648; x=1419962248; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=hBI72WRi8qv6iy/eki9hGx01lXs2r7ubGSWTa9TBtUw=; b=UtNtDXwdIQ+Sc1FV08+6Fg9bkIyM077cKElSimT4n82jZivIgn4+ROvY RVYwJeWwlWmf21v+tMEKo41h6QO9UClX/GUFDGY2nSYcV9cipKCaUcgKK 8j8etrDfYjepaTFD+WqPxQ51XX/J1ujdZfxSMx0/Y7xG8ztNVucuKkviS A=;
X-IronPort-AV: E=Sophos;i="5.07,588,1413244800";  d="scan'208,217";a="277203000"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 16 Dec 2014 17:57:26 +0000
Received: from [64.103.108.123] (dhcp-bdlk10-data-vlan301-64-103-108-123.cisco.com [64.103.108.123]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id sBGHvPNO026916; Tue, 16 Dec 2014 17:57:26 GMT
Message-ID: <54907286.7040703@cisco.com>
Date: Tue, 16 Dec 2014 17:57:26 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Alia Atlas <akatlas@gmail.com>, "draft-ietf-rtgwg-remote-lfa@tools.ietf.org" <draft-ietf-rtgwg-remote-lfa@tools.ietf.org>
Subject: Re: AD review comments on draft-ietf-rtgwg-remote-lfa-08
References: <CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com>
In-Reply-To: <CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070804020404070009070102"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/9_kWO7FP-NB4sYv_mFt65_f3ygo
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: Tue, 16 Dec 2014 17:57:37 -0000

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

On 12/12/2014 00:00, Alia Atlas wrote:

Alia thank you for your review.

Here are my responses and the changes make to -09
> Minor Comments:
>
> 1) In Sec 2, 3rd paragraph, in the sentence:
> "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."
> it should be "S's extended P-space"
Correct - changed
>
> 2) In Sec 2, it says: "The non-failure traffic distribution is not 
> disrupted by the provision of such a tunnel since it is only used for 
> repair traffic and MUST NOT be used for normal traffic."
> This is obviously correct and good - but I think it would be very 
> useful to clarify that OAM traffic to test the rLFA may transit the 
> tunnel at any time.  Otherwise, the MUST NOT could cause some 
> confusion - depending on how one thinks about "normal traffic".
This now says:

The non-failure traffic distribution is not disrupted by the provision 
of such a tunnel since it is only used for repair traffic and MUST NOT 
be used for normal traffic. Note that OAM traffic specifically to verify 
the viability of the repair MAY traverse the tunnel prior to a failure.

I used viability rather than for example "availability" to cover any 
form of OAM test (CC, CV, delay, jitter.....)

I toyed with saying "normal data traffic" and not adding the OAM 
sentence, but that would have allowed routing and network management 
traffic (other than OAM) which we also need to exclude.

>
> 3) In Sec 3:  I can't parse "Examples of worse failures are node 
> failures (see Section 6 ), and through the failure of a shared risk 
> link group (SRLG), the through the independent concurrent failure of 
> multiple links, and these are out of scope for this specification."
>
> I think you mean "Examples of worse failures are node failures (see 
> Section 6), the failure of a shared risk link group (SRLG), the 
> independent concurrent failures of multiple links; protecting against 
> such worse failures is out of scope for this specification."  I would 
> add in the failure of broadcast interfaces and NBMA interfaces for 
> completeness, even though that was mentioned in Sec 2.
This now says:

Examples of worse failures are node failures (see Section 6), the 
failure of a shared risk link group (SRLG), the independent concurrent 
failures of multiple links, broadcast or non-broadcast multi-access 
(NBMA) links [Section 2]; protecting against such worse failures is out 
of scope for this specification.

>
> 4) In Sec 4.2: "Provided both these requirements are met, packets 
> forwarded over the repair tunnel will reach their destination and will 
> not loop."  Please change to:
> "will not loop after the single link failure".  Of course, looping can 
> happen if a worse failure than protected against occurs - as with 
> LFA.  This could also be mitigated by requiring that the PQ node is 
> downstream of the PLR, as  is mentioned in Sec 4.2.2.
Correct

This now says:

Provided both these requirements are met, packets forwarded over the 
repair tunnel will reach their destination, and will not loop after a 
single link failure.
>
> 5) In Sec 4.2.1.2 <http://4.2.1.2>: "This may be calculated by 
> computing an SPT at each of S's neighbors (excluding E) and excising 
> the subtree reached via the path N->S->E."
> As described here, a node Y that is reached via N->S->A would be 
> considered to be in S's extended P-space.  I realize that one would 
> assume that Y would be in S's P-space anyway and thus it is safe to 
> not care about this edge case.  However, the ECMP considerations make 
> it more complex so please at a minimum add in the same caveat as in 
> Sec 4.2.1.2  "(including those routers which are members of an ECMP 
> that includes link S-E)" suitably modified.  In the cost-based version 
> in Compute_Extended_P_Space, this is handled by ignoring any potential 
> node from N whose shortest path goes back through S.  It'd be nice if 
> the two methods were consistent.
I have changed the text to:

This may be calculated by computing an SPT at each of S's neighbors 
(excluding E) and excising the subtree reached via the path N->S->E. 
Note this will excise those routers which are reachable through all 
ECMPs that includes link S-E.

I am not sure that this clarification is strictly needed since "removal 
of the subtree reached via the path N->S->E" would include "those 
routers which are members of any ECMP that includes link S-E".

Would it be less confusing if we changed "excising the subtree reached" 
to "excising the routers reached"?
>
> 6) In Sec 4.2.2: "As described in [RFC5286], always selecting a PQ 
> node that is downstream with respect to the repairing node, prevents 
> the formation of loops when the failure is worse than expected." 
>  Could you clarify that the PQ node is downstream with respect to the 
> repairing node and the destination - rather than the proxy destination 
> E?  I'm fairly certain that the latter wouldn't work (but don't have 
> an example topology created).  If you disagree, let me know and I'll 
> work on creating one.   This is the constraint that is expressed in 
> Apply_Downstream_Constraint().
I don't think there is a problem in practice since if PQ needed to be 
downstream to E WRT S, D_opt(PQ,E) < D_opt(S,E) would apply and in a 
unit cost network there would be no PQ nodes since we would need 
D_opt(PQ,E) < 1, i.e. a link metric from PQ to E of less than one. PQ 
nodes would be so rare that this would no be a practical solution.

I have changed the text to:

As described in [RFC5286], always selecting a PQ node that is downstream 
to the destination with respect to the repairing node, prevents the 
formation of loops when the failure is worse than expected. The use of 
downstream nodes reduces the repair coverage, and operators are advised 
to determine whether adequate coverage is achieved before enabling this 
selection feature.
>
> 7) In Sec 4.3: "The reader is referred to 
> [I-D.psarkar-rtgwg-rlfa-node-protection] for further information 
> on the use of RLFA for node repairs." Can you add "and broadcast or 
> NBMA link repairs"?   Do you feel that is accurate?
>
I cannot see any text on broadcast or NBMA in the draft which is now 
draft-ietf-rtgwg-rlfa-node-protection (updates in text)

I have made no text change on the substantive point.
> 8) In Sec 6: s/"When the failure is a node failure rather than a link 
> failure"/"When the failure is a node failure rather than a 
> point-to-point link failure"
Done
>
> 9) In Sec 6: "Alternatively one might choose to assume that the 
> probability of a node failure and microloops forming is sufficiently 
> rare that the case can be ignored."  Can you please clarify from 
> microloops to "microloops forming due to use of alternates"?  We know 
> that in cases where a rLFA is necessary, that neighbor isn't loop-free 
> and so regular microloops due to reconvergence will form.
>
It took a while to understand the comment but I think I know what you mean.

I have changed the text to:

Alternatively one might choose to assume that the probability of a node 
failure is sufficiently rare that the issue of looping RLFA repairs can 
be ignored.
> 10) In Sec 7: "In the absence of a protocol to learn the preferred IP 
> address for targeted LDP, an LSR should attempt a targeted LDP session 
> with the Router ID [RFC2328] [RFC5305] [RFC5340], unless it is 
> configured otherwise."  Can you please add in some text for how this 
> would work for IPv6?  I believe that there are current drafts 
> discussing carrying Routable IP addresses (e.g. 
> http://datatracker.ietf.org/doc/draft-ietf-ospf-routable-ip-address/ 
> ).  We know that there is interest in having IPv6 only networks with 
> MPLS - so it'd be good not to create new gaps.

It now says

In the absence of a protocol to learn the preferred IP address for targeted LDP, an LSR should attempt a targeted LDP session with the Router ID [RFC2328] [RFC5305] [RFC5340] [RFC6119] [I-D.ietf-ospf-routable-ip-address"
], unless it is configured otherwise.

>
> 11) In Sec 8.4: "In an MPLS network, this is achieved without any 
> scaleability impact, as the tunnels to the PQ nodes are always present 
> as aproperty of an LDP-based deployment."  The targeted LDP sessions 
> don't have a scaleability impact?  That the repair tunnels don't need 
> to be specifically created as new tunnels, I agree with - but this 
> statement is overselling. Please make the technical point more clearly.
>
I have cut this back to

As shown in the table, remote LFA provides close to 100% prefix 
protection against link failure in 11 of the 14 topologies studied, and 
provides a significant improvement in two of the remaining three cases. 
Note that in an MPLS network the tunnels to the PQ nodes are always 
present as a property of an LDP-based deployment.

> 12) In Sec 9:  I feel like here is a good place at least mention the 
> issues with microloops from reconvergence.  Since reconvergence after 
> rLFA is going to result in a local microloop (depending on timing), at 
> least a reference to 
> https://tools.ietf.org/html/draft-litkowski-rtgwg-uloop-delay-03 with 
> a recommendation to consider it is important. Otherwise, the rLFA 
> repair happens and then traffic microloops and is lost.  The fact that 
> these local microloops occur with real impact much more with rLFA (or 
> any advanced FRR technique) is an important management consideration.
I have added the following new para:

When the network re-converges, microloops [RFC5715] may form due to 
transient inconsistencies in the router FIBs. If it is determined that 
microloops are a significant issue in the deployment, then a suitable 
loop free convergence methods such as one of those described in 
[RFC5715], [RFC6976] or  [I-D.litkowski-rtgwg-uloop-delay] should be 
implemented.

>
> 13) Sec 12:  Saying "To prevent their use as an attack vector the 
> repair tunnel endpoints SHOULD be assigned from a set of addresses 
> that are not reachable from outside the routing domain." is basically 
> empty words without more behind Sec 7 default of using Router IDs.  
> Can you find a reference that talks about a BCP for Router IDs not 
> being reachable addresses outside the routing domain? Can you describe 
> how to use the IGP extensions?
Router IDs are used for T-LDP and normal MPLS security applies.

Again with MPLS repair tunnels normal MPLS security applies.

The Section 12 reference was to IP tunnels in an IP rather than MPLS 
network. I have changed the text to:

The security considerations of [RFC 5286] also apply.

Targeted LDP sessions and MPLS tunnels are normal features of an MPLS 
network and their use in this application raises no additional security 
concerns.

To prevent their use as an attack vector  IP repair tunnel endpoints 
(where used) SHOULD be assigned from a set of addresses that are not 
reachable from outside the routing domain.

>
> Nits:
>
> a) In Sec 4.2.1.1 <http://4.2.1.1>: "The exclusion of routers 
> reachable via an ECMP that includes S-E prevents the forwarding 
> subsystem attempting to a repair endpoint via the failed link S-E."
> s/attempting to a repair/from attempting to use a repair
Done
>
> b) In Sec 10: "We propose "Remote LFA" as a natural second step." 
>  This is going to be an RFC - so rather than propose, try specify.
>
I have changed this to:
> The purpose of LFA FRR technology is to provide for a simple FRR 
> solution when such a solution is possible. The first step along this 
> simplicity approach was "local" LFA [RFC5286]. This specification of 
> "Remote LFA" is a natural second step.

Hopefully these resolutions are acceptable to all. If not please let me 
know.

New version at http://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa/

Diffs at 
http://www.ietf.org/rfcdiff?url1=draft-ietf-rtgwg-remote-lfa-08&difftype=--html&submit=Go!&url2=draft-ietf-rtgwg-remote-lfa-09

- Stewart

--------------070804020404070009070102
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">On 12/12/2014 00:00, Alia Atlas wrote:<br>
    </div>
    <br>
    <font color="#3333ff">Alia thank you for your review.<br>
      <br>
      Here are my responses and the changes make to -09</font><br>
    <blockquote
cite="mid:CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>Minor Comments:</div>
        <div><br>
        </div>
        <div>1) In Sec 2, 3rd paragraph, in the sentence:&nbsp;</div>
        <div>"<span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">The
            single node in both S's P-space and E's Q-space is C; thus</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">&nbsp;node
            C is selected as the repair tunnel's end-point."</span></div>
        <div><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">it
            should be "S's extended P-space"</span></div>
      </div>
    </blockquote>
    <font color="#3333ff">Correct - changed</font><br>
    <blockquote
cite="mid:CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em"><br>
          </span></div>
        <div><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">2)
            In Sec 2, it says: "</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">The
            non-failure traffic distribution is not disrupted by the&nbsp;</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">provision
            of such a tunnel since it is only used for repair traffic</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">&nbsp;and
            MUST NOT be used for normal traffic."</span></div>
        <div>This is obviously correct and good - but I think it would
          be very useful to clarify that OAM traffic to test the rLFA
          may transit the tunnel at any time.&nbsp; Otherwise, the MUST NOT
          could cause some confusion - depending on how one thinks about
          "normal traffic".</div>
      </div>
    </blockquote>
    <font color="#3333ff">This now says:<br>
      <br>
      The non-failure traffic distribution is not disrupted by the
      provision of such a tunnel since it is only used for repair
      traffic and MUST NOT be used for normal traffic. Note that OAM
      traffic specifically to verify the viability of the repair MAY
      traverse the tunnel prior to a failure.<br>
      <br>
      I used viability rather than for example "availability" to cover
      any form of OAM test (CC, CV, delay, jitter.....)<br>
      <br>
      I toyed with saying "normal data traffic" and not adding the OAM
      sentence, but that would have allowed routing and network
      management traffic (other than OAM) which we also need to exclude.<br>
      <br>
    </font><span
      style="color:rgb(0,0,0);font-size:13px;line-height:1.2em"></span>
    <blockquote
cite="mid:CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br>
        </div>
        <div>3) In Sec 3: &nbsp;I can't parse "<span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">Examples
            of worse failures are node failures (see Section 6 ), and&nbsp;</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">through
            the failure of a shared risk link group (SRLG), the through&nbsp;</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">the
            independent concurrent failure of multiple links, and these
            are</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">&nbsp;out
            of scope for this specification."</span></div>
        <div><br>
        </div>
        <div>I think you mean "Examples of worse failures are node
          failures (see Section 6), the failure of a shared risk link
          group (SRLG), the independent concurrent failures of multiple
          links; protecting against such worse failures is out of scope
          for this specification." &nbsp;I would add in the failure of
          broadcast interfaces and NBMA interfaces for completeness,
          even though that was mentioned in Sec 2.</div>
      </div>
    </blockquote>
    <font color="#3333ff">This now says:<br>
      <br>
      Examples of worse failures are node failures (see Section 6), the
      failure of a shared risk link group (SRLG), the independent
      concurrent failures of multiple links, broadcast or non-broadcast
      multi-access (NBMA) links [Section 2]; protecting against such
      worse failures is out of scope for this specification.<br>
    </font><br>
    <blockquote
cite="mid:CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br>
        </div>
        <div>4) In Sec 4.2: "<span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">
            Provided both these requirements are met, packets forwarded
            over the&nbsp;</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">repair
            tunnel will reach their destination and will not loop."
            &nbsp;Please change to:</span></div>
        <div>"will not loop after the single link failure".&nbsp; Of course,
          looping can happen if a worse failure than protected against
          occurs - as with LFA.&nbsp; This could also be mitigated by
          requiring that the PQ node is downstream of the PLR, as &nbsp;is
          mentioned in Sec 4.2.2.</div>
      </div>
    </blockquote>
    <font color="#3333ff">Correct<br>
      <br>
      This now says:<br>
      <br>
      Provided both these requirements are met, packets forwarded over
      the repair tunnel will reach their destination, and will not loop
      after a single link failure.</font><br>
    <blockquote
cite="mid:CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br>
        </div>
        <div>5) In Sec <a moz-do-not-send="true" href="http://4.2.1.2">4.2.1.2</a>:
          "<span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">This
            may be calculated by computing an SPT at&nbsp;</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">each
            of S's neighbors (excluding E) and excising the subtree
            reached</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">&nbsp;via
            the path N-&gt;S-&gt;E." &nbsp;</span></div>
        <div>As described here, a node Y that is reached via
          N-&gt;S-&gt;A would be considered to be in S's extended
          P-space.&nbsp; I realize that one would assume that Y would be in
          S's P-space anyway and thus it is safe to not care about this
          edge case.&nbsp; However, the ECMP considerations make it more
          complex so please at a minimum add in the same caveat as in
          Sec 4.2.1.2&nbsp;<span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">&nbsp;"(including
            those routers which are members of an ECMP that&nbsp;</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">includes
            link S-E)" suitably modified.&nbsp; In the cost-based version in
            Compute_Extended_P_Space, this is handled by ignoring any
            potential node from N whose shortest path&nbsp;</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">goes
            back through S.&nbsp; It'd be nice if the two methods were
            consistent.</span></div>
      </div>
    </blockquote>
    <font color="#3333ff">I have changed the text to:<br>
      <br>
      This may be calculated by computing an SPT at each of S's
      neighbors (excluding E) and excising the subtree reached via the
      path N-&gt;S-&gt;E. Note this will excise those routers which are
      reachable through all ECMPs that includes link S-E.<br>
      <br>
      I am not sure that this clarification is strictly needed since
      "removal of the subtree reached via the path N-&gt;S-&gt;E" would
      include "those routers which are members of any ECMP that includes
      link S-E".<br>
      <br>
      Would it be less confusing if we changed "excising the subtree
      reached" to "excising the routers reached"?</font>
    <blockquote
cite="mid:CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br>
        </div>
        <div>6) In Sec 4.2.2: "<span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">As
            described in [RFC5286], always selecting a PQ node that is&nbsp;</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">downstream
            with respect to the repairing node, prevents the formation</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">&nbsp;of
            loops when the failure is worse than expected." &nbsp;Could you
            clarify that the PQ node is downstream with respect to the
            repairing node and the destination - rather than the proxy
            destination E?&nbsp; I'm fairly certain that the latter wouldn't
            work (but don't have an example topology created).&nbsp; If you
            disagree, let me know and I'll work on creating one. &nbsp; This
            is the constraint that is expressed in
            Apply_Downstream_Constraint().</span></div>
      </div>
    </blockquote>
    <font color="#3333ff">I don't think there is a problem in practice
      since if PQ needed to be downstream to E WRT S, D_opt(PQ,E) &lt;
      D_opt(S,E) would apply and in a unit cost network there would be
      no PQ nodes since we would need </font><font color="#3333ff">
      D_opt(PQ,E) &lt; 1, i.e. a link metric from PQ to E of less than
      one. PQ nodes would be so rare that this would no be a practical
      solution.<br>
      <br>
      I have changed the text to:<br>
      <br>
      As described in [RFC5286], always selecting a PQ node that is
      downstream to the destination with respect to the repairing node,
      prevents the formation of loops when the failure is worse than
      expected. The use of downstream nodes reduces the repair coverage,
      and operators are advised to determine whether adequate coverage
      is achieved before enabling this selection feature.</font><br>
    <blockquote
cite="mid:CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br>
        </div>
        <div>7) In Sec 4.3: "<span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">The
            reader is referred to&nbsp;</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">[I-D.psarkar-rtgwg-rlfa-node-protection]
            for further information on</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">&nbsp;the
            use of RLFA for node repairs." Can you add "and broadcast or
            NBMA link repairs"? &nbsp; Do you feel that is accurate?&nbsp;</span></div>
        <div><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em"><br>
          </span></div>
      </div>
    </blockquote>
    <font color="#3333ff">I cannot see any text on <span
        style="font-size: 13px; line-height: 1.2em;">broadcast or NBMA
        in the draft which is now draft-ietf-</span></font><span
      style="color:rgb(0,0,0);font-size:13px;line-height:1.2em"><font
        color="#3333ff">rtgwg-rlfa-node-protection (updates in text)<br>
        <br>
        I have made no text change on the substantive point.</font><br>
    </span>
    <blockquote
cite="mid:CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">8)
            In Sec 6: s/"</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">When
            the failure is a node failure rather than a link failure"/"</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">When
            the failure is a node failure rather than a point-to-point
            link failure"</span></div>
      </div>
    </blockquote>
    <font color="#3333ff">Done</font><br>
    <blockquote
cite="mid:CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br>
        </div>
        <div>9) In Sec 6: "<span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">Alternatively
            one might choose to assume that the probability of a&nbsp;</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">node
            failure and microloops forming is sufficiently rare that the</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">&nbsp;case
            can be ignored." &nbsp;Can you please clarify from microloops to
            "microloops forming due to use of alternates"?&nbsp; We know that
            in cases where a rLFA is necessary, that neighbor isn't
            loop-free and so regular microloops due to reconvergence
            will form.</span></div>
        <div><br>
        </div>
      </div>
    </blockquote>
    <font color="#3333ff">It took a while to understand the comment but
      I think I know what you mean.<br>
      <br>
      I have changed the text to:<br>
      <br>
      Alternatively one might choose to assume that the probability of a
      node failure is sufficiently rare that the issue of looping RLFA
      repairs can be ignored.</font><br>
    <blockquote
cite="mid:CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>10) In Sec 7: "<span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">In
            the absence of a protocol to learn the preferred IP address
            for&nbsp;</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">targeted
            LDP, an LSR should attempt a targeted LDP session with the</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">&nbsp;Router
            ID [RFC2328] [RFC5305] [RFC5340], unless it is configured</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">&nbsp;otherwise."
            &nbsp;Can you please add in some text for how this would work for
            IPv6?&nbsp; I believe that there are current drafts discussing
            carrying Routable IP addresses (e.g.&nbsp;</span><font
            color="#000000"><span style="line-height:15.6000003814697px"><a
                moz-do-not-send="true"
href="http://datatracker.ietf.org/doc/draft-ietf-ospf-routable-ip-address/">http://datatracker.ietf.org/doc/draft-ietf-ospf-routable-ip-address/</a>
              ).&nbsp; We know that there is interest in having IPv6 only
              networks with MPLS - so it'd be good not to create new
              gaps.</span></font></div>
      </div>
    </blockquote>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <pre><font color="#3333ff">It now says

In the absence of a protocol to learn the preferred IP address for targeted LDP, an LSR should attempt a targeted LDP session with the Router ID [RFC2328] [RFC5305] [RFC5340] [RFC6119] [I-D.ietf-ospf-routable-ip-address"
], unless it is configured otherwise.</font>
</pre>
    <blockquote
cite="mid:CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em"><br>
          </span></div>
        <div><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">11)
            In Sec 8.4: "</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">In
            an MPLS network, this is achieved without any scaleability&nbsp;</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">impact,
            as the tunnels to the PQ nodes are always present as a</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">&nbsp;
            property of an LDP-based deployment." &nbsp;The targeted LDP
            sessions don't have a scaleability impact?&nbsp; That the repair
            tunnels don't need to be specifically created as new
            tunnels, I agree with - but this statement is overselling.&nbsp;
            Please make the technical point more clearly.</span></div>
        <div><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em"><br>
          </span></div>
      </div>
    </blockquote>
    <font color="#3333ff">I have cut this back to <br>
      <br>
      As shown in the table, remote LFA provides close to 100% prefix
      protection against link failure in 11 of the 14 topologies
      studied, and provides a significant improvement in two of the
      remaining three cases. Note that in an MPLS network the tunnels to
      the PQ nodes are always present as a property of an LDP-based
      deployment.</font><br>
    <br>
    <blockquote
cite="mid:CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">12)
            In Sec 9: &nbsp;I feel like here is a good place at least mention
            the issues with microloops from reconvergence.&nbsp; Since
            reconvergence after rLFA is going to result in a local
            microloop (depending on timing), at least a reference to&nbsp;</span><font
            color="#000000"><span style="line-height:15.6000003814697px"><a
                moz-do-not-send="true"
                href="https://tools.ietf.org/html/draft-litkowski-rtgwg-uloop-delay-03">https://tools.ietf.org/html/draft-litkowski-rtgwg-uloop-delay-03</a>
              with a recommendation to consider it is important.&nbsp;
              Otherwise, the rLFA repair happens and then traffic
              microloops and is lost.&nbsp; The fact that these local
              microloops occur with real impact much more with rLFA (or
              any advanced FRR technique) is an important management
              consideration.</span></font></div>
      </div>
    </blockquote>
    <font color="#3333ff">I have added the following new para:<br>
      <br>
      When the network re-converges, microloops [RFC5715] may form due
      to transient inconsistencies in the router FIBs. If it is
      determined that microloops are a significant issue in the
      deployment, then a suitable loop free convergence methods such as
      one of those described in [RFC5715], [RFC6976] or&nbsp; [I-D.<span
        style="line-height:15.6000003814697px">litkowski-rtgwg-uloop-delay]
        should be implemented.</span><br>
    </font>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <br>
    <blockquote
cite="mid:CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><font color="#000000"><span
              style="line-height:15.6000003814697px"><br>
            </span></font></div>
        <div><font color="#000000"><span
              style="line-height:15.6000003814697px">13) Sec 12: &nbsp;Saying
              "</span></font><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">To
            prevent their use as an attack vector the repair tunnel
            endpoints&nbsp;</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">SHOULD
            be assigned from a set of addresses that are not reachable&nbsp;</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">from
            outside the routing domain." is basically empty words
            without more behind Sec 7 default of using Router IDs.&nbsp; Can
            you find a reference that talks about a BCP for Router IDs
            not being reachable addresses outside the routing domain?&nbsp;
            Can you describe how to use the IGP extensions?</span></div>
      </div>
    </blockquote>
    <font color="#3333ff">Router IDs are used for T-LDP and normal MPLS
      security applies.<br>
      <br>
      Again with MPLS repair tunnels normal MPLS security applies.<br>
      <br>
      The Section 12 reference was to IP tunnels in an IP rather than
      MPLS network. I have changed the text to:<br>
      <br>
      The security considerations of [RFC 5286] also apply.<br>
      <br>
      Targeted LDP sessions and MPLS tunnels are normal features of an
      MPLS network and their use in this application raises no
      additional security concerns.<br>
      <br>
      To prevent their use as an attack vector&nbsp; IP repair tunnel
      endpoints (where used) SHOULD be assigned from a set of addresses
      that are not reachable from outside the routing domain.</font><br>
    <br>
    <blockquote
cite="mid:CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br>
        </div>
        <div>Nits:</div>
        <div><br>
        </div>
        <div>a) In Sec <a moz-do-not-send="true" href="http://4.2.1.1">4.2.1.1</a>:
          "<span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">The
            exclusion of routers reachable via an ECMP&nbsp;</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">that
            includes S-E prevents the forwarding subsystem attempting to
            a</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">&nbsp;repair
            endpoint via the failed link S-E."</span></div>
        <div>s/attempting to a repair/from attempting to use a repair</div>
      </div>
    </blockquote>
    <font color="#3333ff">Done</font><br>
    <blockquote
cite="mid:CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br>
        </div>
        <div>b) In Sec 10: "<span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">We
            propose "Remote&nbsp;</span><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em">LFA"
            as a natural second step." &nbsp;This is going to be an RFC - so
            rather than propose, try specify.</span></div>
        <div><span
            style="color:rgb(0,0,0);font-size:13px;line-height:1.2em"><br>
          </span></div>
      </div>
    </blockquote>
    <font color="#3333ff">I have changed this to:</font><br>
    <blockquote
cite="mid:CAG4d1red0acjgUbsAuss2L+WNdnAUq5Uynv_MzV8DccvTtDPnA@mail.gmail.com"
      type="cite">
      <div dir="ltr"><font color="#3333ff">The purpose of LFA FRR
          technology is to provide for a simple FRR solution when such a
          solution is possible. The first step along this simplicity
          approach was &#8220;local&#8221; LFA [RFC5286]. This specification of
          &#8220;Remote LFA&#8221; is a natural second step.</font></div>
    </blockquote>
    <br>
    <font color="#3333ff">Hopefully these resolutions are acceptable to
      all. If not please let me know.<br>
      <br>
      New version at
      <a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa/">http://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa/</a><br>
      <br>
      Diffs at
<a class="moz-txt-link-freetext" href="http://www.ietf.org/rfcdiff?url1=draft-ietf-rtgwg-remote-lfa-08&amp;difftype=--html&amp;submit=Go!&amp;url2=draft-ietf-rtgwg-remote-lfa-09">http://www.ietf.org/rfcdiff?url1=draft-ietf-rtgwg-remote-lfa-08&amp;difftype=--html&amp;submit=Go!&amp;url2=draft-ietf-rtgwg-remote-lfa-09</a><br>
      <br>
      - Stewart</font><br>
  </body>
</html>

--------------070804020404070009070102--


From nobody Fri Dec 19 08:04:35 2014
Return-Path: <maho@lab.dtag.de>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F03A1A6F91 for <rtgwg@ietfa.amsl.com>; Wed, 17 Dec 2014 00:52:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.812
X-Spam-Level: 
X-Spam-Status: No, score=-0.812 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nzarp4mWl6ug for <rtgwg@ietfa.amsl.com>; Wed, 17 Dec 2014 00:52:33 -0800 (PST)
Received: from owl.lab.dtag.de (Owl.lab.DTAG.DE [194.25.1.236]) by ietfa.amsl.com (Postfix) with ESMTP id E8C041A1BBB for <rtgwg@ietf.org>; Wed, 17 Dec 2014 00:52:32 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by owl.lab.dtag.de (Postfix) with ESMTP id 1ADAA597CCB for <rtgwg@ietf.org>; Wed, 17 Dec 2014 09:52:31 +0100 (CET)
Received: from TSUNAMI-neu.114.lab.DTAG.de (o.Hippogryff.lab.dtag.de [194.25.10.166]) by owl.lab.dtag.de (Postfix) with ESMTPSA id EBF63597CC2 for <rtgwg@ietf.org>; Wed, 17 Dec 2014 09:52:30 +0100 (CET)
Message-ID: <5491444E.8070700@lab.dtag.de>
Date: Wed, 17 Dec 2014 09:52:30 +0100
From: Martin Horneffer <maho@lab.dtag.de>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: rtgwg@ietf.org
Subject: Re: Working Group last call on draft-ietf-rtgwg-lfa-manageability - IPR
References: <D08664E9.78999%jeff.tantsura@ericsson.com>
In-Reply-To: <D08664E9.78999%jeff.tantsura@ericsson.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/DmOpb5Z4dmCoqtYbgDqK8Hxkp8M
X-Mailman-Approved-At: Fri, 19 Dec 2014 08:04:31 -0800
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Dec 2014 08:52:35 -0000

I am not aware of any IPR related to draft-ietf-rtgwg-lfa-manageability.

Best regards,
Martin


Am 10.11.14 um 21:54 schrieb Jeff Tantsura:
> All,
>
> 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.  The draft will not progress (pending the results of
> the WGLC) until we have received a response from each author.
>
>
> In addition, we wanted to take this opportunity to remind the entire WG
> that the duty of disclosure is NOT limited to authors:
>
>     (c) in order for the working group and the rest of the IETF to have
>         the information needed to make an informed decision about the use
>         of a particular technology, all those contributing to the working
>         group's discussions must disclose the existence of any IPR the
>         Contributor or other IETF participant believes Covers or may
>         ultimately Cover the technology under discussion.  This applies
>         to both Contributors and other participants, and applies whether
>         they contribute in person, via email or by other means.  The
>         requirement applies to all IPR of the participant, the
>         participant's employer, sponsor, or others represented by the
>         participants, that is reasonably and personally known to the
>         participant.  No patent search is required.
>
> RFC 3979 also points out disclosure must be "as soon as reasonably
> possible":
>
>     The IPR disclosure required pursuant to section 6.1.1 must be made as
>     soon as reasonably possible after the Contribution is published in an
>     Internet Draft unless the required disclosure is already on file.
>
> Thank you!
>
>
>
> Cheers,
> Jeff
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

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

# Mail Account for technical purposes only

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


From nobody Mon Dec 22 07:16:23 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22C6D1A9091; Mon, 22 Dec 2014 07:16:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IV9R6LzzgsQq; Mon, 22 Dec 2014 07:16:06 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D2A231A19F8; Mon, 22 Dec 2014 07:16:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-rtgwg-ipfrr-ip-mib-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.9.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141222151605.22440.96204.idtracker@ietfa.amsl.com>
Date: Mon, 22 Dec 2014 07:16:05 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/jx2xuE2Engtsd-Q0D1KXr_FT9I0
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Dec 2014 15:16:17 -0000

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

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

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



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

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

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


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

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


From nobody Sat Dec 27 00:08:53 2014
Return-Path: <jeff.tantsura@ericsson.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17F9B1AD491 for <rtgwg@ietfa.amsl.com>; Sat, 27 Dec 2014 00:08:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2HakpBq8o8pO for <rtgwg@ietfa.amsl.com>; Sat, 27 Dec 2014 00:08:48 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D998F1AD4A0 for <rtgwg@ietf.org>; Sat, 27 Dec 2014 00:08:20 -0800 (PST)
X-AuditID: c618062d-f79376d000000ceb-54-549e17b46b6b
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 5B.C6.03307.4B71E945; Sat, 27 Dec 2014 03:21:41 +0100 (CET)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0195.001; Sat, 27 Dec 2014 03:08:18 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>, "draft-ietf-rtgwg-lfa-manageability@tools.ietf.org" <draft-ietf-rtgwg-lfa-manageability@tools.ietf.org>
Subject: Re: Working Group last call on draft-ietf-rtgwg-lfa-manageability
Thread-Topic: Working Group last call on draft-ietf-rtgwg-lfa-manageability
Thread-Index: AQHP/Rf7NjJCBupQsk+E64gCsxlfoJyjLCMA
Date: Sat, 27 Dec 2014 08:08:17 +0000
Message-ID: <D0C3A69E.80713%jeff.tantsura@ericsson.com>
References: <D07E84FE.77EE4%jeff.tantsura@ericsson.com>
In-Reply-To: <D07E84FE.77EE4%jeff.tantsura@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.4.140807
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BB54A49F2EBF8243B65CC5F9D9AFFE92@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupnkeLIzCtJLcpLzFFi42KZXLonXHer+LwQg7kH+S3+/tzKaLHuxAIW iwtvfjM7MHtM+b2R1WPJkp9MHl8uf2YLYI7isklJzcksSy3St0vgyphz+Tt7wWHWip23LjI1 MO5l6WLk4JAQMJG4drWwi5ETyBSTuHBvPVsXIxeHkMARRolbrf+gnOWMEqc3XWcCqWITMJD4 /+04C0hCRGASo8Takx1sIAlmAVWJ/w+XghUJC3hJ3PkzlRHEFhHwlmi98oAZwjaSeLNkFTuI zQJU/+rNGhYQm1fAXKKneyfYHCEge9OnLWA2p4CFROfkvWA1jEDnfT+1hglil7jErSfzmSDO FpBYsuc8M4QtKvHy8T9WEFtUQE/i2YbN7BBxJYk5r68xQ/TqSCzY/QnqZmuJJU+XQNnaEssW vmaGuEdQ4uTMJywTGCVmIVk3C0n7LCTts5C0z0LSvoCRdRUjR2lxalluupHBJkZgDB6TYNPd wbjnpeUhRgEORiUe3oIXc0OEWBPLiitzDzFKc7AoifPOqp0XLCSQnliSmp2aWpBaFF9UmpNa fIiRiYNTqoFx9fq5MUG2cyRjyye6ZXtlbfXnjG/SeVZyY0+aXctbYYOPFmGRYc8sz5mvUzfc /ITbJmpG1epTyfadGya9risU7Zl4ftr+13Km7ZwaL1It+8zTDsycxXioy/C/fGYLz4YUMb/v Pqvezt9hK25UdvUCG0PxSdYz+hYGVmrOv3Ub/4Q35NtaHlJiKc5INNRiLipOBADOIHfLogIA AA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/01ktannkMYuvwwzafXmCnuLJdo4
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Dec 2014 08:08:50 -0000

All,

Working Group last call has been closed, we have only recevied supporting
responses.=20
There has been comment posted (Uma C).
Could the authors please address, agree with the reviewers, confirm that
they are ready to go ahead and request publication of the updated version
of the document?


Happy New Year!

Cheers,
Jeff




-----Original Message-----
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
Date: Monday, November 10, 2014 at 10:56 AM
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Cc: Alvaro Retana <aretana@cisco.com>
Subject: Working Group last call on draft-ietf-rtgwg-lfa-manageability

>All,
>
>We are starting a working group last call on the subject document.


From nobody Sat Dec 27 21:57:29 2014
Return-Path: <yangang@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7F671ACEA6; Sat, 27 Dec 2014 21:57:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.911
X-Spam-Level: 
X-Spam-Status: No, score=-3.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D_jJg7tViUvU; Sat, 27 Dec 2014 21:57:23 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 416221ACEA4; Sat, 27 Dec 2014 21:57:23 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BNJ63004; Sun, 28 Dec 2014 05:57:21 +0000 (GMT)
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 28 Dec 2014 05:57:18 +0000
Received: from NKGEML507-MBS.china.huawei.com ([169.254.6.3]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0158.001; Sun, 28 Dec 2014 13:57:14 +0800
From: Yangang <yangang@huawei.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>, "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>
Subject: =?utf-8?B?QWJvdXQgbmV3IHJvdXRlLXBvbGljeSB5YW5nIG1vZGVsLi8vLy8v6L2s5Y+R?= =?utf-8?B?OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LXlhbi1ydGd3?= =?utf-8?Q?g-routing-policy-yang-00.txt?=
Thread-Topic: =?utf-8?B?QWJvdXQgbmV3IHJvdXRlLXBvbGljeSB5YW5nIG1vZGVsLi8vLy8v6L2s5Y+R?= =?utf-8?B?OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LXlhbi1ydGd3?= =?utf-8?Q?g-routing-policy-yang-00.txt?=
Thread-Index: AQHQIaR5ZOYENOzSHUGPHGLsoibGJJykfAsA
Date: Sun, 28 Dec 2014 05:57:13 +0000
Message-ID: <D496C972D1A13540A730720631EC73413B143242@nkgeml507-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.72.210]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/Gyvq9Oavipsy3gV1MKuZ6IhGbq4
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: Sun, 28 Dec 2014 05:57:26 -0000

SGksIEFsbA0KDQogICBNeSBjb2xsZWFndWUgYW5kIG1lIGp1c3QgZmluaXNoIHRoZSBkcmFmdCBv
ZiByb3V0ZS1wb2xpY3kgeWFuZyBtb2RlbCwgYW5kIHN1Ym1pdCBvbiBydGd3ZyB5ZXN0ZXJkYXku
IElmIHlvdSBoYXZlIHRpbWUsIHBsZWFzZSByZXZpZXcgaXQgYW5kIHByb3ZpZGUgeW91ciBjb21t
ZW50cy4NCg0KICAgUmlnaHQgbm93LCBhbG1vc3QgYWxsIHJvdXRpbmcgcHJvdG9jb2wncyB5YW5n
IG1vZGVsIGFscmVhZHkgaXMgcHJvY2Vzc2luZywganVzdCBubyBwb2xpY3kgbW9kZWwsIHNvIHdl
IHByZXBhcmUgaXQuIA0KDQogICBUaHJvdWdoIHdlIGtub3cgdGhlcmUgYXJlIG11Y2ggZGlmZmVy
ZW50IGluIHJvdXRlLXBvbGljeSwgd2Ugc3RpbGwgcHJvdmlkZSB0aGUgbW9zdCBkZXRhaWwgdGhh
dCB3ZSBjYW4gcHJvdmlkZSwgd2UgZG9uJ3QgYXNzdW1lIHdoYXQgaXMgdGhlIGJhc2ljIG1vZGVs
IGFuZCB3aGF0IGlzIHRoZSBleHBhbnNpYmlsaXR5LiBXZSB0aGluayBtYXliZSB3ZSBjYW4gZ2F0
aGVyIGFsbCBkaWZmZXJlbmNlIGF0IGZpcnN0LCBhbmQgdGhlbiB3ZSBjYW4gZ2V0IGEgYWJzdHJh
Y3QgbW9kZWwgdGhhdCBlYXN5IHRvIGV4cGFuZC4gTWF5YmUgaXQgY2FuIGltcHJvdmUgdGhlIHBy
b2dyZXNzLg0KDQogICBGaW5hbGx5LCBzdGlsbCBhYm91dCB0aGUgcmV2aWV3IGNvbW1lbnRzLiBB
bGwgb2YgeW91ciBjb21tZW50cyB3aWxsIGJlIHdlbGNvbWUgYWx3YXlzLg0KDQpUaGFua3MgYSBs
b3QuDQpZYW5nYW5nLg0KDQotLS0tLemCruS7tuWOn+S7ti0tLS0tDQrlj5Hku7bkuro6IGludGVy
bmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10gDQrl
j5HpgIHml7bpl7Q6IDIwMTTlubQxMuaciDI35pelIDE1OjEyDQrmlLbku7bkuro6IFpodWFuZ3No
dW53YW47IFpodWFuZ3NodW53YW47IFlhbmdhbmc7IFlhbmdhbmcNCuS4u+mimDogTmV3IFZlcnNp
b24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC15YW4tcnRnd2ctcm91dGluZy1wb2xpY3kteWFuZy0w
MC50eHQNCg0KDQpBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQteWFuLXJ0Z3dnLXJvdXRpbmct
cG9saWN5LXlhbmctMDAudHh0DQpoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFNo
dW53YW4gWmh1YW5nIGFuZCBwb3N0ZWQgdG8gdGhlIElFVEYgcmVwb3NpdG9yeS4NCg0KTmFtZToJ
CWRyYWZ0LXlhbi1ydGd3Zy1yb3V0aW5nLXBvbGljeS15YW5nDQpSZXZpc2lvbjoJMDANClRpdGxl
OgkJWWFuZyBEYXRhIE1vZGVsIGZvciBSb3V0aW5nIFBvbGljeQ0KRG9jdW1lbnQgZGF0ZToJMjAx
NC0xMi0yNw0KR3JvdXA6CQlJbmRpdmlkdWFsIFN1Ym1pc3Npb24NClBhZ2VzOgkJNTANClVSTDog
ICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC15YW4t
cnRnd2ctcm91dGluZy1wb2xpY3kteWFuZy0wMC50eHQNClN0YXR1czogICAgICAgICBodHRwczov
L2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC15YW4tcnRnd2ctcm91dGluZy1wb2xpY3kt
eWFuZy8NCkh0bWxpemVkOiAgICAgICBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC15
YW4tcnRnd2ctcm91dGluZy1wb2xpY3kteWFuZy0wMA0KDQoNCkFic3RyYWN0Og0KICAgVGhpcyBk
b2N1bWVudCBkZWZpbmVzIGEgWUFORyBkYXRhIG1vZGVsIHRoYXQgY2FuIGJlIHVzZWQgdG8gY29u
ZmlndXJlDQogICBhbmQgbWFuYWdlIHJvdXRpbmcgcG9saWNpZXMuDQoNCg0KICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIA0KDQoNClBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUg
b2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24gdW50aWwgdGhlIGh0bWxpemVk
IHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCg0KVGhl
IElFVEYgU2VjcmV0YXJpYXQNCg0K

