TRIP in action....
TRIP is
modeled after the IETF Border Gateway Protocol 4 (BGP-4) and is further enhanced
with some link state features, as in the Open Shortest Path First (OSPF) protocol.
TRIP uses BGP's inter-domain transport mechanism, BGP's peer communication,
BGP's finite state machine, and similar formats and attributes. Unlike BGP
however, TRIP permits generic intra-domain topologies, which simplifies configuration
and increases Salability in contrast to BGP's full mesh requirement of internal
BGP speakers. TRIP uses an intra-domain flooding mechanism similar to that
used in OSPF.
Note:
The links and documents found on this page refer to standards, proposals and draft standards. Whilst we endeavor to post the most recent versions, please refer to the IETF RFC's ITU SG16 and W3C for latest status
Related Standards, RFC's and Drafts (Click)
+44 (0) 8707 125100
Contact Form
The IETF TRIP standard was defined to address gateway location and routing problems for the selection of an egress gateway for a telephony call, traversing an IP network towards an ultimate destination in the PSTN. It is driven mainly by the policies of the various parties along the path, and by the relationships established between these parties. As such, a global directory of egress gateways in which users look up destination phone numbers is not a feasible solution. Rather, information about the availability of egress gateways is exchanged between providers, and subject to policy, made available locally and then propagated to other providers, thus creating routes towards these egress gateways.
