ICN Traceroute Protocol Specification
draft-irtf-icnrg-icntraceroute-01

Document Type Active Internet-Draft (icnrg RG)
Authors Spyridon Mastorakis  , Jim Gibson  , Ilya Moiseenko  , Ralph Droms  , David Oran 
Last updated 2020-10-12 (latest revision 2020-10-10)
Replaces draft-mastorakis-icnrg-icntraceroute
Stream IRTF
Intended RFC status Experimental
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Additional Resources
- GitHub Repository
- Mailing list discussion
Stream IRTF state Active RG Document
Consensus Boilerplate Unknown
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
ICNRG                                                      S. Mastorakis
Internet-Draft                             University of Nebraska, Omaha
Intended status: Experimental                                  J. Gibson
Expires: 13 April 2021                                     Cisco Systems
                                                            I. Moiseenko
                                                               Apple Inc
                                                                R. Droms
                                                             Google Inc.
                                                                 D. Oran
                                     Network Systems Research and Design
                                                         10 October 2020

                 ICN Traceroute Protocol Specification
                   draft-irtf-icnrg-icntraceroute-01

Abstract

   This document presents the design of an ICN Traceroute protocol.
   This includes the operation of both the client and the forwarder.

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 13 April 2021.

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 (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

Mastorakis, et al.        Expires 13 April 2021                 [Page 1]
Internet-Draft               ICN Traceroute                 October 2020

   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
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Background on IP-Based Traceroute Operation . . . . . . . . .   3
   3.  Traceroute Functionality Challenges and Opportunities in
           ICN . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  ICN Traceroute CCNx Packet Format . . . . . . . . . . . . . .   5
     4.1.  ICN Traceroute Request CCNx Packet Format . . . . . . . .   6
     4.2.  Traceroute Reply CCNx Packet Format . . . . . . . . . . .   7
   5.  ICN Traceroute NDN Packet Format  . . . . . . . . . . . . . .  11
     5.1.  ICN Traceroute Request NDN Packet Format  . . . . . . . .  11
     5.2.  Traceroute Reply NDN Packet Format  . . . . . . . . . . .  12
   6.  Forwarder Operation . . . . . . . . . . . . . . . . . . . . .  13
   7.  Protocol Operation For Locally-Scoped Namespaces  . . . . . .  14
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  16
   Appendix A.  Traceroute Client Application (Consumer)
           Operation . . . . . . . . . . . . . . . . . . . . . . . .  17
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   In TCP/IP, routing and forwarding are based on IP addresses.  To
   ascertain the route to an IP address and to measure the transit
   delays, the traceroute utility is commonly used.  In ICN, routing and
   forwarding are based on name prefixes.  To this end, the problem of
   ascertaining the characteristics (i.e., transit forwarders and
   delays) of at least one of the available routes to a name prefix is a
   fundamendal requirement for instumentation and network management.

   This document describes protocol mechanisms for a traceroute
   equivalent in ICN networks based on CCNx [RFC8569] or NDN [NDNTLV]).
   The document also contains a non-normative appendix section
   suggesting useful properties for an ICN traceroute client application
   that originates traceroute requests and processes traceroute replies.

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text