
From kevin.gross@avanw.com  Fri Jan 11 11:27:33 2013
Return-Path: <kevin.gross@avanw.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA44621F845A for <tictoc@ietfa.amsl.com>; Fri, 11 Jan 2013 11:27:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.642
X-Spam-Level: 
X-Spam-Status: No, score=-1.642 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iFtaX9r-HstS for <tictoc@ietfa.amsl.com>; Fri, 11 Jan 2013 11:27:31 -0800 (PST)
Received: from oproxy13-pub.unifiedlayer.com (oproxy13-pub.unifiedlayer.com [69.89.16.30]) by ietfa.amsl.com (Postfix) with SMTP id A2A0A21F8444 for <tictoc@ietf.org>; Fri, 11 Jan 2013 11:27:29 -0800 (PST)
Received: (qmail 22449 invoked by uid 0); 11 Jan 2013 19:27:05 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by oproxy13.unifiedlayer.com with SMTP; 11 Jan 2013 19:27:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default;  h=Content-Type:To:From:Subject:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=Dy0AsmF+C2w9fyotEwy6x+LDkHIhdONEkGAqCXciHY8=;  b=YelonPglmSI2oAKMQAzAFfwujRa8ezHakFbds/MBKG9kkepEtXNWzzj7Pj5gMazuLi2w6dNED6SMqlzB77RUiIhqfWYg7QMZp7uDggx4K6H30GMIhGRligvyadDxs1mq;
Received: from [209.85.223.173] (port=61220 helo=mail-ie0-f173.google.com) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1TtkFs-00056b-M3 for tictoc@ietf.org; Fri, 11 Jan 2013 12:27:04 -0700
Received: by mail-ie0-f173.google.com with SMTP id e13so2779514iej.32 for <tictoc@ietf.org>; Fri, 11 Jan 2013 11:27:03 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.50.183.227 with SMTP id ep3mr150312igc.107.1357932423677; Fri, 11 Jan 2013 11:27:03 -0800 (PST)
Received: by 10.50.151.135 with HTTP; Fri, 11 Jan 2013 11:27:03 -0800 (PST)
In-Reply-To: <20120802185805.24036.33724.idtracker@ietfa.amsl.com>
References: <20120802185805.24036.33724.idtracker@ietfa.amsl.com>
Date: Fri, 11 Jan 2013 12:27:03 -0700
Message-ID: <CALw1_Q1x=BMG5Fstom2MBs1uFUoAGr4RZTwts=C=ugkGw+ROhA@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: tictoc@ietf.org
Content-Type: multipart/alternative; boundary=14dae9340d91be06df04d3084718
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 209.85.223.173 authed with kevin.gross@avanw.com}
Subject: Re: [TICTOC] I-D Action: draft-ietf-tictoc-ptp-mib-03.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 11 Jan 2013 19:27:33 -0000

--14dae9340d91be06df04d3084718
Content-Type: text/plain; charset=ISO-8859-1

Some comments on this:

Abstract:

Add a bracketed reference to IEEE 1588-2008


Section 1

s/defined to monitor, measure the performance/defined to monitor and
measure the performance

It is claimed that monitoring is not a supported function of this MIB but I
have identified numerous versiables in the MIB which I would consider to be
providing a monitoring function. If you need specific examples, let me know.


Section 1.1

What in this MIB is profile dependent? I did not identify anything in my
review. It would be desirable. if possible,  to have a profile-independent
MIB.


TEXTUAL-CONVENTION general issues

Consider alphabetizing


ClockInstanceType TEXTUAL-CONVENTION definition

Description requires elucidation or a reference.


ClockProfileType TEXTUAL-CONVENTION definition

Consider using and OUI instead of an enumeration. IEEE 1588-1588 requires
an OUI be associated with each profile.


OBJECT-TYPE general issues

Consider being consistent about repeating TEXTUAL-CONVENTION descriptions,
explicitly referencing them or assuming readers will track down the
reference without reminder.


ptpDomainClockPortsTotal OBJECT-TYPE

I assume this is the number of ports for the managed PTP-capable system
(i.e. a router or switch). Suggest adding "in the system" to the
description to clarify scope of count.


ptpbaseClockTimePropertiesDSTable OBJECT-TYPE


s/clock Timeproperties Datasets for/clock time properties datasets for



PtpbaseClockTransDefaultDSEntry SEQUENCE


Use ClockDomainType textual convention instead of Integer32 for
ptpbaseClockTransDefaultDSPrimaryDomain



PtpbaseClockPortEntry SEQUENCE


Change ptpbaseClockPortSyncOneStep to ptpbaseClockPortSyncTwoStep to
match 1588 semantics for this boolean



ptpbaseClockPortRunningEncapsulationType OBJECT-TYPE


Needs a textual convention or description of allowed values and their meanings



ptpbaseClockPortTransDSlogMinPdelayReqInt OBJECT-TYPE


Change to ClockIntervalBase2 type



Section 5


Copy-paste error: "creation and/or manipulation of tunnels"



Section 6


To be added


Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org


On Thu, Aug 2, 2012 at 12:58 PM, <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the Timing over IP Connection and Transfer
> of Clock Working Group of the IETF.
>
>         Title           : Precision Time Protocol Version 2 (PTPv2)
> Management Information Base
>         Author(s)       : Vinay Shankarkumar
>                           Laurent Montini
>                           Tim Frost
>                           Greg Dowd
>         Filename        : draft-ietf-tictoc-ptp-mib-03.txt
>         Pages           : 65
>         Date            : 2012-07-31
>
> Abstract:
>    This memo defines a portion of the Management Information Base (MIB)
>    for use with network management protocols in TCP/IP-based internets.
>    In particular, it defines objects for managing networks using
>    Precision Time Protocol.
>
>    This memo specifies a MIB module in a manner that is both compliant
>    to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
>    definitions.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tictoc-ptp-mib-03
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-tictoc-ptp-mib-03
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>

--14dae9340d91be06df04d3084718
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Some comments on this:<div><br></div><div>Abstract:</div><div><br></div><di=
v>Add a bracketed reference to IEEE 1588-2008</div><div><br></div><div><br>=
</div><div>Section 1</div><div><br></div><div>s/defined to monitor, measure=
 the performance/defined to monitor and measure the performance</div>
<div><br></div><div>It is claimed that monitoring is not a supported=A0func=
tion=A0of this MIB but I have identified numerous versiables in the MIB whi=
ch I would consider to be providing a monitoring function. If you need spec=
ific examples, let me know.</div>
<div><br></div><div><br></div><div>Section 1.1</div><div><br></div><div>Wha=
t in this MIB is profile dependent? I did not identify anything in my revie=
w. It would be=A0desirable. if possible,=A0=A0to have a profile-independent=
 MIB.</div>
<div><br></div><div><br></div><div>TEXTUAL-CONVENTION general issues</div><=
div><br></div><div>Consider alphabetizing</div><div><br></div><div><br></di=
v><div>ClockInstanceType TEXTUAL-CONVENTION definition</div><div><br></div>
<div>Description requires elucidation or a reference.</div><div><br></div><=
div><br></div><div>ClockProfileType=A0TEXTUAL-CONVENTION definition</div><d=
iv><br></div><div>Consider using and OUI instead of an enumeration. IEEE 15=
88-1588 requires an OUI be associated with each profile.</div>
<div><br></div><div><br></div><div>OBJECT-TYPE general issues</div><div><br=
></div><div>Consider being consistent about repeating=A0TEXTUAL-CONVENTION =
descriptions, explicitly referencing them or assuming readers will track do=
wn the reference without reminder.</div>
<div><br></div><div><br></div><div>ptpDomainClockPortsTotal=A0<span style=
=3D"font-size:1em">OBJECT-TYPE</span></div><div><br></div><div>I assume thi=
s is the number of ports for the managed PTP-capable system (i.e. a router =
or switch). Suggest adding &quot;in the system&quot; to the description to =
clarify scope of count.</div>
<div><br></div><div><br></div><div><pre class=3D"newpage" style=3D"font-siz=
e:1em;margin-top:0px;margin-bottom:0px">ptpbaseClockTimePropertiesDSTable O=
BJECT-TYPE</pre><pre class=3D"newpage" style=3D"font-size:1em;margin-top:0p=
x;margin-bottom:0px">
<br></pre><pre class=3D"newpage" style=3D"font-size:1em;margin-top:0px;marg=
in-bottom:0px">s/<span style=3D"font-size:1em">clock Timeproperties </span>=
<span style=3D"font-size:1em">Datasets for/clock time properties datasets f=
or</span></pre>
<pre class=3D"newpage" style=3D"font-size:1em;margin-top:0px;margin-bottom:=
0px"><span style=3D"font-size:1em"><br></span></pre><pre class=3D"newpage" =
style=3D"font-size:1em;margin-top:0px;margin-bottom:0px"><span style=3D"fon=
t-size:1em"><br>
</span></pre><pre class=3D"newpage" style=3D"font-size:1em;margin-top:0px;m=
argin-bottom:0px">PtpbaseClockTransDefaultDSEntry SEQUENCE</pre><pre class=
=3D"newpage" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px"><br><=
/pre>
<pre class=3D"newpage" style=3D"font-size:1em;margin-top:0px;margin-bottom:=
0px">Use ClockDomainType textual convention instead of Integer32 for <span =
style=3D"font-size:1em">ptpbaseClockTransDefaultDSPrimaryDomain</span></pre=
><pre class=3D"newpage" style=3D"font-size:1em;margin-top:0px;margin-bottom=
:0px">
<span style=3D"font-size:1em"><br></span></pre><pre class=3D"newpage" style=
=3D"font-size:1em;margin-top:0px;margin-bottom:0px"><span style=3D"font-siz=
e:1em"><br></span></pre><pre class=3D"newpage" style=3D"font-size:1em;margi=
n-top:0px;margin-bottom:0px">
PtpbaseClockPortEntry SEQUENCE</pre><pre class=3D"newpage" style=3D"font-si=
ze:1em;margin-top:0px;margin-bottom:0px"><br></pre><pre class=3D"newpage" s=
tyle=3D"margin-top:0px;margin-bottom:0px"><span style=3D"font-size:1em">Cha=
nge ptpbaseClockPortSyncOneStep to ptpbaseClockPortSyncTwoStep to match 158=
8 </span>semantics<span style=3D"font-size:1em"> for this boolean</span></p=
re>
<pre class=3D"newpage" style=3D"margin-top:0px;margin-bottom:0px"><span sty=
le=3D"font-size:1em"><br></span></pre><pre class=3D"newpage" style=3D"margi=
n-top:0px;margin-bottom:0px"><span style=3D"font-size:1em"><br></span></pre=
><pre class=3D"newpage" style=3D"margin-top:0px;margin-bottom:0px">
<pre class=3D"newpage" style=3D"font-size:1em;margin-top:0px;margin-bottom:=
0px">ptpbaseClockPortRunningEncapsulationType OBJECT-TYPE</pre><pre class=
=3D"newpage" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px"><br><=
/pre><pre class=3D"newpage" style=3D"font-size:1em;margin-top:0px;margin-bo=
ttom:0px">
Needs a textual convention or description of allowed values and their meani=
ngs</pre><pre class=3D"newpage" style=3D"font-size:1em;margin-top:0px;margi=
n-bottom:0px"><br></pre><pre class=3D"newpage" style=3D"font-size:1em;margi=
n-top:0px;margin-bottom:0px">
<br></pre><pre class=3D"newpage" style=3D"font-size:1em;margin-top:0px;marg=
in-bottom:0px">ptpbaseClockPortTransDSlogMinPdelayReqInt OBJECT-TYPE</pre><=
pre class=3D"newpage" style=3D"font-size:1em;margin-top:0px;margin-bottom:0=
px">
<br></pre><pre class=3D"newpage" style=3D"font-size:1em;margin-top:0px;marg=
in-bottom:0px">Change to ClockIntervalBase2 type</pre><pre class=3D"newpage=
" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px"><br></pre><pre c=
lass=3D"newpage" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px">
<br></pre><pre class=3D"newpage" style=3D"font-size:1em;margin-top:0px;marg=
in-bottom:0px">Section 5</pre><pre class=3D"newpage" style=3D"font-size:1em=
;margin-top:0px;margin-bottom:0px"><br></pre><pre class=3D"newpage" style=
=3D"font-size:1em;margin-top:0px;margin-bottom:0px">
Copy-paste error: &quot;<span style=3D"font-size:1em">creation and/or manip=
ulation of tunnels&quot;</span></pre><pre class=3D"newpage" style=3D"font-s=
ize:1em;margin-top:0px;margin-bottom:0px"><span style=3D"font-size:1em"><br=
></span></pre>
<pre class=3D"newpage" style=3D"font-size:1em;margin-top:0px;margin-bottom:=
0px"><span style=3D"font-size:1em"><br></span></pre><pre class=3D"newpage" =
style=3D"font-size:1em;margin-top:0px;margin-bottom:0px"><span style=3D"fon=
t-size:1em">Section 6</span></pre>
<pre class=3D"newpage" style=3D"font-size:1em;margin-top:0px;margin-bottom:=
0px"><span style=3D"font-size:1em"><br></span></pre><pre class=3D"newpage" =
style=3D"font-size:1em;margin-top:0px;margin-bottom:0px"><span style=3D"fon=
t-size:1em">To be added</span></pre>
</pre></div><div><br clear=3D"all"><div>Kevin Gross<br><div>+1-303-447-0517=
</div><div>Media Network Consultant<br><div>AVA Networks -=A0<a href=3D"htt=
p://www.avanw.com/" target=3D"_blank">www.AVAnw.com</a>,=A0<a href=3D"http:=
//www.X192.org" target=3D"_blank">www.X192.org</a></div>
</div></div>
<br><br><div class=3D"gmail_quote">On Thu, Aug 2, 2012 at 12:58 PM,  <span =
dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blan=
k">internet-drafts@ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">
<br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
=A0This draft is a work item of the Timing over IP Connection and Transfer =
of Clock Working Group of the IETF.<br>
<br>
=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Precision Time Protocol Version=
 2 (PTPv2) Management Information Base<br>
=A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Vinay Shankarkumar<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Laurent Montini<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Tim Frost<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Greg Dowd<br>
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-tictoc-ptp-mib-03.txt<=
br>
=A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 65<br>
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2012-07-31<br>
<br>
Abstract:<br>
=A0 =A0This memo defines a portion of the Management Information Base (MIB)=
<br>
=A0 =A0for use with network management protocols in TCP/IP-based internets.=
<br>
=A0 =A0In particular, it defines objects for managing networks using<br>
=A0 =A0Precision Time Protocol.<br>
<br>
=A0 =A0This memo specifies a MIB module in a manner that is both compliant<=
br>
=A0 =A0to the SNMPv2 SMI, and semantically identical to the peer SNMPv1<br>
=A0 =A0definitions.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib" targ=
et=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib</a=
><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-tictoc-ptp-mib-03" target=
=3D"_blank">http://tools.ietf.org/html/draft-ietf-tictoc-ptp-mib-03</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tictoc-ptp-mib-03"=
 target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tictoc-ptp=
-mib-03</a><br>
<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org">TICTOC@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><br>
</blockquote></div><br></div>

--14dae9340d91be06df04d3084718--

From kevin.gross@avanw.com  Fri Jan 11 11:43:29 2013
Return-Path: <kevin.gross@avanw.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7596121F8A6E for <tictoc@ietfa.amsl.com>; Fri, 11 Jan 2013 11:43:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.642
X-Spam-Level: 
X-Spam-Status: No, score=-1.642 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7i4J76xrQggU for <tictoc@ietfa.amsl.com>; Fri, 11 Jan 2013 11:43:28 -0800 (PST)
Received: from oproxy13-pub.unifiedlayer.com (oproxy13-pub.unifiedlayer.com [69.89.16.30]) by ietfa.amsl.com (Postfix) with SMTP id 8786621F87D6 for <tictoc@ietf.org>; Fri, 11 Jan 2013 11:43:27 -0800 (PST)
Received: (qmail 22910 invoked by uid 0); 11 Jan 2013 19:43:06 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by oproxy13.unifiedlayer.com with SMTP; 11 Jan 2013 19:43:06 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default;  h=Content-Type:Cc:To:From:Subject:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=aX2kFu24xY4J+FJjvbgEluXLs7YMYWdAQahg8oGHOeI=;  b=RPFoZ4XqtB5T3laKC/PJYCGJZfyxqtgY/ja1B+PhBb/BDWYBq/yrS9V88CWH7PnUh9j48FMe60NzJxsKpWnkJ8RBm7/IWcMJO3o8Q/WwVWI1xrg/d+uJucgUrSHQMxcH;
Received: from [209.85.210.174] (port=40182 helo=mail-ia0-f174.google.com) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1TtkVO-00046Z-0G for tictoc@ietf.org; Fri, 11 Jan 2013 12:43:06 -0700
Received: by mail-ia0-f174.google.com with SMTP id o25so788140iad.5 for <tictoc@ietf.org>; Fri, 11 Jan 2013 11:43:05 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.50.53.161 with SMTP id c1mr200359igp.95.1357933385106; Fri, 11 Jan 2013 11:43:05 -0800 (PST)
Received: by 10.50.151.135 with HTTP; Fri, 11 Jan 2013 11:43:05 -0800 (PST)
In-Reply-To: <50A57494.40306@pobox.com>
References: <50A22846.3080609@isoc.org> <07F7D7DED63154409F13298786A2ADC904647348@EXRAD5.ad.rad.co.il> <CA+RyBmWNmxMTcOBjUqJwMVDbwoErvd1J9xMzhP2EC-G1VuSanw@mail.gmail.com> <50A57494.40306@pobox.com>
Date: Fri, 11 Jan 2013 12:43:05 -0700
Message-ID: <CALw1_Q1eLND2vHhWuAK48_qjZWZ2Bze1vyn22Lkcc+92bNm9wQ@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: kodonog@pobox.com
Content-Type: multipart/alternative; boundary=f46d04339d180c45c204d3088111
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 209.85.210.174 authed with kevin.gross@avanw.com}
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] consensus question on change of scope for the 1588 mib document
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 11 Jan 2013 19:43:29 -0000

--f46d04339d180c45c204d3088111
Content-Type: text/plain; charset=ISO-8859-1

The draft purports that this is that this MIB is one of several modular
parts which combine to presumably provide comprehensive configuration and
monitoring. If that modular approach can actually be pursued, we can finish
this MIB as defined and then go to work on a writable one. I sort of doubt
that approach will be technically effective but if someone can cite an
example of another project done in this way, maybe I can get over my
skepticism.

As or if the scope of this effort increases another complication that
becomes stronger is the interaction with the small multitude of other
1588-related MIBs that have already been published. How does functionality
overlap. Do we want to borrow good ideas from previous efforts. Do we want
to try and unify all of this?

In summary, I'm usually opposed to increasing scope but I question whether
the originally defined scope was sufficiently useful. I was not involved at
the outset of this effort so my understanding of the original development
plan is limited.

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org


On Thu, Nov 15, 2012 at 4:02 PM, Karen O'Donoghue <kodonog@pobox.com> wrote:

>  Greg,
>
> I don't expect this change to be a small deal. However, the authors have
> indicated they can accomplish the change without a significant delay in
> getting the document to WGLC. The reviews we've had thus far are informal,
> and the formal MIB Doctor review won't occur until the document goes to the
> IESG.
>
> Karen
>
>
> On 11/15/12 12:57 PM, Greg Mirsky wrote:
>
> Dear Yaakov, et al.,
> changing from R/O paradigm to R/W is never a small deal. It is, IMHO, an
> endeavor. Had the R/O version been through MIB Doctor review? I'd expect it
> to be ran though again once R/W objects introduced.
>
> Regards,
> Greg
>
> On Thu, Nov 15, 2012 at 12:53 AM, Yaakov Stein <yaakov_s@rad.com> wrote:
>
>> With chair hat off -
>>
>> I am in favor of the change as long as it remains a minor change,
>> and introduce radically new functionality.
>>
>> Y(J)S
>>
>> -----Original Message-----
>> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
>> Of Karen O'Donoghue
>> Sent: Tuesday, November 13, 2012 13:00
>> To: tictoc@ietf.org
>> Subject: [TICTOC] consensus question on change of scope for the 1588 mib
>> document
>>
>> During last week's tictoc meeting at ietf85, it was decided that the mib
>> would be changed from a read only mib to a read/write mib for
>> configuration purposes.
>>
>> The authors proposed this change, and they believe this will not
>> significantly delay publication of the mib.
>>
>> The current draft is available at:
>> http://tools.ietf.org/wg/tictoc/draft-ietf-tictoc-ptp-mib/
>>
>> The feeling in the room was that this was an acceptable change. This
>> email is to confirm that decision and to solicit comments or concerns
>> from the mailing list.
>>
>> Regards,
>> Karen
>>
>>
>> _______________________________________________
>> TICTOC mailing list
>> TICTOC@ietf.org
>> https://www.ietf.org/mailman/listinfo/tictoc
>> _______________________________________________
>> TICTOC mailing list
>> TICTOC@ietf.org
>> https://www.ietf.org/mailman/listinfo/tictoc
>>
>
>
>
> _______________________________________________
> TICTOC mailing listTICTOC@ietf.orghttps://www.ietf.org/mailman/listinfo/tictoc
>
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>
>

--f46d04339d180c45c204d3088111
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The draft=A0purports=A0that this is that this MIB is one of several modular=
 parts which combine to presumably provide comprehensive configuration and =
monitoring. If that modular approach can actually be pursued, we can finish=
 this MIB as defined and then go to work on a writable one. I sort of doubt=
 that approach will be=A0technically=A0effective but if someone can cite an=
 example of another project done in this way, maybe I can get over my skept=
icism.<div>
<br></div><div>As or if the scope of this effort=A0increases=A0another comp=
lication that becomes stronger is the interaction with the small multitude =
of other 1588-related MIBs that have already been published. How does funct=
ionality overlap. Do we want to borrow good ideas from previous efforts. Do=
 we want to try and unify all of this?</div>
<div><br></div><div>In summary, I&#39;m usually=A0opposed=A0to increasing s=
cope but I question whether the originally defined scope was sufficiently u=
seful. I was not involved at the outset of this effort so my=A0understandin=
g=A0of the original development plan is limited.<br>
<div><br clear=3D"all"><div>Kevin Gross<br><div>+1-303-447-0517</div><div>M=
edia Network Consultant<br><div>AVA Networks -=A0<a href=3D"http://www.avan=
w.com/" target=3D"_blank">www.AVAnw.com</a>,=A0<a href=3D"http://www.X192.o=
rg" target=3D"_blank">www.X192.org</a></div>
</div></div>
<br><br><div class=3D"gmail_quote">On Thu, Nov 15, 2012 at 4:02 PM, Karen O=
&#39;Donoghue <span dir=3D"ltr">&lt;<a href=3D"mailto:kodonog@pobox.com" ta=
rget=3D"_blank">kodonog@pobox.com</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">

 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div>Greg,<br>
      <br>
      I don&#39;t expect this change to be a small deal. However, the
      authors have indicated they can accomplish the change without a
      significant delay in getting the document to WGLC. The reviews
      we&#39;ve had thus far are informal, and the formal MIB Doctor review
      won&#39;t occur until the document goes to the IESG.<span class=3D"HO=
EnZb"><font color=3D"#888888"><br>
      <br>
      Karen</font></span><div class=3D"im"><br>
      <br>
      On 11/15/12 12:57 PM, Greg Mirsky wrote:<br>
    </div></div><div><div class=3D"h5">
    <blockquote type=3D"cite">Dear Yaakov, et al.,<br>
      changing from R/O paradigm to R/W is never a small deal. It is,
      IMHO, an endeavor. Had the R/O version been through MIB Doctor
      review? I&#39;d expect it to be ran though again once R/W objects
      introduced.<br>
      <br>
      Regards,<br>
      Greg<br>
      <br>
      <div class=3D"gmail_quote">On Thu, Nov 15, 2012 at 12:53 AM, Yaakov
        Stein <span dir=3D"ltr">&lt;<a href=3D"mailto:yaakov_s@rad.com" tar=
get=3D"_blank">yaakov_s@rad.com</a>&gt;</span>
        wrote:<br>
        <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">
          With chair hat off -<br>
          <br>
          I am in favor of the change as long as it remains a minor
          change,<br>
          and introduce radically new functionality.<br>
          <br>
          Y(J)S<br>
          <br>
          -----Original Message-----<br>
          From: <a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_blank=
">tictoc-bounces@ietf.org</a>
          [mailto:<a href=3D"mailto:tictoc-bounces@ietf.org" target=3D"_bla=
nk">tictoc-bounces@ietf.org</a>]
          On Behalf Of Karen O&#39;Donoghue<br>
          Sent: Tuesday, November 13, 2012 13:00<br>
          To: <a href=3D"mailto:tictoc@ietf.org" target=3D"_blank">tictoc@i=
etf.org</a><br>
          Subject: [TICTOC] consensus question on change of scope for
          the 1588 mib document<br>
          <br>
          During last week&#39;s tictoc meeting at ietf85, it was decided
          that the mib<br>
          would be changed from a read only mib to a read/write mib for<br>
          configuration purposes.<br>
          <br>
          The authors proposed this change, and they believe this will
          not<br>
          significantly delay publication of the mib.<br>
          <br>
          The current draft is available at:<br>
          <a href=3D"http://tools.ietf.org/wg/tictoc/draft-ietf-tictoc-ptp-=
mib/" target=3D"_blank">http://tools.ietf.org/wg/tictoc/draft-ietf-tictoc-p=
tp-mib/</a><br>
          <br>
          The feeling in the room was that this was an acceptable
          change. This<br>
          email is to confirm that decision and to solicit comments or
          concerns<br>
          from the mailing list.<br>
          <br>
          Regards,<br>
          Karen<br>
          <br>
          <br>
          _______________________________________________<br>
          TICTOC mailing list<br>
          <a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.=
org</a><br>
          <a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/tictoc</a><br>
          _______________________________________________<br>
          TICTOC mailing list<br>
          <a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.=
org</a><br>
          <a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/tictoc</a><br>
        </blockquote>
      </div>
      <br>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
TICTOC mailing list
<a href=3D"mailto:TICTOC@ietf.org" target=3D"_blank">TICTOC@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a>
</pre>
    </blockquote>
    <br>
  </div></div></div>

<br>_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org">TICTOC@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><br>
<br></blockquote></div><br></div></div>

--f46d04339d180c45c204d3088111--

From vinays@cisco.com  Wed Jan 23 08:58:55 2013
Return-Path: <vinays@cisco.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D9FD21F893D for <tictoc@ietfa.amsl.com>; Wed, 23 Jan 2013 08:58:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5VhWfUCN4tCD for <tictoc@ietfa.amsl.com>; Wed, 23 Jan 2013 08:58:52 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id A047A21F855C for <tictoc@ietf.org>; Wed, 23 Jan 2013 08:58:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17435; q=dns/txt; s=iport; t=1358960332; x=1360169932; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=9MYXzq574en7nIq2WcLV07jojI5s0dZTXwamfwhyOUM=; b=Q1X66fP0eP4JjTIjPIXs1RKctg9vlvrk15K7zOrJEZT4Ny1/cy81SJSz dTqvVF2YL77wbGzuGfJIMEcmxJj/hS8IZOCcO/9dGUg6USfukY/JFHTi2 2H3k2W9y8TzogGFuxrCI5rdvOnJIjdmuevCVTlullJQLolsiyYyCSTqKt Q=;
X-IronPort-AV: E=Sophos;i="4.84,523,1355097600";  d="scan'208,217";a="166862876"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-5.cisco.com with ESMTP; 23 Jan 2013 16:58:52 +0000
Received: from [64.102.95.250] (dhcp-64-102-95-250.cisco.com [64.102.95.250]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r0NGwpfZ019820; Wed, 23 Jan 2013 16:58:51 GMT
Message-ID: <510016CB.1090906@cisco.com>
Date: Wed, 23 Jan 2013 11:58:51 -0500
From: Vinay Shankarkumar <vinays@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Kevin Gross <kevin.gross@avanw.com>
References: <20120802185805.24036.33724.idtracker@ietfa.amsl.com> <CALw1_Q1x=BMG5Fstom2MBs1uFUoAGr4RZTwts=C=ugkGw+ROhA@mail.gmail.com>
In-Reply-To: <CALw1_Q1x=BMG5Fstom2MBs1uFUoAGr4RZTwts=C=ugkGw+ROhA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------000805030109090904050902"
Cc: tictoc@ietf.org
Subject: Re: [TICTOC] I-D Action: draft-ietf-tictoc-ptp-mib-03.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Jan 2013 16:58:55 -0000

This is a multi-part message in MIME format.
--------------000805030109090904050902
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Hello Kevin,
Thanks for the comments, we will address these in the next revision,

Regards,
-Vinay.


On 1/11/13 2:27 PM, Kevin Gross wrote:
> Some comments on this:
>
> Abstract:
>
> Add a bracketed reference to IEEE 1588-2008
>
>
> Section 1
>
> s/defined to monitor, measure the performance/defined to monitor and 
> measure the performance
>
> It is claimed that monitoring is not a supported function of this MIB 
> but I have identified numerous versiables in the MIB which I would 
> consider to be providing a monitoring function. If you need specific 
> examples, let me know.
>
>
> Section 1.1
>
> What in this MIB is profile dependent? I did not identify anything in 
> my review. It would be desirable. if possible,  to have a 
> profile-independent MIB.
>
>
> TEXTUAL-CONVENTION general issues
>
> Consider alphabetizing
>
>
> ClockInstanceType TEXTUAL-CONVENTION definition
>
> Description requires elucidation or a reference.
>
>
> ClockProfileType TEXTUAL-CONVENTION definition
>
> Consider using and OUI instead of an enumeration. IEEE 1588-1588 
> requires an OUI be associated with each profile.
>
>
> OBJECT-TYPE general issues
>
> Consider being consistent about repeating TEXTUAL-CONVENTION 
> descriptions, explicitly referencing them or assuming readers will 
> track down the reference without reminder.
>
>
> ptpDomainClockPortsTotal OBJECT-TYPE
>
> I assume this is the number of ports for the managed PTP-capable 
> system (i.e. a router or switch). Suggest adding "in the system" to 
> the description to clarify scope of count.
>
>
> ptpbaseClockTimePropertiesDSTable OBJECT-TYPE
> s/clock TimepropertiesDatasets for/clock time properties datasets for
>
>
>
> PtpbaseClockTransDefaultDSEntry SEQUENCE
> Use ClockDomainType textual convention instead of Integer32 forptpbaseClockTransDefaultDSPrimaryDomain
>
>
> PtpbaseClockPortEntry SEQUENCE
> Change ptpbaseClockPortSyncOneStep to ptpbaseClockPortSyncTwoStep to match 1588semantics  for this boolean
>
>
> ptpbaseClockPortRunningEncapsulationType OBJECT-TYPE
> Needs a textual convention or description of allowed values and their meanings
> ptpbaseClockPortTransDSlogMinPdelayReqInt OBJECT-TYPE
> Change to ClockIntervalBase2 type
> Section 5
> Copy-paste error: "creation and/or manipulation of tunnels"
>
>
>
> Section 6
>
>
> To be added
>
>
> Kevin Gross
> +1-303-447-0517
> Media Network Consultant
> AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org 
> <http://www.X192.org>
>
>
> On Thu, Aug 2, 2012 at 12:58 PM, <internet-drafts@ietf.org 
> <mailto:internet-drafts@ietf.org>> wrote:
>
>
>     A New Internet-Draft is available from the on-line Internet-Drafts
>     directories.
>      This draft is a work item of the Timing over IP Connection and
>     Transfer of Clock Working Group of the IETF.
>
>             Title           : Precision Time Protocol Version 2
>     (PTPv2) Management Information Base
>             Author(s)       : Vinay Shankarkumar
>                               Laurent Montini
>                               Tim Frost
>                               Greg Dowd
>             Filename        : draft-ietf-tictoc-ptp-mib-03.txt
>             Pages           : 65
>             Date            : 2012-07-31
>
>     Abstract:
>        This memo defines a portion of the Management Information Base
>     (MIB)
>        for use with network management protocols in TCP/IP-based
>     internets.
>        In particular, it defines objects for managing networks using
>        Precision Time Protocol.
>
>        This memo specifies a MIB module in a manner that is both compliant
>        to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
>        definitions.
>
>
>     The IETF datatracker status page for this draft is:
>     https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib
>
>     There's also a htmlized version available at:
>     http://tools.ietf.org/html/draft-ietf-tictoc-ptp-mib-03
>
>     A diff from the previous version is available at:
>     http://www.ietf.org/rfcdiff?url2=draft-ietf-tictoc-ptp-mib-03
>
>
>     Internet-Drafts are also available by anonymous FTP at:
>     ftp://ftp.ietf.org/internet-drafts/
>
>     _______________________________________________
>     TICTOC mailing list
>     TICTOC@ietf.org <mailto:TICTOC@ietf.org>
>     https://www.ietf.org/mailman/listinfo/tictoc
>
>
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc


--------------000805030109090904050902
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix"><br>
      Hello Kevin,<br>
      Thanks for the comments, we will address these in the next
      revision,<br>
      <br>
      Regards,<br>
      -Vinay.<br>
      <br>
      <br>
      On 1/11/13 2:27 PM, Kevin Gross wrote:<br>
    </div>
    <blockquote
cite="mid:CALw1_Q1x=BMG5Fstom2MBs1uFUoAGr4RZTwts=C=ugkGw+ROhA@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      Some comments on this:
      <div><br>
      </div>
      <div>Abstract:</div>
      <div><br>
      </div>
      <div>Add a bracketed reference to IEEE 1588-2008</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>Section 1</div>
      <div><br>
      </div>
      <div>s/defined to monitor, measure the performance/defined to
        monitor and measure the performance</div>
      <div><br>
      </div>
      <div>It is claimed that monitoring is not a supported&nbsp;function&nbsp;of
        this MIB but I have identified numerous versiables in the MIB
        which I would consider to be providing a monitoring function. If
        you need specific examples, let me know.</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>Section 1.1</div>
      <div><br>
      </div>
      <div>What in this MIB is profile dependent? I did not identify
        anything in my review. It would be&nbsp;desirable. if possible,&nbsp;&nbsp;to
        have a profile-independent MIB.</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>TEXTUAL-CONVENTION general issues</div>
      <div><br>
      </div>
      <div>Consider alphabetizing</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>ClockInstanceType TEXTUAL-CONVENTION definition</div>
      <div><br>
      </div>
      <div>Description requires elucidation or a reference.</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>ClockProfileType&nbsp;TEXTUAL-CONVENTION definition</div>
      <div><br>
      </div>
      <div>Consider using and OUI instead of an enumeration. IEEE
        1588-1588 requires an OUI be associated with each profile.</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>OBJECT-TYPE general issues</div>
      <div><br>
      </div>
      <div>Consider being consistent about repeating&nbsp;TEXTUAL-CONVENTION
        descriptions, explicitly referencing them or assuming readers
        will track down the reference without reminder.</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>ptpDomainClockPortsTotal&nbsp;<span style="font-size:1em">OBJECT-TYPE</span></div>
      <div><br>
      </div>
      <div>I assume this is the number of ports for the managed
        PTP-capable system (i.e. a router or switch). Suggest adding "in
        the system" to the description to clarify scope of count.</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>
        <pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">ptpbaseClockTimePropertiesDSTable OBJECT-TYPE</pre>
        <pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">
</pre>
        <pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">s/<span style="font-size:1em">clock Timeproperties </span><span style="font-size:1em">Datasets for/clock time properties datasets for</span></pre>
        <pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px"><span style="font-size:1em">
</span></pre>
        <pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px"><span style="font-size:1em">

</span></pre>
        <pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">PtpbaseClockTransDefaultDSEntry SEQUENCE</pre>
        <pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">
</pre>
        <pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">Use ClockDomainType textual convention instead of Integer32 for <span style="font-size:1em">ptpbaseClockTransDefaultDSPrimaryDomain</span></pre>
        <pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px"><span style="font-size:1em">
</span></pre>
        <pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px"><span style="font-size:1em">
</span></pre>
        <pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">PtpbaseClockPortEntry SEQUENCE</pre>
        <pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">
</pre>
        <pre class="newpage" style="margin-top:0px;margin-bottom:0px"><span style="font-size:1em">Change ptpbaseClockPortSyncOneStep to ptpbaseClockPortSyncTwoStep to match 1588 </span>semantics<span style="font-size:1em"> for this boolean</span></pre>
        <pre class="newpage" style="margin-top:0px;margin-bottom:0px"><span style="font-size:1em">
</span></pre>
        <pre class="newpage" style="margin-top:0px;margin-bottom:0px"><span style="font-size:1em">
</span></pre>
        <pre class="newpage" style="margin-top:0px;margin-bottom:0px"><pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">ptpbaseClockPortRunningEncapsulationType OBJECT-TYPE</pre><pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">
</pre><pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">Needs a textual convention or description of allowed values and their meanings</pre><pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">
</pre><pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">
</pre><pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">ptpbaseClockPortTransDSlogMinPdelayReqInt OBJECT-TYPE</pre><pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">
</pre><pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">Change to ClockIntervalBase2 type</pre><pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">
</pre><pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">
</pre><pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">Section 5</pre><pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">
</pre><pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px">Copy-paste error: "<span style="font-size:1em">creation and/or manipulation of tunnels"</span></pre><pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px"><span style="font-size:1em">
</span></pre>
<pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px"><span style="font-size:1em">
</span></pre><pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px"><span style="font-size:1em">Section 6</span></pre>
<pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px"><span style="font-size:1em">
</span></pre><pre class="newpage" style="font-size:1em;margin-top:0px;margin-bottom:0px"><span style="font-size:1em">To be added</span></pre>
</pre>
      </div>
      <div><br clear="all">
        <div>Kevin Gross<br>
          <div>+1-303-447-0517</div>
          <div>Media Network Consultant<br>
            <div>AVA Networks -&nbsp;<a moz-do-not-send="true"
                href="http://www.avanw.com/" target="_blank">www.AVAnw.com</a>,&nbsp;<a
                moz-do-not-send="true" href="http://www.X192.org"
                target="_blank">www.X192.org</a></div>
          </div>
        </div>
        <br>
        <br>
        <div class="gmail_quote">On Thu, Aug 2, 2012 at 12:58 PM, <span
            dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:internet-drafts@ietf.org" target="_blank">internet-drafts@ietf.org</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <br>
            A New Internet-Draft is available from the on-line
            Internet-Drafts directories.<br>
            &nbsp;This draft is a work item of the Timing over IP Connection
            and Transfer of Clock Working Group of the IETF.<br>
            <br>
            &nbsp; &nbsp; &nbsp; &nbsp; Title &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : Precision Time Protocol Version 2
            (PTPv2) Management Information Base<br>
            &nbsp; &nbsp; &nbsp; &nbsp; Author(s) &nbsp; &nbsp; &nbsp; : Vinay Shankarkumar<br>
            &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Laurent Montini<br>
            &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Tim Frost<br>
            &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Greg Dowd<br>
            &nbsp; &nbsp; &nbsp; &nbsp; Filename &nbsp; &nbsp; &nbsp; &nbsp;: draft-ietf-tictoc-ptp-mib-03.txt<br>
            &nbsp; &nbsp; &nbsp; &nbsp; Pages &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 65<br>
            &nbsp; &nbsp; &nbsp; &nbsp; Date &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 2012-07-31<br>
            <br>
            Abstract:<br>
            &nbsp; &nbsp;This memo defines a portion of the Management Information
            Base (MIB)<br>
            &nbsp; &nbsp;for use with network management protocols in TCP/IP-based
            internets.<br>
            &nbsp; &nbsp;In particular, it defines objects for managing networks
            using<br>
            &nbsp; &nbsp;Precision Time Protocol.<br>
            <br>
            &nbsp; &nbsp;This memo specifies a MIB module in a manner that is both
            compliant<br>
            &nbsp; &nbsp;to the SNMPv2 SMI, and semantically identical to the peer
            SNMPv1<br>
            &nbsp; &nbsp;definitions.<br>
            <br>
            <br>
            The IETF datatracker status page for this draft is:<br>
            <a moz-do-not-send="true"
              href="https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib"
              target="_blank">https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib</a><br>
            <br>
            There's also a htmlized version available at:<br>
            <a moz-do-not-send="true"
              href="http://tools.ietf.org/html/draft-ietf-tictoc-ptp-mib-03"
              target="_blank">http://tools.ietf.org/html/draft-ietf-tictoc-ptp-mib-03</a><br>
            <br>
            A diff from the previous version is available at:<br>
            <a moz-do-not-send="true"
              href="http://www.ietf.org/rfcdiff?url2=draft-ietf-tictoc-ptp-mib-03"
              target="_blank">http://www.ietf.org/rfcdiff?url2=draft-ietf-tictoc-ptp-mib-03</a><br>
            <br>
            <br>
            Internet-Drafts are also available by anonymous FTP at:<br>
            <a moz-do-not-send="true"
              href="ftp://ftp.ietf.org/internet-drafts/" target="_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
            <br>
            _______________________________________________<br>
            TICTOC mailing list<br>
            <a moz-do-not-send="true" href="mailto:TICTOC@ietf.org">TICTOC@ietf.org</a><br>
            <a moz-do-not-send="true"
              href="https://www.ietf.org/mailman/listinfo/tictoc"
              target="_blank">https://www.ietf.org/mailman/listinfo/tictoc</a><br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
TICTOC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:TICTOC@ietf.org">TICTOC@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/tictoc">https://www.ietf.org/mailman/listinfo/tictoc</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------000805030109090904050902--

From odonoghue@isoc.org  Thu Jan 24 01:14:15 2013
Return-Path: <odonoghue@isoc.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E26D521F87FE for <tictoc@ietfa.amsl.com>; Thu, 24 Jan 2013 01:14:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.299
X-Spam-Level: 
X-Spam-Status: No, score=-103.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id taF49odfNun7 for <tictoc@ietfa.amsl.com>; Thu, 24 Jan 2013 01:14:15 -0800 (PST)
Received: from smtp175.iad.emailsrvr.com (smtp175.iad.emailsrvr.com [207.97.245.175]) by ietfa.amsl.com (Postfix) with ESMTP id 1D54621F87D5 for <tictoc@ietf.org>; Thu, 24 Jan 2013 01:14:15 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp57.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 664D3F82DF; Thu, 24 Jan 2013 04:14:14 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp57.relay.iad1a.emailsrvr.com (Authenticated sender: odonoghue-AT-isoc.org) with ESMTPSA id 449D5F82DB;  Thu, 24 Jan 2013 04:14:14 -0500 (EST)
Message-ID: <5100FB66.2040202@isoc.org>
Date: Thu, 24 Jan 2013 04:14:14 -0500
From: Karen O'Donoghue <odonoghue@isoc.org>
Organization: ISOC
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "tictoc@ietf.org" <tictoc@ietf.org>,  NTP Working Group <ntpwg@lists.ntp.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [TICTOC] =?windows-1252?q?IEEE_P1588=99_Study_Group_=28SG=29_Call?= =?windows-1252?q?_for_Participation?=
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: odonoghue@isoc.org
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: Thu, 24 Jan 2013 09:14:16 -0000

Folks,

The kickoff of the IEEE 1588 activities that we discussed in November 
has been initiated. The first step is to develop a PAR. Details of the 
CFP are available at:

http://standards.ieee.org/email/2013_01_cfp1588_web.html

Regards,
Karen



From btv1==736c27320d5==darnold@symmetricom.com  Thu Jan 24 10:33:58 2013
Return-Path: <btv1==736c27320d5==darnold@symmetricom.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE29811E8099 for <tictoc@ietfa.amsl.com>; Thu, 24 Jan 2013 10:33:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.965
X-Spam-Level: 
X-Spam-Status: No, score=-1.965 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vlpl1Lt-08e4 for <tictoc@ietfa.amsl.com>; Thu, 24 Jan 2013 10:33:58 -0800 (PST)
Received: from mail5.symmetricom.com (mail5.symmetricom.com [69.25.98.10]) by ietfa.amsl.com (Postfix) with ESMTP id 2952F21F858E for <tictoc@ietf.org>; Thu, 24 Jan 2013 10:33:58 -0800 (PST)
X-ASG-Debug-ID: 1359052437-05bdbc4d9e246580001-4wH9i1
Received: from SJC-HUB-01.symmetricom.com ([192.168.10.171]) by mail5.symmetricom.com with ESMTP id duWCMnVQ6pEI6ZIG; Thu, 24 Jan 2013 10:33:57 -0800 (PST)
X-Barracuda-Envelope-From: darnold@symmetricom.com
X-ASG-Whitelist: Client
Received: from SJC-MBX-01.symmetricom.com ([169.254.1.133]) by SJC-HUB-01.symmetricom.com ([::1]) with mapi id 14.01.0289.001; Thu, 24 Jan 2013 10:33:56 -0800
From: Doug Arnold <darnold@symmetricom.com>
To: "odonoghue@isoc.org" <odonoghue@isoc.org>, "tictoc@ietf.org" <tictoc@ietf.org>, NTP Working Group <ntpwg@lists.ntp.org>
Thread-Topic: =?Windows-1252?Q?[TICTOC]_IEEE_P1588=99_Study_Group_(SG)_Call_for_Partici?= =?Windows-1252?Q?pation?=
X-ASG-Orig-Subj: =?Windows-1252?Q?RE:_[TICTOC]_IEEE_P1588=99_Study_Group_(SG)_Call_for_Par?= =?Windows-1252?Q?ticipation?=
Thread-Index: AQHN+hNIY9aCQ6Iz+kC2H5Igc4sM1JhYziDg
Date: Thu, 24 Jan 2013 18:33:55 +0000
Message-ID: <D2CC4074A4E35B43A4EE2CA7859D567B69356136@SJC-MBX-01.symmetricom.com>
References: <5100FB66.2040202@isoc.org>
In-Reply-To: <5100FB66.2040202@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.22.119]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.10.171]
X-Barracuda-Start-Time: 1359052437
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at symmetricom.com
X-Barracuda-BRTS-Status: 1
Subject: Re: [TICTOC] =?windows-1252?q?IEEE_P1588=99_Study_Group_=28SG=29_Call?= =?windows-1252?q?_for_Participation?=
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 24 Jan 2013 18:36:08 -0000

I would like to see multipath PTP as part of the PAR.  I encourage those of=
 you in TICTOC working on this to participate in the IEEE 1588 revision.

//Doug Arnold

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Karen O'Donoghue
Sent: Thursday, January 24, 2013 1:14 AM
To: tictoc@ietf.org; NTP Working Group
Subject: [TICTOC] IEEE P1588=99 Study Group (SG) Call for Participation

Folks,

The kickoff of the IEEE 1588 activities that we discussed in November=20
has been initiated. The first step is to develop a PAR. Details of the=20
CFP are available at:

http://standards.ieee.org/email/2013_01_cfp1588_web.html

Regards,
Karen


_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc

From internet-drafts@ietf.org  Thu Jan 31 14:36:57 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6032C21F853E; Thu, 31 Jan 2013 14:36:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29C1Q0IsvqCg; Thu, 31 Jan 2013 14:36:56 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3B6D21F8558; Thu, 31 Jan 2013 14:36:56 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20130131223656.5501.36611.idtracker@ietfa.amsl.com>
Date: Thu, 31 Jan 2013 14:36:56 -0800
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-ptp-mib-04.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 31 Jan 2013 22:36:57 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Timing over IP Connection and Transfer of=
 Clock Working Group of the IETF.

	Title           : Precision Time Protocol Version 2 (PTPv2) Management Inf=
ormation Base
	Author(s)       : Vinay Shankarkumar
                          Laurent Montini
                          Tim Frost
                          Greg Dowd
	Filename        : draft-ietf-tictoc-ptp-mib-04.txt
	Pages           : 76
	Date            : 2013-01-31

Abstract:
   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in TCP/IP-based internets.
   In particular, it defines objects for managing networks using
   Precision Time Protocol, specified in [IEEE 1588-2008].

   This memo specifies a MIB module in a manner that is both compliant
   to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
   definitions.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tictoc-ptp-mib-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tictoc-ptp-mib-04


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From brian@innovationslab.net  Thu Jan 31 16:54:51 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C763B21F89A4 for <tictoc@ietfa.amsl.com>; Thu, 31 Jan 2013 16:54:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iRwM4SGhDNwJ for <tictoc@ietfa.amsl.com>; Thu, 31 Jan 2013 16:54:50 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id EB38C21F8971 for <tictoc@ietf.org>; Thu, 31 Jan 2013 16:54:50 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 92B0A88164 for <tictoc@ietf.org>; Thu, 31 Jan 2013 16:54:50 -0800 (PST)
Received: from Littlejohn.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 386EA13000C for <tictoc@ietf.org>; Thu, 31 Jan 2013 16:54:50 -0800 (PST)
Message-ID: <510B1257.6040508@innovationslab.net>
Date: Thu, 31 Jan 2013 19:54:47 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: tictoc@ietf.org
References: <9904FB1B0159DA42B0B887B7FA8119CA07B447@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA07B447@AZ-FFEXMB04.global.avaya.com>
X-Forwarded-Message-Id: <9904FB1B0159DA42B0B887B7FA8119CA07B447@AZ-FFEXMB04.global.avaya.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: [TICTOC] Fwd: Call for Participation - IEEE P1588(tm) Study Group
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 01 Feb 2013 00:54:51 -0000

From: IEEE Standards Association [mailto:ieee-sa-exec@ieee.org]
Sent: Wednesday, January 23, 2013 5:57 AM
To: john-eidson@stanfordalumni.org
Subject: Call for Participation - IEEE P1588(tm) Study Group



   click here if you have trouble viewing this email





                   IEEE P1588™ Study Group (SG)
                   Call for Participation



                         The IEEE P1588™ Study Group (SG) announces a 
Call for Participation (CFP) to develop a Project Authorization Request 
(PAR) for the revision of IEEE 1588™ -2008, Standard for a Precision 
Clock Synchronization Protocol for Networked Measurement and Control 
Systems.

                         IEEE P1588 SG is sponsored by the 
Instrumentation and Measurement Society (IMS)/TC-9. IEEE 1588-2008 is 
also published as International Standard IEC/IEEE 61588, which was 
processed through subcommittee 65C: Industrial networks, of IEC 
technical committee 65: Industrial-process measurement, control and 
automation.

                         IEEE P1588 SG is seeking participants with a 
technical or commercial interest in IEEE 1588 -2008. We ask that you 
please share this CFP with any colleagues that are eligible to participate.

                         Participants are expected to adhere to the 
IEEE-SA guidelines for SG members, and IEEES-SA Patent Policy.

                         MEETING INFORMATION:

                         The first IEEE P1588, face-to-face SG meeting 
is scheduled for Tuesday and Wednesday, 2 and 3 April 2013 in 
Gaithersburg, MD, USA, at NIST. Attendees must register for this event 
no later than 13 February 2013.

                         Preliminary one hour teleconferences will be 
held on Friday 22 February, and Wednesday 6 March 2013 at 16:00 UTC 
(11AM EST). Anyone planning to attend the 2-3 April, face-to-face 
meeting must participate in at least one of the teleconferences.

                               PARTICIPATION:

                               To join the IEEE P1588 SG, we ask that 
you please:

                               - create an email (subject line: IEEE 
P1588 SG participation)
                               - include your name, organization, email, 
& phone number
                               - indicate whether you will be attending 
the 2-3 April meeting
                               - and submit to:

                               Silvana Rodrigues
                               IEEE P1588 Study Group
                               SG Secretary
                               silvana.rodrigues@idt.com


                               NOTE:
                               If you plan on attending the face-to-face 
meeting on 2-3 April, your email must be received no later than 13 
February 2013!



                         Participants will be expected to attend the 
Study Group's regular meetings. Times and agendas will be posted on the 
IEEE 1588 WG site. If you have further questions about the SG, feel free 
to contact:

                         Doug Arnold
                         email: darnold@symmetricom.com

                         John Eidson
                         email: john-eidson@stanfordalumni.org

                         Kang Lee
                         email:kang.lee@ieee.org

                         IEEE Standards Association
                         445 Hoes Lane
                         Piscataway, NJ 08854















                         STAND WITH US!
                         learn more about
                         OpenStand






                   Copyright 2013 IEEE-SA | IEEE-SA Home | Privacy & 
Security



                   click here to unsubscribe instantly














===
