Re: What is Ant's Fit Protocol?

Warren Kumari <warren@kumari.net> Sun, 22 January 2017 19:21 UTC

Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E473129859 for <ietf@ietfa.amsl.com>; Sun, 22 Jan 2017 11:21:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
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 M3fRAX-WQleN for <ietf@ietfa.amsl.com>; Sun, 22 Jan 2017 11:21:39 -0800 (PST)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11CD012985B for <ietf@ietf.org>; Sun, 22 Jan 2017 11:21:39 -0800 (PST)
Received: by mail-qt0-x236.google.com with SMTP id l7so90501273qtd.1 for <ietf@ietf.org>; Sun, 22 Jan 2017 11:21:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tMK4Xt2OhUf49jdXgqdn9iGp2tCNVT6NDr54mjvSPvE=; b=Rt1+oTJ4CPfD5cmxr5UyFUI/PzXzIScHVb88JVf9LSuhA4wYy7Xvm6kYAq7srlZ7eR 6grfm9CwSIiFu464+Y0rOt1jsbSmiMOiyvAGVRvZweuD5iee/NmvSKhgKCVQDo+hthTD /Zx6Bb3cRI2aiMfUamxJSjw2a6/UfqXPJF4+EG3TExUPODGbpSSrnOUAgI8CjzisqFg8 QE1UrWyd2E/BPn6WjbGyj0ejtUdXNoHAAySKPR9kavjxw0lVX+tcQCSivDNHY1vePMvi wa83eH563HKt5bCUDG6f4H/1D6gBoiX2z0DMUkAkUNktpDbcK2krdrq9oDz1lRMq6LJP 0AmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tMK4Xt2OhUf49jdXgqdn9iGp2tCNVT6NDr54mjvSPvE=; b=Zvw7nT7mBnJR4/JepXSLeu0SaRxYKqC0SHEoef8ItnIIuf6HrljBNmemCIypO+8dZ7 CfqSH83Gb9mnCL2+eav1MdmwHJsRnUGZ6/d9DZf0GH+4Vat+l68O1jhH31C0KghfZ0HR 3YgGMzuWy+P7Hp8lr8pTT7PA37bta3V+pzT4yzGW1ib9D9sIsSUlZ3dImiXeTNwatzBE xEiDK0p1OIkr1MAG1thA4Gloo0R+4NztsUlPQPSJxxaDB73KDVDY1dPkw52Yhobj2XKa VhdprLkmb8MAeATkoHiW2+ebHV4RIdWzU25DenT/wvjjAa1/Wn6NcHWItNgG5eLoVqM5 MBvA==
X-Gm-Message-State: AIkVDXI2ur2SOWC8FnqKr6OvX9l+JoiMl1k61ZOCig1PPEqP/oktiBHKwSaFnHYILGvoSBlptiRARLx1FMbfv//H
X-Received: by 10.200.54.247 with SMTP id b52mr22412051qtc.124.1485112897921; Sun, 22 Jan 2017 11:21:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.179.19 with HTTP; Sun, 22 Jan 2017 11:21:07 -0800 (PST)
In-Reply-To: <b4c43d8c6e137d4b9196080f6643d83c5f0ffbae@webmail.weijax.net>
References: <c9bd3653-f421-e2ea-1b77-16d8ecd1a412@tana.it> <b4c43d8c6e137d4b9196080f6643d83c5f0ffbae@webmail.weijax.net>
From: Warren Kumari <warren@kumari.net>
Date: Sun, 22 Jan 2017 14:21:07 -0500
Message-ID: <CAHw9_iL7G2Qa_iG_Ws1vMO5LXpF91gV3UQUF7G2ytV6RwXdgpA@mail.gmail.com>
Subject: Re: What is Ant's Fit Protocol?
To: sandy@weijax.net
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1Ebg_AYcm_kloTNwJcCRvJ_UjJo>
Cc: "ietf@ietf.org Disgust" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jan 2017 19:21:41 -0000

On Sun, Jan 22, 2017 at 12:27 PM,  <sandy@weijax.net> wrote:
> The URL you provide says:
>
> "ANT/ANT+ are managed by ANT Wireless, a division of Dynastream Innovations
> Inc.......Dynastream was established in 1998 and became a wholly owned
> subsidiary of Garmin Ltd. in December 2006. "
>
> So, there is the most likely reason for using a new proprietary solution.
> They OWN the company.  Clearly, the company's software is superior to any
> solution that was 'Not Invented Here'.

Sorry, but no -- that is an entirely reasonable supposition for
Garmin, but ANT/ANT+ is used by a significant number of other
companies as well -- for example, I know them from Peloton exercise
bikes, Samsung phones, etc.
A quick glance at their "directory" shows what looks like a few
hundred brands, and >600 products.

>From a *very* quick glance it seems that, for simple things, it is
simpler to integrate than programming against bluetooth directly (e.g
the Nordic RNF5283 is ~$2.00, and does BLE, ANT and NFC) -- there are
a number of friendly looking libraries and demos for things like
talking to bikes, etc. ANT *feels* like it provides a higher layer /
abstraction to program against -- for example, this datasheet
https://www.thisisant.com/resources/fit2-fitness-module-datasheet/...
'tis been many years since I tried to integrate a bluetooth module
into something, but when I did, there seemed to be so much rope that
getting started was tricky...

I suspect that the root answer to Alessandro question is a combination
of 1: NIH, 2: because other devices I need to talk to already do this,
and 3: better abstractions / nicely defined and documented stack.

[ Note: This is just from a brief skim of their website - I may be
completely wrong, BT / BLE may have progressed and libraries improved,
and better, clearer profiles created, etc... ]

W

>
> -Sandy
>
>
> ----- Original Message -----
> From:
> "Alessandro Vesely" <vesely@tana.it>
>
> To:
> <ietf@ietf.org>
> Cc:
>
> Sent:
> Sat, 21 Jan 2017 21:10:57 +0100
> Subject:
> What is Ant's Fit Protocol?
>
>
>
> Hi,
> I annoyingly see this stuff in some GPS devices. It seems to be a
> proprietary
> protocol for wireless communication, also used as a file format. It is
> resumed
> here:
>
> https://www.thisisant.com/company/
>
> I'm wondering why companies use that protocol instead of an open standard.
> Is
> it because there is no suitable open standard or just because they hate open
> standards?
>
> I would try and dissuade open source packages, e.g. gpsbabel, to try to
> support
> it, since that protocol seems to be going to change unpredictably and hence
> their software will never work. Opinions?
>
> TIA for any reply
> Ale
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf