Internet Services over ICN in 5G LAN Environments
draft-trossen-icnrg-internet-icn-5glan-01
ICNRG D. Trossen
Internet-Draft Huawei
Intended status: Informational C. Wang
Expires: August 7, 2020 S. Robitzsch
InterDigital Inc.
M. Reed
M. Al-Naday
Essex University
J. Riihijarvi
RWTH Aachen
February 4, 2020
Internet Services over ICN in 5G LAN Environments
draft-trossen-icnrg-internet-icn-5glan-01
Abstract
In this draft, we provide architecture and operations for enabling
Internet services over ICN over (5G-enabled) LAN environments.
Operations include ICN API to upper layers, HTTP over ICN, Service
Proxy Operations, ICN Flow Management, Name Resolution, Mobility
Handling, and Dual Stack Device Support.
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 August 7, 2020.
Copyright Notice
Copyright (c) 2020 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
Trossen, et al. Expires August 7, 2020 [Page 1]
Internet-Draft Internet over ICN in 5GLAN February 2020
(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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. 5G Control Plane Services . . . . . . . . . . . . . . . . 5
3.2. HTTP-based Streaming . . . . . . . . . . . . . . . . . . 6
4. 5GLAN in 5G Next Generation Core Network Architecture . . . . 7
4.1. Realization in SDN Transport Networks . . . . . . . . . . 10
4.2. Realization in Other Transport Networks . . . . . . . . . 10
5. Internet Services over ICN over 5GLAN . . . . . . . . . . . . 11
5.1. General Operations . . . . . . . . . . . . . . . . . . . 13
5.2. ICN API to Upper Layers . . . . . . . . . . . . . . . . . 14
5.3. HTTP over ICN . . . . . . . . . . . . . . . . . . . . . . 15
5.3.1. General Mapping Procedures . . . . . . . . . . . . . 15
5.3.2. Realizing Ad-Hoc Multicast Responses for HTTP . . . . 15
5.4. Service Proxy Operations . . . . . . . . . . . . . . . . 16
5.5. ICN Flow Management . . . . . . . . . . . . . . . . . . . 17
5.6. NR Operations . . . . . . . . . . . . . . . . . . . . . . 17
5.7. Mobility Handling . . . . . . . . . . . . . . . . . . . . 17
5.8. Dual Stack Device Support . . . . . . . . . . . . . . . . 17
6. Deployment Considerations . . . . . . . . . . . . . . . . . . 18
7. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 19
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
9. Security Considerations . . . . . . . . . . . . . . . . . . . 19
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19
11. Informative References . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction
As discussed in [I-D.ravi-icnrg-5gc-icn], Information-Centric
Networks (ICN) could be more easily implemented in a Local Area
Network (LAN) environment. In relation to 5G, this specifically
would realize an ICN deployment without requiring integration of ICN
Show full document text