Extended Ping (Xping)
draft-bonica-intarea-eping-04

Document Type Active Internet-Draft (individual)
Last updated 2017-03-03
Stream (None)
Intended RFC status (None)
Formats plain text pdf 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)
INTAREA                                                        R. Bonica
Internet-Draft                                                 R. Thomas
Updates: RFC 4884 (if approved)                         Juniper Networks
Intended status: Standards Track                              J. Linkova
Expires: September 3, 2017                                        Google
                                                               C. Lenart
                                                                 Verizon
                                                           March 2, 2017

                         Extended Ping (Xping)
                     draft-bonica-intarea-eping-04

Abstract

   This document describes a new diagnostic tool called Extended Ping
   (Xping).  Network operators execute Xping to determine the status of
   a remote interface.  In this respect, Xping is similar to Ping.
   Xping differs from Ping in that it does not require network
   reachability between itself and remote interface whose status is
   being queried.

   Xping relies on two new ICMP messages, called Extended Echo Request
   and Extended Echo Reply.  Both ICMP messages are defined herein.

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 RFC 2119 [RFC2119].

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 September 3, 2017.

Bonica, et al.          Expires September 3, 2017               [Page 1]
Internet-Draft            Extended Ping (eping)               March 2017

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
   (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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   2
   2.  ICMP Extended Echo Request  . . . . . . . . . . . . . . . . .   4
     2.1.  Interface Identification Object . . . . . . . . . . . . .   6
   3.  ICMP Extended Echo Reply  . . . . . . . . . . . . . . . . . .   7
   4.  ICMP Extended Echo and Extended Echo Reply Processing . . . .   9
     4.1.  Code Field Processing . . . . . . . . . . . . . . . . . .  10
   5.  The Xping Application . . . . . . . . . . . . . . . . . . . .  10
   6.  Use-Cases . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     6.1.  Unnumbered Interfaces . . . . . . . . . . . . . . . . . .  12
     6.2.  Link-local Interfaces . . . . . . . . . . . . . . . . . .  12
     6.3.  Unadvertised Interfaces . . . . . . . . . . . . . . . . .  13
   7.  Updates to RFC 4884 . . . . . . . . . . . . . . . . . . . . .  13
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  15
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     11.2.  Informative References . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Problem Statement

   Network operators use Ping [RFC2151] to determine whether a remote
   interface is operational.  Ping sends an ICMP [RFC0792] [RFC4443]
   Echo message to the interface being probed and waits for an ICMP Echo
   Reply.  If Ping receives the expected ICMP Echo Reply, it reports
Show full document text