IETF Logo Mail Archive

Re: [Ntp] WGLC: draft-ietf-ntp-using-nts-for-ntp

"Salz, Rich" <rsalz@akamai.com> Tue, 11 December 2018 18:38 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 055BD130F0D for <ntp@ietfa.amsl.com>; Tue, 11 Dec 2018 10:38:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.161
X-Spam-Level:
X-Spam-Status: No, score=-4.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 ZIuXEvBbXL5R for <ntp@ietfa.amsl.com>; Tue, 11 Dec 2018 10:38:33 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 3DF47130F06 for <ntp@ietf.org>; Tue, 11 Dec 2018 10:38:33 -0800 (PST)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id wBBIbuL9010982; Tue, 11 Dec 2018 18:38:19 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=ZhfaDwscSxeykkak9ZTjgGnijeOUnvnL6zpbOTxXYkY=; b=LFzxNUcdAXQooXPL9h5DX7IzrxIg+nkT8COjQclAsFHItdaT6Z3Z5gpLhr99Dx6FPTxM wzzf992UXOIEU0OcsOvnlFIEINmWYgunyJc74JdhyLfIwTFbHB3mI2LF3jXK31lK1sPA Bp+j6DeGeVBhz8CL52+lNenXCdyEoHD59E3crfTb7ze0eYgGngknO3taIT1Tsi9GKh0x Yc6Kv99Vr/WKQEqfgMXZYXsm6iNjKZpm0dlggqiWAmqiNLTUahzDG6qJlP76NWhucusV HZNOLnRq9Em4WdFXAtH66xZI4e3D4xY81I19Dz942H0hMVChCwuk1mm2a45K1HVXdKAW Nw==
Received: from prod-mail-ppoint3 (a96-6-114-86.deploy.static.akamaitechnologies.com [96.6.114.86] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 2pa8qm20um-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 11 Dec 2018 18:38:19 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id wBBIWG6N030830; Tue, 11 Dec 2018 13:38:18 -0500
Received: from email.msg.corp.akamai.com ([172.27.25.34]) by prod-mail-ppoint3.akamai.com with ESMTP id 2p8a6gp7dw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 11 Dec 2018 13:38:18 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.27.101) by ustx2ex-dag1mb1.msg.corp.akamai.com (172.27.27.101) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Tue, 11 Dec 2018 12:38:17 -0600
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.6.131]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.6.131]) with mapi id 15.00.1365.000; Tue, 11 Dec 2018 12:38:17 -0600
From: "Salz, Rich" <rsalz@akamai.com>
To: Dieter Sibold <dsibold.ietf@gmail.com>, Marcus Dansarie <marcus@dansarie.se>
CC: "ntp@ietf.org" <ntp@ietf.org>
Thread-Topic: [Ntp] WGLC: draft-ietf-ntp-using-nts-for-ntp
Thread-Index: AQHUdhHAFwSSjMB8+U6iQOfyGeWBuqVywEaAgAZiEQCAATCGAIAAJfCA//+tMIA=
Date: Tue, 11 Dec 2018 18:38:17 +0000
Message-ID: <C7C2A71D-F6F8-4845-B1DF-D07D84541265@akamai.com>
References: <FF5E07A6-6F59-4D45-A186-7FC7C9B4A41C@isoc.org> <0805badf-b411-a0f7-e1ae-b94b4581a86c@dansarie.se> <07E2892F-AD50-4585-AD43-8886FDAD776F@gmail.com> <a017887b-3eac-7c18-ef41-e33ddd715caa@dansarie.se> <EB2055DF-7263-4CCE-A38A-F1B93E21A10F@gmail.com>
In-Reply-To: <EB2055DF-7263-4CCE-A38A-F1B93E21A10F@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.14.0.181202
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.36.227]
Content-Type: text/plain; charset="utf-8"
Content-ID: <5C148789439E5D45B27FD0449A66A2CF@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-12-11_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=765 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1812110164
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-12-11_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=762 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1812110165
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/iSasBBI7eaHci461xSMcwbltHaQ>
Subject: Re: [Ntp] WGLC: draft-ietf-ntp-using-nts-for-ntp
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Dec 2018 18:38:35 -0000

    > There may be some (weird) cases where a user wishes to manually 
    > instruct
    > their NTP client to use the received cookies with a different NTP
    > server. I also believe SHALL should be reserved for cases where
    > non-compliance could cause security issues or cause the protocol to
    > break. This is not an important issue for me, however, and I'll be
    > perfectly happy even if this isn't included.

SHALL isn't just for security issues, it's for "what is required for interop."

Leaving the SHALL NOT share cookies is the right thing to do, and a client if it wants to share cookies with another server and it knows that it is okay, is free to do so.

v2.23.0 | Report a Bug | By Email