Re: [OSPF] [Technical Errata Reported] RFC6506 (3567)

t.petch <ietfc@btconnect.com> Fri, 29 March 2013 21:15 UTC

Return-Path: <ietfc@btconnect.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 111B221F9025 for <ospf@ietfa.amsl.com>; Fri, 29 Mar 2013 14:15:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 hsSthHHa-ivv for <ospf@ietfa.amsl.com>; Fri, 29 Mar 2013 14:15:02 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe005.messaging.microsoft.com [65.55.88.15]) by ietfa.amsl.com (Postfix) with ESMTP id B5F1E21F9023 for <ospf@ietf.org>; Fri, 29 Mar 2013 14:15:02 -0700 (PDT)
Received: from mail184-tx2-R.bigfish.com (10.9.14.245) by TX2EHSOBE006.bigfish.com (10.9.40.26) with Microsoft SMTP Server id 14.1.225.23; Fri, 29 Mar 2013 21:15:01 +0000
Received: from mail184-tx2 (localhost [127.0.0.1]) by mail184-tx2-R.bigfish.com (Postfix) with ESMTP id A7F97220179; Fri, 29 Mar 2013 21:15:01 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.254.197; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0711HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -19
X-BigFish: PS-19(zz9371I542I1432Izz1f42h1fc6h1ee6h1de0h1202h1e76h1d1ah1d2ahzz1033IL17326ah19a27bh172cdfh8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah304l1155h)
Received: from mail184-tx2 (localhost.localdomain [127.0.0.1]) by mail184-tx2 (MessageSwitch) id 1364591700357098_8908; Fri, 29 Mar 2013 21:15:00 +0000 (UTC)
Received: from TX2EHSMHS027.bigfish.com (unknown [10.9.14.250]) by mail184-tx2.bigfish.com (Postfix) with ESMTP id 438F7340084; Fri, 29 Mar 2013 21:15:00 +0000 (UTC)
Received: from DB3PRD0711HT003.eurprd07.prod.outlook.com (157.56.254.197) by TX2EHSMHS027.bigfish.com (10.9.99.127) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 29 Mar 2013 21:14:59 +0000
Received: from AMXPRD0310HT001.eurprd03.prod.outlook.com (157.56.248.133) by pod51017.outlook.com (10.255.183.36) with Microsoft SMTP Server (TLS) id 14.16.263.1; Fri, 29 Mar 2013 21:14:57 +0000
Message-ID: <018b01ce2cc1$dd8defa0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: manav.bhatia@alcatel-lucent.com, vishwas.manral@hp.com, acee.lindem@ericsson.com
References: <20130327123752.EFE2DB1E002@rfc-editor.org>
Date: Fri, 29 Mar 2013 21:10:28 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.248.133]
X-OriginatorOrg: btconnect.com
Cc: ospf@ietf.org
Subject: Re: [OSPF] [Technical Errata Reported] RFC6506 (3567)
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, 29 Mar 2013 21:15:07 -0000

Looks like a functional change to me.

Tom Petch

----- Original Message -----
From: "RFC Errata System" <rfc-editor@rfc-editor.org>
To: <manav.bhatia@alcatel-lucent.com>; <vishwas.manral@hp.com>;
<acee.lindem@ericsson.com>; <stbryant@cisco.com>; <adrian@olddog.co.uk>;
<akr@cisco.com>; <acee.lindem@ericsson.com>
Cc: <ospf@ietf.org>; <rfc-editor@rfc-editor.org>
Sent: Wednesday, March 27, 2013 12:37 PM

> The following errata report has been submitted for RFC6506,
> "Supporting Authentication Trailer for OSPFv3".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=6506&eid=3567
>
> --------------------------------------
> Type: Technical
> Reported by: Marek Karasek <mkarasek@cisco.com>
>
> Section: 2.2
>
> Original Text
> -------------
>    Consistent with OSPFv2 Cryptographic Authentication [RFC2328], both
>    OSPFv3 header checksum calculation and verification are omitted
when
>    the OSPFv3 authentication mechanism described in this specification
>    is used.
>
>
> Corrected Text
> --------------
> OSPFv3 authentication mechanism provides capability to detect
corruption of
> OSPFv3 packet, which is under non authenticated operation achieved
using OSPFv3
> header checksum [RFC 5340] and LLS data block checksum [RFC 5613]. In
spirit of
> OSPFv2 Cryptographic Authentication [RFC2328], OSPFv3 header checksum
and LLS
> Data Block Checksum calculation and verification are omitted when the
OSPFv3
> authentication mechanism described in this specification is used.
>
> Notes
> -----
> RFC does not specify how to work with LLS Data Block Checksum. Errata
suggests omit checksum calculation/verification in the same way like for
OSPFv3 header checksum.
>
> 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.
>
> --------------------------------------
> RFC6506 (draft-ietf-ospf-auth-trailer-ospfv3-11)
> --------------------------------------
> Title               : Supporting Authentication Trailer for OSPFv3
> Publication Date    : February 2012
> Author(s)           : M. Bhatia, V. Manral, A. Lindem
> Category            : PROPOSED STANDARD
> Source              : Open Shortest Path First IGP
> Area                : Routing
> Stream              : IETF
> Verifying Party     : IESG
>