Re: [OSPF] [Technical Errata Reported] RFC3101 (4767)
"Acee Lindem (acee)" <acee@cisco.com> Thu, 11 August 2016 16:46 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 C245112D81C for <ospf@ietfa.amsl.com>; Thu, 11 Aug 2016 09:46:51 -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 fLBFS9Fhi96E for <ospf@ietfa.amsl.com>; Thu, 11 Aug 2016 09:46:50 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5BC612D5CD for <ospf@ietf.org>; Thu, 11 Aug 2016 09:46:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7386; q=dns/txt; s=iport; t=1470934010; x=1472143610; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=yRfhIR9SmWTihz/k27zU8RhI9dswwCERCkBcA94LITM=; b=KWIXKw5XRikFyrQK7OEhBAQ2YnTjt1Aq+fO5QhTo+zpImgNgIXk/nahT 73gSQBNPZ5ecb3AN4gk3jcUqwknL0cFzMILN7/QGexZwOrmUQiu2VWOS+ ThYCxl4iMB8gSf4tO1QhjfLJG1Kg/2ZxO3h41YLFSpVvyfPXKShlNv7ZR 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B2AgCaq6xX/4MNJK1EGoNFVnwHrH6MKIF9JIV5AhyBRjgUAQEBAQEBAV0nhF4BAQUjEUUMBAIBCBEEAQEDAiMDAgICHxEUAQgIAgQBDQWIFwMXDi2vPotgDYRAAQEBAQEBAQEBAQEBAQEBAQEBAQEBHIEBiHOBA4E5gQqBYAEBGxeCaoJaBYgmDIcdiTk0AYYdhjmCPYFrhFuIfYZkgUmECIN3AR42ghIND4FMbgEThS03fwEBAQ
X-IronPort-AV: E=Sophos;i="5.28,506,1464652800"; d="scan'208";a="134846080"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Aug 2016 16:46:21 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u7BGkJCE017647 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 11 Aug 2016 16:46:21 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 11 Aug 2016 12:46:20 -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; Thu, 11 Aug 2016 12:46:19 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Chao Fu <chao.fu@ericsson.com>, 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+6cGAgATa4gCAADjUgA==
Date: Thu, 11 Aug 2016 16:46:19 +0000
Message-ID: <D3D22387.78312%acee@cisco.com>
References: <20160808035016.6B4C1B80C59@rfc-editor.org> <D3CDE054.762DF%acee@cisco.com> <06F6F5EBB94E6043A805319DFE5B3E0B78817B19@ESGSCMB109.ericsson.se>
In-Reply-To: <06F6F5EBB94E6043A805319DFE5B3E0B78817B19@ESGSCMB109.ericsson.se>
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.24.119.225]
Content-Type: text/plain; charset="utf-8"
Content-ID: <AF3EFFCA8B7F9E47829BF621CCD23EF7@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/rKSqFNTr1ByvXKwZAP-ZCgLYzio>
Cc: "ospf@ietf.org" <ospf@ietf.org>
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: Thu, 11 Aug 2016 16:46:51 -0000
Hi Chao, On 8/11/16, 5:22 AM, "Chao Fu" <chao.fu@ericsson.com> wrote: >Hi Acee, > >If my understanding is correct, you said there is the topology that an >ABR receives one NSSA LSA and one ASE LSA with the same destination, cost >and non-zero forwarding address. It is right but when doing external >route calculation, one of it would be rejected according to 2.5.(3): > If the forwarding address is non-zero look up the forwarding > address in the routing table. For a Type-5 LSA the matching > routing table entry must specify an intra-area or inter-area > path through a Type-5 capable area. For a Type-7 LSA the > matching routing table entry must specify an intra-area path > through the LSA's originating NSSA. >Then the path to the forwarding address cannot be through a Type-5 >capable area and an NSSA area at the same time, which means one of them >would be ignored here and no chance to match rule (e). With this respect to this reasoning, your understanding is incorrect. If the FA path is via a intra-area NSSA route (which it would be for an NSSA ABR), then it would be pass the reachability test for both the NSSA-LSA and the AS-External LSA. Thanks, Acee > >At the same time, rule (e) is not only defined to check the mixture of >an ASE LSA and an NSSA LSA, and then it is possible to compare two ASE >LSAs or two NSSA LSAs. But the referenced text describes that no such two >NSSA LSAs exist because one of them should be flushed. Consequently, the >condition of rule (e) will never be matched and then it is a redundant >rule. > >If rule (e) is not valid, I guess it is better to record it somewhere, >otherwise some conformance testers always want to verify it, that is the >reason why I would like to report the errata. If my understanding on rule >(e) is wrong, please correct me and I will appreciate it very much. > >Thanks & best Regards, >Chao Fu > >-----Original Message----- >From: Acee Lindem (acee) [mailto:acee@cisco.com] >Sent: Monday, August 08, 2016 19:15 >To: RFC Errata System <rfc-editor@rfc-editor.org>; pmurphy@noc.usgs.net; >akatlas@gmail.com; db3546@att.com; Alvaro Retana (aretana) ><aretana@cisco.com>; Abhay Roy (akr) <akr@cisco.com> >Cc: Chao Fu <chao.fu@ericsson.com>; ospf@ietf.org >Subject: Re: [Technical Errata Reported] RFC3101 (4767) > >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 >> >
- Re: [OSPF] [Technical Errata Reported] RFC3101 (4… Acee Lindem (acee)
- Re: [OSPF] [Technical Errata Reported] RFC3101 (4… Chao Fu
- Re: [OSPF] [Technical Errata Reported] RFC3101 (4… Acee Lindem (acee)
- Re: [OSPF] [Technical Errata Reported] RFC3101 (4… Chao Fu
- Re: [OSPF] [Technical Errata Reported] RFC3101 (4… Acee Lindem (acee)
- Re: [OSPF] [Technical Errata Reported] RFC3101 (4… Acee Lindem (acee)
- [OSPF] [Errata Rejected] RFC3101 (4767) RFC Errata System
- [OSPF] [Technical Errata Reported] RFC3101 (4767) RFC Errata System
- Re: [OSPF] [Technical Errata Reported] RFC3101 (4… Chao Fu