IETF Logo Mail Archive

Re: Reigistry for tv:URI's

"Mark Baker" <distobj@acm.org> Mon, 02 October 2006 20:03 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUU0g-0000bM-HP; Mon, 02 Oct 2006 16:03:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUU0f-0000WZ-CI for discuss@apps.ietf.org; Mon, 02 Oct 2006 16:03:29 -0400
Received: from ug-out-1314.google.com ([66.249.92.168]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUU0e-0008Fz-2k for discuss@apps.ietf.org; Mon, 02 Oct 2006 16:03:29 -0400
Received: by ug-out-1314.google.com with SMTP id k3so569764ugf for <discuss@apps.ietf.org>; Mon, 02 Oct 2006 13:03:26 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=KlLRryyyXOK7SwTvTgHAp6mPefZyEZVvbuj1EWV4cMhlOhBcRsVhX6VXrXwuSwLdyS1GfjEjsFwP2rOXgqIITCn8DQK+2oG6SDCyVJWVMTJuzWqPAGuG2ikJs/PKZ28I7POoimpUKM1yEC7XtohNqz3CfW/7dxPYhvGurFPusH8=
Received: by 10.78.203.15 with SMTP id a15mr1671763hug; Mon, 02 Oct 2006 13:03:26 -0700 (PDT)
Received: by 10.78.168.14 with HTTP; Mon, 2 Oct 2006 13:03:25 -0700 (PDT)
Message-ID: <c70bc85d0610021303g6be98c1dqc3beccd42a51264@mail.gmail.com>
Date: Mon, 02 Oct 2006 16:03:25 -0400
From: Mark Baker <distobj@acm.org>
To: "Deventer, M.O. (Oskar) van" <oskar.vandeventer@tno.nl>
Subject: Re: Reigistry for tv:URI's
In-Reply-To: <42F3BE57026C6E49B09E267EEF639D5601246747@ms-dt01thalia.tsn.tno.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <42F3BE57026C6E49B09E267EEF639D5601246747@ms-dt01thalia.tsn.tno.nl>
X-Google-Sender-Auth: 3082a28e81f0a94c
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: discuss@apps.ietf.org, "Zigmond, Dan" <djz@google.com>, "Keesmaat, N.W. (Iko)" <iko.keesmaat@tno.nl>
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

Some questions ...

On 10/2/06, Deventer, M.O. (Oskar) van <oskar.vandeventer@tno.nl> wrote:
> Ad 5) The relationship with the DNS registry will be as described in
> RFC2838. That is, DNS-style domain name syntax is used to identify a
> broadcast. Further then this syntactic relation we do not foresee any
> relation with the DNS.

So would there be any relationship between, say, "tv:nbc.com" and
General Electric (the current owner, per the DNS)?  If yes, do you
intend to reuse the association already maintained by the DNS/ICANN,
or do you intend to create a new registry to make this association?
If not, don't you think General Electric might express concern about
not owning the set of tv URIs using the nbc.com name?

You also mentioned that anybody would be able to register a tv URI.
Again, don't you think GE (or Disney or ...) would balk at that?

> Note that this implies - as already stated in
> RFC2838 - that it is not the intention that tv:URI's are resolved
> through the DNS.

It sounds like you're leaving the door open to resolvable URIs which
is good, but what would you recommend for those that want them?

And a meta question; would this discussion not be more appropriate for
the URI list (uri@w3.org)?

Cheers,

Mark.

v2.23.0 | Report a Bug | By Email