Re: [OSPF] [Technical Errata Reported] RFC3101 (4767)

"Acee Lindem (acee)" <acee@cisco.com> Mon, 08 August 2016 11:14 UTC

Return-Path: <acee@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16AAE12B028 for <ospf@ietfa.amsl.com>; Mon, 8 Aug 2016 04:14:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.768
X-Spam-Level:
X-Spam-Status: No, score=-15.768 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 hgcMWkr-Yydz for <ospf@ietfa.amsl.com>; Mon, 8 Aug 2016 04:14:51 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E90A12D190 for <ospf@ietf.org>; Mon, 8 Aug 2016 04:14:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3974; q=dns/txt; s=iport; t=1470654879; x=1471864479; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=6cL1ubqZGq/YfNrhUltDQE6cFK/Ds8a6Ag0iKggJMlc=; b=cZK55UGIBSNU2u9thJncYzKsjNEkFITR4lev5sYk9wqJ1GEtycC9iaNT hpHfWHbmd2xb04i4KBOe2lHzmtxmiKQCGjCeRblyeo2OjtjWr2NNOYjjs K1DAqTA7t2wamE7opc7tvGDGpHBWU+bdDOU0b+4ZSvGqVM018QMhA8v0e 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BtAgAaaahX/4sNJK1DGoNFVnwHuQeBfSSFeQIcgRg4FAEBAQEBAQFdJ4RfAQUjEUUQAgEIGgImAgICMBUQAgQBDQWIMQ4tsg+QCQEBAQEBAQEBAQEBAQEBAQEBAQEBARyBAYl2gTmCagEBgxyCWgWIJQyHHYlrAYYciG2Ba4RbiH2GZIlHAR42ghIND4FMbgEThX83fwEBAQ
X-IronPort-AV: E=Sophos;i="5.28,489,1464652800"; d="scan'208";a="135427747"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Aug 2016 11:14:37 +0000
Received: from XCH-RTP-003.cisco.com (xch-rtp-003.cisco.com [64.101.220.143]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u78BEb0V021237 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 8 Aug 2016 11:14:38 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-003.cisco.com (64.101.220.143) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 8 Aug 2016 07:14:37 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Mon, 8 Aug 2016 07:14:36 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>, "pmurphy@noc.usgs.net" <pmurphy@noc.usgs.net>, "akatlas@gmail.com" <akatlas@gmail.com>, "db3546@att.com" <db3546@att.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>, "Abhay Roy (akr)" <akr@cisco.com>
Thread-Topic: [Technical Errata Reported] RFC3101 (4767)
Thread-Index: AQHR8Sf71gJsVCFEVECeSTlIVIj5NqA+6cGA
Date: Mon, 08 Aug 2016 11:14:36 +0000
Message-ID: <D3CDE054.762DF%acee@cisco.com>
References: <20160808035016.6B4C1B80C59@rfc-editor.org>
In-Reply-To: <20160808035016.6B4C1B80C59@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: text/plain; charset="utf-8"
Content-ID: <3B8920D34E6A704CBAD9DC9EF2AB6BF1@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/JVvNhUCZn_bL-e4hjYbOQfE3o7A>
Cc: "ospf@ietf.org" <ospf@ietf.org>, "chao.fu@ericsson.com" <chao.fu@ericsson.com>
Subject: Re: [OSPF] [Technical Errata Reported] RFC3101 (4767)
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2016 11:14:53 -0000

This Errata should be rejected as it is easy to envision a topology where
an ABR for an NSSA receives an NSSA-LSA from an NSSA internal router and
an AS-Exernal-LSA from originating routers that do not receive each others
equivalent LSAs. Furthermore, even if this were not the case, the
referenced text refers to LSAs that are both NSSA-LSAs as opposed to a
mixture of an NSSA-LSA and an AS-External-LSA.

Thanks,
Acee 

On 8/7/16, 11:50 PM, "RFC Errata System" <rfc-editor@rfc-editor.org> wrote:

>The following errata report has been submitted for RFC3101,
>"The OSPF Not-So-Stubby Area (NSSA) Option".
>
>--------------------------------------
>You may review the report below and at:
>http://www.rfc-editor.org/errata_search.php?rfc=3101&eid=4767
>
>--------------------------------------
>Type: Technical
>Reported by: Chao Fu <chao.fu@ericsson.com>
>
>Section: 2.5.(6).(e)
>
>Original Text
>-------------
>          (e) If the current LSA is functionally the same as an
>              installed LSA (i.e., same destination, cost and non-zero
>              forwarding address) then apply the following priorities in
>              deciding which LSA is preferred:
>
>                 1. A Type-7 LSA with the P-bit set.
>
>                 2. A Type-5 LSA.
>
>                 3. The LSA with the higher router ID.
>
>              [NSSA]
>
>Corrected Text
>--------------
>NULL (it should be deleted because no LSAs would be compared here.)
>
>Notes
>-----
>If one LSA is Type-5 and the other is Type-7, one of them would be
>rejected at step (2.5.(3) ( please refer to OSPF mail list:
>https://mailarchive.ietf.org/arch/msg/ospf/KBoh5T75o-s7n_bL1knrc6uVlTs ).
>If both of them are Type-7 LSAs, one of them would be flushed according
>2.4: 
>   If two NSSA routers, both
>   reachable from one another over the NSSA, originate functionally
>   equivalent Type-7 LSAs (i.e., same destination, cost and non-zero
>   forwarding address), then the router having the least preferred LSA
>   should flush its LSA.
>
>As a result, rule (e) would never be applied and should be removed.
>
>Instructions:
>-------------
>This erratum is currently posted as "Reported". If necessary, please
>use "Reply All" to discuss whether it should be verified or
>rejected. When a decision is reached, the verifying party (IESG)
>can log in to change the status and edit the report, if necessary.
>
>--------------------------------------
>RFC3101 (draft-ietf-ospf-nssa-update-11)
>--------------------------------------
>Title               : The OSPF Not-So-Stubby Area (NSSA) Option
>Publication Date    : January 2003
>Author(s)           : P. Murphy
>Category            : PROPOSED STANDARD
>Source              : Open Shortest Path First IGP
>Area                : Routing
>Stream              : IETF
>Verifying Party     : IESG
>