Talk:Simple Network Management Protocol

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
B	This article has been rated as B-class on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by Networking task force (assessed as High-importance).

Archives

1

This page has archives. Sections older than 365 days may be automatically archived by when more than 5 sections are present.

Plagiarism

This article IS NOT plagiarism. The original can be found here: Cisco SNMP article, which is copyrighted. —The preceding unsigned comment was added by Darkmane (talk • contribs) 10:39, 31 January 2007 (UTC).[reply]

I tend to disagree.. I took a look at the cisco article offical, and this one here and did some comparing. The content under "Management Information Base (MIBs)" is very similar to that on the offical document. Its like a copy and paste job with a clean up style wise.

Parts of this article may be considered plagiarism, but not the whole anyway.

--Sully 22:09, 19 April 2007 (UTC)[reply]

There are several unusual phrases that can be googled and they hit 2 places, this article and the Cisco paper. Try "SNMPv1 is widely used and is the de facto network-management protocol in the Internet community" for example. This article is plagiarism in part and badly written overall. —Preceding unsigned comment added by 67.79.13.14 (talk) 18:28, 12 January 2010 (UTC)[reply]

A list of SNMP Features would be useful

To help the newbie understand the 'why' of SNMP, it might be useful to start this article with a list of SNMP's features, such as

provides a way to ask a device on a network to describe itself.
information is organized by keyword and a corresponding value, for example you can ask a device for its 'sysLocation' and receive a response like 'Room 202A'.
There is a single family tree (hierarchy) of keywords for all of SNMP, which makes it easy to attach new branches to this tree as new needs arise.

Yes, but how does it work? What does it look like?

Is it a binary protocol? Or a text protocol? Or vendor specified? What does the packet/message/whatever look like? The description is very abstract - the article says that there are some types and variables and the ASN describes only the high level structure but not the implementation. The RFCs are great - as a reference for people who already know how it works. I went quickly throught the first listed and there is still only the high level structure. —Preceding unsigned comment added by 80.95.97.145 (talk) 08:02, 1 December 2009 (UTC)[reply]

Realizing this might be better in the text than here, but none the less: the protocol is encoded in BER which is a binary encoding. —Preceding unsigned comment added by Hardaker (talk • contribs) 15:31, 1 December 2009 (UTC)[reply]

Varbind missing

The term "Varbind" is redirected to this page. This page, however, does not contain the word "Varbind." —Preceding unsigned comment added by 206.169.32.3 (talk) 19:24, 27 August 2009 (UTC)[reply]

Introduction to SNMP, with an overview of RFCs

RFC 3410 provides a valuable introduction to the SNMP framework, and an overview of the many RFCs relating to it.