Packet Filter Configuration Protocol
draft-paddon-pfcp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Michael Paddon , Philip Hawkes | ||
| Last updated | 2005-12-12 | ||
| 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
The Packet Filter Configuration Protocol (PFCP) is a client-server protocol which provides a mechanism for trusted clients to dynamically request updates to a packet filtering policy managed by a server. Typically, a server is either a packet filter or an entity which controls one or more packet filters. Since clients may specify permitted flows as and when they are required, packet filters configured via PFCP may operate an extremely restrictive default policy.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)