In short, the relation between SNMP Usage and RELOAD as follows: SNMP Usage get a available IP address, which is used for SNMP communication, for snmeEngineID or NodeID or ResourceID or Manager name by RELOAD mechanism, such as AppAttach, Store, Fetch. Then SNMP Usage uses this IP address for SNMP communication between SNMP entities by the SNMP mechanism and architecture which defined in RFC3411 and RFC5953 and other SNMP RFCs (as depicted in the diagram below). And now there is little relation between SNMP Usage and RELOAD besides using RELOAD certificate. So we say "SNMP entities talk to each other using SNMP protocol on dedicated connections"
If you till have questions, please tell us. Thanks! ************************************************* 邮 件：[email protected] 内 线：81543 外 线：025-52871543 手 机：13776637274 传 真：025-52872187 ************************************************* "t.petch" <[email protected]> 2011-10-25 22:15 收件人 <[email protected]>, <[email protected]>, <[email protected]> 抄送 <[email protected]> 主题 Re: [OPSAWG] An SNMP Usage for RELOAD ----- Original Message ----- From: <[email protected]>; <[email protected]> To: <[email protected]>; <[email protected]>; <[email protected]>; <[email protected]> Cc: <[email protected]>; <[email protected]> Sent: Tuesday, October 25, 2011 4:23 AM > We have done more research on security and other issues based on David's > comments, and updated our draft. > > This is the new version of draft: > http://www.ietf.org/id/draft-peng-p2psip-snmp-03.txt > > We welcome any comments! Thanks! > > Our analysis of David's comments as follows(blue text): > > 1) Use SNMPv3 terminology > Apparently, you come from the RELOAD side of things, not the SNMP > side. > Your text doesn't use the common SNMP terminology for various > SNMP-related things. > You will have a better chance of success if you describe SNMP-related > things using the normal SNMPv3 terminology. > This isn't critical; your ideas seem reasonable, but since you don't > use the standard terminology, you might mean slightly different things > than what it would mean if you used the standard terminology. > > (I don't have a RELOAD background, so some of my comments might seem > wrong because I don't know the RELOAD concepts and terminology. Now > you'll understand my point ;-) > > PYL: We have updated the draft using SNMP terminology. As we are not SNMP > experts, some terminology may not be accurate. We will try to improve this > over time. You are indeed using SNMP terminology, but I struggle to see how its usage is the same as in RFC3411. RELOAD defines a messaging network, on top of which run applications, which RELOAD calls Usages, so when you define an SNMP Usage, you would appear to be discarding most of an Architecture for SNMP as defined in RFC3411, perhaps providing instead a gateway for functionality such as that specified in RFC3414; or perhaps not, I do not find the I-D clear on this. Thus you have Application +-------+ +-------+ +-------+ | SIP | | XMPP | | SNMP | ... | Usage | | Usage | | Usage | +-------+ +-------+ +-------+ ------------------------------------------- Messaging API RELOAD but elsewhere you say ' SNMP entities talk to each other using SNMP protocol on dedicated connections' which is rather different. The I-D reads more like a wish list of requirements, than an overview, architecture or framework. Or perhaps it is all beyond me:-( Tom Petch <snip> -------------------------------------------------------- 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.
<<image/gif>>
_______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
