Re: [TICTOC] TICTOC WGLC of draft-ietf-tictoc-security-requirements

Kevin Gross <kevin.gross@avanw.com> Mon, 25 February 2013 14:40 UTC

Return-Path: <kevin.gross@avanw.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57DD121F9372 for <tictoc@ietfa.amsl.com>; Mon, 25 Feb 2013 06:40:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.573
X-Spam-Level:
X-Spam-Status: No, score=-0.573 tagged_above=-999 required=5 tests=[AWL=-0.263, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9LhQHKnl62Em for <tictoc@ietfa.amsl.com>; Mon, 25 Feb 2013 06:40:03 -0800 (PST)
Received: from oproxy1-pub.bluehost.com (oproxy1-pub.bluehost.com [66.147.249.253]) by ietfa.amsl.com (Postfix) with SMTP id B8E4C21F932F for <tictoc@ietf.org>; Mon, 25 Feb 2013 06:40:00 -0800 (PST)
Received: (qmail 25636 invoked by uid 0); 25 Feb 2013 14:39:37 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by oproxy1.bluehost.com with SMTP; 25 Feb 2013 14:39:37 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default; h=Content-Type:Cc:To:From:Subject:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=ATDDmlgZ5KuG9LZQ+yWdO2nTVStWXpmCgB8CoDo6cqY=; b=SduENt8fiWQwWm/RrGrOSY945mlLQ20OZvPBQ05Iyk9egttXzxiFWYWSa/OABhNlinzOpfkkBRjdI7isnt8ydR+r73agNsLVV16LIL67BONSo61niy7AMAClNQOZSCgH;
Received: from [209.85.223.176] (port=49747 helo=mail-ie0-f176.google.com) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.80) (envelope-from <kevin.gross@avanw.com>) id 1U9zDN-0005AG-BU for tictoc@ietf.org; Mon, 25 Feb 2013 07:39:37 -0700
Received: by mail-ie0-f176.google.com with SMTP id k13so3078196iea.7 for <tictoc@ietf.org>; Mon, 25 Feb 2013 06:39:36 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.50.37.212 with SMTP id a20mr3533801igk.88.1361803176448; Mon, 25 Feb 2013 06:39:36 -0800 (PST)
Received: by 10.50.183.163 with HTTP; Mon, 25 Feb 2013 06:39:36 -0800 (PST)
In-Reply-To: <512B4DF0.8040907@isoc.org>
References: <512B4DF0.8040907@isoc.org>
Date: Mon, 25 Feb 2013 07:39:36 -0700
Message-ID: <CALw1_Q3fWn4V3V99MV2OZ=8x8WwUyQXyUxh9VrK0tGY0xJJpWg@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: odonoghue@isoc.org
Content-Type: multipart/alternative; boundary="f46d04446b2196139704d68d820d"
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 209.85.223.176 authed with kevin.gross@avanw.com}
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] TICTOC WGLC of draft-ietf-tictoc-security-requirements
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tictoc>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 14:40:06 -0000

I support advancing this draft.

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org


On Mon, Feb 25, 2013 at 4:41 AM, Karen O'Donoghue <odonoghue@isoc.org>wrote:

>
> This message initiates a two week TICTOC Working Group Last Call on
> advancing:
>
> Title : Security Requirements of Time Synchronization Protocols in Packet
> Switched Networks
> Author(s) : Tal Mizrahi
> Filename : draft-ietf-tictoc-security-**requirements-04.txt
> Pages : 32
> Date : 2013-02-07
>
> http://datatracker.ietf.org/**doc/draft-ietf-tictoc-**
> security-requirements/<http://datatracker.ietf.org/doc/draft-ietf-tictoc-security-requirements/>
>
> as an Informational RFC. Substantive comments and statements of support
> for advancing this document should be directed to the mailing list.
> Editorial suggestions can be sent directly to the authors. This last call
> will end on 12 March 2013.
>
> I realize this WGLC comes right before the IETF; however, this document
> has been around for a long time, and it is my hope that this can be done
> expeditiously.
>
> Regards,
> Karen
>
> Abstract: As time synchronization 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 synchronization protocols, focusing on the Precision
> Time Protocol (PTP) and the Network Time Protocol (NTP). This document also
> discusses the security impacts of time synchronization protocol practices,
> the time synchronization performance implications of external security
> practices, the dependencies between other security services and time
> synchronization.
>
>
>
> ______________________________**_________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/**listinfo/tictoc<https://www.ietf.org/mailman/listinfo/tictoc>
>