Re: [TICTOC] Enterprise profile update

Richard Cochran <richardcochran@gmail.com> Wed, 09 April 2014 13:54 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 829B51A02C6 for <tictoc@ietfa.amsl.com>; Wed, 9 Apr 2014 06:54:33 -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 dY3Un3CVaLJ4 for <tictoc@ietfa.amsl.com>; Wed, 9 Apr 2014 06:54:31 -0700 (PDT)
Received: from mail-ee0-x232.google.com (mail-ee0-x232.google.com [IPv6:2a00:1450:4013:c00::232]) by ietfa.amsl.com (Postfix) with ESMTP id 6BDD71A027E for <tictoc@ietf.org>; Wed, 9 Apr 2014 06:54:31 -0700 (PDT)
Received: by mail-ee0-f50.google.com with SMTP id c13so1959250eek.9 for <tictoc@ietf.org>; Wed, 09 Apr 2014 06:54:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=Uu3IoiQya6vKXhiEQ3jk1NFQ5rrm0zvBuwdF0u2gRZ0=; b=S2PZdaCCP1conx38k942Vsg8WDgMVsbtLTBQQbJVlpPptzkn/CdHUOxr5XLiQIZM5o xjGgbIiFbIO8QTBFcgx81SEAG36+wbz7suqNY3dJnrv/fpHsaKLyrmtVA7CHy1OR4JBK XqKr1noy5TYF/NR8h96Tqdhd9/YkXCR3LB4MDdulkG4gJfG6+ISQZuN9Ah7ajV/QZ04r 7sqOZ5cAj8vVjzf278Xu30MbwpqixORNc/sWK1+qe5BOF8Mcw7lR1xQGzbZQb/8N2NZ/ aj1IQUgPqPFtERXKnbvFBSMGBH+ogxGRTPlyAv5MsfgjYHgXr2L0emWAXFiCJc56GvGn AY4w==
X-Received: by 10.15.51.141 with SMTP id n13mr12840504eew.17.1397051670418; Wed, 09 Apr 2014 06:54:30 -0700 (PDT)
Received: from netboy (089144206019.atnat0015.highway.bob.at. [89.144.206.19]) by mx.google.com with ESMTPSA id z48sm2448693eel.27.2014.04.09.06.54.25 for <multiple recipients> (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 09 Apr 2014 06:54:29 -0700 (PDT)
Date: Wed, 09 Apr 2014 15:54:19 +0200
From: Richard Cochran <richardcochran@gmail.com>
To: John Fletcher <John.Fletcher@bbc.co.uk>
Message-ID: <20140409135419.GB6719@netboy>
References: <CACQYgzE106JaKArgc=3HKkKcrdvSy5PmK-A0=_ZMdfrFUJbrtQ@mail.gmail.com> <20140405112034.GM22106@netboy> <20140405133748.GB4566@netboy> <CALw1_Q3hNRNpHzQ=1z0XRTqvcvm2W7=Gm_ZWa2UJT-BqYTvmZw@mail.gmail.com> <CF68E7A8.7488B%lmontini@cisco.com> <1D3F6A7C-AD27-4A63-9F63-41D9929AE285@owczarek.co.uk> <20140408144527.GA5087@netboy> <CAHyFsxmfCsJtP4+PwKyRciPHBQuZw9ONDBPtOkBSqup1P2z_Rw@mail.gmail.com> <B1D49063AD5FBD4688F3EEDEC68B201757E1F8DF@BGB01XUD1011.national.core.bbc.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <B1D49063AD5FBD4688F3EEDEC68B201757E1F8DF@BGB01XUD1011.national.core.bbc.co.uk>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/tictoc/5kvYORMaySOqpeGb9xbuwd3L7LA
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Enterprise profile update
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: Wed, 09 Apr 2014 13:54:33 -0000

On Wed, Apr 09, 2014 at 10:00:25AM +0000, John Fletcher wrote:
> Wojciech,
> 
> In your email below, you omitted the option b)
> 
> 9.5.11.1 states:
> 
> Delay_Req messages shall be transmitted as multicast except if:
> a) The optional unicast provisions of Clause 16 are used
> b) Specified otherwise by a profile
> 
> 
> In the case of the Enterprise and SMPTE Profiles, option b) is in effect, yes?

Well, in 1588, there is more to it than that.

19.2.2:

  A node that uses a transport protocol for which the mapping is
  defined in an annex of this standard shall conform to that annex.

D.3:

  PTP messages shall use the multicast message specified in Table D.1.

The enterprise profile uses the IPv4 transport, and it therefore nodes
must conform to Annex D, which in turn specifies using multicast. The
option of unicast is available via 16.1, and so the enterprise profile
should mandate that option.

At least, that is how I understand the text.

Another interpretation would be, "we can do anything we want regarding
unicast," justified by the vague wording of 7.3.1.

Thanks,
Richard