Internet DRAFT - draft-liu-i2rs-ipv6-use-case
draft-liu-i2rs-ipv6-use-case
I2RS D. Liu
Internet-Draft China Mobile
Intended status: Informational July 15, 2013
Expires: January 16, 2014
I2RS use case for IPv6 transition
draft-liu-i2rs-ipv6-use-case-00
Abstract
This document discusses the use cases of I2RS in IPv4/IPv6 transition
scenario.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on January 16, 2014.
Copyright Notice
Copyright (c) 2013 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
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Liu Expires January 16, 2014 [Page 1]
Internet-Draft i2rs IPv6 use case July 2013
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions used in this document . . . . . . . . . . . . . . 2
3. Use case of I2RS in IPv4/IPv6 transition scenario . . . . . . 2
3.1. I2RS use case for IPv4/IPv6 dual-stack network . . . . . 2
3.2. I2RS use case in IPv4 and IPv6 translation scenario . . . 3
3.3. Requirement for I2RS from the use case . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
I2RS working group is chartered to define an interface to the routing
system. This interface can be used to read topology and forwarding
information of the routing system. This document discusses the use
cases of I2RS in IPv4/IPv6 transition scenario.
2. Conventions used in this document
RIB: Routing Information Base
I2RS: Interface to Routing System
3. Use case of I2RS in IPv4/IPv6 transition scenario
3.1. I2RS use case for IPv4/IPv6 dual-stack network
There are several different ways for IPv4/IPv6 transition. For
example, dual-stack is one popular technology to enable IPv4 to IPv6
transition. In dual-stack network, every router has both IPv4 and
IPv6 IP stack running on it. The IPv4 and IPv6 protocol stack
running on the dual-stack router normally work independently from
each other although they share the same physical resources in the
dual-stack router(CPU,memory etc). There are two different views of
the dual-stack network from the IPv4 or IPv6 perspective. There are
different set of routing information base for IPv4 and IPv6. In most
cases, the IPv4 and IPv6 network need to have the same topology and
forwarding state since they normally serves for the same dusal-stack
host.
Liu Expires January 16, 2014 [Page 2]
Internet-Draft i2rs IPv6 use case July 2013
+------------+
| Dual-stack |
+-------| Router |-------
/ +------------+ \
+----------+ +-----------+
+----+ |Dual-stack| | Dual-stack|
|Host|-------| Router | | Router |
+----+ +----------+ +-----------+
\ |
\ +------------+ /
+--------| Dual-stack |-------+
| Router |
+------------+
Figure 1. IPv4/IPv6 Dual-stack network for IPv4/IPv6 transition
It is a big challenge for the operators to operate dual-stack
network, there are several reasons: 1. The network operation and
management team may not familiar with IPv6. They have to learn new
knowledge and new tools for IPv6. 2. There are two separate domains
of the IPv4 and IPv6 network, the trouble shooting will become much
more complex than single stack network. 3. Since the IPv4 and IPv6
stack share a single physical router, the problem of one protocol
stack may spread to the other stack.
With I2RS, it can help the network operator to maintain a consistent
view of both the IPv4 and IPv6 network in real time. The network
operator can even configure the IPv6 network based on the existing
IPv4 network and make the IPv4 network and the IPv6 have the same
topology and forwarding state. This will reduce the complexity of
operation and management and help the network operator discovery the
in-consistent between the IPv4 and IPv6 network quickly.
3.2. I2RS use case in IPv4 and IPv6 translation scenario
In IPv4 and IPv6 translation scenario, the IPv4/IPv6 network's
packets will be translated in to IPv4/IPv6 network's packets and vice
versa. It is difficult for the network management system to get a
consistent view of the translated network.
Liu Expires January 16, 2014 [Page 3]
Internet-Draft i2rs IPv6 use case July 2013
+--------------+ +----------------+
+----+ | | +---------------+ | |
|Host|-------|IPv4/6 network|---|Translation box|---| IPv6/4 network |
+----+ | | +---------------+ | |
+--------------+ +----------------+
Figure 2. IPv4/IPv6 translation network for IPv4/IPv6 transition
It is difficult for the current network management system to get IPv4
and IPv6 network topology and routing information simultaneously.
With I2RS, it can provide a flexible way to get both IPv4 and IPv6
network topology and other information, hence it could be very useful
for trouble shooting and network management.
3.3. Requirement for I2RS from the use case
From the above use case, the requirements for I2RS are: 1. I2RS
interface should support both IPv4 and IPv6. It should be able to
read both IPv4 and IPv6 routing information in a timely manner. 2.
I2RS interface should have enough security mechanism to protect the
data that read from the routing information base. 3. I2RS interface
should have data consistent protection mechanism to protect the data
in the routing information base. 4. I2RS interface should allow
injection of routing polices to the routing forwarding table.
4. Security Considerations
Routing information is very critical and sensitive information for
the operators. I2RS should provide strong security mechanism to
protect the routing information that it could not be accessed by the
un-authorised users. It should also protect the security and
integrity protection of the routing data.
5. IANA Considerations
No IANA action is required.
6. Acknowledgments
TBD
Liu Expires January 16, 2014 [Page 4]
Internet-Draft i2rs IPv6 use case July 2013
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.
7.2. Informative References
[I-D.atlas-irs-ps]
Atlas, A., "Interface to the Routing System Problem
Statement", draft-atlas-i2rs-problem-statement-01 (work in
progress), February 2013.
[RFC4213] Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms
for IPv6 Hosts and Routers", RFC 4213, October 2005.
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful
NAT64: Network Address and Protocol Translation from IPv6
Clients to IPv4 Servers", RFC 6146, April 2011.
Author's Address
Dapeng Liu
China Mobile
Unit2, 28 Xuanwumenxi Ave,Xuanwu District
Beijing 100053
China
Email: liudapeng@chinamobile.com
Liu Expires January 16, 2014 [Page 5]
