What is Ant's Fit Protocol?

Alessandro Vesely <vesely@tana.it> Sat, 21 January 2017 20:11 UTC

Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6B0F0129B20 for <ietf@ietfa.amsl.com>; Sat, 21 Jan 2017 12:11:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.101
X-Spam-Status: No, score=-6.101 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=tana.it
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 8Jp_K8W5hPQG for <ietf@ietfa.amsl.com>; Sat, 21 Jan 2017 12:11:03 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C05AF1288B8 for <ietf@ietf.org>; Sat, 21 Jan 2017 12:11:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1485029457; bh=sujL7tO9dve9d1LxDINhkvNDoScihqsmeX1596gRg7M=; l=609; h=To:From:Date; b=iiKj1Zwb40Ztr+poTMWWf0zR40k3DsiSZ83RHcXjMHMLM750YUITIGaoaqcSnaAVE qAelDnRq6Fg5CyxyivNjvrQRh63b6u/QR5du1RuWu9P2+m3F6uYuGDlFvg7P7B9806 7YCmv7ZBE24Vp61HgXmuZrX8d2eLv3di9Rk1fQt8=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [] (pcale.tana []) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Sat, 21 Jan 2017 21:10:57 +0100 id 00000000005DC044.000000005883C051.00000A89
To: ietf@ietf.org
From: Alessandro Vesely <vesely@tana.it>
Subject: What is Ant's Fit Protocol?
Message-ID: <c9bd3653-f421-e2ea-1b77-16d8ecd1a412@tana.it>
Date: Sat, 21 Jan 2017 21:10:57 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LrilkDsZoRARr1t_I_r2NXZCkXM>
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: Sat, 21 Jan 2017 20:11:04 -0000

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 


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 

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