Re: [OSPF] [Technical Errata Reported] RFC2328 (4022)
Acee Lindem <acee.lindem@ericsson.com> Tue, 24 June 2014 20:23 UTC
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D166B1B27DE for <ospf@ietfa.amsl.com>; Tue, 24 Jun 2014 13:23:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 AVMRbJmZWevJ for <ospf@ietfa.amsl.com>; Tue, 24 Jun 2014 13:23:28 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 641A11B27E4 for <ospf@ietf.org>; Tue, 24 Jun 2014 13:23:27 -0700 (PDT)
X-AuditID: c6180641-f79df6d000002de0-3d-53a98a4b9f4b
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id D2.DA.11744.B4A89A35; Tue, 24 Jun 2014 16:25:16 +0200 (CEST)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0174.001; Tue, 24 Jun 2014 16:23:18 -0400
From: Acee Lindem <acee.lindem@ericsson.com>
To: RFC Editor <rfc-editor@rfc-editor.org>
Thread-Topic: [Technical Errata Reported] RFC2328 (4022)
Thread-Index: AQHPj3u1QlnJECDid0mXvnC7YugMCJuA+FYA
Date: Tue, 24 Jun 2014 20:23:17 +0000
Message-ID: <FCB8C036-5D41-4D9D-8457-2DAAD8CBD741@ericsson.com>
References: <20140624071113.B6A8918001B@rfc-editor.org>
In-Reply-To: <20140624071113.B6A8918001B@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6BE9684503EF3E4E9FB1EEFBA0FE2615@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMIsWRmVeSWpSXmKPExsUyuXRPgq5P18pgg00rWS1+9Nxgtvj08BKz xeGDs9gser/HWEycK2PRcu8eu0XT/q9sDuwe/1ZvY/aY8nsjq8fOWXfZPZYs+cnksWLzSkaP hrZjrAFsUVw2Kak5mWWpRfp2CVwZ23/MZy7YJV6x9MRdpgbG80JdjJwcEgImErcbH7JB2GIS F+6tB7K5OIQEjjJKTJx0iwXCWc4ocX/+fkaQKjYBHYnnj/4xg9giAloSJ7YfYQWxmQWeM0qc WZ8CYgsLmEu0NvxjgaixkGicdIoRwjaS2HD4KVgvi4CqxOw3b8FqeAXsJabu+AY0hwNombnE /EVpIGFOoNbrn16xg9iMQMd9P7WGCWKVuMStJ/OZII4WkFiy5zwzhC0q8fLxP1YIW0ni4+/5 7BD1OhILdn9ig7CtJWZNWAwV15ZYtvA1M8QJghInZz5hmcAoPgvJillI2mchaZ+FpH0WkvYF jKyrGDlKi1PLctONDDcxAmP1mASb4w7GBZ8sDzEKcDAq8fAq+KwMFmJNLCuuzD3EKM3BoiTO q1k9L1hIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QDY0fri1kzvxRK+8zraxZ/9684Wf9Pvdeh DuMElxAhjs6CjvAIMc2tltHsbtJ3nu86OslUft7LJRd7z3hab3998cfWNdKyFYJP6kV+q0xr awloauVd8+vbh9cHTe+5Pzrvv19eacr9+O5nDWJvuUoPJk2d5/yCa+rJ4st3trwtt97K1adp b7T1jBJLcUaioRZzUXEiABsfkNy2AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/YjfMuM_N7yeb5BFy7u4lfQzBfUU
Cc: "jmoy@casc.com" <jmoy@casc.com>, "alexander.okonnikov@gmail.com" <alexander.okonnikov@gmail.com>, OSPF List <ospf@ietf.org>
Subject: Re: [OSPF] [Technical Errata Reported] RFC2328 (4022)
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Jun 2014 20:23:31 -0000
Hi Alia, As long as you are verifying these, I agree with Errata as well. Thanks, Acee On Jun 24, 2014, at 3:11 AM, RFC Errata System <rfc-editor@rfc-editor.org> wrote: > The following errata report has been submitted for RFC2328, > "OSPF Version 2". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=2328&eid=4022 > > -------------------------------------- > Type: Technical > Reported by: Alexander Okonnikov <alexander.okonnikov@gmail.com> > > Section: 10.5 > > Original Text > ------------- > When receiving an Hello Packet from a neighbor on a broadcast, > Point-to-MultiPoint or NBMA network, set the neighbor > structure's Neighbor ID equal to the Router ID found in the > packet's OSPF header. For these network types, the neighbor > structure's Router Priority field, Neighbor's Designated Router > field, and Neighbor's Backup Designated Router field are also > set equal to the corresponding fields found in the received > Hello Packet; changes in these fields should be noted for > possible use in the steps below. When receiving an Hello on a > point-to-point network (but not on a virtual link) set the > neighbor structure's Neighbor IP address to the packet's IP > source address. > > Corrected Text > -------------- > When receiving an Hello Packet from a neighbor on a broadcast, > Point-to-MultiPoint or NBMA network, set the neighbor > structure's Neighbor ID equal to the Router ID found in the > packet's OSPF header. For broadcast and NBMA network types, the neighbor > structure's Router Priority field, Neighbor's Designated Router > field, and Neighbor's Backup Designated Router field are also > set equal to the corresponding fields found in the received > Hello Packet; changes in these fields should be noted for > possible use in the steps below. When receiving an Hello on a > point-to-point network (but not on a virtual link) set the > neighbor structure's Neighbor IP address to the packet's IP > source address. > > Notes > ----- > This is unnecessary in case of Point-to-MultiPoint network type to hold neighbor's Router Priority, DR, and BDR values. > > Instructions: > ------------- > This errata 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. > > -------------------------------------- > RFC2328 (no draft string recorded) > -------------------------------------- > Title : OSPF Version 2 > Publication Date : April 1998 > Author(s) : J. Moy > Category : INTERNET STANDARD > Source : Open Shortest Path First IGP > Area : Routing > Stream : IETF > Verifying Party : IESG
- [OSPF] [Technical Errata Reported] RFC2328 (4022) RFC Errata System
- Re: [OSPF] [Technical Errata Reported] RFC2328 (4… Acee Lindem
- Re: [OSPF] [Technical Errata Reported] RFC2328 (4… Alia Atlas
- [OSPF] [Errata Verified] RFC2328 (4022) RFC Errata System