| blob | 8fea5c311bfd2021d373f210d61b09b736169233 |
7 Network Working Group J. Loughney, Ed.
8 Request for Comments: 4294 Nokia
9 Category: Informational April 2006
12 IPv6 Node Requirements
14 Status of This Memo
16 This memo provides information for the Internet community. It does
17 not specify an Internet standard of any kind. Distribution of this
18 memo is unlimited.
20 Copyright Notice
22 Copyright (C) The Internet Society (2006).
24 Abstract
26 This document defines requirements for IPv6 nodes. It is expected
27 that IPv6 will be deployed in a wide range of devices and situations.
28 Specifying the requirements for IPv6 nodes allows IPv6 to function
29 well and interoperate in a large number of situations and
30 deployments.
32 Table of Contents
34 1. Introduction ....................................................2
35 1.1. Requirement Language .......................................3
36 1.2. Scope of This Document .....................................3
37 1.3. Description of IPv6 Nodes ..................................3
38 2. Abbreviations Used in This Document .............................3
39 3. Sub-IP Layer ....................................................4
40 3.1. Transmission of IPv6 Packets over Ethernet Networks
41 - RFC 2464 .................................................4
42 3.2. IP version 6 over PPP - RFC 2472 ...........................4
43 3.3. IPv6 over ATM Networks - RFC 2492 ..........................4
44 4. IP Layer ........................................................5
45 4.1. Internet Protocol Version 6 - RFC 2460 .....................5
46 4.2. Neighbor Discovery for IPv6 - RFC 2461 .....................5
47 4.3. Path MTU Discovery and Packet Size .........................6
48 4.4. ICMP for the Internet Protocol Version 6 (IPv6) -
49 RFC 2463 ...................................................7
50 4.5. Addressing .................................................7
51 4.6. Multicast Listener Discovery (MLD) for IPv6 - RFC 2710 .....8
52 5. DNS and DHCP ....................................................8
53 5.1. DNS ........................................................8
58 Loughney Informational [Page 1]
59 \f
60 RFC 4294 IPv6 Node Requirements April 2006
63 5.2. Dynamic Host Configuration Protocol for IPv6
64 (DHCPv6) - RFC 3315 ........................................9
65 6. IPv4 Support and Transition ....................................10
66 6.1. Transition Mechanisms .....................................10
67 7. Mobile IP ......................................................10
68 8. Security .......................................................10
69 8.1. Basic Architecture ........................................10
70 8.2. Security Protocols ........................................11
71 8.3. Transforms and Algorithms .................................11
72 8.4. Key Management Methods ....................................12
73 9. Router-Specific Functionality ..................................12
74 9.1. General ...................................................12
75 10. Network Management ............................................12
76 10.1. Management Information Base Modules (MIBs) ...............12
77 11. Security Considerations .......................................13
78 12. References ....................................................13
79 12.1. Normative References .....................................13
80 12.2. Informative References ...................................16
81 13. Authors and Acknowledgements ..................................18
83 1. Introduction
85 The goal of this document is to define the common functionality
86 required from both IPv6 hosts and routers. Many IPv6 nodes will
87 implement optional or additional features, but this document
88 summarizes requirements from other published Standards Track
89 documents in one place.
91 This document tries to avoid discussion of protocol details, and
92 references RFCs for this purpose. This document is informational in
93 nature and does not update Standards Track RFCs.
95 Although the document points to different specifications, it should
96 be noted that in most cases, the granularity of requirements are
97 smaller than a single specification, as many specifications define
98 multiple, independent pieces, some of which may not be mandatory.
100 As it is not always possible for an implementer to know the exact
101 usage of IPv6 in a node, an overriding requirement for IPv6 nodes is
102 that they should adhere to Jon Postel's Robustness Principle:
104 Be conservative in what you do, be liberal in what you accept from
105 others [RFC-793].
114 Loughney Informational [Page 2]
115 \f
116 RFC 4294 IPv6 Node Requirements April 2006
119 1.1. Requirement Language
121 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
122 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
123 document are to be interpreted as described in RFC 2119 [RFC-2119].
125 1.2. Scope of This Document
127 IPv6 covers many specifications. It is intended that IPv6 will be
128 deployed in many different situations and environments. Therefore,
129 it is important to develop the requirements for IPv6 nodes to ensure
130 interoperability.
132 This document assumes that all IPv6 nodes meet the minimum
133 requirements specified here.
135 1.3. Description of IPv6 Nodes
137 From the Internet Protocol, Version 6 (IPv6) Specification
138 [RFC-2460], we have the following definitions:
140 Description of an IPv6 Node
142 - a device that implements IPv6.
144 Description of an IPv6 router
146 - a node that forwards IPv6 packets not explicitly addressed
147 to itself.
149 Description of an IPv6 Host
151 - any node that is not a router.
153 2. Abbreviations Used in This Document
155 ATM Asynchronous Transfer Mode
157 AH Authentication Header
159 DAD Duplicate Address Detection
161 ESP Encapsulating Security Payload
163 ICMP Internet Control Message Protocol
165 IKE Internet Key Exchange
170 Loughney Informational [Page 3]
171 \f
172 RFC 4294 IPv6 Node Requirements April 2006
175 MIB Management Information Base
177 MLD Multicast Listener Discovery
179 MTU Maximum Transfer Unit
181 NA Neighbor Advertisement
183 NBMA Non-Broadcast Multiple Access
185 ND Neighbor Discovery
187 NS Neighbor Solicitation
189 NUD Neighbor Unreachability Detection
191 PPP Point-to-Point Protocol
193 PVC Permanent Virtual Circuit
195 SVC Switched Virtual Circuit
197 3. Sub-IP Layer
199 An IPv6 node must include support for one or more IPv6 link-layer
200 specifications. Which link-layer specifications are included will
201 depend upon what link-layers are supported by the hardware available
202 on the system. It is possible for a conformant IPv6 node to support
203 IPv6 on some of its interfaces and not on others.
205 As IPv6 is run over new layer 2 technologies, it is expected that new
206 specifications will be issued. This section highlights some major
207 layer 2 technologies and is not intended to be complete.
209 3.1. Transmission of IPv6 Packets over Ethernet Networks - RFC 2464
211 Nodes supporting IPv6 over Ethernet interfaces MUST implement
212 Transmission of IPv6 Packets over Ethernet Networks [RFC-2464].
214 3.2. IP version 6 over PPP - RFC 2472
216 Nodes supporting IPv6 over PPP MUST implement IPv6 over PPP
217 [RFC-2472].
219 3.3. IPv6 over ATM Networks - RFC 2492
221 Nodes supporting IPv6 over ATM Networks MUST implement IPv6 over ATM
222 Networks [RFC-2492]. Additionally, RFC 2492 states:
226 Loughney Informational [Page 4]
227 \f
228 RFC 4294 IPv6 Node Requirements April 2006
231 A minimally conforming IPv6/ATM driver SHALL support the PVC mode
232 of operation. An IPv6/ATM driver that supports the full SVC mode
233 SHALL also support PVC mode of operation.
235 4. IP Layer
237 4.1. Internet Protocol Version 6 - RFC 2460
239 The Internet Protocol Version 6 is specified in [RFC-2460]. This
240 specification MUST be supported.
242 Unrecognized options in Hop-by-Hop Options or Destination Options
243 extensions MUST be processed as described in RFC 2460.
245 The node MUST follow the packet transmission rules in RFC 2460.
247 Nodes MUST always be able to send, receive, and process fragment
248 headers. All conformant IPv6 implementations MUST be capable of
249 sending and receiving IPv6 packets; the forwarding functionality MAY
250 be supported.
252 RFC 2460 specifies extension headers and the processing for these
253 headers.
255 A full implementation of IPv6 includes implementation of the
256 following extension headers: Hop-by-Hop Options, Routing (Type 0),
257 Fragment, Destination Options, Authentication and Encapsulating
258 Security Payload [RFC-2460].
260 An IPv6 node MUST be able to process these headers. It should be
261 noted that there is some discussion about the use of Routing Headers
262 and possible security threats [IPv6-RH] that they cause.
264 4.2. Neighbor Discovery for IPv6 - RFC 2461
266 Neighbor Discovery SHOULD be supported. [RFC-2461] states:
268 "Unless specified otherwise (in a document that covers operating
269 IP over a particular link type) this document applies to all link
270 types. However, because ND uses link-layer multicast for some of
271 its services, it is possible that on some link types (e.g., NBMA
272 links) alternative protocols or mechanisms to implement those
273 services will be specified (in the appropriate document covering
274 the operation of IP over a particular link type). The services
275 described in this document that are not directly dependent on
276 multicast, such as Redirects, Next-hop determination, Neighbor
277 Unreachability Detection, etc., are expected to be provided as
282 Loughney Informational [Page 5]
283 \f
284 RFC 4294 IPv6 Node Requirements April 2006
287 specified in this document. The details of how one uses ND on
288 NBMA links is an area for further study."
290 Some detailed analysis of Neighbor Discovery follows:
292 Router Discovery is how hosts locate routers that reside on an
293 attached link. Router Discovery MUST be supported for
294 implementations.
296 Prefix Discovery is how hosts discover the set of address prefixes
297 that define which destinations are on-link for an attached link.
298 Prefix discovery MUST be supported for implementations. Neighbor
299 Unreachability Detection (NUD) MUST be supported for all paths
300 between hosts and neighboring nodes. It is not required for paths
301 between routers. However, when a node receives a unicast Neighbor
302 Solicitation (NS) message (that may be a NUD's NS), the node MUST
303 respond to it (i.e., send a unicast Neighbor Advertisement).
305 Duplicate Address Detection MUST be supported on all links supporting
306 link-layer multicast (RFC 2462, Section 5.4, specifies DAD MUST take
307 place on all unicast addresses).
309 A host implementation MUST support sending Router Solicitations.
311 Receiving and processing Router Advertisements MUST be supported for
312 host implementations. The ability to understand specific Router
313 Advertisement options is dependent on supporting the specification
314 where the RA is specified.
316 Sending and Receiving Neighbor Solicitation (NS) and Neighbor
317 Advertisement (NA) MUST be supported. NS and NA messages are
318 required for Duplicate Address Detection (DAD).
320 Redirect functionality SHOULD be supported. If the node is a router,
321 Redirect functionality MUST be supported.
323 4.3. Path MTU Discovery and Packet Size
325 4.3.1. Path MTU Discovery - RFC 1981
327 Path MTU Discovery [RFC-1981] SHOULD be supported, though minimal
328 implementations MAY choose to not support it and avoid large packets.
329 The rules in RFC 2460 MUST be followed for packet fragmentation and
330 reassembly.
332 4.3.2. IPv6 Jumbograms - RFC 2675
334 IPv6 Jumbograms [RFC-2675] MAY be supported.
338 Loughney Informational [Page 6]
339 \f
340 RFC 4294 IPv6 Node Requirements April 2006
343 4.4. ICMP for the Internet Protocol Version 6 (IPv6) - RFC 2463
345 ICMPv6 [RFC-2463] MUST be supported.
347 4.5. Addressing
349 4.5.1. IP Version 6 Addressing Architecture - RFC 3513
351 The IPv6 Addressing Architecture [RFC-3513] MUST be supported as
352 updated by [RFC-3879].
354 4.5.2. IPv6 Stateless Address Autoconfiguration - RFC 2462
356 IPv6 Stateless Address Autoconfiguration is defined in [RFC-2462].
357 This specification MUST be supported for nodes that are hosts.
358 Static address can be supported as well.
360 Nodes that are routers MUST be able to generate link local addresses
361 as described in RFC 2462 [RFC-2462].
363 From 2462:
365 The autoconfiguration process specified in this document applies
366 only to hosts and not routers. Since host autoconfiguration uses
367 information advertised by routers, routers will need to be
368 configured by some other means. However, it is expected that
369 routers will generate link-local addresses using the mechanism
370 described in this document. In addition, routers are expected to
371 successfully pass the Duplicate Address Detection procedure
372 described in this document on all addresses prior to assigning
373 them to an interface.
375 Duplicate Address Detection (DAD) MUST be supported.
377 4.5.3. Privacy Extensions for Address Configuration in IPv6 - RFC 3041
379 Privacy Extensions for Stateless Address Autoconfiguration [RFC-3041]
380 SHOULD be supported. It is recommended that this behavior be
381 configurable on a connection basis within each application when
382 available. It is noted that a number of applications do not work
383 with addresses generated with this method, while other applications
384 work quite well with them.
386 4.5.4. Default Address Selection for IPv6 - RFC 3484
388 The rules specified in the Default Address Selection for IPv6
389 [RFC-3484] document MUST be implemented. It is expected that IPv6
390 nodes will need to deal with multiple addresses.
394 Loughney Informational [Page 7]
395 \f
396 RFC 4294 IPv6 Node Requirements April 2006
399 4.5.5. Stateful Address Autoconfiguration
401 Stateful Address Autoconfiguration MAY be supported. DHCPv6
402 [RFC-3315] is the standard stateful address configuration protocol;
403 see Section 5.3 for DHCPv6 support.
405 Nodes which do not support Stateful Address Autoconfiguration may be
406 unable to obtain any IPv6 addresses, aside from link-local addresses,
407 when it receives a router advertisement with the 'M' flag (Managed
408 address configuration) set and that contains no prefixes advertised
409 for Stateless Address Autoconfiguration (see Section 4.5.2).
410 Additionally, such nodes will be unable to obtain other configuration
411 information, such as the addresses of DNS servers when it is
412 connected to a link over which the node receives a router
413 advertisement in which the 'O' flag ("Other stateful configuration")
414 is set.
416 4.6. Multicast Listener Discovery (MLD) for IPv6 - RFC 2710
418 Nodes that need to join multicast groups SHOULD implement MLDv2
419 [RFC-3810]. However, if the node has applications that only need
420 support for Any-Source Multicast [RFC-3569], the node MAY implement
421 MLDv1 [RFC-2710] instead. If the node has applications that need
422 support for Source-Specific Multicast [RFC-3569, SSM-ARCH], the node
423 MUST support MLDv2 [RFC-3810].
425 When MLD is used, the rules in the "Source Address Selection for the
426 Multicast Listener Discovery (MLD) Protocol" [RFC-3590] MUST be
427 followed.
429 5. DNS and DHCP
431 5.1. DNS
433 DNS is described in [RFC-1034], [RFC-1035], [RFC-3152], [RFC-3363],
434 and [RFC-3596]. Not all nodes will need to resolve names; those that
435 will never need to resolve DNS names do not need to implement
436 resolver functionality. However, the ability to resolve names is a
437 basic infrastructure capability that applications rely on and
438 generally needs to be supported. All nodes that need to resolve
439 names SHOULD implement stub-resolver [RFC-1034] functionality, as in
440 RFC 1034, Section 5.3.1, with support for:
442 - AAAA type Resource Records [RFC-3596];
444 - reverse addressing in ip6.arpa using PTR records [RFC-3152];
450 Loughney Informational [Page 8]
451 \f
452 RFC 4294 IPv6 Node Requirements April 2006
455 - EDNS0 [RFC-2671] to allow for DNS packet sizes larger than 512
456 octets.
458 Those nodes are RECOMMENDED to support DNS security extensions
459 [RFC-4033], [RFC-4034], and [RFC-4035].
461 Those nodes are NOT RECOMMENDED to support the experimental A6 and
462 DNAME Resource Records [RFC-3363].
464 5.2. Dynamic Host Configuration Protocol for IPv6 (DHCPv6) - RFC 3315
466 5.2.1. Managed Address Configuration
468 The method by which IPv6 nodes that use DHCP for address assignment
469 can obtain IPv6 addresses and other configuration information upon
470 receipt of a Router Advertisement with the 'M' flag set is described
471 in Section 5.5.3 of RFC 2462.
473 In addition, in the absence of a router, those IPv6 nodes that use
474 DHCP for address assignment MUST initiate DHCP to obtain IPv6
475 addresses and other configuration information, as described in
476 Section 5.5.2 of RFC 2462. Those IPv6 nodes that do not use DHCP for
477 address assignment can ignore the 'M' flag in Router Advertisements.
479 5.2.2. Other Configuration Information
481 The method by which IPv6 nodes that use DHCP to obtain other
482 configuration information can obtain other configuration information
483 upon receipt of a Router Advertisement with the 'O' flag set is
484 described in Section 5.5.3 of RFC 2462.
486 Those IPv6 nodes that use DHCP to obtain other configuration
487 information initiate DHCP for other configuration information upon
488 receipt of a Router Advertisement with the 'O' flag set, as described
489 in Section 5.5.3 of RFC 2462. Those IPv6 nodes that do not use DHCP
490 for other configuration information can ignore the 'O' flag in Router
491 Advertisements.
493 An IPv6 node can use the subset of DHCP (described in [RFC-3736]) to
494 obtain other configuration information.
496 5.3.3. Use of Router Advertisements in Managed Environments
498 Nodes using the Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
499 are expected to determine their default router information and on-
500 link prefix information from received Router Advertisements.
506 Loughney Informational [Page 9]
507 \f
508 RFC 4294 IPv6 Node Requirements April 2006
511 6. IPv4 Support and Transition
513 IPv6 nodes MAY support IPv4.
515 6.1. Transition Mechanisms
517 6.1.1. Transition Mechanisms for IPv6 Hosts and Routers - RFC 2893
519 If an IPv6 node implements dual stack and tunneling, then [RFC-4213]
520 MUST be supported.
522 7. Mobile IP
524 The Mobile IPv6 [RFC-3775] specification defines requirements for the
525 following types of nodes:
527 - mobile nodes
529 - correspondent nodes with support for route optimization
531 - home agents
533 - all IPv6 routers
535 Hosts MAY support mobile node functionality described in Section 8.5
536 of [RFC-3775], including support of generic packet tunneling [RFC-
537 2473] and secure home agent communications [RFC-3776].
539 Hosts SHOULD support route optimization requirements for
540 correspondent nodes described in Section 8.2 of [RFC-3775].
542 Routers SHOULD support the generic mobility-related requirements for
543 all IPv6 routers described in Section 8.3 of [RFC-3775]. Routers MAY
544 support the home agent functionality described in Section 8.4 of
545 [RFC-3775], including support of [RFC-2473] and [RFC-3776].
547 8. Security
549 This section describes the specification of IPsec for the IPv6 node.
551 8.1. Basic Architecture
553 Security Architecture for the Internet Protocol [RFC-4301] MUST be
554 supported.
562 Loughney Informational [Page 10]
563 \f
564 RFC 4294 IPv6 Node Requirements April 2006
567 8.2. Security Protocols
569 ESP [RFC-4303] MUST be supported. AH [RFC-4302] MUST be supported.
571 8.3. Transforms and Algorithms
573 Current IPsec RFCs specify the support of transforms and algorithms
574 for use with AH and ESP: NULL encryption, DES-CBC, HMAC-SHA-1-96, and
575 HMAC-MD5-96. However, "Cryptographic Algorithm Implementation
576 Requirements For ESP And AH" [RFC-4305] contains the current set of
577 mandatory to implement algorithms for ESP and AH. It also specifies
578 algorithms that should be implemented because they are likely to be
579 promoted to mandatory at some future time. IPv6 nodes SHOULD conform
580 to the requirements in [RFC-4305], as well as the requirements
581 specified below.
583 Since ESP encryption and authentication are both optional, support
584 for the NULL encryption algorithm [RFC-2410] and the NULL
585 authentication algorithm [RFC-4303] MUST be provided to maintain
586 consistency with the way these services are negotiated. However,
587 while authentication and encryption can each be NULL, they MUST NOT
588 both be NULL. The NULL encryption algorithm is also useful for
589 debugging.
591 The DES-CBC encryption algorithm [RFC-2405] SHOULD NOT be supported
592 within ESP. Security issues related to the use of DES are discussed
593 in [DESDIFF], [DESINT], and [DESCRACK]. DES-CBC is still listed as
594 required by the existing IPsec RFCs, but updates to these RFCs will
595 be published in the near future. DES provides 56 bits of protection,
596 which is no longer considered sufficient.
598 The use of the HMAC-SHA-1-96 algorithm [RFC-2404] within AH and ESP
599 MUST be supported. The use of the HMAC-MD5-96 algorithm [RFC-2403]
600 within AH and ESP MAY also be supported.
602 The 3DES-CBC encryption algorithm [RFC-2451] does not suffer from the
603 same security issues as DES-CBC, and the 3DES-CBC algorithm within
604 ESP MUST be supported to ensure interoperability.
606 The AES-128-CBC algorithm [RFC-3602] MUST also be supported within
607 ESP. AES-128 is expected to be a widely available, secure, and
608 efficient algorithm. While AES-128-CBC is not required by the
609 current IPsec RFCs, it is expected to become required in the future.
618 Loughney Informational [Page 11]
619 \f
620 RFC 4294 IPv6 Node Requirements April 2006
623 8.4. Key Management Methods
625 An implementation MUST support the manual configuration of the
626 security key and SPI. The SPI configuration is needed in order to
627 delineate between multiple keys.
629 Key management SHOULD be supported. Examples of key management
630 systems include IKEv2 [RFC-4306] and Kerberos; S/MIME and TLS include
631 key management functions.
633 Where key refresh, anti-replay features of AH and ESP, or on-demand
634 creation of Security Associations (SAs) is required, automated keying
635 MUST be supported.
637 Key management methods for multicast traffic are also being worked on
638 by the MSEC WG.
640 9. Router-Specific Functionality
642 This section defines general host considerations for IPv6 nodes that
643 act as routers. Currently, this section does not discuss routing-
644 specific requirements.
646 9.1. General
648 9.1.1. IPv6 Router Alert Option - RFC 2711
650 The IPv6 Router Alert Option [RFC-2711] is an optional IPv6 Hop-by-
651 Hop Header that is used in conjunction with some protocols (e.g.,
652 RSVP [RFC-2205] or MLD [RFC-2710]). The Router Alert option will
653 need to be implemented whenever protocols that mandate its usage are
654 implemented. See Section 4.6.
656 9.1.2. Neighbor Discovery for IPv6 - RFC 2461
658 Sending Router Advertisements and processing Router Solicitation MUST
659 be supported.
661 10. Network Management
663 Network Management MAY be supported by IPv6 nodes. However, for IPv6
664 nodes that are embedded devices, network management may be the only
665 possible way of controlling these nodes.
667 10.1. Management Information Base Modules (MIBs)
669 The following two MIBs SHOULD be supported by nodes that support an
670 SNMP agent.
674 Loughney Informational [Page 12]
675 \f
676 RFC 4294 IPv6 Node Requirements April 2006
679 10.1.1. IP Forwarding Table MIB
681 IP Forwarding Table MIB [RFC-4292] SHOULD be supported by nodes that
682 support an SNMP agent.
684 10.1.2. Management Information Base for the Internet Protocol (IP)
686 IP MIB [RFC-4293] SHOULD be supported by nodes that support an SNMP
687 agent.
689 11. Security Considerations
691 This document does not affect the security of the Internet, but
692 implementations of IPv6 are expected to support a minimum set of
693 security features to ensure security on the Internet. "IP Security
694 Document Roadmap" [RFC-2411] is important for everyone to read.
696 The security considerations in RFC 2460 state the following:
698 The security features of IPv6 are described in the Security
699 Architecture for the Internet Protocol [RFC-2401].
701 RFC 2401 has been obsoleted by RFC 4301, therefore refer RFC 4301 for
702 the security features of IPv6.
704 12. References
706 12.1. Normative References
708 [RFC-1035] Mockapetris, P., "Domain names - implementation and
709 specification", STD 13, RFC 1035, November 1987.
711 [RFC-1981] McCann, J., Deering, S., and J. Mogul, "Path MTU
712 Discovery for IP version 6", RFC 1981, August 1996.
714 [RFC-2104] Krawczyk, H., Bellare, M., and R. Canetti, "HMAC:
715 Keyed-Hashing for Message Authentication", RFC 2104,
716 February 1997.
718 [RFC-2119] Bradner, S., "Key words for use in RFCs to Indicate
719 Requirement Levels", BCP 14, RFC 2119, March 1997.
721 [RFC-2403] Madson, C. and R. Glenn, "The Use of HMAC-MD5-96
722 within ESP and AH", RFC 2403, November 1998.
724 [RFC-2404] Madson, C. and R. Glenn, "The Use of HMAC-SHA-1-96
725 within ESP and AH", RFC 2404, November 1998.
730 Loughney Informational [Page 13]
731 \f
732 RFC 4294 IPv6 Node Requirements April 2006
735 [RFC-2405] Madson, C. and N. Doraswamy, "The ESP DES-CBC Cipher
736 Algorithm With Explicit IV", RFC 2405, November 1998.
738 [RFC-2410] Glenn, R. and S. Kent, "The NULL Encryption Algorithm
739 and Its Use With IPsec", RFC 2410, November 1998.
741 [RFC-2411] Thayer, R., Doraswamy, N., and R. Glenn, "IP Security
742 Document Roadmap", RFC 2411, November 1998.
744 [RFC-2451] Pereira, R. and R. Adams, "The ESP CBC-Mode Cipher
745 Algorithms", RFC 2451, November 1998.
747 [RFC-2460] Deering, S. and R. Hinden, "Internet Protocol, Version
748 6 (IPv6) Specification", RFC 2460, December 1998.
750 [RFC-2461] Narten, T., Nordmark, E., and W. Simpson, "Neighbor
751 Discovery for IP Version 6 (IPv6)", RFC 2461, December
752 1998.
754 [RFC-2462] Thomson, S. and T. Narten, "IPv6 Stateless Address
755 Autoconfiguration", RFC 2462, December 1998.
757 [RFC-2463] Conta, A. and S. Deering, "Internet Control Message
758 Protocol (ICMPv6) for the Internet Protocol Version 6
759 (IPv6) Specification", RFC 2463, December 1998.
761 [RFC-2472] Haskin, D. and E. Allen, "IP Version 6 over PPP", RFC
762 2472, December 1998.
764 [RFC-2473] Conta, A. and S. Deering, "Generic Packet Tunneling in
765 IPv6 Specification", RFC 2473, December 1998.
767 [RFC-2671] Vixie, P., "Extension Mechanisms for DNS (EDNS0)", RFC
768 2671, August 1999.
770 [RFC-2710] Deering, S., Fenner, W., and B. Haberman, "Multicast
771 Listener Discovery (MLD) for IPv6", RFC 2710, October
772 1999.
774 [RFC-2711] Partridge, C. and A. Jackson, "IPv6 Router Alert
775 Option", RFC 2711, October 1999.
777 [RFC-3041] Narten, T. and R. Draves, "Privacy Extensions for
778 Stateless Address Autoconfiguration in IPv6", RFC
779 3041, January 2001.
781 [RFC-3152] Bush, R., "Delegation of IP6.ARPA", BCP 49, RFC 3152,
782 August 2001.
786 Loughney Informational [Page 14]
787 \f
788 RFC 4294 IPv6 Node Requirements April 2006
791 [RFC-3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins,
792 C., and M. Carney, "Dynamic Host Configuration
793 Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003.
795 [RFC-3363] Bush, R., Durand, A., Fink, B., Gudmundsson, O., and
796 T. Hain, "Representing Internet Protocol version 6
797 (IPv6) Addresses in the Domain Name System (DNS)", RFC
798 3363, August 2002.
800 [RFC-3484] Frye, R., Levi, D., Routhier, S., and B. Wijnen,
801 "Coexistence between Version 1, Version 2, and Version
802 3 of the Internet-standard Network Management
803 Framework", BCP 74, RFC 3584, August 2003.
805 [RFC-3513] Hinden, R. and S. Deering, "Internet Protocol Version
806 6 (IPv6) Addressing Architecture", RFC 3513, April
807 2003.
809 [RFC-3590] Haberman, B., "Source Address Selection for the
810 Multicast Listener Discovery (MLD) Protocol", RFC
811 3590, September 2003.
813 [RFC-3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi,
814 "DNS Extensions to Support IP Version 6", RFC 3596,
815 October 2003.
817 [RFC-3602] Frankel, S., Glenn, R., and S. Kelly, "The AES-CBC
818 Cipher Algorithm and Its Use with IPsec", RFC 3602,
819 September 2003.
821 [RFC-3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility
822 Support in IPv6", RFC 3775, June 2004.
824 [RFC-3776] Arkko, J., Devarapalli, V., and F. Dupont, "Using
825 IPsec to Protect Mobile IPv6 Signaling Between Mobile
826 Nodes and Home Agents", RFC 3776, June 2004.
828 [RFC-3810] Vida, R. and L. Costa, "Multicast Listener Discovery
829 Version 2 (MLDv2) for IPv6", RFC 3810, June 2004.
831 [RFC-3879] Huitema, C. and B. Carpenter, "Deprecating Site Local
832 Addresses", RFC 3879, September 2004.
834 [RFC-4292] Haberman, B., "IP Forwarding Table MIB", RFC 4292,
835 April 2006.
837 [RFC-4293] Routhier, S., Ed., "Management Information Base for
838 the Internet Protocol (IP)", RFC 4293, April 2006.
842 Loughney Informational [Page 15]
843 \f
844 RFC 4294 IPv6 Node Requirements April 2006
847 [RFC-4301] Kent, S. and R. Atkinson, "Security Architecture for
848 the Internet Protocol", RFC 4301, December 2005.
850 [RFC-4302] Kent, S., "IP Authentication Header", RFC 4302,
851 December 2005.
853 [RFC-4303] Kent, S., "IP Encapsulating Security Payload (ESP)",
854 RFC 4303, December 2005.
856 [RFC-4305] Eastlake 3rd, D., "Cryptographic Algorithm
857 Implementation Requirements for Encapsulating Security
858 Payload (ESP) and Authentication Header (AH)", RFC
859 4305, December 2005.
861 12.2. Informative References
863 [DESDIFF] Biham, E., Shamir, A., "Differential Cryptanalysis of
864 DES-like cryptosystems", Journal of Cryptology Vol 4,
865 Jan 1991.
867 [DESCRACK] Cracking DES, O'Reilly & Associates, Sebastapol, CA
868 2000.
870 [DESINT] Bellovin, S., "An Issue With DES-CBC When Used Without
871 Strong Integrity", Proceedings of the 32nd IETF,
872 Danvers, MA, April 1995.
874 [IPv6-RH] P. Savola, "Security of IPv6 Routing Header and Home
875 Address Options", Work in Progress.
877 [RFC-793] Postel, J., "Transmission Control Protocol", STD 7,
878 RFC 793, September 1981.
880 [RFC-1034] Mockapetris, P., "Domain names - concepts and
881 facilities", STD 13, RFC 1034, November 1987.
883 [RFC-2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S.
884 Jamin, "Resource ReSerVation Protocol (RSVP) --
885 Version 1 Functional Specification", RFC 2205,
886 September 1997.
888 [RFC-2464] Crawford, M., "Transmission of IPv6 Packets over
889 Ethernet Networks", RFC 2464, December 1998.
891 [RFC-2492] Armitage, G., Schulter, P., and M. Jork, "IPv6 over
892 ATM Networks", RFC 2492, January 1999.
898 Loughney Informational [Page 16]
899 \f
900 RFC 4294 IPv6 Node Requirements April 2006
903 [RFC-2675] Borman, D., Deering, S., and R. Hinden, "IPv6
904 Jumbograms", RFC 2675, August 1999.
906 [RFC-4213] Nordmark, E. and R. Gilligan, "Basic Transition
907 Mechanisms for IPv6 Hosts and Routers", RFC 4213,
908 October 2005.
910 [RFC-3569] Bhattacharyya, S., "An Overview of Source-Specific
911 Multicast (SSM)", RFC 3569, July 2003.
913 [RFC-3736] Droms, R., "Stateless Dynamic Host Configuration
914 Protocol (DHCP) Service for IPv6", RFC 3736, April
915 2004.
917 [RFC-4001] Daniele, M., Haberman, B., Routhier, S., and J.
918 Schoenwaelder, "Textual Conventions for Internet
919 Network Addresses", RFC 4001, February 2005.
921 [RFC-4033] Arends, R., Austein, R., Larson, M., Massey, D., and
922 S. Rose, "DNS Security Introduction and Requirements",
923 RFC 4033, March 2005.
925 [RFC-4034] Arends, R., Austein, R., Larson, M., Massey, D., and
926 S. Rose, "Resource Records for the DNS Security
927 Extensions", RFC 4034, March 2005.
929 [RFC-4035] Arends, R., Austein, R., Larson, M., Massey, D., and
930 S. Rose, "Protocol Modifications for the DNS Security
931 Extensions", RFC 4035, March 2005.
933 [RFC-4306] Kaufman, C., Ed., "Internet Key Exchange (IKEv2)
934 Protocol", RFC 4306, December 2005.
936 [SSM-ARCH] H. Holbrook, B. Cain, "Source-Specific Multicast for
937 IP", Work in Progress.
954 Loughney Informational [Page 17]
955 \f
956 RFC 4294 IPv6 Node Requirements April 2006
959 13. Authors and Acknowledgements
961 This document was written by the IPv6 Node Requirements design team:
963 Jari Arkko
964 [jari.arkko@ericsson.com]
966 Marc Blanchet
967 [marc.blanchet@viagenie.qc.ca]
969 Samita Chakrabarti
970 [samita.chakrabarti@eng.sun.com]
972 Alain Durand
973 [alain.durand@sun.com]
975 Gerard Gastaud
976 [gerard.gastaud@alcatel.fr]
978 Jun-ichiro itojun Hagino
979 [itojun@iijlab.net]
981 Atsushi Inoue
982 [inoue@isl.rdc.toshiba.co.jp]
984 Masahiro Ishiyama
985 [masahiro@isl.rdc.toshiba.co.jp]
987 John Loughney
988 [john.loughney@nokia.com]
990 Rajiv Raghunarayan
991 [raraghun@cisco.com]
993 Shoichi Sakane
994 [shouichi.sakane@jp.yokogawa.com]
996 Dave Thaler
997 [dthaler@windows.microsoft.com]
999 Juha Wiljakka
1000 [juha.wiljakka@Nokia.com]
1002 The authors would like to thank Ran Atkinson, Jim Bound, Brian
1003 Carpenter, Ralph Droms, Christian Huitema, Adam Machalek, Thomas
1004 Narten, Juha Ollila, and Pekka Savola for their comments.
1010 Loughney Informational [Page 18]
1011 \f
1012 RFC 4294 IPv6 Node Requirements April 2006
1015 Editor's Contact Information
1017 Comments or questions regarding this document should be sent to the
1018 IPv6 Working Group mailing list (ipv6@ietf.org) or to:
1020 John Loughney
1021 Nokia Research Center
1022 Itamerenkatu 11-13
1023 00180 Helsinki
1024 Finland
1026 Phone: +358 50 483 6242
1027 EMail: John.Loughney@Nokia.com
1066 Loughney Informational [Page 19]
1067 \f
1068 RFC 4294 IPv6 Node Requirements April 2006
1071 Full Copyright Statement
1073 Copyright (C) The Internet Society (2006).
1075 This document is subject to the rights, licenses and restrictions
1076 contained in BCP 78, and except as set forth therein, the authors
1077 retain all their rights.
1079 This document and the information contained herein are provided on an
1080 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
1081 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
1082 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
1083 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
1084 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
1085 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1087 Intellectual Property
1089 The IETF takes no position regarding the validity or scope of any
1090 Intellectual Property Rights or other rights that might be claimed to
1091 pertain to the implementation or use of the technology described in
1092 this document or the extent to which any license under such rights
1093 might or might not be available; nor does it represent that it has
1094 made any independent effort to identify any such rights. Information
1095 on the procedures with respect to rights in RFC documents can be
1096 found in BCP 78 and BCP 79.
1098 Copies of IPR disclosures made to the IETF Secretariat and any
1099 assurances of licenses to be made available, or the result of an
1100 attempt made to obtain a general license or permission for the use of
1101 such proprietary rights by implementers or users of this
1102 specification can be obtained from the IETF on-line IPR repository at
1103 http://www.ietf.org/ipr.
1105 The IETF invites any interested party to bring to its attention any
1106 copyrights, patents or patent applications, or other proprietary
1107 rights that may cover technology that may be required to implement
1108 this standard. Please address the information to the IETF at
1109 ietf-ipr@ietf.org.
1111 Acknowledgement
1113 Funding for the RFC Editor function is provided by the IETF
1114 Administrative Support Activity (IASA).
1122 Loughney Informational [Page 20]
1123 \f