Network Working Group P. Tsuchiya INTERNET-DRAFT Bellcore November 1992 Pip Objects Status of this Memo This document is an Internet Draft. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups.
Download free video effects, photo presets. PiP Objects Titles. Overlay PiP 178 442. Top free pip objects downloads. IOrgsoft Video Editor for Mac helps you turn your home video into something extraordinary with minimal effort. Crazy Objects is a.
Note that other groups may also distribute working documents as Internet Drafts). Internet Drafts are draft documents valid for a maximum of six months.
Internet Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet Drafts as reference material or to cite them other than as a 'working draft' or 'work in progress.' Please check the I-D abstract listing contained in each Internet Draft directory to learn the current status of this or any other Internet Draft. 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. Acknowledgements Pip WG, Expires May. 1, 1993 [Page 1] INTERNET-DRAFT Pip Objects November 1992. Introduction 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. There are many different kinds of semantics that can be encoded in the HD or RC. Examples of such semantics are 'low cost route', 'low delay queueing', 'route along first alternate path', and 'multicast address'.
When one Pip system transmits a Pip packet to another Pip system, it must translate the HD and RC from its own syntax to that of the receiving Pip system. To do this, the Pip system must know how the receiving system is interpreting the HD and RC. The common means of knowing this is to exchange configuration information. To do this, there must be a means of unambiguously conveying semantic meaning between Pip systems. This document defines how semantic meaning is conveyed by Pip systems. This document is also the repository for better-known Pip semantics..
Pip Objects The Pip Object is the basic unit for identifying a Pip semantic mean- ing. Window Xp Vista Theme. Pip Objects have names and descriptors (Pip Object Names, PON, and Pip Object Descriptors, POD). A PON is a globally unique number 8 octets in length. A POD is a string of characters of any length. PODs need not be globally unique.
The first octet of the PON is the PON Type. If the first octet is value 1, then the next 4 octets are an IP address, followed by a 3 octet Pip Object number. If the first octet is value 2, then the next 6 octets is an IEEE 802 address followed by a 1 octet Pip Object number. The purpose of the IP or IEEE 802 address is to define an authority for the subsequent Pip Object number for the purposes of insuring that every Pip Object has a unique PON. This allows virtually any- body to create and name a Pip Object. Note that PONs have no rela- tion what-so-ever to the IP or IEEE 802 address they contain.
Comments are closed.