RFC 8573 on Message Authentication Code for the Network Time Protocol

rfc-editor@rfc-editor.org Mon, 24 June 2019 02:48 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C6F2120282; Sun, 23 Jun 2019 19:48:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level:
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 Bft8yQsvbsSx; Sun, 23 Jun 2019 19:48:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04551120019; Sun, 23 Jun 2019 19:48:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5BE1AB81F21; Sun, 23 Jun 2019 19:48:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg1NzMgb24gTWVzc2FnZSBBdXRoZW50aWNhdGlvbiBDb2RlIGZvciB0aGUgTmV0d29yayBUaW1lIFByb3RvY29s?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ntp@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20190624024836.5BE1AB81F21@rfc-editor.org>
Date: Sun, 23 Jun 2019 19:48:36 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/itckpd7Fndm2oFH6El2Ia36cTO0>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2019 02:48:38 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8573

        Title:      Message Authentication Code for the 
                    Network Time Protocol 
        Author:     A. Malhotra,
                    S. Goldberg
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2019
        Mailbox:    aanchal4@bu.edu, 
                    goldbe@cs.bu.edu
        Pages:      5
        Characters: 10055
        Updates:    RFC 5905

        I-D Tag:    draft-ietf-ntp-mac-06.txt

        URL:        https://www.rfc-editor.org/info/rfc8573

        DOI:        10.17487/RFC8573

The Network Time Protocol (NTP), as described in RFC 5905, states
that NTP packets should be authenticated by appending NTP data to a
128-bit key and hashing the result with MD5 to obtain a 128-bit tag.
This document deprecates MD5-based authentication, which is
considered too weak, and recommends the use of AES-CMAC as described
in RFC 4493 as a replacement.

This document is a product of the Network Time Protocol Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC