ICN Ping Protocol
draft-mastorakis-icnrg-icnping-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Authors Spyridon Mastorakis  , Jim Gibson  , Ilya Moiseenko  , Ralph Droms  , David Oran 
Last updated 2016-08-26
Replaced by draft-irtf-icnrg-icnping
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized 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: February 27, 2017                                  I. Moiseenko
                                                                R. Droms
                                                                 D. Oran
                                                           Cisco Systems
                                                         August 26, 2016

                           ICN Ping Protocol
                   draft-mastorakis-icnrg-icnping-00

Abstract

   This document presents the design of an ICN Ping protocol.  This
   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 http://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 27, 2017.

Copyright Notice

   Copyright (c) 2016 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
   (http://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

Mastorakis, et al.      Expires February 27, 2017               [Page 1]
Internet-Draft                  ICN Ping                     August 2016

   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 . . . . . . . . . . . .   2
   3.  Ping Functionality Challenges and Opportunities in ICN  . . .   3
   4.  ICN Ping Echo Packet Formats  . . . . . . . . . . . . . . . .   5
     4.1.  ICN Ping Echo Request Packet Format . . . . . . . . . . .   5
     4.2.  Ping Echo Reply Packet Format . . . . . . . . . . . . . .   8
   5.  Forwarder Handling  . . . . . . . . . . . . . . . . . . . . .  11
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Appendix A.  Ping Client Application (Consumer) Operation . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

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].

2.  Background on IP-Based Ping Operation

   In IP-based ping, an IP address is specified, either directly, or via
   translation of a domain name through DNS.  The ping client
   application sends a number of ICMP Echo Request packets with the

Mastorakis, et al.      Expires February 27, 2017               [Page 2]
Internet-Draft                  ICN Ping                     August 2016

   specified IP address as the IP destination address and an IP address
Show full document text