IETF Logo Mail Archive

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

Alissa Cooper <alissa@cooperw.in> Thu, 01 August 2019 17:54 UTC

Return-Path: <alissa@cooperw.in>
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 C9BA1120186; Thu, 1 Aug 2019 10:54:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=ZtA7Zo/4; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=gQ697m57
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 j_mWX6Lm9RZ1; Thu, 1 Aug 2019 10:54:38 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B98812018C; Thu, 1 Aug 2019 10:54:38 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 64DE921AFB; Thu, 1 Aug 2019 13:54:37 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Thu, 01 Aug 2019 13:54:37 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=g HHS8pqv5K14Jk7iqgJ1GgZD3g7t7TCIvNTBISjfGl0=; b=ZtA7Zo/4AEghbnUhp ZehY3rcaS+tmD3G4IWHjCW0zT/lJ2NeOenlYzygi3CIjs0MpLk9Gr6L28cjTAxSh FdvFMCcEfJH3V2XBe6AUlhECPNjkIqwhli++DYUeekMqc+UkzV8/ogdgm94bWKQM 9lMGfTdGCndystYUKCMJAJ92seoMMbPa0HVgBKKraRwCRt6JRykg8KM3j3GqvxUN VQi8AgK1SYei1w8d344JhI8i12jy9Q+Q33SF5DVEYj5zyACSR1yKPKR1GgXlGhHV LH6saqwCdw0L/vZeCR38lN1bUMnMH7bQP2Kisa2zpv+Gbt7Qe3X9NN5ih6ZshQDP GU8Lw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=gHHS8pqv5K14Jk7iqgJ1GgZD3g7t7TCIvNTBISjfG l0=; b=gQ697m57B3RmrGnUBzgGzG3GFt/oFsDf4LZoL0kAPKMjmUuE5GzBlRTh8 gwJLsbgpx9CiAPrIr0nnqhS8/fTj4ml8SnhoQnX7R14ROQR22EVpeWNINCI/HnUL 5ksOGbQOLNtymJOzouRwDyTS8bcddm7+EbTpkUgJpoQpTdwUTCiQby0P+7XN8tHx 1ofkXOtCp6ton9WGwR3MzI4VT3T2OF/SJB5gggqgSmpnFMgsljuglKVLK27SIm4g HRGR3nwJb253pdRLZABpJdQjyzpC06+BE97wxUNTV5gXARuL6qifk0QflWR2PWue BGaQ8qK8xS8mg0u47YCyRK77J9ZcQ==
X-ME-Sender: <xms:XCdDXVv89fut4NH7xxdtL6XN835Wq94HrqbXzpq5XdkZCj2E547dxw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrleejgdduudeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomheptehlihhs shgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucfkphepud ejfedrfeekrdduudejrdejkeenucfrrghrrghmpehmrghilhhfrhhomheprghlihhsshgr segtohhophgvrhifrdhinhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:XCdDXe7q--foRpq5zKLudU6D6RZfkZ6PBgOtH4-zFXFmlWUp_rUGTg> <xmx:XCdDXZfXw9sPeQ1q8NnkGfTvw-yhNTuDh0AG9Kc0Oa7a2o-s038-nQ> <xmx:XCdDXTxcFK_POTdNSiMeoVIiJX2tL0w0B9Ojp1QpupadnY0AR9UpYg> <xmx:XSdDXfmvf4yISBD0x9O9dsf5VF8A3OT7nivUHOumgRT47Z2kStNosA>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.78]) by mail.messagingengine.com (Postfix) with ESMTPA id 11D2B380084; Thu, 1 Aug 2019 13:54:36 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CALaySJLMp0+D6ceS_NxPbkTLKbiQjmX6kbXJvKfgt_2Cnpdwng@mail.gmail.com>
Date: Thu, 01 Aug 2019 13:54:33 -0400
Cc: Adam Roach <adam@nostrum.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, IESG <iesg@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, draft-ietf-mmusic-rfc4566bis@ietf.org, mmusic@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF5C7C72-52A2-4E1C-8814-D26270B8B8F3@cooperw.in>
References: <155907213212.25802.10923362703417281306.idtracker@ietfa.amsl.com> <da24d89f-79cc-3fcc-aaad-4753cc552b3b@alum.mit.edu> <e3baf0e3-831b-7286-fbb4-c76758e12c7a@nostrum.com> <f5ed2cbb-188d-19ff-a973-bb27c4e3ca0b@alum.mit.edu> <58600430-a539-7773-8fb2-4a065f95cd64@nostrum.com> <CALaySJLMp0+D6ceS_NxPbkTLKbiQjmX6kbXJvKfgt_2Cnpdwng@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/TOj4CAVNGgHn_9zt88o4H-Z6_5Q>
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: Thu, 01 Aug 2019 17:54:40 -0000

Based on some unrelated recent conversations with IANA, I think it is better for all involved to have the explicit instructions in the RFC.

Alissa


> On Jul 24, 2019, at 5:24 PM, Barry Leiba <barryleiba@computer.org> wrote:
> 
> Even if IANA understands what you want and gets it perfect when they
> create the registry, there is value in having the specifics recorded
> in the IANA Considerations in the published RFC.  It's not hard to do,
> so let's just do it, yes?
> 
> Barry
> 
> On Wed, Jul 24, 2019 at 4:40 PM Adam Roach <adam@nostrum.com> wrote:
>> 
>> On 7/24/19 16:23, Paul Kyzivat wrote:
>>> 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.
>> 
>> 
>> Even if it's not the best -- and it might be -- it's certainly the fastest.
>> 
>> To be clear, I sent my email after conferring with Alissa, and it is my
>> impression that it would take more than a little convincing for her to
>> allow the current text in -36 to move forward, if it is indeed possible
>> at all.
>> 
>> /a
>>

v2.23.0 | Report a Bug | By Email