Re: [AVTCORE] Errata 4192 RFC 3550

worley@ariadne.com (Dale R. Worley) Thu, 11 December 2014 16:54 UTC

Return-Path: <worley@alum.mit.edu>
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 F0ADA1A702A for <avt@ietfa.amsl.com>; Thu, 11 Dec 2014 08:54:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.065
X-Spam-Level: **
X-Spam-Status: No, score=2.065 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_52=0.6, SPF_SOFTFAIL=0.665] autolearn=no
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 evaqheLU3oaN for <avt@ietfa.amsl.com>; Thu, 11 Dec 2014 08:54:55 -0800 (PST)
Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAFC81A8034 for <avt@ietf.org>; Thu, 11 Dec 2014 08:54:55 -0800 (PST)
Received: from resomta-ch2-06v.sys.comcast.net ([69.252.207.102]) by resqmta-ch2-03v.sys.comcast.net with comcast id SGuu1p0042D5gil01Guujs; Thu, 11 Dec 2014 16:54:54 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-ch2-06v.sys.comcast.net with comcast id SGuu1p0011KKtkw01GuuT4; Thu, 11 Dec 2014 16:54:54 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id sBBGsr4d028627; Thu, 11 Dec 2014 11:54:53 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id sBBGsrDj028626; Thu, 11 Dec 2014 11:54:53 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Julius Friedman <juliusfriedman@gmail.com>
In-Reply-To: <CACFvNHXjy+PxHaZsrjdO5SHg6PSaQVt_J8WPH6hQTKQKkdoo5A@mail.gmail.com> (juliusfriedman@gmail.com)
Sender: worley@ariadne.com
Date: Thu, 11 Dec 2014 11:54:53 -0500
Message-ID: <877fxy6s9u.fsf@hobgoblin.ariadne.com>
MIME-Version: 1.0
Content-Type: text/plain
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1418316894; bh=PwU+0f9e/S62VY5Ftz/BujQ6K1hCv8ufwRvIbDwHnQg=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:MIME-Version:Content-Type; b=WK+ryCwiiAlR8REprHyDoou3jHMY3tbLp4J+YuuX2PvleX5/+BnsNyaJ89IfalLXh RnW+INkFfOKiVAXuUxhC+cIOr2A/dw/h7hSTcdGzSuxWDsVxNW9fmS8ehbB6826bc8 zEGcmfldxqWbFMfhvDPdJvgrQArFwbVyMcNqRCymenRzeJgvQs/4rE8CCGlPnNTtJz hB7GzCGKIs7VnhNTZADu5LyE5VrttjF4qCWak7XokfSBXMOCtLZc3cDFvKg7JqMpLS Eat+71wb0n9bPw+bGWDmqSN1UJBp2YoYIKK1ATHKnL+dXYLHhsZPuxHw6FKLlozhxD 8AWC1vT8np7AQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/-HtFTrVGIucb_5qkyTNxttKTTmk
Cc: avt@ietf.org
Subject: Re: [AVTCORE] Errata 4192 RFC 3550
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: Thu, 11 Dec 2014 16:54:57 -0000

Julius Friedman <juliusfriedman@gmail.com> writes:
> However,  before beginning I would like there to be an acknowledgement of
> the given errata so it can be justified that time be spent working on the
> draft.

You've already been told that the erratum will be rejected, since the
RFC does, in fact, correctly describe what the working group intended
for it to describe.

You believe that the information the protocol carries is not the
information that it *should* carry.  That is a complex technical
judgement that can only be made by the working group as a whole.  The
way to get the working group to consider the question is to write an
Internet-Draft and then raise the question on the appropriate working
group mailing list.

> Even if its held for update, (which it seems there are already at least one
> without my additions) it would allow me to address these issues and outline
> both the relationship and determine if a new version be specified in the
> draft or if just the same version be specified but with changes given or to
> make the draft correct for the initial standard (which would involve
> keeping track of the entities in question to properly calculate the given
> terms)of which options is the very least desirable to me.
>
> If a new version is specified I even will go as far to acknowledge all the
> back to rtp 1 to ensure that all variations are specified partly because I
> have identified version 0 as potentially another version (4) or explicitly
> marking it as reserved for compatibility with VAT.
>
> I will also address that uncompressed video be supported abd pcm be
> supported at a minimum.
>
> I also have changes which can remove dependence on media clock rate which
> will simplify overall general calculations for jitter and the like, since
> again they would be know or determinate and also incorrect which shouldn't
> make calculations invalid.
>
> Hopefully you and everyone else sees that I have a lot of considerations /
> ideas and that I don't want to flood the working group with such problems
> if they can be avoided however with web rtc becoming mainstream I believe
> we need to address these issues today rather than tomorrow and I will do
> whatever work is necessary to ensure the standards are correct and
> encompass the best possible principles of engineering possible but I need
> to know that the work is both utilized and understood otherwise it will be
> for nothing.
>
> Hopefully it's not too much to ask and thanks again and I appreciate your
> time and effort in this matter as well as that of the committees.

All of these matters can only be handled by the working group as a
whole.  They are excellent items to address in an Internet-Draft.

Dale