Debian Codegraph @

rfc6119.html

raw
1 <pre>Internet Engineering Task Force (IETF) J. Harrison
2 Request for Comments: 6119 J. Berger
3 Category: Standards Track M. Bartlett
4 ISSN: 2070-1721 Metaswitch Networks
5 February 2011
6
7
8 <span class="h1">IPv6 Traffic Engineering in IS-IS</span>
9
10 Abstract
11
12 This document specifies a method for exchanging IPv6 traffic
13 engineering information using the IS-IS routing protocol. This
14 information enables routers in an IS-IS network to calculate traffic-
15 engineered routes using IPv6 addresses.
16
17 Status of This Memo
18
19 This is an Internet Standards Track document.
20
21 This document is a product of the Internet Engineering Task Force
22 (IETF). It represents the consensus of the IETF community. It has
23 received public review and has been approved for publication by the
24 Internet Engineering Steering Group (IESG). Further information on
25 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
26
27 Information about the current status of this document, any errata,
28 and how to provide feedback on it may be obtained at
29 <a href="http://www.rfc-editor.org/info/rfc6119">http://www.rfc-editor.org/info/rfc6119</a>.
30
31 Copyright Notice
32
33 Copyright (c) 2011 IETF Trust and the persons identified as the
34 document authors. All rights reserved.
35
36 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
37 Provisions Relating to IETF Documents
38 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
39 publication of this document. Please review these documents
40 carefully, as they describe your rights and restrictions with respect
41 to this document. Code Components extracted from this document must
42 include Simplified BSD License text as described in Section 4.e of
43 the Trust Legal Provisions and are provided without warranty as
44 described in the Simplified BSD License.
45
46
47
48
49
50
51
52 <span class="grey">Harrison, et al. 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="./rfc6119">RFC 6119</a> IPv6 Traffic Engineering in IS-IS February 2011</span>
55
56
57 This document may contain material from IETF Documents or IETF
58 Contributions published or made publicly available before November
59 10, 2008. The person(s) controlling the copyright in some of this
60 material may not have granted the IETF Trust the right to allow
61 modifications of such material outside the IETF Standards Process.
62 Without obtaining an adequate license from the person(s) controlling
63 the copyright in such materials, this document may not be modified
64 outside the IETF Standards Process, and derivative works of it may
65 not be created outside the IETF Standards Process, except to format
66 it for publication as an RFC or to translate it into languages other
67 than English.
68
69 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Overview</span>
70
71 The IS-IS routing protocol is defined in [<a href="#ref-IS-IS" title="&quot;Intermediate System to Intermediate System intra- domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode network service (ISO 8473)&quot;">IS-IS</a>]. Each router
72 generates a Link State PDU (LSP) that contains information describing
73 the router and the links from the router. The information in the LSP
74 is encoded in a variable length data structure consisting of a Type,
75 Length, and Value. Such a data structure is referred to as a TLV.
76
77 [<a id="ref-TE">TE</a>] and [<a href="#ref-GMPLS" title="&quot;IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)&quot;">GMPLS</a>] define a number of TLVs and sub-TLVs that allow
78 Traffic Engineering (TE) information to be disseminated by the IS-IS
79 protocol [<a href="#ref-IS-IS" title="&quot;Intermediate System to Intermediate System intra- domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode network service (ISO 8473)&quot;">IS-IS</a>]. The addressing information passed in these TLVs is
80 IPv4 specific.
81
82 [<a id="ref-IPv6">IPv6</a>] describes how the IS-IS protocol can be used to carry out
83 Shortest Path First (SPF) routing for IPv6. It does this by defining
84 IPv6-specific TLVs that are analogous to the TLVs used by IS-IS for
85 carrying IPv4 addressing information.
86
87 Multiprotocol Label Switching (MPLS) traffic engineering is very
88 successful, and, as the use of IPv6 grows, there is a need to be able
89 to support traffic engineering in IPv6 networks.
90
91 This document defines the TLVs that allow traffic engineering
92 information (including Generalized-MPLS (GMPLS) TE information) to be
93 carried in IPv6 IS-IS networks.
94
95 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements Language</span>
96
97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
98 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
99 document are to be interpreted as described in [<a href="#ref-KEYWORDS" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">KEYWORDS</a>].
100
101
102
103
104
105
106
107
108 <span class="grey">Harrison, et al. 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="./rfc6119">RFC 6119</a> IPv6 Traffic Engineering in IS-IS February 2011</span>
111
112
113 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Summary of Operation</span>
114
115 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Identifying IS-IS Links Using IPv6 Addresses</span>
116
117 Each IS-IS link has certain properties -- bandwidth, shared risk link
118 groups (SRLGs), switching capabilities, and so on. The IS-IS
119 extensions defined in [<a href="#ref-TE" title="&quot;IS-IS Extensions for Traffic Engineering&quot;">TE</a>] and [<a href="#ref-GMPLS" title="&quot;IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)&quot;">GMPLS</a>] describe how to associate
120 these traffic engineering parameters with IS-IS links. These TLVs
121 use IPv4 addresses to identify the link (or local/remote link
122 identifiers on unnumbered links).
123
124 When IPv6 is used, a numbered link may be identified by IPv4 and/or
125 IPv6 interface addresses. The type of identifier used does not
126 affect the properties of the link; it still has the same bandwidth,
127 SRLGs, and switching capabilities.
128
129 This document describes an approach for supporting IPv6 traffic
130 engineering by defining TLV extensions that allow TE links and nodes
131 to be identified by IPv6 addresses.
132
133 <span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. IPv6 Address Types</span>
134
135 An IPv6 address can have global, unique-local, or link-local scope.
136
137 - A global IPv6 address is valid within the scope of the Internet.
138
139 - A unique-local IPv6 address is globally unique but is intended for
140 local communication.
141
142 - A link-local IPv6 address is valid only within the scope of a
143 single link and may only be referenced on that link.
144
145 Because the IPv6 traffic engineering TLVs present in LSPs are
146 propagated across networks, they MUST NOT use link-local addresses.
147
148 IS-IS does not need to differentiate between global and unique-local
149 addresses.
150
151 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. IP Addresses Used in Traffic Engineering TLVs</span>
152
153 This section lists the IP addresses used in the TLVs defined in [<a href="#ref-TE" title="&quot;IS-IS Extensions for Traffic Engineering&quot;">TE</a>]
154 and [<a href="#ref-GMPLS" title="&quot;IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)&quot;">GMPLS</a>] and gives an overview of the required IPv6 equivalents.
155
156
157
158
159
160
161
162
163
164 <span class="grey">Harrison, et al. 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="./rfc6119">RFC 6119</a> IPv6 Traffic Engineering in IS-IS February 2011</span>
167
168
169 <span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. TE Router ID TLV</span>
170
171 The TE Router ID TLV contains a stable IPv4 address that is routable,
172 regardless of the state of each interface.
173
174 Similarly, for IPv6, it is useful to have a stable IPv6 address
175 identifying a TE node. The IPv6 TE Router ID TLV is defined in
176 <a href="#section-4.1">Section 4.1</a>.
177
178 <span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>. IPv4 Interface Address Sub-TLV</span>
179
180 This sub-TLV of the Extended IS Reachability TLV contains an IPv4
181 address for the local end of a link. The equivalent IPv6 Interface
182 Address sub-TLV is defined in <a href="#section-4.2">Section 4.2</a>.
183
184 <span class="h4"><a class="selflink" id="section-3.2.3" href="#section-3.2.3">3.2.3</a>. IPv4 Neighbor Address Sub-TLV</span>
185
186 This sub-TLV of the Extended IS Reachability TLV is used for point-
187 to-point links and contains an IPv4 address for the neighbor's end of
188 a link. The equivalent IPv6 Neighbor Address sub-TLV is defined in
189 <a href="#section-4.3">Section 4.3</a>.
190
191 A router constructs the IPv4 Neighbor Address sub-TLV using one of
192 the IPv4 addresses received in the IS-IS Hello (IIH) PDU from the
193 neighbor on the link.
194
195 The IPv6 Neighbor Address sub-TLV contains a globally unique IPv6
196 address for the interface from the peer (which can be either a global
197 or unique-local IPv6 address). The IPv6 Interface Address TLV
198 defined in [<a href="#ref-IPv6" title="&quot;Routing IPv6 with IS-IS&quot;">IPv6</a>] only contains link-local addresses when used in the
199 IIH PDU. Hence, a neighbor's IP address from the IPv6 Interface
200 Address TLV cannot be used when constructing the IPv6 Neighbor
201 Address sub-TLV. Instead, we define an additional TLV, the IPv6
202 Global Interface Address TLV in <a href="#section-4.5">Section 4.5</a>. The IPv6 Global
203 Interface Address TLV is included in IIH PDUs to provide the globally
204 unique IPv6 address that a neighbor router needs in order to
205 construct the IPv6 Neighbor Address sub-TLV.
206
207 <span class="h4"><a class="selflink" id="section-3.2.4" href="#section-3.2.4">3.2.4</a>. IPv4 SRLG TLV</span>
208
209 The SRLG TLV (type 138) defined in [<a href="#ref-GMPLS" title="&quot;IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)&quot;">GMPLS</a>] contains the set of SRLGs
210 associated with a link. The SRLG TLV identifies the link using
211 either local/remote IPv4 addresses or, for point-to-point unnumbered
212 links, link-local/remote identifiers. The SRLG TLV includes a flags
213 field to indicate which type of identifier is used.
214
215
216
217
218
219
220 <span class="grey">Harrison, et al. 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="./rfc6119">RFC 6119</a> IPv6 Traffic Engineering in IS-IS February 2011</span>
223
224
225 When only IPv6 is used, IPv4 addresses and link-local/remote
226 identifiers are not available to identify the link, but IPv6
227 addresses can be used instead.
228
229 There is no backward-compatible way to modify the SRLG TLV (type 138)
230 to identify the link by IPv6 addresses; therefore, we need a new TLV.
231
232 The IPv6 SRLG TLV is defined in <a href="#section-4.4">Section 4.4</a>.
233
234 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IPv6 TE TLVs</span>
235
236 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. IPv6 TE Router ID TLV</span>
237
238 The IPv6 TE Router ID TLV is TLV type 140.
239
240 The IPv6 TE Router ID TLV contains a 16-octet IPv6 address. A stable
241 global IPv6 address MUST be used, so that the router ID provides a
242 routable address, regardless of the state of a node's interfaces.
243
244 If a router does not implement traffic engineering, it MAY include or
245 omit the IPv6 TE Router ID TLV. If a router implements traffic
246 engineering for IPv6, it MUST include this TLV in its LSP. This TLV
247 MUST NOT be included more than once in an LSP.
248
249 An implementation receiving an IPv6 TE Router ID TLV MUST NOT
250 consider the router ID as a /128 reachable prefix in the standard SPF
251 calculation because this can lead to forwarding loops when
252 interacting with systems that do not support this TLV.
253
254 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. IPv6 Interface Address Sub-TLV</span>
255
256 The IPv6 Interface Address sub-TLV of the Extended IS Reachability
257 TLV has sub-TLV type 12. It contains a 16-octet IPv6 address for the
258 interface described by the containing Extended IS Reachability TLV.
259 This sub-TLV can occur multiple times.
260
261 Implementations MUST NOT inject a /128 prefix for the interface
262 address into their routing or forwarding table because this can lead
263 to forwarding loops when interacting with systems that do not support
264 this sub-TLV.
265
266 If a router implements the basic TLV extensions described in [<a href="#ref-TE" title="&quot;IS-IS Extensions for Traffic Engineering&quot;">TE</a>], it
267 MAY include or omit this sub-TLV. If a router implements IPv6
268 traffic engineering, it MUST include this sub-TLV (except on an
269 unnumbered point-to-point link, in which case the Link-Local
270 Interface Identifiers sub-TLV is used instead).
271
272 This sub-TLV MUST NOT contain an IPv6 link-local address.
273
274
275
276 <span class="grey">Harrison, et al. 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="./rfc6119">RFC 6119</a> IPv6 Traffic Engineering in IS-IS February 2011</span>
279
280
281 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. IPv6 Neighbor Address sub-TLV</span>
282
283 The IPv6 Neighbor Address sub-TLV of the Extended IS Reachability TLV
284 has sub-TLV type 13. It contains a 16-octet IPv6 address for a
285 neighboring router on the link described by the (main) TLV. This
286 sub-TLV can occur multiple times.
287
288 Implementations MUST NOT inject a /128 prefix for the interface
289 address into their routing or forwarding table because this can lead
290 to forwarding loops when interacting with systems that do not support
291 this sub-TLV.
292
293 If a router implements the basic TLV extensions described in [<a href="#ref-TE" title="&quot;IS-IS Extensions for Traffic Engineering&quot;">TE</a>], it
294 MAY include or omit this sub-TLV. If a router implements IPv6
295 traffic engineering, it MUST include this sub-TLV for point-to-point
296 links (except on an unnumbered point-to-point link, in which case the
297 Link-Local Interface Identifiers sub-TLV is used instead).
298
299 This sub-TLV MUST NOT contain an IPv6 link-local address.
300
301 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. IPv6 SRLG TLV</span>
302
303 The IPv6 SRLG TLV has type 139. The TLV carries the Shared Risk Link
304 Group information (see the "Shared Risk Link Group Information"
305 section of [<a href="#ref-GMPLS-ROUTING">GMPLS-ROUTING</a>]).
306
307 It contains a data structure consisting of the following:
308
309 - 6 octets of System ID
310 - 1 octet of pseudonode number
311 - 1 octet flags
312 - 16 octets of IPv6 interface address
313 - (optional) 16 octets of IPv6 neighbor address
314 - (variable) list of SRLG values, where each element in the list has
315 4 octets
316
317 The following illustrates the encoding of the Value field of the IPv6
318 SRLG TLV.
319
320
321
322
323
324
325
326
327
328
329
330
331
332 <span class="grey">Harrison, et al. 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="./rfc6119">RFC 6119</a> IPv6 Traffic Engineering in IS-IS February 2011</span>
335
336
337 0 1 2 3
338 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
339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
340 | System ID |
341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
342 | System ID (cont.) | Pseudonode num| Flags |
343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
344 | IPv6 interface address |
345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
346 | IPv6 interface address (continued) |
347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
348 | IPv6 interface address (continued) |
349 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
350 | IPv6 interface address (continued) |
351 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
352 | (optional) IPv6 neighbor address |
353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
354 | IPv6 neighbor address (continued) |
355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
356 | IPv6 neighbor address (continued) |
357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
358 | IPv6 neighbor address (continued) |
359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
360 | Shared Risk Link Group Value |
361 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
362 | ............ |
363 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
364 | Shared Risk Link Group Value |
365 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
366
367 The neighbor is identified by its System ID (6 octets), plus one
368 octet to indicate the pseudonode number if the neighbor is on a LAN
369 interface.
370
371 The 1-octet flags field is interpreted as follows.
372
373 Flags (1 octet)
374
375 0 1 2 3 4 5 6 7
376 +--+--+--+--+--+--+--+--+
377 | Reserved |NA|
378 +--+--+--+--+--+--+--+--+
379
380 NA - Neighbor Address included.
381
382 The flags field currently contains one flag to indicate whether the
383 IPv6 neighbor address is included (the NA bit is set to 1) or not
384 included (the NA bit is set to 0).
385
386
387
388 <span class="grey">Harrison, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc6119">RFC 6119</a> IPv6 Traffic Engineering in IS-IS February 2011</span>
391
392
393 Other bits in the flags field are reserved for future use. Any bits
394 not understood by an implementation MUST be set to zero by the
395 sender. If a router receives an IPv6 SRLG TLV with non-zero values
396 for any bit that it does not understand, it MUST ignore the TLV (in
397 other words, it does not use the TLV locally but floods the TLV
398 unchanged to neighbors as normal).
399
400 Note that this rule for processing the flags octet allows for future
401 extensibility of the IPv6 SRLG TLV. In particular, it allows
402 alternative means of identifying the corresponding link to be added
403 in the future. An implementation that does not understand such an
404 extension will ignore the TLV rather than attempt to interpret the
405 TLV incorrectly.
406
407 The length of this TLV is 24 + 4 * (number of SRLG values) + 16 (if
408 the IPv6 neighbor address is included).
409
410 To prevent an SRLG TLV and an IPv6 SRLG TLV in the same logical LSP
411 from causing confusion of interpretation, the following rules are
412 applied.
413
414 - The IPv6 SRLG TLV MAY occur more than once within the IS-IS
415 logical LSP.
416
417 - There MUST NOT be more than one IPv6 SRLG TLV for a given link.
418
419 - The IPv6 SRLG TLV (type 139) MUST NOT be used to describe the
420 SRLGs for a given link if it is possible to use the SRLG TLV (type
421 138).
422
423 - If both an SRLG TLV and an IPv6 SRLG are received describing the
424 SRLGs for the same link, the receiver MUST apply the SRLG TLV and
425 ignore the IPv6 SRLG TLV.
426
427 In other words, if SRLGs are to be advertised for a link and if the
428 Extended IS Reachability TLV describing a link contains IPv4
429 interface/neighbor address sub-TLVs or the link-local identifiers
430 sub-TLV, then the SRLGs MUST be advertised in the SRLG TLV (type
431 138).
432
433 <span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. IPv6 Global Interface Address TLV</span>
434
435 The IPv6 Global Interface Address TLV is TLV type 233. The TLV
436 structure is identical to that of the IPv6 Interface Address TLV
437 defined in [<a href="#ref-IPv6" title="&quot;Routing IPv6 with IS-IS&quot;">IPv6</a>], but the semantics are different. In particular,
438 the TLV is included in IIH PDUs for those interfaces using IPv6 TE
439 extensions. The TLV contains global or unique-local IPv6 addresses
440 assigned to the interface that is sending the Hello.
441
442
443
444 <span class="grey">Harrison, et al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc6119">RFC 6119</a> IPv6 Traffic Engineering in IS-IS February 2011</span>
447
448
449 The IPv6 Global Interface Address TLV is not used in LSPs.
450
451 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
452
453 This document raises no new security issues for IS-IS; for general
454 security considerations for IS-IS, see [<a href="#ref-ISIS-AUTH" title="&quot;IS-IS Cryptographic Authentication&quot;">ISIS-AUTH</a>].
455
456 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IPv4/IPv6 Migration</span>
457
458 The IS-IS extensions described in this document allow the routing of
459 GMPLS Label Switched Paths using IPv6 addressing through an IS-IS
460 network. There are no migration issues introduced by the addition of
461 this IPv6 TE routing information into an existing IPv4 GMPLS network.
462 Migration of Label Switched Paths from IPv4 to IPv6 is an issue for
463 GMPLS signaling and is outside the scope of this document.
464
465 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span>
466
467 This document defines the following new IS-IS TLV types that IANA has
468 reflected in the IS-IS TLV code-point registry:
469
470 Type Description IIH LSP SNP
471 ---- ---------------------- --- --- ---
472 139 IPv6 SRLG TLV n y n
473 140 IPv6 TE Router ID n y n
474 233 IPv6 Global Interface y n n
475 Address TLV
476
477 This document also defines the following new sub-TLV types of top-
478 level TLV 22 that IANA has reflected in the Sub-TLVs for TLV 22, 141,
479 and 222 registry:
480
481 Type Description 22 141 222 Length
482 ---- ----------- -- --- --- ------
483 12 IPv6 Interface Address y y y 16
484 13 IPv6 Neighbor Address y y y 16
485
486 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Normative References</span>
487
488 [<a id="ref-IS-IS">IS-IS</a>] ISO, "Intermediate System to Intermediate System intra-
489 domain routeing information exchange protocol for use in
490 conjunction with the protocol for providing the
491 connectionless-mode network service (ISO 8473)",
492 International Standard 10589: 2002, Second Edition, 2002.
493
494 [<a id="ref-IPv6">IPv6</a>] Hopps, C., "Routing IPv6 with IS-IS", <a href="./rfc5308">RFC 5308</a>, October
495 2008.
496
497
498
499
500 <span class="grey">Harrison, et al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc6119">RFC 6119</a> IPv6 Traffic Engineering in IS-IS February 2011</span>
503
504
505 [<a id="ref-TE">TE</a>] Li, T. and H. Smit, "IS-IS Extensions for Traffic
506 Engineering", <a href="./rfc5305">RFC 5305</a>, October 2008.
507
508 [<a id="ref-KEYWORDS">KEYWORDS</a>] Bradner, S., "Key words for use in RFCs to Indicate
509 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
510
511 [<a id="ref-ISIS-AUTH">ISIS-AUTH</a>] Li, T. and R. Atkinson, "IS-IS Cryptographic
512 Authentication", <a href="./rfc5304">RFC 5304</a>, October 2008.
513
514 [<a id="ref-GMPLS">GMPLS</a>] Kompella, K., Ed., and Y. Rekhter, Ed., "IS-IS Extensions
515 in Support of Generalized Multi-Protocol Label Switching
516 (GMPLS)", <a href="./rfc5307">RFC 5307</a>, October 2008.
517
518 [<a id="ref-GMPLS-ROUTING">GMPLS-ROUTING</a>]
519 Kompella, K., Ed., and Y. Rekhter, Ed., "Routing
520 Extensions in Support of Generalized Multi-Protocol Label
521 Switching (GMPLS)", <a href="./rfc4202">RFC 4202</a>, October 2005.
522
523 Authors' Addresses
524
525 Jon Harrison
526 Metaswitch Networks
527 100 Church Street
528 Enfield
529 EN2 6BQ
530 U.K.
531 Phone: +44 20 8366 1177
532 EMail: [email protected]
533
534 Jon Berger
535 Metaswitch Networks
536 100 Church Street
537 Enfield
538 EN2 6BQ
539 U.K.
540 Phone: +44 20 8366 1177
541 EMail: [email protected]
542
543 Mike Bartlett
544 Metaswitch Networks
545 100 Church Street
546 Enfield
547 EN2 6BQ
548 U.K.
549 Phone: +44 20 8366 1177
550 EMail: [email protected]
551
552
553
554
555
556 Harrison, et al. Standards Track [Page 10]
557 </pre>