Path Steering in CCNx and NDN
draft-oran-icnrg-pathsteering-02
ICNRG I. Moiseenko
Internet-Draft UCLA
Intended status: Experimental D. Oran
Expires: 6 May 2021 Network Systems Research and Design
2 November 2020
Path Steering in CCNx and NDN
draft-oran-icnrg-pathsteering-02
Abstract
Path Steering is a mechanism to discover paths to the producers of
ICN content objects and steer subsequent Interest messages along a
previously discovered path. It has various uses, including the
operation of state-of-the-art multipath congestion control algorithms
and for network measurement and management. This specification
derives directly from the design published in _Path Switching in
Content Centric and Named Data Networks_ (4th ACM Conference on
Information-Centric Networking - ICN'17) and therefore does not
recapitulate the design motivations, implementation details, or
evaluation of the scheme. Some technical details are different
however, and where there are differences, the design documented here
is to be considered definitive.
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 6 May 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
Moiseenko & Oran Expires 6 May 2021 [Page 1]
Internet-Draft ICN Path Steering November 2020
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Essential elements of ICN path discovery and path steering . 4
2.1. Path Discovery . . . . . . . . . . . . . . . . . . . . . 4
2.2. Path Steering . . . . . . . . . . . . . . . . . . . . . . 5
2.3. Handling Path Steering errors . . . . . . . . . . . . . . 6
2.4. How to represent the Path Label . . . . . . . . . . . . . 6
3. Mapping to CCNx and NDN packet encodings . . . . . . . . . . 7
3.1. Path label TLV . . . . . . . . . . . . . . . . . . . . . 7
3.2. Path label encoding for CCNx . . . . . . . . . . . . . . 9
3.3. Path label encoding for NDN . . . . . . . . . . . . . . . 9
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5. Security Considerations . . . . . . . . . . . . . . . . . . . 11
5.1. Cryptographic protection of a path label . . . . . . . . 12
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.1. Normative References . . . . . . . . . . . . . . . . . . 14
6.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction
Path Steering is a mechanism to discover paths to the producers of
ICN content objects and steer subsequent Interest messages along a
previously discovered path. It has various uses, including the
operation of state-of-the-art multipath congestion control algorithms
and for network measurement and management. This specification
derives directly from the design published in [Moiseenko2017] and
therefore does not recapitulate the design motivations,
implementation details, or evaluation of the scheme. That
publication should be considered a normative reference as it is not
likely a reader will be able to understand all elements of this
design without first having read the reference. Some technical
details are different however, and where there are differences, the
design documented here is to be considered definitive.
There are a number of important use cases to justify extending ICN
architectures such as CCNx [RFC8569] or [NDN] to provide these
capabilities. These are summarized as follows:
Show full document text