Re: [AVTCORE] WGLC on RTP topologies

Bo Burman <bo.burman@ericsson.com> Fri, 10 October 2014 15:44 UTC

From: Bo Burman <bo.burman@ericsson.com>
To: Roni Even <ron.even.tlv@gmail.com>, "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [AVTCORE] WGLC on RTP topologies
Thread-Index: Ac/WeDb+chBv/hfVT2ied9So6pprqgOC0QKQ
Date: Fri, 10 Oct 2014 15:44:00 +0000
Message-ID: <BBE9739C2C302046BD34B42713A1E2A22E329184@ESESSMB105.ericsson.se>
References: <007c01cfd678$4c608fd0$e521af70$@gmail.com>
In-Reply-To: <007c01cfd678$4c608fd0$e521af70$@gmail.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_BBE9739C2C302046BD34B42713A1E2A22E329184ESESSMB105erics_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/ls7m3mWloYbucfL8YzMslLzjRBo
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "stewe@stewe.org" <stewe@stewe.org>
Subject: Re: [AVTCORE] WGLC on RTP topologies
Precedence: list

I have only some editorial nits, no technical comments:

1.       Top of page 10: teh --> the

2.       First sentence of 3.3.3 at page 14: The reference [RFC6285] is actually not included in references but pure text.

3.       Figure 7 on page 15 has no caption text.

4.       Language, top of page 16: "...is, ..., be used as..." --> "...can, ..., be used as..." or "...is, ..., used as..."

5.       Page 18, just below Figure 10:  "...media is a handled..." --> "...media is handled..."

6.       Page 18, close to above: "...as each being associated..." --> "...each being associated..." or "...as each is associated..."

7.       Page 19, top: I think the referred Figure should be 10 (independent RTP sessions), not 8 (RTP session agnostic picture) or 9 (joint RTP session).

8.       Section 3.5.2, bottom of page 20: "If End Point B in Figure 11 were..." --> "...was"

9.       Section 3.6, mid page 22: "...each other End Point, ..." --> "...all other EndPoints, ..."

10.   Bottom of page 24: teh --> the

11.   In Figure 15: In RTP2 CSRCs should be (AA1+CA1), and in RTP3 CSRCs should be (AA1+BA1).

12.   In Figure 16: Not strictly needed, but to use consistent naming, F client's video should (as in Figure 17) be FV1, not CV1.

13.   Section 4.1.1, second clause: "in in" --> "in"

14.   Really minor: I think that centered pictures would be more visually pleasing, especially since the captions are generally centered. If you are editing XML, note that there are separate alignment properties for the caption (entire figure object) and the picture content...

I'm otherwise fine with the document, including the changes discussed previously on this list during the WGLC.

/Bo

From: avt [mailto:avt-bounces@ietf.org] On Behalf Of Roni Even
Sent: den 22 september 2014 17:17
To: avt@ietf.org
Cc: Magnus Westerlund; stewe@stewe.org
Subject: [AVTCORE] WGLC on RTP topologies


WG,


This is to start the WGLC on RTP Topologies in https://tools.ietf.org/html/draft-ietf-avtcore-rtp-topologies-update-04
The WGLC is for three weeks till October 14th

Please send your comments and approvals to the AVTcore list.





Authors, please let the WG chairs know if you are aware of any undeclared  IPR related to this draft. It is needed for the publication request.

Thanks

Roni Even

AVTcore co-chair

[AVTCORE] WGLC on RTP topologies Roni Even
Re: [AVTCORE] WGLC on RTP topologies Schwarz, Albrecht (Albrecht)
Re: [AVTCORE] WGLC on RTP topologies Stephan Wenger
Re: [AVTCORE] WGLC on RTP topologies Schwarz, Albrecht (Albrecht)
Re: [AVTCORE] WGLC on RTP topologies Colin Perkins
Re: [AVTCORE] WGLC on RTP topologies Bo Burman
Re: [AVTCORE] WGLC on RTP topologies Stephan Wenger