Debian Codegraph @

rfc2335.html

raw
1 <pre>Network Working Group J. Luciani
2 Request for Comments: 2335 Bay Networks
3 Category: Standards Track April 1998
4
5
6 <span class="h1">A Distributed NHRP Service Using SCSP</span>
7
8 Status of this Memo
9
10 This document specifies an Internet standards track protocol for the
11 Internet community, and requests discussion and suggestions for
12 improvements. Please refer to the current edition of the "Internet
13 Official Protocol Standards" (STD 1) for the standardization state
14 and status of this protocol. Distribution of this memo is unlimited.
15
16 Copyright Notice
17
18 Copyright (C) The Internet Society (1998). All Rights Reserved.
19
20 Abstract
21
22 This document describes a method for distributing an NHRP service
23 within a LIS [<a href="#ref-1" title="&quot;NMBA Next Hop Resolution Protocol (NHRP)&quot;">1</a>]. This method uses the Server Cache Synchronization
24 Protocol (SCSP) [<a href="#ref-2" title="&quot;Server Cache Synchronization Protocol (SCSP)&quot;">2</a>] to synchronize the client information databases
25 held by NHRP Servers (NHSs) within a LIS.
26
27 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
28
29 The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
30 SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this
31 document, are to be interpreted as described in [<a href="#ref-4" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">4</a>].
32
33 NHRP Clients (NHCs) register their existence and reachability
34 information with NHRP Servers (NHSs). There may be multiple NHSs in
35 a given Logical IP Subnet (LIS). NHCs do not necessarily register
36 with all NHSs in a LIS; however, all NHCs need to be able to query at
37 least one NHS about any NHC within the LIS. Thus, the contents of
38 the NHS databases in a LIS need to be synchronized across the LIS.
39 The Server Cache Synchronization Protocol (SCSP) solves the
40 generalized server synchronization/cache-replication problem for
41 distributed databases and thus SCSP may be applied to the NHS
42 database synchronization problem within the LIS.
43
44
45
46
47
48
49
50
51
52 <span class="grey">Luciani Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2335">RFC 2335</a> NHRP Using SCSP April 1998</span>
55
56
57 SCSP is defined in two parts: the protocol independent part and the
58 client/server protocol specific part. The protocol independent part
59 is defined in [<a href="#ref-2" title="&quot;Server Cache Synchronization Protocol (SCSP)&quot;">2</a>] whereas this document will specify the
60 client/server protocol specific part where NHRP is the client/server
61 protocol.
62
63 This document is separate from [<a href="#ref-2" title="&quot;Server Cache Synchronization Protocol (SCSP)&quot;">2</a>] because it was felt that it was
64 desirable to allow the client/server protocol specific part
65 specification for NHRP to progress independently from the protocol
66 independent specification.
67
68 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Overview</span>
69
70 All NHSs belonging to a Logical IP Subnet (LIS) [<a href="#ref-1" title="&quot;NMBA Next Hop Resolution Protocol (NHRP)&quot;">1</a>] are said to
71 belong to a Server Group (SG). An SG is identified by, not
72 surprisingly, its SGID which is contained in a field in all SCSP
73 packets. All SCSP packets contain a Protocol ID (PID) field as well.
74 This PID field is set to 0x0002 to signify that SCSP synchronizing
75 NHS databases as opposed to synchronizing some other protocol's
76 databases (see Section B.2.0.1 of [<a href="#ref-2" title="&quot;Server Cache Synchronization Protocol (SCSP)&quot;">2</a>] for more details). In general,
77 PIDs for SCSP will be assigned by IANA as described in Section C of
78 [<a href="#ref-2" title="&quot;Server Cache Synchronization Protocol (SCSP)&quot;">2</a>]. In the case of NHRP, the client/server protocol specific
79 specification was initially written at the same time as SCSP, and
80 thus a PID=0x0002 was assigned by the author.
81
82 SCSP places no topological requirements upon an NHRP SG. Obviously,
83 however, the resultant graph of NHSs must span the set of NHSs to be
84 synchronized. For more information about the client/server protocol
85 independent part of SCSP, the reader is encouraged to see [<a href="#ref-2" title="&quot;Server Cache Synchronization Protocol (SCSP)&quot;">2</a>].
86
87 When a SG is using SCSP for synchronization, an NHC will register
88 with only one NHS, but the NHC MAY use any NHS in the SG. When an
89 NHC wishes to leave a SG, the NHC MUST do one of the following: 1)
90 the NHC MUST send an NHRP Purge Request for itself requesting a
91 reply, and it MUST wait for an NHRP Purge Reply, 2) the NHC MUST keep
92 the Request ID it used when registering itself in non-volatile RAM
93 and use a Request ID larger than the one saved when re-registering,
94 or 3) the NHC MUST not re-register for a time equal to the Holding
95 Time specified in the previous registration. It is necessary to do
96 one of the previous in order to prevent the unlikely case of race
97 conditions from occurring during updated. In the case where method 2
98 is used, the NHS with which the NHC registered uses its ID as the OID
99 and the Request ID from the NHC as the CSA Sequence Number in the
100 CSA(S) Record.
101
102
103
104
105
106
107
108 <span class="grey">Luciani Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2335">RFC 2335</a> NHRP Using SCSP April 1998</span>
111
112
113 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Format of the CSA Record NHRP Specific Part</span>
114
115 CSA Records in SCSP contain a "Client/Server Protocol Specific Part"
116 which contains the non-protocol independent information for a given
117 server's cache entry.
118
119 0 1 2 3
120 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
121 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
122 | Address Family Number | NHRP Protocol Type |
123 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
124 | Snap |
125 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
126 | Snap | NHRP Vers Num | Flags |
127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
128 | Request ID |
129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
130 | State | Prefix Length | unused |
131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
132 | Maximum Transmission Unit | Holding Time |
133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
134 | Cli Addr T/L | Cli SAddr T/L | Cli Proto Len | Preference |
135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
136 | Client Subnetwork Address (variable length) |
137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
138 | Client Subnetwork Subaddress (variable length) |
139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
140 | Client Protocol Address (variable length) |
141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
142
143 The following six fields contain values specified in the common
144 header of the mandatory part of an NHRP Registration Request or NHRP
145 Purge Request packet which caused the
146 creation/deletion/modification/update/etc. of an NHS's cache entry.
147
148 Address Family Number
149 Defines the type of "link layer" addresses being carried. This
150 number is taken from the 'address family number' list specified in
151 [<a href="#ref-3" title="&quot;Assigned Numbers&quot;">3</a>]. This field is the same field which would be supplied in an
152 NHRP packet in the ar$afn field.
153
154 NHRP Protocol Type
155 This field is the same field which would be supplied in an NHRP
156 packet in the ar$pro.type field.
157
158 Snap
159 This field is the same field which would be supplied in an NHRP
160 packet in the ar$pro.snap field.
161
162
163
164 <span class="grey">Luciani Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2335">RFC 2335</a> NHRP Using SCSP April 1998</span>
167
168
169 NHRP Vers Num
170 This field indicates what version of generic address mapping and
171 management protocol that is represented by this message. This
172 field contains 0x01 for the NHRP protocol version 1. This field is
173 the same field which would be supplied in an NHRP packet in the
174 ar$op.version field.
175
176 Flags
177 Defined flags are as follows:
178
179 0 1
180 0 1
181 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
183 |U|A| unused |
184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
185
186 U
187 This is the Uniqueness bit.
188
189 A
190 When set, this bit specifies that the cache entry was created
191 as a result of ATMARP client interaction with the NHS.
192
193 Request ID
194 This field contains the Request ID value placed in the cache entry
195 of the NHS as a result of an NHRP Registration Request. This NHS
196 is the NHS causing a synchronization event.
197
198 State
199 This field contains a value which represents the new state of the
200 client.
201
202 0 - Client is registered and available.
203 1 - Client reregistered.
204 2 - Client has been purged.
205 3 - No such client data in server cache
206
207 Note that a time-out of a cache entry does not cause a CSA Record
208 to be sent because, if everything is working properly then all NHSs
209 have the cache entry timing out at the same time. Thus, the
210 individual NHSs would take the appropriate actions necessary.
211
212 The following ten fields contain values specified in or derived from
213 the CIE of an NHRP Registration Request or NHRP Purge Request packet
214 which caused the creation/deletion/modification/update/etc. of an
215 NHS's cache entry.
216
217
218
219
220 <span class="grey">Luciani Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2335">RFC 2335</a> NHRP Using SCSP April 1998</span>
223
224
225 Prefix Length
226 This field contains the internetwork layer address prefix length
227 value covered by the cache entry being synchronized.
228
229 Maximum Transmission Unit
230 This field contains a value supplied by or derived from information
231 in the CIE of the NHRP Registration Request packet.
232
233 Holding Time
234 The Holding Time field specifies the number of seconds remaining
235 for which the Next Hop NBMA information specified in the CIE of the
236 NHRP Registration Request is considered to be valid by the NHS
237 initiating the synchronization event.
238
239 Cli Addr T/L
240 Type &amp; length of next hop NBMA address (see [<a href="#ref-1" title="&quot;NMBA Next Hop Resolution Protocol (NHRP)&quot;">1</a>]).
241
242 Cli SAddr T/L
243 Type &amp; length of next hop NBMA subaddress (see [<a href="#ref-1" title="&quot;NMBA Next Hop Resolution Protocol (NHRP)&quot;">1</a>]).
244
245 Cli Proto Len
246 This field holds the length in octets of the Client Protocol
247 Address.
248
249 Preference
250 This field specifies the preference value for use of the next hop
251 NBMA information specified.
252
253 Client NBMA Address
254 This is the client's NBMA address.
255
256 Client NBMA SubAddress
257 This is the client's NBMA subaddress.
258
259 Client Protocol Address
260 This is the client's internetworking layer address.
261
262 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Values for SCSP Protocol Independent Part</span>
263
264 The following sections give values for fields of the SCSP Protocol
265 Independent Part of the various SCSP messages.
266
267 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> Values for the SCSP "Mandatory Common Part"</span>
268
269 Protocol ID = 0x0002
270 Sender ID Len = 0x04
271 Recvr ID Len = 0x04
272
273
274
275
276 <span class="grey">Luciani Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2335">RFC 2335</a> NHRP Using SCSP April 1998</span>
279
280
281 See Section B.2.0.1 of [<a href="#ref-2" title="&quot;Server Cache Synchronization Protocol (SCSP)&quot;">2</a>] for a detailed description of these
282 fields.
283
284 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> Values for the SCSP "CSAS Record"</span>
285
286 Cache Key Len = 0x04
287 Orig ID Len = 0x04
288
289 See Section B.2.0.2 of [<a href="#ref-2" title="&quot;Server Cache Synchronization Protocol (SCSP)&quot;">2</a>] for a detailed description of these
290 fields.
291
292 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
293
294 Relevant security considerations are documented in [<a href="#ref-1" title="&quot;NMBA Next Hop Resolution Protocol (NHRP)&quot;">1</a>] and [<a href="#ref-2" title="&quot;Server Cache Synchronization Protocol (SCSP)&quot;">2</a>].
295
296 References
297
298 [<a id="ref-1">1</a>] Luciani, J., Katz, D., Piscitello, D., Cole, B., and N.
299 Doraswamy, "NMBA Next Hop Resolution Protocol (NHRP)", <a href="./rfc2332">RFC 2332</a>,
300 April 1998.
301
302 [<a id="ref-2">2</a>] Luciani, J., Armitage, G., Halpern, J., and N. Doraswamy, "Server
303 Cache Synchronization Protocol (SCSP)", <a href="./rfc2334">RFC 2334</a>, April 1998.
304
305 [<a id="ref-3">3</a>] Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, <a href="./rfc1700">RFC 1700</a>,
306 October 1994.
307
308 [<a id="ref-4">4</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
309 Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
310
311 Acknowledgments
312
313 I would like to thank (in no particular order) Maxine Burns of ISR
314 and Joel Halpern of Newbridge. I would also like to thank the
315 members of the ION working group of the IETF, whose review and
316 discussion of this document has been invaluable.
317
318 Author's Address
319
320 James V. Luciani
321 Bay Networks, Inc.
322 3 Federal Street, BL3-03
323 Billerica, MA 01821
324
325 Phone: +1-978-916-4734
326 EMail: [email protected]
327
328
329
330
331
332 <span class="grey">Luciani Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2335">RFC 2335</a> NHRP Using SCSP April 1998</span>
335
336
337 Full Copyright Statement
338
339 Copyright (C) The Internet Society (1998). All Rights Reserved.
340
341 This document and translations of it may be copied and furnished to
342 others, and derivative works that comment on or otherwise explain it
343 or assist in its implementation may be prepared, copied, published
344 and distributed, in whole or in part, without restriction of any
345 kind, provided that the above copyright notice and this paragraph are
346 included on all such copies and derivative works. However, this
347 document itself may not be modified in any way, such as by removing
348 the copyright notice or references to the Internet Society or other
349 Internet organizations, except as needed for the purpose of
350 developing Internet standards in which case the procedures for
351 copyrights defined in the Internet Standards process must be
352 followed, or as required to translate it into languages other than
353 English.
354
355 The limited permissions granted above are perpetual and will not be
356 revoked by the Internet Society or its successors or assigns.
357
358 This document and the information contained herein is provided on an
359 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
360 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
361 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
362 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
363 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388 Luciani Standards Track [Page 7]
389 </pre>