Re: [karp] [Editorial Errata Reported] RFC7210 (4016)

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 18 June 2014 17:46 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: karp@ietfa.amsl.com
Delivered-To: karp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A5181A01E1 for <karp@ietfa.amsl.com>; Wed, 18 Jun 2014 10:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, 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 iJ3hbJ0k5eqP for <karp@ietfa.amsl.com>; Wed, 18 Jun 2014 10:46:51 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 476211A014C for <karp@ietf.org>; Wed, 18 Jun 2014 10:46:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 23A752471FC; Wed, 18 Jun 2014 10:46:51 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from host-78-75-253-21.homerun.telia.com (host-78-75-253-21.homerun.telia.com [78.75.253.21]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 0BA2F2471FB; Wed, 18 Jun 2014 10:46:48 -0700 (PDT)
Message-ID: <53A1D08C.5030109@joelhalpern.com>
Date: Wed, 18 Jun 2014 13:46:52 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: RFC Errata System <rfc-editor@rfc-editor.org>, housley@vigilsec.com, tim.polk@nist.gov, hartmans-ietf@mit.edu, zhangdacheng@huawei.com, akatlas@gmail.com, adrian@olddog.co.uk, bew@cisco.com
References: <20140618095254.A59CB18000E@rfc-editor.org>
In-Reply-To: <20140618095254.A59CB18000E@rfc-editor.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/karp/VzKhTUZJsVkUhTQu9QyszmP-b6A
X-Mailman-Approved-At: Wed, 18 Jun 2014 10:48:34 -0700
Cc: infrastation@yandex.ru, karp@ietf.org
Subject: Re: [karp] [Editorial Errata Reported] RFC7210 (4016)
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion list for key management for routing and transport protocols <karp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/karp>, <mailto:karp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/karp/>
List-Post: <mailto:karp@ietf.org>
List-Help: <mailto:karp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/karp>, <mailto:karp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jun 2014 17:46:53 -0000

He seems to be quite correct.  The HHSS should have been HHMMSS in both 
cases.  The text is clear as to the WG intent.

Yours,
Joel

On 6/18/14, 5:52 AM, RFC Errata System wrote:
> The following errata report has been submitted for RFC7210,
> "Database of Long-Lived Symmetric Cryptographic Keys".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=7210&eid=4016
>
> --------------------------------------
> Type: Editorial
> Reported by: Denis Ovsienko <infrastation@yandex.ru>
>
> Section: 2
>
> Original Text
> -------------
>        SendLifetimeStart
>           The SendLifetimeStart field specifies the earliest date and
>           time in Coordinated Universal Time (UTC) at which this key
>           should be considered for use when sending traffic.  The format
>           is YYYYMMDDHHSSZ, where four digits specify the year, two
>           digits specify the month, two digits specify the day, two
>           digits specify the hour, two digits specify the minute, and two
>           digits specify the second.  The "Z" is included as a clear
>           indication that the time is in UTC.
>
>        SendLifeTimeEnd
>           The SendLifeTimeEnd field specifies the latest date and time at
>           which this key should be considered for use when sending
>           traffic.  The format is the same as the SendLifetimeStart
>           field.
>
>        AcceptLifeTimeStart
>           The AcceptLifeTimeStart field specifies the earliest date and
>           time in Coordinated Universal Time (UTC) at which this key
>           should be considered for use when processing received traffic.
>           The format is YYYYMMDDHHSSZ, where four digits specify the
>           year, two digits specify the month, two digits specify the day,
>           two digits specify the hour, two digits specify the minute, and
>           two digits specify the second.  The "Z" is included as a clear
>           indication that the time is in UTC.
>
>
> Corrected Text
> --------------
>        SendLifetimeStart
>           The SendLifetimeStart field specifies the earliest date and
>           time in Coordinated Universal Time (UTC) at which this key
>           should be considered for use when sending traffic.  The format
>           is YYYYmmddHHMMSSZ, where four digits specify the year, two
>           digits specify the month, two digits specify the day, two
>           digits specify the hour, two digits specify the minute, and two
>           digits specify the second.  The "Z" is included as a clear
>           indication that the time is in UTC.
>
>        SendLifeTimeEnd
>           The SendLifeTimeEnd field specifies the latest date and time at
>           which this key should be considered for use when sending
>           traffic.  The format is the same as the SendLifetimeStart
>           field.
>
>        AcceptLifeTimeStart
>           The AcceptLifeTimeStart field specifies the earliest date and
>           time in Coordinated Universal Time (UTC) at which this key
>           should be considered for use when processing received traffic.
>           The format is YYYYmmddHHMMSSZ, where four digits specify the
>           year, two digits specify the month, two digits specify the day,
>           two digits specify the hour, two digits specify the minute, and
>           two digits specify the second.  The "Z" is included as a clear
>           indication that the time is in UTC.
>
>
> Notes
> -----
> The date and time format in the original document omits minute.
>
> 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.
>
> --------------------------------------
> RFC7210 (draft-ietf-karp-crypto-key-table-10)
> --------------------------------------
> Title               : Database of Long-Lived Symmetric Cryptographic Keys
> Publication Date    : April 2014
> Author(s)           : R. Housley, T. Polk, S. Hartman, D. Zhang
> Category            : PROPOSED STANDARD
> Source              : Keying and Authentication for Routing Protocols
> Area                : Routing
> Stream              : IETF
> Verifying Party     : IESG
>