draft-ietf-ospf-transition-to-ospfv3-08.txt   draft-ietf-ospf-transition-to-ospfv3-09.txt 
Internet Draft I. Chen Internet Draft I. Chen
<draft-ietf-ospf-transition-to-ospfv3-08.txt> Ericsson <draft-ietf-ospf-transition-to-ospfv3-09.txt> Ericsson
Intended Status: Standards Track A. Lindem Intended Status: Standards Track A. Lindem
Updates: 5838 Cisco Updates: 5838 Cisco
R. Atkinson R. Atkinson
Consultant Consultant
Expires in 6 months June 13, 2016 Expires in 6 months June 17, 2016
OSPFv3 over IPv4 for IPv6 Transition OSPFv3 over IPv4 for IPv6 Transition
<draft-ietf-ospf-transition-to-ospfv3-08.txt> <draft-ietf-ospf-transition-to-ospfv3-09.txt>
Status of this Memo Status of this Memo
Distribution of this memo is unlimited. Distribution of this memo is unlimited.
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 6, line 18 skipping to change at page 6, line 18
address for the interface over which the packet is transmitted. address for the interface over which the packet is transmitted.
All OSPFv3 routers on the link SHOULD share the same IPv4 subnet All OSPFv3 routers on the link SHOULD share the same IPv4 subnet
for IPv4 transport to function correctly. for IPv4 transport to function correctly.
While OSPFv2 operates on a subnet, OSPFv3 operates on a link While OSPFv2 operates on a subnet, OSPFv3 operates on a link
[RFC5340]. Accordingly, an OSPFv3 router implementation MAY [RFC5340]. Accordingly, an OSPFv3 router implementation MAY
support adjacencies with OSPFv3 neighbors on different IPv4 support adjacencies with OSPFv3 neighbors on different IPv4
subnets. If this is supported, the IPv4 data plane MUST resolve subnets. If this is supported, the IPv4 data plane MUST resolve
IPv4 addresses to layer-2 addresses using Address Resolution IPv4 addresses to layer-2 addresses using Address Resolution
Protocol (ARP) on multi-access networks and point-to-point over LAN Protocol (ARP) on multi-access networks and point-to-point over LAN
[RFC5309] for direct next-hops on different IPv4 subnets. [RFC5309] for direct next-hops on different IPv4 subnets. When
OSPFv3 adjacencies on different IPv4 subnets are supported,
Bidirectional Forwarding Detection (BFD) [RFC5881] cannot be used
for adjacency loss detection since BFD is restricted to a single
subnet.
3.2. Destination Address 3.2. Destination Address
As defined in OSPFv2, the IPv4 destination address of an OSPF As defined in OSPFv2, the IPv4 destination address of an OSPF
protocol packet is either an IPv4 multicast address or the IPv4 protocol packet is either an IPv4 multicast address or the IPv4
unicast address of an OSPFv2 neighbor. Two well-known link-local unicast address of an OSPFv2 neighbor. Two well-known link-local
multicast addresses are assigned to OSPFv2, the AllSPFRouters multicast addresses are assigned to OSPFv2, the AllSPFRouters
address (224.0.0.5) and the AllDRouters address (224.0.0.6). The address (224.0.0.5) and the AllDRouters address (224.0.0.6). The
multicast address used depends on the OSPF packet type, the OSPF multicast address used depends on the OSPF packet type, the OSPF
interface type, and the OSPF router's role on multi-access interface type, and the OSPF router's role on multi-access
skipping to change at page 9, line 21 skipping to change at page 9, line 25
R. Aggarwal, "Support of Address Families in OSPFv3", RFC R. Aggarwal, "Support of Address Families in OSPFv3", RFC
5838, April 2010. 5838, April 2010.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5309] Shen, N., Ed., and A. Zinin, Ed., "Point-to-Point [RFC5309] Shen, N., Ed., and A. Zinin, Ed., "Point-to-Point
Operation over LAN in Link State Routing Protocols", RFC Operation over LAN in Link State Routing Protocols", RFC
5309, October 2008. 5309, October 2008.
[RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, DOI
10.17487/RFC5881, June 2010.
8.2. Informative References 8.2. Informative References
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271, January Border Gateway Protocol 4 (BGP-4)", RFC 4271, January
2006. 2006.
[RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains
via IPv4 Clouds", RFC 3056, February 2001. via IPv4 Clouds", RFC 3056, February 2001.
[RFC5613] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D. [RFC5613] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D.
 End of changes. 5 change blocks. 
4 lines changed or deleted 12 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/