Internet Protocol Tunneling over Content Centric Mobile Networks
draft-white-icnrg-ipoc-00
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-12-28
|
|
Replaced by |
|
draft-irtf-icnrg-ipoc
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
ICNRG G. White
Internet-Draft CableLabs
Intended status: Experimental S. Shannigrahi
Expires: July 1, 2018 C. Fan
Colorado State University
December 28, 2017
Internet Protocol Tunneling over Content Centric Mobile Networks
draft-white-icnrg-ipoc-00
Abstract
This document describes a protocol that enables tunneling of Internet
Protocol traffic over a Content Centric Network (CCN) or a Named Data
Network (NDN). The target use case for such a protocol is to provide
an IP mobility plane for mobile networks that might otherwise use IP-
over-IP tunneling, such as the GPRS Tunneling Protocol (GTP) used by
the Evolved Packet Core in LTE networks (LTE-EPC). By leveraging the
elegant, built-in support for mobility provided by CCN or NDN, this
protocol achieves performance on par with LTE-EPC, equivalent
efficiency, and substantially lower implementation and protocol
complexity. Furthermore, the use of CCN/NDN for this purpose paves
the way for the deployment of ICN native applications on the mobile
network.
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 https://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 July 1, 2018.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
White, et al. Expires July 1, 2018 [Page 1]
Internet-Draft IP over CCN December 2017
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. IPoC Overview . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Client Interest Table and Interest Deficit Report . . . . . . 5
5. Handling PIT Entry Lifetimes . . . . . . . . . . . . . . . . 6
6. Managing the CIT, PIT lifetimes and the in-flight message
count . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7. Establishing Communication . . . . . . . . . . . . . . . . . 8
8. IPoC Naming Conventions . . . . . . . . . . . . . . . . . . . 8
9. Sequence Numbers . . . . . . . . . . . . . . . . . . . . . . 9
10. Packet Sequencer . . . . . . . . . . . . . . . . . . . . . . 9
10.1. Packet Sequencer Example Algorithm . . . . . . . . . . . 9
11. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . 10
12. Gateway Behavior . . . . . . . . . . . . . . . . . . . . . . 11
13. Security Considerations . . . . . . . . . . . . . . . . . . . 12
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
15. Normative References . . . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
Content Centric Networking provides some key advantages over IP
networking that make it attractive as a replacement for IP for
wireless networking. In particular, by employing stateful
forwarding, CCN elegantly supports information retrieval by mobile
client devices without the need for tunneling or a location
registration protocol. Furthermore, CCN supports a client device
utilizing multiple network attachments (e.g. multiple radio links)
simultaneously in order to provide greater reliability or greater
performance. Finally, CCN is optimized for content retrieval, where
content can be easily retrieved from an on-path cache.
A significant hurdle that stands in the way of deploying a CCN-only
Show full document text