IP Network Address Translator Application Programming Interface
draft-ietf-nat-api-00
| Document | Type |
Expired Internet-Draft
(nat WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Pyda Srisuresh | ||
| Last updated | 1998-11-09 | ||
| 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
NAT provides routing transparency for hosts in disparate routing realms to communicate with each other. However, external agents such as Application Level Gateways (ALGs), Host-NAT-clients and Management applications need to interact with NAT and influence its operations. The document identifies the resources and other elements controlled by a NAT device, with specific focus on areas subject to influence from external agents. An Application Programming Interface (API) framework by which external agents could interact with NAT is presented. The intent of this document is to leverage the API specification as a base to identify requirements for the development of one or more protocols by which external agents could interact with NAT.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)