IETF Logo Mail Archive

Re: [Ntp] Version request

James <james.ietf@gmail.com> Wed, 17 February 2021 13:02 UTC

Return-Path: <james.ietf@gmail.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 522D33A19E1 for <ntp@ietfa.amsl.com>; Wed, 17 Feb 2021 05:02:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level:
X-Spam-Status: No, score=-2.088 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 mtdfCOJSQfKa for <ntp@ietfa.amsl.com>; Wed, 17 Feb 2021 05:02:21 -0800 (PST)
Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C20C3A19DD for <ntp@ietf.org>; Wed, 17 Feb 2021 05:02:21 -0800 (PST)
Received: by mail-ej1-x62e.google.com with SMTP id jt13so22019178ejb.0 for <ntp@ietf.org>; Wed, 17 Feb 2021 05:02:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=S7h0liBAkQo/qON8iBcyJorXzeCFpvncGmKenm+gGtA=; b=TGvl7xs9EpBjITWuCzkP12B9HTQkiywQFRwZxTqSS9rrHlpQ/lmCFmz4PPzc9t6iwY Kdj+dLzP5e0isFx7hxgFojJf+Kr7VuvfmFIo4d7xVYvHeO6YSA8YduYaIYybYG8+kVak J/qE2BH+m89iMwzlUeO25JnSH29/riyGR1anythWvhkOD2RHIbSpIc6EVfVVaH4LAc6L oTSh0J4dgrFy3xoP/4yJpvoFgnnhw4z4XzGsmG9IgJn93IykkSOWxZtYfV1xEtpwiZzT yMtCsCwZCikXY+pSMHj+c0XwJhSxY/zfvDKXG/Ve4WeDjE5YBIIg5KpKUL2yPzqq7WDK uSEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=S7h0liBAkQo/qON8iBcyJorXzeCFpvncGmKenm+gGtA=; b=K7m/USi8RGPuwtdxUvTp76lj8sH9bH9mnOr/W2bqbNiD54sJprxuCf2r2Y31pvCZFV lAxio2EMshKUUq6DdIU2jMn6+mI3Vk3t8PG3DxXh2UmZkF9eSmqHI4Se3Y6Hg7sqGETv 6VHZki7GOXfxgcjmiWS4Yp89s4Y5LC2QEPKPHEPFZOx4DMCB42KTlCUQJsfadhiDq/42 LOnz1lStlsOZcDuKAd5unB92HzM02iDPSFhGTybfLtkjqccWQjp6TzWOEi2sMNh65t8/ jvlNLIfJTP72Q3P2sP1XASRMgaP/Xy5OaDdgXBBEBHgfxe95PZuclJ4Ll0oTjh4MJIwo I32w==
X-Gm-Message-State: AOAM532JmdH6t5uTcV/DGXJyf0BTcmYwjjtwu5B2hD6QuiaHZw+muzyD +sLiZ5Pm+zPfaOvIB6QpZ/ekNm/Z65I=
X-Google-Smtp-Source: ABdhPJz/n/FMdzVyNEqzeljPJ9JUB1rJo7eD+HcgpoB3EmCipcs3mHbcJA71P7b1oiH5/u2gEy0eQg==
X-Received: by 2002:a17:907:16a4:: with SMTP id hc36mr20210672ejc.127.1613566939678; Wed, 17 Feb 2021 05:02:19 -0800 (PST)
Received: from ?IPv6:2001:984:65b0:2:494a:151c:fcb9:1e8d? ([2001:984:65b0:2:494a:151c:fcb9:1e8d]) by smtp.gmail.com with ESMTPSA id fu7sm987296ejc.11.2021.02.17.05.02.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 17 Feb 2021 05:02:19 -0800 (PST)
To: "Dijck, Gerard van" <gerard.vandijck@crow.nl>, "ntp@ietf.org" <ntp@ietf.org>
References: <AM0PR0302MB31867350946D1E4A1B03B0F1E0869@AM0PR0302MB3186.eurprd03.prod.outlook.com>
From: James <james.ietf@gmail.com>
Message-ID: <1a4673b4-a547-745f-3364-5dedc4fb5e0b@gmail.com>
Date: Wed, 17 Feb 2021 14:02:18 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <AM0PR0302MB31867350946D1E4A1B03B0F1E0869@AM0PR0302MB3186.eurprd03.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------242D02DEFF4BC42CAD3D5A16"
Content-Language: en-AU
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/2XcvNfjDzTw-93ghT9HKw3dPVQA>
Subject: Re: [Ntp] Version request
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: Wed, 17 Feb 2021 13:02:23 -0000

Please see inline.

On 17-02-2021 10:47, Dijck, Gerard van wrote:
>
> Dear mr/mrs,
>
> Would it be possible to ask a few questions about the versions of some 
> specific RFC doc’s please?
>
> I like to know about the following doc’s:
>
> name
>
> 	
>
> titel
>
> 	
>
> Active version
>
> 	
>
> Prev. version
>
> IETF RFC 7159
>
> 	
>
> The JavaScript Object Notation (JSON) Data Interchange Format
>
> 	
>
> *RFC 7159_2014-3***
>
> 	
>
> -
>
> IETF RFC 5246
>
> 	
>
> The Transport Layer Security (TLS) Protocol
>
> 	
>
> *TLS1.3 **RFC8446**_2018-3***
>
> 	
>
> TLS1.2 RFC5246_2008-08
>
> IETF RFC 3986
>
> 	
>
> Uniform Resource Identifier (URI): Generic Syntax
>
> 	
>
> *STD66 RFC 3986_2005***
>
> 	
>
> -
>
> IETF RFC 7525
>
> 	
>
> Recommendations for Secure Use of Transport Layer Security (TLS) and 
> Datagram Transport Layer Security (DTLS)
>
> 	
>
> *BCP 195 RFC 7525_2015-05***
>
> 	
>
> IETF RFC 5905
>
> 	
>
> Network Time Protocol Version 4: Protocol and Algorithms Specification
>
> 	
>
> *RFC 5905 V4_2010-6***
>
> 	
>
> n/a
>
> Are the versions in “Active version” indeed the latest versions?
>
Correct. RFCs are considered immutable, and the date identifiers after 
them are only indicators of the time of publication.

> Is RFC 5246 replaced by RFC 8446?
>
This is correct, however it's important to understand that 
implementations may include support for both, but if you are asking in 
the context of NTS (RFC 8915) section 3 very explicitly states that no 
earlier version than TLS 1.3 be used.

> Are any other of the mentioned RFC’s replaced by an other document or RFC?
>
This is information you can acquire yourself - the documents are 
completely public. Viewing them on tools (for example 
https://tools.ietf.org/html/rfc3986) you can see "Updated by" in the 
top, which will refer to other published documents which may update 
partially or in its entirety.

> Thank you so much!
>
> Met vriendelijke groet,
>
> Gerard van Dijck
>
>
>
> *E *gerard.vandijck@crow.nl <mailto:gerard.vandijck@crow.nl>
> *T *
> *M *    06-206 509 03
> *W **    www.crow.nl
>
> **VOLG ONS:
>
> **View Company's Twitter profile* <http://twitter.com/crow_nl>***View 
> Company's LinkedIn profile* 
> <http://www.linkedin.com/company/crow>***View Company's Facebook 
> profile* <http://www.facebook.com/crownl>*
>
> *
>
>
> _______________________________________________
> ntp mailing list
> ntp@ietf.org
> https://www.ietf.org/mailman/listinfo/ntp

v2.14.0 | Report a Bug | By Email