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

"Salz, Rich" <rsalz@akamai.com> Tue, 11 December 2018 19:16 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 5A373130F36 for <ntp@ietfa.amsl.com>; Tue, 11 Dec 2018 11:16:41 -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 zpDD5FPcX9Dz for <ntp@ietfa.amsl.com>; Tue, 11 Dec 2018 11:16:37 -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 D14E1130E0A for <ntp@ietf.org>; Tue, 11 Dec 2018 11:16:37 -0800 (PST)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id wBBJ7Prf015906; Tue, 11 Dec 2018 19:16:32 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=vyKE9t0EE6w3uGCPvEj/q2cVNLNs/GK16YKLDQ9GyXU=; b=cH+kvQY/4HKKaTzKyBgBwE94whBMHoJsFqCMP1/dbFsq4jxC5XtVkUvI79/3mSthjbGV 1NnRY6GAvUx7fr1QbXlBHA9qkOaFHpD8R/AVZgmDukkDe0TiINBLkt77sz0seQ6HD1FA 1Hp1Qn+mS2uFJ6FZho/xsjDATEfPUzERXlba976Ocr9HrjiBVLHJC8tjfy0CjPXAhf9Z QhW9s0V3EPzF10NSMqcMzVmDmWkOvDnNXkMC5uWgQlgFJHNAo4R8zfTyRj6df+CpEgyG iBhaqpmAC2X8LpAkaFxqxfvKd3+OXkAoBqhMFoeBsc26ZjXKs8wWxAxpWYuVrGhi3ZzJ 8A==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19]) by mx0a-00190b01.pphosted.com with ESMTP id 2pae8114sw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 11 Dec 2018 19:16:32 +0000
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.21/8.16.0.21) with SMTP id wBBJ2acE006324; Tue, 11 Dec 2018 14:16:31 -0500
Received: from email.msg.corp.akamai.com ([172.27.25.32]) by prod-mail-ppoint2.akamai.com with ESMTP id 2p8a6f1gw8-5 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 11 Dec 2018 14:16:30 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.27.101) by ustx2ex-dag1mb2.msg.corp.akamai.com (172.27.27.102) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Tue, 11 Dec 2018 13:16:20 -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 13:16:20 -0600
From: "Salz, Rich" <rsalz@akamai.com>
To: Dieter Sibold <dsibold.ietf@gmail.com>
CC: "ntp@ietf.org" <ntp@ietf.org>, Marcus Dansarie <marcus@dansarie.se>
Thread-Topic: [Ntp] WGLC: draft-ietf-ntp-using-nts-for-ntp
Thread-Index: AQHUdhHAFwSSjMB8+U6iQOfyGeWBuqVywEaAgAZiEQCAATCGAIAAJfCA//+tMICAAF2XAP//rQmA
Date: Tue, 11 Dec 2018 19:16:19 +0000
Message-ID: <5EEE74CE-08A8-4BCF-8C4A-540F11AF7521@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> <C7C2A71D-F6F8-4845-B1DF-D07D84541265@akamai.com> <F06DCD87-961E-43F8-8112-707D718AE42C@gmail.com>
In-Reply-To: <F06DCD87-961E-43F8-8112-707D718AE42C@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: <BF3F32AA01B8944C9BB6DABAF252682D@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=841 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1812110169
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=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=845 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1812110170
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/I9Uuf31WP2aqAB3RxE5jAsVQIbA>
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 19:16:41 -0000

Yes, leave the SHALL.  IF a client goes outside the "boundary" because it knows it is safe to do so, that is okay.

On 12/11/18, 2:13 PM, "Dieter Sibold" <dsibold.ietf@gmail.com> wrote:

    Hi Rich,
    I’m not sure if I got your right. Are you arguing to leave the SHALL 
    as it is?
    - Dieter
    
    
    Dieter Sibold
    dsibold.ietf@gmail.com
    
    On 11 Dec 2018, at 19:38, Salz, Rich wrote:
    
    >     > 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.
    
    _______________________________________________
    ntp mailing list
    ntp@ietf.org
    https://www.ietf.org/mailman/listinfo/ntp