| Related sites for http://www.faqs.org/rfcs/rfc2838.html |
| Swissbit_Ltd_ Sells computer memory products for desktop, notebook and server PCs and is a distributor of Mosel Vitelic products in Europe. Located in Switzerland. | | RFC_1722 RIP Version 2 Protocol Applicability Statement. G. Malkin. November 1994. | | Bean_Software_Search_Control ASP.NET web custom control, intended for web developers add searching database features to their web sites. | | Stunnel A universal SSL tunnel. It is designed to work as SSL encryption wrapper between remote client and local (inetd-startable) or remote server. [Free / Open Source] | | Linux_Forums__Installing_NVIDIA_3D_Drivers Howto explaining installation process for NVIDIA 3d graphics drivers. | | Franklins_NET Based in New London, Connecticut, they offer expertise in web development on the Microsoft.NET platform, system design and development, developer training and mentoring, and .NET site hosting. | | COSS_Systems_Inc_ Manufacturing software for small and mid-sized make-to-order and mixed mode manufacturers like job shop, aerospace, tool and mold, discrete manufacturers. Includes integrated ERP for estimating and qu | | 20/20_Engineering Provides engineering solutions and graphic simulations for industrial automation, robotics, machine design, electro-optical systems. | | Ixi_Software Prototypes and apps for composition of experimental music. | | BBay_com_3D_Products Commercial 3D polymesh, Poser4 ready. Suitable for other programs such and Bryce, 3D Studio Max, Wavefront. Custom work available. | | Programming_Languages_Mini-howto Briefly compares major Linux programming languages: C, C++, Fortran, Java, Lisp, Perl, PHP, Python, Tcl; by Risto S. Varanka. | | s38_org_-_WebWorks Articles on web development topics including interface design rules of thumb, W3C compliancy, and ADA issues in website design. | | Dolphinity Free multi users and multi projects management software. | | GroteApproach Offers web-based employee performance appraisal software and services. | | RFC_1786 Representation of IP Routing Policies in a Routing Registry (ripe-81++). T. Bates, E. Gerich, L. Joncheray, J-M. Jouanigot, D. Karrenberg, M. Terpstra, J. Yu. March 1995. | | BulletProof_FTP_Server Full featured server for Windows. | | NB_Design Offers design and graphics services. | | Open_Dynamics_Engine ODE is a platform independent C++ library for simulating articulated rigid body dynamics; ground vehicles, legged creatures, or moving objects. Supports advanced joints, contact with friction, and bui | | Palcom_InfoTech_Pvt__Ltd Offers design, maintenance, e-commerce solution, hosting and domain registration. Based in India. | | Realmailonly Email Spam filtering service for businesses. Mailboxes available. |
|
RFC 2838 (rfc2838) - Uniform Resource Identifiers for Television Broadcasts@import 'http://faqs.org/abstracts/css/default.css';@import 'http://faqs.org/search.css';function erfc(s){document.write("[ RFC Index | RFC Search | Usenet FAQs | Web FAQs | Documents | Cities ]Alternate Formats: rfc2838.txt | rfc2838.txt.pdfRFC 2838 - Uniform Resource Identifiers for Television BroadcastsSearch the Archives  Display RFC by number RFC2838 - Uniform Resource Identifiers for Television BroadcastsNetwork Working Group D. ZigmondRequest for Comments: 2838 WebTV Networks, Inc.Category: Informational M. Vickers Liberate Technologies, Inc. May 2000 Uniform Resource Identifiers for Television BroadcastsStatus of this Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.Copyright Notice Copyright (C) The Internet Society (2000). All Rights Reserved.1. Introduction World-Wide Web browsers are starting to appear on a variety of consumer electronic devices, such as television sets and television set-top boxes, which are capable of receiving television programming from either terrestrial broadcast, satellite broadcast, or cable. In this context there is a need to reference television broadcasts using the URI format described in [RFC 2396]. This document describes a widely-implemented URI scheme to refer to such broadcasts.2. Television URI The basic structure of a television URI is: tv:<broadcast> where broadcast is a description of the data source. The description takes the form of a DNS-style identifier for a particular broadcaster or television network. For example: tv:wqed.org the WQED station tv:nbc.com the NBC network3.1. Scheme-only form A simplest form of the "tv:" URI scheme is used to refer to the "current" or "default" channel: tv: This URI refers to whichever television broadcast is currently being received by the device. It is often used in combination with HTML content that is actually being broadcast along with the audio and video, where the meaning of "current broadcast" is quite unambiguous (because it is the broadcast along with which the content containing the URI was received). This is in fact the most common usage of the "tv:" scheme today, and is explicitly referenced by the recently published specification of the Advanced Television Enhancement Forum [ATVEF 1.1].3.2 DNS-style identifiers Television broadcasts traditionally have been identified in a variety of ways. All terrestrial television broadcasters are assigned call signs (such as "KDKA" or "WQED") to identify their signal. These are generally assigned by national authorities (such as the Federal Communications Commission in the United States) and are world unique. The global namespace is managed by the International Telecommunications Union, which assigns portions to member countries (see [ITU RR]). Many modern television networks are not broadcasted over-the-air, but available only through cable or satellite subscriptions. The identifiers for these networks (such as the familiar "CNN" and "HBO") are not regulated at this time. In some countries, even over-the-air broadcasters use these sorts of identifiers, rather than call signs. Unfortunately, these two namespaces overlap, with most network identifiers also being valid call signs. Furthermore, network identifiers are not world unique, and many cases exist of name collisions. (For example, both the Australian Broadcast Corporation and the American Broadcasting Company identify themselves as "ABC".) In order to ensure uniqueness, the "tv:" scheme uses DNS-style identifiers for all broadcast streams. Because these build on the existing registration system for DNS hostname, all name collisions can be resolved through the existing DNS dispute resolution processes. In the simplest form, domain names themselves are used as broadcast identifiers. For example: tv:abc.com the American Broadcast Company tv:abc.co.au the Australian Broadcast Corporation In some cases, networks have multiple broadcast streams that need to be distinguished. This is also handled in DNS style: tv:east.hbo.com HBO East tv:west.hbo.com HBO West It is important to note that these DNS-style identifiers need not match real hostnames; they should not be resolved to IP addresses using DNS. Thus, using the terms as defined in RFC 2396, the "tv:" scheme is a Uniform Resource Identifier and not a Uniform Resource Locator. In order to support these identifiers in a "tv:" URI, a receiver must implement a means to map known identifiers to frequencies. The nature of this map and the way in which it is used are currently browser- and device-specific and are beyond the scope of this document. In this way, the "tv:" scheme is somewhat analogous to the "news:" and "file:" schemes in [1]: it merely names a television broadcast signal but assumes that the local browser has some means for actually retrieving that signal on the local device. A variety of software systems currently provide device-specific mappings from such identifiers to specific channel numbers or directly to frequencies. These systems can be incorporated into television sets or set-top boxes to facilitate the interpretation of television URIs by the client device.3.3 Obsolete forms Previous drafts of this specification allowed broadcasts to be identified by channel numbers, such as "tv:4", and this form is currently supported by several independent platforms. The channel numbers generally correspond to tuning frequencies in the various national broadcast frequency standards; for example, "tv:4" in the United states would be found at 66 MHz. However, because this mapping of channel numbers to frequencies varies from country to country, this form is particularly ill-suited to use on the Internet. Previous drafts also allowed network identifiers and call signs to be used directly as broadcast identifiers, as in "tv:abc" and "tv:kron". These forms should not be used because of the name collision issues described in the previous section.4. BNF for Television URIs The following is a formal specification for the new URIs: tvuri = "tv:" [ broadcast ] broadcast = dns-identifier dns-identifier = *( domainlabel "." ) toplabel [ "." ] domainlabel = alphanum | alphanum *( alphanum | "-" ) alphanum toplabel = alpha | alpha *( alphanum | "-" ) alphanum The definitions of alpha and alphanum are from [RFC 2396]. Furthermore, the definition of dns-identifier is identical to the definition of hostname in RFC 2396, and is case-insensitive.5. Acknowledgments Many of the ideas in this document came out of conversations with Andrew Lochart. Other people who supplied valuable input include Matt Trifiro and Eric Del Sesto. The original draft of this URI scheme was developed while the author was at Wink Communications. More recent suggestions have come from Lee Acton, Jonathan Boltax, Dean Blackketter, Michael Dolan, Iain Hackett, Jim Helman, Sean McDowell, David Mott, Scott Watson, and others in the ATVEF Technical Working Group (which the authors co-chaired), and from Craig Finseth, Gomer Thomas, Harald Alvestrand, and Larry Masinter.6. Security Considerations This new URI scheme is subject to the same security implications as the general URI scheme described in [RFC 2396]. It is possible that the mere act of viewing a television broadcast signal may cause costs to be incurred to the viewer in some instances (e.g., "pay-per-view" movies and events). Any software that uses this URI scheme to allow automatic tuning of a client device to a particular television broadcast signal should alert users before performing actions that may incur costs to the user.7. References [RFC 2396] Berners T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998. [ATVEF 1.1] Advanced Television Enhancement Forum, "Advanced Television Enhancement Forum Specification Version 1.1r26," February 1999. http://www.atvef.com/library/spec1_1a.html [ITU RR] International Telecommunications Union, "Radio Regulations," 1998. See especially Article S19, "Identification of stations," and Appendix S42, "Table of allocation of international call sign series."9. Authors' Addresses Dan Zigmond WebTV Networks, Inc. 1065 La Avenida Mountain View, CA 94043 USA EMail: djz@corp.webtv.net Mark Vickers Liberate Technologies 2 Circle Star Way San Carlos, CA 94070 USA EMail: mav@liberate.com10. Full Copyright Statement Copyright (C) The Internet Society (2000). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. Comments about this RFC:RFC 2838: ABC Australia's domain name is "abc.net.au" not "abc.co.au". Indeed, there is no... by M0les (11/20/2005) Previous: RFC 2837 - Definitions of Managed Objects for the Fabric Element in Fibre Channel Standard Next: RFC 2839 - Internet Kermit Service [ RFC Index | RFC Search | Usenet FAQs | Web FAQs | Documents | Cities ] © 2008 FAQS.ORG. All rights reserved. |
|
