Current Meeting Report
Slides


2.8.6 IP Telephony (iptel)

In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

       http://www.bell-labs.com/mailing-lists/iptel/ -- Additional IPTEL Page
NOTE: This charter is a snapshot of the 54th IETF Meeting in Yokohama, Japan. It may now be out-of-date.

Last Modifield: 05/30/2002

Chair(s):
J. Rosenberg <jdrosen@dynamicsoft.com>
Transport Area Director(s):
Scott Bradner <sob@harvard.edu>
A. Mankin <mankin@isi.edu>
Transport Area Advisor:
Scott Bradner <sob@harvard.edu>
Mailing Lists:
General Discussion: iptel@lists.bell-labs.com
To Subscribe: iptel-request@lists.bell-labs.com
Archive: http://www.bell-labs.com/mailing-lists/iptel
Description of Working Group:
The focus of the IP Telephony (iptel) group is on the problems related to propagation of routing information for VoIP protocols. Specifically, both SIP and H.323 have the notion of signaling intermediaries (proxies in SIP and gatekeepers in H.323). When these devices receive call establishment messages, they must make a routing decision on where to forward the call setup messages.

The iptel group has already defined a protocol, Telephony Routing over IP (TRIP), which solves one aspect of this problem. Specifically, it handles the case where calls need to be routed between domains. It allows for the exchange of routing information between these providers, so that policies can be applied to the resulting data to create a forwarding information base.

However, this protocol does not address all the scenarios of route information exchange between servers. One important scenario is the propagation of routing information between gateways and the signaling servers in front of them. This is also known as "gateway registration". It allows the signaling server to make a routing decision about which gateway to use based on dynamic information about the gateway resources. Vendors have deployed proprietary solutions for this communications interface. A standard is needed. The group will generate a standards track document that defines a protocol (possibly based on TRIP) for this interface.

The group will also generate a MIB document for TRIP.

Note that the group is not working on elevating TRIP to Draft Standard at this time.

Deliverables:

1. A proposed standard RFC for gateway to server route exchange.

2. A proposed standard TRIP MIB specification, based heavily on the existing BGP-4 MIB documents.

Goals and Milestones:
Done  Submit gateway location framework document to IESG for consideration as an RFC.
Done  Submit call processing syntax framework document to IESG for consideration as an RFC.
Done  Submit call processing syntax document to IESG for consideration as a Proposed Standard.
Done  Submit gateway location protocol document to IESG for consideration as an RFC.
Done  TRIP MIB Document submitted to IESG for consideration as proposed standard
MAR 02  Gateway to Server Route Exchange document submitted to IESG for consideration as proposed standard.
Internet-Drafts:
  • - draft-ietf-iptel-cpl-06.txt
  • - draft-ietf-iptel-trip-mib-03.txt
  • - draft-ietf-iptel-trip-gw-00.txt
    • Request For Comments:
    RFCStatusTitle
    RFC2824 I Call Processing Language Framework and Requirements
    RFC2871 I A Framework for a Gateway Location Protocol
    RFC3219 PS Telephony Routing over IP (TRIP)

    Current Meeting Report

    None received.

    Slides

    None received.