[TICTOC] Delay and delay variation as a function of network path computation contribution to ccamp

"Greg Dowd" <GDowd@symmetricom.com> Wed, 10 November 2010 05:51 UTC

Return-Path: <btv1==930f102dc4b==GDowd@symmetricom.com>
X-Original-To: tictoc@core3.amsl.com
Delivered-To: tictoc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A8733A6813 for <tictoc@core3.amsl.com>; Tue, 9 Nov 2010 21:51:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.664
X-Spam-Level:
X-Spam-Status: No, score=-1.664 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_81=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QbsbRV2DSFiX for <tictoc@core3.amsl.com>; Tue, 9 Nov 2010 21:51:06 -0800 (PST)
Received: from mail5.symmetricom.com (mail5.symmetricom.com [69.25.98.10]) by core3.amsl.com (Postfix) with ESMTP id 9EDFE3A689F for <tictoc@ietf.org>; Tue, 9 Nov 2010 21:51:06 -0800 (PST)
X-ASG-Debug-ID: 1289367635-5aa9ddc40001-4wH9i1
Received: from sjowa.symmetricom.com ([192.168.10.41]) by mail5.symmetricom.com with ESMTP id 48gEsqBJDZSGySGI for <tictoc@ietf.org>; Tue, 09 Nov 2010 21:40:35 -0800 (PST)
X-Barracuda-Envelope-From: GDowd@symmetricom.com
X-ASG-Whitelist: Client
Received: from sjmail2.symmetricom.com ([192.168.10.66]) by sjowa.symmetricom.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 9 Nov 2010 21:40:35 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
x-cr-hashedpuzzle: AiI3 BgRA F5Kj GP5W HLh3 HVrU H5T7 IL7H I3fM JiLl J64a K4Ut K/A6 LNlg L7U5 Mpfi; 1; dABpAGMAdABvAGMAQABpAGUAdABmAC4AbwByAGcA; Sosha1_v1; 7; {C5B3D043-F461-4D53-A90E-66B1EDEE3221}; ZwBkAG8AdwBkAEAAcwB5AG0AbQBlAHQAcgBpAGMAbwBtAC4AYwBvAG0A; Wed, 10 Nov 2010 05:40:29 GMT; RABlAGwAYQB5ACAAYQBuAGQAIABkAGUAbABhAHkAIAB2AGEAcgBpAGEAdABpAG8AbgAgAGEAcwAgAGEAIABmAHUAbgBjAHQAaQBvAG4AIABvAGYAIABuAGUAdAB3AG8AcgBrACAAcABhAHQAaAAgAGMAbwBtAHAAdQB0AGEAdABpAG8AbgAgAGMAbwBuAHQAcgBpAGIAdQB0AGkAbwBuACAAdABvACAAYwBjAGEAbQBwAA==
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB8099.CC03CB24"
x-cr-puzzleid: {C5B3D043-F461-4D53-A90E-66B1EDEE3221}
Content-class: urn:content-classes:message
Date: Tue, 09 Nov 2010 21:40:29 -0800
X-ASG-Orig-Subj: Delay and delay variation as a function of network path computation contribution to ccamp
Message-ID: <CB45EB047BD43041BF1F4CC7D6DB21BF05B1C0AE@sjmail2.symmetricom.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Delay and delay variation as a function of network path computation contribution to ccamp
Thread-Index: AcuAmciQ9kJVXfeTTcCztHgrLy/0Wg==
From: Greg Dowd <GDowd@symmetricom.com>
To: tictoc@ietf.org
X-OriginalArrivalTime: 10 Nov 2010 05:40:35.0250 (UTC) FILETIME=[CC157120:01CB8099]
X-Barracuda-Connect: UNKNOWN[192.168.10.41]
X-Barracuda-Start-Time: 1289367635
X-Barracuda-URL: http://192.168.10.96:80/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at symmetricom.com
Subject: [TICTOC] Delay and delay variation as a function of network path computation contribution to ccamp
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 10 Nov 2010 05:52:23 -0000

GMPLS extensions to communicate latency as a TE performance metric

                 draft-wang-ccamp-latency-te-metric-01

 

 

http://tools.ietf.org/html/draft-wang-ccamp-latency-te-metric-01

 

Here's a submission defining support for communicating node/path latency
and variation.  This is the type of effort I think we could incorporate
into our discussions of synch network detection/construction.

 

Any comments?s