RFC 3219: Telephony Routing over IP (TRIP)
In plain English — editorial summary, not part of the RFC
This document presents the Telephony Routing over IP (TRIP). TRIP is a policy driven inter-administrative domain protocol for advertising the reachability of telephony destinations between location servers, and for advertising attributes of the routes to those destinations. TRIP's operation is independent of any signaling protocol, hence TRIP can serve as the telephony routing protocol for any signaling protocol. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3219
- Published
- January 2002
- Authors
- J. Rosenberg; H. Salama; M. Squire
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 79
- Also known as
- —
- Updated by:
- RFC 8602
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3872Management Information Base for Telephony Routing over IP (TRIP)Current
September 2004
- RFC 5140A Telephony Gateway REgistration Protocol (TGREP)Current
March 2008
- RFC 3107Carrying Label Information in BGP-4Obsoleted
May 2001
- RFC 3392Capabilities Advertisement with BGP-4Obsoleted
November 2002
- RFC 2918Route Refresh Capability for BGP-4Updated
September 2000
- RFC 3562Key Management Considerations for the TCP MD5 Signature OptionCurrent
July 2003
- RFC 2796BGP Route Reflection - An Alternative to Full Mesh IBGPObsoleted
April 2000
- RFC 2439BGP Route Flap DampingCurrent
November 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?