Re: What is Ant's Fit Protocol?

sandy@weijax.net Sun, 22 January 2017 17:27 UTC

Return-Path: <sandy@weijax.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 6E8051297C1 for <ietf@ietfa.amsl.com>; Sun, 22 Jan 2017 09:27:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level:
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=weijax.net
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 R2BV1efAqhJg for <ietf@ietfa.amsl.com>; Sun, 22 Jan 2017 09:27:01 -0800 (PST)
Received: from homiemail-a36.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 261031297AC for <ietf@ietf.org>; Sun, 22 Jan 2017 09:27:01 -0800 (PST)
Received: from homiemail-a36.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a36.g.dreamhost.com (Postfix) with ESMTP id 910E2900012E for <ietf@ietf.org>; Sun, 22 Jan 2017 09:27:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=weijax.net; h=message-id :from:to:in-reply-to:subject:date:content-type:mime-version; s= weijax.net; bh=Pc5azHF7+Ktw2O2fpKQJbOCNAxI=; b=f+3w0m6FOg1sdyeBu EOEBgdj0bOaRUKP4+jT0PZBWicAql3mSh/iRBFhcqJx5W5KMxeSn1OaCR/Y7/NVe Vmufe7V9LAa/087SWY4xptGmG895lDvCqE/IHiiwHDSbqu1DGptSuwrFPfLX1vgw ynAjJJi8VQf4pmkzFJWvlGP74o=
Received: from localhost (alc-nat.dreamhost.com [66.33.206.8]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: sandy@weijax.net) by homiemail-a36.g.dreamhost.com (Postfix) with ESMTPSA id 875A69000110 for <ietf@ietf.org>; Sun, 22 Jan 2017 09:27:00 -0800 (PST)
Message-Id: <b4c43d8c6e137d4b9196080f6643d83c5f0ffbae@webmail.weijax.net>
From: sandy@weijax.net
To: ietf@ietf.org
X-Mailer: Atmail 7.5.3
X-Originating-IP: 24.96.120.184
in-reply-to: <c9bd3653-f421-e2ea-1b77-16d8ecd1a412@tana.it>
Subject: Re: What is Ant's Fit Protocol?
Date: Sun, 22 Jan 2017 12:27:00 -0500
Content-Type: multipart/alternative; boundary="=_9c0fb6f0dcdaeac2255ae96c54461b6f"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NsUpBA0RCeESO8oNCn78CsD993c>
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 17:27:02 -0000

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'.

-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