Pip Header Processing, May 1994
- Canonical URL:
- File formats:
- HISTORIC (changed from INFORMATIONAL May 2016)
- P. Francis
- pip (int)
Discuss this RFC: Send questions or comments to email@example.com
The purpose of this RFC and the companion RFC "Pip Near-term Architecture" are to record the ideas (good and bad) of Pip. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.