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

"Murray S. Kucherawy" <superuser@gmail.com> Tue, 27 July 2021 00:41 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 315DE3A09BB; Mon, 26 Jul 2021 17:41:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 bEgOHzQCWbDQ; Mon, 26 Jul 2021 17:41:13 -0700 (PDT)
Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) (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 7041C3A09B9; Mon, 26 Jul 2021 17:41:12 -0700 (PDT)
Received: by mail-vs1-xe34.google.com with SMTP id x21so6240715vsx.5; Mon, 26 Jul 2021 17:41:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=F22xj3Hm8GyGq/0rumom2lUfPcQlBxD4KxjbmrT33YE=; b=qyskNr94ppJh55LSWdluT8L8x15PdN26ki0XZrqIwcWiVbRrYUBcTns5pH+75Vx1Lz RDlng3g377RGDe6RI99XwmKuiFa3L5caf3svNfv8MBm+YWv/StDtXCv750EdF+qsIB1S rqlGr7x5ZE5OceXDsgVjFbtaOvW92TXAKMc/SfGNGocGCLCLtk2bZXg7w4RXcaXlJYby 2KUSmZi/MaVrLnL7WqdRBihEyJI/JodWm83luwAMu6IOJCfWeWCxck2ds9xEKmXRIQHF hjxYUoYwP0zTRZ2IKCOSVGrq48F3l57Rl79KpXIGJSk6H6f0yujO8D17rX8Cm1wwFxlM JH0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=F22xj3Hm8GyGq/0rumom2lUfPcQlBxD4KxjbmrT33YE=; b=oQUacJkmxq5+MGKSSS69ZZ0ClRRPEnEOIJTPNv87THSCSkvKV/F7smAYfpuBdGNlxR Ie6xU0vdfRTOxRc3o4hbt/nwJEcTHNms3sLKe9BQAWDd3g/8P3Aa1i6CkPtdC2rWBcEY jcsH1hCNI4CAVQplGkEbc7PJKXzWywWNbvqUwBhyLf4+GnMzCmjrFg/uJ0jyUKUuq0Ws mlsA0W51Oo7rM35U9gb13Sh1dVSt5i9ttxwWVjZhmFbVeyd6NGeS/NhbhQUszRtg/rC4 GOCyAWH71nhNRvrGGCr/jBIlzjgDlGqZt7wHjVuJpr16VLTc7iPp5NW4FvCTGXFn4qXw 1fdw==
X-Gm-Message-State: AOAM533LAjqGbfqnfGIi0pCf6bk/f6FrNM+cG3LKg1bGNsQV/ME5chjv b4/5GSSeK5Yryesj7mcc+z5iIPlO4nx/G5vc3Xs=
X-Google-Smtp-Source: ABdhPJzeVL3gNCDT/hEyUi093y6aqEZsZQp56MQ7+HNG1yvn7yte+F1oeAUz5V9OSVyMp+zBO39XyOPHJqSbXangn14=
X-Received: by 2002:a67:ee59:: with SMTP id g25mr14443293vsp.40.1627346470861; Mon, 26 Jul 2021 17:41:10 -0700 (PDT)
MIME-Version: 1.0
References: <162559677588.2044.9942407728164856156@ietfa.amsl.com> <CAL0qLwaFS7gLV9YxpuWqedSyVQ3bAoJNQxVM5=D+Hc0tFTcS1w@mail.gmail.com> <cc768731-f6d4-14a2-df08-bd2e13214a70@cisco.com> <HE1PR07MB4441B42BB0E367FCECFF327093E19@HE1PR07MB4441.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB4441B42BB0E367FCECFF327093E19@HE1PR07MB4441.eurprd07.prod.outlook.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Mon, 26 Jul 2021 17:40:59 -0700
Message-ID: <CAL0qLwbUxyYFx_cOPZjw0uocjQ69f8ozDCFcNR-vWGukSMXYug@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Flemming Andreasen <fandreas=40cisco.com@dmarc.ietf.org>, Flemming Andreasen via Datatracker <noreply@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000527f8e05c81020ce"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/E_kMLsSs9UFpQmbuYIhrgd_E2TQ>
Subject: Re: [MMUSIC] Publication has been requested for draft-ietf-mmusic-rfc8843bis-04
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2021 00:41:17 -0000

(Sorry, was on vacation.)

On Mon, Jul 19, 2021 at 8:46 AM Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> >> 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.
>
> I am not really sure what the change would look like.
>
> For example, if I do the following change in Section 16.1:
>
> s/This document adds the MID SDES item to the IANA "RTP SDES Item Types"
> registry as follows: /This document updates the MID SDES item registered in
> RFC 8843 in the IANA "RTP SDES Item Types" registry as follows
>
> ...it seems like all the information is updated.
>

That's pretty much what I'm looking for.

>> 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 ?
>
> As Flemming said, people that have reviewed BUNDLEbis are also active in
> RTCWEB. In addition, when Flemming sent out the publication request e-mail,
> I did forward it to the RTCWEB list.
>
> As RTCWEB is meeting this week, I guess it can also be mentioned there.
>

It's probably fine to say in the shepherd writeup that there's substantial
overlap in the participants between RTCWEB and MMUSIC, just to head off any
questions ADs from other areas might have.

-MSK