[AGENT++] Possible bug in SET-response

Frank Fock fock at agentpp.com
Mon Aug 28 18:39:28 CEST 2006


Hello Marcus,

This is indeed a bug. Although it has only "academic"
relevance, since a request generator should ignore
the value fields (see §4.2.4 of RFC3416) if the error
status is non zero.

I will provide a fix for it until end of this week.

Best regards,
Frank


Fehde, Marcus wrote:
> Hi,
> 
> I think I might have find a minor bug regarding SET-request processing in case of an error.
> 
> Situation:
> A SET-request results in an error, for instance, a notWritable-error that is included in the SET-response PDU. The fields errorStatus and errorIndex are set accordingly. But the variable bindings of the response PDU are set to NULL values. Accordingly to RFC3416 §4.2.5, the SET-response PDU shall keep the variable bindings of the original request.
> 
> Investigation:
> The processing of the SET-request ends with the invocation of Mib::finalize which further invokes RequestList::answer. While executing this method the method RequestList::null_vbs gets invoked. This is pretty good for any GET-request type (also accordingly to RFC3416), but it isn't for a SET-request.
> I modified the RequestList::answer in order to skip this method invocation for a SET-PDU. But I'm unable to appraise for any side-effects on this modification.
> 
> However, do you agree on my interpretation of RFC3416?
> 
> Regards,
> Marcus
> 
>  
> 
> Marcus Fehde
> R&D Business Unit Perioperative Care
> S30 Module Project Leader
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> 
> Draeger Medical AG & Co. KG
> Moislinger Allee 53-55
> D-23542 Luebeck
> 
> Phone:   + 49-451-882-3646
> Fax:         + 49-451-882-73646
> Mobile: + 49-177 79 78 272
> 
> E-mail: marcus.fehde at draeger.com
> 
> www.draeger-medical.com <http://www.draeger-medical.com> 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> 
>  
> 
> 
> 
> ------------------------------------------------------------------------
> 
> Important Note 
> This e-mail message may contain confidential and/or privileged information. If you are not an 
> addressee or otherwise authorized to receive this message, you should not use, copy, disclose 
> or take any action based on this e-mail or any information contained in the message. If you have 
> received this material in error, please advise the sender immediately by reply e-mail and delete 
> this message. Thank you.
>  
> Wichtiger Hinweis 
> Diese E-Mail und etwaige Anlagen koennen Betriebs- oder Geschaeftsgeheimnisse oder sonstige 
> vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen 
> dieser Umstand hiermit bekannt. Bitte benachrichtigen Sie uns in diesem Fall umgehend durch 
> Ruecksendung der E-Mail und loeschen Sie diese E-Mail einschließlich etwaiger Anlagen von Ihrem
> System. Diese E-Mail und ihre Anlagen duerfen weiterhin nicht kopiert oder an Dritte weitergegeben 
> werden. Vielen Dank.
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> AGENTPP mailing list
> AGENTPP at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/agentpp

-- 
AGENT++
http://www.agentpp.com
http://www.mibexplorer.com
http://www.mibdesigner.com




More information about the AGENTPP mailing list