Re: progressing draft-ietf-rtgwg-mofrr-06 [AUTHOR RESPONSE NEEDED]

Alia Atlas <akatlas@gmail.com> Tue, 12 May 2015 15:06 UTC

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 7375C1A8961 for <rtgwg@ietfa.amsl.com>; Tue, 12 May 2015 08:06:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level:
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J8lQS_FypQJe for <rtgwg@ietfa.amsl.com>; Tue, 12 May 2015 08:06:29 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAEA21B2E4F for <rtgwg@ietf.org>; Tue, 12 May 2015 08:06:01 -0700 (PDT)
Received: by oiko83 with SMTP id o83so8245087oik.1 for <rtgwg@ietf.org>; Tue, 12 May 2015 08:06:01 -0700 (PDT)
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=70Tf1foj7wf+P+j8llFASwlMsByE8wLONBx0z9jCAtY=; b=tdJj7Y6fk/nrZyj+UFiSlt3UXCTkmqVTGDN0A5hS3SWHn3e/u5FnYTf7Bkiy+ZEgl0 Y4lBzxIZfxDAyLFwt8DsIKuGjhEVewbiNFHjf7UHcM1zR9t6B/iDSLXHvRnxdf2LjEb9 VG8FFZ6Mg0Ywvbr+y8asH4w2wfCaS8j7fxPm7F9HmDywdu5IHU1h5P26oEjU4IFZ0Hcf hltf9JDTk/rcf/9LMdArbaVN3e+wZySm/8E6mKc12mmC8w8XgynKAIXCHZFgKp78eo1w DH4iu/awFKLfDIPSJZm2uy2i4EhT5BBik8+/TPhj0defcFtj0fXBm7ATS6QAttOGtAyx 83sw==
MIME-Version: 1.0
X-Received: by 10.60.78.232 with SMTP id e8mr12532616oex.24.1431443161133; Tue, 12 May 2015 08:06:01 -0700 (PDT)
Received: by 10.60.172.77 with HTTP; Tue, 12 May 2015 08:06:01 -0700 (PDT)
In-Reply-To: <DA269A34-D852-48E5-8E60-54E1F9BF3A93@cisco.com>
References: <CAG4d1rcR70zoTU6VWONJUZjWua4rnNLjEVNCYDqARn9gWkjoKA@mail.gmail.com> <3989FBE3-BE8C-4DCF-A0FB-83F4A8A1629D@cisco.com> <CAG4d1rf1d9Cun9RxUArcBk8avCLr8YXt2HavTR3y6xDX9dV02w@mail.gmail.com> <DA269A34-D852-48E5-8E60-54E1F9BF3A93@cisco.com>
Date: Tue, 12 May 2015 11:06:01 -0400
Message-ID: <CAG4d1rcJDK0s0x26i+SOSvEb0wMKkZTkJtt0jjoQ5pxnSJwNLg@mail.gmail.com>
Subject: Re: progressing draft-ietf-rtgwg-mofrr-06 [AUTHOR RESPONSE NEEDED]
From: Alia Atlas <akatlas@gmail.com>
To: IJsbrand Wijnands <ice@cisco.com>
Content-Type: multipart/alternative; boundary="089e0111ba6822b8dd0515e3d56f"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/Z_KRstPshq80vg5h76jDGf9ItHI>
Cc: draft-ietf-rtgwg-mofrr@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, 12 May 2015 15:06:35 -0000

Hi Ice,

On Tue, May 12, 2015 at 4:18 AM, IJsbrand Wijnands <ice@cisco.com> wrote:

> Hi Alia,
>
>
> > It is a gap and I'd like to see a short sentence about it in the draft.
> Troubleshooting is very important.  I don't expect this draft to address
> it, but to indicate the gap would be, I believe, useful.
>
> Ok, I’ll add this to the draft.
>

Thanks


> > Regarding the micro-loops related to MoFRR. I was not involved in the
> private discussion you had regarding MoFRR, IGP re-convergence and loops.
> So I can’t really address that concern. To me it does not look any
> different from a normal IGP convergence with PIM and mLDP. Can clarify?
> >
> > Sure - the question is whether - during IGP reconvergence - either of
> the trees will actually stay stable or will have micro-loops.  If the
> topology is basically split - so dual-plane backbone or the like - this
> isn't an issue.  However, for more interesting topologies, there can be
> micro-loops that may affect the traffic even when it is using the secondary
> tree.
> >
> > Again - just a brief sentence mentioning the concern to consider would
> be useful.  I think that'll help avoid surprises by folks interested in
> MoFRR.
>
> I think what you are saying is that with non-DUAL plane topologies, there
> is no guarantee that the secondary path is going to be stable,
> un-interuppted traffic flow after switching to it. If the secondary path is
> effected by the same failure that effected the primary path, any sort of
> failure may apply here, including micro-loops. I don’t see any additional
> concerns regarding micro-loops with MoFRR, do you agree?
>
> I can add a statement regarding the above in the draft, but its its not
> specific to micro-loops..
>

A general statement is fine.  I think you are right that microloops aren't
an extra concern.

Regards,
Alia


> Thx,
>
> Ice.