
From nobody Mon Jan  5 10:10:55 2015
Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 402F81A8729; Mon,  5 Jan 2015 10:10:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 k4anE4vnfWjI; Mon,  5 Jan 2015 10:10:43 -0800 (PST)
Received: from mail-yk0-x22a.google.com (mail-yk0-x22a.google.com [IPv6:2607:f8b0:4002:c07::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E11041A871E; Mon,  5 Jan 2015 10:10:42 -0800 (PST)
Received: by mail-yk0-f170.google.com with SMTP id 200so3708624ykr.29; Mon, 05 Jan 2015 10:10:42 -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=V0lJELvIeFBEmJbqXbvIakg5Ui+Bl2Lj1gsgRXFWaiA=; b=TcQWCKy7AwqwvqQMoAMs3cpXZAbj7gN1CnQBd1H2f0bE5MusNVvGxcIPUOX+Sg6CuJ 2Bs6Gil7PiVf9Z4j6669kIGiKPHqdfw7VrtsGgnpSq6CZw33dRpkwPLHtlpJ60QvoxCa sbSm2DiKywhgjZbHlL44pq6KozOzLWg5fD8UC3WlSQ1mzXy3tx2EUNy9GHMkxvvoik9G 6v/uaZm+JUs9kr4Z7Qv8Fnid06F4KDAM0w63M8o/DQLuKzWtDJo1cd0Tn8k3Ug7z08lu cGrsA+5JkXWyv24W630b5xEasKoldz97eVho0TkGieIjaWoff4ag4EZHzkZOfWxbH9ah 38Qw==
MIME-Version: 1.0
X-Received: by 10.170.196.203 with SMTP id n194mr67976299yke.55.1420481442105;  Mon, 05 Jan 2015 10:10:42 -0800 (PST)
Received: by 10.170.133.18 with HTTP; Mon, 5 Jan 2015 10:10:42 -0800 (PST)
In-Reply-To: <20141229160904.27130.40113.idtracker@ietfa.amsl.com>
References: <20141229160904.27130.40113.idtracker@ietfa.amsl.com>
Date: Mon, 5 Jan 2015 13:10:42 -0500
Message-ID: <CAG4d1rfFLuknjUvSKfu8frRR7XLfwvMmwa9qGhV6Li6ETpZLwA@mail.gmail.com>
Subject: Re: Adrian Farrel's Discuss on draft-ietf-rtgwg-remote-lfa-09: (with DISCUSS and COMMENT)
From: Alia Atlas <akatlas@gmail.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=001a1139ef04c44f02050beb9b76
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/wSGSZEWghOwGoqm8QcNzxDVkxvc
Cc: "draft-ietf-rtgwg-remote-lfa@tools.ietf.org" <draft-ietf-rtgwg-remote-lfa@tools.ietf.org>, "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>, The IESG <iesg@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: Mon, 05 Jan 2015 18:10:51 -0000

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

[+rtgwg mailing list]

Adrian,

Thanks very much for working through the example.  It was very interesting
to see an understanding by someone who isn't as close to the problem-space
and helped pick up on imprecisions and lack of clarity in the definitions.

Not to speak for Stewart - whom I'm sure will be responding quite soon,
but...

On Mon, Dec 29, 2014 at 11:09 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Adrian Farrel has entered the following ballot position for
> draft-ietf-rtgwg-remote-lfa-09: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> I'm placing this Discuss because I found the description of the
> algorithm in 4.2.1 and the worked example in Section 2 to be at odds
> with the definitions of P-space, extended P-space, and Q-space.
>
> I have been able to make things work by messing with the algorithm and
> keeping the current definitions. You could probably do it by keeping
> the algorithm and messing with the definitions.
>

Yes - we want to keep the algorithm.  In particular, the pseudo-code gets it
write and the definitions are a little sloppy.   Stewart clarified a bit
around the
extended P-space not including paths through the failed link in the text
before
I put it to the IESG.



> My workings were as follows, based on the example in Section 2:
>
> >            S---E
> >           /     \
> >          A       D
> >           \     /
> >            B---C
> >
> >  In Figure 1 S can reach A, B, and C without going via E;
> >  these form S's extended P-space.
>
> First, this should say "via S-E" and "extended P-space with respect to
> S-E".
>
> But...
> >  Extended P-space
> >                 The union of the P-space of the neighbours of a
> >                 specific router with respect to the protected link
>
> (Noting that 4.2.1.2 changes this definition *significantly* by saying
> that the neighbour at the far end of the failing link - i.e., E in this
> case - must be excised from the list of neighbours whose P-spaces are
> combined).
>

To be fair, the definition of P-space (below) includes that the paths
can't transit the protected link (S-E in the example).

I think that the definition needs to be updated to be "the neighbors of a
specific router that are reachable without going via the protected link".

When there's only a single link S-E, S has no direct way of forcing traffic
to E so E's P-space can't be included.

...and...
> >  P-space        P-space is the set of routers reachable from a
> >                 specific router using the normal FIB, without any path
> >                 (including equal cost path splits) transiting the
> >                 protected link.
>
> Now, S's neighbours are A and E.
> The P-space of A with respect to S-E is {B, C}
> And the P-space of E with respect to S-E is {C, D}
> So the extended P-Space of S with respect to S-E is {B, C, D}
>
> Something is broken!
>

Yes, can't include the P-space of E when the failed link is S-E and there's
no way to reach E directly (one hop) from S.


> {A, B, C} is not even the (not extended) P-space of S with respect to
> S-E which is {A, B} since C is not in that set because of SEDC.
> On the other hand {A, B, C} *is* the extended P-space of E wrt S-E.
>

Although, I would observe that the pseudocode in 4.2.1 does derive
> A, B, C as the extended P-space of S wrt S-E, but I think that is
> because it has an entirely different definition of an extended P-space.
>

?? Because it omits E?  Do you see anything else different that needs
to be better clarified?


> Now...
> >  Q-space        Q-space is the set of routers from which a specific
> >                 router can be reached without any path (including
> >                 equal cost path splits) transiting the protected link.
> ...so the Q-space of S wrt S-E is {A, B} since CDES.
> And, for the record, the Q-space or E wrt S-E is {C, D}
>
> Now, to compound the confusion, the example determines the PQ nodes for
> S wrt S-E by taking the intersection of the extended P-space for S wrt
> S-E  and the Q-space of E wrt S-E. This is done notwithstanding the
> definition...
>
> >  PQ node        A node which is a member of both the P-space and the
> >                 Q-space.  Where extended P-space is in use it is a
> >                 node which is a member of both the extended P-space
> >                 and the Q-space.  In remote LFA this is used as the
> >                 repair tunnel endpoint.
>

Yup - so clearly it means "of both the extended P-space of the PLR (S) and
the Q-space of the far-end of the failed link (E)".  Some improved
definitions
are definitely needed.


> This definition gives the PQ nodes of S wrt SE as either
> - the intersection of {A, B} and {A, B} if P-space is being discussed
> or
> - the intersection of {B, C, D} and {A, B} if extended P-space is being
>   used.
>
> So the correct tunnel end point for your example is B.
> But it clearly doesn't work since traffic to E that is tunneled to B may
> still be ECMP routed back along BAS.
>
> So I think in this whole example, you sit at S and you say "I want to
> protect traffic to E". Then you work out the extended P-space of *E* wrt
> S-E (which is {A, B, C}) and the Q-space of *E* wrt S-E (which is
> {C, D}) giving you the correct PQ node for S to use to protect traffic
> to E in the event of a failure of S-E as C.
>

Extended-P space is the space that the PLR S can send traffic to - what
nodes
can it reach without using the failed link.

Q-space is what nodes can reach the far-end E of the failed-link S-E
without using
the failed link.

Obviously the definitions need improvement.


> It is simple! All you have to do is update the text to describe the
> actual process and not the wrong one. Then the right result will pop
> out :-)
>
> The replacement is
> OLD
>    In Figure 1 S can reach A, B, and C without going via E;
>    these form S's extended P-space.
> NEW
>    In Figure 1 S can reach A and B without going via S-E, and
>    D can reach B and C without going via S-E. So E's extended P-space
>    with respect to S-E is the nodes A, B, and C.
> END
>
>
> BUT, given all of this, are you sure that Section 4.2.1 is right? I'm
> not.
>

Yes, not concerned about that.  You are just high-lighting some imprecisions
and lack of clarity in the definitions.


> ------
>
> Shouldn't the pseudocode in 4.3 be enclosed in code component macros to
> match with the copyright TLP etc.?


> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> This is not my area of expertise so please excuse the brevity of the
> rest of this review.
>
> ---
>
> Please s/draft/document/ throughout (except the boilerplate and
> filename) so that it can be published as an RFC (which is not a draft).
>
> ---
>
> Although it causes some pain with abbreviations and a little more care
> in explanation, you need to put the Introduction as the first section in
> the document.
>
> ---
>
> You are using RFC 5714 as a Normative Reference by making me go there
> for the definition of terms. Please move it to the correct section.
>
> ---
>
> IMHO your definition of FIB is rather loose.  Fortunately (?) "FIB" is
> barely used in this document, so it might not be important, but if you
> wanted to fix it:
> - you are talking about IP packets in this document
>

Mostly MPLS actually...


> - the actions are, I think, limited to forwarding actions
>
> ---
>
> This comment applies iff the resolution of the Discuss is not a complete
> change to the terminology!
>
> I think definitions need to be tighter or omitted from this part of the
> document. The definitions in 4.2.1 are more verbose and probably for
> good reason. If you feel you need to retain these definitions early in
> the document and can't lift the text from 4.2.1 then you need to address
> the concerns below.
>
>    P-space        P-space is the set of routers reachable from a
>                   specific router using the normal FIB, without any path
>                   (including equal cost path splits) transiting the
>                   protected link.
>
> "the protected link"? There is only one protected link?
>
> Since the example is worded as...
>
>                   For example, the P-space of S with respect to link
>                   S-E, is the set of routers that S can reach without
>                   using the protected link S-E.
>
> ...I think you need...
>
>    P-space        The P-space of a router with respect to a specific
>                   protected link is the set of routers reachable from
>                   the specific router using the normal FIB, without any
>                   path (including equal cost path splits) transiting the
>                   protected link.
>
> Similarly, you need...
>
>    Extended P-space
>                   The union of the P-spaces of all of the neighbours of
>                   a specific router with respect to a single specific
>                   protected link (see Section 4.2.1.2).
>
> But note that 4.2.1.2 makes a significant change to this definition.
>
>    Q-space        The Q-space for a specific router with respect to a
>                   specific protected link is the set of routers from
>                   which the specific router can be reached without any
>                   path (including equal cost path splits) transiting the
>                   protected link.
>
>    PQ node        A PQ node is a node which is a member of both the
>                   P-space and the Q-space for the same router and with
>                   respect to the same protected link.
>
>                   Where extended P-space is being discussed, a PQ node
>                   is a node which is a member of both the extended
>                   P-space and the Q-space for the same router and with
>                   respect to the same protected link.
>
>                   In remote LFA the repair tunnel endpoint is a PQ node.
>
> Throughout the text, however, the terms are used rather loosely. For
> example, when discussing Figure 1 you say "S's extended P-space", but
> this is really "S's extended P-space with respect to S-E". Someone
> familiar with the work might say that it is obvious from the context
> that we are discussing the link S-E, and it is, but the terminology
> needs to be tight.
>
> ---
>
> There is some difficult terminology in Section 2
>
>    If all link costs are equal, the link S-E cannot be fully protected
>    by LFAs.  The destination C is an ECMP from S, and so can be
>    protected when S-E fails, but D and E are not protectable using LFAs.
>
> Is it the link or the node that is protected (or the traffic)? Perhaps
> this could be rewritten to be less ambiguous.
>
> ---
>
> Section 2
>
>    B
>    has equal-cost paths via B-A-S-E and B-C-D-E and so may go through
>    S-E.
>
> I don't think B is going anywhere. Maybe...
>
>    B
>    has equal-cost paths to E via B-A-S-E and B-C-D-E and so may reach E
>    through S-E.
>
> ---
>
> Section 2
>
>    In MPLS networks the targeted LDP
>    protocol needed to learn the label binding at the repair tunnel
>    endpoint is a well understood and widely deployed technology.
>
> But it would still benefit from a citation or a forward reference to
> section 7.
>
> ---
>
> I enjoyed 3.2
>
>    relatively rare as is the incidence of failure in a well managed
>    network.
>
> So, managing my network well is protection against back-hoes. Nice.
>

LOL - the argument is about the set-up time to be protected again and what
is the interval between failures.  The editors and WG have decided that this
trade-off is acceptable - but I'd also prefer to see it more clearly
articulated.


> ---
>
> In 3.2
>
>    Multiple
>    repairs MAY share a tunnel end point.
>
> 1. s/repairs/repair tunnels/
> 2. s/MAY/may/ since this is not an implementation or operational choice,
>    but a fact of life.
>
> ---
>
> In 4.2 you have truncated...
>
>    The repair tunnel endpoint needs to be a node in the network
>    reachable from S without traversing S-E.
>
> ...and...
>
>    o  The repair tunneled point MUST be reachable from the tunnel source
>       without traversing the failed link; and
>
> You mean "reachable using the normal FIB" I think.
>

Not quite because if the repair tunnel endpoint is in the extended P-space
and
not the P-space, then S has to force the first hop rather than send it via
the normal FIB.

 ---

>
> Section 4.3
>
>    The preceding text has mostly described the computation of the remote
>    LFA repair target (PQ) in terms of the intersection of two
>    reachability graphs computed using SPFs.
>
> "mostly"?
>
> "reachability graphs"? Were they? Or were they reachability sets?
>
> ---
>
> Your pseducode in 4.3 invokes an unresolved (and undescribed) function
> Compute_Forward_SPF().
>
> Actually, I think this is a bogus line that can be deleted.
>
> ---
>
> 4.3 has
>
>                           if ( D_opt(n, y) <
>                                   D_opt(n,self) + D_opt)(self, y)
>
> Surely this is
>
>                           if ( D_opt(n, y) <
>                                   D_opt(n,self) + D_opt(self, y) )
>
> ---
>
> I think the introduction of "pseudonode" in 4.3 may be a little without
> context.
>
> ---
>
> Section 7
>    If for any reason the TLDP session cannot
>    not be established
>
> s/cannot not/cannot/
>
> ---
>
> I think [RFC5424] and [RFC3411] are pretty poor references to give in
> section 7. You appear to be saying that an implementation that cannot
> establish a TLDP session should write a MIB module, standardise it, and
> then report an error.
>
> Can't you find an existing LDP MIB module that reports Session-up
> failures?
>
> Or maybe just delete "using any well known mechanism such as Syslog
> [RFC5424] or SNMP [RFC3411]."
>
> ---
>
> Why is the discussion of microloops on network re-converges considered
> to be a management consideration (by inclusion in Section 9). Surely it
> is a deployment or operational consideration.
>

I wanted that text somewhere in the doc.  Adding an operational
considerations
section to put it in would be fine.



> ---
>
> I think you can strengthen the security considerations. You have:
>
>    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.
>
> 1. "To prevent their use" is surely consistent with a "MUST".
>    The fact that you want to say "SHOULD" means that you need to turn
>    the text around...
>
>    IP repair tunnel endpoints (where used) SHOULD be assigned from a set
>    of addresses that are not reachable from outside the routing domain.
>    This would prevent their use as an attack vector.
>
> 2. You can add a note about what traffic can be placed into a repair
>    tunnel. You already have this earlier in the document, and it is
>    worth restating.
>
> 3. I think you should also make note of whether the repair tunnel is
>    advertised by the routing protocol as an available link.
>

I agree on the comments otherwise.

Regards,
Alia

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

<div dir=3D"ltr">[+rtgwg mailing list]<div class=3D"gmail_extra"><br></div>=
<div class=3D"gmail_extra">Adrian,</div><div class=3D"gmail_extra"><br></di=
v><div class=3D"gmail_extra">Thanks very much for working through the examp=
le.=C2=A0 It was very interesting</div><div class=3D"gmail_extra">to see an=
 understanding by someone who isn&#39;t as close to the problem-space</div>=
<div class=3D"gmail_extra">and helped pick up on imprecisions and lack of c=
larity in the definitions.</div><div class=3D"gmail_extra"><br></div><div c=
lass=3D"gmail_extra">Not to speak for Stewart - whom I&#39;m sure will be r=
esponding quite soon, but...</div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Mon, Dec 29, 2014 at 11:09 AM, Adrian Farrel <span dir=
=3D"ltr">&lt;<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank">adria=
n@olddog.co.uk</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Adri=
an Farrel has entered the following ballot position for<br>
draft-ietf-rtgwg-remote-lfa-09: Discuss<br>
<br>
When responding, please keep the subject line intact and reply to all<br>
email addresses included in the To and CC lines. (Feel free to cut this<br>
introductory paragraph, however.)<br>
<br>
<br>
Please refer to <a href=3D"http://www.ietf.org/iesg/statement/discuss-crite=
ria.html" target=3D"_blank">http://www.ietf.org/iesg/statement/discuss-crit=
eria.html</a><br>
for more information about IESG DISCUSS and COMMENT positions.<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa/" ta=
rget=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa=
/</a><br>
<br>
<br>
<br>
----------------------------------------------------------------------<br>
DISCUSS:<br>
----------------------------------------------------------------------<br>
<br>
I&#39;m placing this Discuss because I found the description of the<br>
algorithm in 4.2.1 and the worked example in Section 2 to be at odds<br>
with the definitions of P-space, extended P-space, and Q-space.<br>
<br>
I have been able to make things work by messing with the algorithm and<br>
keeping the current definitions. You could probably do it by keeping<br>
the algorithm and messing with the definitions.<br></blockquote><div><br></=
div><div>Yes - we want to keep the algorithm.=C2=A0 In particular, the pseu=
do-code gets it</div><div>write and the definitions are a little sloppy. =
=C2=A0 Stewart clarified a bit around the</div><div>extended P-space not in=
cluding paths through the failed link in the text before</div><div>I put it=
 to the IESG.</div><div><br></div><div>=C2=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">
My workings were as follows, based on the example in Section 2:<br>
<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 S---E<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/=C2=A0 =C2=A0 =C2=A0\<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 A=C2=A0 =C2=A0 =C2=A0 =C2=A0D<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0\=C2=A0 =C2=A0 =C2=A0/<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 B---C<br>
&gt;<br>
&gt;=C2=A0 In Figure 1 S can reach A, B, and C without going via E;<br>
&gt;=C2=A0 these form S&#39;s extended P-space.<br>
<br>
First, this should say &quot;via S-E&quot; and &quot;extended P-space with =
respect to<br>
S-E&quot;.<br>
<br>
But...<br>
&gt;=C2=A0 Extended P-space<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The union=
 of the P-space of the neighbours of a<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0specific =
router with respect to the protected link<br>
<br>
(Noting that 4.2.1.2 changes this definition *significantly* by saying<br>
that the neighbour at the far end of the failing link - i.e., E in this<br>
case - must be excised from the list of neighbours whose P-spaces are<br>
combined).<br></blockquote><div><br></div><div>To be fair, the definition o=
f P-space (below) includes that the paths</div><div>can&#39;t transit the p=
rotected link (S-E in the example).</div><div><br></div><div>I think that t=
he definition needs to be updated to be &quot;the neighbors of a</div><div>=
specific router that are reachable without going via the protected link&quo=
t;.</div><div><br></div><div>When there&#39;s only a single link S-E, S has=
 no direct way of forcing traffic</div><div>to E so E&#39;s P-space can&#39=
;t be included.=C2=A0</div><div><br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
...and...<br>
&gt;=C2=A0 P-space=C2=A0 =C2=A0 =C2=A0 =C2=A0 P-space is the set of routers=
 reachable from a<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0specific =
router using the normal FIB, without any path<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(includin=
g equal cost path splits) transiting the<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0protected=
 link.<br>
<br>
Now, S&#39;s neighbours are A and E.<br>
The P-space of A with respect to S-E is {B, C}<br>
And the P-space of E with respect to S-E is {C, D}<br>
So the extended P-Space of S with respect to S-E is {B, C, D}<br>
<br>
Something is broken!<br></blockquote><div><br></div><div>Yes, can&#39;t inc=
lude the P-space of E when the failed link is S-E and there&#39;s</div><div=
>no way to reach E directly (one hop) from S.</div><div>=C2=A0</div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
{A, B, C} is not even the (not extended) P-space of S with respect to<br>
S-E which is {A, B} since C is not in that set because of SEDC.<br>
On the other hand {A, B, C} *is* the extended P-space of E wrt S-E.<br></bl=
ockquote><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Although, I would ob=
serve that the pseudocode in 4.2.1 does derive<br>
A, B, C as the extended P-space of S wrt S-E, but I think that is<br>
because it has an entirely different definition of an extended P-space.<br>=
</blockquote><div><br></div><div>?? Because it omits E?=C2=A0 Do you see an=
ything else different that needs</div><div>to be better clarified?=C2=A0</d=
iv><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Now...<br>
&gt;=C2=A0 Q-space=C2=A0 =C2=A0 =C2=A0 =C2=A0 Q-space is the set of routers=
 from which a specific<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0router ca=
n be reached without any path (including<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0equal cos=
t path splits) transiting the protected link.<br>
...so the Q-space of S wrt S-E is {A, B} since CDES.<br>
And, for the record, the Q-space or E wrt S-E is {C, D}<br>
<br>
Now, to compound the confusion, the example determines the PQ nodes for<br>
S wrt S-E by taking the intersection of the extended P-space for S wrt<br>
S-E=C2=A0 and the Q-space of E wrt S-E. This is done notwithstanding the<br=
>
definition...<br>
<br>
&gt;=C2=A0 PQ node=C2=A0 =C2=A0 =C2=A0 =C2=A0 A node which is a member of b=
oth the P-space and the<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Q-space.=
=C2=A0 Where extended P-space is in use it is a<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0node whic=
h is a member of both the extended P-space<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0and the Q=
-space.=C2=A0 In remote LFA this is used as the<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0repair tu=
nnel endpoint.<br></blockquote><div><br></div><div>Yup - so clearly it mean=
s &quot;of both the extended P-space of the PLR (S) and</div><div>the Q-spa=
ce of the far-end of the failed link (E)&quot;.=C2=A0 Some improved definit=
ions</div><div>are definitely needed.=C2=A0</div><div>=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">
This definition gives the PQ nodes of S wrt SE as either<br>
- the intersection of {A, B} and {A, B} if P-space is being discussed<br>
or<br>
- the intersection of {B, C, D} and {A, B} if extended P-space is being<br>
=C2=A0 used.<br>
<br>
So the correct tunnel end point for your example is B.<br>
But it clearly doesn&#39;t work since traffic to E that is tunneled to B ma=
y<br>
still be ECMP routed back along BAS.<br>
<br>
So I think in this whole example, you sit at S and you say &quot;I want to<=
br>
protect traffic to E&quot;. Then you work out the extended P-space of *E* w=
rt<br>
S-E (which is {A, B, C}) and the Q-space of *E* wrt S-E (which is<br>
{C, D}) giving you the correct PQ node for S to use to protect traffic<br>
to E in the event of a failure of S-E as C.<br></blockquote><div><br></div>=
<div>Extended-P space is the space that the PLR S can send traffic to - wha=
t nodes</div><div>can it reach without using the failed link.</div><div><br=
></div><div>Q-space is what nodes can reach the far-end E of the failed-lin=
k S-E without using</div><div>the failed link.</div><div><br></div><div>Obv=
iously the definitions need improvement.</div><div>=C2=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">
It is simple! All you have to do is update the text to describe the<br>
actual process and not the wrong one. Then the right result will pop<br>
out :-)<br>
<br>
The replacement is<br>
OLD<br>
=C2=A0 =C2=A0In Figure 1 S can reach A, B, and C without going via E;<br>
=C2=A0 =C2=A0these form S&#39;s extended P-space.<br>
NEW<br>
=C2=A0 =C2=A0In Figure 1 S can reach A and B without going via S-E, and<br>
=C2=A0 =C2=A0D can reach B and C without going via S-E. So E&#39;s extended=
 P-space<br>
=C2=A0 =C2=A0with respect to S-E is the nodes A, B, and C.<br>
END<br>
<br>
<br>
BUT, given all of this, are you sure that Section 4.2.1 is right? I&#39;m<b=
r>
not.<br></blockquote><div><br></div><div>Yes, not concerned about that.=C2=
=A0 You are just high-lighting some imprecisions</div><div>and lack of clar=
ity in the definitions.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
------<br>
<br>
Shouldn&#39;t the pseudocode in 4.3 be enclosed in code component macros to=
<br>
match with the copyright TLP etc.?</blockquote><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">
<br>
----------------------------------------------------------------------<br>
COMMENT:<br>
----------------------------------------------------------------------<br>
<br>
This is not my area of expertise so please excuse the brevity of the<br>
rest of this review.<br>
<br>
---<br>
<br>
Please s/draft/document/ throughout (except the boilerplate and<br>
filename) so that it can be published as an RFC (which is not a draft).<br>
<br>
---<br>
<br>
Although it causes some pain with abbreviations and a little more care<br>
in explanation, you need to put the Introduction as the first section in<br=
>
the document.<br>
<br>
---<br>
<br>
You are using RFC 5714 as a Normative Reference by making me go there<br>
for the definition of terms. Please move it to the correct section.<br>
<br>
---<br>
<br>
IMHO your definition of FIB is rather loose.=C2=A0 Fortunately (?) &quot;FI=
B&quot; is<br>
barely used in this document, so it might not be important, but if you<br>
wanted to fix it:<br>
- you are talking about IP packets in this document<br></blockquote><div><b=
r></div><div>Mostly MPLS actually...</div><div>=C2=A0</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
- the actions are, I think, limited to forwarding actions<br>
<br>
---<br>
<br>
This comment applies iff the resolution of the Discuss is not a complete<br=
>
change to the terminology!<br>
<br>
I think definitions need to be tighter or omitted from this part of the<br>
document. The definitions in 4.2.1 are more verbose and probably for<br>
good reason. If you feel you need to retain these definitions early in<br>
the document and can&#39;t lift the text from 4.2.1 then you need to addres=
s<br>
the concerns below.<br>
<br>
=C2=A0 =C2=A0P-space=C2=A0 =C2=A0 =C2=A0 =C2=A0 P-space is the set of route=
rs reachable from a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 specific rou=
ter using the normal FIB, without any path<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (including e=
qual cost path splits) transiting the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 protected li=
nk.<br>
<br>
&quot;the protected link&quot;? There is only one protected link?<br>
<br>
Since the example is worded as...<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 For example,=
 the P-space of S with respect to link<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 S-E, is the =
set of routers that S can reach without<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 using the pr=
otected link S-E.<br>
<br>
...I think you need...<br>
<br>
=C2=A0 =C2=A0P-space=C2=A0 =C2=A0 =C2=A0 =C2=A0 The P-space of a router wit=
h respect to a specific<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 protected li=
nk is the set of routers reachable from<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 the specific=
 router using the normal FIB, without any<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 path (includ=
ing equal cost path splits) transiting the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 protected li=
nk.<br>
<br>
Similarly, you need...<br>
<br>
=C2=A0 =C2=A0Extended P-space<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 The union of=
 the P-spaces of all of the neighbours of<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 a specific r=
outer with respect to a single specific<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 protected li=
nk (see Section 4.2.1.2).<br>
<br>
But note that 4.2.1.2 makes a significant change to this definition.<br>
<br>
=C2=A0 =C2=A0Q-space=C2=A0 =C2=A0 =C2=A0 =C2=A0 The Q-space for a specific =
router with respect to a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 specific pro=
tected link is the set of routers from<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 which the sp=
ecific router can be reached without any<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 path (includ=
ing equal cost path splits) transiting the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 protected li=
nk.<br>
<br>
=C2=A0 =C2=A0PQ node=C2=A0 =C2=A0 =C2=A0 =C2=A0 A PQ node is a node which i=
s a member of both the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 P-space and =
the Q-space for the same router and with<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 respect to t=
he same protected link.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Where extend=
ed P-space is being discussed, a PQ node<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 is a node wh=
ich is a member of both the extended<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 P-space and =
the Q-space for the same router and with<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 respect to t=
he same protected link.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 In remote LF=
A the repair tunnel endpoint is a PQ node.<br>
<br>
Throughout the text, however, the terms are used rather loosely. For<br>
example, when discussing Figure 1 you say &quot;S&#39;s extended P-space&qu=
ot;, but<br>
this is really &quot;S&#39;s extended P-space with respect to S-E&quot;. So=
meone<br>
familiar with the work might say that it is obvious from the context<br>
that we are discussing the link S-E, and it is, but the terminology<br>
needs to be tight.<br>
<br>
---<br>
<br>
There is some difficult terminology in Section 2<br>
<br>
=C2=A0 =C2=A0If all link costs are equal, the link S-E cannot be fully prot=
ected<br>
=C2=A0 =C2=A0by LFAs.=C2=A0 The destination C is an ECMP from S, and so can=
 be<br>
=C2=A0 =C2=A0protected when S-E fails, but D and E are not protectable usin=
g LFAs.<br>
<br>
Is it the link or the node that is protected (or the traffic)? Perhaps<br>
this could be rewritten to be less ambiguous.<br>
<br>
---<br>
<br>
Section 2<br>
<br>
=C2=A0 =C2=A0B<br>
=C2=A0 =C2=A0has equal-cost paths via B-A-S-E and B-C-D-E and so may go thr=
ough<br>
=C2=A0 =C2=A0S-E.<br>
<br>
I don&#39;t think B is going anywhere. Maybe...<br>
<br>
=C2=A0 =C2=A0B<br>
=C2=A0 =C2=A0has equal-cost paths to E via B-A-S-E and B-C-D-E and so may r=
each E<br>
=C2=A0 =C2=A0through S-E.<br>
<br>
---<br>
<br>
Section 2<br>
<br>
=C2=A0 =C2=A0In MPLS networks the targeted LDP<br>
=C2=A0 =C2=A0protocol needed to learn the label binding at the repair tunne=
l<br>
=C2=A0 =C2=A0endpoint is a well understood and widely deployed technology.<=
br>
<br>
But it would still benefit from a citation or a forward reference to<br>
section 7.<br>
<br>
---<br>
<br>
I enjoyed 3.2<br>
<br>
=C2=A0 =C2=A0relatively rare as is the incidence of failure in a well manag=
ed<br>
=C2=A0 =C2=A0network.<br>
<br>
So, managing my network well is protection against back-hoes. Nice.<br></bl=
ockquote><div><br></div><div>LOL - the argument is about the set-up time to=
 be protected again and what</div><div>is the interval between failures.=C2=
=A0 The editors and WG have decided that this</div><div>trade-off is accept=
able - but I&#39;d also prefer to see it more clearly articulated.</div><di=
v>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
---<br>
<br>
In 3.2<br>
<br>
=C2=A0 =C2=A0Multiple<br>
=C2=A0 =C2=A0repairs MAY share a tunnel end point.<br>
<br>
1. s/repairs/repair tunnels/<br>
2. s/MAY/may/ since this is not an implementation or operational choice,<br=
>
=C2=A0 =C2=A0but a fact of life.<br>
<br>
---<br>
<br>
In 4.2 you have truncated...<br>
<br>
=C2=A0 =C2=A0The repair tunnel endpoint needs to be a node in the network<b=
r>
=C2=A0 =C2=A0reachable from S without traversing S-E.<br>
<br>
...and...<br>
<br>
=C2=A0 =C2=A0o=C2=A0 The repair tunneled point MUST be reachable from the t=
unnel source<br>
=C2=A0 =C2=A0 =C2=A0 without traversing the failed link; and<br>
<br>
You mean &quot;reachable using the normal FIB&quot; I think.<br></blockquot=
e><div><br></div><div>Not quite because if the repair tunnel endpoint is in=
 the extended P-space and</div><div>not the P-space, then S has to force th=
e first hop rather than send it via the normal FIB.=C2=A0</div><div><br></d=
iv><div>=C2=A0---</div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Section 4.3<br>
<br>
=C2=A0 =C2=A0The preceding text has mostly described the computation of the=
 remote<br>
=C2=A0 =C2=A0LFA repair target (PQ) in terms of the intersection of two<br>
=C2=A0 =C2=A0reachability graphs computed using SPFs.<br>
<br>
&quot;mostly&quot;?<br>
<br>
&quot;reachability graphs&quot;? Were they? Or were they reachability sets?=
<br>
<br>
---<br>
<br>
Your pseducode in 4.3 invokes an unresolved (and undescribed) function<br>
Compute_Forward_SPF().<br>
<br>
Actually, I think this is a bogus line that can be deleted.<br>
<br>
---<br>
<br>
4.3 has<br>
<br>
=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 if ( D_opt(n, y) &lt;<br>
=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 =C2=A0 =C2=A0 =C2=A0 =C2=A0 D_opt(n,self) + D_opt)(self, =
y)<br>
<br>
Surely this is<br>
<br>
=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 if ( D_opt(n, y) &lt;<br>
=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 =C2=A0 =C2=A0 =C2=A0 =C2=A0 D_opt(n,self) + D_opt(self, y=
) )<br>
<br>
---<br>
<br>
I think the introduction of &quot;pseudonode&quot; in 4.3 may be a little w=
ithout<br>
context.<br>
<br>
---<br>
<br>
Section 7<br>
=C2=A0 =C2=A0If for any reason the TLDP session cannot<br>
=C2=A0 =C2=A0not be established<br>
<br>
s/cannot not/cannot/<br>
<br>
---<br>
<br>
I think [RFC5424] and [RFC3411] are pretty poor references to give in<br>
section 7. You appear to be saying that an implementation that cannot<br>
establish a TLDP session should write a MIB module, standardise it, and<br>
then report an error.<br>
<br>
Can&#39;t you find an existing LDP MIB module that reports Session-up<br>
failures?<br>
<br>
Or maybe just delete &quot;using any well known mechanism such as Syslog<br=
>
[RFC5424] or SNMP [RFC3411].&quot;<br>
<br>
---<br>
<br>
Why is the discussion of microloops on network re-converges considered<br>
to be a management consideration (by inclusion in Section 9). Surely it<br>
is a deployment or operational consideration.<br></blockquote><div><br></di=
v><div>I wanted that text somewhere in the doc.=C2=A0 Adding an operational=
 considerations</div><div>section to put it in would be fine.=C2=A0</div><d=
iv><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
---<br>
<br>
I think you can strengthen the security considerations. You have:<br>
<br>
=C2=A0 =C2=A0To prevent their use as an attack vector IP repair tunnel endp=
oints<br>
=C2=A0 =C2=A0(where used) SHOULD be assigned from a set of addresses that a=
re not<br>
=C2=A0 =C2=A0reachable from outside the routing domain.<br>
<br>
1. &quot;To prevent their use&quot; is surely consistent with a &quot;MUST&=
quot;.<br>
=C2=A0 =C2=A0The fact that you want to say &quot;SHOULD&quot; means that yo=
u need to turn<br>
=C2=A0 =C2=A0the text around...<br>
<br>
=C2=A0 =C2=A0IP repair tunnel endpoints (where used) SHOULD be assigned fro=
m a set<br>
=C2=A0 =C2=A0of addresses that are not reachable from outside the routing d=
omain.<br>
=C2=A0 =C2=A0This would prevent their use as an attack vector.<br>
<br>
2. You can add a note about what traffic can be placed into a repair<br>
=C2=A0 =C2=A0tunnel. You already have this earlier in the document, and it =
is<br>
=C2=A0 =C2=A0worth restating.<br>
<br>
3. I think you should also make note of whether the repair tunnel is<br>
=C2=A0 =C2=A0advertised by the routing protocol as an available link.<br>
</blockquote></div></div><br><div>I agree on the comments otherwise.</div><=
div><br></div><div>Regards,</div><div>Alia</div><div><br></div></div>

--001a1139ef04c44f02050beb9b76--


From nobody Mon Jan  5 10:55:49 2015
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3CE01A8881; Mon,  5 Jan 2015 10:55:45 -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 XIQuvU0hNvuX; Mon,  5 Jan 2015 10:55:38 -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 9AAFA1A888C; Mon,  5 Jan 2015 10:55:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2712; q=dns/txt; s=iport; t=1420484135; x=1421693735; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=4Xf4dvxD3g1xn/1zx+OmM8g6DgRe9l80y77a0nyi7uE=; b=e6DqmJIw1ZdGNVTANBti6/L9fZuFuQgtPKaBMca5l+A66yXy1dm7dHmQ F3JXlk4kv29js8QQzhOfnC7SoyLKdlDVFHt5cFYGRLz9ypfOqd/h6oPj/ T+2Uod2ZdQ7TOMnAe2XittlVULhCdiQTnXQEqciQ67nyV3RrwPf9zy2c/ 0=;
X-IronPort-AV: E=Sophos;i="5.07,701,1413244800";  d="scan'208,217";a="300204777"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 05 Jan 2015 18:55:33 +0000
Received: from [64.103.108.130] (dhcp-bdlk10-data-vlan301-64-103-108-130.cisco.com [64.103.108.130]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t05ItXxO023452; Mon, 5 Jan 2015 18:55:33 GMT
Message-ID: <54AADE25.2040406@cisco.com>
Date: Mon, 05 Jan 2015 18:55:33 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Alia Atlas <akatlas@gmail.com>, Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: Adrian Farrel's Discuss on draft-ietf-rtgwg-remote-lfa-09: (with DISCUSS and COMMENT)
References: <20141229160904.27130.40113.idtracker@ietfa.amsl.com> <CAG4d1rfFLuknjUvSKfu8frRR7XLfwvMmwa9qGhV6Li6ETpZLwA@mail.gmail.com>
In-Reply-To: <CAG4d1rfFLuknjUvSKfu8frRR7XLfwvMmwa9qGhV6Li6ETpZLwA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------000000020607030102000702"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/e_O7MEapVbV1G4BtkCMdWq-cbLA
Cc: "draft-ietf-rtgwg-remote-lfa@tools.ietf.org" <draft-ietf-rtgwg-remote-lfa@tools.ietf.org>, "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>, The IESG <iesg@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: Mon, 05 Jan 2015 18:55:46 -0000

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

Mike and I have a session with Adrian tomorrow to work through his 
discuss points
it is 2pm UK. You are welcome. I expect that it will mostly address 
definitions.

Just to pick on one point:
>
>
>     Why is the discussion of microloops on network re-converges considered
>     to be a management consideration (by inclusion in Section 9).
>     Surely it
>     is a deployment or operational consideration.
>
>
> I wanted that text somewhere in the doc.  Adding an operational 
> considerations
> section to put it in would be fine.
>
.. Or mirroring the IETF and calling it (Ops and Management) or 
(Management and Ops)

I will see that it's tidy one way or the other.

Stewart





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

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Mike and I have a session with Adrian tomorrow to work through his
    discuss points<br>
    it is 2pm UK. You are welcome. I expect that it will mostly address
    definitions.<br>
    <br>
    Just to pick on one point:<br>
    <blockquote
cite="mid:CAG4d1rfFLuknjUvSKfu8frRR7XLfwvMmwa9qGhV6Li6ETpZLwA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <br>
              Why is the discussion of microloops on network
              re-converges considered<br>
              to be a management consideration (by inclusion in Section
              9). Surely it<br>
              is a deployment or operational consideration.<br>
            </blockquote>
            <div><br>
            </div>
            <div>I wanted that text somewhere in the doc.  Adding an
              operational considerations</div>
            <div>section to put it in would be fine. </div>
            <div><br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    .. Or mirroring the IETF and calling it (Ops and Management) or
    (Management and Ops)<br>
    <br>
    I will see that it's tidy one way or the other.<br>
    <br>
    Stewart<br>
    <br>
    <br>
    <br>
    <br>
  </body>
</html>

--------------000000020607030102000702--


From nobody Tue Jan  6 02:07:40 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C09C1A1F1D; Tue,  6 Jan 2015 02:07:39 -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 62tIxUJV_iCq; Tue,  6 Jan 2015 02:07:37 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 882B91A1BC3; Tue,  6 Jan 2015 02:07:37 -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-lfa-manageability-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150106100737.30911.2907.idtracker@ietfa.amsl.com>
Date: Tue, 06 Jan 2015 02:07:37 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/jORDPhc499tAM-dHMf_wR1xUNp8
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, 06 Jan 2015 10:07:39 -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           : Operational management of Loop Free Alternates
        Authors         : Stephane Litkowski
                          Bruno Decraene
                          Clarence Filsfils
                          Kamran Raza
                          Martin Horneffer
                          Pushpasis Sarkar
	Filename        : draft-ietf-rtgwg-lfa-manageability-05.txt
	Pages           : 22
	Date            : 2015-01-06

Abstract:
   Loop Free Alternates (LFA), as defined in RFC 5286 is an IP Fast
   ReRoute (IP FRR) mechanism enabling traffic protection for IP traffic
   (and MPLS LDP traffic by extension).  Following first deployment
   experiences, this document provides operational feedback on LFA,
   highlights some limitations, and proposes a set of refinements to
   address those limitations.  It also proposes required management
   specifications.

   This proposal is also applicable to remote LFA solution.



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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-lfa-manageability-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 Tue Jan  6 02:11:11 2015
Return-Path: <stephane.litkowski@orange.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 281941A911F for <rtgwg@ietfa.amsl.com>; Tue,  6 Jan 2015 02:11:10 -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 0HI6DNzHqbJW for <rtgwg@ietfa.amsl.com>; Tue,  6 Jan 2015 02:11:08 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B1701A1F70 for <rtgwg@ietf.org>; Tue,  6 Jan 2015 02:11:08 -0800 (PST)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda10.si.francetelecom.fr (ESMTP service) with ESMTP id BE14C37426E; Tue,  6 Jan 2015 11:11:05 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.16]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id 9E24DC8098; Tue,  6 Jan 2015 11:11:05 +0100 (CET)
Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.68]) by OPEXCLILH05.corporate.adroot.infra.ftgroup ([10.114.31.16]) with mapi id 14.03.0210.002; Tue, 6 Jan 2015 11:11:05 +0100
From: <stephane.litkowski@orange.com>
To: Jeff Tantsura <jeff.tantsura@ericsson.com>, "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+E64gCsxlfoJyjLCMAgBALCfA=
Date: Tue, 6 Jan 2015 10:11:04 +0000
Message-ID: <12804_1420539065_54ABB4B9_12804_18132_1_9E32478DFA9976438E7A22F69B08FF920C74AE1B@OPEXCLILM34.corporate.adroot.infra.ftgroup>
References: <D07E84FE.77EE4%jeff.tantsura@ericsson.com> <D0C3A69E.80713%jeff.tantsura@ericsson.com>
In-Reply-To: <D0C3A69E.80713%jeff.tantsura@ericsson.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.12.22.201820
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/ME7hd91Az4IGsNbUIubgtHOj5FE
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, 06 Jan 2015 10:11:10 -0000

Hi Folks,

First, I would like to wish you all the best for this new year !

I just posted a new version of the draft addressing the comment from Uma, w=
e are inline with the proposed update.

http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-lfa-manageability-05.t=
xt


Best Regards,

Stephane


-----Original Message-----
From: Jeff Tantsura [mailto:jeff.tantsura@ericsson.com]=20
Sent: Saturday, December 27, 2014 09:08
To: rtgwg@ietf.org; draft-ietf-rtgwg-lfa-manageability@tools.ietf.org
Cc: Alvaro Retana
Subject: Re: Working Group last call on draft-ietf-rtgwg-lfa-manageability

All,

Working Group last call has been closed, we have only recevied supporting r=
esponses.=20
There has been comment posted (Uma C).
Could the authors please address, agree with the reviewers, confirm that th=
ey 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.


___________________________________________________________________________=
______________________________________________

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 Tue Jan  6 02:22:04 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED31D1A912C; Tue,  6 Jan 2015 02:22:01 -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 NK8xS897_mlw; Tue,  6 Jan 2015 02:22:00 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8229D1A9164; Tue,  6 Jan 2015 02:21:50 -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-lfa-manageability-06.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150106102150.32722.80846.idtracker@ietfa.amsl.com>
Date: Tue, 06 Jan 2015 02:21:50 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/W_8cefuWCkvPkHeJkwR108NdQWQ
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, 06 Jan 2015 10:22:02 -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           : Operational management of Loop Free Alternates
        Authors         : Stephane Litkowski
                          Bruno Decraene
                          Clarence Filsfils
                          Kamran Raza
                          Martin Horneffer
                          Pushpasis Sarkar
	Filename        : draft-ietf-rtgwg-lfa-manageability-06.txt
	Pages           : 22
	Date            : 2015-01-06

Abstract:
   Loop Free Alternates (LFA), as defined in RFC 5286 is an IP Fast
   ReRoute (IP FRR) mechanism enabling traffic protection for IP traffic
   (and MPLS LDP traffic by extension).  Following first deployment
   experiences, this document provides operational feedback on LFA,
   highlights some limitations, and proposes a set of refinements to
   address those limitations.  It also proposes required management
   specifications.

   This proposal is also applicable to remote LFA solution.



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

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

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


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

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


From nobody Tue Jan  6 08:16:49 2015
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E751A014C; Tue,  6 Jan 2015 08:16:30 -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 peBAcCgJoPDa; Tue,  6 Jan 2015 08:16:21 -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 922481A00E2; Tue,  6 Jan 2015 08:16:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=50472; q=dns/txt; s=iport; t=1420560979; x=1421770579; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=TPjJUVRmBiGevvXMKrsmRZpHyXzTV71u3rvqxYns/0g=; b=kzUNFY8jbfTk1wncj+AarucGyg2mC0RuoK++bGF34GFJVuqB35c0jIwc T2em9+p674UGST13BUJNz7HEYUa3wLmU3Uvk+EVrhSY1FgmsUNFabNP/9 sJzOHpqj4Ip+8duF78jyd/5oqnqKetvQV+YsUimuEEVtWXSDzH8MMPocb 0=;
X-IronPort-AV: E=Sophos;i="5.07,708,1413244800";  d="scan'208,217";a="301989187"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 06 Jan 2015 16:16:17 +0000
Received: from [64.103.108.130] (dhcp-bdlk10-data-vlan301-64-103-108-130.cisco.com [64.103.108.130]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t06GGGoM014511; Tue, 6 Jan 2015 16:16:16 GMT
Message-ID: <54AC0A50.8040009@cisco.com>
Date: Tue, 06 Jan 2015 16:16:16 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Alia Atlas <akatlas@gmail.com>, Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: Adrian Farrel's Discuss on draft-ietf-rtgwg-remote-lfa-09: (with DISCUSS and COMMENT)
References: <20141229160904.27130.40113.idtracker@ietfa.amsl.com> <CAG4d1rfFLuknjUvSKfu8frRR7XLfwvMmwa9qGhV6Li6ETpZLwA@mail.gmail.com>
In-Reply-To: <CAG4d1rfFLuknjUvSKfu8frRR7XLfwvMmwa9qGhV6Li6ETpZLwA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------050304090609000306040806"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/gHmOQ9_hUIklA1zpF5z6CMNlmiQ
Cc: "draft-ietf-rtgwg-remote-lfa@tools.ietf.org" <draft-ietf-rtgwg-remote-lfa@tools.ietf.org>, "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>, The IESG <iesg@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: Tue, 06 Jan 2015 16:16:30 -0000

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

Adrian, Mike and I just worked through the definitions and tightened 
them up.
We then looked at some of the usage in section 2 and made that more precise.

I fixed the use of the term draft and adopted Barry's title, but without 
including
the abbreviations (I can put them in if people want).

Hopefully this will allow Adrian to clear his DISCUSS.

The Editorial points I will pick in a post Telechat pass to also pick up any
other comments during review.

I will upload version 10 in a few minutes.

- Stewart


On 05/01/2015 18:10, Alia Atlas wrote:
> [+rtgwg mailing list]
>
> Adrian,
>
> Thanks very much for working through the example.  It was very interesting
> to see an understanding by someone who isn't as close to the problem-space
> and helped pick up on imprecisions and lack of clarity in the definitions.
>
> Not to speak for Stewart - whom I'm sure will be responding quite 
> soon, but...
>
> On Mon, Dec 29, 2014 at 11:09 AM, Adrian Farrel <adrian@olddog.co.uk 
> <mailto:adrian@olddog.co.uk>> wrote:
>
>     Adrian Farrel has entered the following ballot position for
>     draft-ietf-rtgwg-remote-lfa-09: Discuss
>
>     When responding, please keep the subject line intact and reply to all
>     email addresses included in the To and CC lines. (Feel free to cut
>     this
>     introductory paragraph, however.)
>
>
>     Please refer to
>     http://www.ietf.org/iesg/statement/discuss-criteria.html
>     for more information about IESG DISCUSS and COMMENT positions.
>
>
>     The document, along with other ballot positions, can be found here:
>     http://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa/
>
>
>
>     ----------------------------------------------------------------------
>     DISCUSS:
>     ----------------------------------------------------------------------
>
>     I'm placing this Discuss because I found the description of the
>     algorithm in 4.2.1 and the worked example in Section 2 to be at odds
>     with the definitions of P-space, extended P-space, and Q-space.
>
>     I have been able to make things work by messing with the algorithm and
>     keeping the current definitions. You could probably do it by keeping
>     the algorithm and messing with the definitions.
>
>
> Yes - we want to keep the algorithm.  In particular, the pseudo-code 
> gets it
> write and the definitions are a little sloppy. Stewart clarified a bit 
> around the
> extended P-space not including paths through the failed link in the 
> text before
> I put it to the IESG.
>
>     My workings were as follows, based on the example in Section 2:
>
>     >            S---E
>     >           /     \
>     >          A       D
>     >           \     /
>     >            B---C
>     >
>     >  In Figure 1 S can reach A, B, and C without going via E;
>     >  these form S's extended P-space.
>
>     First, this should say "via S-E" and "extended P-space with respect to
>     S-E".
>
>     But...
>     >  Extended P-space
>     >                 The union of the P-space of the neighbours of a
>     >                 specific router with respect to the protected link
>
>     (Noting that 4.2.1.2 changes this definition *significantly* by saying
>     that the neighbour at the far end of the failing link - i.e., E in
>     this
>     case - must be excised from the list of neighbours whose P-spaces are
>     combined).
>
>
> To be fair, the definition of P-space (below) includes that the paths
> can't transit the protected link (S-E in the example).
>
> I think that the definition needs to be updated to be "the neighbors of a
> specific router that are reachable without going via the protected link".
>
> When there's only a single link S-E, S has no direct way of forcing 
> traffic
> to E so E's P-space can't be included.
>
>     ...and...
>     >  P-space        P-space is the set of routers reachable from a
>     >                 specific router using the normal FIB, without
>     any path
>     >                 (including equal cost path splits) transiting the
>     >                 protected link.
>
>     Now, S's neighbours are A and E.
>     The P-space of A with respect to S-E is {B, C}
>     And the P-space of E with respect to S-E is {C, D}
>     So the extended P-Space of S with respect to S-E is {B, C, D}
>
>     Something is broken!
>
>
> Yes, can't include the P-space of E when the failed link is S-E and 
> there's
> no way to reach E directly (one hop) from S.
>
>     {A, B, C} is not even the (not extended) P-space of S with respect to
>     S-E which is {A, B} since C is not in that set because of SEDC.
>     On the other hand {A, B, C} *is* the extended P-space of E wrt S-E.
>
>
>     Although, I would observe that the pseudocode in 4.2.1 does derive
>     A, B, C as the extended P-space of S wrt S-E, but I think that is
>     because it has an entirely different definition of an extended
>     P-space.
>
>
> ?? Because it omits E?  Do you see anything else different that needs
> to be better clarified?
>
>     Now...
>     >  Q-space        Q-space is the set of routers from which a specific
>     >                 router can be reached without any path (including
>     >                 equal cost path splits) transiting the protected
>     link.
>     ...so the Q-space of S wrt S-E is {A, B} since CDES.
>     And, for the record, the Q-space or E wrt S-E is {C, D}
>
>     Now, to compound the confusion, the example determines the PQ
>     nodes for
>     S wrt S-E by taking the intersection of the extended P-space for S wrt
>     S-E  and the Q-space of E wrt S-E. This is done notwithstanding the
>     definition...
>
>     >  PQ node        A node which is a member of both the P-space and the
>     >                 Q-space.  Where extended P-space is in use it is a
>     >                 node which is a member of both the extended P-space
>     >                 and the Q-space.  In remote LFA this is used as the
>     >                 repair tunnel endpoint.
>
>
> Yup - so clearly it means "of both the extended P-space of the PLR (S) and
> the Q-space of the far-end of the failed link (E)". Some improved 
> definitions
> are definitely needed.
>
>     This definition gives the PQ nodes of S wrt SE as either
>     - the intersection of {A, B} and {A, B} if P-space is being discussed
>     or
>     - the intersection of {B, C, D} and {A, B} if extended P-space is
>     being
>       used.
>
>     So the correct tunnel end point for your example is B.
>     But it clearly doesn't work since traffic to E that is tunneled to
>     B may
>     still be ECMP routed back along BAS.
>
>     So I think in this whole example, you sit at S and you say "I want to
>     protect traffic to E". Then you work out the extended P-space of
>     *E* wrt
>     S-E (which is {A, B, C}) and the Q-space of *E* wrt S-E (which is
>     {C, D}) giving you the correct PQ node for S to use to protect traffic
>     to E in the event of a failure of S-E as C.
>
>
> Extended-P space is the space that the PLR S can send traffic to - 
> what nodes
> can it reach without using the failed link.
>
> Q-space is what nodes can reach the far-end E of the failed-link S-E 
> without using
> the failed link.
>
> Obviously the definitions need improvement.
>
>     It is simple! All you have to do is update the text to describe the
>     actual process and not the wrong one. Then the right result will pop
>     out :-)
>
>     The replacement is
>     OLD
>        In Figure 1 S can reach A, B, and C without going via E;
>        these form S's extended P-space.
>     NEW
>        In Figure 1 S can reach A and B without going via S-E, and
>        D can reach B and C without going via S-E. So E's extended P-space
>        with respect to S-E is the nodes A, B, and C.
>     END
>
>
>     BUT, given all of this, are you sure that Section 4.2.1 is right? I'm
>     not.
>
>
> Yes, not concerned about that.  You are just high-lighting some 
> imprecisions
> and lack of clarity in the definitions.
>
>     ------
>
>     Shouldn't the pseudocode in 4.3 be enclosed in code component
>     macros to
>     match with the copyright TLP etc.?
>
>
>     ----------------------------------------------------------------------
>     COMMENT:
>     ----------------------------------------------------------------------
>
>     This is not my area of expertise so please excuse the brevity of the
>     rest of this review.
>
>     ---
>
>     Please s/draft/document/ throughout (except the boilerplate and
>     filename) so that it can be published as an RFC (which is not a
>     draft).
>
>     ---
>
>     Although it causes some pain with abbreviations and a little more care
>     in explanation, you need to put the Introduction as the first
>     section in
>     the document.
>
>     ---
>
>     You are using RFC 5714 as a Normative Reference by making me go there
>     for the definition of terms. Please move it to the correct section.
>
>     ---
>
>     IMHO your definition of FIB is rather loose.  Fortunately (?) "FIB" is
>     barely used in this document, so it might not be important, but if you
>     wanted to fix it:
>     - you are talking about IP packets in this document
>
>
> Mostly MPLS actually...
>
>     - the actions are, I think, limited to forwarding actions
>
>     ---
>
>     This comment applies iff the resolution of the Discuss is not a
>     complete
>     change to the terminology!
>
>     I think definitions need to be tighter or omitted from this part
>     of the
>     document. The definitions in 4.2.1 are more verbose and probably for
>     good reason. If you feel you need to retain these definitions early in
>     the document and can't lift the text from 4.2.1 then you need to
>     address
>     the concerns below.
>
>        P-space        P-space is the set of routers reachable from a
>                       specific router using the normal FIB, without
>     any path
>                       (including equal cost path splits) transiting the
>                       protected link.
>
>     "the protected link"? There is only one protected link?
>
>     Since the example is worded as...
>
>                       For example, the P-space of S with respect to link
>                       S-E, is the set of routers that S can reach without
>                       using the protected link S-E.
>
>     ...I think you need...
>
>        P-space        The P-space of a router with respect to a specific
>                       protected link is the set of routers reachable from
>                       the specific router using the normal FIB,
>     without any
>                       path (including equal cost path splits)
>     transiting the
>                       protected link.
>
>     Similarly, you need...
>
>        Extended P-space
>                       The union of the P-spaces of all of the
>     neighbours of
>                       a specific router with respect to a single specific
>                       protected link (see Section 4.2.1.2).
>
>     But note that 4.2.1.2 makes a significant change to this definition.
>
>        Q-space        The Q-space for a specific router with respect to a
>                       specific protected link is the set of routers from
>                       which the specific router can be reached without any
>                       path (including equal cost path splits)
>     transiting the
>                       protected link.
>
>        PQ node        A PQ node is a node which is a member of both the
>                       P-space and the Q-space for the same router and with
>                       respect to the same protected link.
>
>                       Where extended P-space is being discussed, a PQ node
>                       is a node which is a member of both the extended
>                       P-space and the Q-space for the same router and with
>                       respect to the same protected link.
>
>                       In remote LFA the repair tunnel endpoint is a PQ
>     node.
>
>     Throughout the text, however, the terms are used rather loosely. For
>     example, when discussing Figure 1 you say "S's extended P-space", but
>     this is really "S's extended P-space with respect to S-E". Someone
>     familiar with the work might say that it is obvious from the context
>     that we are discussing the link S-E, and it is, but the terminology
>     needs to be tight.
>
>     ---
>
>     There is some difficult terminology in Section 2
>
>        If all link costs are equal, the link S-E cannot be fully protected
>        by LFAs.  The destination C is an ECMP from S, and so can be
>        protected when S-E fails, but D and E are not protectable using
>     LFAs.
>
>     Is it the link or the node that is protected (or the traffic)? Perhaps
>     this could be rewritten to be less ambiguous.
>
>     ---
>
>     Section 2
>
>        B
>        has equal-cost paths via B-A-S-E and B-C-D-E and so may go through
>        S-E.
>
>     I don't think B is going anywhere. Maybe...
>
>        B
>        has equal-cost paths to E via B-A-S-E and B-C-D-E and so may
>     reach E
>        through S-E.
>
>     ---
>
>     Section 2
>
>        In MPLS networks the targeted LDP
>        protocol needed to learn the label binding at the repair tunnel
>        endpoint is a well understood and widely deployed technology.
>
>     But it would still benefit from a citation or a forward reference to
>     section 7.
>
>     ---
>
>     I enjoyed 3.2
>
>        relatively rare as is the incidence of failure in a well managed
>        network.
>
>     So, managing my network well is protection against back-hoes. Nice.
>
>
> LOL - the argument is about the set-up time to be protected again and what
> is the interval between failures.  The editors and WG have decided 
> that this
> trade-off is acceptable - but I'd also prefer to see it more clearly 
> articulated.
>
>     ---
>
>     In 3.2
>
>        Multiple
>        repairs MAY share a tunnel end point.
>
>     1. s/repairs/repair tunnels/
>     2. s/MAY/may/ since this is not an implementation or operational
>     choice,
>        but a fact of life.
>
>     ---
>
>     In 4.2 you have truncated...
>
>        The repair tunnel endpoint needs to be a node in the network
>        reachable from S without traversing S-E.
>
>     ...and...
>
>        o  The repair tunneled point MUST be reachable from the tunnel
>     source
>           without traversing the failed link; and
>
>     You mean "reachable using the normal FIB" I think.
>
>
> Not quite because if the repair tunnel endpoint is in the extended 
> P-space and
> not the P-space, then S has to force the first hop rather than send it 
> via the normal FIB.
>
>  ---
>
>
>     Section 4.3
>
>        The preceding text has mostly described the computation of the
>     remote
>        LFA repair target (PQ) in terms of the intersection of two
>        reachability graphs computed using SPFs.
>
>     "mostly"?
>
>     "reachability graphs"? Were they? Or were they reachability sets?
>
>     ---
>
>     Your pseducode in 4.3 invokes an unresolved (and undescribed) function
>     Compute_Forward_SPF().
>
>     Actually, I think this is a bogus line that can be deleted.
>
>     ---
>
>     4.3 has
>
>                               if ( D_opt(n, y) <
>                                       D_opt(n,self) + D_opt)(self, y)
>
>     Surely this is
>
>                               if ( D_opt(n, y) <
>                                       D_opt(n,self) + D_opt(self, y) )
>
>     ---
>
>     I think the introduction of "pseudonode" in 4.3 may be a little
>     without
>     context.
>
>     ---
>
>     Section 7
>        If for any reason the TLDP session cannot
>        not be established
>
>     s/cannot not/cannot/
>
>     ---
>
>     I think [RFC5424] and [RFC3411] are pretty poor references to give in
>     section 7. You appear to be saying that an implementation that cannot
>     establish a TLDP session should write a MIB module, standardise
>     it, and
>     then report an error.
>
>     Can't you find an existing LDP MIB module that reports Session-up
>     failures?
>
>     Or maybe just delete "using any well known mechanism such as Syslog
>     [RFC5424] or SNMP [RFC3411]."
>
>     ---
>
>     Why is the discussion of microloops on network re-converges considered
>     to be a management consideration (by inclusion in Section 9).
>     Surely it
>     is a deployment or operational consideration.
>
>
> I wanted that text somewhere in the doc.  Adding an operational 
> considerations
> section to put it in would be fine.
>
>     ---
>
>     I think you can strengthen the security considerations. You have:
>
>        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.
>
>     1. "To prevent their use" is surely consistent with a "MUST".
>        The fact that you want to say "SHOULD" means that you need to turn
>        the text around...
>
>        IP repair tunnel endpoints (where used) SHOULD be assigned from
>     a set
>        of addresses that are not reachable from outside the routing
>     domain.
>        This would prevent their use as an attack vector.
>
>     2. You can add a note about what traffic can be placed into a repair
>        tunnel. You already have this earlier in the document, and it is
>        worth restating.
>
>     3. I think you should also make note of whether the repair tunnel is
>        advertised by the routing protocol as an available link.
>
>
> I agree on the comments otherwise.
>
> Regards,
> Alia
>
>
>
> _______________________________________________
> 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


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

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Adrian, Mike and I just worked through
      the definitions and tightened them up.<br>
      We then looked at some of the usage in section 2 and made that
      more precise.<br>
      <br>
      I fixed the use of the term draft and adopted Barry's title, but
      without including<br>
      the abbreviations (I can put them in if people want).<br>
      <br>
      Hopefully this will allow Adrian to clear his DISCUSS.<br>
      <br>
      The Editorial points I will pick in a post Telechat pass to also
      pick up any<br>
      other comments during review.<br>
      <br>
      I will upload version 10 in a few minutes.<br>
      <br>
      - Stewart<br>
      <br>
      <br>
      On 05/01/2015 18:10, Alia Atlas wrote:<br>
    </div>
    <blockquote
cite="mid:CAG4d1rfFLuknjUvSKfu8frRR7XLfwvMmwa9qGhV6Li6ETpZLwA@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div dir="ltr">[+rtgwg mailing list]
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">Adrian,</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">Thanks very much for working through
          the example.  It was very interesting</div>
        <div class="gmail_extra">to see an understanding by someone who
          isn't as close to the problem-space</div>
        <div class="gmail_extra">and helped pick up on imprecisions and
          lack of clarity in the definitions.</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">Not to speak for Stewart - whom I'm
          sure will be responding quite soon, but...</div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Mon, Dec 29, 2014 at 11:09 AM,
            Adrian Farrel <span dir="ltr">&lt;<a moz-do-not-send="true"
                href="mailto:adrian@olddog.co.uk" target="_blank">adrian@olddog.co.uk</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">Adrian
              Farrel has entered the following ballot position for<br>
              draft-ietf-rtgwg-remote-lfa-09: Discuss<br>
              <br>
              When responding, please keep the subject line intact and
              reply to all<br>
              email addresses included in the To and CC lines. (Feel
              free to cut this<br>
              introductory paragraph, however.)<br>
              <br>
              <br>
              Please refer to <a moz-do-not-send="true"
                href="http://www.ietf.org/iesg/statement/discuss-criteria.html"
                target="_blank">http://www.ietf.org/iesg/statement/discuss-criteria.html</a><br>
              for more information about IESG DISCUSS and COMMENT
              positions.<br>
              <br>
              <br>
              The document, along with other ballot positions, can be
              found here:<br>
              <a moz-do-not-send="true"
                href="http://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa/"
                target="_blank">http://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa/</a><br>
              <br>
              <br>
              <br>
----------------------------------------------------------------------<br>
              DISCUSS:<br>
----------------------------------------------------------------------<br>
              <br>
              I'm placing this Discuss because I found the description
              of the<br>
              algorithm in 4.2.1 and the worked example in Section 2 to
              be at odds<br>
              with the definitions of P-space, extended P-space, and
              Q-space.<br>
              <br>
              I have been able to make things work by messing with the
              algorithm and<br>
              keeping the current definitions. You could probably do it
              by keeping<br>
              the algorithm and messing with the definitions.<br>
            </blockquote>
            <div><br>
            </div>
            <div>Yes - we want to keep the algorithm.  In particular,
              the pseudo-code gets it</div>
            <div>write and the definitions are a little sloppy.  
              Stewart clarified a bit around the</div>
            <div>extended P-space not including paths through the failed
              link in the text before</div>
            <div>I put it to the IESG.</div>
            <div><br>
            </div>
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              My workings were as follows, based on the example in
              Section 2:<br>
              <br>
              &gt;            S---E<br>
              &gt;           /     \<br>
              &gt;          A       D<br>
              &gt;           \     /<br>
              &gt;            B---C<br>
              &gt;<br>
              &gt;  In Figure 1 S can reach A, B, and C without going
              via E;<br>
              &gt;  these form S's extended P-space.<br>
              <br>
              First, this should say "via S-E" and "extended P-space
              with respect to<br>
              S-E".<br>
              <br>
              But...<br>
              &gt;  Extended P-space<br>
              &gt;                 The union of the P-space of the
              neighbours of a<br>
              &gt;                 specific router with respect to the
              protected link<br>
              <br>
              (Noting that 4.2.1.2 changes this definition
              *significantly* by saying<br>
              that the neighbour at the far end of the failing link -
              i.e., E in this<br>
              case - must be excised from the list of neighbours whose
              P-spaces are<br>
              combined).<br>
            </blockquote>
            <div><br>
            </div>
            <div>To be fair, the definition of P-space (below) includes
              that the paths</div>
            <div>can't transit the protected link (S-E in the example).</div>
            <div><br>
            </div>
            <div>I think that the definition needs to be updated to be
              "the neighbors of a</div>
            <div>specific router that are reachable without going via
              the protected link".</div>
            <div><br>
            </div>
            <div>When there's only a single link S-E, S has no direct
              way of forcing traffic</div>
            <div>to E so E's P-space can't be included. </div>
            <div><br>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              ...and...<br>
              &gt;  P-space        P-space is the set of routers
              reachable from a<br>
              &gt;                 specific router using the normal FIB,
              without any path<br>
              &gt;                 (including equal cost path splits)
              transiting the<br>
              &gt;                 protected link.<br>
              <br>
              Now, S's neighbours are A and E.<br>
              The P-space of A with respect to S-E is {B, C}<br>
              And the P-space of E with respect to S-E is {C, D}<br>
              So the extended P-Space of S with respect to S-E is {B, C,
              D}<br>
              <br>
              Something is broken!<br>
            </blockquote>
            <div><br>
            </div>
            <div>Yes, can't include the P-space of E when the failed
              link is S-E and there's</div>
            <div>no way to reach E directly (one hop) from S.</div>
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              {A, B, C} is not even the (not extended) P-space of S with
              respect to<br>
              S-E which is {A, B} since C is not in that set because of
              SEDC.<br>
              On the other hand {A, B, C} *is* the extended P-space of E
              wrt S-E.<br>
            </blockquote>
            <div><br>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">Although,
              I would observe that the pseudocode in 4.2.1 does derive<br>
              A, B, C as the extended P-space of S wrt S-E, but I think
              that is<br>
              because it has an entirely different definition of an
              extended P-space.<br>
            </blockquote>
            <div><br>
            </div>
            <div>?? Because it omits E?  Do you see anything else
              different that needs</div>
            <div>to be better clarified? </div>
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              Now...<br>
              &gt;  Q-space        Q-space is the set of routers from
              which a specific<br>
              &gt;                 router can be reached without any
              path (including<br>
              &gt;                 equal cost path splits) transiting
              the protected link.<br>
              ...so the Q-space of S wrt S-E is {A, B} since CDES.<br>
              And, for the record, the Q-space or E wrt S-E is {C, D}<br>
              <br>
              Now, to compound the confusion, the example determines the
              PQ nodes for<br>
              S wrt S-E by taking the intersection of the extended
              P-space for S wrt<br>
              S-E  and the Q-space of E wrt S-E. This is done
              notwithstanding the<br>
              definition...<br>
              <br>
              &gt;  PQ node        A node which is a member of both the
              P-space and the<br>
              &gt;                 Q-space.  Where extended P-space is
              in use it is a<br>
              &gt;                 node which is a member of both the
              extended P-space<br>
              &gt;                 and the Q-space.  In remote LFA this
              is used as the<br>
              &gt;                 repair tunnel endpoint.<br>
            </blockquote>
            <div><br>
            </div>
            <div>Yup - so clearly it means "of both the extended P-space
              of the PLR (S) and</div>
            <div>the Q-space of the far-end of the failed link (E)". 
              Some improved definitions</div>
            <div>are definitely needed. </div>
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              This definition gives the PQ nodes of S wrt SE as either<br>
              - the intersection of {A, B} and {A, B} if P-space is
              being discussed<br>
              or<br>
              - the intersection of {B, C, D} and {A, B} if extended
              P-space is being<br>
                used.<br>
              <br>
              So the correct tunnel end point for your example is B.<br>
              But it clearly doesn't work since traffic to E that is
              tunneled to B may<br>
              still be ECMP routed back along BAS.<br>
              <br>
              So I think in this whole example, you sit at S and you say
              "I want to<br>
              protect traffic to E". Then you work out the extended
              P-space of *E* wrt<br>
              S-E (which is {A, B, C}) and the Q-space of *E* wrt S-E
              (which is<br>
              {C, D}) giving you the correct PQ node for S to use to
              protect traffic<br>
              to E in the event of a failure of S-E as C.<br>
            </blockquote>
            <div><br>
            </div>
            <div>Extended-P space is the space that the PLR S can send
              traffic to - what nodes</div>
            <div>can it reach without using the failed link.</div>
            <div><br>
            </div>
            <div>Q-space is what nodes can reach the far-end E of the
              failed-link S-E without using</div>
            <div>the failed link.</div>
            <div><br>
            </div>
            <div>Obviously the definitions need improvement.</div>
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              It is simple! All you have to do is update the text to
              describe the<br>
              actual process and not the wrong one. Then the right
              result will pop<br>
              out :-)<br>
              <br>
              The replacement is<br>
              OLD<br>
                 In Figure 1 S can reach A, B, and C without going via
              E;<br>
                 these form S's extended P-space.<br>
              NEW<br>
                 In Figure 1 S can reach A and B without going via S-E,
              and<br>
                 D can reach B and C without going via S-E. So E's
              extended P-space<br>
                 with respect to S-E is the nodes A, B, and C.<br>
              END<br>
              <br>
              <br>
              BUT, given all of this, are you sure that Section 4.2.1 is
              right? I'm<br>
              not.<br>
            </blockquote>
            <div><br>
            </div>
            <div>Yes, not concerned about that.  You are just
              high-lighting some imprecisions</div>
            <div>and lack of clarity in the definitions. </div>
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              ------<br>
              <br>
              Shouldn't the pseudocode in 4.3 be enclosed in code
              component macros to<br>
              match with the copyright TLP etc.?</blockquote>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <br>
----------------------------------------------------------------------<br>
              COMMENT:<br>
----------------------------------------------------------------------<br>
              <br>
              This is not my area of expertise so please excuse the
              brevity of the<br>
              rest of this review.<br>
              <br>
              ---<br>
              <br>
              Please s/draft/document/ throughout (except the
              boilerplate and<br>
              filename) so that it can be published as an RFC (which is
              not a draft).<br>
              <br>
              ---<br>
              <br>
              Although it causes some pain with abbreviations and a
              little more care<br>
              in explanation, you need to put the Introduction as the
              first section in<br>
              the document.<br>
              <br>
              ---<br>
              <br>
              You are using RFC 5714 as a Normative Reference by making
              me go there<br>
              for the definition of terms. Please move it to the correct
              section.<br>
              <br>
              ---<br>
              <br>
              IMHO your definition of FIB is rather loose.  Fortunately
              (?) "FIB" is<br>
              barely used in this document, so it might not be
              important, but if you<br>
              wanted to fix it:<br>
              - you are talking about IP packets in this document<br>
            </blockquote>
            <div><br>
            </div>
            <div>Mostly MPLS actually...</div>
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              - the actions are, I think, limited to forwarding actions<br>
              <br>
              ---<br>
              <br>
              This comment applies iff the resolution of the Discuss is
              not a complete<br>
              change to the terminology!<br>
              <br>
              I think definitions need to be tighter or omitted from
              this part of the<br>
              document. The definitions in 4.2.1 are more verbose and
              probably for<br>
              good reason. If you feel you need to retain these
              definitions early in<br>
              the document and can't lift the text from 4.2.1 then you
              need to address<br>
              the concerns below.<br>
              <br>
                 P-space        P-space is the set of routers reachable
              from a<br>
                                specific router using the normal FIB,
              without any path<br>
                                (including equal cost path splits)
              transiting the<br>
                                protected link.<br>
              <br>
              "the protected link"? There is only one protected link?<br>
              <br>
              Since the example is worded as...<br>
              <br>
                                For example, the P-space of S with
              respect to link<br>
                                S-E, is the set of routers that S can
              reach without<br>
                                using the protected link S-E.<br>
              <br>
              ...I think you need...<br>
              <br>
                 P-space        The P-space of a router with respect to
              a specific<br>
                                protected link is the set of routers
              reachable from<br>
                                the specific router using the normal
              FIB, without any<br>
                                path (including equal cost path splits)
              transiting the<br>
                                protected link.<br>
              <br>
              Similarly, you need...<br>
              <br>
                 Extended P-space<br>
                                The union of the P-spaces of all of the
              neighbours of<br>
                                a specific router with respect to a
              single specific<br>
                                protected link (see Section 4.2.1.2).<br>
              <br>
              But note that 4.2.1.2 makes a significant change to this
              definition.<br>
              <br>
                 Q-space        The Q-space for a specific router with
              respect to a<br>
                                specific protected link is the set of
              routers from<br>
                                which the specific router can be reached
              without any<br>
                                path (including equal cost path splits)
              transiting the<br>
                                protected link.<br>
              <br>
                 PQ node        A PQ node is a node which is a member of
              both the<br>
                                P-space and the Q-space for the same
              router and with<br>
                                respect to the same protected link.<br>
              <br>
                                Where extended P-space is being
              discussed, a PQ node<br>
                                is a node which is a member of both the
              extended<br>
                                P-space and the Q-space for the same
              router and with<br>
                                respect to the same protected link.<br>
              <br>
                                In remote LFA the repair tunnel endpoint
              is a PQ node.<br>
              <br>
              Throughout the text, however, the terms are used rather
              loosely. For<br>
              example, when discussing Figure 1 you say "S's extended
              P-space", but<br>
              this is really "S's extended P-space with respect to S-E".
              Someone<br>
              familiar with the work might say that it is obvious from
              the context<br>
              that we are discussing the link S-E, and it is, but the
              terminology<br>
              needs to be tight.<br>
              <br>
              ---<br>
              <br>
              There is some difficult terminology in Section 2<br>
              <br>
                 If all link costs are equal, the link S-E cannot be
              fully protected<br>
                 by LFAs.  The destination C is an ECMP from S, and so
              can be<br>
                 protected when S-E fails, but D and E are not
              protectable using LFAs.<br>
              <br>
              Is it the link or the node that is protected (or the
              traffic)? Perhaps<br>
              this could be rewritten to be less ambiguous.<br>
              <br>
              ---<br>
              <br>
              Section 2<br>
              <br>
                 B<br>
                 has equal-cost paths via B-A-S-E and B-C-D-E and so may
              go through<br>
                 S-E.<br>
              <br>
              I don't think B is going anywhere. Maybe...<br>
              <br>
                 B<br>
                 has equal-cost paths to E via B-A-S-E and B-C-D-E and
              so may reach E<br>
                 through S-E.<br>
              <br>
              ---<br>
              <br>
              Section 2<br>
              <br>
                 In MPLS networks the targeted LDP<br>
                 protocol needed to learn the label binding at the
              repair tunnel<br>
                 endpoint is a well understood and widely deployed
              technology.<br>
              <br>
              But it would still benefit from a citation or a forward
              reference to<br>
              section 7.<br>
              <br>
              ---<br>
              <br>
              I enjoyed 3.2<br>
              <br>
                 relatively rare as is the incidence of failure in a
              well managed<br>
                 network.<br>
              <br>
              So, managing my network well is protection against
              back-hoes. Nice.<br>
            </blockquote>
            <div><br>
            </div>
            <div>LOL - the argument is about the set-up time to be
              protected again and what</div>
            <div>is the interval between failures.  The editors and WG
              have decided that this</div>
            <div>trade-off is acceptable - but I'd also prefer to see it
              more clearly articulated.</div>
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              ---<br>
              <br>
              In 3.2<br>
              <br>
                 Multiple<br>
                 repairs MAY share a tunnel end point.<br>
              <br>
              1. s/repairs/repair tunnels/<br>
              2. s/MAY/may/ since this is not an implementation or
              operational choice,<br>
                 but a fact of life.<br>
              <br>
              ---<br>
              <br>
              In 4.2 you have truncated...<br>
              <br>
                 The repair tunnel endpoint needs to be a node in the
              network<br>
                 reachable from S without traversing S-E.<br>
              <br>
              ...and...<br>
              <br>
                 o  The repair tunneled point MUST be reachable from the
              tunnel source<br>
                    without traversing the failed link; and<br>
              <br>
              You mean "reachable using the normal FIB" I think.<br>
            </blockquote>
            <div><br>
            </div>
            <div>Not quite because if the repair tunnel endpoint is in
              the extended P-space and</div>
            <div>not the P-space, then S has to force the first hop
              rather than send it via the normal FIB. </div>
            <div><br>
            </div>
            <div> ---</div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <br>
              Section 4.3<br>
              <br>
                 The preceding text has mostly described the computation
              of the remote<br>
                 LFA repair target (PQ) in terms of the intersection of
              two<br>
                 reachability graphs computed using SPFs.<br>
              <br>
              "mostly"?<br>
              <br>
              "reachability graphs"? Were they? Or were they
              reachability sets?<br>
              <br>
              ---<br>
              <br>
              Your pseducode in 4.3 invokes an unresolved (and
              undescribed) function<br>
              Compute_Forward_SPF().<br>
              <br>
              Actually, I think this is a bogus line that can be
              deleted.<br>
              <br>
              ---<br>
              <br>
              4.3 has<br>
              <br>
                                        if ( D_opt(n, y) &lt;<br>
                                                D_opt(n,self) +
              D_opt)(self, y)<br>
              <br>
              Surely this is<br>
              <br>
                                        if ( D_opt(n, y) &lt;<br>
                                                D_opt(n,self) +
              D_opt(self, y) )<br>
              <br>
              ---<br>
              <br>
              I think the introduction of "pseudonode" in 4.3 may be a
              little without<br>
              context.<br>
              <br>
              ---<br>
              <br>
              Section 7<br>
                 If for any reason the TLDP session cannot<br>
                 not be established<br>
              <br>
              s/cannot not/cannot/<br>
              <br>
              ---<br>
              <br>
              I think [RFC5424] and [RFC3411] are pretty poor references
              to give in<br>
              section 7. You appear to be saying that an implementation
              that cannot<br>
              establish a TLDP session should write a MIB module,
              standardise it, and<br>
              then report an error.<br>
              <br>
              Can't you find an existing LDP MIB module that reports
              Session-up<br>
              failures?<br>
              <br>
              Or maybe just delete "using any well known mechanism such
              as Syslog<br>
              [RFC5424] or SNMP [RFC3411]."<br>
              <br>
              ---<br>
              <br>
              Why is the discussion of microloops on network
              re-converges considered<br>
              to be a management consideration (by inclusion in Section
              9). Surely it<br>
              is a deployment or operational consideration.<br>
            </blockquote>
            <div><br>
            </div>
            <div>I wanted that text somewhere in the doc.  Adding an
              operational considerations</div>
            <div>section to put it in would be fine. </div>
            <div><br>
            </div>
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              ---<br>
              <br>
              I think you can strengthen the security considerations.
              You have:<br>
              <br>
                 To prevent their use as an attack vector IP repair
              tunnel endpoints<br>
                 (where used) SHOULD be assigned from a set of addresses
              that are not<br>
                 reachable from outside the routing domain.<br>
              <br>
              1. "To prevent their use" is surely consistent with a
              "MUST".<br>
                 The fact that you want to say "SHOULD" means that you
              need to turn<br>
                 the text around...<br>
              <br>
                 IP repair tunnel endpoints (where used) SHOULD be
              assigned from a set<br>
                 of addresses that are not reachable from outside the
              routing domain.<br>
                 This would prevent their use as an attack vector.<br>
              <br>
              2. You can add a note about what traffic can be placed
              into a repair<br>
                 tunnel. You already have this earlier in the document,
              and it is<br>
                 worth restating.<br>
              <br>
              3. I think you should also make note of whether the repair
              tunnel is<br>
                 advertised by the routing protocol as an available
              link.<br>
            </blockquote>
          </div>
        </div>
        <br>
        <div>I agree on the comments otherwise.</div>
        <div><br>
        </div>
        <div>Regards,</div>
        <div>Alia</div>
        <div><br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
rtgwg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/rtgwg">https://www.ietf.org/mailman/listinfo/rtgwg</a>
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

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

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

--------------050304090609000306040806--


From nobody Tue Jan  6 08:28:58 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C56D51A020B; Tue,  6 Jan 2015 08:28:50 -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 2H4pwzWrKO2N; Tue,  6 Jan 2015 08:28:44 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EDE151A017D; Tue,  6 Jan 2015 08:28:36 -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-10.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150106162836.18055.11870.idtracker@ietfa.amsl.com>
Date: Tue, 06 Jan 2015 08:28:36 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/ZsQRUZn6OxBI0h_qc6eJ2EAxqWU
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, 06 Jan 2015 16:28:51 -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 Loop-Free Alternate Fast Re-Route
        Authors         : Stewart Bryant
                          Clarence Filsfils
                          Stefano Previdi
                          Mike Shand
                          Ning So
	Filename        : draft-ietf-rtgwg-remote-lfa-10.txt
	Pages           : 29
	Date            : 2015-01-06

Abstract:
   This document 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-10

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


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 Jan  6 09:33:19 2015
Return-Path: <jeff.tantsura@ericsson.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9281D1A1A5A for <rtgwg@ietfa.amsl.com>; Tue,  6 Jan 2015 09:33:09 -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 Jfa3krhnL_it for <rtgwg@ietfa.amsl.com>; Tue,  6 Jan 2015 09:33:07 -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 D152C1A1A31 for <rtgwg@ietf.org>; Tue,  6 Jan 2015 09:33:06 -0800 (PST)
X-AuditID: c6180641-f79916d00000623a-bd-54abbe5d3de7
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id FB.4C.25146.D5EBBA45; Tue,  6 Jan 2015 11:52:14 +0100 (CET)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.03.0195.001; Tue, 6 Jan 2015 12:33:05 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "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+E64gCsxlfoJyjLCMAgBALCfCAAEn7AA==
Date: Tue, 6 Jan 2015 17:33:04 +0000
Message-ID: <D0D15A53.86CC0%jeff.tantsura@ericsson.com>
References: <D07E84FE.77EE4%jeff.tantsura@ericsson.com> <D0C3A69E.80713%jeff.tantsura@ericsson.com> <12804_1420539065_54ABB4B9_12804_18132_1_9E32478DFA9976438E7A22F69B08FF920C74AE1B@OPEXCLILM34.corporate.adroot.infra.ftgroup>
In-Reply-To: <12804_1420539065_54ABB4B9_12804_18132_1_9E32478DFA9976438E7A22F69B08FF920C74AE1B@OPEXCLILM34.corporate.adroot.infra.ftgroup>
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.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <65F5B14892EE2747B2F37B5789D2AD6E@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprFIsWRmVeSWpSXmKPExsUyuXRPlG7cvtUhBt2zWSz+/tzKaLHuxAIW iwtvfjNbfN37kNWBxWPK742sHkuW/GTyaHl2ks3jy+XPbAEsUVw2Kak5mWWpRfp2CVwZZw+c YSpYJVFx8uM0xgbGLSJdjBwcEgImEh8Xm3UxcgKZYhIX7q1nA7GFBI4wShxYGNnFyAVkL2OU mHXgOSNIgk3AQOL/t+MsIAkRgauMErc6lzCBJJgFVCX+P1wKZgsLeEnc+TMVrEFEwFui9coD ZgjbSeLG2h3sIDaLgIrEpHeHWEFsXgFziQOTHzNCbHvKKLF65X+wDZwCXYwSm7u+sIBUMQLd 9/3UGqht4hK3nsxngrhbQGLJnvPMELaoxMvH/8CmigroSTzbsJkdIq4kMWnpOVaIXj2JG1On sEHY1hKr3sxmhLC1JZYtfM0McZGgxMmZT1gmAH2OZN0sJO2zkLTPQtI+C0n7AkbWVYwcpcWp ZbnpRoabGIGReUyCzXEH44JPlocYBTgYlXh4N/ivDhFiTSwrrsw9xCjNwaIkzqtZPS9YSCA9 sSQ1OzW1ILUovqg0J7X4ECMTB6dUA6OaWsyejb82M22boN+94pOF8k4v0fd6r8XS507TfcdX YdCe8Xe61MSMmlu7nTIPZQV/nSTtYHb51tp3D0V7PRy62GeemOD2N/wEf1X1BwO2yq9vL34T iOPbFCb3ZYJrhlaDkqr0hqgy+dOPKh6veSJ8ZKattl1X6/7Vb67qX/4xY44V71pzl9NKLMUZ iYZazEXFiQDFl85RrQIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/ZzxonlzY6N1REO_ij7CX_GbSpHw
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, 06 Jan 2015 17:33:09 -0000

Hi,

Happy New Year all!

Thanks Stephane, I=B9m sure - this is the first thing you did coming back
from holidays :)

If there are no more comments/questions we will proceed further, all -
please review the latest version posted.

Cheers,
Jeff


-----Original Message-----
From: "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>
Date: Tuesday, January 6, 2015 at 2:11 AM
To: Jeff Tantsura <jeff.tantsura@ericsson.com>, "rtgwg@ietf.org"
<rtgwg@ietf.org>, "draft-ietf-rtgwg-lfa-manageability@tools.ietf.org"
<draft-ietf-rtgwg-lfa-manageability@tools.ietf.org>
Cc: Alvaro Retana <aretana@cisco.com>
Subject: RE: Working Group last call on draft-ietf-rtgwg-lfa-manageability

>Hi Folks,
>
>First, I would like to wish you all the best for this new year !
>
>I just posted a new version of the draft addressing the comment from Uma,
>we are inline with the proposed update.
>
>http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-lfa-manageability-05.
>txt
>
>
>Best Regards,
>
>Stephane
>
>
>-----Original Message-----
>From: Jeff Tantsura [mailto:jeff.tantsura@ericsson.com]
>Sent: Saturday, December 27, 2014 09:08
>To: rtgwg@ietf.org; draft-ietf-rtgwg-lfa-manageability@tools.ietf.org
>Cc: Alvaro Retana
>Subject: Re: Working Group last call on draft-ietf-rtgwg-lfa-manageability
>
>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.
>
>
>__________________________________________________________________________
>_______________________________________________
>
>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 Tue Jan  6 13:02:41 2015
Return-Path: <rjs@rob.sh>
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 A8C121A6FEC for <rtgwg@ietfa.amsl.com>; Tue,  6 Jan 2015 13:02:37 -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 gxh4BBQ3EE7S for <rtgwg@ietfa.amsl.com>; Tue,  6 Jan 2015 13:02:23 -0800 (PST)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2a03:9800:10:4c::cafe:b00c]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B77581A0113 for <rtgwg@ietf.org>; Tue,  6 Jan 2015 13:02:21 -0800 (PST)
Received: from [88.128.80.1] (helo=[172.19.249.227]) by cappuccino.rob.sh with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <rjs@rob.sh>) id 1Y8bGY-0006Jl-Ij; Tue, 06 Jan 2015 21:02:16 +0000
Subject: Re: Working Group last call on draft-ietf-rtgwg-lfa-manageability
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Content-Type: text/plain; charset=utf-8
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <12804_1420539065_54ABB4B9_12804_18132_1_9E32478DFA9976438E7A22F69B08FF920C74AE1B@OPEXCLILM34.corporate.adroot.infra.ftgroup>
Date: Tue, 6 Jan 2015 21:02:00 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <49FE7B56-60D9-4FA4-875F-FAE7D9FAC06E@rob.sh>
References: <D07E84FE.77EE4%jeff.tantsura@ericsson.com> <D0C3A69E.80713%jeff.tantsura@ericsson.com> <12804_1420539065_54ABB4B9_12804_18132_1_9E32478DFA9976438E7A22F69B08FF920C74AE1B@OPEXCLILM34.corporate.adroot.infra.ftgroup>
To: stephane.litkowski@orange.com
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/Vj_ChbJdJEhjsP2lt11-_kFhzcw
Cc: "draft-ietf-rtgwg-lfa-manageability@tools.ietf.org" <draft-ietf-rtgwg-lfa-manageability@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: Tue, 06 Jan 2015 21:02:37 -0000

Hi Jeff,

Apologies, I missed commenting on the previous call. I think this draft =
is ready for publication, and operationally useful - I=E2=80=99ve =
reviewed the -05 draft that was posted. We are pushing for this =
functionality in our deployments as it is key for deterministic =
behaviours of LFA in SP networks.

Stephane and co-authors, thanks very much for your continued efforts on =
this work.

Cheers,
r.

> On 6 Jan 2015, at 10:11, stephane.litkowski@orange.com wrote:
>=20
> Hi Folks,
>=20
> First, I would like to wish you all the best for this new year !
>=20
> I just posted a new version of the draft addressing the comment from =
Uma, we are inline with the proposed update.
>=20
> =
http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-lfa-manageability-05.=
txt
>=20
>=20
> Best Regards,
>=20
> Stephane
>=20
>=20
> -----Original Message-----
> From: Jeff Tantsura [mailto:jeff.tantsura@ericsson.com]=20
> Sent: Saturday, December 27, 2014 09:08
> To: rtgwg@ietf.org; draft-ietf-rtgwg-lfa-manageability@tools.ietf.org
> Cc: Alvaro Retana
> Subject: Re: Working Group last call on =
draft-ietf-rtgwg-lfa-manageability
>=20
> All,
>=20
> 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?
>=20
>=20
> Happy New Year!
>=20
> Cheers,
> Jeff
>=20
>=20
>=20
>=20
> -----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
>=20
>> All,
>>=20
>> We are starting a working group last call on the subject document.
>=20
>=20
> =
__________________________________________________________________________=
_______________________________________________
>=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.
>=20
> 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.
>=20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


From nobody Tue Jan 13 01:34:18 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CAC81ACE44; Tue, 13 Jan 2015 01:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XgRs2DH06y2Q; Tue, 13 Jan 2015 01:34:14 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B760A1ACDDE; Tue, 13 Jan 2015 01:34:14 -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-lfa-manageability-07.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150113093414.13275.11913.idtracker@ietfa.amsl.com>
Date: Tue, 13 Jan 2015 01:34:14 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/iDi3dqN-wEseguT4hLY-768Hc0E>
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, 13 Jan 2015 09:34: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           : Operational management of Loop Free Alternates
        Authors         : Stephane Litkowski
                          Bruno Decraene
                          Clarence Filsfils
                          Kamran Raza
                          Martin Horneffer
                          Pushpasis Sarkar
	Filename        : draft-ietf-rtgwg-lfa-manageability-07.txt
	Pages           : 22
	Date            : 2015-01-13

Abstract:
   Loop Free Alternates (LFA), as defined in RFC 5286 is an IP Fast
   ReRoute (IP FRR) mechanism enabling traffic protection for IP traffic
   (and MPLS LDP traffic by extension).  Following first deployment
   experiences, this document provides operational feedback on LFA,
   highlights some limitations, and proposes a set of refinements to
   address those limitations.  It also proposes required management
   specifications.

   This proposal is also applicable to remote LFA solution.



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

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

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


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 Jan 19 09:58:25 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A89A21B2BF2; Mon, 19 Jan 2015 09:58:20 -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 gDWnUzc_2s0n; Mon, 19 Jan 2015 09:58:19 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D1D81B2BE1; Mon, 19 Jan 2015 09:58:19 -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-mrt-frr-architecture-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150119175819.28261.55783.idtracker@ietfa.amsl.com>
Date: Mon, 19 Jan 2015 09:58:19 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/2PImJulqSAVCrsEEZrbz4Z0LGHU>
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, 19 Jan 2015 17:58:20 -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           : An Architecture for IP/LDP Fast-Reroute Using Maximally Redundant Trees
        Authors         : Alia Atlas
                          Robert Kebler
                          Chris Bowers
                          Gabor Sandor Enyedi
                          Andras Csaszar
                          Jeff Tantsura
                          Russ White
	Filename        : draft-ietf-rtgwg-mrt-frr-architecture-05.txt
	Pages           : 41
	Date            : 2015-01-19

Abstract:
   With increasing deployment of Loop-Free Alternates (LFA) [RFC5286],
   it is clear that a complete solution for IP and LDP Fast-Reroute is
   required.  This specification provides that solution.  IP/LDP Fast-
   Reroute with Maximally Redundant Trees (MRT-FRR) is a technology that
   gives link-protection and node-protection with 100% coverage in any
   network topology that is still connected after the failure.

   MRT removes all need to engineer for coverage.  MRT is also extremely
   computationally efficient.  For any router in the network, the MRT
   computation is less than the LFA computation for a node with three or
   more neighbors.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-mrt-frr-architecture/

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-mrt-frr-architecture-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 Mon Jan 19 10:17:32 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5401A1B2BE4; Mon, 19 Jan 2015 10:17:29 -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 TfEhZjOFsyzL; Mon, 19 Jan 2015 10:17:27 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4254B1B2BE2; Mon, 19 Jan 2015 10:17:27 -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-mrt-frr-algorithm-02.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150119181727.11137.95164.idtracker@ietfa.amsl.com>
Date: Mon, 19 Jan 2015 10:17:27 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/ZBEPz5diAsF79TkwCOTlk-7ItuU>
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, 19 Jan 2015 18:17:29 -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           : Algorithms for computing Maximally Redundant Trees for IP/LDP Fast- Reroute
        Authors         : Gabor Sandor Enyedi
                          Andras Csaszar
                          Alia Atlas
                          Chris Bowers
                          Abishek Gopalan
	Filename        : draft-ietf-rtgwg-mrt-frr-algorithm-02.txt
	Pages           : 61
	Date            : 2015-01-19

Abstract:
   A complete solution for IP and LDP Fast-Reroute using Maximally
   Redundant Trees is presented in [I-D.ietf-rtgwg-mrt-frr-
   architecture].  This document defines the associated MRT Lowpoint
   algorithm that is used in the default MRT profile to compute both the
   necessary Maximally Redundant Trees with their associated next-hops
   and the alternates to select for MRT-FRR.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-mrt-frr-algorithm/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rtgwg-mrt-frr-algorithm-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-mrt-frr-algorithm-02


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

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


From nobody Thu Jan 22 07:29:01 2015
Return-Path: <pthubert@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 2450F1ACD0C for <rtgwg@ietfa.amsl.com>; Thu, 22 Jan 2015 07:28:58 -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 pfpsGLche7s5 for <rtgwg@ietfa.amsl.com>; Thu, 22 Jan 2015 07:28:55 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78C081ACCF2 for <rtgwg@ietf.org>; Thu, 22 Jan 2015 07:28:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3194; q=dns/txt; s=iport; t=1421940535; x=1423150135; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=N77kCn+hT//U+yqqf5jNevzmHl1jmub1M0rOd05SD+Y=; b=Wo+icdBrMD0HI+WnkFvAYgutLWTFmbkDxHDIChBvV7EmuWIQO8JbgIc+ SwrqQOB/YAlhFMZjVJDfyOgXchKFn9Sk8eDqDMpQ7AHlvY+J/ZLcU6jGh 530k9r1ozEcRy97YLWDl5hEYf2w6o8JTsi5rZrv/re4b0OmBfVZQuM106 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvYFAGIWwVStJV2Z/2dsb2JhbABagwZSUwUEgwDBHIInhW8CHHlDAQEBAQF9hAwBAQEEIxFDAgwGAQgRBAEBAwIGHQMCBDAUAQYBAQUEAQQOBQgBiCMIBb5HlFIBAQEBAQEBAQEBAQEBAQEBAQEBAQEXgSGOJzENgmIugRMFJQKOP4NKhmM2gkiHdIYvIoNubwGBFS9+AQEB
X-IronPort-AV: E=Sophos;i="5.09,449,1418083200"; d="scan'208";a="116603326"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-8.cisco.com with ESMTP; 22 Jan 2015 15:28:54 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t0MFSsjq011289 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtgwg@ietf.org>; Thu, 22 Jan 2015 15:28:54 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.100]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0195.001; Thu, 22 Jan 2015 09:28:54 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: New Version Notification for draft-thubert-rtgwg-arc-03.txt
Thread-Topic: New Version Notification for draft-thubert-rtgwg-arc-03.txt
Thread-Index: AdA2V/5WXAQkW8nDSqipu/xsYw3+NA==
Date: Thu, 22 Jan 2015 15:28:54 +0000
Deferred-Delivery: Thu, 22 Jan 2015 15:28:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD848B40A30@xmb-rcd-x01.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.49.80.18]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/bJqnoNSjpK9jTOguIEjWv4qTrRQ>
Cc: "Dirk Anteunis \(danteuni\)" <danteuni@cisco.com>, "Vengada Prasad Govindan \(venggovi\)" <venggovi@cisco.com>, "Patrice Bellagamba \(pbellaga\)" <pbellaga@cisco.com>, "Frank Brockners \(fbrockne\)" <fbrockne@cisco.com>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 15:28:58 -0000

RGVhciBhbGw6DQoNClBsZWFzZSBub3RlIHRoYXQgYXQgbG9uZyBsYXN0LCB3ZSBzdWJtaXR0ZWQg
YW4gdXBkYXRlIG9mIHRoZSBBUkMgZHJhZnQgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1k
cmFmdHMvZHJhZnQtdGh1YmVydC1ydGd3Zy1hcmMtMDMudHh0ICANClRoaXMgZHJhZnQgaXMgYW4g
aW5mb3JtYXRpdmUgd29yayB0aGF0IGxheXMgb3V0IHRoZSBiYXNlIGNvbmNlcHRzIG9mIHRoZSBB
UkNzIHRlY2hub2xvZ3kuDQoNClRoZSB1cGRhdGUgYWRkcyBpbmRpY2F0aW9ucyBvbjoNCi0gT0FN
IGZyYW1lcw0KLSBBcHBsaWNhdGlvbiBvZiBNUExTIGFuZCBTZWdtZW50IFJvdXRpbmcgdGVjaG5p
cXVlcyB0byBpbXBsZW1lbnQgQVJDcywgDQotIHJlbGlhYmxlIGZsb29kaW5nIG92ZXIgYW4gQVJD
IHNldCwNCi0gY2VudHJhbGl6ZWQgKCJTRE4iKSBjb21wdXRhdGlvbiBhbmQgKG1pY3JvbG9vcC1s
ZXNzKSB1cGRhdGUgaW5qZWN0aW9uLA0KLSBwcm9ibGVtcyB0aGF0IEFSQ3MgY2FuIGhlbHAgc29s
dmUsIHN1Y2ggYXMgT2x5bXBpYyBSaW5ncyBhbmQgbXVsdGlwbGUgZmFpbHVyZXMgKFNSTEcpLiAN
Cg0KV2UgYWxzbyByZXB1Ymxpc2hlZCB0aGUgQVJDIHZzLiBNUlQgZHJhZnQgKGh0dHA6Ly93d3cu
aWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LXRodWJlcnQtcnRnd2ctYXJjLXZzLW1ydC0w
MS50eHQgKSBhcyBhIHJlZnJlc2hlciwgd2l0aCBubyBzaWduaWZpY2FudCBjaGFuZ2UuDQoNCkNo
ZWVycywNCg0KUGFzY2FsDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGlu
dGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10g
DQpTZW50OiBqZXVkaSAyMiBqYW52aWVyIDIwMTUgMTQ6MTgNClRvOiBQYXRyaWNlIEJlbGxhZ2Ft
YmEgKHBiZWxsYWdhKTsgUGFzY2FsIFRodWJlcnQgKHB0aHViZXJ0KTsgUGF0cmljZSBCZWxsYWdh
bWJhIChwYmVsbGFnYSk7IFBhc2NhbCBUaHViZXJ0IChwdGh1YmVydCkNClN1YmplY3Q6IE5ldyBW
ZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtdGh1YmVydC1ydGd3Zy1hcmMtMDMudHh0DQoN
Cg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LXRodWJlcnQtcnRnd2ctYXJjLTAzLnR4dCBo
YXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFBhc2NhbCBUaHViZXJ0IGFuZCBwb3N0
ZWQgdG8gdGhlIElFVEYgcmVwb3NpdG9yeS4NCg0KTmFtZToJCWRyYWZ0LXRodWJlcnQtcnRnd2ct
YXJjDQpSZXZpc2lvbjoJMDMNClRpdGxlOgkJQXZhaWxhYmxlIFJvdXRpbmcgQ29uc3RydWN0cw0K
RG9jdW1lbnQgZGF0ZToJMjAxNS0wMS0yMg0KR3JvdXA6CQlJbmRpdmlkdWFsIFN1Ym1pc3Npb24N
ClBhZ2VzOgkJMjENClVSTDogICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0
LWRyYWZ0cy9kcmFmdC10aHViZXJ0LXJ0Z3dnLWFyYy0wMy50eHQNClN0YXR1czogICAgICAgICBo
dHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC10aHViZXJ0LXJ0Z3dnLWFyYy8N
Ckh0bWxpemVkOiAgICAgICBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC10aHViZXJ0
LXJ0Z3dnLWFyYy0wMw0KRGlmZjogICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlm
Zj91cmwyPWRyYWZ0LXRodWJlcnQtcnRnd2ctYXJjLTAzDQoNCkFic3RyYWN0Og0KICAgVGhpcyBk
cmFmdCBpbnRyb2R1Y2VzIHRoZSBjb25jZXB0IG9mIEFSQywgYSB0d28tZWRnZWQgcm91dGluZw0K
ICAgY29uc3RydWN0IHRoYXQgZm9ybXMgaXRzIG93biBmYXVsdCBpc29sYXRpb24gYW5kIHJlY292
ZXJ5IGRvbWFpbi4NCiAgIFRoZSBuZXcgcGFyYWRpZ20gY2FuIGJlIGxldmVyYWdlZCB0byBpbXBy
b3ZlIHRoZSBuZXR3b3JrIHV0aWxpemF0aW9uDQogICBhbmQgcmVzaWxpZW5jeSBmb3IgdW5pY2Fz
dCBhbmQgbXVsdGljYXN0IHRyYWZmaWMgaW4gbXVsdGlwbGUNCiAgIGVudmlyb25tZW50cywgYW5k
IGlzIG9wdGltaXplZCB0byBjb21wdXRlIHNob3J0IHJlcm91dGUgcGF0aHMgaW4gY2FzZQ0KICAg
b2YgYnJlYWthZ2VzLg0KDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICANCg0KDQpQbGVhc2Ug
bm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBv
ZiBzdWJtaXNzaW9uIHVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFp
bGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0DQoNCg==


From nobody Fri Jan 23 13:10:21 2015
Return-Path: <jmh@joelhalpern.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 935B01A8858; Fri, 23 Jan 2015 13:09:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v_cOQNQj-IM0; Fri, 23 Jan 2015 13:09:57 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8ED111A87BE; Fri, 23 Jan 2015 13:09:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id F08661BC717E; Fri, 23 Jan 2015 13:09:39 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-134-12.clppva.east.verizon.net [70.106.134.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 14A351BC7164; Fri, 23 Jan 2015 13:09:38 -0800 (PST)
Message-ID: <54C2B86A.6010607@joelhalpern.com>
Date: Fri, 23 Jan 2015 16:08:58 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>
Subject: RtgDir review: draft-ietf-rtgwg-cl-use-cases-06.txt
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/NzkwP52A6IR1sac1yTXrgTbVyT0>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, draft-ietf-rtgwg-cl-use-cases@tools.ietf.org, "<rtgwg@ietf.org>" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 21:09:58 -0000

Hello,

I have been selected as the Routing Directorate reviewer for this draft. 
The Routing Directorate seeks to review all routing or routing-related 
drafts as they pass through IETF last call and IESG review, and 
sometimes on special request. The purpose of the review is to provide 
assistance to the Routing ADs. For more information about the Routing 
Directorate, please see â€‹ 
http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Although these comments are primarily for the use of the Routing ADs, it 
would be helpful if you could consider them along with any other IETF 
Last Call comments that you receive, and strive to resolve them through 
discussion or by updating the draft.

Document: draft-ietf-rtgwg-cl-use-cases-06.txt
     Advanced Multipath Use Cases and Design Considerations
Reviewer: Joel M. Halpern
Review Date: 23-January-2015
IETF LC End Date: N/A
Intended Status: Informational

Summary: No issues found. This document is ready for publication.

Minor note: This draft appears to have expired.


From nobody Fri Jan 30 10:11:11 2015
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6650E1A1A43; Fri, 30 Jan 2015 10:10:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.811
X-Spam-Level: 
X-Spam-Status: No, score=-11.811 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 C9ZIzQXLWUWY; Fri, 30 Jan 2015 10:10:38 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DFCB1A0086; Fri, 30 Jan 2015 10:10:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8167; q=dns/txt; s=iport; t=1422641434; x=1423851034; h=message-id:date:from:reply-to:mime-version:to:cc:subject: content-transfer-encoding; bh=ee4q/sK4xWHxKgss0V5dy7bqzHkbukGm82lRrLAFths=; b=R4lACcQQY8kimSlfV9HTc/suYECRAYM6uwdhPKTwunoToF204e1fLB19 l1i1MXGFAR8O94sijmHJppXzzKwuuPaY4M3n1jCa6mcABpPVwYiWVjRki abPXQIoEaJvg4wY4TlUozP3OQ36mbFYMXiSmum76Ppad7mt46mCJ501Xp 0=;
X-IronPort-AV: E=Sophos;i="5.09,492,1418083200"; d="scan'208";a="328430995"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 30 Jan 2015 18:10:30 +0000
Received: from [10.61.106.207] (dhcp-10-61-106-207.cisco.com [10.61.106.207]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t0UIATmS024607;  Fri, 30 Jan 2015 18:10:29 GMT
Message-ID: <54CBC915.8010702@cisco.com>
Date: Fri, 30 Jan 2015 18:10:29 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: adrian Farrel <adrian@olddog.co.uk>
Subject: Adrian Farrel's Comments on draft-ietf-rtgwg-remote-lfa
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/FKZnv30y6ilYRMmtevvISQufkWE>
Cc: "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>, "iesg@ietf.org" <iesg@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: Fri, 30 Jan 2015 18:10:45 -0000

Comment (2015-01-06 for -10)

SB> Adrian here is the commentary on the resolution
of your comments:

Although it causes some pain with abbreviations and a little more care
in explanation, you need to put the Introduction as the first section in
the document. The RFC editor will insist on this, so it is better if you
do it now and get the wording exactly how you would like it.

SB> I have put the following introduction before the definition of terms:

"RFC 5714 [RFC5714] describes a framework for IP Fast Re-route (IPFRR)
and provides a summary of various proposed IPFRR solutions. A basic
mechanism using loop-free alternates (LFAs) is described in  that
provides good repair coverage in many topologies, especially those
that are highly meshed. However, some topologies, notably ring based
topologies are not well protected by LFAs alone because there is no
neighbor of the point of local repair (PLR) that has a cost to the
destination without traversing the failure that is cheaper than the
cost to the destination via the failure."

"The method described in this document extends LFA approach
described in to cover many of these cases by tunneling the packets
that require IPFRR to a node that is both reachable from the
PLR and can reach the destination."

SB> Then the old introduction is renamed Overview of Solution and
starts with

"The problem of LFA IPFRR reachability in some networks is illustrated by
the network fragment shown in Figure 1."

SB> It then continues as before with the Figure

---

You are using RFC 5714 as a Normative Reference by making me go there
for the definition of terms. Please move it to the correct section.

SB> Done
---

IMHO your definition of FIB is rather loose.  Fortunately (?) "FIB" is
barely used in this document, so it might not be important, but if you
wanted to fix it:
- you are talking about IP packets in this document
- the actions are, I think, limited to forwarding actions

SB> As Alia said mostly MPLS, but the solution applies to both IP and MPLS.
SB> However I think I can get rid of the definition.

SB> I have modified the P-space definition slightly to

"The P-space of a router with respect to a protected link is
the set of routers reachable from that specific router using
the pre-convergence shortest paths, without any of those
paths (including equal cost path splits) transiting that
protected link."

SB> Then is section 10

"When the network re-converges, microloops [RFC5715]
can form due to transient inconsistencies in the forwarding
tables of different routers."

SB> Then I have deleted the definition of FIB.

---

SB> Throughout the text, the terms P-space, Q-space, and extended P-space
are used rather loosely. For example, when discussing Figure 1 you say
"S's extended P-space", but this is really "S's extended P-space with
respect to S-E". Someone familiar with the work might say that it is
obvious from the context that we are discussing the link S-E, and it is,
but the terminology needs to be tight.

SB> I have gone though the uses and cleaned it it.

SB> It seems a bit wordy in places, but it is more precise.

---

Section 2

    B
    has equal-cost paths via B-A-S-E and B-C-D-E and so may go through
    S-E.

I don't think B is going anywhere. Maybe...

    B
    has equal-cost paths to E via B-A-S-E and B-C-D-E and so may reach E
    through S-E.

SB> This now says:

"B has equal-cost paths to E via B-A-S-E and B-C-D-E and so the forwarder
at S might choose to send a packet to E via link S-E. Hence B is not in the
Q-space of E with respect to link S-E."

---

Section 2

    In MPLS networks the targeted LDP
    protocol needed to learn the label binding at the repair tunnel
    endpoint is a well understood and widely deployed technology.

But it would still benefit from a citation or a forward reference to
section 7.

SB> Done

---

I enjoyed 3.2

    relatively rare as is the incidence of failure in a well managed
    network.

So, managing my network well is protection against back-hoes. Nice.

SB> It's not a well managed network if it does not include a back-hoe
exclusion force field along the fiber tracks.

SB> I have left the text as it was, since I think the meaning is clear.

---

In 3.2

    Multiple
    repairs MAY share a tunnel end point.

1. s/repairs/repair tunnels/
2. s/MAY/may/ since this is not an implementation or operational choice,
    but a fact of life.

SB> Done

---

In 4.2 you have truncated...

    The repair tunnel endpoint needs to be a node in the network
    reachable from S without traversing S-E.

...and...

    o  The repair tunneled point MUST be reachable from the tunnel source
       without traversing the failed link; and

You mean "reachable using the normal FIB", I think.

SB> No, the first hop may not be in the normal FIB, that is a property of
LFAs. All of the other hops at in the normal FIB.

SB> I am concerned that fixing this would add confusion so have
left the text.

---

Section 4.3

    The preceding text has mostly described the computation of the remote
    LFA repair target (PQ) in terms of the intersection of two
    reachability graphs computed using SPFs.

"mostly"?

SB> mostly deleted

"reachability graphs"? Were they? Or were they reachability sets?

SB> I think graphs since you take into account how you get there
when you compute the SPT.

---

Your pseducode in 4.3 invokes an unresolved (and undescribed) function
Compute_Forward_SPF().

Actually, I think this is a bogus line that can be deleted.

SB> I would argue that the computation is well known, and it is
needed for the edge case that S-E has ECMPs that were
discarded by normal routing, for example if normal
routing ignored ECMP.

---

I think the introduction of "pseudonode" in 4.3 may be a little without
context.

SB> I have added a pointer to RFC1195. The reader can get from there
to ISO-10589, but that is less accessible as a first reference.

---

Section 7
    If for any reason the TLDP session cannot
    not be established

s/cannot not/cannot/

SB> Done

---

I think [RFC5424] and [RFC3411] are pretty poor references to give in
section 7. You appear to be saying that an implementation that cannot
establish a TLDP session should write a MIB module, standardise it, and
then report an error.

Can't you find an existing LDP MIB module that reports Session-up
failures?

Or maybe just delete "using any well known mechanism such as Syslog
[RFC5424] or SNMP [RFC3411]."

SB> It now says:

"... SHOULD advise the operator about the protection setup issue
through the network management system."

---

I think you can strengthen the security considerations. You have:

    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.

1. "To prevent their use" is surely consistent with a "MUST".
    The fact that you want to say "SHOULD" means that you need to turn
    the text around...

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

SB> Done.

2. You can add a note about what traffic can be placed into a repair
    tunnel. You already have this earlier in the document, and it is
    worth restating.

SB> See below

3. I think you should also make note of whether the repair tunnel is
    advertised by the routing protocol as an available link.

SB> I have added:

"Other than OAM traffic, used to verify the correct operation of a repair
tunnel, only traffic that is being protected as a result of a link failure
is placed a repair tunnel. The repair tunnel MUST NOT be advertised
by the routing protocol as a link that may be used to carry normal
user traffic, or routing protocol traffic."

Will be in version 11 shortly.

Stewart



From nobody Fri Jan 30 10:49:04 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE33D1A1B19; Fri, 30 Jan 2015 10:49:00 -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 iqY8s9bQQYfz; Fri, 30 Jan 2015 10:48:59 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5618D1A19F6; Fri, 30 Jan 2015 10:48:59 -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-11.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150130184859.11742.11809.idtracker@ietfa.amsl.com>
Date: Fri, 30 Jan 2015 10:48:59 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/oXDsUlzYE5iJCNk8p-iSp6VWkow>
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 18:49:01 -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 Loop-Free Alternate (LFA) Fast Re-Route (FRR)
        Authors         : Stewart Bryant
                          Clarence Filsfils
                          Stefano Previdi
                          Mike Shand
                          Ning So
	Filename        : draft-ietf-rtgwg-remote-lfa-11.txt
	Pages           : 30
	Date            : 2015-01-30

Abstract:
   This document 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-11

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


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/

