Re: [TICTOC] Enterprise Profile

[Douglas Arnold <[e-mail]>]

Hello Laurent,

Thank you for the feedback on the Enterprise Profile.  I have made the
following changes in the draft [see inline comments below].  An update will
be posted shortly.

On Mon, Oct 13, 2014 at 8:10 AM, Laurent Montini (lmontini) <
[e-mail]> wrote:

>  Hi,
>
>  I have 3 comments:
>
>  1) Clause 8, first paragraph: is the sentence correct?
> “When Preferred Master Clocks are not the Best Master in one domain, they
> SHOULD operate in another domain when they. “
> Seems something missing.
>

   Text now reads:
   When Preferred Master Clocks are not the Best Master in one domain,
   they SHOULD operate as a master in another domain.

   Further explanation of multi-domain operation is added as well.

>
>  2) Unicast Discovery
> Clause 12: Forbidden options: “Slave clocks operating in the Enterprise
> Profile SHALL NOT use Unicast Discovery to establish connection to Master
> clocks.”
> Clause 13, 3rd paragraph:
> “Clocks operating in the Enterprise profile will not interoperate with
> clocks operating in the Telecom Profile for Frequency
> Synchronization[G8265.1], because the Enterprise Profile forbids Unicast
> Message Negotiation, and Unicast Discovery.”
> As neither Enterprise nor this Telecom profile use Unicast Discovery, how
> does it make this oiption an interoperability issue?
>

    Reference of Unicast Discovery has been removed from this passage.

>
>  3) Clause 13, paragraph before last, last sentence: “the Default Profile
> is…” : there are two default profiles in IEEE 1588-2008, in Annexes J.3 and
> J.4, one using the delay mechanism the other the pdelay mechanism.
>
>    - Obviously the Enterprise profile will not interop with J.4.
>    - Should the text be “The Default Profiles are described in Annexes
>    J.3 and J.4.”
>
>    This clause has been rewritten to discuss J.3 and J.4 cases separately.


> Regards,
> Laurent
>
>


-- 
Doug Arnold
Principal Technologist
*JTime!* Meinberg USA
[phone]