RFC 2824 on CPL-F

RFC Editor <rfc-ed@ISI.EDU> Wed, 31 May 2000 22:37 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26352; Wed, 31 May 2000 18:37:21 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id SAA18508 for ietf-123-outbound.10@ietf.org; Wed, 31 May 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 SAA18481 for <all-ietf@loki.ietf.org>; Wed, 31 May 2000 18:30:26 -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 SAA26231 for <all-ietf@ietf.org>; Wed, 31 May 2000 18:30:21 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id PAA26407; Wed, 31 May 2000 15:30:20 -0700 (PDT)
Message-Id: <200005312230.PAA26407@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2824 on CPL-F
Cc: rfc-ed@ISI.EDU, iptel@lists.research.bell-labs.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 31 May 2000 15:30:20 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2824

        Title:	    Call Processing Language Framework and
                    Requirements 
        Author(s):  J. Lennox, H. Schulzrinne 
        Status:     Informational
	Date:       May 2000
        Mailbox:    lennox@cs.columbia.edu,
                    schulzrinne@cs.columbia.edu 
        Pages:      25
        Characters: 58711
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-iptel-cpl-framework-02.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2824.txt


A large number of the services we wish to make possible for Internet
telephony require fairly elaborate combinations of signalling
operations, often in network devices, to complete. We want a simple
and standardized way to create such services to make them easier to
implement and deploy.  This document describes an architectural
framework for such a mechanism, which we call a call processing
language. It also outlines requirements for such a language.

This document is a product of the IP Telephony Working Group of the
IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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.
ftp://ftp.isi.edu/in-notes/rfc2824.txt"><ftp://ftp.isi.edu/in-notes/rfc2824.txt>