IETF Logo Mail Archive

Re: [P2PSIP] I-D Action: draft-ietf-p2psip-diagnostics-16.txt

"Roy, Radhika R CIV USARMY (US)" <radhika.r.roy.civ@mail.mil> Fri, 23 January 2015 19:25 UTC

Return-Path: <radhika.r.roy.civ@mail.mil>
X-Original-To: p2psip@ietfa.amsl.com
Delivered-To: p2psip@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58EA21ACED3 for <p2psip@ietfa.amsl.com>; Fri, 23 Jan 2015 11:25:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 7q_5EdnLqbs1 for <p2psip@ietfa.amsl.com>; Fri, 23 Jan 2015 11:25:09 -0800 (PST)
Received: from upbd19pa11.eemsg.mail.mil (upbd19pa11.eemsg.mail.mil [214.24.27.86]) by ietfa.amsl.com (Postfix) with ESMTP id 2F4BE1ACED0 for <p2psip@ietf.org>; Fri, 23 Jan 2015 11:25:06 -0800 (PST)
X-EEMSG-Attachment-filename: smime.p7s
Received: from edge-cols02.mail.mil ([131.64.104.103]) by upbd19pa11.eemsg.mail.mil with ESMTP; 23 Jan 2015 19:25:04 +0000
Received: from UCOLHPMO.easf.csd.disa.mil (131.64.104.43) by edge-cols02.mail.mil (131.64.104.103) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 23 Jan 2015 19:24:38 +0000
Received: from UCOLHPKT.easf.csd.disa.mil ([169.254.2.202]) by ucolhpmo.easf.csd.disa.mil ([131.64.104.43]) with mapi id 14.03.0195.001; Fri, 23 Jan 2015 19:24:38 +0000
From: "Roy, Radhika R CIV USARMY (US)" <radhika.r.roy.civ@mail.mil>
To: "p2psip@ietf.org" <p2psip@ietf.org>
Thread-Topic: [P2PSIP] I-D Action: draft-ietf-p2psip-diagnostics-16.txt
Thread-Index: AQHQNuP00hLTrMrU1EWpqWeJ3iYkxpzOFKlw
Date: Fri, 23 Jan 2015 19:24:38 +0000
Message-ID: <8486C8728176924BAF5BDB2F7D7EEDDF724F6F55@ucolhpkt.easf.csd.disa.mil>
References: <20150123080935.4605.51843.idtracker@ietfa.amsl.com>
In-Reply-To: <20150123080935.4605.51843.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [131.64.22.14]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_000F_01D03718.4F32DAA0"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/p2psip/jfPC2boe_p0BW8FBrS0sBfS3EA8>
Subject: Re: [P2PSIP] I-D Action: draft-ietf-p2psip-diagnostics-16.txt
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 23 Jan 2015 19:25:11 -0000

Hi, Song, et al:

I have one general question about the draft as follows:

1. Will these diagnostics collection by P2P RELOAD protocol as it is being
extended be good enough for P2PSIP management?

2. Does it mean that we do not need any separate P2P Management Protocol
(e.g. P2PSNMP aka like P2PSIP) for management P2PSIP network for all of its
nodes that use P2PSIP protocol?

BR/Radhika

-----Original Message-----
From: P2PSIP [mailto:p2psip-bounces@ietf.org] On Behalf Of
internet-drafts@ietf.org
Sent: Friday, January 23, 2015 3:10 AM
To: i-d-announce@ietf.org
Cc: p2psip@ietf.org
Subject: [P2PSIP] I-D Action: draft-ietf-p2psip-diagnostics-16.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
 This draft is a work item of the Peer-to-Peer Session Initiation Protocol
Working Group of the IETF.

        Title           : P2P Overlay Diagnostics
        Authors         : Haibin Song
                          Jiang Xingfeng
                          Roni Even
                          David A. Bryan
                          Yi Sun
	Filename        : draft-ietf-p2psip-diagnostics-16.txt
	Pages           : 29
	Date            : 2015-01-23

Abstract:
   This document describes mechanisms for P2P overlay diagnostics.  It
   defines extensions to the RELOAD P2PSIP 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 in P2PSIP overlay networks.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-p2psip-diagnostics/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-p2psip-diagnostics-16

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-p2psip-diagnostics-16


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www.ietf.org/mailman/listinfo/p2psip

v2.23.0 | Report a Bug | By Email