[TICTOC] Unicast discovery in 1588

Richard Cochran <richardcochran@gmail.com> Sat, 05 April 2014 14:13 UTC

Return-Path: <richardcochran@gmail.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45A491A0467 for <tictoc@ietfa.amsl.com>; Sat, 5 Apr 2014 07:13:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 0SZGJxO6SPTr for <tictoc@ietfa.amsl.com>; Sat, 5 Apr 2014 07:13:50 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 2325A1A017C for <tictoc@ietf.org>; Sat, 5 Apr 2014 07:13:49 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id hi2so2758551wib.11 for <tictoc@ietf.org>; Sat, 05 Apr 2014 07:13:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:mime-version:content-type :content-disposition:user-agent; bh=bOtNQpDEnvfKPcRpn4U9BV4uAI6qPbpCzsTN3XBNpj4=; b=nQOAfiQmOL+FMseCTO1yt3KZHdLwlu+Sg9NER5bJi3PCIs7mCQ1UpEQp1GSqKpEeya dnkPSJL7Y0HtSayh7QRVlgkeyG5FTPVePN0X0KRAXbWNF7MW3u6FdhYlsYRKMHBEuS/u gxOHUO47HG/hDTseuWWcVkyalmboRlFr/9Nowj90xeNiFyyBp6PfUGHHo6ua6AWHaGl/ EOLbvhT98zwfRgehusBju28VKfiiivtofpYl3vogDiqmj3mCbHXPtXnFvdFQ8xNEDgAQ NuKGtQuJv5P5M+GRbeL3OlbQFb+nf7FKtwtRu0sRCheKjUN4RTtLKh2MnM5odt2l3AH3 QCCA==
X-Received: by 10.195.13.76 with SMTP id ew12mr3746636wjd.80.1396707224821; Sat, 05 Apr 2014 07:13:44 -0700 (PDT)
Received: from netboy (089144207110.atnat0016.highway.bob.at. [89.144.207.110]) by mx.google.com with ESMTPSA id u46sm27327582eel.1.2014.04.05.07.13.42 for <tictoc@ietf.org> (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sat, 05 Apr 2014 07:13:44 -0700 (PDT)
Date: Sat, 05 Apr 2014 16:13:35 +0200
From: Richard Cochran <richardcochran@gmail.com>
To: tictoc@ietf.org
Message-ID: <20140405141335.GA6235@netboy>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/tictoc/dd1qRPqF_85vANWltP1ipAmPfTs
Subject: [TICTOC] Unicast discovery in 1588
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Apr 2014 14:13:56 -0000

Dear list,

Recently I have been considering how to implement the unicast bits of
1588 in linuxptp. It looks like to me that unicast is one of those
grey areas of the standard. I wanted to request an "interpretation",
but it looks like 1588 has been dropped, and so I ask my question
here.

Clause 17.5.1 talks about slaves wanting to use unicast when the
network doesn't provide multicast. In this case, they are supposed to
use unicast message negotiation with the masters in their table.

However, the way to ask for unicast service and the way to configure
the table are both via management messages. These are never unicast,
as far as I can tell. So it seems impossible to use this option.

Does anyone have any insight into this?

Thanks,
Richard