IETF B. Haberman, Ed.
Internet-Draft JHU APL
Intended status: Standards Track May 11, 2009
Expires: November 12, 2009
A Dedicated RPSL Interface Identifier for Operational Testing
draft-haberman-rpsl-reachable-test-00
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 12, 2009.
Copyright Notice
Copyright (c) 2009 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 in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract
The deployment of new IP connectivity typically results in
intermittent reachability for numerous reasons which are outside the
scope of this document. In order to aid in the debugging of these
Haberman Expires November 12, 2009 [Page 1]
Internet-Draft RPSL Pingable Attribute May 2009
persistent problems, this document proposes the creation of a new
Routing Policy Specification Language object that allows a network to
advertise an IP address which is reachable and can be used as a
target for diagnostic tests (e.g., pings).
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. RPSL Extension for Diagnostic Address . . . . . . . . . . . . . 3
3. Using the RPSL Pingable Attribute . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . . 4
6.2. Informative References . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4
Haberman Expires November 12, 2009 [Page 2]
Internet-Draft RPSL Pingable Attribute May 2009
1. Introduction
The deployment of new IP connectivity typically results in
intermittent reachability for numerous reasons which are outside the
scope of this document. In order to aid in the debugging of these
persistent problems, this document proposes the creation of a new
Routing Policy Specification Language object [RFC4012] that allows a
network to advertise an IP address which is reachable and can be used
as a target for diagnostic tests (e.g., pings).
The goal of this diagnostic address is to provide operators a means
to advertise selected hosts that can be targets of tests for such
common issues as reachability and Path MTU discovery.
The capitalized 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. RPSL Extension for Diagnostic Address
Network operators wishing to provide a diagnostic address for its
peers, customers, etc. can advertise its existence via the Routing
Policy Specification Language [RFC4012] [RFC2622]. The pingable
attribute is a member of the aut-num class of the RPSL. The debug
attribute has the following characteristics:
+-----------+-------------------------------+-----------------------+
| Attribute | Value | Type |
+-----------+-------------------------------+-----------------------+
| pingable | <ipv6-address> or | optional, |
| | <ipv4-address> | multi-valued |
+-----------+-------------------------------+-----------------------+
The pingable attribute allows a network operator to advertise an IP
address of a node which should be reachable from outside networks.
This node can be used as a destination address for diagnostic tests.
An example of using the pingable attribute is shown in Figure 1.
aut-num: AS64500
pingable: 2001:DB8::DEAD:BEEF
Figure 1: DEBUG Attribute Example
Haberman Expires November 12, 2009 [Page 3]
Internet-Draft RPSL Pingable Attribute May 2009
3. Using the RPSL Pingable Attribute
The presence of one or more pingable attributes signals to network
operators that the maintainer of the referenced network is providing
the address(es) for external diagnostic testing. Tests involving the
advertised address(es) MUST be rate limited to no more than ten
probes in a five minute window.
4. IANA Considerations
None.
5. Acknowledgements
Randy Bush and David Farmer provided the original concept for the
pingable attribute and useful comments on preliminary versions of
this draft.
6. References
6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2622] Alaettinoglu, C., Villamizar, C., Gerich, E., Kessens, D.,
Meyer, D., Bates, T., Karrenberg, D., and M. Terpstra,
"Routing Policy Specification Language (RPSL)", RFC 2622,
June 1999.
[RFC4012] Blunk, L., Damas, J., Parent, F., and A. Robachevsky,
"Routing Policy Specification Language next generation
(RPSLng)", RFC 4012, March 2005.
6.2. Informative References
Haberman Expires November 12, 2009 [Page 4]
Internet-Draft RPSL Pingable Attribute May 2009
Author's Address
Brian Haberman (editor)
Johns Hopkins University Applied Physics Lab
11100 Johns Hopkins Road
Laurel, MD 20723-6099
US
Phone: +1 443 778 1319
Email: brian@innovationslab.net
Haberman Expires November 12, 2009 [Page 5]
