One document matched: draft-xu-homenet-twod-ip-routing-00.txt
Network Working Group M. Xu
Internet-Draft S. Yang
Expires: August 5, 2013 J. Wu
Tsinghua University
D. Wang
Hong Kong Polytechnic University
Feb 2013
Two Dimensional-IP Routing Protocol in Home Networks
draft-xu-homenet-twod-ip-routing-00
Abstract
Home netowrk design faces many challenges currently. Two of them are
multi-homing and policy enforcement. Different with other types of
networks, home network operators are usually not professional
technicians or geeks. The problems we face are fundamentally related
with the poor semantics provided by current destination-based routing
protocol.
TwoD-IP routing protocol is a link state routing protocol that makes
routing decisions based on both destination and source addresses.
This document describes the mechanism for supporting flexible multi-
homing and policy routing across home networks.
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 August 5, 2013.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
Xu, et al. Expires August 5, 2013 [Page 1]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
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.
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.
Xu, et al. Expires August 5, 2013 [Page 2]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Scenario of Interests . . . . . . . . . . . . . . . . . . . . 6
3.1. Multi-homing in Home Networks . . . . . . . . . . . . . . 6
3.2. Access-control in Home Networks . . . . . . . . . . . . . 7
4. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 9
5. TwoD Link Metric Configuration . . . . . . . . . . . . . . . . 11
6. New Link State Advertisement/Database . . . . . . . . . . . . 13
7. Calculation of The Routing Table . . . . . . . . . . . . . . . 14
8. Forwarding Table Modification . . . . . . . . . . . . . . . . 15
9. Incremental Deployment . . . . . . . . . . . . . . . . . . . . 16
10. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 17
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
13.1. Normative References . . . . . . . . . . . . . . . . . . . 20
13.2. Informative References . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21
Xu, et al. Expires August 5, 2013 [Page 3]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
1. Introduction
With more and more devices join home networks, there are increasingly
large residential home networks. Traditionally, we keep home network
simple using single exit router (subnet) and default route. However,
more complex network technologies, such as multi-homing, appear when
the networks become large. Besides, users demand for more than
connectivity service, as varieties of devices like private health
sensors, exist in their home networks. For example, users want finer
granularity control for privacy and security reasons. While we can
not expect home network operators, who usually know nothing about
network technologies, to configure complex network policies using
tools like access control list (ACL). We need a simpler and more
flexible routing protocol in home networks.
Traditionally, routing protocols make routing decisions solely based
on destination IP addresses, packets towards the same destination
will be delivered to the same next hop no matter where they come
from. These protocols work well with simple home network. However,
as users demand for more source-related functions and network
techonologies evolve. Destination-based routing protocol can not
handle these demands, and even fail to provide the basic connectivity
services. For example, in the multi-homing scenario, packets may be
dropped if forwarded only based on destination addresses [1].
Although many patch-like solutions, like policy-based routing (PBR),
can improve the situation. However, they complex the configurations
in home networks, and are not suitable for home network operators.
The underlying cause for these problems is the lack of semantics of
destination-based routing. A new routing protocol that makes routing
decisions based on both destination and source IP addresses is
preferred in future home networks [3].
In this document, we propose a new link state routing protocol,
called Two Dimensional-IP (TwoD-IP) routing protocol, that greatly
enriches the routing semantics. We list two important scenarios,
including multi-homing and access control in home networks, where
TwoD-IP routing protocol will apply. We also use them as examples to
illustrate the new routing protocol.
We modify OSPF to support our TwoD-IP routing protocol. With one
more dimension, the routing protocol has to disseminate additional
information with newly defined LSAs, and compute a two dimensional
routing table based on the collected LSAs. Thus, we must design new
LSA packet formats, data structures and routing algorithm for the new
routing protocol.
Xu, et al. Expires August 5, 2013 [Page 4]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
2. Terminology
Terminology used in this document:
o TwoD-IP routing protocol: Two Dimensional IP routing protocol,
which makes routing decisions based on both destination and source
IP addresses.
o Guest Network: A subnet in a home network, that supports
communication with other subnets in the home network and the
Internet.
o Private Network: A subnet in a home network, that only supports
communication with other subnets in the home network.
o Restricted Network: A subnet in a home network, that supports
communication with other subnets in the home network and only
parts of the Internet.
o TwoD Traffic Class: We borror the definition from [4], which
describes it as a selector that identifies a set of traffic, e.g.,
from a stated source prefix and towards a stated destination
prefix.
o TwoD Link Metric: The cost of travelling through a link, for a
TwoD traffic class.
o TwoD-LSA: Link state advertisement that disseminates the TwoD link
metric information across the network.
o TwoD-LSB: Extended link state database that stores the TwoD-LSAs.
Xu, et al. Expires August 5, 2013 [Page 5]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
3. Scenario of Interests
This section describes two scenarios, including multi-homing and
policy routing, where TwoD-IP routing protocol will apply in home
networks. Note that TwoD-IP routing protocol can also apply in other
scenarios, despite we focus on two important ones.
3.1. Multi-homing in Home Networks
In this scenario, a home network may be connected to multiple
upstream ISPs. The network is responsible for delivering packets to
the exit router that is connected to the corresponding upstream ISP.
For example, in Figure 1, a home network is connected with two ISPs,
ISP1 and ISP2. ISP1 has prefix P1 and is connected to the home
network through border router BR1; ISP2 has prefix P2 and is
connected to the home network through border router BR2. A host in
the network is connected to the intermediate router I1, and obtains
two addresses, A from P1 and B from P2. Packets from the host
towards the Internet should be sent to BR1 when the host uses address
A, else the packets should be sent to BR2 when the host uses address
B.
The multi-homing scenario is an emerging requirement in home
networks. These networks are naturally connected to multiple
upstream ISPs, e.g., broadband service provider and IPTV service
provider, at the same time. Packets could be dropped if they are not
delivered to the right ISP. For example, some IPTV service provider
does not allow packets with any source addresses other than their own
addresses.
Xu, et al. Expires August 5, 2013 [Page 6]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
+--------------------------+
| |
| Internet |
| |
| |
+--------------------------+
| |
+-----------+---+ +---+-------------+
| | | |
| ISP1: P1 | | ISP2: P2 |
| | | |
+--------+------+ +-----+-----------+
| |
+--+---+ +--+---+
|Router| |Router|
| BR1 | | BR2 |
+---+--+ +---+--+
------+------------+- -+-------------+-----
+-+----+-+
| Router |
| I1 |
+---+----+
-------+--------
|
+--+---+ Address A in P1
| Host |
+------+ Address B in P2
Figure 1: Multi-homing Scenario in Home Networks
3.2. Access-control in Home Networks
Home networks will involve multiple subset and routers, as more and
more dedicated devices including sensors are incorporated into home
networks. Different subsets in home networks usually have different
privacy and security policies. For instance, modern home routers
will support both guest and private subnets [3].
For example, in Figure 2, a home network is divided into three
subnets, the guest network, private network and restricted network.
The guest network can communicate with all peer devices/hosts inside
or outside the home network. The private network can only
communicate with all devices/hosts inside the home network. For the
restricted network, it can communicate with others inside the home
network, but only has limited Internet access.
Considering the importance of privacy and security in home network,
Xu, et al. Expires August 5, 2013 [Page 7]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
this senario will be common in the home network enviroment. With
more and more devices, like some private health sensors take part in,
it is envisaged that home networks should provide a simple and
flexible routing protocol, where access-control could be made in much
finer granularity.
+---------------------+
| |
| Internet |
+----------+----------+
|
+---+---+
| |
+------| BR1 |------+
| +-------+ |
+------------+ | | +------------+
| | +---+---+ +---+---+ | |
| Guest | | | | | | Private |
| Network +-----+ I1 | | I2 +-----+ Network |
| | +---+---+ +---+---+ | |
+------------+ | | +------------+
| +-------+ |
+------| +------+
| I3 |
+---+---+
|
+-----+------+
| |
| Restricted |
| Network |
| |
+------------+
Figure 2: Acess-control Scenario in Home Networks
Xu, et al. Expires August 5, 2013 [Page 8]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
4. Protocol Overview
TwoD-IP routing protocol is a link-state routing protocol, which is
preferred in home network, as routing protocol can have knowledge of
the whole home network topology [3]. The new routing protocol can be
self-configuring, and allows customizing for selected subnets.
Similar with traditional OSPF protocol, TwoD-IP periodically gather
link information and dynamically construct network topology. Then
routers within TwoD-IP routing protocol maintains link state data
base that describes network topology. After that, all routers will
run routing algorithm that determines the next hop for each packet
[2].
Different with OSPF protocol, which makes routing decisions solely
based on the destination IP address, and computes next hop towards
different destination IP addresses. TwoD-IP routing protocol makes
routing decisions based on both destination and source IP addresses.
Thus, routers need to disseminate and store additional information,
and run a different routing algorithm that computes next hop for
different destination and source IP address pairs.
In this document, we will focus on the differences between new
TwoD-IP routing protocol and traditional OSPF protocol. Basically,
they can be divided into three parts: link metric configuration, link
state advertisement/database, routing table calculation.
With TwoD-IP routing protocol, all traffic can be classified into a
TwoD traffic class, which can be represented by a (destination
prefix, source prefix) pair. Each packet falls into only one traffic
class based on its destination and source IP addresses. On each
link, we can configure multiple two dimensional link metrics, each
expresses the cost for a TwoD traffic class. Such link metric is
called TwoD link metric, and can be represented by a (destination
prefix, source prefix, cost) triple.
After link metric configuration, routers will disseminate these TwoD
link metric with new LSA, which is call TwoD-LSA. Receiving them,
routers will store them into extended link state database (LSB),
which can accomodate TwoD-LSAs. The extended link state database is
called TwoD-LSB.
With the TwoD-LSB, routers can run routing algorithm that computes
the next hop for each TwoD traffic class. Intrinsically, each TwoD
traffic class will match a TwoD link metric on every link over the
network. Thus, each TwoD traffic class can obtain a full network
topolgoy (which may be different with topology for other TwoD traffic
classes). Then the routing algorithm shall construct an SPT for the
Xu, et al. Expires August 5, 2013 [Page 9]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
TwoD traffic class. When a packet arrives, according to the TwoD
traffic class that it falls into, it will flow along the
corresponding SPT. Note that a packet may fall into multiple TwoD
traffic class, we resolve the confliction through the "Most Specific
First" rule [4].
Xu, et al. Expires August 5, 2013 [Page 10]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
5. TwoD Link Metric Configuration
Like OSPF, the TwoD link metric is configured in the interface data
structure. However, TwoD link metric is not solely a scalar that
describes the cost of sending a packet on the interface, but a triple
(destination prefix, source prefix, cost) that describes the cost of
sending a packet for TwoD traffic class (destination prefix, source
prefix). A single link can be configured to have multiple TwoD link
metrics, each for a different TwoD traffic class. Note that the
links can be automatically configured to have (*,*,1), that
degenerates into the default configuration for traditional OSPF.
+---------------+ +-----------------+
| | | |
| ISP1: P1 | | ISP2: P2 |
| | | |
+--------+------+ +-----+-----------+
|IF1:(*,P1,1) |IF2:(*,P2,1)
+--+---+(*,P2,1000) +--+---+(*,P1,1000)
|Router| |Router|
| BR1 | | BR2 |
+---+--+ +---+--+
------+------------+- -+-------------+-----
+-+----+-+
| Router |
| I1 |
+---+----+
-------+--------
|
+--+---+ Address A in P1
| Host |
+------+ Address B in P2
Figure 3: TwoD link metric configuration in the multi-homing Scenario
Continuing the example in Figure 1, we plot the TwoD link metric
configuration in Figure 3. We only have to configure the out-going
interface (like IF1 and IF2) on the border routers. On IF1, we
configure two TwoD link metrics, (*, P1, 1) and (*, P2, 1000),
indicating packets from P1 will traverse the link with cost 1 while
packets from 2 will traverse the link with much higher cost, 1000.
Similarly, on IF2, we also configure two TwoD link metrics, (*, P2,
1) and (*, P1, 1000). With this configuration, traffic from P1 (or
P2) will see a topology where the path through ISP1 (or ISP2) costs
much less than the path through ISP2 (or ISP1). Packets from P1 (or
P2) will never be diverted to ISP2 (or ISP1) unless the connection
Xu, et al. Expires August 5, 2013 [Page 11]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
with ISP1 (or ISP2) fails.
Also continuing the example in Figure 2, we plot the TwoD link metric
configuration in Figure 4. Let PX, PY, and PZ be the prefix of the
guest, private and restricted network, PR be the private prefix used
in the home network, and PV be the prefix in the Internet which the
restricted network can communicate with. We only have to configure
the router interfaces (like IFA, IFB and IFC) where the subnets are
connected. On IFA, we only have to configure (PX, *, 1) as all
traffic can travel into the guest network. We have to configure (PY,
PR, 1) on IFB, because only hosts from the home network (using
address in the private prefix) can travel into the private network.
At last, we have to configure (PZ, PR, 1), (PZ, PV, 1) on IFC,
because not only hosts inside the home network, but also hosts from
PV, can access the restricted network.
+---+---+
| |
+------| BR1 |------+
| +-------+ |
+------------+ (PX,*,1)| |(PY,PR,1)+------------+
| | +---+---+ +---+---+ | |
| Guest | IFA| | | |IFB | Private |
| Network +-----+ I1 | | I2 +-----+ Network |
| | +---+---+ +---+---+ | :PX |
+------------+ | | +------------+
| +-------+ |
+------| +------+
| I3 |
+---+---+ (PZ,PV,1)
|IFC (PZ,PR,1)
+-----+------+
| |
| Restricted |
| Network |
| :PY |
+------------+
Figure 4: TwoD link metric configuration in the acess-control
Scenario
Xu, et al. Expires August 5, 2013 [Page 12]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
6. New Link State Advertisement/Database
TBD.
Xu, et al. Expires August 5, 2013 [Page 13]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
7. Calculation of The Routing Table
TBD.
Xu, et al. Expires August 5, 2013 [Page 14]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
8. Forwarding Table Modification
Traditional forwarding table only supports making forwarding
decisions based on destination IP addresses. TwoD-IP routing
protocol needs a new forwarding table structure that supports making
forwarding decisions based on both destination and source IP
addresses. This can be achieved through a variety of ways, we will
discuss them in the next version of this document.
Xu, et al. Expires August 5, 2013 [Page 15]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
9. Incremental Deployment
TwoD-IP routing protocol should support incremental deployment, i.e.,
deploying one or two routers shall be useful in certain scenarios.
However, with more routers deployed, the network should be more
flexible to support policies with finer granularity.
Xu, et al. Expires August 5, 2013 [Page 16]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
10. Conclusion
Xu, et al. Expires August 5, 2013 [Page 17]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
11. IANA Considerations
Some newly designed TwoD-IP routing protocols may need new protocol
numbers assigned by IANA.
Xu, et al. Expires August 5, 2013 [Page 18]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
12. Acknowledgments
Zheng Liu and Gautier Bayzelon provided useful input into this
document.
Xu, et al. Expires August 5, 2013 [Page 19]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
13. References
13.1. Normative References
[1] Baker, F. and P. Savola, "Ingress Filtering for Multihomed
Networks", BCP 84, RFC 3704, March 2004.
[2] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF for
IPv6", RFC 5340, July 2008.
13.2. Informative References
[3] Chown, T., Arkko, J., Brandt, A., Troan, O., and J. Weil, "Home
Networking Architecture for IPv6", draft-ietf-homenet-arch-07
(work in progress), February 2013.
[4] Baker, F., "Routing a Traffic Class",
draft-baker-fun-routing-class-00 (work in progress), July 2011.
Xu, et al. Expires August 5, 2013 [Page 20]
Internet-Draft Two-IP Routing in HomeNet Feb 2013
Authors' Addresses
Mingwei Xu
Tsinghua University
Department of Computer Science, Tsinghua University
Beijing 100084
P.R. China
Phone: +86-10-6278-5822
Email: xmw@csnet1.cs.tsinghua.edu.cn
Shu Yang
Tsinghua University
Department of Computer Science, Tsinghua University
Beijing 100084
P.R. China
Phone: +86-10-6278-5822
Email: yangshu@csnet1.cs.tsinghua.edu.cn
Jianping Wu
Tsinghua University
Department of Computer Science, Tsinghua University
Beijing 100084
P.R. China
Phone: +86-10-6278-5983
Email: jianping@cernet.edu.cn
Dan Wang
Hong Kong Polytechnic University
Department of Computing, Hong Kong Polytechnic University
Hong Kong
P.R. China
Phone: +852-2766-7267
Email: csdwang@comp.polyu.edu.hk
Xu, et al. Expires August 5, 2013 [Page 21]
| PAFTECH AB 2003-2026 | 2026-04-24 03:10:09 |