H.323 Firewall Control Interface (HFCI)
draft-rfced-info-mercer-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Andrew Molitor | ||
| Last updated | 1998-12-23 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
It is becoming clear that next generation telephony networks will be built on top of IP-based networks, as opposed to the traditional voice technology. There are several reasons for this, among them lower cost and greater flexibility. While there are several Voice on IP (VoIP) solutions, the H.323 [2] standard from the ITU seems to be a major player. Other solutions will probably resemble H.323, even if they do not comply with the standard. This memo proposes an Application Interface to permit H.323 devices to open 'pinholes' in an otherwise opaque firewall, to permit the traffic necessary for H.323 through, and nothing else. Since other VoIP solutions resemble H.323, at least approximately, the same Application Interface may well be useful for them. In particular, Real-Time Protocol (RTP), defined in RFC1889 [3], is likely to be the underlying voice transport for any VoIP solution.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)