Return-Path: 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 B780CC14F6B9; Wed, 15 May 2024 19:09:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.098 X-Spam-Level: X-Spam-Status: No, score=-7.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=meinberg-usa.com Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8RGs76uxVMTi; Wed, 15 May 2024 19:09:48 -0700 (PDT) Received: from EUR02-DB5-obe.outbound.protection.outlook.com (mail-db5eur02on2094.outbound.protection.outlook.com [40.107.249.94]) (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 D463AC14F6A1; Wed, 15 May 2024 19:09:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=erQeXllpEpqJ3zYmte0tNS8uSDBXb05ur24Na0+ZIYNpdA6iRQ8Hf6S74QLj5+kvQMGlQyBHkyrIxEh7chnK8w11s92dsXaywRiOC5ONSj6j5LyNpVLF8yZFH/ZcuhQQjQgWv/D2ws7bzQy7rHIKsy0g8kHv1LoAMxCONTZJkC63o+pCTZVdTNZlDalXvDqbpUd3ooDJqF6aCTTCfd8WZFnjuntP3JC9ZwzxBASH7LOQZI4TkGmq0NA5wut+SShle/NmbwkUvOXu1OqTeJQVFxtQQxBP1qoRev3Y8SlEYGG54iEr4NtTjiHx9Pl+g5vRmFuwNyTDPnkm+OtrobI1/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=/j91WdsQVB4OkDrz0hh1kizTBTwjcQkc0hHj39EUeQo=; b=mn/hayL7wi8fYBBBB15mAUy9VHw3ryxgnr1F8MhXCyGoRCzDf5v69Ibys7XeYYafac3OGBrat+U5dtaOjpwtQqfdbIW6w6buAv9CwqAgG2UoFufBiQ5n/0EHm1dzeK+StfZU09y2AJTFQnxEppHqZNStKTaPydr/hnZImDauL9QPxbHafLwfpp14EQEud5FAm9H/+rf7YV9WTOlaYn59OlsC91SOxHE26ALrstkZ5jzlOJLO4qXCIneKdJ6wWFtJFel+3z0aabxxNDZw2NMF4Ji2YORKD0l0eWddJ+h6hjygSlHjfsFFqMP4dyHyUjdRCBiBNBRyHxNFsrDV+dmt1Q== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=meinberg-usa.com; dmarc=pass action=none header.from=meinberg-usa.com; dkim=pass header.d=meinberg-usa.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=meinberg-usa.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/j91WdsQVB4OkDrz0hh1kizTBTwjcQkc0hHj39EUeQo=; b=ICSTuabsxDpQZj1U4YhY/I5NRfcDGLHbixm95cwotsRF5N6WgKG08E8wd3LsE7lcUW9qYXoC5B1WKGJ2GdcC6QyZpwWbhk2wUFjDT9P/Ye56knbeJR60CTVSHqDq4wz1UGIt0iR86bSdmNky1WR0z1vrDq+RgTRkXpcrBRmflVXT4O0AfTn6RjEgaAnS2ovkZED1ax3WY6jL6fk8/yKp2jymYvLlcPs7UHPrnPMwD79Wkmep1HyDs5UFcVgwuANcZem4FKskHkRyDcDYM0f6DkJw5AMONNn8OW9WLuC9fBPCrgvchJqWxQ+ZBkVP4apF0ndaWrQE8Z6IAkpbha5xjA== Received: from AM7PR02MB5765.eurprd02.prod.outlook.com (2603:10a6:20b:102::15) by PA4PR02MB6926.eurprd02.prod.outlook.com (2603:10a6:102:104::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7587.27; Thu, 16 May 2024 02:09:42 +0000 Received: from AM7PR02MB5765.eurprd02.prod.outlook.com ([fe80::f9d9:cd85:99a8:d18a]) by AM7PR02MB5765.eurprd02.prod.outlook.com ([fe80::f9d9:cd85:99a8:d18a%4]) with mapi id 15.20.7587.028; Thu, 16 May 2024 02:09:42 +0000 From: Doug Arnold To: The IESG , Murray Kucherawy Thread-Topic: Murray Kucherawy's No Objection on draft-ietf-tictoc-ptp-enterprise-profile-26: (with COMMENT) Thread-Index: AQHapt9g9Id+DY+gsES9NfsZpxcV7bGZHNTI Date: Thu, 16 May 2024 02:09:42 +0000 Message-ID: References: <171578812422.9312.9399341515327775640@ietfa.amsl.com> In-Reply-To: <171578812422.9312.9399341515327775640@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=meinberg-usa.com; x-ms-publictraffictype: Email x-ms-traffictypediagnostic: AM7PR02MB5765:EE_|PA4PR02MB6926:EE_ x-ms-office365-filtering-correlation-id: bab0fee1-b61e-4f96-e9f4-08dc754d3fb8 x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0;ARA:13230031|376005|1800799015|366007|38070700009; x-microsoft-antispam-message-info: =?Windows-1252?Q?rx+GlIUnhFES/15j95zI+st41kxi4n0Ts18Z9ySWucLuS33nOGgoyUrR?= =?Windows-1252?Q?3zwRhaKwMhJktNrmJ1vuaHRRPkDvgNMEZHaUoOC113wW56way7uOcV17?= =?Windows-1252?Q?4D1q8H4K4Uv/aQglXnEvLuoeX2tBpcVWLMSqiusrjOsX+/qKLt8nJWsY?= =?Windows-1252?Q?wxOJx0kFChtzDjeAhTtx+Q7X985+g8Ght2m5PsNYEeRzhvsHurkTpOMB?= =?Windows-1252?Q?sL+Gx7tpd55U+GMoVjZcgtX1H3en+uk2qTWkMiQnY+s56KHp4oD5cttJ?= =?Windows-1252?Q?Css2SjTFXE8szPqv+xQN3+bc2eSsII3vqkEmvwV1DJAq3RBp4jFvyU6b?= =?Windows-1252?Q?MBsL4ABktRzYesBPmerLCHO68aS7w8i/y24ZL+A0NDDDBTnRs/0B9W2I?= =?Windows-1252?Q?OIo65w1zR5z2IRlPCimbVk29QME6yBIkLHumT3SzSanF20rBf0Si/1iy?= =?Windows-1252?Q?M9/Z5nwQox5LqN06kugR/oFps/JXgX2/JyvDf9w7G2rCC5KaaNcZWRDl?= =?Windows-1252?Q?IN64M5xhrFnQjlaG9Lf0cdWqGmVQa/vLusO5JpEko1UGJSYh6GpVqpkg?= =?Windows-1252?Q?AVxLDMEgi4QIrH5CHbwqlZdCrTzEVODOiivQkx78yZWw0Q14Rz3qttv5?= =?Windows-1252?Q?cCSJ02ZO3nKu3ocb/nQXLplk2ATeV58JO+DRM62dT2DNcMuXyIKyR+uc?= =?Windows-1252?Q?bI4UKojJAx+Lc/b9X0/s0ri6FK6iytln6qeVzP6Ej0n4JFq2nbq5mcr5?= =?Windows-1252?Q?61i0vBv0Mogyz3sUqlXimTVVkwsL9ROJY1iI+NasjER3S8geV01QPAQW?= =?Windows-1252?Q?PIi2bZ9G7j//jjHw3LzQTuBMaQBKe0ymgQnhBda3CaHFtXqmYonh+tlH?= =?Windows-1252?Q?3bFgSwjHVd5ar+vRg3kGxnWGrp8sxpGiVadxYbwaG/VSI48XUWvpZlQW?= =?Windows-1252?Q?Oa6LR8RXyAjv8SNS8U95MuPOoq7peVANAS0/sCutJeZ5+t6WpNSTppEb?= =?Windows-1252?Q?KryDGocYbOinMAQWbVrH+wdMOMe+l97vSHtYvIoDbwePYAbm+3saTjhM?= =?Windows-1252?Q?iyGIyomk9HQLXJn7n5HCT5dWjZakugAMnlZc6xj87I29fwbdVeQxVzpW?= =?Windows-1252?Q?doK1MvN65rzUN9C++liW3ZwhMyGbanM3Y3DCrJnk5oVyAmAqrgscFkfb?= =?Windows-1252?Q?h6flP7ljrCZU+vVMsp2YWUtlffkLWaO4onGvpCjQdGroxbmOBJ3Tbisx?= =?Windows-1252?Q?+k/RDTQSu1rzSMdVmfR/9Yud5EKXNArgshxS4OUhW7f5A6t203d++RQu?= =?Windows-1252?Q?31sx0Vn8rU203WMRaEcSa5zwsRbScdpq9vPdzrie/qsB0A4oNb28tRoA?= =?Windows-1252?Q?C5zF0+rwYixmAQ=3D=3D?= x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:AM7PR02MB5765.eurprd02.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230031)(376005)(1800799015)(366007)(38070700009);DIR:OUT;SFP:1102; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?Windows-1252?Q?qesWIO5bPLwT++5p3f8Ocx2/Iaht+qPsb4HnNxfx5DeqtmZlLOhOCYoI?= =?Windows-1252?Q?BwBflkv7NGcu0oRZmUe1FxaHEa9Ma1JYxhVRkTBUm1Y+oCrG6kPBqj2t?= =?Windows-1252?Q?7I3FPzhMLpwz6q5C2zbcDGXUUr4xc4Xwz3msQ9UX7sa8jedJ2g/QdFkd?= =?Windows-1252?Q?hIJYuibMRogHJviNETYmDLszJBIGJvz2FrmJvqUmQI9HqG+aWYjwqizQ?= =?Windows-1252?Q?pYydmmMyklYN07TRO5jFFDqwtLpz4p9C4Jbluslf0/mNTRy86DzL6U9f?= =?Windows-1252?Q?BmgZTIodyDTouYNsIdhEWORjfnawoqMg/12xRAQZmNTAVp2X/iJYm3SC?= =?Windows-1252?Q?9kNbzGeCOaGjJyIviFdN/otSTUsNCJRDYPEjk51QPQA/bib2u8UsTPOW?= =?Windows-1252?Q?YpWo+cEetmHLEyeODFBI96sRdFMam9w6MPb8cVDu3lR3ZP8ET51yrNQI?= =?Windows-1252?Q?XM8qHMu6yyNOAxpI7KjihAGrc7MAqyFrhmQe0vhoDmDlEnRDOOyecV9m?= =?Windows-1252?Q?yjeptXU49dggn4073o3yQY+RLsCZYLHzg3Ntu3+96K8wXjDTNn9TH3rt?= =?Windows-1252?Q?kEhG6zVBnMRyjJbE5SL0dQbOrzYEOiLFVE3cWvzyFct5cb3muysSAJx2?= =?Windows-1252?Q?2yNakjt+NAla8o/jqqltCz/SLQpjgQk3blaSa/KaIfFNsq4d4uYUqA7I?= =?Windows-1252?Q?K0zrC9AWgkrvju51+9gBMqlh62QCfIO+002rNjy+wWZpKi9USZVnp0Ll?= =?Windows-1252?Q?CBKyb5OB9HRntaYKN2DSq2n2mX0V+biw5Ixbf80OZGGQdyXL6BBoNNT0?= =?Windows-1252?Q?8+annWKLdEGwVyFqpGpWlM/4EWCDFvebLxAnvv65vMyQT5j8SbW6znhV?= =?Windows-1252?Q?fS/KGNCuVt70WJ4aTd7YZvoorx6ntNIk2oG6cS+tsmZ2Z4lr50bK1cot?= =?Windows-1252?Q?hio6Rjf0z9+Dt0Hv1goUPmLEgvAXlecSWWhY91Ic2r8hASpqZXqy+9lU?= =?Windows-1252?Q?9jSbN9emP3TpKzPKupayaw0q5f5eHimR+oDTCPrOFU7po6mLOWTAICag?= =?Windows-1252?Q?YGVRwtG8HXRFM98UoTVcxGTPF9ThC0iaWwYk/NjIVcr0R73p6vndO46n?= =?Windows-1252?Q?+1GbUU1+ydNb5VuTG3KSHtrUiBHIngQWjTnpgF3ZPipecJ6c6gSuJihD?= =?Windows-1252?Q?peIcaHS8xbfAMGf7+Vk30+vxYb/XSaQQxfZHsaDKharQ//JdSs3vjtlK?= =?Windows-1252?Q?oFHmd+KqTSN0k5/hRCVYHw72gIVUIfHo+N9rJtTDrSQ33tUxsvb7C1+Y?= =?Windows-1252?Q?NgVwQToXFWa5R0CO5HliHyFpcnoKbvbZNNdZaciCYWWFR20ppMF3L3DD?= =?Windows-1252?Q?PwvjEZ8rlhNEK4LFwctp7qgAXnrt/Rd/mntLvvEofb6EOfg2PA1d5EM/?= =?Windows-1252?Q?ET3cUgTC1J2AuJrwlwidQFmDCA8WyY5wCW+1jx/nrr8lsNnUfQLUxhP2?= =?Windows-1252?Q?JSzatP7/VwpTPWS4JDIlyI/w4ifv+DkdAutG9bHfBu9VHcs6Z7Tw8ni7?= =?Windows-1252?Q?kvZSvrqyG39bLFgcoWeebIWkJfxZx8v64SP0BHipv1h7OG95k05Z15lV?= =?Windows-1252?Q?dN88m6HMxpsiB9rVXCXQk8JXr9XiIu+tf/5JrSN4NFDOae2vpz417uTp?= =?Windows-1252?Q?oz5z0h2B+BD+FjqrFHJCzSM6ZriPIq76gk7yiOJHw/RA/OrkpZv3yQ?= =?Windows-1252?Q?=3D=3D?= Content-Type: multipart/alternative; boundary="_000_AM7PR02MB57659834509996FDE53205D4CFED2AM7PR02MB5765eurp_" MIME-Version: 1.0 X-OriginatorOrg: meinberg-usa.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: AM7PR02MB5765.eurprd02.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: bab0fee1-b61e-4f96-e9f4-08dc754d3fb8 X-MS-Exchange-CrossTenant-originalarrivaltime: 16 May 2024 02:09:42.1486 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: d59904cd-769f-4368-8bd0-f5f435893a38 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: /b0luwIj8KEqEDwi9otWe21RYMIYPIYezGDaoY1vaO22Kwo7kfEFtLs1sJ/eRmfk8yblFoImmbz5d2W1eufRWakfhrGo7IJa+4K+YqBGuko= X-MS-Exchange-Transport-CrossTenantHeadersStamped: PA4PR02MB6926 Message-ID-Hash: TDXE5NPXOFXXNZMSYJTARH7WYZ4UHH24 X-Message-ID-Hash: TDXE5NPXOFXXNZMSYJTARH7WYZ4UHH24 X-MailFrom: doug.arnold@meinberg-usa.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tictoc.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: "draft-ietf-tictoc-ptp-enterprise-profile@ietf.org" , "tictoc-chairs@ietf.org" , "tictoc@ietf.org" X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5BTICTOC=5DRe=3A_Murray_Kucherawy=27s_No_Objection_on_draft-ietf-?= =?utf-8?q?tictoc-ptp-enterprise-profile-26=3A_=28with_COMMENT=29?= List-Id: Timing over IP Connection and Transfer of Clock BOF Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --_000_AM7PR02MB57659834509996FDE53205D4CFED2AM7PR02MB5765eurp_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hello Murray, Thanks for the review. You found some inconsistencies or unclear passages = that I and others missed. I reply to the comments inline below This seems like what RFC 2026 defines as an Applicability Statement. Shoul= d it say so explicitly? This might be characterized as an applicability statement according to RFC = 2026, but I=92m not sure that stating this will clarify this draft to reade= rs. I am open to detailed suggestions. NTP in the Abstract could use a reference to its RFC. I agree. I propose to add a reference to RFC 5905 The SHOULD in Section 5 is bare. When might an implementer legitimately de= cide to deviate from the advice given there? Or maybe MUST is better? Good point. I propose: In Section 5, change: =93Note that clocks SHOULD always be identified by their Clock ID and not t= he IP or Layer 2 address.=94 To: =93Note that clocks SHOULD always be identified by their Clock ID and not t= he IP or Layer 2 address in implementations that might operate in a network= that contains Transparent Clocks.=94 The first SHOULD in Section 9 seems to me to be redundant to the MUST that precedes it. The MUST and SHOULD are as intended. However, if you are confused then I w= asn=92t clear. I propose: In section 9, change: =93TimeReceiver Clocks MUST be able to operate properly in a network which = contains multiple timeTransmitters in multiple domains. TimeReceivers SHOUL= D make use of information from all the timeTransmitters in their clock cont= rol subsystems.=94 To: =93In a network which contains multiple timeTransmitters in multiple domain= s. TimeReceivers SHOULD make use of information from all the timeTransmitte= rs in their clock control subsystems.=94 TimeReceiver Clocks MUST be able t= o function in such networks even if they use time from only one of the doma= ins.=94 Is the SHOULD in Section 10 a restatement of the SHOULD in the last paragra= ph of Section 6? Yes it is. I propose removing the sentence with the SHOULD in section 10. ________________________________ From: Murray Kucherawy via Datatracker Sent: Wednesday, May 15, 2024 11:48 AM To: The IESG Cc: draft-ietf-tictoc-ptp-enterprise-profile@ietf.org ; tictoc-chairs@ietf.org ; tictoc@ietf.org ; ek.ietf@gmail.com Subject: Murray Kucherawy's No Objection on draft-ietf-tictoc-ptp-enterpris= e-profile-26: (with COMMENT) Murray Kucherawy has entered the following ballot position for draft-ietf-tictoc-ptp-enterprise-profile-26: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-= ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-enterprise-profile/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- This seems like what RFC 2026 defines as an Applicability Statement. Shoul= d it say so explicitly? NTP in the Abstract could use a reference to its RFC. The SHOULD in Section 5 is bare. When might an implementer legitimately de= cide to deviate from the advice given there? Or maybe MUST is better? The first SHOULD in Section 9 seems to me to be redundant to the MUST that precedes it. Is the SHOULD in Section 10 a restatement of the SHOULD in the last paragra= ph of Section 6? --_000_AM7PR02MB57659834509996FDE53205D4CFED2AM7PR02MB5765eurp_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

Hello Murray,


Thanks for the review.  You found some= inconsistencies or unclear passages that I and others missed.  I reply to the comments inline below


This seems like what RFC 2026 defines as= an Applicability Statement.  Should it
say so explicitly?

 

This might be characterized as an applicability statement according = to RFC 2026, but I=92m not sure that stating this will clarify this draft to readers.  I am open to detailed suggestion= s. 


NTP in the Abstract could use a referenc= e to its RFC.

 

I agree.  I propose to add a reference to RFC 5905

 

The SHOULD in Section 5 is bare.  When might an implementer = legitimately decide
to deviate from the advice given there?  Or maybe MUST is better?<= /span>

 

Good point.  I propose:

In Section 5, change:

=93Note that clocks SHOULD always be i= dentified by their Clock ID and not the IP or Layer 2 address.=94

To:

=93Note that clocks SHOULD always be i= dentified by their Clock ID and not the IP or Layer 2 address in implementa= tions that might operate in a network that contains Transparent Clocks.=94

 

The first SHOULD in Section 9 seems to me to be redundant to the = MUST that
precedes it.

 

The MUST and SHOULD are as intended.  However, if you are confu= sed then I wasn=92t clear.  I propose:

In section 9, change:

=93TimeReceiver Clocks MUST be able to operate properly in a network which contains multiple timeTransmitters in multiple domains.= TimeReceivers SHOULD make use of information from all the timeTransmitters= in their clock control subsystems.=94

To:

=93In a network which contains multiple timeTransmitters in multiple domains. TimeReceivers SHOULD make use of information from all= the timeTransmitters in their clock control subsystems.=94 TimeReceiver Cl= ocks MUST be able to function in such networks even if they use time from o= nly one of the domains.=94

 

Is the SHOULD in Section 10 a restatement of the SHOULD in the la= st paragraph
of Section 6?

 

Yes it is.  I propose removing the sentence with the SHOULD in = section 10.

 

 

 



 

 

 

 

 

 

 

 

 

From: Murray Kucherawy via = Datatracker <noreply@ietf.org>
Sent: Wednesday, May 15, 2024 11:48 AM
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-tictoc-ptp-enterprise-profile@ietf.org <draft-ietf= -tictoc-ptp-enterprise-profile@ietf.org>; tictoc-chairs@ietf.org <tic= toc-chairs@ietf.org>; tictoc@ietf.org <tictoc@ietf.org>; ek.ietf@g= mail.com <ek.ietf@gmail.com>
Subject: Murray Kucherawy's No Objection on draft-ietf-tictoc-ptp-en= terprise-profile-26: (with COMMENT)
 
Murray Kucherawy has entered the following ballot = position for
draft-ietf-tictoc-ptp-enterprise-profile-26: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions= /
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-enterpri= se-profile/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

This seems like what RFC 2026 defines as an Applicability Statement.  = Should it
say so explicitly?

NTP in the Abstract could use a reference to its RFC.

The SHOULD in Section 5 is bare.  When might an implementer legitimate= ly decide
to deviate from the advice given there?  Or maybe MUST is better?

The first SHOULD in Section 9 seems to me to be redundant to the MUST that<= br> precedes it.

Is the SHOULD in Section 10 a restatement of the SHOULD in the last paragra= ph
of Section 6?



--_000_AM7PR02MB57659834509996FDE53205D4CFED2AM7PR02MB5765eurp_--