RE: draft RFC to describe a URN for DTS audio

Phillip Maness <> Wed, 19 February 2014 02:40 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 2CE9B1A0534 for <>; Tue, 18 Feb 2014 18:40:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jWSDx1epTDcl for <>; Tue, 18 Feb 2014 18:39:56 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 4303E1A043D for <>; Tue, 18 Feb 2014 18:39:56 -0800 (PST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.878.16; Wed, 19 Feb 2014 02:39:51 +0000
Received: from (2a01:111:f400:7c10::1:180) by (2a01:111:e400:841::34) with Microsoft SMTP Server (TLS) id 15.0.883.10 via Frontend Transport; Wed, 19 Feb 2014 02:39:51 +0000
Received: from LAX-EXCA02.dts.local ( by ( with Microsoft SMTP Server (TLS) id 15.0.868.13 via Frontend Transport; Wed, 19 Feb 2014 02:39:51 +0000
Received: from LAX-EXMB02.dts.local ([fe80::b50e:9af7:de19:4aa9]) by LAX-EXCA02.dts.local ([fe80::5efe:]) with mapi id 14.03.0174.001; Tue, 18 Feb 2014 18:39:50 -0800
From: Phillip Maness <>
To: "Dale R. Worley" <>
Subject: RE: draft RFC to describe a URN for DTS audio
Thread-Topic: draft RFC to describe a URN for DTS audio
Date: Wed, 19 Feb 2014 02:39:48 +0000
Message-ID: <520A56052CF01E42B1C128F990FBE681A46B5587@LAX-EXMB02.dts.local>
References: <520A56052CF01E42B1C128F990FBE681A46AFD52@LAX-EXMB02.dts.local> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009001)(6009001)(13464003)(199002)(189002)(85714005)(377454003)(80022001)(81342001)(83072002)(2656002)(56816005)(80976001)(92726001)(33656001)(85852003)(63696002)(46406003)(94946001)(93136001)(79102001)(65816001)(83322001)(77096001)(44976005)(20776003)(19580405001)(19580395003)(90146001)(74706001)(47976001)(47736001)(49866001)(50986001)(6806004)(69226001)(74502001)(47446002)(76786001)(87266001)(55846006)(54316002)(53806001)(51856001)(15975445006)(77982001)(46102001)(59766001)(93516002)(81686001)(81816001)(86362001)(74366001)(74662001)(31966008)(85306002)(92566001)(76796001)(4396001)(74876001)(94316002)(81542001)(47776003)(95666001)(87936001)(95416001)(50466002)(56776001)(23726002)(76482001)(54356001); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR01MB469; H:LAX-EXCA02.dts.local; CLIP:; FPR:CE9FF1ED.AE3A97A6.29F3394A.84F4D1CD.20440; PTR:.; A:1; MX:1; LANG:en;
X-Forefront-PRVS: 012792EC17
Cc: "" <>, "Mark R. Johnson" <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 19 Feb 2014 02:40:00 -0000

Hi Dale,
Historically, many 100's of millions of products containing DTS technologies over many 1000's of SKUs and hundreds of manufacturers have shipped worldwide. We have an extensive footprint in physical media, but we know that digital media and cloud services are quickly displacing this. We have publicly stated that this is our vision and where we are focusing our efforts.

Sorry, I have to be intentionally vague from this point on. We have a number of business activities in process so we have to consider customers, partners and competitors (and, of course, the financial community, as we are a publicly traded company). The nature of these disclosures in publications such as an RFC can be (intentionally or unintentionally) indicative, (or perceived as being indicative), of future business.

I will say that our prospects are considerably more extensive than audio parameters. Audio parameters were used as examples as they are fairly obvious to the current nature of our business. We have the potential for many thousands of references over multiple categories under the dts namespace.

While I can't put any more color to this in writing, I would be happy to schedule a phone conversation with myself and our VP of Streaming and Media Solutions to give you a better idea of how we plan to utilize this namespace. When would be a good time to schedule a call? Fridays are generally good for us.

Best Regards,
Phil Maness

-----Original Message-----
From: Dale R. Worley []
Sent: Monday, February 17, 2014 2:46 PM
To: Phillip Maness
Subject: Re: draft RFC to describe a URN for DTS audio

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 and RFC 3553.)



This message and any included attachments are intended only for the use of the addressee, and may contain information that is privileged or confidential. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please destroy the original message and any copies or printouts hereof.