RFC 2974 on Session Announcement Protocol
RFC Editor <rfc-ed@ISI.EDU> Wed, 11 October 2000 20:08 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20497; Wed, 11 Oct 2000 16:08:28 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id QAA04477 for ietf-123-outbound.10@ietf.org; Wed, 11 Oct 2000 16:05: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 PAA04024 for <all-ietf@loki.ietf.org>; Wed, 11 Oct 2000 15:04:07 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA18573 for <all-ietf@ietf.org>; Wed, 11 Oct 2000 15:04:05 -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 MAA24414; Wed, 11 Oct 2000 12:03:53 -0700 (PDT)
Message-Id: <200010111903.MAA24414@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2974 on Session Announcement Protocol
Cc: rfc-ed@ISI.EDU, confctrl@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 11 Oct 2000 12:03:53 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2974 Title: Session Announcement Protocol Author(s): M. Handley, C. Perkins, E. Whelan Status: Experimental Date: October 2000 Mailbox: mjh@aciri.org, csp@ISI.EDU, e.whelan@cs.ucl.ac.uk Pages: 18 Characters: 40129 Updates/Obsoletes/SeeAlso: none I-D Tag: draft-ietf-mmusic-sap-v2-06.txt URL: ftp://ftp.isi.edu/in-notes/rfc2974.txt This document describes version 2 of the multicast session directory announcement protocol, Session Announcement Protocol (SAP), and the related issues affecting security and scalability that should be taken into account by implementors. This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. 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.
- RFC 2974 on Session Announcement Protocol RFC Editor