IPV6 RFCs and Compliance - Radware

19
Radware ADC IPV6 RFCs and Compliance Knowledgebase Team February 2016

Transcript of IPV6 RFCs and Compliance - Radware

IPV6 RFCs and ComplianceScope:
This document lists most of the RFCs that relevant to IPv6. Legend: Yes – supported RFC N/A – not applicable No – Currently not supported RFC Relevance: This RFC list is relevant for:
Alteon 28.x and later
Alteon 29.x and later
Alteon 30.x and later
AppDirector 2.30 and later
LinkProof 6.0 and later
Title App Director
Formats and Addresses
2460 IPv6 Specification Yes Yes Yes Specifies the IP header structure
4291 3513 IPv6 Addressing Architecture
Yes Yes Yes Defines the addressing architecture.
3587 2374 Global Unicast address format
Yes Yes Yes Defines the IPv6 address allocation structure.
Obsoletes the imposed hierarchy on the global Unicast addresses
6177 3177 IAB/IESG recommendations on IPv6 address allocations to sites
N/A N/A N/A Recommends allocation of 48 and 64-bit prefixes per specific cases
Informational RFC
No No No Reserves Mobile IP home agent Anycast addresses
3986 URI Generic Syntax
Page 4
Title App Director
Alteon LinkProof RFC content Comment
3879 Deprecating site- local addresses
Yes Yes Yes Describes the issues surrounding the use of IPv6 site-local unicast addresses in their original form, and formally deprecates them.
4193 Unique local IPv6 Unicast addresses
Yes Yes Yes Replaces site local addresses.
3849 IPv6 address prefix reserved for documentation
N/A N/A N/A Prefixes to be used for examples in documents
2375 Multicast address assignment
Yes* Yes* Yes* Specifies Multicast address group prefixes for common cases.
Supported only the Multicast addresses that are required for Neighbor discovery (ND), Router Discovery
Page 5
Title App Director
(RD) and Stateless address auto- configuration (SLACC).
5156 Special-use IPv6 addresses
Yes Yes Yes Summarizes the special address prefixes from other RFCs.
Informational RFC
IP Networking
4861 2461 Neighbor discovery
Yes Yes Yes specifies the Neighbor Discovery protocol for IP Version 6.
4862 2462 Stateless address auto- configuration
Yes Yes Yes Specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6
4443 2463 ICMPv6 Yes Yes Yes Neighbor discovery (ND), Router Discovery (RD),
Page 6
Title App Director
Echo, Errors (incl. MTU), link multicast group.
3315 4361
Dynamic Host Configuration Protocol Version Four (DHCPv4)
N/A N/A N/A Specifies the format that is to be used for encoding Dynamic Host Configuration Protocol Version Four (DHCPv4) client identifiers, so that those identifiers will be interchangeable with identifiers used in the DHCPv6 protocol
3633 IPv6 prefix options for DHCPv6
N/A N/A N/A Prefix delegation mechanism.
3736 Stateless Dynamic Host Configuration Protocol (DHCP)
N/A N/A N/A DHCP service without maintaining state per client
Page 7
Title App Director
Service for IPv6
1981 Path MTU discovery
Yes Yes Yes Describes Path MTU Discovery for IP version 6. It is largely derived from RFC 1191, which describes Path MTU Discovery for IP
version 4.
3178 IPv6 Multi- homing support at site with exit routers
No No No Mechanism for basic IPv6 multihoming support, and its operational requirements. The method relies on routing protocol (BGP or RIPng) for optimal route selection.
Informational TFC
Page 8
Title App Director
than 64 KB
2711 IPv6 router alert option
No No No Alert to suggest the router look at the payload.
4007 IPv6 scoped address architecture
Yes Yes Yes Specifies the way local and global addresses are used.
5095 Deprecation of type 0 routing headers in IPv6
Yes Yes Yes Deprecates type 0
The only type of routing header specified in RFC 2460.
3484 Default address selection
Yes Yes Yes Selects source and destination address pair in case there are multiple addresses on each side.
4192 Default router preferences
No No No Extends router advertisement protocol with preferences in order for the host to select the best router
Page 9
Title App Director
for a given destination.
4311 Host to router load sharing
No No No Guidance on how to share load among equivalent routers
4941 3041 Privacy extensions for Stateless address auto- configuration in IPv6
No No No Adapt to anonymous addresses that have short lifespan
3646 DNS configuration options for DHCPv6
No No No
3122 Inverse neighbor discovery
No No No Retrieves a neighbor’s IP given its MAC address.
2474 Definition of the DS-field in IPv4 and IPv6 headers
No No No Per hop behavior as defined by the DS field.
1809 Using the flow label field in IPv6
No No No Flow label is used for IntServ QoS: guaranteeing
Informational RFC
Page 10
Title App Director
Alteon LinkProof RFC content Comment
QoS per specific connection (flow)
2894 Router renumbering for IPv6
No No No Support dynamic changes in the prefixes allocated by routers. Might be relevant for LinkProof.
4864 Local network protection for IPv6
N/A N/A N/A Techniques to achieve NAT benefits without NAT in IPv6.
Informational RFC.
No Yes Yes Replaces VRRPv2 which was solely for IPv4
IPv6 over Link Layer
2464 IPv6 over Ethernet
Upper layers over IPv6
Title App Director
3596 1886 DNS extensions for IPv6
Yes Yes Yes
2874 DNS extensions to support IPv6 address aggregation and renumbering
No No No A6 record for part of the IPv6 address
3363 Representing IPv6 addresses in DNS
N/A N/A N/A Informational RFC
3364 Tradeoffs in DNS for IPv6
N/A N/A N/A Informational RFC
3901 DNS IPv6 transport operational guidelines
Yes Yes
Yes BCP
4074 Common misbehavior against DNS queries for IPv6 addresses
Yes Yes Yes Return 0 answers rather than “name error” on A record request when only AAAA exists and vice versa.
Informational RFC
Page 12
Title App Director
modifications for IPv6
2080 RIPng for IPv6 No No No
2428 FTP extensions for IPv6 and NATs
Yes No Yes Specifies extensions to FTP that will allow the protocol to work over IPv4 and IPv6.
4760 Multiprotocol Extensions for BGP-4
No No No General RFC which relates to IPv6 among others
2545 Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-domain routing
No No No How the extensions of RFC 4760 are used in IPv6
2740 OSPF for IPv6 No Yes. (Starting from Alteon 29.x)
No
4286 Multicast Routing Discovery
Page 13
Title App Director
routers that support Multicast.
No No No
4293 2011, 2465, 2466
MIB for IP Yes No Yes Unified RFCs for both IPv4 and IPv6
4292 IP Forwarding Table MIB
Yes No Yes Both IPv4 and IPv6
4022 MIB for TCP No No No
4113 MIB for UDP No No No
3019 IPv6 MIB for multicast listener discovery
No No No
4001 Textual conventions for Internet network addresses
Yes No Yes Defines the format for IP addresses and prefixes. The
Page 14
Title App Director
Mobile IPv6 (MIPv6)
No No No
No No No
No No No
3776, 4877 Using IPSec to protect MIPv6 signaling between Mobile Nodes and HA
No No No
Yes* Yes* No Discusses dual stack and tunneling.
Radware ADCs implement the dual stack only.
6145 2765 IP/ICMP Translation
Not supported
Page 15
Title App Director
Alteon LinkProof RFC content Comment
Algorithm for IP and ICMP headers (L3). We took the proxy (L4) approach to achieve the same goal. (RFC 3142).
starting from Alteon version 28.1
2766 NAT-PT No No No Translation gateway. Role assumed by router.
The RFC is in “historic” status and its use is discouraged but not deprecated, since there is no alternative for it.
4966 Reasons to Move the Network Address Translator - Protocol Translator (NAT- PT) to Historic Status
N/A N/A N/A See RFC 2766 above.
6144 Framework for IPv4/IPv6
Title App Director
Translation different translation scenarios replacing NAT- PT.
AppDirector and Alteon implement the framework described in this RFC based on transport relay translator (TRT - RFC 3142) rather than SIIT (RFC 6145
2767 Dual stack hosts using Bump in Stack techniques (BIS)
No No No
No No No Translation between L7 and dual TCP/IP stack.
3142 IPv6 to IPv4 transport relay translator (TRT)
Yes Yes* No Translation at L4 level.
Supported by Alteon starting from 28.1 version.
2473 Generic packet tunneling in IPv6
No No No
Title App Director
specification
No No No
No No No 6 to 4 tunnels.
4659 BGP-MPLS IP VPN extension for IPv6 VPN
No No No
5211 Internet Transition Plan
N/A N/A N/A Proposes a plan for transition of the core Internet to IPv6.
Informational RFC
5969 6rd Protocol Specification
No No No Uses 6to4 but with the ISP’s IPv6 prefix, rather than the well-known 6to4 prefix.
6146 Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to
No No* No
*Will be Supported by Alteon in Future version
Page 18
Title App Director
Alteon LinkProof RFC content Comment
IPv4 Servers clients to contact IPv4 servers using unicast UDP, TCP, or ICMP.
6147 DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers.
No No* No Specifies DNS64, and provides suggestions on how it should be deployed in conjunction withIPv6/ IPv4 translators.
Will be Supported by Alteon in Future version
6296 IPv6-to-IPv6 Network Prefix Translation
No No No* *LP implements similar behavior without CRC preservation after translation
General
Page 19