IETF Logo Mail Archive

Re: [AVTCORE] Mail regarding draft-ietf-avtcore-clksrc

Julius Friedman <juliusfriedman@gmail.com> Wed, 17 December 2014 14:20 UTC

Return-Path: <juliusfriedman@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43D5B1A884B for <avt@ietfa.amsl.com>; Wed, 17 Dec 2014 06:20:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 anpSM2ec7mi9 for <avt@ietfa.amsl.com>; Wed, 17 Dec 2014 06:20:36 -0800 (PST)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B1691A1B57 for <avt@ietf.org>; Wed, 17 Dec 2014 06:20:36 -0800 (PST)
Received: by mail-pa0-f51.google.com with SMTP id ey11so16384883pad.24 for <avt@ietf.org>; Wed, 17 Dec 2014 06:20:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=+svu0KlQrxS5vJrbezevHP88HZnRirRbksEs/rs4/TI=; b=Z3ZKQRzcLIAYeVzbPGYx2qS3eKgK4EIt3eYvWpL9GRDrMpb8Emm8yieykP6pNPzb4t ytuMOEBnbgNd6iASxiRBNHDpnjr07Vr3whxGPmsj1uXrggZGBZ/+EYJdiGz0js9HUZb1 Lg63KaRQG/hSaGhHdvMAmOkmbA08l8LW6b2sHnTjcHADZJXy7EUVhP+e3NzHj38bjI0B KVu050DHCfDslW37m3CyYbVZQ0xccauR3mnLksol5n8GXZetOEUbSLxpLSXpV5ytxNan oBMF8KN0S+jphl19/tWuPumPWqT8/dNaU8unMmDzziVegLU7R8eRsMrXa0r2vv5Xa0EB Xzvw==
MIME-Version: 1.0
X-Received: by 10.70.41.134 with SMTP id f6mr36075642pdl.25.1418826035772; Wed, 17 Dec 2014 06:20:35 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Wed, 17 Dec 2014 06:20:35 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Wed, 17 Dec 2014 06:20:35 -0800 (PST)
In-Reply-To: <CANO7kWCk_OHFa9y7OOGagPBS_fcTg2TM0C7J1haqEOVL9YE2nQ@mail.gmail.com>
References: <CACFvNHXLk2+2h2wYtTOR-uJm=AB7coBO8O9EQkT44yeZsA5UQA@mail.gmail.com> <CACFvNHWu8Yqs4fccjn4nBiypqXxvDdiDDmR7B=va-Fjnpmff8g@mail.gmail.com> <B1289322-A9FE-4EB1-BAFE-B53B8B57E2CB@tno.nl> <CACFvNHW-unBgBF=nsNW7EPd+-5-4=_y_00eBCg-6_TVLJooODA@mail.gmail.com> <CALw1_Q2QF71goA_W9AVmSrHEMA4yuPSW2vZhYSmu1uQ5p21pWw@mail.gmail.com> <CACFvNHVdBS_sAMjB=N2Ok1R-K9XV4oyri2Q+U-t0AhxyENu-Gg@mail.gmail.com> <FCC100FC8D6B034CB88CD8173B2DA1582031BBFD@EXC-MBX03.tsn.tno.nl> <CACFvNHX9WDgyVL+6crNaXB99ry0+qjSJPnmbn3b6EER2wD9OCw@mail.gmail.com> <FCC100FC8D6B034CB88CD8173B2DA1582031DB12@EXC-MBX03.tsn.tno.nl> <CACFvNHXs+rzoomzfueBKSTWe8noNAjgyVsknq-YnNF9vmqZ00A@mail.gmail.com> <27CF275E-2456-4D18-BB25-75E147411214@tno.nl> <CANO7kWCk_OHFa9y7OOGagPBS_fcTg2TM0C7J1haqEOVL9YE2nQ@mail.gmail.com>
Date: Wed, 17 Dec 2014 09:20:35 -0500
Message-ID: <CACFvNHX+kVGaVBtgGu3fB1BkZ2J=74MhbC+nqD-_UGXeu=qrEA@mail.gmail.com>
From: Julius Friedman <juliusfriedman@gmail.com>
To: Simon Perreault <sperreault@jive.com>, avt@ietf.org
Content-Type: multipart/alternative; boundary="047d7bfeb080dc45b6050a6a2d85"
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/NF-7HgajY-IYr1eiDaEaLPkDvBU
Subject: Re: [AVTCORE] Mail regarding draft-ietf-avtcore-clksrc
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Dec 2014 14:20:38 -0000

Well I didn't know that we could define rfc documents for things which
break others.

I also didn't realize that we published them either without determining
applicability and appropriateness in ALL use cases.

Its not my fault no one used the standard tools available.

Its also not my fault basic changes which allow correct operations  are
turned away but proprietary documents which outline incomplete mechanisms
are indeed accepted.

Get on the ball / with the times already.

If you understood the topics at hand as well as you elude to then I
obviously wouldn't have any issues and wouldn't be urged to clean up a mess
I see which provides no benefits and incomplete information.

Obviously rtp has had this problem from the beginning and rather then just
make a new protocol we all agree on we bastardize standards existing and
convoluted the implementation so much rtp systems are more complex then
mpeg which is transported under rtp.

The points have been made and its not a threat its a promise.

Sincerely,
Julius Richard Friedman
On Dec 17, 2014 9:04 AM, "Simon Perreault" <sperreault@jive.com> wrote:

>
> On Wed, Dec 17, 2014 at 8:51 AM, Brandenburg, R. (Ray) van <
> ray.vanbrandenburg@tno.nl> wrote:
>>
>> until you can articulate a succinctly defined scenario which also handles
>> the issues I cite then I will file errata
>
>
> Until now I never thought that errata could be wielded as a weapon...
>
> "Clear that DISCUSS or I will file errata!" :D
>
> Simon
>

v2.23.0 | Report a Bug | By Email