Network Working Group M. Boucadair
Internet-Draft C. Jacquenet
Intended status: Standards Track France Telecom
Expires: April 22, 2010 D. Cheng
Huawei
Y. Lee
Comcast
October 19, 2009
IPv4-mapped IPv6 Instance IDs in IS-IS
draft-boucadair-isis-v4v6-mi-00
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 22, 2010.
Copyright Notice
Boucadair, et al. Expires April 22, 2010 [Page 1]
Internet-Draft IPv4 Mapped IPv6 IS-IS 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
IS-IS [RFC1195]). These new Instance IDs [I-D.ietf-isis-mi] are
meant to instantiate distinct IS-IS instances to convey routing
information which is restricted to IPv4-mapped IPv6 addresses
[I-D.ietf-behave-address-format]. The ultimate goal of running
separate instances for IPv4-mapped IPv6 is to isolate the native IPv6
routing table from the IPv4 and to prevent to be overloaded by IPv4-
mapped one. This isolation is motivated also from an operational
perspective to allow specific engineering policies for each instance.
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 22, 2010 [Page 2]
Internet-Draft IPv4 Mapped IPv6 IS-IS Instance ID October 2009
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
Boucadair, et al. Expires April 22, 2010 [Page 3]
Internet-Draft IPv4 Mapped IPv6 IS-IS Instance ID October 2009
1. Introduction
[I-D.ietf-isis-mi] specifies a mechanism to map each address family
to a separate IS-IS [RFC1195] Instance identified by an ID. Accepted
ID values are 0 to 65535. Instance ID#0 is used by default (legacy
systems). This document requests the assignment of two new MI-IS-IS
Instance IDs for the following usages:
o Unicast IPv4-mapped IPv6 IS-IS routing instance;
o Multicast IPv4-mapped IPv6 IS-IS routing instance.
In the context of IPv4 address exhaustion and the IPv6-IPv4
interconnection, numerous solutions are currently 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]) based schemes are proposed to
allow IPv6-IPv4 interconnection. These solutions require injecting
in intra-domain routing protocols routes to IPv4-mapped IPv6
[I-D.ietf-behave-address-format] destinations. 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 IS-IS 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 IS-IS instance for unicast IPv4-mapped IPv6 address family
is activated, there creates a separate IS-IS adjacency table based on
which unicast IPv4-mapped IPv6 routing is calculated and performed,
and similarly, when a separate IS-IS instance for multicast IPv4-
mapped IPv6 address family is activated, there creates a separate
IS-IS adjacency table for multicast IPv4-mapped IPv6 routing.
In case [RFC5120] is deployed, new Multi Topology IDs are required to
be defined. As a reminder, [RFC5120] specifies an alternative
mechanism to maintain multiple IS-IS topologies within the same IS-IS
domain. This memo does not make any preference between the solution
described in [RFC5120] and [I-D.ietf-isis-mi]. Network
administrators have to make their decisions based on local policies
and preferences. If multi-instance mechanism [I-D.ietf-isis-mi] is
deployed in an IS-IS network as a preference for multiple topologies,
the extensions as defined in this memo may be used to support
unicast/multicast IPv4-mapped IPv6 routing, respectively.
2. Procedure
This document does not require any modification to the procedure
Boucadair, et al. Expires April 22, 2010 [Page 4]
Internet-Draft IPv4 Mapped IPv6 IS-IS Instance ID October 2009
specified in [I-D.ietf-isis-mi]. Nevertheless, only routes to IPv4-
mapped IPv6 prefixes MUST be instantiated within a IPv4-mapped IPv6
routing M-ISIS Concretely, the IANA's prefix defined in
[I-D.ietf-behave-address-format] MUST be supported by default.
Service providers MAY choose a LIR prefix to build the IPv4-mapped
IPv6 addresses.
3. Forwarding
Only incoming datagrams destined to IPv4-mapped IPv6 addresses are
associated with the IPv4-mapped IPv6 unicast/multicast IS-IS
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 IS-IS 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 [I-D.ietf-isis-mi].
6. Acknowledgements
TBC
7. References
7.1. Normative References
[RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and
dual environments", RFC 1195, December 1990.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi
Boucadair, et al. Expires April 22, 2010 [Page 5]
Internet-Draft IPv4 Mapped IPv6 IS-IS Instance ID October 2009
Topology (MT) Routing in Intermediate System to
Intermediate Systems (IS-ISs)", RFC 5120, February 2008.
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-isis-mi]
Previdi, S., Ginsberg, L., Shand, M., Ward, D., and A.
Roy, "IS-IS Multi-Instance", draft-ietf-isis-mi-02 (work
in progress), October 2009.
Boucadair, et al. Expires April 22, 2010 [Page 6]
Internet-Draft IPv4 Mapped IPv6 IS-IS Instance ID October 2009
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 22, 2010 [Page 7]