Re: [TICTOC] RFC 8575 on YANG Data Model for the Precision Time Protocol (PTP)

Rodney Cummings <rodney.cummings@ni.com> Wed, 08 May 2019 18:17 UTC

Return-Path: <prvs=60312b83ab=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 A41441200F1 for <tictoc@ietfa.amsl.com>; Wed, 8 May 2019 11:17:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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 OeIaxhTmKYD6 for <tictoc@ietfa.amsl.com>; Wed, 8 May 2019 11:17:16 -0700 (PDT)
Received: from mx0b-00010702.pphosted.com (mx0a-00010702.pphosted.com [148.163.156.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A105F120025 for <tictoc@ietf.org>; Wed, 8 May 2019 11:17:16 -0700 (PDT)
Received: from pps.filterd (m0098780.ppops.net [127.0.0.1]) by mx0a-00010702.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x48I5bRr004860; Wed, 8 May 2019 13:17:16 -0500
Received: from nam05-by2-obe.outbound.protection.outlook.com (mail-by2nam05lp2052.outbound.protection.outlook.com [104.47.50.52]) by mx0a-00010702.pphosted.com with ESMTP id 2sbwdhhj96-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 08 May 2019 13:17:16 -0500
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:X-MS-Exchange-SenderADCheck; bh=JcLcth/IphSd3/YqAI9uHokZU+xvX69AM+a1NZrNG7I=; b=T0qXxgaf3BhxOAhdcOkrE7R257pDz5uKyoAUbx2J4KA5mZbU+fb+CbdlmbfblQ6PjzFhBr/XFc8TKp/VTCjqNEV7UUay7k8nFwymbhdNIauZebhBSctB0F91PxTJmz9Nl4eeDXsxAb//8YvAvgHc8wG3NOMHGVgPToYE7QRnvBI=
Received: from CY4PR04MB1127.namprd04.prod.outlook.com (10.173.193.136) by CY4PR04MB0806.namprd04.prod.outlook.com (10.172.138.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1856.12; Wed, 8 May 2019 18:17:14 +0000
Received: from CY4PR04MB1127.namprd04.prod.outlook.com ([fe80::384c:f9ab:67e6:30fa]) by CY4PR04MB1127.namprd04.prod.outlook.com ([fe80::384c:f9ab:67e6:30fa%5]) with mapi id 15.20.1856.012; Wed, 8 May 2019 18:17:14 +0000
From: Rodney Cummings <rodney.cummings@ni.com>
To: "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: RFC 8575 on YANG Data Model for the Precision Time Protocol (PTP)
Thread-Index: AdUFyJFY8mdDayTJS3+yhONTXAB+1w==
Date: Wed, 08 May 2019 18:17:14 +0000
Message-ID: <CY4PR04MB112729F67C5FC7C2FA32410692320@CY4PR04MB1127.namprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.164.62.219]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 90fa9001-bfa8-4d0e-dd86-08d6d3e16589
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:CY4PR04MB0806;
x-ms-traffictypediagnostic: CY4PR04MB0806:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <CY4PR04MB0806892BBACB6DCE53976D5892320@CY4PR04MB0806.namprd04.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:2089;
x-forefront-prvs: 0031A0FFAF
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(376002)(346002)(396003)(39860400002)(136003)(189003)(13464003)(199004)(486006)(99286004)(44832011)(6436002)(5660300002)(14454004)(68736007)(229853002)(2501003)(66574012)(102836004)(86362001)(6246003)(110136005)(316002)(256004)(7736002)(14444005)(55016002)(53936002)(53546011)(305945005)(19627235002)(478600001)(7696005)(8936002)(2906002)(476003)(81166006)(81156014)(9686003)(74316002)(6306002)(6506007)(66556008)(66446008)(64756008)(25786009)(71200400001)(71190400001)(966005)(8676002)(3846002)(66946007)(66476007)(73956011)(76116006)(66066001)(26005)(33656002)(52536014)(6116002)(186003)(48020200001); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR04MB0806; H:CY4PR04MB1127.namprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: ni.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: dDzEyO07MkkaBor/yU8HfyS3xIktoie7diMvBGaCI0WZW7r3rnDdL08Ep1mHTbPjXzdpbrR5lIi+/FFxm+BPCCBl4jLg1BV6Frxu6p2CFY9u9HVW+HP6ZANMQPOKUlpDMxKqD9AUB/9LJHlPIZZa7HziPUbQJlF+sxi5mnUJAONHMOM9Z47qkVyjDZ3YUzn7HzX6U8kl4yTtAtlCl+KP+RWqpxcVEmWWDYpjcPcGs0xcqOp9FIrJD/mfLxCCTITOxkbwqy6gcNsik2+u7zTXr0dhKTuM7fudTVKj7qXJ+ks9OuS+SvnnbuiGvv5q3Tn7f8Q/t4SSqe+A73vf7Dy+fSnC4fzu00P8gXCiIGayIMwkY7ZGDNth5bSNR8aMM102E4GQcA5nx9vu/0ZRgwaGGVRk71VmhetmQxCxJJ1WzAw=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ni.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 90fa9001-bfa8-4d0e-dd86-08d6d3e16589
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 May 2019 18:17:14.2438 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 87ba1f9a-44cd-43a6-b008-6fdb45a5204e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR04MB0806
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-05-08_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=inbound_policy_notspam policy=inbound_policy score=30 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=30 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905080111
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/UsEoZCeTMuWiTvrY3Ap2MoLtpsY>
Subject: Re: [TICTOC] RFC 8575 on YANG Data Model for the Precision Time Protocol (PTP)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.29
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, 08 May 2019 18:17:19 -0000

I'd like to send a quick "thank you" to everyone who worked on RFC 8575, including the RFC Editor Team, participants in IETF TICTOC and IEEE 1588, and my co-authors.

I'd like to especially thank Yuanlong Jiang for all of his hard work on this RFC. Yuanlong submitted the original draft for this work, and he championed its development through all of the issues that arose.

The Precision Time Protocol is currently used in a wide variety of applications, including telecommunications, industrial automation, power distribution, and automotive in-vehicle. As these applications transition to YANG-based network management, I predict that the YANG in RFC 8575 will be used as the foundation, with each application augmenting as needed.

Thanks again,
Rodney Cummings
Vice-chair, IEEE 1588 Working Group
Affiliation: National Instruments

> -----Original Message-----
> From: TICTOC <tictoc-bounces@ietf.org> On Behalf Of rfc-editor@rfc-
> editor.org
> Sent: Tuesday, May 7, 2019 2:48 PM
> To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
> Cc: drafts-update-ref@iana.org; tictoc@ietf.org; rfc-editor@rfc-editor.org
> Subject: [EXTERNAL] [TICTOC] RFC 8575 on YANG Data Model for the Precision
> Time Protocol (PTP)
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>         RFC 8575
> 
>         Title:      YANG Data Model for the
>                     Precision Time Protocol (PTP)
>         Author:     Y. Jiang, Ed.,
>                     X. Liu,
>                     J. Xu,
>                     R. Cummings, Ed.
>         Status:     Standards Track
>         Stream:     IETF
>         Date:       May 2019
>         Mailbox:    jiangyuanlong@huawei.com,
>                     lene.liuxian@foxmail.com,
>                     xujinchun@huawei.com,
>                     rodney.cummings@ni.com
>         Pages:      30
>         Characters: 58253
>         Updates/Obsoletes/SeeAlso:   None
> 
>         I-D Tag:    draft-ietf-tictoc-1588v2-yang-11.txt
> 
>         URL:        https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.rfc-
> 2Deditor.org_info_rfc8575&d=DwICAg&c=I_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPel
> cSjixA&r=WA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k&m=jks9B7DAyG-
> DT4kDnMQfSIRgU8Fka5jgSIzM-S1TRlQ&s=am0g7CHzG8Shb71-
> kY_csT5TO3D4KOdHwVOvipONAmU&e=
> 
>         DOI:        10.17487/RFC8575
> 
> This document defines a YANG data model for the configuration of
> devices and clocks using the Precision Time Protocol (PTP) as
> specified in IEEE Std 1588-2008.  It also defines the retrieval of
> the configuration information, the data sets and the running states
> of PTP clocks.  The YANG module in this document conforms to the
> Network Management Datastore Architecture (NMDA).
> 
> This document is a product of the Timing over IP Connection and Transfer
> of Clock Working Group of the IETF.
> 
> This is now a Proposed Standard.
> 
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and
> suggestions
> for improvements.  Please refer to the current edition of the Official
> Internet Protocol Standards
> (https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-
> 2Deditor.org_standards&d=DwICAg&c=I_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcSj
> ixA&r=WA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k&m=jks9B7DAyG-
> DT4kDnMQfSIRgU8Fka5jgSIzM-
> S1TRlQ&s=1ye3LpwTICpXpmvpyooaZyPdnlY5iPgGQRwd34HBZ30&e= ) for the
> standardization state and status of this protocol.  Distribution of this
> memo is unlimited.
> 
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_ietf-
> 2Dannounce&d=DwICAg&c=I_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcSjixA&r=WA71sf
> 2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k&m=jks9B7DAyG-
> DT4kDnMQfSIRgU8Fka5jgSIzM-
> S1TRlQ&s=DtUE3F02S1hk12w07XrPXYshv1voKMe8HV0JnKlpeyc&e=
>   https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.rfc-
> 2Deditor.org_mailman_listinfo_rfc-
> 2Ddist&d=DwICAg&c=I_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcSjixA&r=WA71sf2o7D
> w7CbYhFt24DPjt3lJuupswWYdnboKbZ8k&m=jks9B7DAyG-DT4kDnMQfSIRgU8Fka5jgSIzM-
> S1TRlQ&s=EeaPkcGOro7AvUhnf6EeUFg-PUqEMf1oJTb065lwhD4&e=
> 
> For searching the RFC series, see
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-
> 2Deditor.org_search&d=DwICAg&c=I_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcSjixA
> &r=WA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k&m=jks9B7DAyG-
> DT4kDnMQfSIRgU8Fka5jgSIzM-
> S1TRlQ&s=L1Ax7uU6CyIEmF5UEL_3MF7zIPe3vpRYTAflrWEOYUk&e=
> For downloading RFCs, see
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-
> 2Deditor.org_retrieve_bulk&d=DwICAg&c=I_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPe
> lcSjixA&r=WA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k&m=jks9B7DAyG-
> DT4kDnMQfSIRgU8Fka5jgSIzM-S1TRlQ&s=KGx4Kq_km_xwk5JIbD2b-wVUcIEJHMfr-
> AVzJTu_zgI&e=
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> 
> The RFC Editor Team
> Association Management Solutions, LLC
> 
> 
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_tictoc&d=DwICAg&c=I_0YwoKy7z5LMTVdyO6YCi
> E2uzI1jjZZuIPelcSjixA&r=WA71sf2o7Dw7CbYhFt24DPjt3lJuupswWYdnboKbZ8k&m=jks9
> B7DAyG-DT4kDnMQfSIRgU8Fka5jgSIzM-
> S1TRlQ&s=cWCdxWR9mij94q6dPboTlpvf19mrDnhyQ7wB_6sentQ&e=