RFC 2862 on RTP Payload Format for Real-Time Pointers
RFC Editor <rfc-ed@ISI.EDU> Thu, 29 June 2000 22:39 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21632; Thu, 29 Jun 2000 18:39:05 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id SAA19048 for ietf-123-outbound.10@ietf.org; Thu, 29 Jun 2000 18:35:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA19023 for <all-ietf@loki.ietf.org>; Thu, 29 Jun 2000 18:25:39 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21402 for <all-ietf@ietf.org>; Thu, 29 Jun 2000 18:25:37 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id PAA23270; Thu, 29 Jun 2000 15:25:38 -0700 (PDT)
Message-Id: <200006292225.PAA23270@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2862 on RTP Payload Format for Real-Time Pointers
Cc: rfc-ed@ISI.EDU, rem-conf@es.net
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 29 Jun 2000 15:25:37 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries.
RFC 2862
Title: RTP Payload Format for Real-Time Pointers
Author(s): M. Civanlar, G. Cash
Status: Standards Track
Date: June 2000
Mailbox: civanlar@research.att.com, glenn@research.att.com
Pages: 7
Characters: 12031
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-avt-pointer-02.txt
This document describes an RTP [1] payload format for transporting the
coordinates of a dynamic pointer that may be used during a
presentation. Although a mouse can be used as the pointer, this
payload format is not intended and may not have all functionalities
needed to implement a general mouse event transmission mechanism.
This document is a product of the Audio/Video Transport Working Group
of the IETF.
This is now a Proposed Standard Protocol.
This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol. Distribution
of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.