Browse Prior Art Database

Telephony Routing over IP (TRIP) (RFC3219)

IP.com Disclosure Number: IPCOM000006624D
Original Publication Date: 2002-Jan-01
Included in the Prior Art Database: 2002-Jan-17

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Rosenberg: AUTHOR [+3]

Abstract

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.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 2% of the total text.

Network Working Group                                       J. Rosenberg

Request for Comments: 3219                                   dynamicsoft

Category: Standards Track                                      H. Salama

                                                           Cisco Systems

                                                               M. Squire

                                                       Hatteras Networks

                                                            January 2002

                    Telephony Routing over IP (TRIP)

Status of this Memo

   This document specifies an Internet standards track protocol for the

   Internet community, and requests discussion and suggestions for

   improvements.  Please refer to the current edition of the "Internet

   Official Protocol Standards" (STD 1) for the standardization state

   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   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.

   The Border Gateway Protocol (BGP-4) is used to distribute routing

   information between administrative domains.  TRIP is used to

   distribute telephony routing information between telephony

   administrative domains.  The similarity between the two protocols is

   obvious, and hence TRIP is modeled after BGP-4.

Table of Contents

   1    Terminology and Definitions  ..............................   3

   2    Introduction  .............................................   4

   3    Summary of Operation  .....................................   5

   3.1  Peering Session Establishment and Maintenance  ............   5

   3.2  Database Exchanges  .......................................   6

   3.3  Internal Versus External Synchronization  .................   6

   3.4  Advertising TRIP Routes  ..................................   6

Rosenberg, et. al.          Standards Track                     [Page 1]

RFC 3219            Telephony Routing over IP (TRIP)        January 2002

   3.5  Telephony Routing Information Bases  ......................   7

   3.6  Routes in TRIP  ...........................................   9

   3.7  Aggregation  ..............................................   9

   4    Message Formats  ..........................................  10

   4.1  Message Header Format  ....................................  10

   4.2  OPEN Message Format  ......................................  11

   4.3  UPDATE Message Format  ....................................  15

   4.4  KEEPALIVE Message Format   ................................  22

   4.5  NOTIFICATION Message Format   .............................  23

   5    TRIP Attributes   .........................................  24

   5.1  WithdrawnRoutes  ..........................................  24

   5.2  ReachableRoutes  ..........................................  28

   5.3  NextHopServer   ...........................................  29

   5.4  AdvertisementPath   .......................................  31

   5.5  RoutedPath  ...............................................  35

   5.6  AtomicAggregate   .........................................  36

   5.7  LocalPreference   ........