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


        RFC 2871

        Title:      A Framework for Telephony Routing over IP
        Author(s):  J. Rosenberg, H. Schulzrinne
        Status:     Informational
        Date:       June 2000
        Mailbox:    jdrosen@dynamicsoft.com,
                    schulzrinne@cs.columbia.edu 
        Pages:      25
        Characters: 60664
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-iptel-gwloc-framework-06.txt

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


This document serves as a framework for Telephony Routing over IP
(TRIP), which supports the discovery and exchange of IP telephony
gateway routing tables between providers. The document defines the
problem of telephony routing exchange, and motivates the need for the
protocol. It presents an architectural framework for TRIP, defines
terminology, specifies the various protocol elements and their
functions, overviews the services provided by the protocol, and
discusses how it fits into the broader context of Internet telephony.

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.