Re: draft RFC to describe a URN for DTS audio

worley@ariadne.com (Dale R. Worley) Mon, 17 February 2014 22:51 UTC

Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: urn-nid@ietfa.amsl.com
Delivered-To: urn-nid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63CEE1A0537 for <urn-nid@ietfa.amsl.com>; Mon, 17 Feb 2014 14:51:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
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 ug2htaySaTcp for <urn-nid@ietfa.amsl.com>; Mon, 17 Feb 2014 14:51:10 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 083D51A041C for <urn-nid@apps.ietf.org>; Mon, 17 Feb 2014 14:51:09 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id s1HMo8Z0006242; Mon, 17 Feb 2014 17:50:11 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id s1HMjnvr5224842; Mon, 17 Feb 2014 17:45:49 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s1HMjnBU5200650; Mon, 17 Feb 2014 17:45:49 -0500 (EST)
Date: Mon, 17 Feb 2014 17:45:49 -0500 (EST)
Message-Id: <201402172245.s1HMjnBU5200650@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Phillip Maness <Phillip.Maness@dts.com>
In-reply-to: <520A56052CF01E42B1C128F990FBE681A46AFD52@LAX-EXMB02.dts.local> (Phillip.Maness@dts.com)
Subject: Re: draft RFC to describe a URN for DTS audio
References: <520A56052CF01E42B1C128F990FBE681A46AFD52@LAX-EXMB02.dts.local>
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/cWomaDeNYAD21vHODSxtO2WuO2M
Cc: urn-nid@apps.ietf.org
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn-nid/>
List-Post: <mailto:urn-nid@ietf.org>
List-Help: <mailto:urn-nid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 22:51:14 -0000

What are the objects that these URNs name?  As far as I can tell, the
draft does not specify that.

It appears from the two examples that the objects are intended to be
parameters which are attributes of particular DTS audio encodings.  In
that case, it would seem that there will only be a small number (maybe
tens or hundreds) of these URNs that are valid.  If so, it may save
effort to have IETF allocate a sub-namespace,
"urn:ietf:params:dts:..." into which DTS can assign paramater URNs.
(See https://www.iana.org/assignments/params/params.xml and RFC 3553.)

Dale