Re: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-rfc4566bis-29.txt

Hi Paul

I have taken a closer look at the updated document, and I think the 
document looks good overall, incl. terminology consistency.

I did note a couple of issues, that require clarification:

1) Section 5.14 - Media Descriptions
The 6th paragraph talks about use of the rtcp attribute with 
hieararchically encoded streams, however AFAIK, the rtcp attribute does 
not support. If it does, then I think the explanation needs to be 
elaborated on (basically, you would need to have more than one of them I 
assume).

2) Section 8.2.3 - Media Formats ("fmt")
Per the beginning of Section 8.2, this is supposed to be a registry, 
however it doesn’t say how this registry works for RTP payload formats. 
Who registers what where ? I will also note, that, although the text is 
similar to RFC4566, such a registry doesn’t actually exist under SDP 
(nor do I think that is the intent).

3) Section 8.2.4.1 - New Attributes
Part of the registration requires "Offer/Answer procedures as explained 
in [RFC3264]". While I agree with that, as part of the recent IESG 
review on Bundle, there were some concerns with simply adhering to RFC 
3264. We plan to discuss this further in the upcoming MMUSIC session in 
Montreal (IETF 102).

I have a few minor nits as well which I will send separately.

Thanks

-- Flemming

On 6/5/18 11:42 AM, Paul Kyzivat wrote:
> I just posted version -29.
>
> This only has minor changes to usage of 'field' to improve consistency 
> across the document. I've been holding these changes for awhile, 
> awaiting additional issues to address, but there have been no comments 
> and I don't want to hold these any longer.
>
> I have no more changes planned. Please comment if you want anything 
> else changed.
>
>     Thanks,
>     Paul
>
>
> -------- Forwarded Message --------
> Subject: New Version Notification for draft-ietf-mmusic-rfc4566bis-29.txt
> Date: Tue, 05 Jun 2018 08:30:12 -0700
> From: internet-drafts@ietf.org
> To: mmusic-chairs@ietf.org, Mark Handley <m.handley@cs.ucl.ac.uk>, Ali 
> Begen <ali.begen@networked.media>, Colin Perkins <csp@csperkins.org>, 
> Mark Handley <M.Handley@cs.ucl.ac.uk>, Paul Kyzivat 
> <pkyzivat@alum.mit.edu>
>
>
> A new version of I-D, draft-ietf-mmusic-rfc4566bis-29.txt
> has been successfully submitted by Paul Kyzivat and posted to the
> IETF repository.
>
> Name:        draft-ietf-mmusic-rfc4566bis
> Revision:    29
> Title:        SDP: Session Description Protocol
> Document date:    2018-06-05
> Group:        mmusic
> Pages:        59
> URL: 
> https://www.ietf.org/internet-drafts/draft-ietf-mmusic-rfc4566bis-29.txt
> Status: https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc4566bis/
> Htmlized: https://tools.ietf.org/html/draft-ietf-mmusic-rfc4566bis-29
> Htmlized: 
> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-rfc4566bis
> Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-rfc4566bis-29
>
> Abstract:
>    This memo defines the Session Description Protocol (SDP).  SDP is
>    intended for describing multimedia sessions for the purposes of
>    session announcement, session invitation, and other forms of
>    multimedia session initiation.  This document obsoletes RFC 4566.
>
>
>
>
> Please note that it may take a couple of minutes from the time of 
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> .
>