As per Relevance of the word implementation, we have this rfc below:
Network Working Group S.
Request for Comments: 1763
Category: Standards Track March 1995
The PPP Banyan Vines Control Protocol (BVCP
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 Banyan VINES protocol over PPP
Table of
1. Introduction .......................................... 2
1.1 Specification of Requirements ................... 2
1.2 Terminology ..................................... 3
2. A PPP Network Control Protocol for VINES .............. 3
2.1 Sending VINES Datagrams ......................... 4
2.2 General Considerations .......................... 4
3. BVCP Configuration Options ............................ 5
3.1 BV-NS-RTP-Link-Type ............................. 5
3.2 BV-FRP .......................................... 6
3.3 BV-RTP .......................................... 7
3.4 BV-Suppress-Broadcast ........................... 8
SECURITY CONSIDERATIONS ...................................... 9
REFERENCES ................................................... 9
ACKNOWLEDGEMENTS .......................................... 9
CHAIR'S ADDRESS .............................................. 10
AUTHOR'S ADDRESS ............................................. 10
Senum [Page 1]
RFC 1763 PPP BVCP 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
BVCP packets to choose and configure the VINES network-
protocol. Once BVCP has reached the Opened state, VINES
can be sent over the link
The link will remain configured for communications until explicit
or BVCP 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 1763 PPP BVCP 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
The Banyan VINES Control Protocol (BVCP) is responsible
configuring, enabling, and disabling the VINES protocol modules
both ends of the point-to-point link. BVCP uses the same
exchange mechanism as the Link Control Protocol. BVCP packets
not be exchanged until PPP has reached the Network-Layer
phase. BVCP packets received before this phase is reached should
silently discarded
The Baynan VINES Control Protocol is exactly the same as the
Control 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 1763 PPP BVCP March 1995
Data Link Layer Protocol
Exactly one BVCP packet is encapsulated in the Information
of a PPP Data Link Layer frame where the Protocol field
type hex 8035 (Banyan VINES 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
BVCP 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
BVCP has a distinct set of Configuration Options
2.1. Sending VINES
Before any VINES datagrams may be communicated, PPP must reach
Network-Layer Protocol phase, and the Banyan VINES Control
must reach the Opened state
Exactly one VINES packet is encapsulated in the Information field
a PPP Data Link Layer frame where the Protocol field indicates
hex 0035 (Banyan VINES datagram). The maximum length of a
datagram transmitted over a PPP link is the same as the
length of the Information field of a PPP data link layer frame
The format of the Information field itself is the same as
defined in [2].
2.2. General
VINES supports an Address Resolution Protocol, VINES ARP,
used for address assignment. Since this protocol is part of
IP, it is fully supported over BVCP. VINES also supports a data-
Echo Protocol (VINES Echo), used to test connectivity to a
Server in a LAN environment, which is not supported over BVCP
Senum [Page 4]
RFC 1763 PPP BVCP March 1995
3. BVCP Configuration
BVCP Configuration Options allow modifications to the
characteristics of the network-layer protocol to be negotiated. If
Configuration Option is not included in a Configure-Request packet
the default value for that Configuration Option is assumed
BVCP uses the same Configuration Option format defined for LCP [1],
with a separate set of Options
Up-to-date values of the BVCP Option Type field are specified in
most recent "Assigned Numbers" RFC [3]. Current values are
as follows
Value
1 BV-NS-RTP-Link-
2 BV-
3 BV-
4 BV-Suppress-
Note: A suggestion was made to combine the BV-NS-RTP-Link-Type
and the BV-RTP option into a single option that could negotiate
of four settings (S-RTP, NS-RTP-LAN, NS-RTP-WAN, NO-RTP).
suggestion has been rejected because VINES must already deal with
mix of S-RTP and NS-RTP, and that pushing this information down
the PPP layer is not desirable
3.1. BV-NS-RTP-Link-
This Configuration Option provides a way to negotiate the way
Non-Sequenced Routing Update Protocol (NS-RTP) (pre-VINES 5.5,
i.e., 4.11 and 5.0) will run on the link. NS-RTP handles
differently depending on whether the interface is a LAN type or
WAN type. For a LAN type, the full routing table is
every update interval (90 seconds). For a WAN type, the
routing table is only transmitted for the first 3 update
after the link comes up. After that only changes are
(for 5 update intervals). Note that this has no effect
Sequenced RTP (VINES 5.5) is being used. More information on
can be found in [2].
This option negotiates what an implementation is willing
receive, and is negotiated separately per side of the
connection. The acceptance of this option (by the peer)
that the peer will send NS-RTP updates as if the link was a
Senum [Page 5]
RFC 1763 PPP BVCP March 1995
type. The rejection (or absence) of this option indicates
the peer will send NS-RTP updates as if the link was a WAN type
By default, NS-RTP updates are sent as if the link was a WAN type
A summary of the BV-NS-RTP-Link-Type Configuration Option format
shown below. The fields are transmitted from left to right
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1
2
3.2. BV-
This Configuration Option provides a way to negotiate the use
VINES Fragmentation Protocol (FRP). This protocol is used
allow fragmentation and reassembly of a VINES packet over
link. FRP prepends a two octet field to every packet going
the link that contains a begin and end fragment information and
sequence number. With PPP's default MRU of 1500, FRP is
normally needed, and no FRP header would be sent with the
packet. If a MRU of less than 1484 is negotiated, FRP will
needed to send a full size VINES packet over the link.
information on this can be found in [2].
This option negotiates what an implementation is willing
receive, and is negotiated separately per side of the
connection. The acceptance of this option (by the peer)
that the peer will send VINES packets with a FRP header.
rejection (or absence) of this option indicates that the peer
send VINES packets without a FRP header
By default, VINES packets are sent without a FRP header
Senum [Page 6]
RFC 1763 PPP BVCP March 1995
A summary of the BV-FRP Configuration Option format is shown below
The fields are transmitted from left to right
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2
2
3.3. BV-
This Configuration Option provides a way to negotiate whether
is used over the link. If dial-up lines with static routes
being used, the use of RTP may be totally suppressed to
bandwidth on the link
This option negotiates what an implementation is willing
receive, and is negotiated separately per side of the
connection. The acceptance of this option (by the peer)
that the peer will not send RTP packets. The rejection (
absence) of this option indicates that the peer will send any
packets
By default, RTP packets are sent over the link
Senum [Page 7]
RFC 1763 PPP BVCP March 1995
A summary of the BV-RTP Configuration Option format is shown below
The fields are transmitted from left to right
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3
2
3.4. BV-Suppress-
This Configuration Option provides a way to negotiate the
of VINES broadcast packets, i.e., packets with a destination
network address of all ones. This option only affects
packets that are not of type VINES ARP or VINES RTP. This
can be used by a VINES Client to request that most of
broadcast packets that would normally be sent to it by a
Server be discarded, in order to conserve link bandwidth. Most
the broadcast packets sent by a VINES Server are not useful to
VINES Client
This option negotiates what an implementation is willing
receive, and is negotiated separately per side of the
connection. The acceptance of this option (by the peer)
that the peer MUST NOT send any VINES broadcast packets,
than packets of type VINES ARP or VINES RTP. The rejection (
absence) of this option indicates that the peer will send
VINES broadcast packets
By default, all VINES broadcast packets are sent
Senum [Page 8]
RFC 1763 PPP BVCP March 1995
A summary of the BV-Suppress-Broadcast Configuration Option format
shown below. The fields are transmitted from left to right
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4
2
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] Banyan, "VINES Protocol Definition", June 1993, Order No
003673.
[3] Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, RFC 1700,
USC/Information Sciences Institute, October 1994.
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
Senum [Page 9]
RFC 1763 PPP BVCP March 1995
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 10]
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
