Re: [MMUSIC] Mirja Kühlewind's No Objection on draft-ietf-mmusic-sdp-mux-attributes-14: (with COMMENT)

"Ben Campbell" <ben@nostrum.com> Fri, 28 October 2016 15:20 UTC

Return-Path: <ben@nostrum.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 21456129407; Fri, 28 Oct 2016 08:20:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.331
X-Spam-Level:
X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431] 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 yl00HYTkAibQ; Fri, 28 Oct 2016 08:20:16 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 D32B2124281; Fri, 28 Oct 2016 08:20:16 -0700 (PDT)
Received: from [10.0.1.21] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u9SFKA4u023853 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 28 Oct 2016 10:20:11 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.21]
From: Ben Campbell <ben@nostrum.com>
To: Mirja Kühlewind <ietf@kuehlewind.net>
Date: Fri, 28 Oct 2016 10:20:10 -0500
Message-ID: <E12F4BE2-DD6E-4787-88C1-8E36DCB16EB0@nostrum.com>
In-Reply-To: <e7f7e348-895a-ec12-6b9f-a673b7c9c7b4@kuehlewind.net>
References: <147741587672.1323.3788097761711986441.idtracker@ietfa.amsl.com> <CAMRcRGTEj-HwOvWtCi5orEKurMirOZLepG2sB1Ya7x-nJU7Pvg@mail.gmail.com> <fefa06b9-75b1-2e58-6532-1a426f7fb69f@kuehlewind.net> <CAMRcRGSmRLEPNjjSnPv_X3-HRNMq8vbDOzQtvXqB7RazrdHuVQ@mail.gmail.com> <e7f7e348-895a-ec12-6b9f-a673b7c9c7b4@kuehlewind.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"; markup="markdown"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.5r5263)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/MkR7PIaLRK6aN0FtbUVy_15b8YA>
Cc: mmusic-chairs@ietf.org, draft-ietf-mmusic-sdp-mux-attributes@ietf.org, The IESG <iesg@ietf.org>, mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Mirja Kühlewind's No Objection on draft-ietf-mmusic-sdp-mux-attributes-14: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 28 Oct 2016 15:20:18 -0000

On 28 Oct 2016, at 3:24, Mirja Kühlewind wrote:

> Hi Suhas,
>
> see below.
>
> On 28.10.2016 06:29, Suhas Nandakumar wrote:
>  >
>  >             2) Is the new registry for the Mux Category really 
> needed? Is it
>  >         expected
>  >             to (much) more categories in future?
>  >
>  >
>  >         [Suhas] -  We need the registry to list the currently 
> defined Mux
>  >         Categories
>  >         and also we do see there might be couple of more categories 
> (if not many)
>  >         that might get defined in the future.
>  >
>  >
>  >     This seems really vague for me. I would assume that you 
> actually don't
>  >     need a registry now and if there will be more categories 
> defined in the
>  >     future (which doesn't seem very likely) a new doc could still 
> define a
>  >     registry and update this RFC.
>  >
>  >
>  >
>  > [Suhas]
>  >  Section 15.2 and its sub-sections assign the multiplexing 
> categories  to
>  > several of the sub-registries in the IANA SDP Parameters registry. 
> This is
>  > done by adding a new column called 'Mux Category' to each of the
>  > sub-registries in the SDP Parameters registry.
>  > Having a registry defined to identify the names of these 
> Multiplexing
>  > categories ( as in Section 15.1) will ensure there is a formal 
> place for
>  > these names and formal rules to expand the category set in the 
> future.
>
> The formal place where these categories are explained is this RFC. 
> This RFC could also talk about the opportunity or even process to 
> expand this list in future. However, as long as it is not clear that 
> any expansion will be really needed in future, I don't see a need for 
> e registry.
>
> That's my view point. Please consult your AD for final advise.

I understand that the working group thinks that the chance that new 
categories will come up is high enough that they prefer to define the 
registry (and more importantly, the registration policy) in advance. I 
agree that this is a borderline case, and reasonable people could go 
either way. I don't think we should overrule the working group consensus 
this late in the process.

Thanks!

Ben.