Pip Objects
draft-ietf-pip-objects-00
Document | Type |
Expired Internet-Draft
(pip WG)
Expired & archived
|
|
---|---|---|---|
Authors | |||
Last updated | 1992-10-30 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | thumper.bellcore.com%3A~/pub/tsuchiya/pip-archive | ||
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
Pip has a strong separation of packet syntax and semantics. Each Pip system determines its own syntax for the Handling Directive (HD) and Routing Context (RC) fields. While the syntax can be local, the semantics that the syntax represents must be globally unambiguous. This document 1) describes the syntax for globally unambiguous Pip HD and RC semantics, 2) a packet format for exchanging the mappings between semantics and HD and RC syntax, and 3) lists objects defined for Pip operation.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)