RFC 5943 on A Dedicated Routing Policy Specification Language Interface Identifier for Operational Testing

rfc-editor@rfc-editor.org Fri, 13 August 2010 16:38 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 007BE3A6A0E for <ietf-announce@core3.amsl.com>; Fri, 13 Aug 2010 09:38:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.035
X-Spam-Level:
X-Spam-Status: No, score=-102.035 tagged_above=-999 required=5 tests=[AWL=-0.035, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E1ROhg08tnQj for <ietf-announce@core3.amsl.com>; Fri, 13 Aug 2010 09:37:59 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 37B9C3A6821 for <ietf-announce@ietf.org>; Fri, 13 Aug 2010 09:37:59 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8914CE06B0; Fri, 13 Aug 2010 09:38:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5943 on A Dedicated Routing Policy Specification Language Interface Identifier for Operational Testing
From: rfc-editor@rfc-editor.org
Message-Id: <20100813163836.8914CE06B0@rfc-editor.org>
Date: Fri, 13 Aug 2010 09:38:36 -0700 (PDT)
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Aug 2010 16:38:00 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5943

        Title:      A Dedicated Routing Policy Specification 
                    Language Interface Identifier for Operational Testing 
        Author:     B. Haberman, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2010
        Mailbox:    brian@innovationslab.net
        Pages:      4
        Characters: 9016
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-haberman-rpsl-reachable-test-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5943.txt

The deployment of new IP connectivity typically results in
intermittent reachability for numerous reasons that 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 attribute that allows a network
to advertise an IP address that is reachable and can be used as a
target for diagnostic tests (e.g., pings).  [STANDARDS TRACK]

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC