Yes Wes ...i am trying to understand the concept.
As i read in RFC 3412:
a. if reportable flag is 0 for a confirmed class of packets, then also 
the receiver should process it as though it had been set to 1.
b . if reportable flag is 1 for a unconfirmed class of packets, then 
also the receiver should process it as though it had been set to 0.

If this is the case then what is the purpose of keeping this flag ??
In place of this flag a rule can be set like always send a report for a 
Confirrmed class of packet and dont send the report for Unconfirmed 
class of packets.
Please help me to understand this concept.

Wes Hardaker wrote:
> M> I am little confused with the use of reportableFlag bit of msgFlags.
> M> As per RFC3412 reportable flag says whether to send a report or not.
> M> What should be behaviour of receiver for the below scenario:
> M> 1. A Get is send using reportableFlag = 0
> M> 2. A trap is send using reportableFlag = 1
>
> The reportable flag is really for internal use by most SNMP stacks
> (including Net-SNMP).  You really don't need to worry about it yourself.
>
> Or are you trying to simply understand the protocol more?
>
>   


------------------------------------------------------------------------------
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to