Re: [AVTCORE] Question

worley@ariadne.com (Dale R. Worley) Tue, 06 January 2015 19:22 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 9C41E1A1B59 for <avt@ietfa.amsl.com>; Tue, 6 Jan 2015 11:22:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 HW-KGV_s99k6 for <avt@ietfa.amsl.com>; Tue, 6 Jan 2015 11:22:20 -0800 (PST)
Received: from resqmta-po-02v.sys.comcast.net (resqmta-po-02v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:161]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3A761A1B57 for <avt@ietf.org>; Tue, 6 Jan 2015 11:22:20 -0800 (PST)
Received: from resomta-po-05v.sys.comcast.net ([96.114.154.229]) by resqmta-po-02v.sys.comcast.net with comcast id cjMp1p0064xDoy801jNK4U; Tue, 06 Jan 2015 19:22:19 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-po-05v.sys.comcast.net with comcast id cjNJ1p00T1KKtkw01jNKHM; Tue, 06 Jan 2015 19:22:19 +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 t06JMI7d013700; Tue, 6 Jan 2015 14:22:18 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id t06JMH0w013696; Tue, 6 Jan 2015 14:22:17 -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: <CACFvNHUGDyJDKA0vpPQeKN1H4TCU_8VzuP2Y-V22Jx4XuYJW9w@mail.gmail.com> (juliusfriedman@gmail.com)
Sender: worley@ariadne.com
Date: Tue, 06 Jan 2015 14:22:17 -0500
Message-ID: <87y4pfd89i.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1420572139; bh=+Znmde4+pj9VxNZ00MaMISzCRE/2EVrXpzp9OJRphHg=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=tP34gqkfNLCvXlbkPmxrzMRnszocO754tY1/KhX9SQ8NvcE7EQ/o+nWNEdAVdGMZv bgxMREToi9BAMN6+SNb26gK566z1yJPoy47UPUBTHr5WkdJ7OUMT+BZyGI/RMAeXZi bYidGfqkXZfSbe9QTrl3aIIkhw0xCP9aBLzkH43GGSwm7sqIbD3X17QDZ+3yziwsGr 01nYIaF8C/G1rB+BcdlsObzV3KA5bTjf+DIRDbYuAJ/s7C3ngJwPOqsAzz/i8uamDh urbPV9kRBSaUQ8U1yRdcovIly4bQt3dfF6faEVEFhyOeqDVCvvROK77qEVo2lDmc/m /WW+KuYRWWzQQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/o7624b6a593UXaH8Jx50ONaYCZw
Cc: avt@ietf.org, mmusic@ietf.org
Subject: Re: [AVTCORE] Question
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: Tue, 06 Jan 2015 19:22:23 -0000

I'll note that I've received this message directly

Julius Friedman <juliusfriedman@gmail.com> writes:
> As for my other 'issues' / errata for RFC2435 has anything been determined
> on them?

Not yet, clearly.  What are you going to do to get them discussed?

> I will include their questions here again and I would appreciate a single
> complete and through reply.

That is the least effective way to get your issues handled.

First, you are *demanding* something, and that always makes people less
interested in helping you.

Second, you want a "single complete and through reply", which means that
if someone doesn't feel like doing all the work to do that, they won't
bother to do any of the work.  That is, it minimizes the chance that
you'll get any response at all.

A better approach would be to select one problem, the one you think
other people are most likely to recognize as a problem, and ask about
it.  Also, add whatever discussion you can provide, to indicate that
you've done as much work on the problem as you can before asking others.

It seems to me this one would be a good one to start with:

> What about my questions regarding the 'source' and 'ssrc' parameters? Those
> aren't proposals, those are genuine questions.

Note that while RFC 2326 talks about a 'source' parameter, it doesn't
provide any BNF for it.  Suggest that it probably has the same BNF as
the 'destination' parameter.  Show that BNF.  Show all the examples of
source parameters that you know of (mention what devices generate them),
compare them to your suggested BNF.  Add your discussion of security
questions.

Once you've solicited as much feedback as you can get, organize all that
information into a well-written errata for the RFC.

Then go on to the next issue.

> As for my other 'issues' / errata for RFC2435 has anything been determined
> on them?

http://www.rfc-editor.org/errata_search.php?rfc=2435&rec_status=15&presentation=table

All of your errata on RFC 2435 have status "reported", so it appears the
answer is "no".

Dale