
From nobody Fri Mar  3 15:58:13 2017
Return-Path: <agenda@ietf.org>
X-Original-To: tictoc@ietf.org
Delivered-To: tictoc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 912701299CE; Fri,  3 Mar 2017 15:55:26 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <tictoc-chairs@ietf.org>, <odonoghue@isoc.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148858532658.15846.1777084068468941148.idtracker@ietfa.amsl.com>
Date: Fri, 03 Mar 2017 15:55:26 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/wNosZmDVxp9QadPSxIDLTTtzm7Y>
Cc: tictoc@ietf.org, suresh.krishnan@ericsson.com
Subject: [TICTOC] tictoc - Requested session has been scheduled for IETF 98
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 03 Mar 2017 23:55:29 -0000

Dear Karen O&#39;Donoghue,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 

tictoc Session 1 (2:00:00)
    Monday, Afternoon Session I 1300-1500
    Room Name: Montreux 3 size: 80
    ---------------------------------------------
    

Special Note: Joint session with NTP


Request Information:


---------------------------------------------------------
Working Group Name: Timing over IP Connection and Transfer of Clock
Area Name: Internet Area
Session Requester: Karen O&#39;Donoghue

Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 30
Conflicts to Avoid: 
 First Priority: sacm oauth nfvrg bmwg cfrg saag trans mpls




People who must be present:
  Karen O&#39;Donoghue
  Suresh Krishnan
  Yaakov Stein
  Dieter Sibold

Resources Requested:
  Experimental room setup (boardroom and classroom) subject to availability

Special Requests:
  Please schedule a joint meeting with the NTP WG. 
---------------------------------------------------------


From nobody Wed Mar 15 15:16:16 2017
Return-Path: <rodney.cummings@ni.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 0DFEE129C48 for <tictoc@ietfa.amsl.com>; Wed, 15 Mar 2017 15:16:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nio365.onmicrosoft.com
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 FTXiEfL-6HZa for <tictoc@ietfa.amsl.com>; Wed, 15 Mar 2017 15:16:12 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0095.outbound.protection.outlook.com [104.47.40.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65579129C49 for <tictoc@ietf.org>; Wed, 15 Mar 2017 15:15:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nio365.onmicrosoft.com; s=selector1-ni-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=t5uAxa3ovJnP9omDoKNaN4RBeyJ005/EEyenO9/H7hA=; b=BE2BZiGRl3mT5kZNvZ+YxMAXbnk2sRIC2ZE+4YadFHrnKmux15mScZ4D7JOKU/JA6scN+2zsAjQ8f4Z4PivpTXWIgtvXMjv4ThdERCYnXX0+zGuGTkhYtuQN+UhBcu0PNzDTDrAcj1F6cfm3lZwPMxCxtOHNcOgucVErIAqiFcY=
Received: from MWHPR04MB0559.namprd04.prod.outlook.com (10.173.49.136) by MWHPR04MB0558.namprd04.prod.outlook.com (10.173.49.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.12; Wed, 15 Mar 2017 22:15:57 +0000
Received: from MWHPR04MB0559.namprd04.prod.outlook.com ([10.173.49.136]) by MWHPR04MB0559.namprd04.prod.outlook.com ([10.173.49.136]) with mapi id 15.01.0947.020; Wed, 15 Mar 2017 22:15:57 +0000
From: Rodney Cummings <rodney.cummings@ni.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: draft-ietf-tictoc-1588v2-yang and RFC7223
Thread-Index: AdKc5s0kzPwIdBTIQ8as3pK1nwg9XQ==
Date: Wed, 15 Mar 2017 22:15:57 +0000
Message-ID: <MWHPR04MB05594F190E0EB3E4083A886A92270@MWHPR04MB0559.namprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=ni.com;
x-originating-ip: [216.123.155.200]
x-ms-office365-filtering-correlation-id: b58114d0-2601-4c6a-9567-08d46bf0db15
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:MWHPR04MB0558;
x-microsoft-exchange-diagnostics: 1; MWHPR04MB0558; 7:3d5v3Xp/MANps8pe89KvtLvTXUB5E7uCe2ezFae6QRG7uUJy9R/b2rGc6nXPmw/i1UHoS78yVZVOJs8FLvVC0BenuuCB/rddAYNLQb10h1N5K7VO1zhgcYdMAzlE6PNJavinzNfseUqhK74HtQY7UnleEjvLsCTTby3av9SDVU8zwV6M2Nt4VnnXm0LOjyibEB+sTqcRfPmKgQyQS5obd/81zStt4VR8a3v7tXigSBRSFEQDGglCRjrg+184ljzMtay0MozNwZpe2Gp5ehGuJB9sPXnsr8VeUEkNQqObH2oXMCFCGLpr40534bIxqVP6N/gEkbBmdtXQj5/QI3jBig==
x-microsoft-antispam-prvs: <MWHPR04MB0558A35E90A7F415267B2F1192270@MWHPR04MB0558.namprd04.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(100405760836317);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123558025)(20161123560025)(20161123555025)(20161123562025)(20161123564025)(6072148); SRVR:MWHPR04MB0558; BCL:0; PCL:0; RULEID:; SRVR:MWHPR04MB0558; 
x-forefront-prvs: 02475B2A01
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39450400003)(53754006)(6916009)(33656002)(2351001)(7696004)(50986999)(66066001)(53936002)(5660300001)(86362001)(230783001)(122556002)(2501003)(3660700001)(54356999)(5640700003)(7736002)(8676002)(25786008)(74316002)(2906002)(6116002)(77096006)(189998001)(110136004)(305945005)(38730400002)(2900100001)(6506006)(99286003)(8936002)(9686003)(6436002)(1730700003)(81166006)(102836003)(966004)(3280700002)(3846002)(55016002)(6306002); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR04MB0558; H:MWHPR04MB0559.namprd04.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ni.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Mar 2017 22:15:57.5988 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 87ba1f9a-44cd-43a6-b008-6fdb45a5204e
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR04MB0558
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/I-VWD0QdKBhjwuQdwLNmNmNx3wk>
Subject: [TICTOC] draft-ietf-tictoc-1588v2-yang and RFC7223
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 15 Mar 2017 22:16:15 -0000

Hello all,

Some questions have come up in recent meetings of IEEE 1588 and IEEE 802.1 =
working groups that are relevant to the TICTOC project draft-ietf-tictoc-15=
88v2-yang. I would like to get some feedback from TICTOC to help determine =
if a change is needed for draft-ietf-tictoc-1588v2-yang.

1588-2008 has the concept of a "port", and for a 1588 product with two or m=
ore ports, 1588 specifies the transfer of time between these ports. The 158=
8-2008 specifications for the port are "logical", in that they are independ=
ent of any specific transport or media. For example, the 1588 port can use =
a layer-2 802 mapping, or the port can use a UDP mapping.

When a 1588-2008 product is managed (such as with YANG), the management cli=
ent is likely to ask:
	How do I find the "real" port that a 1588 "logical" port is using?
For example, if the UDP mapping is used, I might want to find relevant IP a=
ddresses, and then go down in the data models to find relevant MAC addresse=
s, 802.3 link speeds, and so on.

The current consensus in the 1588 working group is that although this quest=
ion is important, since 1588 is transport-independent, the answer cannot be=
 fully specified in the 1588 data sets (i.e. information model). The actual=
 management data model (e.g. YANG, MIB, 1588 management protocol) potential=
ly has better connections to the "real" port, and therefore 1588 defers thi=
s topic to each management data model. In other words, the 1588 standard it=
self will not fully answer this question, but the YANG (i.e. draft-ietf-tic=
toc-1588v2-yang) is expected to answer the question to the best of its abil=
ity.

This question came up in a recent discussion in IEEE 802.1, relative to the=
ir profile of 1588, 802.1AS. Refer to slide 5 of:
	http://www.ieee802.org/1/files/public/docs2017/as-gutierrez-yang-0317-v01.=
pdf
This presentation suggests that the 1588 port (called a "TAS port" in 802.1=
AS) should be done as an augment of the RFC7223 interface.

The current consensus in IEEE 802.1 is that their profile 802.1AS will defe=
r to the 1588 YANG module (draft-ietf-tictoc-1588v2-yang) for this decision=
. The YANG module for 802.1AS will augment the 1588 YANG module as describe=
d at the end of section 1 of draft-ietf-tictoc-1588v2-yang.

So... I think we need to select from one of three options for draft-ietf-ti=
ctoc-1588v2-yang:

Option 1: 1588 port augments RFC7223 interface
--

Although this is a reasonable suggestion, it works under the assumption tha=
t a 1588 port "is a type of" RFC7223 interface. That implies that the 1588 =
port has a place in the interface stack represented by higher-layer-if and =
lower-layer-if.

I would argue that a 1588 port "uses" an RFC7223 interface, and the 1588 po=
rt does not belong in the interface stack. 1588 is a higher-layer protocol,=
 and in that respect, it is more analogous to protocols like TCP and UDP, a=
nd not the protocols listed in iana-if-type.yang.

If we decide to implement this option, we need to do it in the first 1588 Y=
ANG (draft-ietf-tictoc-1588v2-yang). I assume that we cannot change the 158=
8 port from non-augment to augment in a future revision of the 1588 YANG.

Option 2: 1588 port contains a reference to an RFC7223 interface
--

1588 requires a configured interface for each 1588 port. By using interface=
-ref instead of an interface augment, this establishes the relationship as =
"uses".

This would be added to draft-ietf-tictoc-1588v2-yang as a new leaf in group=
ing port-ds-entry, such as:
	leaf interface-reference {
		type if:interface-ref;
		description
			"Reference to the configured interface that is used by
			this PTP Port (see RFC 7223).";
       }
This enables the management client to find the interface that the 1588 (PTP=
) port is using. The management client can also traverse up/down the interf=
ace stack to find additional information.=20

Option 3: Do nothing in draft-ietf-tictoc-1588v2-yang
--

This is what we have so far.

Presumably a future revision of the 1588 YANG could decide to implement opt=
ion 2, but not option 1.

Question: Which option should we use for draft-ietf-tictoc-1588v2-yang?
--

I recommend option 2.

Previously I was fine with option 3, but since this is an open question in =
the 1588 community, it is best to resolve it in the first 1588 YANG module.

At a minimum, we need to decide if we are doing option 1, because that deci=
sion cannot be changed in future 1588 YANG module revisions.

This decision is not related to the 1588 data set specifications (2008 or f=
uture), because current 1588 consensus is that it is entirely within the sc=
ope of the 1588 YANG module.

Thanks everyone,
Rodney Cummings







 =20



From nobody Fri Mar 17 05:08:57 2017
Return-Path: <jiangyuanlong@huawei.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 6ADA9127058 for <tictoc@ietfa.amsl.com>; Fri, 17 Mar 2017 05:08:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 WW_UoUzNjf9y for <tictoc@ietfa.amsl.com>; Fri, 17 Mar 2017 05:08:52 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E83B126C7A for <tictoc@ietf.org>; Fri, 17 Mar 2017 05:08:52 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml708-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DJB66072; Fri, 17 Mar 2017 12:08:49 +0000 (GMT)
Received: from SZXEMA419-HUB.china.huawei.com (10.82.72.37) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 17 Mar 2017 12:08:49 +0000
Received: from SZXEMA506-MBS.china.huawei.com ([169.254.4.67]) by SZXEMA419-HUB.china.huawei.com ([10.82.72.37]) with mapi id 14.03.0235.001; Fri, 17 Mar 2017 20:08:36 +0800
From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: Rodney Cummings <rodney.cummings@ni.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: draft-ietf-tictoc-1588v2-yang and RFC7223
Thread-Index: AdKc5s0kzPwIdBTIQ8as3pK1nwg9XQCLX4AQ
Date: Fri, 17 Mar 2017 12:08:36 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB1D02D@szxema506-mbs.china.huawei.com>
References: <MWHPR04MB05594F190E0EB3E4083A886A92270@MWHPR04MB0559.namprd04.prod.outlook.com>
In-Reply-To: <MWHPR04MB05594F190E0EB3E4083A886A92270@MWHPR04MB0559.namprd04.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.74.203.119]
Content-Type: text/plain; charset="utf-7"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090204.58CBD1D2.00CB, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.4.67, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: fdd20a1826ce475926cb955090884897
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/CiBsezc-cNugP3JOcL2_mAS9R9k>
Subject: Re: [TICTOC] draft-ietf-tictoc-1588v2-yang and RFC7223
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Mar 2017 12:08:55 -0000

Hi Rodney,

Thank you very much for bringing up the head-up situation in the IEEE.=20
I wonder whether RFC7223 interface solely specifies Ethernet interfaces (th=
e examples in this RFC seems give a positive answer).=20
People may also want to support OTN, PON and other physical ports (as I am =
aware, IEEE 1588 PTP is supported by these physical layers now).
Therefore, I prefer to your Option 2 and would like to reference to an RFC7=
223 interface just as an example.=20
In this way, other interfaces may also be introduced quite easily.

Cheers,
Yuanlong

-----Original Message-----
From: TICTOC +AFs-mailto:tictoc-bounces+AEA-ietf.org+AF0- On Behalf Of Rodn=
ey Cummings
Sent: Thursday, March 16, 2017 6:16 AM
To: tictoc+AEA-ietf.org
Subject: +AFs-TICTOC+AF0- draft-ietf-tictoc-1588v2-yang and RFC7223

Hello all,

Some questions have come up in recent meetings of IEEE 1588 and IEEE 802.1 =
working groups that are relevant to the TICTOC project draft-ietf-tictoc-15=
88v2-yang. I would like to get some feedback from TICTOC to help determine =
if a change is needed for draft-ietf-tictoc-1588v2-yang.

1588-2008 has the concept of a +ACI-port+ACI-, and for a 1588 product with =
two or more ports, 1588 specifies the transfer of time between these ports.=
 The 1588-2008 specifications for the port are +ACI-logical+ACI-, in that t=
hey are independent of any specific transport or media. For example, the 15=
88 port can use a layer-2 802 mapping, or the port can use a UDP mapping.

When a 1588-2008 product is managed (such as with YANG), the management cli=
ent is likely to ask:
	How do I find the +ACI-real+ACI- port that a 1588 +ACI-logical+ACI- port i=
s using?
For example, if the UDP mapping is used, I might want to find relevant IP a=
ddresses, and then go down in the data models to find relevant MAC addresse=
s, 802.3 link speeds, and so on.

The current consensus in the 1588 working group is that although this quest=
ion is important, since 1588 is transport-independent, the answer cannot be=
 fully specified in the 1588 data sets (i.e. information model). The actual=
 management data model (e.g. YANG, MIB, 1588 management protocol) potential=
ly has better connections to the +ACI-real+ACI- port, and therefore 1588 de=
fers this topic to each management data model. In other words, the 1588 sta=
ndard itself will not fully answer this question, but the YANG (i.e. draft-=
ietf-tictoc-1588v2-yang) is expected to answer the question to the best of =
its ability.

This question came up in a recent discussion in IEEE 802.1, relative to the=
ir profile of 1588, 802.1AS. Refer to slide 5 of:
	http://www.ieee802.org/1/files/public/docs2017/as-gutierrez-yang-0317-v01.=
pdf
This presentation suggests that the 1588 port (called a +ACI-TAS port+ACI- =
in 802.1AS) should be done as an augment of the RFC7223 interface.

The current consensus in IEEE 802.1 is that their profile 802.1AS will defe=
r to the 1588 YANG module (draft-ietf-tictoc-1588v2-yang) for this decision=
. The YANG module for 802.1AS will augment the 1588 YANG module as describe=
d at the end of section 1 of draft-ietf-tictoc-1588v2-yang.

So... I think we need to select from one of three options for draft-ietf-ti=
ctoc-1588v2-yang:

Option 1: 1588 port augments RFC7223 interface
--

Although this is a reasonable suggestion, it works under the assumption tha=
t a 1588 port +ACI-is a type of+ACI- RFC7223 interface. That implies that t=
he 1588 port has a place in the interface stack represented by higher-layer=
-if and lower-layer-if.

I would argue that a 1588 port +ACI-uses+ACI- an RFC7223 interface, and the=
 1588 port does not belong in the interface stack. 1588 is a higher-layer p=
rotocol, and in that respect, it is more analogous to protocols like TCP an=
d UDP, and not the protocols listed in iana-if-type.yang.

If we decide to implement this option, we need to do it in the first 1588 Y=
ANG (draft-ietf-tictoc-1588v2-yang). I assume that we cannot change the 158=
8 port from non-augment to augment in a future revision of the 1588 YANG.

Option 2: 1588 port contains a reference to an RFC7223 interface
--

1588 requires a configured interface for each 1588 port. By using interface=
-ref instead of an interface augment, this establishes the relationship as =
+ACI-uses+ACI-.

This would be added to draft-ietf-tictoc-1588v2-yang as a new leaf in group=
ing port-ds-entry, such as:
	leaf interface-reference +AHs-
		type if:interface-ref+ADs-
		description
			+ACI-Reference to the configured interface that is used by
			this PTP Port (see RFC 7223).+ACIAOw-
       +AH0-
This enables the management client to find the interface that the 1588 (PTP=
) port is using. The management client can also traverse up/down the interf=
ace stack to find additional information.=20

Option 3: Do nothing in draft-ietf-tictoc-1588v2-yang
--

This is what we have so far.

Presumably a future revision of the 1588 YANG could decide to implement opt=
ion 2, but not option 1.

Question: Which option should we use for draft-ietf-tictoc-1588v2-yang?
--

I recommend option 2.

Previously I was fine with option 3, but since this is an open question in =
the 1588 community, it is best to resolve it in the first 1588 YANG module.

At a minimum, we need to decide if we are doing option 1, because that deci=
sion cannot be changed in future 1588 YANG module revisions.

This decision is not related to the 1588 data set specifications (2008 or f=
uture), because current 1588 consensus is that it is entirely within the sc=
ope of the 1588 YANG module.

Thanks everyone,
Rodney Cummings







 =20


+AF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF=
8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw-
TICTOC mailing list
TICTOC+AEA-ietf.org
https://www.ietf.org/mailman/listinfo/tictoc


From nobody Fri Mar 17 05:28:27 2017
Return-Path: <rodney.cummings@ni.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 5164B12932A for <tictoc@ietfa.amsl.com>; Fri, 17 Mar 2017 05:28:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.911
X-Spam-Level: 
X-Spam-Status: No, score=-2.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nio365.onmicrosoft.com
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 F2pQhpz2toZ3 for <tictoc@ietfa.amsl.com>; Fri, 17 Mar 2017 05:28:23 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0109.outbound.protection.outlook.com [104.47.33.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 283371292AE for <tictoc@ietf.org>; Fri, 17 Mar 2017 05:28:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nio365.onmicrosoft.com; s=selector1-ni-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=vRKHrgxAW9n2mc9McN8Ogmm/AqiqHWNHcjKg5m9+uR0=; b=LDSF17aPr1i60yJFmPCqHVAUYPOnzov4Lnqp8Ea2/z7QpphDHzlrHS0l92s5ISGcYKoZtCmatO4G2dclPgRXNsXBSVBQ3e3JdOQiU4SiqyW7+DfccgkCzSTkLJFbApyMd0hnNUyiagcUnQyio3PgSOdQubio05d/ahgNeXbLpMo=
Received: from MWHPR04MB0559.namprd04.prod.outlook.com (10.173.49.136) by MWHPR04MB0559.namprd04.prod.outlook.com (10.173.49.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.12; Fri, 17 Mar 2017 12:28:21 +0000
Received: from MWHPR04MB0559.namprd04.prod.outlook.com ([10.173.49.136]) by MWHPR04MB0559.namprd04.prod.outlook.com ([10.173.49.136]) with mapi id 15.01.0947.020; Fri, 17 Mar 2017 12:28:21 +0000
From: Rodney Cummings <rodney.cummings@ni.com>
To: Jiangyuanlong <jiangyuanlong@huawei.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: draft-ietf-tictoc-1588v2-yang and RFC7223
Thread-Index: AdKc5s0kzPwIdBTIQ8as3pK1nwg9XQCLX4AQAAE6IeA=
Date: Fri, 17 Mar 2017 12:28:20 +0000
Message-ID: <MWHPR04MB0559C149978B87D3FCF5C17092390@MWHPR04MB0559.namprd04.prod.outlook.com>
References: <MWHPR04MB05594F190E0EB3E4083A886A92270@MWHPR04MB0559.namprd04.prod.outlook.com> <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB1D02D@szxema506-mbs.china.huawei.com>
In-Reply-To: <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB1D02D@szxema506-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;huawei.com; dmarc=none action=none header.from=ni.com;
x-originating-ip: [204.239.253.216]
x-ms-office365-filtering-correlation-id: f46e2c87-10c4-4dde-af98-08d46d311958
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:MWHPR04MB0559;
x-microsoft-exchange-diagnostics: 1; MWHPR04MB0559; 7:xVZujn488qAG0230ECmQ/nNgTeGSGT3XWYYiPNtsO9RYrV00YixKp6aES/L6cFaV67kg7iNHEpEGZ9LmirnKjg85SN/yQDi9BjIac7afLI8AWorFq1//HJSKTcSud/9tYDECljUnneFg86sw39JeHSzbQ4DoC5TppUpjxjjaXKHSNErenIN+kwza2m3REquCeRjmzP/NwzXH7DWmPbe/HYM+luKtK40uI3qnTdbTmoTWPjOYjSXxWM0LzrUnHsJAT8qp8c/MYjZOFLC19yVGIQ+Ro+ha40MI+ixl3/x65rFD9BvWtAaSGEhOUUyIU7avz/3NrWHHIetmjfUXnw0SwA==
x-microsoft-antispam-prvs: <MWHPR04MB055937E056EC2C752E4BCC1A92390@MWHPR04MB0559.namprd04.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(50582790962513)(100405760836317)(1591387915157); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123564025)(20161123562025)(20161123558025)(20161123560025)(20161123555025)(6072148); SRVR:MWHPR04MB0559; BCL:0; PCL:0; RULEID:; SRVR:MWHPR04MB0559; 
x-forefront-prvs: 0249EFCB0B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39450400003)(377454003)(53754006)(13464003)(54094003)(45984002)(6436002)(230783001)(102836003)(229853002)(6246003)(7696004)(50986999)(8676002)(966004)(4326008)(53546008)(81166006)(53936002)(38730400002)(122556002)(189998001)(2906002)(8936002)(2900100001)(6116002)(33656002)(76176999)(54356999)(1720100001)(25786008)(55016002)(66066001)(6506006)(5660300001)(2950100002)(74316002)(7736002)(3280700002)(77096006)(2501003)(9686003)(3846002)(99286003)(86362001)(3660700001)(305945005)(6306002); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR04MB0559; H:MWHPR04MB0559.namprd04.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-7"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ni.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Mar 2017 12:28:20.8266 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 87ba1f9a-44cd-43a6-b008-6fdb45a5204e
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR04MB0559
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/byFxQ3ale7yoy09tw8XxBElxoa0>
Subject: Re: [TICTOC] draft-ietf-tictoc-1588v2-yang and RFC7223
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Mar 2017 12:28:26 -0000

Thanks Yuanlong,

When we discussed it this week, people in 802.1 seemed to agree with Option=
 2 as well, but then again... they are PHY/switch vendors and not really YA=
NG experts.

I think Marina assumed Option 1 because that is what the 802.1 +ACI-bridge-=
port+ACI- YANG does. But... I think Option 1 makes sense there, because the=
 +ACI-bridge-port+ACI- represents the MAC layer of the physical port.

The IANA interface types do have PON and OTN:
	https://www.iana.org/assignments/iana-if-type-yang/iana-if-type-yang
but I think the point is that those are intended to be hardware. A 1588 por=
t seems more like a logical software concept.

I wonder if maybe we should post a link to this TICTOC question to the NETM=
OD mailing list?

I assume the authors of RFC7223 participate in NETMOD but probably not TICT=
OC.

Rodney

+AD4- -----Original Message-----
+AD4- From: Jiangyuanlong +AFs-mailto:jiangyuanlong+AEA-huawei.com+AF0-
+AD4- Sent: Friday, March 17, 2017 7:09 AM
+AD4- To: Rodney Cummings +ADs- tictoc+AEA-ietf.org
+AD4- Cc: liuxian (C)
+AD4- Subject: RE: draft-ietf-tictoc-1588v2-yang and RFC7223
+AD4-=20
+AD4- Hi Rodney,
+AD4-=20
+AD4- Thank you very much for bringing up the head-up situation in the IEEE=
.
+AD4- I wonder whether RFC7223 interface solely specifies Ethernet interfac=
es
+AD4- (the examples in this RFC seems give a positive answer).
+AD4- People may also want to support OTN, PON and other physical ports (as=
 I am
+AD4- aware, IEEE 1588 PTP is supported by these physical layers now).
+AD4- Therefore, I prefer to your Option 2 and would like to reference to a=
n
+AD4- RFC7223 interface just as an example.
+AD4- In this way, other interfaces may also be introduced quite easily.
+AD4-=20
+AD4- Cheers,
+AD4- Yuanlong
+AD4-=20
+AD4- -----Original Message-----
+AD4- From: TICTOC +AFs-mailto:tictoc-bounces+AEA-ietf.org+AF0- On Behalf O=
f Rodney Cummings
+AD4- Sent: Thursday, March 16, 2017 6:16 AM
+AD4- To: tictoc+AEA-ietf.org
+AD4- Subject: +AFs-TICTOC+AF0- draft-ietf-tictoc-1588v2-yang and RFC7223
+AD4-=20
+AD4- Hello all,
+AD4-=20
+AD4- Some questions have come up in recent meetings of IEEE 1588 and IEEE =
802.1
+AD4- working groups that are relevant to the TICTOC project draft-ietf-tic=
toc-
+AD4- 1588v2-yang. I would like to get some feedback from TICTOC to help
+AD4- determine if a change is needed for draft-ietf-tictoc-1588v2-yang.
+AD4-=20
+AD4- 1588-2008 has the concept of a +ACI-port+ACI-, and for a 1588 product=
 with two or
+AD4- more ports, 1588 specifies the transfer of time between these ports. =
The
+AD4- 1588-2008 specifications for the port are +ACI-logical+ACI-, in that =
they are
+AD4- independent of any specific transport or media. For example, the 1588=
 port
+AD4- can use a layer-2 802 mapping, or the port can use a UDP mapping.
+AD4-=20
+AD4- When a 1588-2008 product is managed (such as with YANG), the manageme=
nt
+AD4- client is likely to ask:
+AD4- 	How do I find the +ACI-real+ACI- port that a 1588 +ACI-logical+ACI- =
port is using?
+AD4- For example, if the UDP mapping is used, I might want to find relevan=
t IP
+AD4- addresses, and then go down in the data models to find relevant MAC
+AD4- addresses, 802.3 link speeds, and so on.
+AD4-=20
+AD4- The current consensus in the 1588 working group is that although this
+AD4- question is important, since 1588 is transport-independent, the answe=
r
+AD4- cannot be fully specified in the 1588 data sets (i.e. information mod=
el).
+AD4- The actual management data model (e.g. YANG, MIB, 1588 management
+AD4- protocol) potentially has better connections to the +ACI-real+ACI- po=
rt, and
+AD4- therefore 1588 defers this topic to each management data model. In ot=
her
+AD4- words, the 1588 standard itself will not fully answer this question, =
but
+AD4- the YANG (i.e. draft-ietf-tictoc-1588v2-yang) is expected to answer t=
he
+AD4- question to the best of its ability.
+AD4-=20
+AD4- This question came up in a recent discussion in IEEE 802.1, relative =
to
+AD4- their profile of 1588, 802.1AS. Refer to slide 5 of:
+AD4- 	http://www.ieee802.org/1/files/public/docs2017/as-gutierrez-yang-
+AD4- 0317-v01.pdf
+AD4- This presentation suggests that the 1588 port (called a +ACI-TAS port=
+ACI- in
+AD4- 802.1AS) should be done as an augment of the RFC7223 interface.
+AD4-=20
+AD4- The current consensus in IEEE 802.1 is that their profile 802.1AS wil=
l
+AD4- defer to the 1588 YANG module (draft-ietf-tictoc-1588v2-yang) for thi=
s
+AD4- decision. The YANG module for 802.1AS will augment the 1588 YANG modu=
le as
+AD4- described at the end of section 1 of draft-ietf-tictoc-1588v2-yang.
+AD4-=20
+AD4- So... I think we need to select from one of three options for draft-i=
etf-
+AD4- tictoc-1588v2-yang:
+AD4-=20
+AD4- Option 1: 1588 port augments RFC7223 interface
+AD4- --
+AD4-=20
+AD4- Although this is a reasonable suggestion, it works under the assumpti=
on
+AD4- that a 1588 port +ACI-is a type of+ACI- RFC7223 interface. That impli=
es that the
+AD4- 1588 port has a place in the interface stack represented by higher-la=
yer-
+AD4- if and lower-layer-if.
+AD4-=20
+AD4- I would argue that a 1588 port +ACI-uses+ACI- an RFC7223 interface, a=
nd the 1588
+AD4- port does not belong in the interface stack. 1588 is a higher-layer
+AD4- protocol, and in that respect, it is more analogous to protocols like=
 TCP
+AD4- and UDP, and not the protocols listed in iana-if-type.yang.
+AD4-=20
+AD4- If we decide to implement this option, we need to do it in the first =
1588
+AD4- YANG (draft-ietf-tictoc-1588v2-yang). I assume that we cannot change =
the
+AD4- 1588 port from non-augment to augment in a future revision of the 158=
8
+AD4- YANG.
+AD4-=20
+AD4- Option 2: 1588 port contains a reference to an RFC7223 interface
+AD4- --
+AD4-=20
+AD4- 1588 requires a configured interface for each 1588 port. By using
+AD4- interface-ref instead of an interface augment, this establishes the
+AD4- relationship as +ACI-uses+ACI-.
+AD4-=20
+AD4- This would be added to draft-ietf-tictoc-1588v2-yang as a new leaf in
+AD4- grouping port-ds-entry, such as:
+AD4- 	leaf interface-reference +AHs-
+AD4- 		type if:interface-ref+ADs-
+AD4- 		description
+AD4- 			+ACI-Reference to the configured interface that is used by
+AD4- 			this PTP Port (see RFC 7223).+ACIAOw-
+AD4-        +AH0-
+AD4- This enables the management client to find the interface that the 158=
8
+AD4- (PTP) port is using. The management client can also traverse up/down =
the
+AD4- interface stack to find additional information.
+AD4-=20
+AD4- Option 3: Do nothing in draft-ietf-tictoc-1588v2-yang
+AD4- --
+AD4-=20
+AD4- This is what we have so far.
+AD4-=20
+AD4- Presumably a future revision of the 1588 YANG could decide to impleme=
nt
+AD4- option 2, but not option 1.
+AD4-=20
+AD4- Question: Which option should we use for draft-ietf-tictoc-1588v2-yan=
g?
+AD4- --
+AD4-=20
+AD4- I recommend option 2.
+AD4-=20
+AD4- Previously I was fine with option 3, but since this is an open questi=
on in
+AD4- the 1588 community, it is best to resolve it in the first 1588 YANG
+AD4- module.
+AD4-=20
+AD4- At a minimum, we need to decide if we are doing option 1, because tha=
t
+AD4- decision cannot be changed in future 1588 YANG module revisions.
+AD4-=20
+AD4- This decision is not related to the 1588 data set specifications (200=
8 or
+AD4- future), because current 1588 consensus is that it is entirely within=
 the
+AD4- scope of the 1588 YANG module.
+AD4-=20
+AD4- Thanks everyone,
+AD4- Rodney Cummings
+AD4-=20
+AD4-=20
+AD4-=20
+AD4-=20
+AD4-=20
+AD4-=20
+AD4-=20
+AD4-=20
+AD4-=20
+AD4-=20
+AD4- +AF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8A=
XwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw-
+AD4- TICTOC mailing list
+AD4- TICTOC+AEA-ietf.org
+AD4- https://www.ietf.org/mailman/listinfo/tictoc


From nobody Fri Mar 17 12:55:54 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tictoc@ietf.org
Delivered-To: tictoc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F1B5112940A; Fri, 17 Mar 2017 12:55:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: tictoc@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148978054392.13054.7913206450236177476@ietfa.amsl.com>
Date: Fri, 17 Mar 2017 12:55:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/BY40HKuh1Hs7O4g3Ktk_aggzH5w>
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-ptp-mib-12.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Mar 2017 19:55:44 -0000

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 of the IETF.

        Title           : Precision Time Protocol Version 2 (PTPv2) Management Information Base
        Authors         : Vinay Shankarkumar
                          Laurent Montini
                          Tim Frost
                          Greg Dowd
	Filename        : draft-ietf-tictoc-ptp-mib-12.txt
	Pages           : 64
	Date            : 2017-03-17

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 (PTP), specified in IEEE Std. 1588(TM)-2008.

   This memo specifies a MIB module in a manner that is both compliant
   to the SMIv2, and semantically identical to the peer SMIv1
   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:
https://tools.ietf.org/html/draft-ietf-tictoc-ptp-mib-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-tictoc-ptp-mib-12


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Wed Mar 22 07:24:43 2017
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: tictoc@ietf.org
Delivered-To: tictoc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 446F9131736; Wed, 22 Mar 2017 06:33:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.48.1
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, draft-ietf-tictoc-ptp-mib@ietf.org, suresh.krishnan@ericsson.com, tictoc-chairs@ietf.org, tictoc@ietf.org, kodonog@pobox.com, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <149018959227.10536.8340563517794730248.idtracker@ietfa.amsl.com>
Date: Wed, 22 Mar 2017 06:33:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/DOIyjksfpo9d_09NO9PR454rx84>
Subject: [TICTOC] Protocol Action: 'Precision Time Protocol Version 2 (PTPv2) Management Information Base' to Proposed Standard (draft-ietf-tictoc-ptp-mib-12.txt)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 22 Mar 2017 13:33:12 -0000

The IESG has approved the following document:
- 'Precision Time Protocol Version 2 (PTPv2) Management Information
Base'
  (draft-ietf-tictoc-ptp-mib-12.txt) as Proposed Standard

This document is the product of the Timing over IP Connection and
Transfer of Clock Working Group.

The IESG contact persons are Suresh Krishnan and Terry Manderson.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/





Technical Summary: 

This document defines objects for managing networks using the Precision Time Protocol, specified in IEEE Std. 1588(TM)-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. This MIB is an interim solution until the IEEE 1588 Technical Committee completes its efforts. 

Working Group Summary:

The document has clear working group consensus for publication, and has been reviewed by several WG participants since its initial adoption as a working group item. 
 
Document Quality:
 
This document has been reviewed and revised many times. It has been reviewed externally by members of the IEEE 1588 community and by MIB experts. 
 
Personnel: 

Karen O'Donoghue is acting as the Document Shepherd.  Suresh Krishnan is the Responsible Area Director.




RFC Editor Note

OLD:
            MAC     Media Access Control
                    according to [IEEE 802.3-2008]

NEW:
            MAC     Media Access Control
                    according to [IEEE 802.3-2015]

OLD:
   [IEEE 802.3-2012] "IEEE Standard for Ethernet", IEEE Std. 802.3 -
   2015, 3 September 2015

NEW:
   [IEEE 802.3-2015] "IEEE Standard for Ethernet", IEEE Std. 802.3 -
   2015, 3 September 2015

