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

Flemming Andreasen <fandreas@cisco.com> Tue, 27 July 2021 12:22 UTC

Return-Path: <fandreas@cisco.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 1BA433A2458; Tue, 27 Jul 2021 05:22:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.095
X-Spam-Level:
X-Spam-Status: No, score=-10.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.499, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 TZ76vZOAB6Uq; Tue, 27 Jul 2021 05:22:52 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE7A33A21A4; Tue, 27 Jul 2021 05:22:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7175; q=dns/txt; s=iport; t=1627388572; x=1628598172; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=B/JB17GvIoWgHyglg0rl9IqNOd03DWBzvvVOHOCqVOE=; b=U/+3Nsf7ZuXKmiGkVURpP2V9IW1mkXnXR4JcMKDQFe5Q5elabeKNcUl6 3suSpKZmF7gyyBOXBLtCMt8TGmpKTIFQb5BtJcQ9hZ5lJttfWCXn7XMSf ttE2pVZc3ceiRUF/Y4Y+gOE1PxT9cMFE34k+yAACQhGB7VvJot1LDAvl/ E=;
X-IPAS-Result: =?us-ascii?q?A0CdAQDd+f9gl4gNJK1aHQEBAQEJARIBBQUBghmDeAE6M?= =?us-ascii?q?YRHkTUtA4pohQWBSYN8iCoLAQEBD0EEAQGEWAKCfQIlOBMCBAEBAQEDAgMBA?= =?us-ascii?q?QEBBQEBBQEBAQIBBgQUAQEBAQEBAQFyhTsBBzKGQgEBAQMBI1YQCxgnAwICR?= =?us-ascii?q?hEGAQwGAgEBgm2CYgUhp3d6gTKBAYRog2GBY4E6hwkBhmQnHIFJRIEVJ4J+P?= =?us-ascii?q?oEEAYZWgmQEgkFXZARDaA55NAErOAO7Y4EXgzCeKwYPBSaDY4tfhhCREZYLg?= =?us-ascii?q?hyeCwGFD4F3IoFbTSMVO4JpUBkOhkBHhyQLAgmOSSUDLzgCBgEKAQEDCYsPA?= =?us-ascii?q?QE?=
IronPort-HdrOrdr: A9a23:6NA0FqlI322q7PqPIDQT95fqeDzpDfIo3DAbv31ZSRFFG/Fw9v rDoB1/73TJYVkqN03I9ervBEDjexPhHO9OgLX5VI3KNGOKhILCFvAA0WKN+UyFJwTOssJbyK d8Y+xfJbTLfD9HZB/BkWuF+gAbsby6zJw=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.84,273,1620691200"; d="scan'208,217";a="747002923"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 27 Jul 2021 12:22:51 +0000
Received: from [10.118.10.24] (rtp-fandreas-2-8817.cisco.com [10.118.10.24]) by alln-core-3.cisco.com (8.15.2/8.15.2) with ESMTP id 16RCMohi027965; Tue, 27 Jul 2021 12:22:50 GMT
To: "Murray S. Kucherawy" <superuser@gmail.com>, 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>
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> <CAL0qLwbUxyYFx_cOPZjw0uocjQ69f8ozDCFcNR-vWGukSMXYug@mail.gmail.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <b87963a8-5b66-dedd-38e5-3c4eb9ef1b4d@cisco.com>
Date: Tue, 27 Jul 2021 08:22:50 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwbUxyYFx_cOPZjw0uocjQ69f8ozDCFcNR-vWGukSMXYug@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------A6748C5E0B7ED5A4EEA520EE"
Content-Language: en-US
X-Outbound-SMTP-Client: 10.118.10.24, rtp-fandreas-2-8817.cisco.com
X-Outbound-Node: alln-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/1HDiZ0pH0PwGgD-iUAzKuJ-fwrU>
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 12:22:58 -0000


On 7/26/21 8:40 PM, Murray S. Kucherawy wrote:
> (Sorry, was on vacation.)
>
> On Mon, Jul 19, 2021 at 8:46 AM Christer Holmberg 
> <christer.holmberg@ericsson.com 
> <mailto: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.

I have updated the shepherd write-up accordinlgy.

Thanks

-- Flemming

>
> -MSK