Re: [P2PSIP] I-D Action: draft-ietf-p2psip-diagnostics-16.txt
"Songhaibin (A)" <haibin.song@huawei.com> Thu, 29 January 2015 09:29 UTC
Return-Path: <haibin.song@huawei.com>
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 CBC9D1A0130 for <p2psip@ietfa.amsl.com>; Thu, 29 Jan 2015 01:29:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 JAUKZvz80mmh for <p2psip@ietfa.amsl.com>; Thu, 29 Jan 2015 01:29:41 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA62F1A00FB for <p2psip@ietf.org>; Thu, 29 Jan 2015 01:29:40 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BON96210; Thu, 29 Jan 2015 09:29:39 +0000 (GMT)
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 29 Jan 2015 09:29:38 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.146]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0158.001; Thu, 29 Jan 2015 17:29:35 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: "Roy, Radhika R CIV USARMY (US)" <radhika.r.roy.civ@mail.mil>, "p2psip@ietf.org" <p2psip@ietf.org>
Thread-Topic: [P2PSIP] I-D Action: draft-ietf-p2psip-diagnostics-16.txt
Thread-Index: AQHQNuP49RwG5d6TQUagStguaRu7V5zNkJAAgAQBYfCAAEwogIAE/0gQ
Date: Thu, 29 Jan 2015 09:29:34 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F65227EF9@nkgeml501-mbs.china.huawei.com>
References: <20150123080935.4605.51843.idtracker@ietfa.amsl.com> <8486C8728176924BAF5BDB2F7D7EEDDF724F6F55@ucolhpkt.easf.csd.disa.mil> <E33E01DFD5BEA24B9F3F18671078951F652263B8@nkgeml501-mbs.china.huawei.com> <8486C8728176924BAF5BDB2F7D7EEDDF724F71A6@ucolhpkt.easf.csd.disa.mil>
In-Reply-To: <8486C8728176924BAF5BDB2F7D7EEDDF724F71A6@ucolhpkt.easf.csd.disa.mil>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.49]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/p2psip/qVGjr4LERiiZtpeQNBPZw78EVfI>
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: Thu, 29 Jan 2015 09:29:44 -0000
Hi Radhika, This is a management issue rather than a technical issue. Best Regards! -Haibin > -----Original Message----- > From: Roy, Radhika R CIV USARMY (US) [mailto:radhika.r.roy.civ@mail.mil] > Sent: Monday, January 26, 2015 9:07 PM > To: Songhaibin (A); p2psip@ietf.org > Subject: RE: [P2PSIP] I-D Action: draft-ietf-p2psip-diagnostics-16.txt > > Hi, Haibin: > > Great! > > Yes, I also thought the same. We are looking for full management set for > P2PSIP. > > We saw one proposal P2PSNMP draft some time ago. Why did that draft > authors > not continue? > > Or, will people create extensions one after another until the full set for > P2PSIP management available? > > BR/Radhika > > -----Original Message----- > From: Songhaibin (A) [mailto:haibin.song@huawei.com] > Sent: Sunday, January 25, 2015 7:38 PM > To: Roy, Radhika R CIV USARMY (US); p2psip@ietf.org > Subject: RE: [P2PSIP] I-D Action: draft-ietf-p2psip-diagnostics-16.txt > > Hi Roy, > > > > -----Original Message----- > > From: P2PSIP [mailto:p2psip-bounces@ietf.org] On Behalf Of Roy, > > Radhika R CIV USARMY (US) > > Sent: Saturday, January 24, 2015 3:25 AM > > To: p2psip@ietf.org > > Subject: Re: [P2PSIP] I-D Action: draft-ietf-p2psip-diagnostics-16.txt > > > > 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? > > It is considered useful for diagnostics at this moment. There can be future > extensions. It is not a full set. > > > 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? > > IMO P2P network management and diagnostics are two different concepts, > and > you can have other protocols/extensions for management. > > -Haibin > > > 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
- [P2PSIP] I-D Action: draft-ietf-p2psip-diagnostic… internet-drafts
- Re: [P2PSIP] I-D Action: draft-ietf-p2psip-diagno… Roy, Radhika R CIV USARMY (US)
- Re: [P2PSIP] I-D Action: draft-ietf-p2psip-diagno… Songhaibin (A)
- Re: [P2PSIP] I-D Action: draft-ietf-p2psip-diagno… Roy, Radhika R CIV USARMY (US)
- Re: [P2PSIP] I-D Action: draft-ietf-p2psip-diagno… Songhaibin (A)
- Re: [P2PSIP] I-D Action: draft-ietf-p2psip-diagno… Roy, Radhika R CIV USARMY (US)
- Re: [P2PSIP] I-D Action: draft-ietf-p2psip-diagno… Roy, Radhika R CIV USARMY (US)
- Re: [P2PSIP] I-D Action: draft-ietf-p2psip-diagno… Songhaibin (A)
- Re: [P2PSIP] I-D Action: draft-ietf-p2psip-diagno… Roy, Radhika R CIV USARMY (US)