<div dir="ltr">Hello Srinivasan and Rahul,<div><br></div><div>I the PM for the NTPsec project, and I'm also a fellow HPE employee. I've been working with you guys on your open source governance setup. You can contact me about any currently non-public work about OpenSwitch at <<a href="mailto:mark.atwood@hpe.com">mark.atwood@hpe.com</a>>.</div><div><br></div><div>We have not yet integrated NTPsec with Yocto, but would be willing to do so.</div><div><br></div><div>The NTPsec configuration files and control methods are presently substantially similar to those of the NTF NTP Classic implementation.</div><div><br></div><div>As to your other technical questions, I refer you to our tech lead, Eric Raymond.</div><div><br></div><div>We are extremely willing to work with the OpenSwitch project to make this integration work.</div><div><br></div><div>..m</div><div><br></div><div><br></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Dec 23, 2015 at 1:16 PM Srivatsan, Srinivasan <<a href="mailto:srinivasan.srivatsan@hpe.com">srinivasan.srivatsan@hpe.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi NTPsec team,<br>
<br>
I am Srinivasan and working with the OpenSwitch team at HPE. We are planning to use NTPsec as part of OpenSwitch. For the initial release we are planning to support only NTP client. I have some questions based off that.<br>
<br>
* Would you know if someone has integrated NTPsec into the yocto project with a bitbake recipe (.bb file). If its there then I could use that as reference for my integration with OpenSwitch because it uses Yocto/Bitbake framework.<br>
* Based on what we want to support in the initial release, the interaction with the daemon would include the following: For each of these scenarios, what is the best way to print/configure the info? Can I make a socket/api call to get this info OR is it through a command OR is it through a .conf file change and restarting the daemon?<br>
* Daemon is up and we need to print the current ntp status info,<br>
* Daemon is up and we need to print the NTP associations info,<br>
* Daemon is up, but we need to allow runtime configuration for different NTP servers, along with “prefer” and “version” setting for that NTP server. Can we update the Daemon to pick up this new configuration or do we have to write to the .conf file and then restart the daemon ?<br>
* Daemon is up, the user would provide the key-number and md5 clientpassword. We want to use this configuration for the specific server instead of using autokey. Can a restart of the Daemon be avoided when setting authentication with the ntp client.<br>
* Based on the online material in your website, I have a few questions about the NTPsec support<br>
* Does the Daemon support configuring of Broadcast, Multicast or Manycasting clients.<br>
* Does the Daemon support Ipv6 Configuration ? If so does Daemon support mixed Ipv4 and Ipv6 NTP server configuration ?<br>
<br>
Thanks for supporting NTPsec, looking forward for your response.<br>
<br>
Regards<br>
Srinivasan<br>
<br>
<br>
<br>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@ntpsec.org" target="_blank">devel@ntpsec.org</a><br>
<a href="http://lists.ntpsec.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ntpsec.org/mailman/listinfo/devel</a></blockquote></div></div>