Re: [OSPF] [Technical Errata Reported] RFC2328 (3734)
Abdussalam Baryun <abdussalambaryun@gmail.com> Fri, 27 September 2013 10:39 UTC
Return-Path: <abdussalambaryun@gmail.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 C371D11E813A for <ospf@ietfa.amsl.com>; Fri, 27 Sep 2013 03:39:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level:
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[AWL=0.251, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2YNMijYyhEYg for <ospf@ietfa.amsl.com>; Fri, 27 Sep 2013 03:39:49 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 11FAA21F9FCF for <ospf@ietf.org>; Fri, 27 Sep 2013 03:39:44 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id z10so2436042pdj.31 for <ospf@ietf.org>; Fri, 27 Sep 2013 03:39:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7ushYIMA7HNmQUITiloWRdZRwrsLti0SvstC3ndw8Bc=; b=PsE5LlpMRt9p2ng72DfaFrao0LdPTtUHarMo++YqheWVbuU0r54wQk1EdMK64VPdSO qhSrB2EgDT7vrJIKawVD6a+tRgJLjCA968uHRJk6lSNnkZsZQ6t2fm1SboYQWKZiJpBw I1hFXdpZNPcpjdBCsX28OyqFOGmeWmahAneglq1ADxen9vtft8kjq6aOvf7SZGe6INtr 3E/9Bqw8nA9Vp6TI4ULVZ3aX6QS3SyskU6WiOsUQZ2Jjpnt0I/Q6cskVxqvjrF2DL0Yw 4r3mN6aSvdI+Apk1XCdLtFxwLjhEtV9D43WaXB6C/cApH/pKvNQEE8v6cROzGng1arO/ nJ6A==
MIME-Version: 1.0
X-Received: by 10.68.197.104 with SMTP id it8mr6473700pbc.17.1380278383467; Fri, 27 Sep 2013 03:39:43 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Fri, 27 Sep 2013 03:39:43 -0700 (PDT)
In-Reply-To: <20130924035340.B22B6B1E00B@rfc-editor.org>
References: <20130924035340.B22B6B1E00B@rfc-editor.org>
Date: Fri, 27 Sep 2013 12:39:43 +0200
Message-ID: <CADnDZ88bupfCWL5s9cS2g48-HZvqrC5k1kHJNVGm1PrH1PrSzA@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: OSPF List <ospf@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: jmoy@casc.com
Subject: Re: [OSPF] [Technical Errata Reported] RFC2328 (3734)
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 27 Sep 2013 10:39:50 -0000
I don't think it was an editorial error, it is technical error, AB On 9/24/13, 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=3734 > > -------------------------------------- > Type: Technical > Reported by: Ramakrishna DTV <ramakrishnadtv@infosys.com> > > Section: 8.2 > > Original Text > ------------- > The AuType specified in the packet must match the AuType > specified for the associated area. > > > Corrected Text > -------------- > The AuType specified in the packet must match the AuType > specified for the associated interface. > > > Notes > ----- > In OSPFv2, authentication is configured per interface and not per area. > Appendix D clarifies this: "The authentication type is configurable on a > per-interface > (or equivalently, on a per-network/subnet) basis." > > 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 mailing list > OSPF@ietf.org > https://www.ietf.org/mailman/listinfo/ospf >
- [OSPF] [Technical Errata Reported] RFC2328 (3734) RFC Errata System
- Re: [OSPF] [Technical Errata Reported] RFC2328 (3… Acee Lindem
- Re: [OSPF] [Technical Errata Reported] RFC2328 (3… Abdussalam Baryun
- Re: [OSPF] [Technical Errata Reported] RFC2328 (3… Acee Lindem