Skip to main content

A Framework for a Peer Gatekeeper Routing Protocol
draft-ietf-iptel-pgrp-framework-00

Document Type Expired Internet-Draft (iptel WG)
Expired & archived
Author Ronald Davis
Last updated 1998-11-16
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

Within the ITU H.323 recommendation, the gatekeeper is a central point of communication for H.323 elements within a zone. All elements within the zone establish a communication channel with the gatekeeper over a registration, admission, and status (RAS) channel. Elements within a zone register with the gatekeeper and are subsequently able to communicate with other elements in the zone, or outside of the zone. What is needed in addition to the normal registration and connection admission procedures of H.323 is a means of acquiring information about elements in other zones. This document describes the framework for a peer gatekeeper routing protocol (pgrp) which allows gatekeepers to exchange information with other gatekeepers about elements in their respective zones. PGRP is a protocol supports the exchange of information among gatekeepers which may be used to make call routing decisions in a network. PGRP attempts to extend reliability concepts from telecommunications by incorporating maintenance state information exchange. This allows call routing decisions to be based upon the operational state of elements in the network. This feature is particularly useful in the H.323 gatekeeper mediated call model where a call may be completed to a pool of connection endpoints. An example of such a scenario is in the use of an H.323 to connect telecom end offices which connect to multiple H.323 gateways. In this context, pgrp is also able to support call distribution to balance the call load among the connection gateways serving an end office.

Authors

Ronald Davis

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)