<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>MQX Software SolutionsのトピックRe: NTP packet</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/NTP-packet/m-p/219246#M5695</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Per RFC-4330:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Although setting the Transmit Timestamp field in the request to the&lt;BR /&gt;&amp;nbsp;&amp;nbsp; time of day according to the client clock in NTP timestamp format is&lt;BR /&gt;&amp;nbsp;&amp;nbsp; not necessary in a conforming client implementation, it is highly&lt;BR /&gt;&amp;nbsp;&amp;nbsp; recommended in unicast and manycast modes.&amp;nbsp; This allows a simple&lt;BR /&gt;&amp;nbsp;&amp;nbsp; calculation to determine the propagation delay between the server and&lt;BR /&gt;&amp;nbsp;&amp;nbsp; client and to align the system clock generally within a few tens of&lt;BR /&gt;&amp;nbsp;&amp;nbsp; milliseconds relative to the server.&amp;nbsp; In addition, this provides a&lt;BR /&gt;&amp;nbsp;&amp;nbsp; simple method for verifying that the server reply is in fact a&lt;BR /&gt;&amp;nbsp;&amp;nbsp; legitimate response to the specific client request and thereby for&lt;BR /&gt;&amp;nbsp;&amp;nbsp; avoiding replays.&amp;nbsp; In broadcast mode, the client has no information&lt;BR /&gt;&amp;nbsp;&amp;nbsp; to calculate the propagation delay or to determine the validity of&lt;BR /&gt;&amp;nbsp;&amp;nbsp; the server, unless one of the NTP authentication schemes is used.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; To calculate the roundtrip delay d and system clock offset t relative&lt;BR /&gt;&amp;nbsp;&amp;nbsp; to the server, the client sets the Transmit Timestamp field in the&lt;BR /&gt;&amp;nbsp;&amp;nbsp; request to the time of day according to the client clock in NTP&lt;BR /&gt;&amp;nbsp;&amp;nbsp; timestamp format.&amp;nbsp; For this purpose, the clock need not be&lt;BR /&gt;&amp;nbsp;&amp;nbsp; synchronized.&amp;nbsp; The server copies this field to the Originate&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Timestamp in the reply and sets the Receive Timestamp and Transmit&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Timestamp fields to the time of day according to the server clock in&lt;BR /&gt;&amp;nbsp;&amp;nbsp; NTP timestamp format.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Oct 2009 08:09:12 GMT</pubDate>
    <dc:creator>EAI</dc:creator>
    <dc:date>2009-10-08T08:09:12Z</dc:date>
    <item>
      <title>NTP packet</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/NTP-packet/m-p/219243#M5692</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I need to come up with&amp;nbsp;an implementation&amp;nbsp;of an NTP packet.&amp;nbsp; I was hoping that there was already built in support for this in MQX, but so far I'm coming up empty.&amp;nbsp; I thought I saw in another thread that SNTP is supported, but I can't seem to find any info on it.&lt;/P&gt;&lt;P&gt;Any pointers would be appreciated.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Oct 2009 19:40:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/NTP-packet/m-p/219243#M5692</guid>
      <dc:creator>cbursk</dc:creator>
      <dc:date>2009-10-02T19:40:15Z</dc:date>
    </item>
    <item>
      <title>Re: NTP packet</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/NTP-packet/m-p/219244#M5693</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;MQX implements SNTP client. See MQX RTCS User's guide (MQXRTCSUG.pdf) chapeters 7.1.147 SNTP_oneshot() and 7.1.146 SNTP_init()..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;PetrL&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Oct 2009 20:51:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/NTP-packet/m-p/219244#M5693</guid>
      <dc:creator>PetrL</dc:creator>
      <dc:date>2009-10-05T20:51:13Z</dc:date>
    </item>
    <item>
      <title>Re: NTP packet</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/NTP-packet/m-p/219245#M5694</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your help, its amazing how much easier this becomes when e look in the right spot.&amp;nbsp; I do have a follow up question, in the sntp.c file in the SNTP_build_header method the header is built but the timestamp that gets set is the TRANSMIT_TIMESTAMP1 &amp;amp; 2.&amp;nbsp; I'm confised by this, if the header is being built to be transmitted by a client, shouldn't this be setting the ORIGINATE_TIMESTAMPs?&amp;nbsp; Also I can't seem to find where who fills in the REFERENCE_TIMESTAMPs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Oct 2009 01:24:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/NTP-packet/m-p/219245#M5694</guid>
      <dc:creator>cbursk</dc:creator>
      <dc:date>2009-10-06T01:24:58Z</dc:date>
    </item>
    <item>
      <title>Re: NTP packet</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/NTP-packet/m-p/219246#M5695</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Per RFC-4330:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Although setting the Transmit Timestamp field in the request to the&lt;BR /&gt;&amp;nbsp;&amp;nbsp; time of day according to the client clock in NTP timestamp format is&lt;BR /&gt;&amp;nbsp;&amp;nbsp; not necessary in a conforming client implementation, it is highly&lt;BR /&gt;&amp;nbsp;&amp;nbsp; recommended in unicast and manycast modes.&amp;nbsp; This allows a simple&lt;BR /&gt;&amp;nbsp;&amp;nbsp; calculation to determine the propagation delay between the server and&lt;BR /&gt;&amp;nbsp;&amp;nbsp; client and to align the system clock generally within a few tens of&lt;BR /&gt;&amp;nbsp;&amp;nbsp; milliseconds relative to the server.&amp;nbsp; In addition, this provides a&lt;BR /&gt;&amp;nbsp;&amp;nbsp; simple method for verifying that the server reply is in fact a&lt;BR /&gt;&amp;nbsp;&amp;nbsp; legitimate response to the specific client request and thereby for&lt;BR /&gt;&amp;nbsp;&amp;nbsp; avoiding replays.&amp;nbsp; In broadcast mode, the client has no information&lt;BR /&gt;&amp;nbsp;&amp;nbsp; to calculate the propagation delay or to determine the validity of&lt;BR /&gt;&amp;nbsp;&amp;nbsp; the server, unless one of the NTP authentication schemes is used.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; To calculate the roundtrip delay d and system clock offset t relative&lt;BR /&gt;&amp;nbsp;&amp;nbsp; to the server, the client sets the Transmit Timestamp field in the&lt;BR /&gt;&amp;nbsp;&amp;nbsp; request to the time of day according to the client clock in NTP&lt;BR /&gt;&amp;nbsp;&amp;nbsp; timestamp format.&amp;nbsp; For this purpose, the clock need not be&lt;BR /&gt;&amp;nbsp;&amp;nbsp; synchronized.&amp;nbsp; The server copies this field to the Originate&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Timestamp in the reply and sets the Receive Timestamp and Transmit&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Timestamp fields to the time of day according to the server clock in&lt;BR /&gt;&amp;nbsp;&amp;nbsp; NTP timestamp format.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Oct 2009 08:09:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/NTP-packet/m-p/219246#M5695</guid>
      <dc:creator>EAI</dc:creator>
      <dc:date>2009-10-08T08:09:12Z</dc:date>
    </item>
  </channel>
</rss>

