[P2PSIP] 答复: Comments on draft-peng-p2psip-snmp-00
wang.wei108@zte.com.cn Sun, 07 November 2010 07:42 UTC
Return-Path: <wang.wei108@zte.com.cn>
X-Original-To: p2psip@core3.amsl.com
Delivered-To: p2psip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FB7C28C0D0 for <p2psip@core3.amsl.com>; Sun, 7 Nov 2010 00:42:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -93.912
X-Spam-Level:
X-Spam-Status: No, score=-93.912 tagged_above=-999 required=5 tests=[AWL=-3.723, BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, SARE_SUB_ENC_GB2312=1.345, 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 hi4bqZUuYqpF for <p2psip@core3.amsl.com>; Sun, 7 Nov 2010 00:42:53 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 2D3D03A680D for <p2psip@ietf.org>; Sun, 7 Nov 2010 00:42:52 -0700 (PDT)
Received: from [10.34.0.130] by mx5.zte.com.cn with surfront esmtp id 35102075036648; Sun, 7 Nov 2010 15:41:40 +0800 (CST)
Received: from [10.32.0.74] by [192.168.168.16] with StormMail ESMTP id 90868.2296983992; Sun, 7 Nov 2010 15:39:17 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse3.zte.com.cn with ESMTP id oA77hFBW031939; Sun, 7 Nov 2010 15:43:15 +0800 (CST) (envelope-from wang.wei108@zte.com.cn)
In-Reply-To: <AANLkTikih+fAzRsTzRy8-YsODjTdFxiBuZOg0CVWnzm9@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
MIME-Version: 1.0
X-KeepSent: CBCB32E3:4965778C-482577D4:00272AE8; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFCBCB32E3.4965778C-ON482577D4.00272AE8-482577D4.002A64E1@zte.com.cn>
From: wang.wei108@zte.com.cn
Date: Sun, 07 Nov 2010 15:40:44 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2010-11-07 15:43:03, Serialize complete at 2010-11-07 15:43:03
Content-Type: multipart/alternative; boundary="=_alternative 002A64DE482577D4_="
X-MAIL: mse3.zte.com.cn oA77hFBW031939
Cc: p2psip@ietf.org
Subject: [P2PSIP] 答复: Comments on draft-peng-p2psip-snmp-00
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 07 Nov 2010 07:42:54 -0000
Hi Eric, Our aim of introducing the SNMP usage is to allow existing Management systems which use SNMP to work with RELOAD networks. It is not built in the RELOAD protocol as in the diagnostic draft. It provides a way to add management modules when network operators needs more management functions, including trapping node failures, dynamically reconfiguring nodes, etc. For a RELOAD network using SNMP, there will be some operators who are authorized to control the network, possibly same as the organizations who deploy the enrollment and configuration server. And there will be some manager servers deployed by the network operator. Ordinary nodes may have lightweight SNMP agents on them to be managed by the operator. Management traffic should be quite small, and it helps the network work smoothly. So, users may be willing to deploy such management agents on their nodes. Regards Wang wei ZTE Eric Rescorla <ekr@rtfm.com> 发件人: p2psip-bounces@ietf.org 2010-11-07 05:29 收件人 p2psip@ietf.org 抄送 主题 [P2PSIP] Comments on draft-peng-p2psip-snmp-00 I've just read this document and I've got some comments/questions: (1) I'm not sure I understand the relationship to the diagnostics draft. They seem to occupy much of the same space in terms of use cases. (2) The general concept of this draft seems to be that there is a set of devices/peers which are allowed to be management devices in the SNMP sense. Given the relatively unstructured nature of the p2p network I wonder how much people will really be willing to serve signnificant amounts of management information to random controller nodes. -Ekr _______________________________________________ P2PSIP mailing list P2PSIP@ietf.org https://www.ietf.org/mailman/listinfo/p2psip -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender. This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
- [P2PSIP] Comments on draft-peng-p2psip-snmp-00 Eric Rescorla
- [P2PSIP] 答复: Comments on draft-peng-p2psip-snmp-00 wang.wei108
- [P2PSIP] 答复: Comments on draft-peng-p2psip-snmp-00 peng.yonglin