IETF Logo Mail Archive

Re: [MMUSIC] Alissa Cooper's Discuss on draft-ietf-mmusic-rfc4566bis-35: (with DISCUSS and COMMENT)

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 24 July 2019 20:23 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 05AA31205FE; Wed, 24 Jul 2019 13:23:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 Dtb4edfL7-qo; Wed, 24 Jul 2019 13:23:23 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 576651205F8; Wed, 24 Jul 2019 13:23:23 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x6OKNFLq028005 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 24 Jul 2019 16:23:16 -0400
To: Adam Roach <adam@nostrum.com>, Alissa Cooper <alissa@cooperw.in>, The IESG <iesg@ietf.org>
Cc: fandreas@cisco.com, mmusic-chairs@ietf.org, draft-ietf-mmusic-rfc4566bis@ietf.org, mmusic@ietf.org
References: <155907213212.25802.10923362703417281306.idtracker@ietfa.amsl.com> <da24d89f-79cc-3fcc-aaad-4753cc552b3b@alum.mit.edu> <e3baf0e3-831b-7286-fbb4-c76758e12c7a@nostrum.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <f5ed2cbb-188d-19ff-a973-bb27c4e3ca0b@alum.mit.edu>
Date: Wed, 24 Jul 2019 16:23:18 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <e3baf0e3-831b-7286-fbb4-c76758e12c7a@nostrum.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/4GHLwGmDUKr8dok0G4CZsxuPTJI>
Subject: Re: [MMUSIC] Alissa Cooper's Discuss on draft-ietf-mmusic-rfc4566bis-35: (with DISCUSS and COMMENT)
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: Wed, 24 Jul 2019 20:23:25 -0000

On 7/24/19 8:45 AM, Adam Roach wrote:

> Paul --
> 
> I see that there are some changes in -36 around this text ("IANA will 
> populate its registries with some or all of these values"). This isn't 
> really clear enough for IANA to know what to do. Could you produce a new 
> version that is explicit regarding which of these collected fields are 
> published? (e.g.: "IANA will populate its registries with the parameter 
> name, the parameter type, and the document reference.")

I *can*. But is it necessary for these instructions to be included in 
the draft? ISTM that the structures IANA has now often differ from 
(probably inadequate) instructions in drafts. My impression is that iana 
has considerable discretion about how this stuff is structures in the 
registries. Could I just work with IANA on how to do it?

But if putting this into -37 is the best way then I am happy to do that.

	Thanks,
	Paul

v2.23.0 | Report a Bug | By Email