PROBE: A Utility for Probing Interfaces
RFC 8335
Document | Type |
RFC - Proposed Standard
(February 2018; No errata)
Updates RFC 4884
|
|
---|---|---|---|
Authors | Ron Bonica , Reji Thomas , Jen Linkova , Chris Lenart , Mohamed Boucadair | ||
Last updated | 2018-02-22 | ||
Replaces | draft-bonica-intarea-eping | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Luigi Iannone | ||
Shepherd write-up | Show (last changed 2017-09-29) | ||
IESG | IESG state | RFC 8335 (Proposed Standard) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Suresh Krishnan | ||
Send notices to | Luigi Iannone <ggx@gigix.net> | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) R. Bonica Request for Comments: 8335 R. Thomas Updates: 4884 Juniper Networks Category: Standards Track J. Linkova ISSN: 2070-1721 Google C. Lenart Verizon M. Boucadair Orange February 2018 PROBE: A Utility for Probing Interfaces Abstract This document describes a network diagnostic tool called PROBE. PROBE is similar to PING in that it can be used to query the status of a probed interface, but it differs from PING in that it does not require bidirectional connectivity between the probing and probed interfaces. Instead, PROBE requires bidirectional connectivity between the probing interface and a proxy interface. The proxy interface can reside on the same node as the probed interface, or it can reside on a node to which the probed interface is directly connected. This document updates RFC 4884. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8335. Bonica, et al. Standards Track [Page 1] RFC 8335 PROBE February 2018 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 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 . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Requirements Language . . . . . . . . . . . . . . . . . . 4 2. ICMP Extended Echo Request . . . . . . . . . . . . . . . . . 5 2.1. Interface Identification Object . . . . . . . . . . . . . 6 3. ICMP Extended Echo Reply . . . . . . . . . . . . . . . . . . 7 4. ICMP Message Processing . . . . . . . . . . . . . . . . . . . 9 4.1. Code Field Processing . . . . . . . . . . . . . . . . . . 11 5. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 11 6. Updates to RFC 4884 . . . . . . . . . . . . . . . . . . . . . 12 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 8. Security Considerations . . . . . . . . . . . . . . . . . . . 14 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 9.1. Normative References . . . . . . . . . . . . . . . . . . 15 9.2. Informative References . . . . . . . . . . . . . . . . . 16 Appendix A. The PROBE Application . . . . . . . . . . . . . . . 17 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Bonica, et al. Standards Track [Page 2] RFC 8335 PROBE February 2018 1. Introduction Network operators use PING [RFC2151] to test bidirectional connectivity between two interfaces. For the purposes of this document, these interfaces are called the probing and probed interfaces. PING sends an ICMP [RFC792] [RFC4443] Echo Request message from the probing interface to the probed interface. The probing interface resides on a probing node while the probed interface resides on a probed node. If the probed interface receives the ICMP Echo Request message, it returns an ICMP Echo Reply. When the probing interface receives the ICMP Echo Reply, it has verified bidirectional connectivity betweenShow full document text