RE: Request for RTGWG Working Group adoption for draft-bashandy-rtgwg-segment-routing-ti-lfa

Chris Bowers <cbowers@juniper.net> Mon, 28 May 2018 23:30 UTC

Return-Path: <cbowers@juniper.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E34A12E852; Mon, 28 May 2018 16:30:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.711
X-Spam-Level:
X-Spam-Status: No, score=-0.711 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, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 PXAks2a4ay1q; Mon, 28 May 2018 16:30:27 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADE8712E045; Mon, 28 May 2018 16:30:27 -0700 (PDT)
Received: from pps.filterd (m0108160.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w4SNTOw3011161; Mon, 28 May 2018 16:30:17 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=zhtTGzmx7sCeHmTyll4zsJgG3dR6aAH+yr6fUHLDExk=; b=sfoCl7j3/KGrW7qcEJMNhDPsxYGQyRe4wQ4mqNf9QlM2eVzabi8evid0k4uNGy6l5D8O z1GCpTPtOxFJXrl1mhIR6rB2a+BDQ7HgHt/1pY2Y32eYWqZ5b0fzFCvcV62MkvVDCZMP TrfjVFd4/s1PRZ54pVAbPHl/F5VLTCdp98XB5TNHPDaoufTj2o6CB9RDeuzkZ0GlDX0C oLZpzIXU1E/utkH36C2iHe858qnC9EwdZpVNJCMO8gw7d6/7z6gPslVClijy+J9cqXis XjMbTY9Q9d6aVnX1jyoSjTYwnTbazUBpaYEdEBh3GWYqlhvegZ7E7q96yVYcpRy1pcR0 Xg==
Received: from nam03-dm3-obe.outbound.protection.outlook.com (mail-dm3nam03lp0019.outbound.protection.outlook.com [207.46.163.19]) by mx0b-00273201.pphosted.com with ESMTP id 2j8apvhae9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 28 May 2018 16:30:17 -0700
Received: from SN6PR05MB4430.namprd05.prod.outlook.com (52.135.74.27) by SN6PR05MB4221.namprd05.prod.outlook.com (52.135.67.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.820.5; Mon, 28 May 2018 23:30:14 +0000
Received: from SN6PR05MB4430.namprd05.prod.outlook.com ([fe80::5167:3481:a63e:e6a1]) by SN6PR05MB4430.namprd05.prod.outlook.com ([fe80::5167:3481:a63e:e6a1%2]) with mapi id 15.20.0820.010; Mon, 28 May 2018 23:30:14 +0000
From: Chris Bowers <cbowers@juniper.net>
To: Jeff Tantsura <jefftant.ietf@gmail.com>, Ahmed Bashandy <abashandy.ietf@gmail.com>, "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>, Stewart Bryant <stewart.bryant@gmail.com>
CC: "draft-bashandy-rtgwg-segment-routing-ti-lfa@ietf.org" <draft-bashandy-rtgwg-segment-routing-ti-lfa@ietf.org>, "martin.vigoureux@nokia.com" <martin.vigoureux@nokia.com>, "pfrpfr@gmail.com" <pfrpfr@gmail.com>, "cfilsfil@cisco.com" <cfilsfil@cisco.com>, "bruno.decraene@orange.com" <bruno.decraene@orange.com>, "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "daniel.voyer@bell.ca" <daniel.voyer@bell.ca>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: Request for RTGWG Working Group adoption for draft-bashandy-rtgwg-segment-routing-ti-lfa
Thread-Topic: Request for RTGWG Working Group adoption for draft-bashandy-rtgwg-segment-routing-ti-lfa
Thread-Index: AQHT3HY4sIlczD3L7UWolZy4ncPuCKQpQkoAgA5RxICADkCEAIAAB9uAgAAc/tA=
Date: Mon, 28 May 2018 23:30:14 +0000
Message-ID: <SN6PR05MB44305802FF3330DC2AE27F9CA96E0@SN6PR05MB4430.namprd05.prod.outlook.com>
References: <1e42030f-3d68-fca3-500c-95ab7303e7cd@gmail.com> <F0098308-4F1E-4596-B3F9-B6740BA88F9A@gmail.com> <bfbe9775-ee81-b1fe-bb1f-a02392bc6fb5@gmail.com> <43389eec-6d63-ee35-54ed-19562b24562b@gmail.com> <12E9EB99-2970-49B6-9407-FE6AEAB3A0BB@gmail.com>
In-Reply-To: <12E9EB99-2970-49B6-9407-FE6AEAB3A0BB@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.0.300.84
dlp-reaction: no-action
x-originating-ip: [66.129.239.12]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN6PR05MB4221; 7:BINdWs9ViPdtrEQXwKtGHnyZSV/QUi0VXd6pDfpmeNZftGnDVWsNxOorxCYlH3v7FFE927EcEG5imyLSDfmSZwIhViPIJgfYyXJu/jPE6FeM9pm80wbaV3KCCVAG9/HO3ieLyFW4+g/evUccG9/31h0oWpxnDVaVlzqVoO5JKCKzAOLnQ0hz+0KSug2HOQey3BqmKagIQUp4lwZzLjkYZoyvya/r1OqowjnVp3InPTF9lbTsY9DJGRE12nXawqcb
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:(109105607167333); BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(48565401081)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:SN6PR05MB4221;
x-ms-traffictypediagnostic: SN6PR05MB4221:
x-microsoft-antispam-prvs: <SN6PR05MB422175151B0A3E245E1CB1A9A96E0@SN6PR05MB4221.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(226690903318834)(10436049006162)(120809045254105)(192374486261705)(82608151540597)(85827821059158)(109105607167333)(100405760836317)(95692535739014);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3002001)(93006095)(93001095)(10201501046)(3231254)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123562045)(20161123560045)(20161123564045)(6072148)(201708071742011)(7699016); SRVR:SN6PR05MB4221; BCL:0; PCL:0; RULEID:; SRVR:SN6PR05MB4221;
x-forefront-prvs: 06860EDC7B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(366004)(39380400002)(346002)(39860400002)(376002)(43544003)(199004)(189003)(51444003)(37854004)(8656006)(97736004)(76176011)(11346002)(14454004)(26005)(9686003)(236005)(186003)(68736007)(55016002)(53946003)(7696005)(33656002)(790700001)(3846002)(6116002)(8676002)(53936002)(99286004)(2906002)(8936002)(86362001)(3660700001)(74316002)(54896002)(6306002)(3280700002)(6506007)(102836004)(59450400001)(81166006)(81156014)(25786009)(966005)(110136005)(54906003)(4326008)(106356001)(53546011)(446003)(6246003)(316002)(105586002)(6436002)(19609705001)(229853002)(5250100002)(606006)(7736002)(486006)(2900100001)(93886005)(561944003)(39060400002)(66066001)(5660300001)(476003)(2501003)(478600001)(7416002)(579004); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR05MB4221; H:SN6PR05MB4430.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: IbD0zkPz3Tutpvf+ZpcsVzBOmu6fujMPcTXZqHzsa5++EjeNI7P2/J/vsTq2h/HuAzNN1aD4eYsh4w7u15k/xBBf92P7rx+S5I3LDMatje863EXK9W54LhFEu4b92Ej5lRlhxwR3SodE4UT8ppJkO3YJ/MUcS96CXfkpPmol/TSs9yZy5FCXQouUn93juXS2
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_SN6PR05MB44305802FF3330DC2AE27F9CA96E0SN6PR05MB4430namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 57e1f041-5d1e-4fd8-1c22-08d5c4f2f6fe
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 57e1f041-5d1e-4fd8-1c22-08d5c4f2f6fe
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 May 2018 23:30:14.7302 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR05MB4221
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-28_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805280279
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/BE8uAiVqPptF6eqsRx1x2FTer8c>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 28 May 2018 23:30:33 -0000

Ahmed,

Several participants in the WG (including Stewart) have provided feedback requesting that the draft address particular issues.
The response you have provided to this feedback is that these issues are out-of-scope for the draft, so they will not be addressed.
I have seen no change in the text of the draft to incorporate this feedback.

It is up to the working group to decide what is the scope of a document it works on.  I do not think that it would be productive
to conduct a poll for WG adoption until the scope of the draft is broadened to address the feedback that has already been provided.

Chris


From: Jeff Tantsura <jefftant.ietf@gmail.com>
Sent: Monday, May 28, 2018 4:27 PM
To: Ahmed Bashandy <abashandy.ietf@gmail.com>om>; rtgwg-chairs@ietf.org; Stewart Bryant <stewart.bryant@gmail.com>
Cc: draft-bashandy-rtgwg-segment-routing-ti-lfa@ietf.org; martin.vigoureux@nokia.com; pfrpfr@gmail.com; cfilsfil@cisco.com; bruno.decraene@orange.com; stephane.litkowski@orange.com; daniel.voyer@bell.ca; rtgwg@ietf.org
Subject: Re: Request for RTGWG Working Group adoption for draft-bashandy-rtgwg-segment-routing-ti-lfa

Hi Ahmed,

I’m awaiting Stewart’s response.
Thanks!

Cheers,
Jeff
From: Ahmed Bashandy <abashandy.ietf@gmail.com<mailto:abashandy.ietf@gmail.com>>
Date: Monday, May 28, 2018 at 13:59
To: Jeff Tantsura <jefftant.ietf@gmail.com<mailto:jefftant.ietf@gmail.com>>, rtgwg-chairs <rtgwg-chairs@ietf.org<mailto:rtgwg-chairs@ietf.org>>
Cc: <draft-bashandy-rtgwg-segment-routing-ti-lfa@ietf.org<mailto:draft-bashandy-rtgwg-segment-routing-ti-lfa@ietf.org>>, <martin.vigoureux@nokia.com<mailto:martin.vigoureux@nokia.com>>, <pfrpfr@gmail.com<mailto:pfrpfr@gmail.com>>, <cfilsfil@cisco.com<mailto:cfilsfil@cisco.com>>, <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>, <stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, <daniel.voyer@bell.ca<mailto:daniel.voyer@bell.ca>>, RTGWG <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: Re: Request for RTGWG Working Group adoption for draft-bashandy-rtgwg-segment-routing-ti-lfa

Hi Jeff

All comments have been addressed as shown in the email below

Can we initiate the WG adoption

Ahmed



On 5/19/18 12:20 PM, Ahmed Bashandy wrote:
Hi Jeff

These comments are already addressed with the exception of the minor comment about section 5.3.1 and 5.3.2. But for the convenience of everyone, I will respond to each specific comment here

See "#Ahmed" below


Thanks

Ahmed

> Reviewer: Stewart Bryant

> Review result: Has Issues

>

> These review comments were incorrectly posted against the uloop draft,

> apologies for any confustion.

>

> I have been asked to perform an early review of this document on

> behalf of the Routing Directorate.

>

> Summary:

>

> A document on this subject is something that the WG should publish,

> but I think that there are number of issues that the WG need to

> discuss and reach consensus on before deciding whether or not they

> should adopt this draft as a starting point for that work.

>

>

> Major Issues:

>

> Before I get into the substance I am surprised that there are no IPR

> disclosures. In an earlier and related work

> (draft-francois-segment-routing-ti-lfa-00) there were three IPR

> disclosures.

#Ahmed

The IPR link is

https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-bashandy-rtgwg-segment-routing-ti-lfa<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_ipr_search_-3Fsubmit-3Ddraft-26id-3Ddraft-2Dbashandy-2Drtgwg-2Dsegment-2Drouting-2Dti-2Dlfa&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=mIF18ha_B3lsg_QPPZ0uZE5Mp5Q7LXQIPJHrP9QhvL4&m=hRw9JYX16QjABo0X8NzFeA4qtZ406HEzUaYNGbxzzGQ&s=i0BSrEO9trtQg-svJmisngedg7C2ALPRCMA49HKC8Jg&e=>

If there is anything else for us to do regarding IPR I will be more than happy to take care of



>

> The work has four basic components, the concept of resolving the

> problem of P and Q being non-adjacent, the use of SR to solve the

> non-adjacency, the use of the post convergence path following failure

> and the applicability of these techniques to an SR network. The first

> and second points seem of utility in non-SR networks, and so I am

> surprised that they are not called out as such, in the first case

> perhaps with consideration to strategically places RSVP tunnels, or

> binding segments.

The draft already mentions that the work builds on top of existing FRR work. For example

the second statement of the abstract already says

  builds on proven IP-FRR concepts being

  LFAs, remote LFAs (RLFA), and remote LFAs with directed forwarding

  (DLFA).

The statement about the possibility of using RSVP is clearly outside the scope of document as mentioned in first paragraph of the introduction.



>

> The issue of mapping repair path to the post convergence path to the

> something that has always concerned me in this concept. It is true

> that traffic that always passes through the PLR will experience the

> properties the authors describe, but not all traffic will pass through

> the PLR post convergence. The post failure path will be topology

> dependent, and may take a different path from the point of ingress.

#Ahmed

The fourth paragraph in the introduction clearly mentions that we are protecting the traffic passing through the PLR.



>

> I am also concerned that the authors do not discuss the need for loop

> free convergence, since although traffic going through the repair path

> will be loop-free, traffic arriving at the PLR might not be. Consider

> for example a topology fragment that looks like a clock with a router

> at each minute. Traffic enters at 9 o'clock, leave at 3 o'clock and

> goes via 12 o'clock and 12 o'clock fails.  The routers 9..12 will

> re-converge at different times and this may give rise to the

> micro-looping of traffic trying to get to the PLR. A summary of the

> problem and a pointer to the companion draft may be sufficient.

#Ahmed

The last statement in the first paragraph in the introduction refers the reader to the uloop avoidance draft which handles non-local failures



>

> Finally on the basic concept it would be good to state up from whether

> the proposal is constrained solely to SR networks, or whether the

> authors believe that the concept is of wider applicability. It see no

> reason why it would be constrained to only work on SR networks.

#Ahmed

As it is quite clear from the title of the draft as well as many statements inside it, the scope of document is restricted to segment routing.



>

> There is no discussion of multiple failures, nor as far as I can see

> of failures that are worse than anticipated. This is an important

> point that needs to be established early. Some methods, (MRT)

> intrinsically address multiple failures, others (NV) intrinsically

> exclude them. Simple LFA needs a supervisor to quickly abandon all

> hope when they occur.

#Ahmed

As specified in the 3rd paragraph of the introduction the scope of the document is limited to single link, single node, and single local SRLG failure.



>

> In an SR network the paths used are not the shortest paths, they are a

> collection of shortest paths, so there needs to be some discussion on

> the interaction between the SR paths and repair paths to consider

> whether it is unconditionally safe against forwarding loops. It would

> presumably be so if the authors borrowed the concept of repair

> addresses rather than normal forwarding addresses from not-via, but I

> don't think they have done this.

#Ahmed

Again the second statement of the 1st paragraph of the Introduction says



  By relying on segment routing this document provides

         a local repair mechanism for standard IGP shortest path



So the scope of the document is quite clear



>

> There should also be some discussion on the original path constraints

> that are applicable to the repair. Presumably the ingress node

> constrained the traffic to go though failed node F for a reason. If

> the repair is unconstrained that reason could be violated, but this is

> not discussed in the text.

#Ahmed

Same response as the response to the previous comment. The scope is standard IGP shortest paths





>

>

> In the Security section you say:

>

>     The behavior described in this document is internal functionality

>     to a router that result in the ability to guarantee an upper bound

>     on the time taken to restore traffic flow upon the failure of a

>     directly connected link or node. As such no additional security

>     risk is introduced by using the mechanisms proposed in this

>     document.

>

>

> SB> I am not sure that the above is correct. There may be a security

> reason

> SB> why a packet was steered along a path which breaks when you use

> this

> SB> technique.

#Ahmed

The security consideration section has been modified to to indicate that

the traffic is being steered over the post convergence path and hence there

is no security risk because this is the path that the operator intended to use

after the failure through the metrics configured on the links. In fact by expediting

rerouting the traffic over the intended post convergence path without waiting

for IGP reconvergence, we have introduced a minor security enhancement by reducing

misforwarding and/or traffic drop







>

> In the conclusion you say:

>

>     The

>     mechanism is able to calculate the backup path irrespective of the

>     topology as long as the topology is sufficiently redundant.

>

>

> SB> That is certainly true in classic. I am not sure this is

> universally

> SB> true under SR which includes the use of non-shortest path and

> SB> binding segments.



#Ahmed

Again the document is restricted to IGP shortest path as mentioned in the introduction





> Minor issues:

>

>     For each destination in the network, TI-LFA prepares a data-plane

>     switch-over to be activated upon detection of the failure of a

>     link used to reach the destination.

>

> SB> To make the scaling clearer to the reader, I think you need

> SB> to make it clear that for each protected link, you determine

> SB> the repair needed to reach every destination reachable over that

> SB> link. You sort of say that, but it's a bit hidden.

#Ahmed

I do not understand the difference between the text in the draft and the

text that you are proposing. We think that our text is quite clear





>     We provide the TI-LFA approach that achieves guaranteed coverage

>     against link, node, and local SRLG failure, in any IGP network,

>     relying on the flexibility of SR.

>

> SB> Should that be any SINGLE link.... failure?

#Ahmed

As mentioned above few times above, the introduction clearly mentions *single*





> In the text (and the text that follows)

>

>     To do so, S applies a "NEXT" operation on Adj(S-F) and then two

>     consecutive "PUSH" operations: first it pushes a node segment for

> F,

>     and then it pushes a protection list allowing to reach F while

>     bypassing S-F.

>

> You need to reference the SR operations.

#Ahmed

This paragraph is in Section 5.2.1. The latest version refers to the SR draft



>

> Also you are considering Adj segments, and presumably they were there

> for a reason, but you do not discuss that.

#Ahmed

Section 5.2 discusses protecting adjacency segments





>

> In 5.3.1 and 5.3.2 you have a list of conditions, but do not make it

> clear whether any or all must be true.

>

#Ahmed

The intention is for all of the conditions to be true. I will make it clear in the next version





> Nits

>

> 1. Introduction

>

>     Segment Routing aims at supporting services with tight SLA

>     guarantees [1]. This document provides a local repair mechanism

>     relying on SR-capable of restoring end-to-end connectivity in the

>     case of a sudden failure of a network component.

>

> SB> Grammar needs a little work in the last sentence.

#Ahmed

Addressed in the latest version of the document





> In Fig 1, I assume that the blobs are network fragments.

>

> In the conclusion you say:

>     This document proposes a mechanism that is able to pre-calculate a

>     backup path for every primary path so as to be able to protect

>     against the failure of a directly connected link or node.

> SB> you need to add SRLG

#Ahmed

Addressed in the latest version of the draft


On 5/10/18 9:40 AM, Jeff Tantsura wrote:

Hi Ahmed,



We would like you to address the comments from Early Review and get OK from Stewart, before progressing the document

 https://datatracker.ietf.org/doc/review-bashandy-rtgwg-segment-routing-ti-lfa-00-rtgdir-early-bryant-2017-05-31/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_review-2Dbashandy-2Drtgwg-2Dsegment-2Drouting-2Dti-2Dlfa-2D00-2Drtgdir-2Dearly-2Dbryant-2D2017-2D05-2D31_&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=mIF18ha_B3lsg_QPPZ0uZE5Mp5Q7LXQIPJHrP9QhvL4&m=hRw9JYX16QjABo0X8NzFeA4qtZ406HEzUaYNGbxzzGQ&s=xMxNv--9p-MRxL0OnPyOZs76OvnidWNl7oTWWXG7B3g&e=>



Please let us know when this could be done.



Cheers,

Jeff

On 4/25/18, 02:17, "Ahmed Bashandy" <abashandy.ietf@gmail.com><mailto:abashandy.ietf@gmail.com> wrote:



    Hi



    We would like to request the WG adoption of

    draft-bashandy-rtgwg-segment-routing-ti-lfa-04.



    The draft has been stable for a long while and the IPR declaration has

    been recorded



    The latest version addresses all comments and the draft has been

    presented in IETF-96 and IETF-99



    Thanks



    Ahmed