1 / 7

Registry for tv:URIs draft-keesmaat-tvreg-00

Registry for tv:URIs draft-keesmaat-tvreg-00. Iko Keesmaat iko.keesmaat@tno.nl TNO, Netherlands IETF 67. Identifying TV broadcasts. Use cases : messaging about TV: “Watch CNN now!” with clickable, mnemonic identifiers buddy watching: “Bob is watching ARD1 ”

onofre
Download Presentation

Registry for tv:URIs draft-keesmaat-tvreg-00

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Registry for tv:URIsdraft-keesmaat-tvreg-00 Iko Keesmaat iko.keesmaat@tno.nl TNO, Netherlands IETF 67

  2. Identifying TV broadcasts Usecases: • messaging about TV: “Watch CNN now!” • with clickable, mnemonic identifiers • buddy watching: “Bob is watching ARD1” • presence in relation with TV watching • other forms of communication related to TV broadcast: • scheduling your TV broadcasts • web pages referring to TV broadcasts

  3. Requirements of TV identities Requirements: • identifier identifies uniquely a TV broadcast • id -> TV broadcast mapping MUST be unique • few (preferably one) identifiers per TV broadcast • TV broadcast -> id mapping SHOULD be unique • broad range of TV broadcasts: • terrestial, satellite, cable, cellular, internet • usable in internet communication: • IM, presence, calendar, email, webpages • easy to use by humans (typeable, mnemonic)

  4. Proposal tv:URI Existing RFC (RFC 2838): • URI scheme ‘tv:’, with DNS style syntax: • tv:abc.com, tv:abc.co.au, tv:east.hbo.com • Not required to be resolvable, but future ‘resolvability’ is not precluded: • clickable tv:URI, click results in activation of/switching to TV broadcast that is identified • No central registry specified (yet): • confusion about identifiers for a given TV broadcast: • tv:abc.co.au, or tv:abc.net.au for Australian Broadcast Co.? • tv:bbcone.bbc.co.uk or tv:bbc1.bbc.co.uk for the BBC?

  5. Registry for tv:URIs Requirements for registry: • attaches identification info (“identification records”) to tv:URIs, • can be searched/browsed by humans, • should be implementable even without involvement of TV broadcast parties Nice to have (future extension): • mappable to local TV broadcast frequencies, channels, IP addresses, etc.

  6. Issues • Structure of the registry: form of the “identification records” • Process of registration: who can register what: • nominees, versus TV broadcast owners • (Business) organisation of the registry • Relation with domain name system • Future mappability on local TV ‘frequencies’/’channels’

  7. Proposal 1. Create RFC from current internet-draft as Application Area product or 2. Start BOF/WG working on Registry for tv:URIs and other relevant documents Proposal: 1.

More Related