Re: [MMUSIC] Publication has been requested for draft-ietf-mmusic-rfc8843bis-04

[Flemming Andreasen <[e-mail]>]

On 7/17/21 11:06 PM, Murray S. Kucherawy wrote:
> On Tue, Jul 6, 2021 at 11:39 AM Flemming Andreasen via Datatracker 
> <[e-mail] <mailto:[e-mail]>> wrote:
>
>     Flemming Andreasen has requested publication of
>     draft-ietf-mmusic-rfc8843bis-04 as Proposed Standard on behalf of
>     the MMUSIC working group.
>
>     Please verify the document's state at
>     https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc8843bis/
>     <https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc8843bis/>
>
>
> I've reviewed the diff between this and RFC8843.  Looks good.  Thanks 
> for a good shepherd writeup too.  Just a couple of comments:
>
> The registrations in Section 16 should make it clear they are 
> updating, not creating, the entries they describe.  RFC 8843 created them.
Ok. I believe the authors can make that change later.
>
> It would probably make things even smoother to indicate in the 
> shepherd writeup that RTCWEB reviewed this, so that their JSEP update 
> doesn't conflict with it.  (And if they didn't, please at a minimum 
> forward them the IETF Last Call announcement when it comes out.)  I 
> know the writeup already describes the separation of work, but we're 
> likely to be asked to confirm that there was more coordination than that.
Good point. We did not have RTCWEB review the update per se, however a 
couple of the people that reviewed it are intimately involved in the 
RTCWEB work. Should we alert the RTCWEB group at this point or wait 
until the IETF Last Call ?

Thanks

-- Flemming
>
> Neither of these are enough to hold up IETF Last Call, so I'll go get 
> that going now.
>
> -MSK, ART AD