Re: [Ntp] Last Call: <draft-ietf-6lo-deadline-time-03.txt> (Packet Delivery Deadline time in 6LoWPAN Routing Header) to Proposed Standard
Charlie Perkins <charles.perkins@earthlink.net> Sat, 09 February 2019 02:25 UTC
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E72A128B14; Fri, 8 Feb 2019 18:25:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
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 gMfQgZq3QuQM; Fri, 8 Feb 2019 18:25:23 -0800 (PST)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5903912894E; Fri, 8 Feb 2019 18:25:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1549679123; bh=aJmddUdSVMJa/M0rcx4kBOl9BuMIB0/vDN+n kZ+SW/g=; h=Received:Subject:To:Cc:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language: X-ELNK-Trace:X-Originating-IP; b=Fm0GQtcLY4uCnsEP2ijUfDD5x+CC1M4Zf cgQ0TWnU6CWHwffWBw12ZkkTXmMgbwbODyBTRcF6CGCk3GZfctKmpi2DPLU3EQV9vz/ COzeVEu7ECcb3/PyM6V9lSLB8mD4B2eC3JJllGJbwRH+pkZzH1bgz6otYwsMeZ0+rYn Hh+bnOtk4sxN6rre4UumMi0Ixk4r+ESIVOF3p0R7x59RE4H7MALGz5fGsehUjm9xbS+ QeFSmzupjSfKZVSSgh757IHt/y4PRa/bhEU09gJAeYjag2FuFj2rTB8smmopVXCSGI4 xS6p3gTOKCuE20pag/cqQr5f2LTjc80o7IqxRbNxw==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=d2ZQJRE6s1oGcFIDCA2HLyyPW3P7qWjMroq6RHCt+duY6QCRRe2OYarD7zHHqpokaI5Cmxkfx464ImoEmkOe2jq4kqvf3EYX122Ko75SLWBOjQqMlJ16GryIY9eAFfPeXhpffGsxC+R7WeVWc5eFXPpbavFm2809wo3ZbfGjCMDFbdaeTIX2BTYDQVkrqUe554QkVn4se5l8vuC8tSCmSQN0GBXKsi/GK09r+xrhzDNX3l9hBIhX73RQEPcEJnfNOUdSUqlXABVjOOEdGMzykuW+W1MM5EbWwNBv7f22uSDwLp7aCrubJNHtpketzmmprlXeifpKDGj6NgyfyyD/4Q==; h=Received:Subject:To:Cc:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4) (envelope-from <charles.perkins@earthlink.net>) id 1gsIKX-0008sK-DN; Fri, 08 Feb 2019 21:25:21 -0500
To: Tal Mizrahi <tal.mizrahi.phd@gmail.com>
Cc: Suresh Krishnan <Suresh@kaloom.com>, "draft-ietf-6lo-deadline-time@ietf.org" <draft-ietf-6lo-deadline-time@ietf.org>, "6lo-chairs@ietf.org" <6lo-chairs@ietf.org>, IETF <ietf@ietf.org>, "ntp@ietf.org" <ntp@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>, "ntp-chairs@ietf.org" <ntp-chairs@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
References: <154444480037.17333.5127536482994262799.idtracker@ietfa.amsl.com> <CABUE3XnQSi9rJnN2pxp2ZmmMAF4-aTgZ3eFeuWgj7uDWkZDoHw@mail.gmail.com> <0277B06D-060A-44AB-BA7A-C02F3C6E5021@kaloom.com> <CABUE3XmL_XERozG96bCboxwsbSFWjxvbwyupvs+CjvFA8eR59Q@mail.gmail.com>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <22cec0be-76df-9fed-45d9-48769d662506@earthlink.net>
Date: Fri, 08 Feb 2019 18:25:18 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <CABUE3XmL_XERozG96bCboxwsbSFWjxvbwyupvs+CjvFA8eR59Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------AE9B87FC4709576E0BA12825"
Content-Language: en-US
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956846b590522b13c95b36ddadf380120e6869530b2fa681aa7350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/c4NzUZ2CxZNoSWiJMHyj8wSB3UE>
X-Mailman-Approved-At: Mon, 11 Feb 2019 07:06:49 -0800
Subject: Re: [Ntp] Last Call: <draft-ietf-6lo-deadline-time-03.txt> (Packet Delivery Deadline time in 6LoWPAN Routing Header) to Proposed Standard
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2019 02:25:27 -0000
Hello Tal and all, I have read draft-ietf-ntp-packet-timestamps-05.txt. This is an excellent document. Our previous timestamp format in draft-ietf-6lo-deadline-time-03.txt offers a lot of flexibility in a compact format, but maybe that much flexibility is not needed. I would like to suggest that we use the timestamp template in draft-ietf-ntp-packet-timestamps-05.txt, but with possibly fewer bits than the 32-bit NTP format. As I understand it, that format divides the available number of bits evenly between integral seconds and fractional seconds. So, for instance, if we had an 8-bit timestamp format, that would allow for 16 seconds total duration denominated in sixteenths of a second (i.e., time units of about 64 milliseconds). That would be pretty good for most purposes. If we had a 12-bit timestamp format, that would allow for 64 seconds denominated in units of approximately 16 milliseconds. If the optional Origination Time is included, then we would mandate that the OT has the same time unit as the DT. In this case, that translates to meaning that the number of bits for fractional seconds is the same, but we could allow the OT to have fewer bits for the integer number of seconds. If we go this way with predefined time designations according to the NTP draft format, we don't need the Exp field. It is also possible that an asymmetric number of bits would be considered to satisfy the specified NTP-related format (i.e., not the same number of bits for fractional seconds as for integer seconds). In that case, we could use a new field to locate the binary point. We can make the definitions so that this new information still fits within the space of the Deadline-6LoRHE format. One could argue that this new field is analogous to the Exp field. draft-ietf-ntp-packet-timestamps-05.txt mandates certain details in the Security Considerations which we will need to obey. It also suggests inclusion of material about synchronization. I think we also have to do consider doing that. What do you think? Regards, Charlie P. On 1/3/2019 5:02 AM, Tal Mizrahi wrote: > Hi Suresh, authors, > > >> I would suggest to follow the timestamp specification template of > Section > >> 3 in draft-ietf-ntp-packet-timestamps-05. > > >I think the semantics of the DT and OT fields are a bit different > from the > >NTP packet timestamps and there are also resource constraints in the > >6lo world that might make the 64 bit formats expensive. I will let the > >authors and the WG comment further on this. > > > I agree that the NTP timestamp format does not fit here. > My comment was that DT and OT should be defined according to the > timestamp specification template (section 3 in the packet timestamp > draft). > This is a *generic template* for defining all kinds of timestamp formats. > The template was defined in order to make sure that when you define a > timestamp format you do not forget important details. > Just to clarify, I am not suggesting to change the timestamp formats > of DT and OT, but only to specify them in a clear and unambiguous manner. > > Thanks, > Tal. > > > > > On Wed, Jan 2, 2019 at 11:00 PM Suresh Krishnan <Suresh@kaloom.com > <mailto:Suresh@kaloom.com>> wrote: > > Hi Tal, > >> On Dec 23, 2018, at 3:49 AM, Tal Mizrahi >> <tal.mizrahi.phd@gmail.com <mailto:tal.mizrahi.phd@gmail.com>> wrote: >> >> Hi, >> >> I am not a 6lo native, but I reviewed the draft specifically from >> a timestamp formatting perspective. >> In the NTP working group we currently have a draft in WGLC that >> presents guidelines for defining timestamp formats. >> https://tools.ietf.org/html/draft-ietf-ntp-packet-timestamps-05 >> >> I believe that the definitions of the timestamps (DT and OT) >> in draft-ietf-6lo-deadline-time should be more detailed. For >> example, aspects about the epoch and the potential effect of leap >> seconds are currently not described in the current draft. > > Good point. Authors, can you add some further descriptive text > around these fields. > >> I would suggest to follow the timestamp specification template of >> Section 3 in draft-ietf-ntp-packet-timestamps-05. > > I think the semantics of the DT and OT fields are a bit different > from the NTP packet timestamps and there are also resource > constraints in the 6lo world that might make the 64 bit formats > expensive. I will let the authors and the WG comment further on this. > > Thanks > Suresh >
- Re: [Ntp] Last Call: <draft-ietf-6lo-deadline-tim… Tal Mizrahi
- Re: [Ntp] Last Call: <draft-ietf-6lo-deadline-tim… Tal Mizrahi
- Re: [Ntp] Last Call: <draft-ietf-6lo-deadline-tim… Suresh Krishnan
- Re: [Ntp] [6lo] Last Call: <draft-ietf-6lo-deadli… Lijo Thomas
- Re: [Ntp] Last Call: <draft-ietf-6lo-deadline-tim… Tal Mizrahi
- Re: [Ntp] Last Call: <draft-ietf-6lo-deadline-tim… Charlie Perkins
- Re: [Ntp] Last Call: <draft-ietf-6lo-deadline-tim… MORTON, ALFRED C (AL)
- Re: [Ntp] [6lo] Last Call: <draft-ietf-6lo-deadli… Charlie Perkins
- Re: [Ntp] [6lo] Last Call: <draft-ietf-6lo-deadli… Tal Mizrahi