IETF Logo Mail Archive

[Ntp] Fwd: New Version Notification for draft-ietf-ntp-port-randomization-02.txt

Fernando Gont <fgont@si6networks.com> Thu, 16 April 2020 18:22 UTC

Return-Path: <fgont@si6networks.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 B23F63A0AF5; Thu, 16 Apr 2020 11:22:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 T4L-OQBEgxrv; Thu, 16 Apr 2020 11:22:28 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DE923A0ADE; Thu, 16 Apr 2020 11:22:27 -0700 (PDT)
Received: from [192.168.0.10] (unknown [181.45.84.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 08827893CB; Thu, 16 Apr 2020 20:22:24 +0200 (CEST)
References: <158706113942.27424.5328137517371748525@ietfa.amsl.com>
To: "ntp@ietf.org" <ntp@ietf.org>
From: Fernando Gont <fgont@si6networks.com>
Cc: "ntp-chairs@ietf.org" <ntp-chairs@ietf.org>
X-Forwarded-Message-Id: <158706113942.27424.5328137517371748525@ietfa.amsl.com>
Message-ID: <bb5a098c-e842-da1a-01d2-65d6d064f5cd@si6networks.com>
Date: Thu, 16 Apr 2020 15:22:08 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <158706113942.27424.5328137517371748525@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/hPpVl7HSSINo86caW4cDHdhXmOQ>
Subject: [Ntp] Fwd: New Version Notification for draft-ietf-ntp-port-randomization-02.txt
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: Thu, 16 Apr 2020 18:22:35 -0000

Folks,

FWIW, we have posted a revision according to the recent feedback and the 
discussion at the interim meeting.

We believe this version is ready for WGLC.

Thanks,
Fernando




-------- Forwarded Message --------
Subject: New Version Notification for 
draft-ietf-ntp-port-randomization-02.txt
Date: Thu, 16 Apr 2020 11:18:59 -0700
From: internet-drafts@ietf.org
To: Miroslav Lichvar <mlichvar@redhat.com>, Guillermo Gont 
<ggont@si6networks.com>, Fernando Gont <fgont@si6networks.com>


A new version of I-D, draft-ietf-ntp-port-randomization-02.txt
has been successfully submitted by Fernando Gont and posted to the
IETF repository.

Name:		draft-ietf-ntp-port-randomization
Revision:	02
Title:		Port Randomization in the Network Time Protocol Version 4
Document date:	2020-04-16
Group:		ntp
Pages:		10
URL: 
https://www.ietf.org/internet-drafts/draft-ietf-ntp-port-randomization-02.txt
Status: 
https://datatracker.ietf.org/doc/draft-ietf-ntp-port-randomization/
Htmlized: 
https://tools.ietf.org/html/draft-ietf-ntp-port-randomization-02
Htmlized: 
https://datatracker.ietf.org/doc/html/draft-ietf-ntp-port-randomization
Diff: 
https://www.ietf.org/rfcdiff?url2=draft-ietf-ntp-port-randomization-02

Abstract:
    The Network Time Protocol can operate in several modes.  Some of
    these modes are based on the receipt of unsolicited packets, and
    therefore require the use of a service/well-known port as the local
    port number.  However, in the case of NTP modes where the use of a
    service/well-known port is not required, employing such well-known/
    service port unnecessarily increases the ability of attackers to
    perform blind/off-path attacks.  This document formally updates
    RFC5905, recommending the use of port randomization for those modes
    where use of the NTP service port is not required.

 


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

v2.23.0 | Report a Bug | By Email