ICN Traceroute Protocol Specification
draft-mastorakis-icnrg-icntraceroute-02

Document Type Active Internet-Draft (individual)
Last updated 2017-09-21
Stream (None)
Intended RFC status (None)
Formats plain text pdf xml html 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                                                      S. Mastorakis
Internet-Draft                                                      UCLA
Intended status: Experimental                                  J. Gibson
Expires: March 25, 2018                                     I. Moiseenko
                                                           Cisco Systems
                                                                R. Droms

                                                                 D. Oran
                                                      September 21, 2017

                 ICN Traceroute Protocol Specification
                draft-mastorakis-icnrg-icntraceroute-02

Abstract

   This document presents the design of an ICN Traceroute protocol.
   This includes the operations both on the client and the forwarder
   side.  The design expresses the views of the authors and does not
   represent the views of the Named Data Networking Project Team.

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 March 25, 2018.

Copyright Notice

   Copyright (c) 2017 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

Mastorakis, et al.       Expires March 25, 2018                 [Page 1]
Internet-Draft               ICN Traceroute               September 2017

   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
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   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 . . . . . . . . . . .   8
   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 Handling  . . . . . . . . . . . . . . . . . . . . .  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 .  16
   Appendix B.  Open Design Questions  . . . . . . . . . . . . . . .  17
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

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

   This document proposes protocol mechanisms for a traceroute
   equivalent in ICN networks.  This document contains two appendix
   sections: 1) A non-normative appendix section suggesting useful
   properties for an ICN traceroute client application that originates
   traceroute requests and processes traceroute replies and 2) An
   appendix section summarizing the open questions of the current
   protocol design.
Show full document text