# Using Canada NTP pool for possible commercial product **URL:** \ **Category:** Pool Development\ **Created:** [February 16, 2018, 2:52pm UTC](https://community.ntppool.org/t/using-canada-ntp-pool-for-possible-commercial-product/731 "2018-02-16T14:52:51Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![unknowncoder](https://avatars.discourse-cdn.com/v4/letter/u/94ad74/32.png) [@unknowncoder](https://community.ntppool.org/u/unknowncoder)\ **Post date:** [February 16, 2018, 2:52pm UTC](https://community.ntppool.org/t/using-canada-ntp-pool-for-possible-commercial-product/731/1 "2018-02-16T14:52:51Z")
Hello, We are currently a small organisation working on a new IoT product which runs bare metal. We require NTP services. Is there any legal action against using the [0.ca.pool.ntp.org](http://www.pool.ntp.org/zone/ca) pool. Our product on initial release will be about ~500. Thanks ---
**Author:** ![Hedberg](https://avatars.discourse-cdn.com/v4/letter/h/e95f7d/32.png) [@Hedberg](https://community.ntppool.org/u/Hedberg)\ **Post date:** [February 16, 2018, 7:04pm UTC](https://community.ntppool.org/t/using-canada-ntp-pool-for-possible-commercial-product/731/2 "2018-02-16T19:04:24Z")
As a minimum you need to apply for a vendor zone. You can read more about it here: [http://www.pool.ntp.org/en/vendors.html](http://www.pool.ntp.org/en/vendors.html) ---
**Author:** ![unknowncoder](https://avatars.discourse-cdn.com/v4/letter/u/94ad74/32.png) [@unknowncoder](https://community.ntppool.org/u/unknowncoder)\ **Post date:** [February 16, 2018, 8:15pm UTC](https://community.ntppool.org/t/using-canada-ntp-pool-for-possible-commercial-product/731/3 "2018-02-16T20:15:13Z")
Hello, We are using the AWS IoT service only and we know amazon has a registered NTP pool could we use those without any problems? ---
**Author:** ![Hedberg](https://avatars.discourse-cdn.com/v4/letter/h/e95f7d/32.png) [@Hedberg](https://community.ntppool.org/u/Hedberg)\ **Post date:** [February 16, 2018, 9:06pm UTC](https://community.ntppool.org/t/using-canada-ntp-pool-for-possible-commercial-product/731/4 "2018-02-16T21:06:47Z")
I don’t think so. As I read the rules you need your own zone. ---
**Author:** ![avij](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/avij/32/197_2.png) [@avij](https://community.ntppool.org/u/avij)\ **Post date:** [February 16, 2018, 9:56pm UTC](https://community.ntppool.org/t/using-canada-ntp-pool-for-possible-commercial-product/731/5 "2018-02-16T21:56:30Z")
I don’t know about your IoT product, but many such IoT products are never updated after they have been deployed, and fixing bugs in those might be problematic. If it turns out that your NTP implementation has a bug (for example if it starts sending requests endlessly when it encounters a leap second), having a vendor zone would help in controlling the damage. I would heartily recommend getting a vendor zone. If this is not an option for you, you could always run your own NTP servers and point the devices to those. Theoretically [you could also use the NTP servers specified by the clients’ ISP](https://community.ntppool.org/t/world-wide-pool-traffic-volume/717/2?u=avij) but unfortunately very few ISPs provide that information. One can hope that this will change some day. ---
**Author:** ![unknowncoder](https://avatars.discourse-cdn.com/v4/letter/u/94ad74/32.png) [@unknowncoder](https://community.ntppool.org/u/unknowncoder)\ **Post date:** [February 16, 2018, 11:09pm UTC](https://community.ntppool.org/t/using-canada-ntp-pool-for-possible-commercial-product/731/6 "2018-02-16T23:09:43Z")
The product will support OTA. Using a propriety boot loader. Thus we can always update the firmware. ---
**Author:** ![Hedberg](https://avatars.discourse-cdn.com/v4/letter/h/e95f7d/32.png) [@Hedberg](https://community.ntppool.org/u/Hedberg)\ **Post date:** [February 17, 2018, 1:07pm UTC](https://community.ntppool.org/t/using-canada-ntp-pool-for-possible-commercial-product/731/7 "2018-02-17T13:07:36Z")
It doesnt really change anything. Apply for a vendor zone (seems pretty simple) and read all the recommendations about how often your product should ask for time (so we do not have a situation like the one TPLink caused rescently).