Re: [Ntp] [6lo] Last Call: <draft-ietf-6lo-deadline-time-03.txt> (Packet Delivery Deadline time in 6LoWPAN Routing Header) to Proposed Standard

["Lijo Thomas" <[e-mail]>]

Hi Tal,

Thanks for your comments.

The scope of our deadline-time draft is confined to a resource constrained 6lo network and hence specifies the DT/OT time representation that is suited for such networks.

The draft specifies an encoding method for expressing the deadline time of a packet for its transmission over a resource constrained 6lo network. So really, the interpretation of Time Unit is scoped to the underlying network technology and the definition(s) of time it provides as specified by the underlying network. So we feel the <draft-ietf-ntp-packet-timestamps-05> won’t be applicable to our case.

For providing more clarity as indicated by Suresh Krishnan too, we will add appropriate text in the next revision.

 

Happy to receive further comments if any;


Thanks & Regards,

Lijo Thomas 

 <https://www.codetwo.com/> 

 

From: 6lo <[e-mail]> On Behalf Of Tal Mizrahi
Sent: 23 December 2018 14:20
To: [e-mail]
Cc: [e-mail]; [e-mail]; Samita Chakrabarti <[e-mail]>; [e-mail]; [e-mail]; [e-mail]; [e-mail]; IETF-Announce <[e-mail]>
Subject: Re: [6lo] Last Call: <draft-ietf-6lo-deadline-time-03.txt> (Packet Delivery Deadline time in 6LoWPAN Routing Header) to Proposed Standard

 

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. 

I would suggest to follow the timestamp specification template of Section 3 in draft-ietf-ntp-packet-timestamps-05.

 

Thanks,

Tal.

 

 

 

 

 

 

On Mon, Dec 10, 2018 at 2:27 PM The IESG <[e-mail] <mailto:[e-mail]> > wrote:


The IESG has received a request from the IPv6 over Networks of
Resource-constrained Nodes WG (6lo) to consider the following document: -
'Packet Delivery Deadline time in 6LoWPAN Routing Header'
  <draft-ietf-6lo-deadline-time-03.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
[e-mail] <mailto:[e-mail]>  mailing lists by 2018-12-24. Exceptionally, comments may be
sent to [e-mail] <mailto:[e-mail]>  instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   This document specifies a new type for the 6LoWPAN routing header
   containing the delivery deadline time for data packets.  The deadline
   time enables forwarding and scheduling decisions for time critical
   IoT M2M applications that need deterministic delay guarantees over
   constrained networks and operate within time-synchronized networks.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-6lo-deadline-time/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-6lo-deadline-time/ballot/


No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information: 
    draft-ietf-6tisch-terminology: Terms Used in IPv6 over the TSCH mode of IEEE 802.15.4e (None - IETF stream)





------------------------------------------------------------------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]

This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
------------------------------------------------------------------------------------------------------------