Re: [avtext] AD Eval of draft-ietf-avtext-rtp-grouping-taxonomy-06

"Ben Campbell" <ben@nostrum.com> Tue, 05 May 2015 11:04 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: avtext@ietfa.amsl.com
Delivered-To: avtext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ECBE1A88E6; Tue, 5 May 2015 04:04:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.39
X-Spam-Level:
X-Spam-Status: No, score=0.39 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_LIST=2.3, T_RP_MATCHES_RCVD=-0.01] 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 etRnj6WrzNah; Tue, 5 May 2015 04:04:25 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFE961A88ED; Tue, 5 May 2015 03:59:22 -0700 (PDT)
Received: from [10.10.1.5] (mpdedicated.com [50.97.142.159] (may be forged)) (authenticated bits=0) by nostrum.com (8.15.1/8.14.9) with ESMTPSA id t45AxHoH050016 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 May 2015 05:59:19 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host mpdedicated.com [50.97.142.159] (may be forged) claimed to be [10.10.1.5]
From: Ben Campbell <ben@nostrum.com>
To: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
Date: Tue, 05 May 2015 11:59:18 +0100
Message-ID: <621CBE29-88FF-4D06-80A0-695F688A07BF@nostrum.com>
In-Reply-To: <7098F21E-7DA7-45B8-B953-048ABE0A86A9@cisco.com>
References: <B6FA86CA-EC73-4ED3-84FE-B5CB431DAC58@nostrum.com> <0E3DA6F1-7E6D-4AFE-8CEC-8B86B91ED32A@cisco.com> <7098F21E-7DA7-45B8-B953-048ABE0A86A9@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.1r5084)
Archived-At: <http://mailarchive.ietf.org/arch/msg/avtext/oL-iuemQ5VWbtK4VYA48UB9ZlCE>
Cc: "avtext@ietf.org" <avtext@ietf.org>, "draft-ietf-avtext-rtp-grouping-taxonomy.all@ietf.org" <draft-ietf-avtext-rtp-grouping-taxonomy.all@ietf.org>
Subject: Re: [avtext] AD Eval of draft-ietf-avtext-rtp-grouping-taxonomy-06
X-BeenThere: avtext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Extensions working group discussion list <avtext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avtext>, <mailto:avtext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avtext/>
List-Post: <mailto:avtext@ietf.org>
List-Help: <mailto:avtext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 May 2015 11:04:26 -0000

Hi Gonzalo,

I saw Keith's mail first, and replied to it. Please let me know if that 
failed to cover anything from your email.

Thanks!

Ben.
On 5 May 2015, at 5:39, Gonzalo Salgueiro (gsalguei) wrote:

> Sorry, writing this on phone and hit send prematurely.
>
>
> Thanks, Ben.  I'll let Bo, as editor, comment on the editorials/nits 
> but I'll offer my perspective on the two major issues you raise.
>
> Responses inline...
>
> On May 3, 2015, at 11:55 PM, Ben Campbell 
> <ben@nostrum.com<mailto:ben@nostrum.com>> wrote:
>
> Hi,
>
> Here's my AD Evaluation of draft-ietf-avtext-rtp-grouping-taxonomy-06. 
> Nothing here is sufficient to delay the IETF last call, but I'd like 
> to at least see a response to the subtsantive comments.
>
> Thanks!
>
> Ben.
>
> ----------------
>
> Substantive Comments:
>
> -- I do not object to this being informational per se, but I wonder if 
> people expect it to be normatively references by future standards 
> track documents. Remember that a reference should be normative if it 
> is needed to understand the dependent document. Terminology references 
> often fall squarely into that category. If the answer is yes, has 
> there been any considerations that this draft may need to be standards 
> track?
>
> There seems to be some subjectivity here based on some related 
> discussions in the past with Pete Resnick on similar type documents. 
> This can, does and will have documents referencing it normatively.  In 
> fact, there is a document with the RFC Editor now that is being held 
> up because of a normative reference to this document (as you are 
> likely familiar: 
> https://datatracker.ietf.org/doc/draft-ietf-dart-dscp-rtp/).  From 
> that perspective I think this is Standards Track, but again, thi seems 
> a matter of opinion and I'm fine either way.
>
> -- Along the same lines, all the references informational. Could a 
> reader be expected to understand this draft without reading _any_ of 
> the references? I recognize this may not be important for an 
> informational draft that is not a technical specification. But it may 
> be more important if standards track docs normatively reference this 
> doc.
>
> Again, I agree that there are Normative references, though I think for 
> the purpose of a taxonomy document they can be used sparingly and 
> there is I need to delay publication with a normative reference to an 
> I-D.
>
> Cheers,
>
> Gonzalo
>
>
> Nits and Editorial Comments:
>
> -- Abstract: "... attempts to define..."
>
> Is there a concern that it may not have succeeded?  :-)
>
> -- Section 1, 1st sentence:
>
> Do you think RTP terminology will continue to be confusing and 
> inconsistent after this draft is published? Also, please expand RTP in 
> the first use in the body. (In addition to the abstract.)
>
> -- 2.1.2:
>
> Do you consider the meaning of the term "Media" to be clear enough 
> that it doesn't need a definition here?
>
> I find it hard to parse the following sentence:
>
> "This data is due to its periodical sampling, or at least being timed 
> asynchronous events, some form of a stream of media data. "
>
> -- 2.1.2, 2nd bullet list entry:
>
> s/support/supports
>
> -- 2.1.4, first sentence
>
> I find the sentence hard to parse:
>
> -- 2.1.5
>
> Was the "raw stream" not also time-progressing?
>
> -- 2.1.9, first bullet list entry:
>
> I can't parse the sentence. Is there a missing word towards the end?
>
> -- 2.1.18 "... alarm subsequent transformations ... "
>
> Do you mean "alert"?
>
> -- 2.2.3, first bullet list entry:
>
> is the SIP URI example assumed to be an Address of Record? If so, it 
> might be worth mentioning that, since a SIP URI could also point to a 
> device, and a participant might have more than one.
>
> -- 3.7, last paragraph, 2nd sentence:
>
> Sentence is convoluted and hard to read. Please consider splitting it 
> into multiple simpler sentences.
>
> -- 3.8, first paragraph, 2nd sentence:
>
> Convoluted sentence.
>
> -- 3.9, last paragraph:
>
> Convoluted sentence.
>
> -- 3.10, last paragaph, last sentence:
>
> Convoluted sentence.
>
> -- 3.11, last paragraph : "This requires to either use..."
>
> Missing noun?  ("This requires XXX to use either", or "This requires 
> the use of either...")
>
> 3.13, first paragraph, last sentence:
>
> I can’t parse the sentence—is there a word missing? (i.e. “… 
> and smaller number of flow based…”)?
>
>
> _______________________________________________
> avtext mailing list
> avtext@ietf.org<mailto:avtext@ietf.org>
> https://www.ietf.org/mailman/listinfo/avtext