Network Working Group M. Boucadair
Internet-Draft C. Jacquenet
Intended status: Standards Track France Telecom
Expires: April 23, 2010 D. Cheng
Huawei
Y. Lee
Comcast
October 20, 2009
IPv4-mapped IPv6 Instance IDs in OSPFv3
draft-boucadair-ospf-v4v6-ospfv3-mi-01
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 23, 2010.
Copyright Notice
Boucadair, et al. Expires April 23, 2010 [Page 1]
Internet-Draft IPv4 Mapped IPv6 Instance ID October 2009
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract
This memo defines two new Instance Identifiers (Instance IDs) in
OSPFv3 [RFC2740]). These new Instance IDs [I-D.ietf-ospf-af-alt] are
meant to instantiate distinct OSPFv3 instances to convey routing
information which is specific to IPv4-mapped IPv6 address Address
Family [I-D.ietf-behave-address-format]. The goal of running
separate instances for IPv4-mapped IPv6 is to distinguish the native
IPv6 routing topology from the IPv4 routing topology. Separate
instances are also meant to prevent any overload of the native IPv6
routing tables by IPv4-mapped IPv6 routes. This isolation is
motivated also from an operational perspective to enforce specific
routing policies for each topology.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Boucadair, et al. Expires April 23, 2010 [Page 2]
Internet-Draft IPv4 Mapped IPv6 Instance ID October 2009
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
Boucadair, et al. Expires April 23, 2010 [Page 3]
Internet-Draft IPv4 Mapped IPv6 Instance ID October 2009
1. Introduction
[I-D.ietf-ospf-af-alt] specifies a mechanism to map each address
family (AF) to a separate OSPFv3 [RFC2740] Instance identified by an
ID. Many Instance IDs have been reserved for different AF (e.g.,
Instance ID #0 - #31 for IPv6 unicast AF, Instance ID#32 - #63 for
IPv6 multicast AF, etc.). Instance ID #0 is used by default for IPv6
unicast AF. This document requests to assign two new Instance IDs
for the IPv4-mapped IPv6 AF. They are:
o Unicast IPv4-mapped IPv6 AF;
o Multicast IPv4-mapped IPv6 AF.
Within the double context of IPv4 address exhaustion and the IPv6-
IPv4 interconnection, numerous solutions are being elaborated within
IETF. Both translation (e.g., [I-D.ietf-behave-v6v4-xlate-stateful]
and [I-D.ietf-behave-v6v4-xlate]) and encapsulation (e.g.,
[I-D.boucadair-dslite-interco-v4v6] and
[I-D.boucadair-behave-ipv6-portrange]) schemes are proposed to
facilitate IPv6-IPv4 interconnection. These solutions require the
injection of routes to IPv4-mapped IPv6
[I-D.ietf-behave-address-format] destinations in intra-domain routing
protocols. In order to prevent any overload of the native IPv6
routing table with IPv4-mapped IPv6 routes, this memo defines new
Instance IDs which are required for the activation of several OSPFv3
instances for unicast/multicast IPv4- inferred IPv6 route computation
purposes. This isolation is also motivated for operational reasons
and to ease the migration to full IPv6. As a result, when a separate
OSPFv3 instance for unicast IPv4-mapped IPv6 AF is activated, a
separate OSPFv3 topology is calculated. Likewise, when a separate
OSPFv3 instance for multicast IPv4- inferred IPv6 AF is activated,
another distinct OSPFv3 topology is computed.
In order to prevent from polluting the native IPv6 routing table with
IPv4-mapped IPv6 routes, this memo defines new Instance IDs which are
required for the activation of several OSPFv3 instances for unicast/
multicast IPv4-mapped IPv6. This isolation is also motivated for
operational reasons and to ease the migration to full IPv6. As a
result, when a separate OSPFv3 instance for unicast IPv4-mapped IPv6
AF is activated, there creates a separate OSPFv3 topology based on
which unicast IPv4-mapped IPv6 routing is calculated and performed,
and similarly, when a separate OSPFv3 instance for multicast IPv4-
mapped IPv6 AF is activated, there creates a separate OSPFv3 topology
for multicast IPv4-mapped IPv6 routing.
As a reminder, [I-D.ietf-ospf-mt-ospfv3] specifies a mechanism to
maintain multiple OSPFv3 topologies within the same domain. This
Boucadair, et al. Expires April 23, 2010 [Page 4]
Internet-Draft IPv4 Mapped IPv6 Instance ID October 2009
memo does not make any preference between the solution described in
[I-D.ietf-ospf-mt-ospfv3] and [I-D.ietf-ospf-af-alt]. Network
administrators have to make their decisions based on local policies
and preferences. If the multi-instance mechanism
[I-D.ietf-ospf-af-alt] is deployed in an OSPFv3 network as a
preference for multiple topologies, the extensions defined in this
memo may be used to support unicast/multicast IPv4-mapped IPv6
routing.
2. Procedure
This document does not require any modification to the procedure
specified in [I-D.ietf-ospf-af-alt]. Nevertheless, only routes to
IPv4-mapped IPv6 prefixes MUST be instantiated within a IPv4-mapped
IPv6 routing MI-OSPFv3. Concretely, the IANA prefix defined in
[I-D.ietf-behave-address-format] MUST be supported by default.
Service providers MAY also choose a LIR prefix to build the IPv4-
mapped IPv6 addresses.
3. Forwarding
Only incoming datagrams destined to IPv4-mapped IPv6 addresses are
associated (and therfore forwarded according to) with the IPv4-mapped
IPv6 unicast/multicast OSPFv3 Instance, respectively. WKP and/or LIR
prefix defined in [I-D.ietf-behave-address-format] MUST be configured
in all participating nodes.
4. IANA Considerations
This document requests the following OSPFv3 Instance IDs:
o Instance ID# for IPv4-mapped IPv6 unicast AF;
o Instance ID# for multicast IPv4-mapped IPv6 AF.
5. Security Considerations
This document does not introduce any security issue in addition to
those defined in [RFC2740].
6. Acknowledgements
TBC
Boucadair, et al. Expires April 23, 2010 [Page 5]
Internet-Draft IPv4 Mapped IPv6 Instance ID October 2009
7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2740] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6",
RFC 2740, December 1999.
7.2. Informative References
[I-D.boucadair-behave-ipv6-portrange]
Boucadair, M., Levis, P., Grimault, J., Villefranque, A.,
Kassi-Lahlou, M., Bajko, G., Lee, Y., and T. Melia,
"Flexible IPv6 Migration Scenarios in the Context of IPv4
Address Shortage",
draft-boucadair-behave-ipv6-portrange-03 (work in
progress), October 2009.
[I-D.boucadair-dslite-interco-v4v6]
Boucadair, M., Jacquenet, C., Grimault, J., Kassi-Lahlou,
M., Levis, P., Cheng, D., and Y. Lee, "Deploying Dual-
Stack lite in IPv6-only Network",
draft-boucadair-dslite-interco-v4v6-02 (work in progress),
October 2009.
[I-D.ietf-behave-address-format]
Huitema, C., Bao, C., Bagnulo, M., Boucadair, M., and X.
Li, "IPv6 Addressing of IPv4/IPv6 Translators",
draft-ietf-behave-address-format-00 (work in progress),
August 2009.
[I-D.ietf-behave-v6v4-xlate]
Li, X., Bao, C., and F. Baker, "IP/ICMP Translation
Algorithm", draft-ietf-behave-v6v4-xlate-01 (work in
progress), September 2009.
[I-D.ietf-behave-v6v4-xlate-stateful]
Bagnulo, M., Matthews, P., and I. Beijnum, "NAT64: Network
Address and Protocol Translation from IPv6 Clients to IPv4
Servers", draft-ietf-behave-v6v4-xlate-stateful-02 (work
in progress), October 2009.
[I-D.ietf-ospf-af-alt]
Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R.
Aggarwal, "Support of address families in OSPFv3",
draft-ietf-ospf-af-alt-08 (work in progress), July 2009.
Boucadair, et al. Expires April 23, 2010 [Page 6]
Internet-Draft IPv4 Mapped IPv6 Instance ID October 2009
[I-D.ietf-ospf-mt-ospfv3]
Mirtorabi, S. and A. Roy, "Multi-topology routing in
OSPFv3 (MT-OSPFv3)", draft-ietf-ospf-mt-ospfv3-03 (work in
progress), July 2007.
Authors' Addresses
Mohamed Boucadair
France Telecom
3, Av Francois Chateau
Rennes, 35000
France
Email: mohamed.boucadair@orange-ftgroup.com
Christian Jacquenet
France Telecom
3, Av Francois Chateau
Rennes, 35000
France
Email: christian.jacquenet@orange-ftgroup.com
Dean Cheng
Huawei
USA
Email: Chengd@huawei.com
Yiu L. Lee
Comcast
USA
Email: Yiu_Lee@Cable.Comcast.com
Boucadair, et al. Expires April 23, 2010 [Page 7]