ICN Ping Protocol Specification
draft-mastorakis-icnrg-icnping-03

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03

ICNRG                                                      S. Mastorakis
Internet-Draft                                                      UCLA
Intended status: Experimental                                  J. Gibson
Expires: February 28, 2019                                  I. Moiseenko
                                                           Cisco Systems
                                                                R. Droms
                                                             Google Inc.
                                                                 D. Oran
                                     Network Systems Research and Design
                                                         August 27, 2018

                    ICN Ping Protocol Specification
                   draft-mastorakis-icnrg-icnping-03

Abstract

   This document presents the design of an ICN Ping protocol.  It
   includes the operations both on the client and the forwarder side.

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 February 28, 2019.

Copyright Notice

   Copyright (c) 2018 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 extracted from this document must

Mastorakis, et al.      Expires February 28, 2019               [Page 1]
Internet-Draft                  ICN Ping                     August 2018

   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 Ping Operation . . . . . . . . . . . .   3
   3.  Ping Functionality Challenges and Opportunities in ICN  . . .   3
   4.  ICN Ping Echo CCNx Packet Formats . . . . . . . . . . . . . .   5
     4.1.  ICN Ping Echo Request CCNx Packet Format  . . . . . . . .   5
     4.2.  Ping Echo Reply CCNx Packet Format  . . . . . . . . . . .   8
   5.  ICN Ping Echo NDN Packet Formats  . . . . . . . . . . . . . .  11
     5.1.  ICN Ping Echo Request NDN Packet Format . . . . . . . . .  11
     5.2.  Ping Echo Reply NDN Packet Format . . . . . . . . . . . .  12
   6.  Forwarder Handling  . . . . . . . . . . . . . . . . . . . . .  13
   7.  Protocol Operation For Locally-Scoped Namespaces  . . . . . .  14
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  15
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     10.2.  Informative References . . . . . . . . . . . . . . . . .  15
   Appendix A.  Ping Client Application (Consumer) Operation . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   Determining data plane reachability to a destination and taking
   coarse performance measurements of round trip time are fundamental
   facilities for network administration and troubleshooting.  In IP,
   where routing and forwarding are based on IP addresses, ICMP echo and
   ICMP echo response are the protocol mechanisms used for this purpose,
   generally exercised through the familiar ping utility.  In ICN, where
   routing and forwarding are based on name prefixes, the ability to
   determine reachability of names is required.

   This document proposes protocol mechanisms for a ping equivalent in
   ICN networks.  A non-normative appendix suggests useful properties
   for an ICN ping client application, analogous to IP ping, that
   originates echo requests and process echo replies.

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].