Re: [GSMP] draft-ietf-gsmp-reqs-01.txt

avri <> Fri, 29 March 2002 11:50 UTC

Received: from ( [] (may be forged)) by (8.9.1a/8.9.1a) with ESMTP id GAA08883 for <>; Fri, 29 Mar 2002 06:50:03 -0500 (EST)
Received: (from daemon@localhost) by (8.9.1a/8.9.1) id GAA02412 for; Fri, 29 Mar 2002 06:50:05 -0500 (EST)
Received: from (localhost []) by (8.9.1a/8.9.1) with ESMTP id GAA02249; Fri, 29 Mar 2002 06:45:13 -0500 (EST)
Received: from (odin []) by (8.9.1a/8.9.1) with ESMTP id GAA02218 for <>; Fri, 29 Mar 2002 06:45:11 -0500 (EST)
Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id GAA08831 for <>; Fri, 29 Mar 2002 06:45:08 -0500 (EST)
Received: from (IDENT:root@localhost []) by (8.11.2/8.11.0) with ESMTP id g2TBj9k19126 for <>; Fri, 29 Mar 2002 06:45:09 -0500
Message-ID: <>
Date: Fri, 29 Mar 2002 12:44:30 +0100
From: avri <>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
Subject: Re: [GSMP] draft-ietf-gsmp-reqs-01.txt
References: <>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: General Switch Management Protocol <>
Content-Transfer-Encoding: 7bit wrote:

> Hi,
>     How does SNMP differ from GSMP?Is SNMP replacement for GSMP.Pls do explain
> me how do they differ


While in some very abstracted and general sense, SNMP and 
MIBs could be directed to most any configuration and control 
task, its mechanisms are not well suited for many specific 
control tasks.  In fact the design and use of SNMP seems to 
be largely limited to its use as a way to get status from a 
device rather then to direct the configuration or real time 
behavior of a device.  Although, admittedly there are those 
that do try to bend SNMP to dynamic control and 
configuration tasks.

In the case of GSMP, the protocol has been specialized to 
deal with the needs of a label switch (loosely defined as
any switch that makes its forwarding decisions based on a
small pre-defined set of fields in a packet).  I.e. instead 
of supporting multiple arbitrary information models through 
the use of  MIBs, it is constructed around the specific 
needs of label switches that are separated from their 


GSMP mailing list