
From cabo@tzi.org  Thu Aug  1 01:31:31 2013
Return-Path: <cabo@tzi.org>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A9CE21F9AA2 for <tsv-area@ietfa.amsl.com>; Thu,  1 Aug 2013 01:31:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.087
X-Spam-Level: 
X-Spam-Status: No, score=-106.087 tagged_above=-999 required=5 tests=[AWL=0.162, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V8QnXWXdBREB for <tsv-area@ietfa.amsl.com>; Thu,  1 Aug 2013 01:31:25 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 39AA221F9A96 for <tsv-area@ietf.org>; Thu,  1 Aug 2013 01:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r718VE7J012486 for <tsv-area@ietf.org>; Thu, 1 Aug 2013 10:31:14 +0200 (CEST)
Received: from dhcp-90f8.meeting.ietf.org (dhcp-90f8.meeting.ietf.org [130.129.8.248]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 28711BCB; Thu,  1 Aug 2013 10:31:14 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Date: Thu, 1 Aug 2013 10:31:13 +0200
Subject: MINION and RECOBS: C bit
To: tsv-area@ietf.org
Message-Id: <308366D9-0749-4F76-A752-BC3BD8A3FAB9@tzi.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 08:31:31 -0000

Nice work, and I really would like to use this.

Having done RFC 2687, I can't help noticing that the C bit is in the =
wrong place.
You only know whether the frame will be complete or will need to be =
suspended at the end, not at the start (or you have to proactively slice =
everything up, which is not what a suspend encoding is about).

Simple fix: As frame end marker, use FE and FF, one for completed and =
one for suspended.

Gr=FC=DFe, Carsten


From cheshire@apple.com  Mon Aug 19 17:48:57 2013
Return-Path: <cheshire@apple.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B49B011E8319 for <tsv-area@ietfa.amsl.com>; Mon, 19 Aug 2013 17:48:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z1oC0ob2477t for <tsv-area@ietfa.amsl.com>; Mon, 19 Aug 2013 17:48:49 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 03AA611E8318 for <tsv-area@ietf.org>; Mon, 19 Aug 2013 17:48:46 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Received: from relay6.apple.com ([17.128.113.90]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MRT00MBH0XAKOY0@mail-out.apple.com> for tsv-area@ietf.org; Mon, 19 Aug 2013 17:48:46 -0700 (PDT)
X-AuditID: 1180715a-b7f7f6d000002fcb-ff-5212bceefba3
Received: from spicerack.apple.com (spicerack.apple.com [17.128.115.40]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate)	by relay6.apple.com (Apple SCV relay) with SMTP id AB.2A.12235.EECB2125; Mon, 19 Aug 2013 17:48:46 -0700 (PDT)
Received: from chesh1.apple.com (chesh1.apple.com [17.193.13.41]) by spicerack.apple.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTPSA id <0MRT0093S0X95M50@spicerack.apple.com> for tsv-area@ietf.org; Mon, 19 Aug 2013 17:48:46 -0700 (PDT)
Subject: Re: MINION and RECOBS: C bit
From: Stuart Cheshire <cheshire@apple.com>
In-reply-to: <308366D9-0749-4F76-A752-BC3BD8A3FAB9@tzi.org>
Date: Mon, 19 Aug 2013 17:48:45 -0700
Content-transfer-encoding: quoted-printable
Message-id: <94462BEE-7D98-4B2D-A189-0DF1E7FB62A7@apple.com>
References: <308366D9-0749-4F76-A752-BC3BD8A3FAB9@tzi.org>
To: tsv-area@ietf.org
X-Mailer: Apple Mail (2.1508)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrKLMWRmVeSWpSXmKPExsUi2FCsoftuj1CQwbfdQhYL3ixmdmD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxsn1uxgL9gpWfD8xlbWBsZOvi5GTQ0LAROLc67dsELaYxIV7 64FsLg4hgclMEgf2LGKCcNYySSza9wasillAR6L3+zdmEJtXQE9i84wX7CC2sICqxLzpS8Fs NgEtiRefr4DVcwpYS9y9d5gJxGYBqrl2vxdqjpJE17JLrBC2tsSTdxdYIWbaSGw6sxisRkjA SuJ5P0SviICoRPfjU0A2B9ClshI7fydNYBSYheSiWUgumoVk6gJG5lWMAkWpOYmVZnqJBQU5 qXrJ+bmbGMGBVxi1g7FhudUhRgEORiUeXgMFoSAh1sSy4srcQ4wSHMxKIrzxJUAh3pTEyqrU ovz4otKc1OJDjNIcLErivGzeQCmB9MSS1OzU1ILUIpgsEwenVANjs6r6br83q4Qu/3GexdJf 6mjJe3BenMYH/r3ppiGfb75Zd7BhrVnlopSvT/f+fFiWlvBGZ9eSOxxXpWPkJ7/Kjv00rWDT LMNXjLPLpnR1GTmbV4pK2MrFRaacSF216Ml0w7jrrucYL5pUKvr8Zsjzl26U1wm0Crpf8fNs s6Rc+w6TvXEHSv4rsRRnJBpqMRcVJwIASlYHsjgCAAA=
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 00:48:57 -0000

On 1 Aug, 2013, at 01:31, Carsten Bormann <cabo@tzi.org> wrote:

> Nice work, and I really would like to use this.
>=20
> Having done RFC 2687, I can't help noticing that the C bit is in the =
wrong place.
> You only know whether the frame will be complete or will need to be =
suspended at the end, not at the start (or you have to proactively slice =
everything up, which is not what a suspend encoding is about).
>=20
> Simple fix: As frame end marker, use FE and FF, one for completed and =
one for suspended.
>=20
> Gr=FC=DFe, Carsten

There are two levels of suspension and resumption here.

At the same priority level chunks are interleaved round-robin. That's =
where the C bit is used, to indicate a final chunk of a message that's =
been knowingly broken into chunks in advance. This is done when messages =
are larger than a few Ethernet segments, and round-robin interleaving is =
deemed appropriate to reduce head-of-line blocking at the same priority =
level.

The other level of suspension and resumption is between different =
priority levels. A higher-priority chunk can interrupt a lower-priority =
byte stream at any byte boundary, without advance planning. A chunk is =
complete when the RECOBS decoder encounters an FF code byte. If the =
decoder encounters a zero byte at any other time, it recognises this as =
a higher-priority interruption. The existing state is saved (it's a =
pushdown stack) and decoding of the higher-priority chunk begins. That =
chunk ends with an FF code byte -- but before we get to that, it could =
itself be interrupted by an even higher-priority chunk. In principle the =
stack of interrupted chunks can be arbitrarily deep, but as a pragmatic =
engineering decision we limit it to four priority levels, to avoid =
requiring the receiver to have infinite memory.

We feel that the message dependency primitives are sufficient for =
ordering most messages, where the desired delivery ordering is known in =
advance (the kind of thing people today often think of achieving using =
priorities), and Minion's four priority levels then build on that by =
also supporting unplanned interruptions that are not known in advance.

Stuart Cheshire


From nalini.elkins@insidethestack.com  Tue Aug 27 06:56:03 2013
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5FCE21E80DF for <tsv-area@ietfa.amsl.com>; Tue, 27 Aug 2013 06:56:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ORvh3qorSPPd for <tsv-area@ietfa.amsl.com>; Tue, 27 Aug 2013 06:55:58 -0700 (PDT)
Received: from nm27-vm9.access.bullet.mail.gq1.yahoo.com (nm27-vm9.access.bullet.mail.gq1.yahoo.com [216.39.62.74]) by ietfa.amsl.com (Postfix) with ESMTP id 7BA3A21E80D5 for <tsv-area@ietf.org>; Tue, 27 Aug 2013 06:55:58 -0700 (PDT)
Received: from [216.39.60.175] by nm27.access.bullet.mail.gq1.yahoo.com with NNFMP; 27 Aug 2013 13:55:58 -0000
Received: from [216.39.60.236] by tm11.access.bullet.mail.gq1.yahoo.com with NNFMP; 27 Aug 2013 13:55:58 -0000
Received: from [127.0.0.1] by omp1007.access.mail.gq1.yahoo.com with NNFMP; 27 Aug 2013 13:55:58 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 120670.9629.bm@omp1007.access.mail.gq1.yahoo.com
Received: (qmail 70441 invoked by uid 60001); 27 Aug 2013 13:55:57 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1377611757; bh=G+ZlJBMl4S1zlwoUCLXPLfl8GGYosgY7IQfoC594Clk=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=GqOcZSoAfjnSd6NaFGCaefLAoXT5chHJ/JMXkR42c7u7fEGF1wz2US32GGnzwPgNqhrMxWNLYrBuBSgvjaMtz/CHZWpAmjFsXI50WcjedCHxSH0fzRoqhBIpDSHzf6Df7JQ1KXn+/prTaGelxD+dpmlVVBD225Afx7KIwe6IUi4=
X-YMail-OSG: 0sNadG4VM1lVMvMBWLKiO_U4QE9nCqLA3T5o_vO0_4gpwua 0c.WBaU1.uzNmpTBNxrt1h9U.dRX1ZDdEUfiLrEl9qSjALQCuNrqP1RQVsCC .ANUoGqjfY09eky5rxSpooUbEb4LnZQw4DPciiuBMLAzbiPFhq12OL5LK7H9 dNL85pz2aO3icFXvMGxv0zZv6FVJLZT_Z.IKW82JNnpbv8jGJWlZAHlx0BcE vbbMz4lbmSaQYtbLzAOyqwHn9IpA3kU.TlCUShdyENiYdOPlrcJ8P2PMMPsy VqRu8UzDDxKHWpPJ2zihTUw7Jk6Ycn8M62EchdGqJTb5RIGP1uF0fA9uLM.s MMj7JQO0HGLZj9qW2oUYKa791vGbgAYqeg0fi4O4dHeppq86KH7dUYiMeBO_ clS4C57Gb9tpyyd8eOM.7fzrP9gAZ5YYeipujAFSH1w_sFI2hjGOupxOggKD KsTXgOxkTqEIGmbxRAm5a3375fsIItPJqTeMyPQhhYAYQFfbMdvWZOMUiH9S wQSF_eTTzvTrQ5.wyIO_5nZ_lvj7JLvo1BTITXpsFFNAquSjKNfZZVrFhngH .U0veo70QjllVDNlOHsAy_VEj4B1t.roLHjag.QbXzj_URplWZQKt1H61tV8 LNq7TbfUCm4FzNht1x4i21Xlfus0TS8292secgBfiYGJSS7PXJ1zmkelF729 xz8BamSjxu7JrQr8l5L6PuNgPMrloBVGD.MiE6ffnREj83bjWsaJnDBN7uw- -
Received: from [66.51.70.107] by web2802.biz.mail.ne1.yahoo.com via HTTP; Tue, 27 Aug 2013 06:55:57 PDT
X-Rocket-MIMEInfo: 002.001, TG9yZW56bywKCkkgYmVsaWV2ZSB0aGF0IGR1cmluZyB0aGUgcXVlc3Rpb24gcG9ydGlvbiBvZiBvdXIgcHJvcG9zYWwgYXQgSUVURiA4NywgeW91IGhhZCBicm91Z2h0IHVwIHRoZSBwb2ludCB0aGF0IHRoZSBtZWFzdXJlbWVudHMgd2UgcHJvcG9zZSBtYXkgYmUgdmFsaWQgZm9yIGVudGVycHJpc2UgbmV0d29ya3MgYnV0IHdvdWxkIG5vdCBiZSBmb3Igc2l0ZXMgb3ZlciB0aGUgSW50ZXJuZXQuIMKgUGxlYXNlIGNvcnJlY3QgbWUgaWYgSSBhbSBub3Qgc3RhdGluZyB5b3VyIGNvbW1lbnRzIGNvcnJlY3RseS4BMAEBAQE-
X-Mailer: YahooMailWebService/0.8.155.576
Message-ID: <1377611757.70213.YahooMailNeo@web2802.biz.mail.ne1.yahoo.com>
Date: Tue, 27 Aug 2013 06:55:57 -0700 (PDT)
From: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: re: draft-elkins-v6ops-ipv6-end-to-end-rt-needed-00
To: Lorenzo Colitti <lorenzo@google.com>, IPv6 Ops WG <v6ops@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "joachim.fabini@tuwien.ac.at" <joachim.fabini@tuwien.ac.at>, "ALFRED C \(AL\)" <acmorton@att.com>, "trammell@tik.ee.ethz.ch" <trammell@tik.ee.ethz.ch>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.com>
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 13:56:03 -0000

Lorenzo,=0A=0AI believe that during the question portion of our proposal at=
 IETF 87, you had brought up the point that the measurements we propose may=
 be valid for enterprise networks but would not be for sites over the Inter=
net. =A0Please correct me if I am not stating your comments correctly.=0A=
=0AI would ask you to look at the activities of two working groups in parti=
cular. =A0LMAP and IPPM. =A0 They both are quite interested in measurements=
 of performance over the Internet. =A0I believe that our proposal can add v=
alue to the work of the below groups. =A0=A0=0A=0Ahttp://datatracker.ietf.o=
rg/wg/lmap/charter/=0A=0Ahttp://datatracker.ietf.org/wg/ippm/charter/=0A=0A=
=0AFor those who may be new to this discussion, they may care to look at ou=
r proposals:=0A=0Ahttp://tools.ietf.org/html/draft-elkins-6man-ipv6-pdm-des=
t-option-00=0A=0Ahttp://tools.ietf.org/html/draft-elkins-v6ops-ipv6-end-to-=
end-rt-needed-00=0A=0Ahttp://tools.ietf.org/html/draft-elkins-v6ops-ipv6-pa=
cket-sequence-needed-00=0A=0Ahttp://www.ietf.org/id/draft-elkins-v6ops-ipv6=
-pdm-recommended-usage-00.txt=0A=0A=0AThanks,=0A=0ANalini Elkins=0AInside P=
roducts, Inc.=0A(831) 659-8360=0Awww.insidethestack.com=0A

From joelja@bogus.com  Wed Aug 28 03:17:54 2013
Return-Path: <joelja@bogus.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2768611E817B; Wed, 28 Aug 2013 03:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id odFEGFD7bWXI; Wed, 28 Aug 2013 03:17:53 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id DD1F511E816F; Wed, 28 Aug 2013 03:17:52 -0700 (PDT)
Received: from mb-aye.local (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r7SAHnG6092574 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 28 Aug 2013 10:17:49 GMT (envelope-from joelja@bogus.com)
Message-ID: <521DCE46.6030501@bogus.com>
Date: Wed, 28 Aug 2013 03:17:42 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Nalini Elkins <nalini.elkins@insidethestack.com>, IPv6 Ops WG <v6ops@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>
Subject: Re: draft-elkins-v6ops-ipv6-pdm-recommended-usage-00
References: <51FA6667.4010200@bogus.com> <1377607721.23313.YahooMailNeo@web2806.biz.mail.ne1.yahoo.com>
In-Reply-To: <1377607721.23313.YahooMailNeo@web2806.biz.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 28 Aug 2013 10:17:50 +0000 (UTC)
Cc: "joachim.fabini@tuwien.ac.at" <joachim.fabini@tuwien.ac.at>, "ALFRED C \(AL\)" <acmorton@att.com>, "trammell@tik.ee.ethz.ch" <trammell@tik.ee.ethz.ch>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Aug 2013 10:17:54 -0000

On 8/27/13 5:48 AM, Nalini Elkins wrote:
> Joel,
>
> The synchronization and granularity of the timestamps for our proposal is one of the two outstanding issues.   I will take up the other issue (is this proposal useful for the Internet?) in a separate thread.
>
> We have also had some discussions with the folks in the IPPM group, so I am copying that working group on this thread.
>
> To restate the issues as I understand them (please correct me if I am wrong):
>
> 1.   Timestamp correlation depends on both ends being synchronized using a standard mechanism.
> 2.   This is a question of 'best practices'.
> 3.   Is the timestamp of sufficient quality or granularity to be useful.
>
> The answers to 1. and 2.  is yes.   Of course.   If people find this kind of data to be of use, then they will synchronize.  It is my understanding that activities other than those proposed by us require time synchronization.   So, it is quite likely that people may be doing this already.
>
> The answer to 3. is an interesting one.   I will cite a paper from Dr. Joachim Fabini.  It is available at:
>
> http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=6553584
>
> The significant passage is on page 7:
>
> "Mobile client and server are both accurately timesynchronized using EM-406A GPS modules with PPS support.    The RS232 level conversion required for this GPS module is implemented by a SparkFun 8334 GPS evaluation board
> which has been extended by the PPS circuit as proposed in [8]. The Network Time Protocol Daemon (ntp) synchronizes both endpoints accurately with global time using the evaluation board’s level-converted PPS and GPS time signals accessed by the kernel using native RS232 serial interfaces. Tests over several weeks have shown that this setup can synchronize the system clock accurately down to 5μs to global time. Even if deployed in nonoptimum conditions (indoor, 1st ﬂoor, street view with 6-ﬂoor opposite building), the clock accuracy is better than 50μs." 
network devices are by-in-large not built with embedded GPS.
 
By way of demonstration of the level of measuerment error I expect.
Juniper RPM can do asic based timestamping on measurement traffic
between two devices. I have a path, the length of which does not vary by
much (it's a wave-length between san jose and ashburn virginia). the
routers derive time from a clustered of peered stratum 2 servers which
in turn are clients of stratum-1 sources that are traceable to NIST. 

in the following graph:

http://i.imgur.com/AkDRs9D.png

the top line is the RTT as measured by the sending router.

the green line is the difference between the timestamp applied by the
reciveing router in ashburn and the timestamp applied by the sending
router, and the redline is the differnce between the ashburn router
sending timestamp and the timestamp genrated when the packet is recieved
again in san jose.

the vertical axis is thousands of microseconds.

I'm farily comfortable that my NTP and my devices clocks aren't totaly
busted. I'm also comfortable with the idea that there's substantially
higher variation  out there when you get out a of a single admistrative
domain.
> I believe that 5 - 50 microseconds of accuracy is sufficient for triage.  In our proposal, we want three times: inbound network path, the server processing time, or the outbound network path.  I believe that for accurate triage, we will be able to say that the problem is in the inbound network path, the server, or the outbound network path even if the clocks vary by 50 microseconds.  In my experience, the differences between the 3 calculations which we want vary by quite a bit more than 50 microseconds.   I actually have quite a bit of data available to prove this from running diagnostics with a number of companies and over the Internet in the last few years and I will do a paper (when I get a free weekend!).   I will discuss my findings with the IPPM group as I believe this to be of interest to them.
>
> For those who may be new to this discussion, they may care to look at our proposals:
>
> http://tools.ietf.org/html/draft-elkins-6man-ipv6-pdm-dest-option-00
>
>
> http://tools.ietf.org/html/draft-elkins-v6ops-ipv6-end-to-end-rt-needed-00
>
>
> http://tools.ietf.org/html/draft-elkins-v6ops-ipv6-packet-sequence-needed-00
>
>
> http://www.ietf.org/id/draft-elkins-v6ops-ipv6-pdm-recommended-usage-00.txt
>
>
> Thanks,
>
> Nalini Elkins
> Inside Products, Inc.
> (831) 659-8360
> www.insidethestack.com
>
>
>
> ________________________________
> From: joel jaeggli <joelja@bogus.com>
> To: Nalini Elkins <nalini.elkins@insidethestack.com>; IPv6 Ops WG <v6ops@ietf.org> 
> Sent: Thursday, August 1, 2013 6:45 AM
> Subject: draft-elkins-v6ops-ipv6-pdm-recommended-usage-00
>
>
> Since I ran into you in the hall and the dicussion turned to ntp...
>
> I'll try and be succinct, and as a non-expert in the time field this
> should be taken with a grain of salt.
>
> The generic utility of a high-resultion time-stamp is imho dodgey
> outside of situations where the clocks are deliberately syncronized and
> traceable to a common standard whether the protocol used for this is ntp
> or ieee 1588 (or since this is the ietf PTPV2) . While this is tractable
> for devices in a single span of control, the agruement that ntp might be
> suffcient to make this timstamp useful generically between two
> aribitratry devices where this functionality may need to be enabled is
> imho a hard one to assert.
>
> It is a set of operational practice and discipline moreso than the
> choice of technology that allows for a high-resolution timestamp to have
> sufficient precision to be useful between hosts.
>
> joel 
>


From nalini.elkins@insidethestack.com  Wed Aug 28 03:53:22 2013
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7033811E81B7 for <tsv-area@ietfa.amsl.com>; Wed, 28 Aug 2013 03:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gb+A9GpyHeGR for <tsv-area@ietfa.amsl.com>; Wed, 28 Aug 2013 03:53:17 -0700 (PDT)
Received: from nm27-vm1.access.bullet.mail.bf1.yahoo.com (nm27-vm1.access.bullet.mail.bf1.yahoo.com [216.109.115.224]) by ietfa.amsl.com (Postfix) with ESMTP id 8BB6B11E817B for <tsv-area@ietf.org>; Wed, 28 Aug 2013 03:53:15 -0700 (PDT)
Received: from [66.196.81.162] by nm27.access.bullet.mail.bf1.yahoo.com with NNFMP; 28 Aug 2013 10:53:12 -0000
Received: from [66.196.81.136] by tm8.access.bullet.mail.bf1.yahoo.com with NNFMP; 28 Aug 2013 10:53:12 -0000
Received: from [127.0.0.1] by omp1012.access.mail.bf1.yahoo.com with NNFMP; 28 Aug 2013 10:53:12 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 92516.43803.bm@omp1012.access.mail.bf1.yahoo.com
Received: (qmail 92708 invoked by uid 60001); 28 Aug 2013 10:53:11 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1377687191; bh=pDkUffidHh9Vk1HkClDtWjnNCUXYNIbaNrYo+ISSrk8=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Is/ww4tuadW6pQUsVE0pvFZsZdIm/q2nSYjcN5+jskU+NfPzSNGDq1AXcpHQ4DdYICe9bRu4qo2fnqXfJX0pswCYNuqVcqer1NYOjbqzQnMijSzhO3KVPzgUojROmkhPWTTVvpeUVfx/qNt06hD7SekLoYYR8M2mdF3sZZ2Ek5E=
X-YMail-OSG: YZaOUjQVM1np1QQSmbxwgrJjKoq6YF0c0yM4Eo_TR.9j4P3 ifl6uZKw7UW42uSSSf8u6p4aXpxYbar9X17DZtuK39Q72s9lhJe4atsd4KEW l5pcTTR9.eluq4a2FpEZ_lJj0Ye.pcPiAeUWu992LwH6AH_CLxHA7nz.PHZa vZcew0ztdsCp9_CcmD_5OoLtMGm8agB1c8_0jQmpf1Eq8i7ORQAzkCOUhgI. qRF3b..GZsGqK3_qi94sqBiTuM9knMQGStU_EcyvrbQMIqChf6hkMM5Niz60 ebSwwTWVgVGH2lYO3NVVqJAwzI6nmj2cwjqur89CwqPJMlTZ_xUdcBJXMwZq B.AL4oMnSgBma1ruAL3ff3hK2Ze9zGjfGVmJrcAx7MyWkCpA9vHUU4U.eClS amaFjPIbduGovAoBt4NMQCEZaZC_NP1a641C2WIHas9ignDOQ7HEJHs6CzgX rgU8INcNrgJrvdz2JNwKZQZs1st3zI2p4YXW80pL1ilDJz0mH24wgdGi.7MN Hrkczpxvkmpf8TG4S8uSkBiBLsdSGs0po2k_7yY2zzqoAPgse.5OhIHozYDs Q5SrlMHNrdq8.nbPrkDylb21QLIlW3y_6ILFs3zccs0Hlx3jR3Ir9ttNCS0E x5YUyJ4ocSbI_FHIpfcWu.vmbYmpY2jG3iupSnkt6tj7qMT6LCzYHkcxIrB7 O56bP44eWZg3uxvk1P5JxHxo1Ba4bQKYFJgLYK_e8Sq9NjivxIGSzFpNoTT3 KHzA74V9mj6NwCL7mOXLBwjQfCU.77HN1upmhjFkU_BOp.1MTf45KbHxqOkC BbgcrRSJqyW_LTdozTiN0NQPWkdmKwW9YeEO7hX5f5_OPYutDAvCyjI5Ttg- -
Received: from [63.68.129.61] by web2803.biz.mail.ne1.yahoo.com via HTTP; Wed, 28 Aug 2013 03:53:11 PDT
X-Rocket-MIMEInfo: 002.001, Sm9lbCwKCgo.Pm5ldHdvcmsgZGV2aWNlcyBhcmUgYnktaW4tbGFyZ2Ugbm90IGJ1aWx0IHdpdGggZW1iZWRkZWQgR1BTLgoKV2UgYXJlIG5vdCB0YWxraW5nIGFib3V0IG5ldHdvcmsgZGV2aWNlcy4gwqAgT3VyIGhlYWRlciBpcyBhIERlc3RpbmF0aW9uIE9wdGlvbnMgaGVhZGVyIHdoaWNoIE9OTFkgZW5kIGhvc3RzIG5lZWQgdG8gYmUgY29uY2VybmVkIHdpdGguIMKgIFlvdXIgZGF0YSBpcyB2ZXJ5IGludGVyZXN0aW5nIGJ1dCBpdCBpcyBub3Qgd2hhdCB3ZSBhcmUgdGFsa2luZyBhYm91dC4KCldoYXQgaXMBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.156.576
References: <51FA6667.4010200@bogus.com> <1377607721.23313.YahooMailNeo@web2806.biz.mail.ne1.yahoo.com> <521DCE46.6030501@bogus.com>
Message-ID: <1377687191.85628.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com>
Date: Wed, 28 Aug 2013 03:53:11 -0700 (PDT)
From: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Re: draft-elkins-v6ops-ipv6-pdm-recommended-usage-00
To: joel jaeggli <joelja@bogus.com>, IPv6 Ops WG <v6ops@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>
In-Reply-To: <521DCE46.6030501@bogus.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: "joachim.fabini@tuwien.ac.at" <joachim.fabini@tuwien.ac.at>, "ALFRED C \(AL\)" <acmorton@att.com>, "trammell@tik.ee.ethz.ch" <trammell@tik.ee.ethz.ch>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.com>
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Aug 2013 10:53:22 -0000

Joel,=0A=0A=0A>>network devices are by-in-large not built with embedded GPS=
.=0A=0AWe are not talking about network devices. =C2=A0 Our header is a Des=
tination Options header which ONLY end hosts need to be concerned with. =C2=
=A0 Your data is very interesting but it is not what we are talking about.=
=0A=0AWhat is of concern is what actual end hosts can do. =C2=A0This is a c=
onversation that I will be starting with the OS vendors. =C2=A0 =C2=A0That =
is why Joachim's paper was of interest.=0A=0A=0AThanks,=0A=0ANalini Elkins=
=0AInside Products, Inc.=0A(831) 659-8360=0Awww.insidethestack.com=0A=0A=0A=
________________________________=0AFrom: joel jaeggli <joelja@bogus.com>=0A=
To: Nalini Elkins <nalini.elkins@insidethestack.com>; IPv6 Ops WG <v6ops@ie=
tf.org>; "tsv-area@ietf.org" <tsv-area@ietf.org> =0ACc: ALFRED C (AL) <acmo=
rton@att.com>; "joachim.fabini@tuwien.ac.at" <joachim.fabini@tuwien.ac.at>;=
 "trammell@tik.ee.ethz.ch" <trammell@tik.ee.ethz.ch> =0ASent: Wednesday, Au=
gust 28, 2013 3:17 AM=0ASubject: Re: draft-elkins-v6ops-ipv6-pdm-recommende=
d-usage-00=0A=0A=0AOn 8/27/13 5:48 AM, Nalini Elkins wrote:=0A> Joel,=0A>=
=0A> The synchronization and granularity of the timestamps for our proposal=
 is one of the two outstanding issues.=C2=A0=C2=A0=C2=A0I will take up the =
other issue (is this proposal useful for the Internet?) in a separate threa=
d.=0A>=0A> We have also had some discussions with the folks in the IPPM gro=
up, so I am copying that working group on this thread.=0A>=0A> To restate t=
he issues as I understand them (please correct me if I am wrong):=0A>=0A> 1=
.=C2=A0=C2=A0=C2=A0Timestamp correlation depends on both ends being synchro=
nized using a standard mechanism.=0A> 2.=C2=A0=C2=A0=C2=A0This is a questio=
n of 'best practices'.=0A> 3.=C2=A0=C2=A0=C2=A0Is the timestamp of sufficie=
nt quality or granularity to be useful.=0A>=0A> The answers to 1. and 2.=C2=
=A0 is yes.=C2=A0=C2=A0=C2=A0Of course.=C2=A0=C2=A0=C2=A0If people find thi=
s kind of data to be of use, then they will synchronize.=C2=A0 It is my und=
erstanding that activities other than those proposed by us require time syn=
chronization.=C2=A0=C2=A0=C2=A0So, it is quite likely that people may be do=
ing this already.=0A>=0A> The answer to 3. is an interesting one.=C2=A0=C2=
=A0=C2=A0I will cite a paper from Dr. Joachim Fabini.=C2=A0 It is available=
 at:=0A>=0A> http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=3D6=
553584=0A>=0A> The significant passage is on page 7:=0A>=0A> "Mobile client=
 and server are both accurately timesynchronized using EM-406A GPS modules =
with PPS support.=C2=A0 =C2=A0 The RS232 level conversion required for this=
 GPS module is implemented by a SparkFun 8334 GPS evaluation board=0A> whic=
h has been extended by the PPS circuit as proposed in [8]. The Network Time=
 Protocol Daemon (ntp) synchronizes both endpoints accurately with global t=
ime using the evaluation board=E2=80=99s level-converted PPS and GPS time s=
ignals accessed by the kernel using native RS232 serial interfaces. Tests o=
ver several weeks have shown that this setup can synchronize the system clo=
ck accurately down to 5=CE=BCs to global time. Even if deployed in nonoptim=
um conditions (indoor, 1st =EF=AC=82oor, street view with 6-=EF=AC=82oor op=
posite building), the clock accuracy is better than 50=CE=BCs." =0Anetwork =
devices are by-in-large not built with embedded GPS.=0A=0ABy way of demonst=
ration of the level of measuerment error I expect.=0AJuniper RPM can do asi=
c based timestamping on measurement traffic=0Abetween two devices. I have a=
 path, the length of which does not vary by=0Amuch (it's a wave-length betw=
een san jose and ashburn virginia). the=0Arouters derive time from a cluste=
red of peered stratum 2 servers which=0Ain turn are clients of stratum-1 so=
urces that are traceable to NIST. =0A=0Ain the following graph:=0A=0Ahttp:/=
/i.imgur.com/AkDRs9D.png=0A=0Athe top line is the RTT as measured by the se=
nding router.=0A=0Athe green line is the difference between the timestamp a=
pplied by the=0Areciveing router in ashburn and the timestamp applied by th=
e sending=0Arouter, and the redline is the differnce between the ashburn ro=
uter=0Asending timestamp and the timestamp genrated when the packet is reci=
eved=0Aagain in san jose.=0A=0Athe vertical axis is thousands of microsecon=
ds.=0A=0AI'm farily comfortable that my NTP and my devices clocks aren't to=
taly=0Abusted. I'm also comfortable with the idea that there's substantiall=
y=0Ahigher variation=C2=A0 out there when you get out a of a single admistr=
ative=0Adomain.=0A> I believe that 5 - 50 microseconds of accuracy is suffi=
cient for triage.=C2=A0 In our proposal, we want three times: inbound netwo=
rk path, the server processing time, or the outbound network path.=C2=A0 I =
believe that for accurate triage, we will be able to say that the problem i=
s in the inbound network path, the server, or the outbound network path eve=
n if the clocks vary by 50 microseconds.=C2=A0 In my experience, the differ=
ences between the 3 calculations which we want vary by quite a bit more tha=
n 50 microseconds.=C2=A0=C2=A0=C2=A0I actually have quite a bit of data ava=
ilable to prove this from running diagnostics with a number of companies an=
d over the Internet in the last few years and I will do a paper (when I get=
 a free weekend!).=C2=A0=C2=A0=C2=A0I will discuss my findings with the IPP=
M group as I believe this to be of interest to them.=0A>=0A> For those who =
may be new to this discussion, they may care to look at our proposals:=0A>=
=0A> http://tools.ietf.org/html/draft-elkins-6man-ipv6-pdm-dest-option-00=
=0A>=0A>=0A> http://tools.ietf.org/html/draft-elkins-v6ops-ipv6-end-to-end-=
rt-needed-00=0A>=0A>=0A> http://tools.ietf.org/html/draft-elkins-v6ops-ipv6=
-packet-sequence-needed-00=0A>=0A>=0A> http://www.ietf.org/id/draft-elkins-=
v6ops-ipv6-pdm-recommended-usage-00.txt=0A>=0A>=0A> Thanks,=0A>=0A> Nalini =
Elkins=0A> Inside Products, Inc.=0A> (831) 659-8360=0A> www.insidethestack.=
com=0A>=0A>=0A>=0A> ________________________________=0A> From: joel jaeggli=
 <joelja@bogus.com>=0A> To: Nalini Elkins <nalini.elkins@insidethestack.com=
>; IPv6 Ops WG <v6ops@ietf.org> =0A> Sent: Thursday, August 1, 2013 6:45 AM=
=0A> Subject: draft-elkins-v6ops-ipv6-pdm-recommended-usage-00=0A>=0A>=0A> =
Since I ran into you in the hall and the dicussion turned to ntp...=0A>=0A>=
 I'll try and be succinct, and as a non-expert in the time field this=0A> s=
hould be taken with a grain of salt.=0A>=0A> The generic utility of a high-=
resultion time-stamp is imho dodgey=0A> outside of situations where the clo=
cks are deliberately syncronized and=0A> traceable to a common standard whe=
ther the protocol used for this is ntp=0A> or ieee 1588 (or since this is t=
he ietf PTPV2) . While this is tractable=0A> for devices in a single span o=
f control, the agruement that ntp might be=0A> suffcient to make this timst=
amp useful generically between two=0A> aribitratry devices where this funct=
ionality may need to be enabled is=0A> imho a hard one to assert.=0A>=0A> I=
t is a set of operational practice and discipline moreso than the=0A> choic=
e of technology that allows for a high-resolution timestamp to have=0A> suf=
ficient precision to be useful between hosts.=0A>=0A> joel =0A>=C2=A0

From nalini.elkins@insidethestack.com  Thu Aug 29 05:47:50 2013
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35DAD11E8103 for <tsv-area@ietfa.amsl.com>; Thu, 29 Aug 2013 05:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YYuzWWJ-3YS7 for <tsv-area@ietfa.amsl.com>; Thu, 29 Aug 2013 05:47:37 -0700 (PDT)
Received: from nm23-vm10.access.bullet.mail.bf1.yahoo.com (nm23-vm10.access.bullet.mail.bf1.yahoo.com [216.109.115.169]) by ietfa.amsl.com (Postfix) with ESMTP id A431021F9F50 for <tsv-area@ietf.org>; Thu, 29 Aug 2013 05:47:37 -0700 (PDT)
Received: from [66.196.81.161] by nm23.access.bullet.mail.bf1.yahoo.com with NNFMP; 29 Aug 2013 12:47:35 -0000
Received: from [66.196.81.133] by tm7.access.bullet.mail.bf1.yahoo.com with NNFMP; 29 Aug 2013 12:47:35 -0000
Received: from [127.0.0.1] by omp1009.access.mail.bf1.yahoo.com with NNFMP; 29 Aug 2013 12:47:35 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 788156.87636.bm@omp1009.access.mail.bf1.yahoo.com
Received: (qmail 86216 invoked by uid 60001); 29 Aug 2013 12:47:35 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1377780455; bh=srL6ywz6d0+CCUSmlcFicZzKmk+MISUmk0goAJx1zWI=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=FCrD1sPmERmufWACeUEdgfTkFT+rZaoKh97vbjCZLt9ZO/6uq1yjnW4p8QKMdm9+AKzdxDrJ/KpzFOSoI7L4mFycb77KewOV3jKUQbZPRANoX28nMsD5Ech5QzWPNpG4RmqUkz9zechud9+eVs+hu+5ZgoK/5CvKo8AuOO775Cs=
X-YMail-OSG: QCDRpxUVM1mvMiAEEEPIHz40LptOmjcoNI2ZcvcY5phaa1j vYw2LdXRCTMdSikE5AFReJG.IxNUGULKXt6jqDRBY.bRilYP7Dbuui4.N88S Tft8XznKJPS.Mti34WDaI6nYiwpqrGJbDnWb301Ae25xi_9AJCM4uEUTMOTq gBBcQri.3ySCekLwiJVwpN5vMXFHPNq.gTSxhysx8FP6e.L2oYCGRjuYJOdf XiuFAQimBrepPV08QJEqOQ6dr1Loaf_wE5deatuiJtmjpXBlCuwNs08KvGjv H.oY4N2XOCQWObm7ygmdS6F8MHB5Z9LPEwNXRMnHxkd3dhJSBatsuQDa_h4Q 9SzKkIrJfFTGJPNOmXy28WpP4Cm9jr8JQ.TZxp82_23JpY9k1dWwI.NVfbhs 6GqIl2yZ9x8bRzLavcBCstMIQ.dMBszOs_nFHi1upzWbqGrtdzz6D7MsuUmP si01mwFhgTnUs3ywOB5pUoSRr8eA60igDjZS1R46kHFSx7C53ZYmSqnj76uv QYfSi_JeCxb_qmz_7u0_EPjp3kxFnrg6lVFWnb6rts4JVY8nEAMYG2MMZYbt psSl9td.37CORuxljH1e4kWQIFAIvPR7VDZudoAyJM9xFSGuQ5HTZA1wwvfr eLX6O0jD0Ph2yoke9nTK3lqn6WImOZiVcwtinCCOZ_mUBJj5wtSLOnHbgkQU NqvV0u2Kf.mHimZqtX1zQgJWMtULb3ScMns3R4IjJlmxVRFD9Uo85NKoJsUB kgnLQYes9o4SfEtE-
Received: from [70.192.203.170] by web2805.biz.mail.ne1.yahoo.com via HTTP; Thu, 29 Aug 2013 05:47:35 PDT
X-Rocket-MIMEInfo: 002.001, UGxlYXNlIHRha2UgYSBsb29rIGF0OgoKaHR0cDovL3d3dy5yaXBlLm5ldC9kYXRhLXRvb2xzL3N0YXRzL3R0bS90ZXN0LXRyYWZmaWMtbWVhc3VyZW1lbnQtc2VydmljZQoKCk5vdGUgdGhhdCB3aGF0IHRoZXkgcHJvdmlkZSBpczoKCsKgwqDCoMKgKiBOVFAtc2VydmVyLCB0aGUgdGVzdC1ib3hlcyBjYW4gYWN0IGEgc3RyYXR1bSAxIHNlcnZlciBmb3IgdGhlIG1hY2hpbmVzIG9uIHlvdXIgbmV0d29yaywgcHJvdmlkaW5nIHRpbWUtc3RhbXBzIHdpdGggYW4gYWNjdXJhY3kgb2YgMTAgbWljcm9zZWNvbmRzLgoBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.156.576
References: <51FA6667.4010200@bogus.com> <1377607721.23313.YahooMailNeo@web2806.biz.mail.ne1.yahoo.com>, <521DCE46.6030501@bogus.com> <2845723087023D4CB5114223779FA9C83BF8C4F1@njfpsrvexg8.research.att.com> <521EB4A2.2060006@bogus.com>
Message-ID: <1377780455.80051.YahooMailNeo@web2805.biz.mail.ne1.yahoo.com>
Date: Thu, 29 Aug 2013 05:47:35 -0700 (PDT)
From: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Re: draft-elkins-v6ops-ipv6-pdm-recommended-usage-00
To: joel jaeggli <joelja@bogus.com>, "MORTON JR., ALFRED C \(AL\)" <acmorton@att.com>, IPv6 Ops WG <v6ops@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>
In-Reply-To: <521EB4A2.2060006@bogus.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "joachim.fabini@tuwien.ac.at" <joachim.fabini@tuwien.ac.at>, "trammell@tik.ee.ethz.ch" <trammell@tik.ee.ethz.ch>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.com>
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 12:47:50 -0000

Please take a look at:=0A=0Ahttp://www.ripe.net/data-tools/stats/ttm/test-t=
raffic-measurement-service=0A=0A=0ANote that what they provide is:=0A=0A=A0=
=A0=A0=A0* NTP-server, the test-boxes can act a stratum 1 server for the ma=
chines on your network, providing time-stamps with an accuracy of 10 micros=
econds.=0A=0AThanks,=0A=0ANalini Elkins=0AInside Products, Inc.=0A(831) 659=
-8360=0Awww.insidethestack.com=A0

From joelja@bogus.com  Thu Aug 29 10:48:37 2013
Return-Path: <joelja@bogus.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE1CE21E809B; Thu, 29 Aug 2013 10:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ooE1AnmBgOfO; Thu, 29 Aug 2013 10:48:36 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id CA87F21E80A3; Thu, 29 Aug 2013 10:48:36 -0700 (PDT)
Received: from mb-aye.local (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r7THmVfD012506 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 29 Aug 2013 17:48:32 GMT (envelope-from joelja@bogus.com)
Message-ID: <521F896A.9090305@bogus.com>
Date: Thu, 29 Aug 2013 10:48:26 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Nalini Elkins <nalini.elkins@insidethestack.com>, "MORTON JR., ALFRED C \(AL\)" <acmorton@att.com>, IPv6 Ops WG <v6ops@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>
Subject: Re: draft-elkins-v6ops-ipv6-pdm-recommended-usage-00
References: <51FA6667.4010200@bogus.com> <1377607721.23313.YahooMailNeo@web2806.biz.mail.ne1.yahoo.com>, <521DCE46.6030501@bogus.com> <2845723087023D4CB5114223779FA9C83BF8C4F1@njfpsrvexg8.research.att.com> <521EB4A2.2060006@bogus.com> <1377780455.80051.YahooMailNeo@web2805.biz.mail.ne1.yahoo.com>
In-Reply-To: <1377780455.80051.YahooMailNeo@web2805.biz.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 29 Aug 2013 17:48:34 +0000 (UTC)
Cc: "joachim.fabini@tuwien.ac.at" <joachim.fabini@tuwien.ac.at>, "trammell@tik.ee.ethz.ch" <trammell@tik.ee.ethz.ch>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 17:48:37 -0000

On 8/29/13 5:47 AM, Nalini Elkins wrote:
> Please take a look at:
>
> http://www.ripe.net/data-tools/stats/ttm/test-traffic-measurement-service
>
>
> Note that what they provide is:
>
>     * NTP-server, the test-boxes can act a stratum 1 server for the machines on your network, providing time-stamps with an accuracy of 10 microseconds.
With respect to the IETF 87 presentation/discussion I think is is a
dicussion of the quality of time and it relationship to the general
utility of of pdm optional header, not the availability of specific
point solutions.

With respect to the design of TTM the claimed timestamp accuracy is
associated with packets emitted by the TTM not other devices associated
with them which is course subject to the same general constraints other
ntp deployments.
> Thanks,
>
> Nalini Elkins
> Inside Products, Inc.
> (831) 659-8360
> www.insidethestack.com 
>


From nalini.elkins@insidethestack.com  Thu Aug 29 18:36:21 2013
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5354911E815B for <tsv-area@ietfa.amsl.com>; Thu, 29 Aug 2013 18:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mekc9PJKS5DS for <tsv-area@ietfa.amsl.com>; Thu, 29 Aug 2013 18:36:15 -0700 (PDT)
Received: from nm15-vm1.access.bullet.mail.gq1.yahoo.com (nm15-vm1.access.bullet.mail.gq1.yahoo.com [216.39.63.13]) by ietfa.amsl.com (Postfix) with ESMTP id 93E3C11E8191 for <tsv-area@ietf.org>; Thu, 29 Aug 2013 18:36:15 -0700 (PDT)
Received: from [216.39.60.176] by nm15.access.bullet.mail.gq1.yahoo.com with NNFMP; 30 Aug 2013 01:36:15 -0000
Received: from [216.39.60.161] by tm12.access.bullet.mail.gq1.yahoo.com with NNFMP; 30 Aug 2013 01:36:15 -0000
Received: from [127.0.0.1] by omp1027.access.mail.gq1.yahoo.com with NNFMP; 30 Aug 2013 01:36:15 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 64107.89297.bm@omp1027.access.mail.gq1.yahoo.com
Received: (qmail 16051 invoked by uid 60001); 30 Aug 2013 01:36:14 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1377826574; bh=JyMZVr5TrRe11wAMzSViK9pyRsg5gL52tucqFtwBU3g=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=6HSUraSwkSg+6wSs6ped+/YUTN+qErWZlDzSZ/8Cpai4ikWgQ7kNRn3KIvuxDF6vmn6SPDq7MebohjmgXKYldlVWwUEGoG+qagOaOATilZymPxgtrkr0k3mge6mzd0uzHBDWOmyRejZcXIcj7hNZIS/rD+hyxSMcJRjfnLI9Sng=
X-YMail-OSG: p6h4xIUVM1mVG7Oc1zn6jfL.KfPlKbx6uQam9lWYVGTreWT aIEzu9HY8gSdCwlox6_dQ8Q09yN2duiFMgOjJw_NRoMaAcBqMGh0hiUnc2Zs fxo8EV1QPBNrbuSKIkdjyGSiNpsm3gESqIMPv_H_Y55jh2WxWZuq_gF4mPps eFIaH6VC8lWFkRKG7tuSUKZY.sINQp4ykInjiFKumSHeiGQEYaSJkOUED8gh i0xOC52EMrOSKQ.w3EucxhJrczvp0dtqXmU.H3lBLVEfFa760Y3BXbZUNCsu gblWS4ojJz1xBxoj_adN7jCAujXgO5P.wNW_ahL06l0av2gzX_ZabmUhDJBa uSqNe8TFprgd5oSLJgMLmE0xE7CMQDbRcfyo3OOZwVZhODspB1Ge0BOV_kXY GabCOmJC3CsF8BnZAP2Rn9eLCkT3wDvcTM3LFotSwBD7FhYwRGXzFZiyD.LU eY_ZAPvI1HxDi9y8UbwdSRUYfpS86DdlP_ZBIZ.KdkeP66iyE2FQQvGXOXDG a6tglkKaJAtVMear2QZ.Fge8y_9vd3ZpIwy.kWEGkGe12lb_TNWD0ALuOGLl zgMbxnBUgQY5YwOMXIR2OQZ9R6Pve6JWm5m2q62UsfY0RBklqGaNgwfzSn2a CuK4oPk1.ZdfknQbzonaIvGP7gIsfquM8bunhWlxsTllmsJv.qNbPj.ToYhx BpavB428-
Received: from [70.198.65.73] by web2806.biz.mail.ne1.yahoo.com via HTTP; Thu, 29 Aug 2013 18:36:14 PDT
X-Rocket-MIMEInfo: 002.001, CgoKT24gOC8yOS8xMyA1OjQ3IEFNLCBOYWxpbmkgRWxraW5zIHdyb3RlOgo.IFBsZWFzZSB0YWtlIGEgbG9vayBhdDoKPgo.IGh0dHA6Ly93d3cucmlwZS5uZXQvZGF0YS10b29scy9zdGF0cy90dG0vdGVzdC10cmFmZmljLW1lYXN1cmVtZW50LXNlcnZpY2UKPgo.Cj4gTm90ZSB0aGF0IHdoYXQgdGhleSBwcm92aWRlIGlzOgo.Cj7CoCDCoCAgKiBOVFAtc2VydmVyLCB0aGUgdGVzdC1ib3hlcyBjYW4gYWN0IGEgc3RyYXR1bSAxIHNlcnZlciBmb3IgdGhlIG1hY2hpbmVzIG9uIHlvdXIgbmV0d29yaywgcHJvdmkBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.156.576
References: <51FA6667.4010200@bogus.com> <1377607721.23313.YahooMailNeo@web2806.biz.mail.ne1.yahoo.com>, <521DCE46.6030501@bogus.com> <2845723087023D4CB5114223779FA9C83BF8C4F1@njfpsrvexg8.research.att.com> <521EB4A2.2060006@bogus.com> <1377780455.80051.YahooMailNeo@web2805.biz.mail.ne1.yahoo.com> <521F896A.9090305@bogus.com>
Message-ID: <1377826574.11519.YahooMailNeo@web2806.biz.mail.ne1.yahoo.com>
Date: Thu, 29 Aug 2013 18:36:14 -0700 (PDT)
From: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Re: draft-elkins-v6ops-ipv6-pdm-recommended-usage-00
To: joel jaeggli <joelja@bogus.com>, "MORTON JR., ALFRED C \(AL\)" <acmorton@att.com>, IPv6 Ops WG <v6ops@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>
In-Reply-To: <521F896A.9090305@bogus.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="1510626085-1504756420-1377826574=:11519"
Cc: "joachim.fabini@tuwien.ac.at" <joachim.fabini@tuwien.ac.at>, "trammell@tik.ee.ethz.ch" <trammell@tik.ee.ethz.ch>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.com>
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 01:36:21 -0000

--1510626085-1504756420-1377826574=:11519
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=0A=0A=0AOn 8/29/13 5:47 AM, Nalini Elkins wrote:=0A> Please take a look at=
:=0A>=0A> http://www.ripe.net/data-tools/stats/ttm/test-traffic-measurement=
-service=0A>=0A>=0A> Note that what they provide is:=0A>=0A>=A0 =A0  * NTP-=
server, the test-boxes can act a stratum 1 server for the machines on your =
network, providing time-stamps with an accuracy of 10 microseconds.=0A>With=
 respect to the IETF 87 presentation/discussion I think is is a=0A>dicussio=
n of the quality of time and it relationship to the general=0A>utility of o=
f pdm optional header, not the availability of specific=0A>point solutions.=
=0A=0ALet me back up and see if I can restate your basic concern in simple =
words so that I am sure that I understand you.=0A=0AI believe that you are =
concerned that the timestamps provided by NTP will not be accurate enough i=
f the timestamps are taken from more than one administrative domain. =A0 Ou=
r PDM proposal depends on fairly reliable timestamps. =A0So, if the timesta=
mps are not reliable, then the PDM is not very useful.=0A=0APlease let me k=
now if I have understood you.=0A=0AThanks,=0ANalini
--1510626085-1504756420-1377826574=:11519
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ar=
ial, helvetica, sans-serif;font-size:12pt"><div><br></div><div style=3D"fon=
t-family: arial, helvetica, sans-serif; font-size: 12pt;"><div style=3D"fon=
t-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"><d=
iv dir=3D"ltr"> </div> <div class=3D"y_msg_container"><br>=0AOn 8/29/13 5:4=
7 AM, Nalini Elkins wrote:<br>&gt; Please take a look at:<br>&gt;<br>&gt; h=
ttp://www.ripe.net/data-tools/stats/ttm/test-traffic-measurement-service<br=
>&gt;<br>&gt;<br>&gt; Note that what they provide is:<br>&gt;<br>&gt;&nbsp;=
 &nbsp;  * NTP-server, the test-boxes can act a stratum 1 server for the ma=
chines on your network, providing time-stamps with an accuracy of 10 micros=
econds.<br>&gt;With respect to the IETF 87 presentation/discussion I think =
is is a<br>&gt;dicussion of the quality of time and it relationship to the =
general<br>&gt;utility of of pdm optional header, not the availability of s=
pecific<br>&gt;point solutions.<br><br>Let me back up and see if I can rest=
ate your basic concern in simple words so that I am sure that I understand =
you.</div><div class=3D"y_msg_container"><br></div><div class=3D"y_msg_cont=
ainer">I believe that you are concerned that the timestamps provided by NTP=
 will not be accurate enough if the timestamps are taken
 from more than one administrative domain. &nbsp; Our PDM proposal depends =
on fairly reliable timestamps. &nbsp;So, if the timestamps are not reliable=
, then the PDM is not very useful.</div><div class=3D"y_msg_container"><br>=
</div><div class=3D"y_msg_container">Please let me know if I have understoo=
d you.</div><div class=3D"y_msg_container"><br></div><div class=3D"y_msg_co=
ntainer">Thanks,<br>Nalini<br><br><br><br></div> </div> </div>  </div></bod=
y></html>
--1510626085-1504756420-1377826574=:11519--

From joelja@bogus.com  Fri Aug 30 11:46:11 2013
Return-Path: <joelja@bogus.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5321221F9D23; Fri, 30 Aug 2013 11:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id brXXwjxWH7Bm; Fri, 30 Aug 2013 11:46:06 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id B96F721F9CC2; Fri, 30 Aug 2013 11:46:06 -0700 (PDT)
Received: from mb-aye.corp.zynga.com (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r7UIk0n8027622 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 30 Aug 2013 18:46:01 GMT (envelope-from joelja@bogus.com)
Message-ID: <5220E863.1020700@bogus.com>
Date: Fri, 30 Aug 2013 11:45:55 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Nalini Elkins <nalini.elkins@insidethestack.com>, "MORTON JR., ALFRED C \(AL\)" <acmorton@att.com>, IPv6 Ops WG <v6ops@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>
Subject: Re: draft-elkins-v6ops-ipv6-pdm-recommended-usage-00
References: <51FA6667.4010200@bogus.com> <1377607721.23313.YahooMailNeo@web2806.biz.mail.ne1.yahoo.com>, <521DCE46.6030501@bogus.com> <2845723087023D4CB5114223779FA9C83BF8C4F1@njfpsrvexg8.research.att.com> <521EB4A2.2060006@bogus.com> <1377780455.80051.YahooMailNeo@web2805.biz.mail.ne1.yahoo.com> <521F896A.9090305@bogus.com> <1377826574.11519.YahooMailNeo@web2806.biz.mail.ne1.yahoo.com>
In-Reply-To: <1377826574.11519.YahooMailNeo@web2806.biz.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 30 Aug 2013 18:46:02 +0000 (UTC)
Cc: "joachim.fabini@tuwien.ac.at" <joachim.fabini@tuwien.ac.at>, "trammell@tik.ee.ethz.ch" <trammell@tik.ee.ethz.ch>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 18:46:11 -0000

On 8/29/13 6:36 PM, Nalini Elkins wrote:
>
>
> On 8/29/13 5:47 AM, Nalini Elkins wrote:
> > Please take a look at:
> >
> >
> http://www.ripe.net/data-tools/stats/ttm/test-traffic-measurement-service
> >
> >
> > Note that what they provide is:
> >
> >    * NTP-server, the test-boxes can act a stratum 1 server for the
> machines on your network, providing time-stamps with an accuracy of 10
> microseconds.
> >With respect to the IETF 87 presentation/discussion I think is is a
> >dicussion of the quality of time and it relationship to the general
> >utility of of pdm optional header, not the availability of specific
> >point solutions.
>
> Let me back up and see if I can restate your basic concern in simple
> words so that I am sure that I understand you.
>
> I believe that you are concerned that the timestamps provided by NTP
> will not be accurate enough if the timestamps are taken from more than
> one administrative domain.
The clock in the computer is providing the timestamp, ntp is
syncronizing the clock in the computer to another clock.
>   Our PDM proposal depends on fairly reliable timestamps.
It depends on the accuracy of clocks generating the timestamps with
respect to each other.
>  So, if the timestamps are not reliable, then the PDM is not very useful.
If a diagnostic result is dependant on low number of ms or usec level
timestamp level accuracy and you don't have that, then yes. A related
question is how do you know when you do or don't? if you have long
timeseries data for two devices you may have evidence of the magnitude
of the eror. If packets arrive from the future with respect to your
clock that's a nice and gross indicator. Looking at a packet trace in
the past, the information availble to reconstruct the state of the
clocks is only the timestamps, baring external sources of that information.
>
> Please let me know if I have understood you.
>
> Thanks,
> Nalini
>
>
>


From nalini.elkins@insidethestack.com  Sat Aug 31 05:19:26 2013
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EC7921E80BA for <tsv-area@ietfa.amsl.com>; Sat, 31 Aug 2013 05:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wg0aFCkylbdP for <tsv-area@ietfa.amsl.com>; Sat, 31 Aug 2013 05:19:21 -0700 (PDT)
Received: from nm1-vm5.access.bullet.mail.gq1.yahoo.com (nm1-vm5.access.bullet.mail.gq1.yahoo.com [216.39.63.119]) by ietfa.amsl.com (Postfix) with ESMTP id 0D2D611E80EF for <tsv-area@ietf.org>; Sat, 31 Aug 2013 05:19:20 -0700 (PDT)
Received: from [216.39.60.169] by nm1.access.bullet.mail.gq1.yahoo.com with NNFMP; 31 Aug 2013 12:19:19 -0000
Received: from [216.39.60.237] by tm5.access.bullet.mail.gq1.yahoo.com with NNFMP; 31 Aug 2013 12:19:19 -0000
Received: from [127.0.0.1] by omp1008.access.mail.gq1.yahoo.com with NNFMP; 31 Aug 2013 12:19:19 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 719206.76486.bm@omp1008.access.mail.gq1.yahoo.com
Received: (qmail 97732 invoked by uid 60001); 31 Aug 2013 12:19:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1377951559; bh=nHULu/9UYfjop2xdfTTfqGg9XQSGwXQjxLa9eRoFsDo=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=E8c9ox6lT83coAfw0nqvytRyNuqSb1TjqkeYTjBfYDpl+S4J8ReeOqs7gSbaaN1h0q3KbcPOkJo56MhYPFTWOw9NaG48To+NBh/TCeq0ocRUh7ozyJFc3Sz+i4FfSx7x13N7zzVKtEGQbNpej4iXJ2eW4Cg/0DTpLtkDdcKbdgk=
X-YMail-OSG: rWruHOkVM1kJlRSNm7FdGZQ4e2mtucnfa0.NySQtS_ucoJ9 dyIEEeT9dE9GHX6kyeWIALhfXF1upTkeAUi7FT1CyB.UJQqJ9Tl2uilSWmdv BuKk93pVd_Q7c07y9X_ENoNg_X0FgGnPxpO4f6i6s.Py9nwiZAa_uJe.Fv8N dCYvo3mOtFe3UUzGSJkHBxwzCCVOp3v7Sy__d.BEbKIH3r7CrM_20Nl697.k KDMpeLQzJtWsYyT2IPGsoCdVyGslsC2wHfFJS_w3fjuXTSB09pr8A0sVI2Jz MjKzg.gyVqhXjxi5c3LxTqTwVv_wJpQLrTMtrqTvfencByYxyUISlN3WoQJd nC6pb.LjmBpUQLLj8OtnR4otNLlw5qjZrmmnHW5WCkvlkmHzTid7G1w2Oqfv u7qQcQAh8D4fQMewMgxi8xLDKCQtu3dtSvgBsYQyIELe2eGCLlZEulZE1WtD x9rltWSeAjSFvVTWRNdLmNSA4tdzgs2UgqAXGSB203m6GKOnc.wS1EQE7vM_ gYZgmQ82t0dYO.mNf9_gN1yngtkQ85fG7T13qKOG7PAsinVIZjJkmUKLqUwl 6OKH.fbSB3PlzEa_1Tb0Xuj18jnVO4I8yNvDJ3oFLdQdhh_kykda3wqRlCar TSsWor98KPIDWgGOqp4Go1vIoHDcvi2UBN5SfZLPjktYlV8mFIRRkZYGEzht Qh2Hb_uFBpzzX6K3HWmRohQNtv_AWBPhrnSbKTxO_qaUlq_H1UzcWmTWl9Ta tPCgeSRX15rdrk4dTTCvFm92XyISegZltSQN_YQK0f_it
Received: from [70.198.65.78] by web2806.biz.mail.ne1.yahoo.com via HTTP; Sat, 31 Aug 2013 05:19:18 PDT
X-Rocket-MIMEInfo: 002.001, RnJvbTogam9lbCBqYWVnZ2xpIDxqb2VsamFAYm9ndXMuY29tPgpUbzogTmFsaW5pIEVsa2lucyA8bmFsaW5pLmVsa2luc0BpbnNpZGV0aGVzdGFjay5jb20.OyAiTU9SVE9OIEpSLiwgQUxGUkVEIEMgKEFMKSIgPGFjbW9ydG9uQGF0dC5jb20.OyBJUHY2IE9wcyBXRyA8djZvcHNAaWV0Zi5vcmc.OyAidHN2LWFyZWFAaWV0Zi5vcmciIDx0c3YtYXJlYUBpZXRmLm9yZz4gCkNjOiAiam9hY2hpbS5mYWJpbmlAdHV3aWVuLmFjLmF0IiA8am9hY2hpbS5mYWJpbmlAdHV3aWVuLmFjLmF0PjsgInRyYW1tZWxsQHRpay4BMAEBAQE-
X-Mailer: YahooMailWebService/0.8.156.576
References: <51FA6667.4010200@bogus.com> <1377607721.23313.YahooMailNeo@web2806.biz.mail.ne1.yahoo.com>, <521DCE46.6030501@bogus.com> <2845723087023D4CB5114223779FA9C83BF8C4F1@njfpsrvexg8.research.att.com> <521EB4A2.2060006@bogus.com> <1377780455.80051.YahooMailNeo@web2805.biz.mail.ne1.yahoo.com> <521F896A.9090305@bogus.com> <1377826574.11519.YahooMailNeo@web2806.biz.mail.ne1.yahoo.com> <5220E863.1020700@bogus.com>
Message-ID: <1377951558.94995.YahooMailNeo@web2806.biz.mail.ne1.yahoo.com>
Date: Sat, 31 Aug 2013 05:19:18 -0700 (PDT)
From: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Re: draft-elkins-v6ops-ipv6-pdm-recommended-usage-00
To: joel jaeggli <joelja@bogus.com>, "MORTON JR., ALFRED C \(AL\)" <acmorton@att.com>, IPv6 Ops WG <v6ops@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>
In-Reply-To: <5220E863.1020700@bogus.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "joachim.fabini@tuwien.ac.at" <joachim.fabini@tuwien.ac.at>, "trammell@tik.ee.ethz.ch" <trammell@tik.ee.ethz.ch>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.com>
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 12:19:26 -0000

From: joel jaeggli <joelja@bogus.com>=0ATo: Nalini Elkins <nalini.elkins@in=
sidethestack.com>; "MORTON JR., ALFRED C (AL)" <acmorton@att.com>; IPv6 Ops=
 WG <v6ops@ietf.org>; "tsv-area@ietf.org" <tsv-area@ietf.org> =0ACc: "joach=
im.fabini@tuwien.ac.at" <joachim.fabini@tuwien.ac.at>; "trammell@tik.ee.eth=
z.ch" <trammell@tik.ee.ethz.ch> =0ASent: Friday, August 30, 2013 11:45 AM=
=0ASubject: Re: draft-elkins-v6ops-ipv6-pdm-recommended-usage-00=0A=0A=0AOn=
 8/29/13 6:36 PM, Nalini Elkins wrote:=0A>=0A>=0A> On 8/29/13 5:47 AM, Nali=
ni Elkins wrote:=0A> > Please take a look at:=0A> >=0A> >=0A> http://www.ri=
pe.net/data-tools/stats/ttm/test-traffic-measurement-service=0A> >=0A> >=0A=
> > Note that what they provide is:=0A> >=0A> >=A0 =A0 * NTP-server, the te=
st-boxes can act a stratum 1 server for the=0A> machines on your network, p=
roviding time-stamps with an accuracy of 10=0A> microseconds.=0A> >With res=
pect to the IETF 87 presentation/discussion I think is is a=0A> >dicussion =
of the quality of time and it relationship to the general=0A> >utility of o=
f pdm optional header, not the availability of specific=0A> >point solution=
s.=0A>=0A> Let me back up and see if I can restate your basic concern in si=
mple=0A> words so that I am sure that I understand you.=0A>=0A> I believe t=
hat you are concerned that the timestamps provided by NTP=0A> will not be a=
ccurate enough if the timestamps are taken from more than=0A> one administr=
ative domain.=0AThe clock in the computer is providing the timestamp, ntp i=
s=0Asyncronizing the clock in the computer to another clock.=0A>=A0=A0=A0Ou=
r PDM proposal depends on fairly reliable timestamps.=0AIt depends on the a=
ccuracy of clocks generating the timestamps with=0Arespect to each other.=
=0A>=A0 So, if the timestamps are not reliable, then the PDM is not very us=
eful.=0A=0A>If a diagnostic result is dependant on low number of ms or usec=
 level=0A>timestamp level accuracy and you don't have that, then yes. A rel=
ated=0A>question is how do you know when you do or don't? if you have long=
=0A>timeseries data for two devices you may have evidence of the magnitude=
=0A>of the eror. If packets arrive from the future with respect to your=0A>=
clock that's a nice and gross indicator. Looking at a packet trace in=0A>th=
e past, the information availble to reconstruct the state of the=0A>clocks =
is only the timestamps, baring external sources of that information.=0A=0AT=
he basic issue here goes far beyond our PDM header. =A0 Accurate time synch=
ronization is necessary for much data processing today. =A0 Let me quote fr=
om an IBM Redbook:=0A=0A"In the information technology world, time synchron=
ization has become a critical component for managing the correct order of t=
he events in distributed applications (transaction processing, message logg=
ing), especially for audit and legal purposes."=A0http://www.redbooks.ibm.c=
om/redbooks/pdfs/sg247280.pdf=A0(section 1.1)=0A=0AIf you are arguing that =
time synchronization cannot be done to the millisecond or microsecond level=
, then a great deal of data processing would flat out not work. =A0 Let me =
point you to something called 'parallel sysplex' which is a way of putting =
together very large computer systems=A0http://www-03.ibm.com/systems/z/adva=
ntages/pso/bsvsps.html=A0 These kind of extremely expensive systems are in =
most large data centers today. =A0They require synchronization to the micro=
second level. =A0They do it using NTP.=0A=0AOne of the members of my team h=
as implemented NTP with a consortium of 120 separate organizations (all DIF=
FERENT administrative domains) and they have synched up to 20 - 50 millisec=
onds. =A0If anyone would like, they can contact us offline and we can share=
 the implementation documentation. =A0If you would like, I can get from the=
m the sources for timing that they use. =A0 Multiple MASTER Clocks geograph=
ically dispersed for either accuracy and/or backup-contingency purposes may=
 be needed. =A0 By the way, this was done several years ago.=0A=0AAs far as=
 our PDM header is concerned, what we are looking for MOST is to do triage.=
 =A0 That is to say which of the three: inbound network time, server proces=
sing time, and outbound network time is consistently quite large. =A0 What =
happens in real life is that problems happen with response time to a major =
region or bank branch, and we need to quickly (hopefully VERY quickly) get =
the right team to work solving the problem. =A0 So, what is required is tha=
t the differences in those times be consistently greater than any problems =
with time synchronization. =A0 To give an example:=0A=0AAssume: time synchr=
onization varies at 50 milliseconds.=0A=0AInbound network time =3D 100 mill=
iseconds=0AServer time =3D 500 milliseconds=0AOutbound network time =3D 200=
 milliseconds=0A=0AThe point of this game is to say which is the failing co=
mponent. =A0If you add or subtract 50 milliseconds from the above numbers, =
it won't matter. =A0It will still be the server time.=0A=0AIf you think tha=
t we will have problems if all times are close together, (ex. all times =3D=
 40 milliseconds), then yes. =A0And, it doesn't matter. =A0What we are look=
ing for in doing diagnostics and triage are, basically, the outliers (or th=
ose at the 95% to be a bit more precise). I am looking for which response t=
imes are among the worst. =A0That is where the problems are likely to be. =
=A0 In those transactions, in my experience, I have NEVER found transaction=
s where all numbers are close together. =A0=A0=0A=0A=0ADefinitely for trend=
ing and capacity planning purposes, we want to look at all response times. =
=A0But, I believe that time synchronization to the level that is required c=
an be achieved today. =A0 I have cited numerous examples of organizations d=
oing so.=0A=0A=0AIf our PDM proposal is accepted, it will still be 5-6 year=
s before it is in use because operating systems need to be changed to use i=
t. =A0 I expect that time synchronization will become even better over time=
. =A0 Notice how much more prevalent GPS is from even a few years ago.
