As per Relevance of the word implementation, we have this rfc below:
Network Working Group S.
Request for Comments: 1764
Category: Standards Track March 1995
The PPP XNS IDP Control Protocol (XNSCP
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
The Point-to-Point Protocol (PPP) [1] provides a standard method
transporting multi-protocol datagrams over point-to-point links.
defines an extensible Link Control Protocol, and proposes a family
Network Control Protocols for establishing and configuring
network-layer protocols
This document defines the Network Control Protocol for
and configuring the Xerox Network Systems (XNS) Internet
Protocol (IDP) over PPP
Table of
1. Introduction .......................................... 2
1.1 Specification of Requirements ................... 2
1.2 Terminology ..................................... 3
2. A PPP Network Control Protocol for XNS IDP ............ 3
2.1 Sending XNS IDP Datagrams ....................... 4
SECURITY CONSIDERATIONS ...................................... 5
REFERENCES ................................................... 5
ACKNOWLEDGEMENTS .......................................... 5
CHAIR'S ADDRESS .............................................. 5
AUTHOR'S ADDRESS ............................................. 5
Senum [Page 1]
RFC 1764 PPP XNSCP March 1995
1.
PPP has three main components
1. A method for encapsulating multi-protocol datagrams
2. A Link Control Protocol (LCP) for establishing, configuring
and testing the data-link connection
3. A family of Network Control Protocols for establishing
configuring different network-layer protocols
In order to establish communications over a point-to-point link,
end of the PPP link must first send LCP packets to configure and
the data link. After the link has been established and
facilities have been negotiated as needed by the LCP, PPP must
XNSCP packets to choose and configure the XNS IDP network-
protocol. Once XNSCP has reached the Opened state, XNS IDP
can be sent over the link
The link will remain configured for communications until explicit
or XNSCP packets close the link down, or until some external
occurs (an inactivity timer expires or network
intervention).
1.1. Specification of
In this document, several words are used to signify the
of the specification. These words are often capitalized
MUST This word, or the adjective "required", means that
definition is an absolute requirement of the specification
MUST NOT This phrase means that the definition is an
prohibition of the specification
SHOULD This word, or the adjective "recommended", means that
may exist valid reasons in particular circumstances
ignore this item, but the full implications must
understood and carefully weighed before choosing
different course
MAY This word, or the adjective "optional", means that
item is one of an allowed set of alternatives.
implementation which does not include this option MUST
prepared to interoperate with another implementation
does include the option
Senum [Page 2]
RFC 1764 PPP XNSCP March 1995
1.2.
This document frequently uses the following terms
datagram The unit of transmission in the network layer (such as IP).
A datagram may be encapsulated in one or more
passed to the data link layer
frame The unit of transmission at the data link layer. A
may include a header and/or a trailer, along with
number of units of data
packet The basic unit of encapsulation, which is passed across
interface between the network layer and the data
layer. A packet is usually mapped to a frame;
exceptions are when data link layer fragmentation is
performed, or when multiple packets are incorporated into
single frame
peer The other end of the point-to-point link
silently
This means the implementation discards the packet
further processing. The implementation SHOULD provide
capability of logging the error, including the contents
the silently discarded packet, and SHOULD record the
in a statistics counter
2. A PPP Network Control Protocol for XNS
The XNS IDP Control Protocol (XNSCP) is responsible for configuring
enabling, and disabling the XNS IDP protocol modules on both ends
the point-to-point link. XNSCP uses the same packet
mechanism as the Link Control Protocol (LCP). XNSCP packets may
be exchanged until PPP has reached the Network-Layer Protocol phase
XNSCP packets received before this phase is reached should
silently discarded
The XNS IDP Control Protocol is exactly the same as the Link
Protocol [1] with the following exceptions
Frame
The packet may utilize any modifications to the basic frame
which have been negotiated during the Link Establishment phase
Senum [Page 3]
RFC 1764 PPP XNSCP March 1995
Data Link Layer Protocol
Exactly one XNSCP packet is encapsulated in the Information
of a PPP Data Link Layer frame, where the PPP Protocol
indicates type hex 8025 (XNS IDP Control Protocol).
Code
Only Codes 1 through 7 (Configure-Request, Configure-Ack
Configure-Nak, Configure-Reject, Terminate-Request, Terminate-
and Code-Reject) are used. Other Codes should be treated
unrecognized and should result in Code-Rejects
XNSCP packets may not be exchanged until PPP has reached
Network-Layer Protocol phase. An implementation should
prepared to wait for Authentication and Link Quality
to finish before timing out waiting for a Configure-Ack or
response. It is suggested that an implementation give up
after user intervention or a configurable amount of time
Configuration Option
XNSCP has no Configuration Options
2.1. Sending XNS IDP
Before any XNS IDP packets may be communicated, PPP must reach
Network-Layer Protocol phase, and the XNS IDP Control Protocol
reach the Opened state
Exactly one XNS IDP packet is encapsulated in the Information
of a PPP Data Link Layer frame where the Protocol field
type hex 0025 (XNS IDP datagram).
The maximum length of a XNS IDP datagram transmitted over a PPP
is the same as the maximum length of the Information field of a
data link layer frame. Since there is no standard method
fragmenting and reassembling XNS IDP datagrams, PPP links
XNS IDP MUST allow at least 576 octets in the information field of
data link layer frame
The format of the Information field itself is the same as
defined in [2].
Senum [Page 4]
RFC 1764 PPP XNSCP March 1995
Security
Security issues are not discussed in this memo
[1] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51,
1661, Daydreamer, July 1994.
[2] Xerox, "Internet Transport Protocols", January 1991, Order No
XNSS 029101.
Some of the text in this document is taken from previous
produced by the Point-to-Point Protocol Working Group of the
Engineering Task Force (IETF).
In particular, Bill Simpson provided the boiler-plate used to
this document
Chair's
The working group can be contacted via the current chair
Fred
Cisco
519 Lado
Santa Barbara, California 93111
Phone: (805) 681-0115
EMail: fred@cisco.
Author's
Questions about this memo can also be directed to
Steven J.
6400 Flying Cloud
Eden Prairie, Minnesota 55344
Phone: (612) 943-9020
EMail: sjs@digibd.
Senum [Page 5]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
