Re: [clue] WGLC for draft-ietf-clue-rtp-mapping-07 ends 4 June
"Roni Even" <ron.even.tlv@gmail.com> Fri, 10 June 2016 06:28 UTC
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A755312D59E for <clue@ietfa.amsl.com>; Thu, 9 Jun 2016 23:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 0ZEwpaY1TJWh for <clue@ietfa.amsl.com>; Thu, 9 Jun 2016 23:28:41 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E3FF12B056 for <clue@ietf.org>; Thu, 9 Jun 2016 23:28:41 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id k184so970849wme.1 for <clue@ietf.org>; Thu, 09 Jun 2016 23:28:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-transfer-encoding:thread-index:content-language; bh=I0eKGwzCuGkVee5tOoheTqE2KC5NOAYGimNYbKCETUM=; b=FMK4m7pCJevlOh20M0DYvsv3hX1O5Qsug3/qkyEwqJqXDshPgVG3ns40kbA/HyN1M6 yR0kKCcKzZ9A+Vb4YLe3gQramZYcaOE2UVtb1JS4JcQpP+hYck+hhv9Yirp6cnsgIlIM 63qV0tdq59MEyDTrZB1zPCdMg30X9XqumbJWaW0fXTm/cHsZF9uQJ+FHIescIjVIrO/9 5ntTTl/pX2pIvYb/DcuPrfZvWhRJlAvNRbN5kahMPZctURm+34RZbrz5fti7TNPIHHxH E7OkBHdZYuyHNOAJTcqVukGDOtThPgpdbtmbmO+5ifWsUOEyJP53Rd/N2jmewF7rI73F E6/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=I0eKGwzCuGkVee5tOoheTqE2KC5NOAYGimNYbKCETUM=; b=b8IZHbuBv6pFnaCX1mwXpXwUaTKthWpbN3OUh/+lAS3kEhJQXe7RvNa4t2TwDIoYcx 6+Ge7j9s7HdKi2QlYyGO7xyUMkGU4k3lSRyCWdA0z27eYFNGoE3AMkMFjKkmXB2TVImx mVD/kjXiz0EbePIiv+33fVfscHuIaiw8A1RdOOBFdZ+E+y9l284PQPxHiFsz6j55YtIM 6rK1ELSUBXdzQmEmQqEO/TBtKOpTcelcfuIuiTCWVrdTEEr9GzMt6BApK6b0/m8wq8fP MlUFyOMPG1t6tbamgw0NgVBKqDKNi1ZVE48U/Z4Yd4tNMUlAvjOOzhcDMMRFJ1Dhg0iH eCAw==
X-Gm-Message-State: ALyK8tKgm4dg9Jwi4F7ENXPzfvIyKt18WSbzOnFEBKEIogW8Kq7IEhJF3jt8BOEmhdoO+Q==
X-Received: by 10.28.227.11 with SMTP id a11mr987614wmh.100.1465540120005; Thu, 09 Jun 2016 23:28:40 -0700 (PDT)
Received: from RoniPC (bzq-79-179-194-235.red.bezeqint.net. [79.179.194.235]) by smtp.gmail.com with ESMTPSA id dd7sm10654800wjb.22.2016.06.09.23.28.37 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 09 Jun 2016 23:28:38 -0700 (PDT)
From: Roni Even <ron.even.tlv@gmail.com>
To: 'Paul Kyzivat' <pkyzivat@alum.mit.edu>, clue@ietf.org
References: <CA+EnjbKG8yhf-mifS4E6YCSWzoRfpJ-jZ_RNAmOJoq-XBDNSVg@mail.gmail.com> <60d98730-8908-ec10-d200-c609ce11dd29@alum.mit.edu>
In-Reply-To: <60d98730-8908-ec10-d200-c609ce11dd29@alum.mit.edu>
Date: Fri, 10 Jun 2016 09:27:18 +0300
Message-ID: <0bb201d1c2e1$24cfbfc0$6e6f3f40$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKGQfWVXbgnidECxz21Z79/VZWM4QLnAR89nmIDSJA=
Content-Language: he
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/d26k8xVMu2R9dZAer19D5kmXEpw>
Subject: Re: [clue] WGLC for draft-ietf-clue-rtp-mapping-07 ends 4 June
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2016 06:28:44 -0000
Hi Paul, Thanks, see inline Roni > -----Original Message----- > From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Paul Kyzivat > Sent: Friday, June 03, 2016 7:40 PM > To: clue@ietf.org > Subject: Re: [clue] WGLC for draft-ietf-clue-rtp-mapping-07 ends 4 June > > On 5/21/16 4:20 PM, Daniel Burnett wrote: > > This message announces the start of a 2 week WGLC for > > draft-ietf-clue-rtp-mapping to review the updated draft. The last call > > will end at midnight on Saturday, 4 June 2016. > > > > PLEASE REVIEW NOW. > > Its been a long time since I read this document all the way through, so I just > did so. > > Note that I am far from an RTP expert, so my qualifications for reviewing this > document are limited. The following covers mostly stuff that doesn't require > too much understanding of RTP. > > All of the following seem to be to be "quick fix" things. Aside from these I > think the document is ready to go. > > * Section 4: > > The 2nd to last paragraph begins with "isAlternately". Clearly the "is" > needs to be removed. [Roni Even] OK > > * Section 4.1: > > The sentence "[I-D.ietf-mmusic-sdp-bundle-negotiation] how to associate a > received RTP stream with the m-line describing it." doesn't parse. It is missing > a word. I think "specifies" should be inserted prior to "how to associate". > [Roni Even] OK > Then, in "The assumption in the work is that...", it isn't clear what "the work" > refers to. Is it CLUE, or BUNDLE? I think it means CLUE. So perhaps change > to "The assumption in CLUE is that...". [Roni Even] The work is bundle in this case, changed it. > > I'll also note that "[I-D.ietf-mmusic-sdp-bundle-negotiation]" is rather > unwieldy to read. It would be helpful to change the references to something > more concise, such as [BUNDLE]. (xml2rfc supports this.) [Roni Even] This will change to the RFC number. > > The following one-sentence paragraph: > > SDP Source attribute [RFC5576] mechanisms to describe specific > attributes of RTP sources based on their SSRC. > > isn't a complete sentence. I don't have a particular fix to suggest. [Roni Even] Added provide mechanisms > > Then the sentence: > > The recommended support of the simulcast case is to use > [I-D.ietf-mmusic-sdp-simulcast] > > needs a period at the end. [Roni Even] OK > > * Section 4.2: > > The intro to this section: > > This section lists, more briefly, the requirements a media > architecture for Clue telepresence needs to achieve, summarizing the > discussion of previous sections. > > doesn't seem appropriate now that the work done. Also, I don't think it really > summarizes discussion in prior sections. Perhaps something like the following > would be better: > > "This section lists the CLUE media requirements that guided the development > of this RTP mapping document." [Roni Even] OK > > * Section 4.5: > > The recommendation is that CLUE endpoints using SSRC multiplexing > MUST support [I-D.ietf-mmusic-sdp-bundle-negotiation] and use the SDP > mid attribute for mapping. > > I read this as being a bit stronger than I think is intended. I think the intent is > that all CLUE endpoints support BUNDLE (for interoperability), but that they > need not offer it. And they only need to use mid when they are using > BUNDLE. If they are not using BUNDLE then use of mid is optional. [Roni Even] I am not sure, what it says is that if when using SSRC multiplexing it must be done using bundle > > * Section 5: > > The statement "The solutions described in this document are believed to > meet these requirements" seems a bit weak in a completed document. Any > doubts as to whether the requirements have been met should have been > raised and resolved now. So can we omit this? [Roni Even] I remove "are believed to" > > Should all the requirements be listed in this section, with an explanation of > how each is met? [Roni Even] The section discuss the ones that were discussed and needed clarifications > > * Section 9: > > Shouldn't there be two things registered here? Both the RTP header > extension and the RTCP SDES item. [Roni Even] both are there. > > * Nits: > > There are a few outdated references. [Roni Even] Can be done later > > Thanks, > Paul > > _______________________________________________ > clue mailing list > clue@ietf.org > https://www.ietf.org/mailman/listinfo/clue
- [clue] WGLC for draft-ietf-clue-rtp-mapping-07 en… Daniel Burnett
- Re: [clue] WGLC for draft-ietf-clue-rtp-mapping-0… Christian Groves
- Re: [clue] WGLC for draft-ietf-clue-rtp-mapping-0… Duckworth, Mark
- Re: [clue] WGLC for draft-ietf-clue-rtp-mapping-0… Paul Kyzivat
- Re: [clue] WGLC for draft-ietf-clue-rtp-mapping-0… Colin Perkins
- Re: [clue] WGLC for draft-ietf-clue-rtp-mapping-0… Roni Even
- Re: [clue] WGLC for draft-ietf-clue-rtp-mapping-0… Paul Kyzivat