Standards


Ordering ITU standards
International Telecommunication Union (ITU)
International Organization for Standardization (ISO)
MPEG home page (I think it's by Leonardo Chiariglione. MPEG Convener.) From here, you can link to a lot of MPEG information.
MPEG ORG By Tristan Savatier and Chad Fogg, long-time MPEG gurus.
Peter Rice's work-related links Links to lots of video coding standards
H.324 Downloadable PSTN videophone standard documents.
Summary of H.324 video teleconferencing standard at ITU
Summary of H.263 video coding standard at ITU
Reference Implementation for G.711, G.721, G.723 (uuencoded TAR file offered by Sun)
Summary of G.723 voice codec at ITU
IEEE

The Internet Engineering Task Force: IETF Home Page contains the collections of standards that are being developed for the internet (RFC's and Draft standards that they have proposed).
Cisco - USA Cisco Connection Online - AUS online Universecd contains a lot of useful information including:
Internetworking Terms and Acronyms  This is a good set of glossaries describing the protocols and acronyms that show up so regularly in a non-technical manner.

 Internetworking Technology Overview. More detailed and technical dicussions.

See the Internet Protocols pages for detailed descriptions of Transmission Control Protocol (TCP)  and  User Datagram Protocol (UDP)


RTP

The Internet Real-Time Transport Protocol (RTP) (see RFC 1899 or the newer Draft revision) is the proposed protocol for all forms of real-time data on the Internet.
RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services. RTP does not address resource reservation and does not guarantee quality-of-service for real-time services. The data transport is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner scalable to large multicast networks, and to provide minimal control and identification functionality. RTP and RTCP are designed to be independent of the underlying transport and network layers. RTP typically is used in conjunction with UDP, but can work with other layer protocols.
The RTP protocol is used by products like streaming video servers  (eg: VXtreme webtheater) as well as audio/video internet phones (eg: Microsoft NetMeeting ). As RTP is only at the draft standard stage, some variations in it's implementation  have already been observed in some products.
RTP is intended to be able to support real-time applications, and it is expected that it will often be built into the application rather than being implemented as a separate layer. RTP is a flexible protocol framework which specifies only those functions expected to be common across all the applications for which RTP would be appropriate. RTP is intended to be tailored through modifications and/or additions to the headers as needed.
RTP requires companion documents due to it's extensibility that specify the details of payloads (encodings) and the formats of the payload as carried in RTP. One example is  RTP Profile for Audio and Video Conferences with Minimal Control (RFC 1890), which  specifies the audio and video encodings (compression and encryption modes) used within RTP packets.


RSVP

Resource Reservation Setup Protocol  is a signalling protocol that allows recievers to request resources (bandwidth and buffers to overcome delays) on the path back to senders. RSVP supports multi-cast operation and supports recievers with different characteristics. It was developed to support real-time audio/video across the internet by reserving sufficient resources between a reciever and a sender for the data to arrive without degradation.
The RSVP protocol is used by a host to request specific qualities of service from the network for particular application data streams or flows. RSVP is also used by routers to deliver quality-of-service (QoS) requests to all nodes along the path(s) of the flows and to establish and maintain state to provide the requested service. RSVP
requests will generally result in resources being reserved in each node along the data path. [This is contrary to the current internet situation where the path of each packet is essentially provided on a best-service available basis]
RSVP requests resources in only one direction, so a reciever may request resources to a sender resulting in one path, and the sender may request resources back to the (or many) recievers resulting in other resources being used and reserved..
RSVP operates on top of the IPv4 or IPv6 network protocol and RSVP does not transport application data but is rather an Internet control protocol, like ICMP, or routing protocols.
rfc2205 Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
rfc2210 The Use of RSVP with IETF Integrated Services
The routers within the internet would need to be updated to support the RSVP protocol, and the service providers and carriers would have to be convinced that it is worthwhile to maintain extra capacity to enable the internet to support both reserved services and best available services (current internet), before RSVP becomes widely available.
At present it seems that the service providers and carriers do not think that it will be economically viable to introduce RSVP on a large scale. This is a different view to a year ago, and may change again as the manufacturers of routers assess their positions.


ASF (advanced streaming format) Microsoft NetShow - ASF White Paper Describes what ASF is, and has references to the standards that it is both based on and hopes to support in future versions. See the sept.97 press release: Microsoft, Industry Leaders Publish ASF Draft Specification In Collaborative Effort to Standardize Internet Streaming Media Formats