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

Alexey Melnikov <aamelnikov@fastmail.fm> Wed, 01 June 2016 17:37 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 30BE712D0E5; Wed, 1 Jun 2016 10:37:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=Xwy31twT; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=FLA+y12R
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 ICGYGwij_qaF; Wed, 1 Jun 2016 10:37:51 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B57EF12D0DC; Wed, 1 Jun 2016 10:37:51 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 1B0072139F; Wed, 1 Jun 2016 13:37:51 -0400 (EDT)
Received: from web5 ([10.202.2.215]) by compute4.internal (MEProxy); Wed, 01 Jun 2016 13:37:51 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=2eR7xxKlxBAO2Agi89Zmh6acTmc=; b=Xwy31t wTuKXS18XGAE8LgtbIycdjCW92e+Uvw72yMMpiWmn8Pus6olpnP8FPpGWTCTypKo 8wLs2dop7iQnAzwT2AJhsf2TS2vPwdyMN8Ofh9WFgboptNaKc+TQk1aXvxWDlcqh dVG7MYUv2QcZ2p/wR2fcWDejfdO7kqLdpTedg=
DKIM-Signature: v=1; a=rsa-sha1; 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-sasl-enc:x-sasl-enc; s=smtpout; bh=2eR7xxKlxBAO2Ag i89Zmh6acTmc=; b=FLA+y12RsMUPMaXZOgYyHV1IOlY+pjXubLg2XNaLC2/CMDy SzTk/g6QAIJvWWzMbg7he6099cCvTEAiAUMXNzG+aUBeH4qrKlWBldlgA6K1JW+T ePlnvoRncEmy+mTneyj09Y/ogkGvAI/C4i+BsSSAhPaD6gbUJw+y63mv35IM=
Received: by mailuser.nyi.internal (Postfix, from userid 99) id D2030A9021; Wed, 1 Jun 2016 13:37:50 -0400 (EDT)
Message-Id: <1464802670.1029662.625029417.5E4385F0@webmail.messagingengine.com>
X-Sasl-Enc: yqP36sFu2W2Hj33XG481urHG8ciBM9NDTGFsCsDRV0Ge 1464802670
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: Ben Campbell <ben@nostrum.com>, Roni Even <ron.even.tlv@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-38f217ef
Date: Wed, 01 Jun 2016 18:37:50 +0100
In-Reply-To: <4698EF47-EF15-4B33-9A14-4E2FB2A35488@nostrum.com>
References: <20160601142232.16192.40456.idtracker@ietfa.amsl.com> <061e01d1bc24$7de529b0$79af7d10$@gmail.com> <4698EF47-EF15-4B33-9A14-4E2FB2A35488@nostrum.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/clue/XGES7Ze04LD2Ss6HNtnHbMuMd-A>
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:37:54 -0000

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.

> 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.