| 1 |
<pre>Network Working Group S. Cobb |
| 2 |
Request for Comments: 1877 Microsoft |
| 3 |
Category: Informational December 1995 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">PPP Internet Protocol Control Protocol Extensions for</span> |
| 7 |
<span class="h1">Name Server Addresses</span> |
| 8 |
|
| 9 |
Status of this Memo |
| 10 |
|
| 11 |
This memo provides information for the Internet community. This memo |
| 12 |
does not specify an Internet standard of any kind. Distribution of |
| 13 |
this memo is unlimited. |
| 14 |
|
| 15 |
Abstract |
| 16 |
|
| 17 |
The Point-to-Point Protocol (PPP) [<a href="#ref-1" title=""The Point-to-Point Protocol (PPP)"">1</a>] provides a standard method for |
| 18 |
transporting multi-protocol datagrams over point-to-point links. PPP |
| 19 |
defines an extensible Link Control Protocol and a family of Network |
| 20 |
Control Protocols (NCPs) for establishing and configuring different |
| 21 |
network-layer protocols. |
| 22 |
|
| 23 |
This document extends the NCP for establishing and configuring the |
| 24 |
Internet Protocol over PPP [<a href="#ref-2" title=""PPP Internet Control Protocol"">2</a>], defining the negotiation of primary |
| 25 |
and secondary Domain Name System (DNS) [<a href="#ref-3" title=""Protocol Standard for a NetBIOS Service on a TCP/UDP Transport"">3</a>] and NetBIOS Name Server |
| 26 |
(NBNS) [<a href="#ref-4" title=""Domain Names - Concepts and Facilities"">4</a>] addresses. |
| 27 |
|
| 28 |
Table of Contents |
| 29 |
|
| 30 |
<a href="#section-1">1</a>. Additional IPCP Configuration options ................. <a href="#page-1">1</a> |
| 31 |
<a href="#section-1.1">1.1</a> Primary DNS Server Address .................... <a href="#page-2">2</a> |
| 32 |
<a href="#section-1.2">1.2</a> Primary NBNS Server Address ................... <a href="#page-3">3</a> |
| 33 |
<a href="#section-1.3">1.3</a> Secondary DNS Server Address .................. <a href="#page-4">4</a> |
| 34 |
<a href="#section-1.4">1.4</a> Secondary NBNS Server Address ................. <a href="#page-5">5</a> |
| 35 |
REFRENCES .................................................... <a href="#page-6">6</a> |
| 36 |
SECURITY CONSIDERATIONS ...................................... <a href="#page-6">6</a> |
| 37 |
CHAIR'S ADDRESS .............................................. <a href="#page-6">6</a> |
| 38 |
AUTHOR'S ADDRESS ............................................. <a href="#page-6">6</a> |
| 39 |
|
| 40 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Additional IPCP Configuration Options</span> |
| 41 |
|
| 42 |
The four name server address configuration options, 129 to 132, |
| 43 |
provide a method of obtaining the addresses of Domain Name System |
| 44 |
(DNS) servers and (NetBIOS Name Server (NBNS) nodes on the remote |
| 45 |
network. |
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Cobb Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1877">RFC 1877</a> PPP IPCP Extensions December 1995</span> |
| 55 |
|
| 56 |
|
| 57 |
Primary and secondary addresses are negotiated independently. They |
| 58 |
serve identical purposes, except that when both are present an |
| 59 |
attempt SHOULD be made to resolve names using the primary address |
| 60 |
before using the secondary address. |
| 61 |
|
| 62 |
For implementational convenience, these options are designed to be |
| 63 |
identical in format and behavior to option 3 (IP-Address) which is |
| 64 |
already present in most IPCP implementations. |
| 65 |
|
| 66 |
Since the usefulness of name server address information is dependent |
| 67 |
on the topology of the remote network and local peer's application, |
| 68 |
it is suggested that these options not be included in the list of |
| 69 |
"IPCP Recommended Options". |
| 70 |
|
| 71 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Primary DNS Server Address</span> |
| 72 |
|
| 73 |
Description |
| 74 |
|
| 75 |
This Configuration Option defines a method for negotiating with |
| 76 |
the remote peer the address of the primary DNS server to be used |
| 77 |
on the local end of the link. If local peer requests an invalid |
| 78 |
server address (which it will typically do intentionally) the |
| 79 |
remote peer specifies the address by NAKing this option, and |
| 80 |
returning the IP address of a valid DNS server. |
| 81 |
|
| 82 |
By default, no primary DNS address is provided. |
| 83 |
|
| 84 |
A summary of the Primary DNS Address Configuration Option format is |
| 85 |
shown below. The fields are transmitted from left to right. |
| 86 |
|
| 87 |
0 1 2 3 |
| 88 |
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 |
| 89 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 90 |
| Type | Length | Primary-DNS-Address |
| 91 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 92 |
Primary-DNS-Address (cont) | |
| 93 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 94 |
|
| 95 |
Type |
| 96 |
|
| 97 |
129 |
| 98 |
|
| 99 |
Length |
| 100 |
|
| 101 |
6 |
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Cobb Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1877">RFC 1877</a> PPP IPCP Extensions December 1995</span> |
| 111 |
|
| 112 |
|
| 113 |
Primary-DNS-Address |
| 114 |
|
| 115 |
The four octet Primary-DNS-Address is the address of the primary |
| 116 |
DNS server to be used by the local peer. If all four octets are |
| 117 |
set to zero, it indicates an explicit request that the peer |
| 118 |
provide the address information in a Config-Nak packet. |
| 119 |
|
| 120 |
Default |
| 121 |
|
| 122 |
No address is provided. |
| 123 |
|
| 124 |
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Primary NBNS Server Address</span> |
| 125 |
|
| 126 |
Description |
| 127 |
|
| 128 |
This Configuration Option defines a method for negotiating with |
| 129 |
the remote peer the address of the primary NBNS server to be used |
| 130 |
on the local end of the link. If local peer requests an invalid |
| 131 |
server address (which it will typically do intentionally) the |
| 132 |
remote peer specifies the address by NAKing this option, and |
| 133 |
returning the IP address of a valid NBNS server. |
| 134 |
|
| 135 |
By default, no primary NBNS address is provided. |
| 136 |
|
| 137 |
A summary of the Primary NBNS Address Configuration Option format is |
| 138 |
shown below. The fields are transmitted from left to right. |
| 139 |
|
| 140 |
0 1 2 3 |
| 141 |
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 |
| 142 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 143 |
| Type | Length | Primary-NBNS-Address |
| 144 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 145 |
Primary-NBNS-Address (cont) | |
| 146 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 147 |
|
| 148 |
Type |
| 149 |
|
| 150 |
130 |
| 151 |
|
| 152 |
Length |
| 153 |
|
| 154 |
6 |
| 155 |
|
| 156 |
Primary-NBNS-Address |
| 157 |
|
| 158 |
The four octet Primary-NBNS-Address is the address of the primary |
| 159 |
NBNS server to be used by the local peer. If all four octets are |
| 160 |
set to zero, it indicates an explicit request that the peer |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Cobb Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1877">RFC 1877</a> PPP IPCP Extensions December 1995</span> |
| 167 |
|
| 168 |
|
| 169 |
provide the address information in a Config-Nak packet. |
| 170 |
|
| 171 |
Default |
| 172 |
|
| 173 |
No address is provided. |
| 174 |
|
| 175 |
<span class="h3"><a class="selflink" id="section-1.3" href="#section-1.3">1.3</a>. Secondary DNS Server Address</span> |
| 176 |
|
| 177 |
Description |
| 178 |
|
| 179 |
This Configuration Option defines a method for negotiating with |
| 180 |
the remote peer the address of the secondary DNS server to be used |
| 181 |
on the local end of the link. If local peer requests an invalid |
| 182 |
server address (which it will typically do intentionally) the |
| 183 |
remote peer specifies the address by NAKing this option, and |
| 184 |
returning the IP address of a valid DNS server. |
| 185 |
|
| 186 |
By default, no secondary DNS address is provided. |
| 187 |
|
| 188 |
A summary of the Secondary DNS Address Configuration Option format is |
| 189 |
shown below. The fields are transmitted from left to right. |
| 190 |
|
| 191 |
0 1 2 3 |
| 192 |
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 |
| 193 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 194 |
| Type | Length | Secondary-DNS-Address |
| 195 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 196 |
Secondary-DNS-Address (cont) | |
| 197 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 198 |
|
| 199 |
Type |
| 200 |
|
| 201 |
131 |
| 202 |
|
| 203 |
Length |
| 204 |
|
| 205 |
6 |
| 206 |
|
| 207 |
Secondary-DNS-Address |
| 208 |
|
| 209 |
The four octet Secondary-DNS-Address is the address of the primary |
| 210 |
NBNS server to be used by the local peer. If all four octets are |
| 211 |
set to zero, it indicates an explicit request that the peer |
| 212 |
provide the address information in a Config-Nak packet. |
| 213 |
|
| 214 |
Default |
| 215 |
|
| 216 |
No address is provided. |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Cobb Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1877">RFC 1877</a> PPP IPCP Extensions December 1995</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h3"><a class="selflink" id="section-1.4" href="#section-1.4">1.4</a>. Secondary NBNS Server Address</span> |
| 226 |
|
| 227 |
Description |
| 228 |
|
| 229 |
This Configuration Option defines a method for negotiating with |
| 230 |
the remote peer the address of the secondary NBNS server to be |
| 231 |
used on the local end of the link. If local peer requests an |
| 232 |
invalid server address (which it will typically do intentionally) |
| 233 |
the remote peer specifies the address by NAKing this option, and |
| 234 |
returning the IP address of a valid NBNS server. |
| 235 |
|
| 236 |
By default, no secondary NBNS address is provided. |
| 237 |
|
| 238 |
A summary of the Secondary NBNS Address Configuration Option format |
| 239 |
is shown below. The fields are transmitted from left to right. |
| 240 |
|
| 241 |
0 1 2 3 |
| 242 |
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 |
| 243 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 244 |
| Type | Length | Secondary-NBNS-Address |
| 245 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 246 |
Secondary-NBNS-Address (cont) | |
| 247 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 248 |
|
| 249 |
Type |
| 250 |
|
| 251 |
132 |
| 252 |
|
| 253 |
Length |
| 254 |
|
| 255 |
6 |
| 256 |
|
| 257 |
Secondary-NBNS-Address |
| 258 |
|
| 259 |
The four octet Secondary-NBNS-Address is the address of the |
| 260 |
secondary NBNS server to be used by the local peer. If all |
| 261 |
four octets are set to zero, it indicates an explicit request |
| 262 |
that the peer provide the address information in a Config-Nak |
| 263 |
packet. |
| 264 |
|
| 265 |
Default |
| 266 |
|
| 267 |
No address is provided. |
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Cobb Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1877">RFC 1877</a> PPP IPCP Extensions December 1995</span> |
| 279 |
|
| 280 |
|
| 281 |
References |
| 282 |
|
| 283 |
[<a id="ref-1">1</a>] Simpson, W., Editor, "The Point-to-Point Protocol (PPP)", STD 51, |
| 284 |
<a href="./rfc1661">RFC 1661</a>, Daydreamer, July 1994. |
| 285 |
|
| 286 |
[<a id="ref-2">2</a>] McGregor, G., "PPP Internet Control Protocol", <a href="./rfc1332">RFC 1332</a>, Merit, |
| 287 |
May 1992. |
| 288 |
|
| 289 |
[<a id="ref-3">3</a>] Auerbach, K., and A. Aggarwal, "Protocol Standard for a NetBIOS |
| 290 |
Service on a TCP/UDP Transport", STD 19, RFCs 1001 and 1002, |
| 291 |
March 1987. |
| 292 |
|
| 293 |
[<a id="ref-4">4</a>] Mockapetris, P., "Domain Names - Concepts and Facilities", STD |
| 294 |
13, <a href="./rfc1034">RFC 1034</a>, USC/Information Sciences Institute, November 1987. |
| 295 |
|
| 296 |
[<a id="ref-5">5</a>] Mockapetris, P., "Domain Names - Implementation and |
| 297 |
Specification", STD 13, <a href="./rfc1035">RFC 1035</a>, USC/Information Sciences |
| 298 |
Institute, November 1987. |
| 299 |
|
| 300 |
Security Considerations |
| 301 |
|
| 302 |
Security issues are not discussed in this memo. |
| 303 |
|
| 304 |
Chair's Address |
| 305 |
|
| 306 |
The working group can be contacted via the current chair: |
| 307 |
|
| 308 |
Fred Baker |
| 309 |
Cisco Systems |
| 310 |
519 Lado Drive |
| 311 |
Santa Barbara, California 93111 |
| 312 |
|
| 313 |
EMail: [email protected] |
| 314 |
|
| 315 |
Author's Address |
| 316 |
|
| 317 |
Questions about this memo can also be directed to: |
| 318 |
|
| 319 |
Steve Cobb |
| 320 |
Microsoft Corporation |
| 321 |
One Microsoft Way |
| 322 |
Redmond, WA 98052-6399 |
| 323 |
|
| 324 |
Phone: (206) 882-8080 |
| 325 |
|
| 326 |
EMail: [email protected] |
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
Cobb Informational [Page 6] |
| 333 |
</pre> |