Re: [OSPF] [Technical Errata Reported] RFC6987 (4685)

Alexander Okonnikov <alexander.okonnikov@gmail.com> Fri, 06 May 2016 01:48 UTC

Date: Fri, 06 May 2016 04:48:10 +0300
From: Alexander Okonnikov <alexander.okonnikov@gmail.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>, "Alvaro Retana (aretana)" <aretana@cisco.com>, "Liem Nguyen (lhnguyen)" <lhnguyen@cisco.com>, "alex.zinin@gmail.com" <alex.zinin@gmail.com>, "Russ.White@vce.com" <Russ.White@vce.com>, "dmcpherson@verisign.com" <dmcpherson@verisign.com>, "akatlas@gmail.com" <akatlas@gmail.com>, "db3546@att.com" <db3546@att.com>, "Abhay Roy (akr)" <akr@cisco.com>, "Acee Lindem (acee)" <acee@cisco.com>
Message-ID: <d78754d0-2b77-40f6-9816-14cfe8938b78@Spark>
In-Reply-To: <D3516B9E.5FFDD%acee@cisco.com>
References: <20160506001711.5545D180003@rfc-editor.org> <D3516B9E.5FFDD%acee@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="572bf7f0_327b23c6_ca"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/sE0Iqk9EbVSaa_fUw2Qgm9XPd6g>
Cc: "ospf@ietf.org" <ospf@ietf.org>
Subject: Re: [OSPF] [Technical Errata Reported] RFC6987 (4685)
Precedence: list

Hello Acee,

Yes, it is addition, but I have no idea about another way how to add this clarification rather than via errata tool.

Thank you.


6 мая 2016 г., 4:40 +0300, Acee Lindem (acee)<acee@cisco.com>, писал:
> The text below is technically correct (other than the grammar). However,
> I’d view it more as additional information than an actual errata.
>  
> Thanks,
> Acee
>  
> On 5/5/16, 8:17 PM, "RFC Errata System"<rfc-editor@rfc-editor.org>wrote:
>  
> > The following errata report has been submitted for RFC6987,
> > "OSPF Stub Router Advertisement".
> >  
> > --------------------------------------
> > You may review the report below and at:
> > http://www.rfc-editor.org/errata_search.php?rfc=6987&eid=4685
> >  
> > --------------------------------------
> > Type: Technical
> > Reported by: Alexander Okonnikov<alexander.okonnikov@gmail.com
> >  
> > Section: 4
> >  
> > Original Text
> > -------------
> >  
> >  
> > Corrected Text
> > --------------
> > (At the end of the section)
> >  
> > If the stub router is located in transit area, crossed by virtual
> > link(s), latter will become inoperational in case the stub router is
> > on path between two virtual link endpoints - either due to only path
> > in transit area or due to topology changes which move stub router onto
> > this path.
> >  
> > Notes
> > -----
> > Virtual links become inoperational in case path metric between two
> > endpoints is>0xffff. Path metric of two or more links, one of which has
> > MaxLinkMetric, will inevitably exceed value 0xffff.
> >  
> > 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.
> >  
> > --------------------------------------
> > RFC6987 (draft-ietf-ospf-rfc3137bis-04)
> > --------------------------------------
> > Title : OSPF Stub Router Advertisement
> > Publication Date : September 2013
> > Author(s) : A. Retana, L. Nguyen, A. Zinin, R. White, D.
> > McPherson
> > Category : INFORMATIONAL
> > Source : Open Shortest Path First IGP
> > Area : Routing
> > Stream : IETF
> > Verifying Party : IESG
> >  
>

[OSPF] [Errata Rejected] RFC6987 (4685) RFC Errata System
[OSPF] [Technical Errata Reported] RFC6987 (4685) RFC Errata System
Re: [OSPF] [Technical Errata Reported] RFC6987 (4… Acee Lindem (acee)
Re: [OSPF] [Technical Errata Reported] RFC6987 (4… Alexander Okonnikov
Re: [OSPF] [Technical Errata Reported] RFC6987 (4… Acee Lindem (acee)