draft-ietf-ospf-ipv4-embedded-ipv6-routing-10.txt   draft-ietf-ospf-ipv4-embedded-ipv6-routing-11.txt 
Network Working Group D. Cheng Network Working Group D. Cheng
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Informational M. Boucadair Intended status: Informational M. Boucadair
Expires: October 14, 2013 France Telecom Expires: October 19, 2013 France Telecom
A. Retana A. Retana
Cisco Systems Cisco Systems
April 12, 2013 April 17, 2013
Routing for IPv4-embedded IPv6 Packets Routing for IPv4-embedded IPv6 Packets
draft-ietf-ospf-ipv4-embedded-ipv6-routing-10 draft-ietf-ospf-ipv4-embedded-ipv6-routing-11
Abstract Abstract
This document describes routing packets destined to IPv4-embedded This document describes routing packets destined to IPv4-embedded
IPv6 addresses across an IPv6 core using OSPFv3 with a separate IPv6 addresses across an IPv6 core using OSPFv3 with a separate
routing table. routing table.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 14, 2013. This Internet-Draft will expire on October 19, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 8, line 11 skipping to change at page 8, line 11
described in Section 3.3 and Section 3.4, respectively. described in Section 3.3 and Section 3.4, respectively.
3.3. OSPFv3 Topology with a Separate Instance ID 3.3. OSPFv3 Topology with a Separate Instance ID
It is assumed that the IPv6 network that is inter-connected with IPv4 It is assumed that the IPv6 network that is inter-connected with IPv4
networks in this document is under one administration and as such, an networks in this document is under one administration and as such, an
OSPFv3 instance ID (IID) is allocated locally and used for OSPFv3 OSPFv3 instance ID (IID) is allocated locally and used for OSPFv3
operation dedicated to unicast IPv4-embedded IPv6 routing in an IPv6 operation dedicated to unicast IPv4-embedded IPv6 routing in an IPv6
network. This IID is configured on OSPFv3 router interfaces that network. This IID is configured on OSPFv3 router interfaces that
participate in the IPv4-embedded IPv6 topology. participate in the IPv4-embedded IPv6 topology.
The range for a locally configured OSPFv3 IID is from 192 to 255, The range for a locally configured OSPFv3 IID is allocated from 192
inclusive, and this IID must be used to encode the "Instance ID" to 255, inclusive, as "Private Use" per
field in the packet header of OSPFv3 packets associated with the [I-D.ietf-ospf-ospfv3-iid-registry-update]. This IID must be used to
OSPFv3 instance. encode the "Instance ID" field in the packet header of OSPFv3 packets
associated with the OSPFv3 instance.
In addition, the "AF" bit in the OSPFv3 Option field MUST be set. In addition, the "AF" bit in the OSPFv3 Option field MUST be set.
During Hello packet processing, an adjacency may only be established During Hello packet processing, an adjacency may only be established
when the received Hello packet contains the same Instance ID as when the received Hello packet contains the same Instance ID as
configured on the receiving OSPFv3 interface. This insures that only configured on the receiving OSPFv3 interface. This insures that only
interfaces configured as part of the OSPFv3 unicast IPv4-embedded interfaces configured as part of the OSPFv3 unicast IPv4-embedded
IPv6 topology are used for IPv4-embedded IPv6 unicast routing. IPv6 topology are used for IPv4-embedded IPv6 unicast routing.
For more details, the reader is referred to [RFC5838]. For more details, the reader is referred to [RFC5838].
skipping to change at page 15, line 9 skipping to change at page 15, line 9
14. Acknowledgements 14. Acknowledgements
Many thanks to Acee Lindem, Dan Wing, Joel Halpern, Mike Shand and Many thanks to Acee Lindem, Dan Wing, Joel Halpern, Mike Shand and
Brian Carpenter for their comments. Brian Carpenter for their comments.
15. References 15. References
15.1. Normative References 15.1. Normative References
[I-D.ietf-ospf-ospfv3-iid-registry-update]
Retana, A. and D. Cheng, "OSPFv3 Instance ID Registry
Update", draft-ietf-ospf-ospfv3-iid-registry-update-02
(work in progress), February 2013.
[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.
[RFC4576] Rosen, E., Psenak, P., and P. Pillay-Esnault, "Using a [RFC4576] Rosen, E., Psenak, P., and P. Pillay-Esnault, "Using a
Link State Advertisement (LSA) Options Bit to Prevent Link State Advertisement (LSA) Options Bit to Prevent
Looping in BGP/MPLS IP Virtual Private Networks (VPNs)", Looping in BGP/MPLS IP Virtual Private Networks (VPNs)",
RFC 4576, June 2006. RFC 4576, June 2006.
[RFC5565] Wu, J., Cui, Y., Metz, C., and E. Rosen, "Softwire Mesh [RFC5565] Wu, J., Cui, Y., Metz, C., and E. Rosen, "Softwire Mesh
Framework", RFC 5565, June 2009. Framework", RFC 5565, June 2009.
 End of changes. 6 change blocks. 
8 lines changed or deleted 14 lines changed or added

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