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

IJsbrand Wijnands <ice@cisco.com> Tue, 12 May 2015 08:18 UTC

Return-Path: <ice@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 D29611A3BA6 for <rtgwg@ietfa.amsl.com>; Tue, 12 May 2015 01:18:15 -0700 (PDT)
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 lZsSmyAy0gYi for <rtgwg@ietfa.amsl.com>; Tue, 12 May 2015 01:18:14 -0700 (PDT)
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 BE0BF1A6EE6 for <rtgwg@ietf.org>; Tue, 12 May 2015 01:18:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1703; q=dns/txt; s=iport; t=1431418693; x=1432628293; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=aN4KVAR+UF7zm3rGkPmKsaXqEQ3gopR1it0Nodo2krE=; b=amdE2Q0cFcgWtA4XVTICltRii3OU0JOJr0vxoenK8ns1Q6NIFbx3gsE1 ghmg9HTkymzR128cZN7lU1tOjmgmOVEzNmoDPNiSZLwyXZD0eqtDkE03S WJ2KAtJZ2PkWhc7fzcZPFep0a6bH8S56kK4QTnZtG+AGzEcGR5c0R2tKv 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BcBQDRtlFV/xbLJq1ch1+vfQEBAQEBAQUBgQSQcQmHXQKBaxQBAQEBAQEBgQqEIQEBAwEjVgULCw4MAiYCAlcGiDcItGuTegEBAQEBAQEBAQEBAQEBAQEBAQEZgSGEdYUjhFIzB4JoL4EWBZ04lmojYYMYPIJ3AQEB
X-IronPort-AV: E=Sophos;i="5.13,413,1427760000"; d="scan'208";a="492619505"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 12 May 2015 08:18:10 +0000
Received: from dhcp-10-61-99-181.cisco.com (dhcp-10-61-99-181.cisco.com [10.61.99.181]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t4C8IAcM011585 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 May 2015 08:18:10 GMT
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Subject: Re: progressing draft-ietf-rtgwg-mofrr-06 [AUTHOR RESPONSE NEEDED]
From: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <CAG4d1rf1d9Cun9RxUArcBk8avCLr8YXt2HavTR3y6xDX9dV02w@mail.gmail.com>
Date: Tue, 12 May 2015 10:18:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA269A34-D852-48E5-8E60-54E1F9BF3A93@cisco.com>
References: <CAG4d1rcR70zoTU6VWONJUZjWua4rnNLjEVNCYDqARn9gWkjoKA@mail.gmail.com> <3989FBE3-BE8C-4DCF-A0FB-83F4A8A1629D@cisco.com> <CAG4d1rf1d9Cun9RxUArcBk8avCLr8YXt2HavTR3y6xDX9dV02w@mail.gmail.com>
To: Alia Atlas <akatlas@gmail.com>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/o6DNFuUPR3xg6VNRDhH1NOEmibA>
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 08:18:16 -0000

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.

> 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..

Thx,

Ice.