RFC 3219 (rfc3219) - Page 3 of 79


Telephony Routing over IP (TRIP)



Alternative Format: Original Text Document



RFC 3219            Telephony Routing over IP (TRIP)        January 2002


   14    Security Considerations   ................................. 70
   A1    Appendix 1: TRIP FSM State Transitions and Actions   ...... 71
   A2    Appendix 2: Implementation Recommendations   .............. 73
   Acknowledgments  ................................................ 75
   References  ..................................................... 75
   Intellectual Property Notice  ................................... 77
   Authors' Addresses  ............................................. 78
   Full Copyright Statement  ....................................... 79

1. Terminology and Definitions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [1].

   A framework for Telephony Routing over IP (TRIP) is described in [2].
   We assume the reader is familiar with the framework and terminology
   of [2].  We define and use the following terms in addition to those
   defined in [2].

   Telephony Routing Information Base (TRIB): The database of reachable
   telephony destinations built and maintained at an LS as a result of
   its participation in TRIP.

   IP Telephony Administrative Domain (ITAD): The set of resources
   (gateways, location servers, etc.) under the control of a single
   administrative authority.  End users are customers of an ITAD.

   Less/More Specific Route: A route X is said to be less specific than
   a route Y if every destination in Y is also a destination in X, and X
   and Y are not equal.  In this case, Y is also said to be more
   specific than X.

   Aggregation: Aggregation is the process by which multiple routes are
   combined into a single less specific route that covers the same set
   of destinations.  Aggregation is used to reduce the size of the TRIB
   being synchronized with peer LSs by reducing the number of exported
   TRIP routes.

   Peers: Two LSs that share a logical association (a transport
   connection).  If the LSs are in the same ITAD, they are internal
   peers.  Otherwise, they are external peers.  The logical association
   between two peer LSs is called a peering session.








Rosenberg, et. al.          Standards Track