Re: [MSEC] [Technical Errata Reported] RFC3830 (4638)

Karl Norrman <karl.norrman@ericsson.com> Tue, 15 March 2016 12:25 UTC

Return-Path: <karl.norrman@ericsson.com>
X-Original-To: msec@ietfa.amsl.com
Delivered-To: msec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E95912D9D3 for <msec@ietfa.amsl.com>; Tue, 15 Mar 2016 05:25:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 BXw7cw4rmnoY for <msec@ietfa.amsl.com>; Tue, 15 Mar 2016 05:25:35 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D592512D9CD for <msec@ietf.org>; Tue, 15 Mar 2016 05:25:29 -0700 (PDT)
X-AuditID: c1b4fb30-f79246d00000788a-00-56e7ff384b46
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 64.B5.30858.83FF7E65; Tue, 15 Mar 2016 13:25:28 +0100 (CET)
Received: from ESESSMB203.ericsson.se ([169.254.3.8]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0248.002; Tue, 15 Mar 2016 13:25:27 +0100
From: Karl Norrman <karl.norrman@ericsson.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>, Jari Arkko <jari.arkko@ericsson.com>, "elisabetta.carrara@ericsson.com" <elisabetta.carrara@ericsson.com>, Fredrik Lindholm <fredrik.lindholm@ericsson.com>, =?iso-8859-1?Q?Mats_N=E4slund?= <mats.naslund@ericsson.com>, "stephen.farrell@cs.tcd.ie" <stephen.farrell@cs.tcd.ie>, "Kathleen.Moriarty.ietf@gmail.com" <Kathleen.Moriarty.ietf@gmail.com>, "bew@cisco.com" <bew@cisco.com>, "vincent.roca@inria.fr" <vincent.roca@inria.fr>
Thread-Topic: [Technical Errata Reported] RFC3830 (4638)
Thread-Index: AQHRfquB6iz30Q5T/U2NmR9MQLQiyJ9aaptA
Date: Tue, 15 Mar 2016 12:25:26 +0000
Message-ID: <33E51946CDE71249AF9D86CE4D8966B428B846E7@ESESSMB203.ericsson.se>
References: <20160315111128.0D18E18019D@rfc-editor.org>
In-Reply-To: <20160315111128.0D18E18019D@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrBIsWRmVeSWpSXmKPExsUyM2K7sa7F/+dhBkt28Vn0vW1kteiaPpvF omFnvsWZFweZLJr2f2WzmL73GrtFz6p+Fgd2j5mL9zJ5TPm9kdVjbfdVNo+ds+6yeyxZ8pPJ Y9KLQyweDW3HWAPYo7hsUlJzMstSi/TtErgyHm+cwFjwWLLiVNcdpgbGlSJdjJwcEgImEs/n rWeHsMUkLtxbz9bFyMUhJHCYUeL/2V/sEM4iRolVrx+DVbEJ6Elcu/kcLCEi8JpZ4uKBf4wg CWaBNInW/3fBioQFzCWu3O1kAbFFBCwk1iz+zdrFyA5kG0nscgWJsgioSiw/uR+ogoODV8BX ouGZL0hYCKixd/U/sCGcQI0ta/rAhjAC3fb91BomiEXiEreezGeCuFlAYsme88wQtqjEy8f/ WCFsJYkfGy6xQNTrSdyYOoUNwtaWWLbwNVg9r4CgxMmZT1gmMIrNQjJ2FpKWWUhaZiFpWcDI sopRtDi1OCk33chIL7UoM7m4OD9PLy+1ZBMjMD4PbvltsIPx5XPHQ4wCHIxKPLwFTs/DhFgT y4orcw8xSnAwK4nwRv8DCvGmJFZWpRblxxeV5qQWH2KU5mBREudl/XQ5TEggPbEkNTs1tSC1 CCbLxMEp1cAYrK0hq2clFDHr3cKpJlu2rLo6UW7S33IHga91qZnPHqvVZl3y+5967Yv2ZNcV Sk0xSYvPz3Lp8LDg//G7ynayrGWf0yMxFcFWDb498jrt4RHuq30jc6KvT5YosVI5fET/xomP gb93yL+KvCT6doHS7rBEr9SjLjkfIzIPdIQ99LNR9zaVT1JiKc5INNRiLipOBACy4qdiywIA AA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/msec/XNzaA0NKB65zpNQXHb7eFwYiqbU>
X-Mailman-Approved-At: Tue, 15 Mar 2016 08:32:57 -0700
Cc: "chris.dearlove@baesystems.com" <chris.dearlove@baesystems.com>, "msec@ietf.org" <msec@ietf.org>
Subject: Re: [MSEC] [Technical Errata Reported] RFC3830 (4638)
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/msec>, <mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/msec/>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>, <mailto:msec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2016 12:25:38 -0000

Hello!

My understanding is that the 64-bit timestamp of NTP consists of a 32-bit part giving the number of seconds and another 32-bit part giving fractions of seconds.  That is, even though the timestamp itself is 64 bits, only 32 of those bits represent full seconds. So, I believe the original text is correct.

However, I agree that the formulation after "i.e." is a bit misleading. Read in isolation, it does give the impression that all the 64 bits are used to represent seconds. But given that the sentence start with  "The timestamp is as defined in NTP [NTP], i.e., ...",  I believe it is clear that it is the encoding defined in RFC 1305 that is intended.

BR
Karl

> -----Original Message-----
> From: RFC Errata System [mailto:rfc-editor@rfc-editor.org]
> Sent: den 15 mars 2016 12:11
> To: Jari Arkko; elisabetta.carrara@ericsson.com; Fredrik Lindholm; Mats
> Näslund; Karl Norrman; stephen.farrell@cs.tcd.ie;
> Kathleen.Moriarty.ietf@gmail.com; bew@cisco.com; vincent.roca@inria.fr
> Cc: chris.dearlove@baesystems.com; msec@ietf.org; rfc-editor@rfc-
> editor.org
> Subject: [Technical Errata Reported] RFC3830 (4638)
> 
> The following errata report has been submitted for RFC3830,
> "MIKEY: Multimedia Internet KEYing".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3830&eid=4638
> 
> --------------------------------------
> Type: Technical
> Reported by: Christopher Dearlove <chris.dearlove@baesystems.com>;
> 
> Section: 4.2.8
> 
> Original Text
> -------------
>    The timestamp is as defined in NTP [NTP], i.e., a 64-bit number in
>    seconds relative to 0h on 1 January 1900.  An implementation MUST be
>    aware of (and take into account) the fact that the counter will
>    overflow approximately every 136th year.  It is RECOMMENDED that the
>    time always be specified in UTC.
> 
> 
> Corrected Text
> --------------
>    The timestamp is as defined in NTP [NTP], i.e., a 64-bit number in
>    seconds relative to 0h on 1 January 1900.  It is RECOMMENDED that the
>    time always be specified in UTC.
> 
> 
> Notes
> -----
> A 32-bt number of seconds overflows in about 136.1 years. A 64-bit number
> of seconds will, for all practical purposes, not overflow.
> 
> (The use in Section 4.2.3 is of a 64 bit number, not a 32 bit number, so 64 bits
> is correct.)
> 
> 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.
> 
> --------------------------------------
> RFC3830 (draft-ietf-msec-mikey-08)
> --------------------------------------
> Title               : MIKEY: Multimedia Internet KEYing
> Publication Date    : August 2004
> Author(s)           : J. Arkko, E. Carrara, F. Lindholm, M. Naslund, K. Norrman
> Category            : PROPOSED STANDARD
> Source              : Multicast Security
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG