RFC 7384 on Security Requirements of Time Protocols in Packet Switched Networks
rfc-editor@rfc-editor.org Fri, 17 October 2014 00:15 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF161A9060 for <ietf-announce@ietfa.amsl.com>; Thu, 16 Oct 2014 17:15:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 E_ssuvb7jbO0 for <ietf-announce@ietfa.amsl.com>; Thu, 16 Oct 2014 17:15:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 401111A9045 for <ietf-announce@ietf.org>; Thu, 16 Oct 2014 17:15:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 76214181C81; Thu, 16 Oct 2014 17:15:34 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7384 on Security Requirements of Time Protocols in Packet Switched Networks
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20141017001534.76214181C81@rfc-editor.org>
Date: Thu, 16 Oct 2014 17:15:34 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/5_-74vXr8g1jja_6MTh4RZbYUFQ
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: <http://www.ietf.org/mail-archive/web/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: Fri, 17 Oct 2014 00:15:47 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7384
Title: Security Requirements of Time Protocols
in Packet Switched Networks
Author: T. Mizrahi
Status: Informational
Stream: IETF
Date: October 2014
Mailbox: talmi@marvell.com
Pages: 36
Characters: 78942
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tictoc-security-requirements-12.txt
URL: https://www.rfc-editor.org/rfc/rfc7384.txt
As time and frequency distribution protocols are becoming
increasingly common and widely deployed, concern about their exposure
to various security threats is increasing. This document defines a
set of security requirements for time protocols, focusing on the
Precision Time Protocol (PTP) and the Network Time Protocol (NTP).
This document also discusses the security impacts of time protocol
practices, the performance implications of external security
practices on time protocols, and the dependencies between other
security services and time synchronization.
This document is a product of the Timing over IP Connection and Transfer of Clock Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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/rfc.html
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