RFC relevance of extensions

As per Relevance of the word extensions, we have this rfc below:

Network Working Group S.
Request for Comments: 1877
Category: Informational December 1995

PPP Internet Protocol Control Protocol Extensions
Name Server

Status of this

This memo provides information for the Internet community. This
does not specify an Internet standard of any kind. Distribution
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 a family of
Control Protocols (NCPs) for establishing and configuring
network-layer protocols

This document extends the NCP for establishing and configuring
Internet Protocol over PPP [2], defining the negotiation of
and secondary Domain Name System (DNS) [3] and NetBIOS Name
(NBNS) [4] addresses

Table of

1. Additional IPCP Configuration options ................. 1
1.1 Primary DNS Server Address .................... 2
1.2 Primary NBNS Server Address ................... 3
1.3 Secondary DNS Server Address .................. 4
1.4 Secondary NBNS Server Address ................. 5
REFRENCES .................................................... 6
SECURITY CONSIDERATIONS ...................................... 6
CHAIR'S ADDRESS .............................................. 6
AUTHOR'S ADDRESS ............................................. 6

1. Additional IPCP Configuration

The four name server address configuration options, 129 to 132,
provide a method of obtaining the addresses of Domain Name
(DNS) servers and (NetBIOS Name Server (NBNS) nodes on the
network

Cobb Informational [Page 1]

RFC 1877 PPP IPCP Extensions December 1995

Primary and secondary addresses are negotiated independently.
serve identical purposes, except that when both are present
attempt SHOULD be made to resolve names using the primary
before using the secondary address

For implementational convenience, these options are designed to
identical in format and behavior to option 3 (IP-Address) which
already present in most IPCP implementations

Since the usefulness of name server address information is
on the topology of the remote network and local peer's application
it is suggested that these options not be included in the list
"IPCP Recommended Options".

1.1. Primary DNS Server

This Configuration Option defines a method for negotiating
the remote peer the address of the primary DNS server to be
on the local end of the link. If local peer requests an
server address (which it will typically do intentionally)
remote peer specifies the address by NAKing this option,
returning the IP address of a valid DNS server

By default, no primary DNS address is provided

A summary of the Primary DNS Address Configuration Option format
shown below. The fields are transmitted from left to right

0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Primary-DNS-
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Primary-DNS-Address (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

129

6

Cobb Informational [Page 2]

RFC 1877 PPP IPCP Extensions December 1995

Primary-DNS-

The four octet Primary-DNS-Address is the address of the
DNS server to be used by the local peer. If all four octets
set to zero, it indicates an explicit request that the
provide the address information in a Config-Nak packet

No address is provided

1.2. Primary NBNS Server

This Configuration Option defines a method for negotiating
the remote peer the address of the primary NBNS server to be
on the local end of the link. If local peer requests an
server address (which it will typically do intentionally)
remote peer specifies the address by NAKing this option,
returning the IP address of a valid NBNS server

By default, no primary NBNS address is provided

A summary of the Primary NBNS Address Configuration Option format
shown below. The fields are transmitted from left to right

0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Primary-NBNS-
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Primary-NBNS-Address (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

130

6

Primary-NBNS-

The four octet Primary-NBNS-Address is the address of the
NBNS server to be used by the local peer. If all four octets
set to zero, it indicates an explicit request that the

Cobb Informational [Page 3]

RFC 1877 PPP IPCP Extensions December 1995

provide the address information in a Config-Nak packet

No address is provided

1.3. Secondary DNS Server

This Configuration Option defines a method for negotiating
the remote peer the address of the secondary DNS server to be
on the local end of the link. If local peer requests an
server address (which it will typically do intentionally)
remote peer specifies the address by NAKing this option,
returning the IP address of a valid DNS server

By default, no secondary DNS address is provided

A summary of the Secondary DNS Address Configuration Option format
shown below. The fields are transmitted from left to right

0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Secondary-DNS-
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Secondary-DNS-Address (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

131

6

Secondary-DNS-

The four octet Secondary-DNS-Address is the address of the
NBNS server to be used by the local peer. If all four octets
set to zero, it indicates an explicit request that the
provide the address information in a Config-Nak packet

No address is provided

Cobb Informational [Page 4]

RFC 1877 PPP IPCP Extensions December 1995

1.4. Secondary NBNS Server

This Configuration Option defines a method for negotiating
the remote peer the address of the secondary NBNS server to
used on the local end of the link. If local peer requests
invalid server address (which it will typically do intentionally
the remote peer specifies the address by NAKing this option,
returning the IP address of a valid NBNS server

By default, no secondary NBNS address is provided

A summary of the Secondary NBNS Address Configuration Option
is shown below. The fields are transmitted from left to right

0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Secondary-NBNS-
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Secondary-NBNS-Address (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

132

6

Secondary-NBNS-

The four octet Secondary-NBNS-Address is the address of
secondary NBNS server to be used by the local peer. If
four octets are set to zero, it indicates an explicit
that the peer provide the address information in a Config-
packet

No address is provided

Cobb Informational [Page 5]

RFC 1877 PPP IPCP Extensions December 1995

[1] Simpson, W., Editor, "The Point-to-Point Protocol (PPP)", STD 51,
RFC 1661, Daydreamer, July 1994.

[2] McGregor, G., "PPP Internet Control Protocol", RFC 1332, Merit
May 1992.

[3] Auerbach, K., and A. Aggarwal, "Protocol Standard for a
Service on a TCP/UDP Transport", STD 19, RFCs 1001 and 1002,
March 1987.

[4] Mockapetris, P., "Domain Names - Concepts and Facilities",
13, RFC 1034, USC/Information Sciences Institute, November 1987.

[5] Mockapetris, P., "Domain Names - Implementation
Specification", STD 13, RFC 1035, USC/Information
Institute, November 1987.

Security

Security issues are not discussed in this memo

Chair's

The working group can be contacted via the current chair

Fred
Cisco
519 Lado
Santa Barbara, California 93111

EMail: fred@cisco.

Author's

Questions about this memo can also be directed to

Steve
Microsoft
One Microsoft
Redmond, WA 98052-6399

Phone: (206) 882-8080

EMail: stevec@microsoft.

Cobb Informational [Page 6]

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