[P2PSIP] RFC 7851 on Peer-to-Peer (P2P) Overlay Diagnostics

rfc-editor@rfc-editor.org Tue, 10 May 2016 00:03 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: p2psip@ietfa.amsl.com
Delivered-To: p2psip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1231F12D56D; Mon, 9 May 2016 17:03:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.898
X-Spam-Level:
X-Spam-Status: No, score=-107.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TpBdPG7tfcoY; Mon, 9 May 2016 17:03:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 660AE12D0A7; Mon, 9 May 2016 17:03:22 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 64BDC180014; Mon, 9 May 2016 17:02:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160510000231.64BDC180014@rfc-editor.org>
Date: Mon, 09 May 2016 17:02:31 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/p2psip/t4MuCibkhaEK2_EAABD2bIGzpxg>
Cc: drafts-update-ref@iana.org, p2psip@ietf.org, rfc-editor@rfc-editor.org
Subject: [P2PSIP] RFC 7851 on Peer-to-Peer (P2P) Overlay Diagnostics
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/p2psip/>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 00:03:39 -0000

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

        
        RFC 7851

        Title:      Peer-to-Peer (P2P) Overlay Diagnostics 
        Author:     H. Song, X. Jiang,
                    R. Even, D. Bryan, Y. Sun
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2016
        Mailbox:    haibin.song@huawei.com, 
                    jiangxingfeng@huawei.com, 
                    ron.even.tlv@gmail.com,
                    dbryan@ethernot.org, 
                    sunyi@ict.ac.cn
        Pages:      30
        Characters: 70591
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-p2psip-diagnostics-22.txt

        URL:        https://www.rfc-editor.org/info/rfc7851

        DOI:        http://dx.doi.org/10.17487/RFC7851

This document describes mechanisms for Peer-to-Peer (P2P) overlay
diagnostics.  It defines extensions to the REsource LOcation And
Discovery (RELOAD) base protocol to collect diagnostic information
and details the protocol specifications for these extensions.  Useful
diagnostic information for connection and node status monitoring is
also defined.  The document also describes the usage scenarios and
provides examples of how these methods are used to perform
diagnostics.

This document is a product of the Peer-to-Peer Session Initiation Protocol Working Group of the IETF.

This is now a Proposed Standard.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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