--- 1/draft-ietf-rtgwg-multihomed-prefix-lfa-05.txt 2018-02-08 12:13:10.734487313 -0800 +++ 2/draft-ietf-rtgwg-multihomed-prefix-lfa-06.txt 2018-02-08 12:13:10.774488271 -0800 @@ -1,36 +1,36 @@ Routing Area Working Group P. Sarkar, Ed. Internet-Draft Arrcus, Inc. Updates: 5286 (if approved) S. Hegde Intended status: Standards Track Juniper Networks, Inc. -Expires: August 10, 2018 U. Chunduri, Ed. +Expires: August 12, 2018 U. Chunduri, Ed. Huawei USA J. Tantsura - Individual + Nuage Networks H. Gredler RtBrick, Inc. - February 6, 2018 + February 8, 2018 LFA selection for Multi-Homed Prefixes - draft-ietf-rtgwg-multihomed-prefix-lfa-05 + draft-ietf-rtgwg-multihomed-prefix-lfa-06 Abstract This document shares experience gained from implementing algorithms to determine Loop-Free Alternates for multi-homed prefixes. In particular, this document provides explicit inequalities that can be used to evaluate neighbors as a potential alternates for multi-homed prefixes. It also provides detailed criteria for evaluating potential alternates for external prefixes advertised by OSPF ASBRs. This documents updates and expands some of the "Routing Aspects" as - specified in Section 6 of [RFC 5286]. + specified in Section 6 of RFC 5286. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119 [RFC2119]. Status of This Memo This Internet-Draft is submitted in full conformance with the @@ -38,21 +38,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on August 10, 2018. + This Internet-Draft will expire on August 12, 2018. Copyright Notice Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -386,22 +386,21 @@ 1a. if primary ASBR and alternate ASBR are intra area non-backbone path go to step 2. 1b. If primary ASBR and alternate ASBR belong to intra-area backbone and/or inter-area path go to step 2. 1c. for other paths, skip this alternate ASBR and consider next ASBR. 2. If cost type (type1/type2) advertised by alternate ASBR same as primary - 2a. If not, same skip alternate ASBR and consider - next ASBR. + 2a. If not, same skip alternate ASBR and consider next ASBR. 2b. If same proceed to step 3. 3. If cost type is type1 3a. If cost is same, program ECMP and return. 3b. else go to step 5. 4 If cost type is type 2 4a. If cost is different, skip alternate ASBR and consider next ASBR. 4b. If type2 cost is same, proceed to step 4c to compare @@ -710,17 +709,20 @@ Uma Chunduri (editor) Huawei USA 2330 Central Expressway Santa Clara, CA 95050 USA Email: uma.chunduri@huawei.com Jeff Tantsura - Individual + Nuage Networks + 755 Ravendale Drive + Mountain View, CA 94043 + USA Email: jefftant.ietf@gmail.com Hannes Gredler RtBrick, Inc. Email: hannes@rtbrick.com