Re: [clue] Ben Campbell's Discuss on draft-ietf-clue-data-model-schema-15: (with DISCUSS and COMMENT)

"Ben Campbell" <ben@nostrum.com> Wed, 01 June 2016 17:46 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0044912D1A7; Wed, 1 Jun 2016 10:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level:
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] 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 3OqzT4fMRg1N; Wed, 1 Jun 2016 10:46:07 -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 69D6312D09D; Wed, 1 Jun 2016 10:46:07 -0700 (PDT)
Received: from [10.10.1.2] ([162.216.46.76]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u51Hk0RO029921 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 1 Jun 2016 12:46:02 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [162.216.46.76] claimed to be [10.10.1.2]
From: Ben Campbell <ben@nostrum.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Date: Wed, 01 Jun 2016 13:46:00 -0400
Message-ID: <E415901E-685E-4FEF-AE1B-11C84C935356@nostrum.com>
In-Reply-To: <1464802670.1029662.625029417.5E4385F0@webmail.messagingengine.com>
References: <20160601142232.16192.40456.idtracker@ietfa.amsl.com> <061e01d1bc24$7de529b0$79af7d10$@gmail.com> <4698EF47-EF15-4B33-9A14-4E2FB2A35488@nostrum.com> <1464802670.1029662.625029417.5E4385F0@webmail.messagingengine.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/clue/KW2DZUjfA17suhWkx5_j5pFuiV8>
Cc: clue-chairs@ietf.org, clue@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-clue-data-model-schema@ietf.org
Subject: Re: [clue] Ben Campbell's Discuss on draft-ietf-clue-data-model-schema-15: (with DISCUSS and COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2016 17:46:09 -0000


On 1 Jun 2016, at 13:37, Alexey Melnikov wrote:

> Hi Ben,
>
> On Wed, Jun 1, 2016, at 06:24 PM, Ben Campbell wrote:
>> Also inline,
>>
>> On 1 Jun 2016, at 12:41, Roni Even wrote:
>>
>>> Inline
>>> Roni
>>>
>>>> -----Original Message-----
>>>> From: Ben Campbell [mailto:ben@nostrum.com]
>>>> Sent: Wednesday, June 01, 2016 5:23 PM
>>>> To: The IESG
>>>> Cc: draft-ietf-clue-data-model-schema@ietf.org; 
>>>> clue-chairs@ietf.org;
>>>> ron.even.tlv@gmail.com; clue@ietf.org
>>>> Subject: Ben Campbell's Discuss on
>>>> draft-ietf-clue-data-model-schema-15:
>>>> (with DISCUSS and COMMENT)
>>>>
>
>  [snip]
>
>>>> ----------------------------------------------------------------------
>>>> DISCUSS:
>>>> ----------------------------------------------------------------------
>>>>
>>>> - 11.2: I would like to discuss whether it's a good idea to allow
>>>> arbitrary
>>>> values for mediaType, beyond those types registered in IANA.
>>>> The text seem to encourage proprietary values. Did the working 
>>>> group
>>>> consider requiring IANA registration of some sort for new values?
>>>
>>>
>>> [Roni Even] ] I think that the meaning was to allow the media types
>>> from the IANA registry
>>> http://www.iana.org/assignments/media-types/media-types.xhtml . The
>>> issue will be about the usage of other media types in the CLUE
>>> environment and not about the values themselves.
>>> Alissa also suggested that we clarify it
>>
>> I'm not sure I understand your response. When you say "other media
>> types", do you mean other types that are registered in the media-type
>> registry, but not described in RFC6838?
>
> In case it helps: top level media types like "model", "application",
> "message", and not full media types like "application/pdf". These 
> should
> be very rare. JUSTFONT WG is working on another one, but this is the
> first time something was added in more than 10 years. I honestly doubt
> anything other than "video", "audio" or "text" would be usable for 
> CLUE
> anyway.

That was my assumption. That's part of why I wondered about the ability 
to ability to invent arbitrary values. (But note that I've already 
cleared my DISCUSS.)

>
>> Or other arbitary media types
>> that are not registered or otherwise publicly documented?
>
> I would be impressed if any undocumented or unregistered top level 
> media
> type would be interoperable, so I don't think any such media types
> matter.

Does that mean you don't think people will use undocumented media-types 
due to the lack of interoperability, or that anyone who does will be 
effectively proprietary and we should assume they don't want to 
interoperate in the first place?

Thanks!

Ben.