>
> >>>>> Peder Chr Norgaard writes:
>
> Peder> The scotty, in the role of command generator, specifies a
> Peder> maxSizeResponseScopedPDU (the value is 2048) in a request. My
> Peder> implementation, as command responder, produces a response where
> Peder> the ScopedPDU is less than 2048, but the entire message is
> Peder> slightly larger (2070 bytes). Scotty complains:
>
>
> Do not confuse the maxSizeResponseScopedPDU parameter of the ASIs with
> the msgMaxSize field in the message. RFC 2272 section 6.3 says:
>
Sorry. You are right, of course; I had stupidly just copied my internal
value of maxSizeResponseScopedPDU from the msgMaxSize of the incoming
SNMP message. I need to adjust that.
>
> [I think it would be nice if the RFCs would contain precise hints on
> how to derive maxSizeResponseScopedPDU from msgMaxSize. It might be
> useful to bring this up on the SNMPv3 mailing list so that this can be
> clarified in the next revision cycle.]
Agreed!
best regards
--peder chr.
Peder Chr. Nørgaard System Developer, M. Sc.
Telebit Communications A/S tel: +45 86 28 81 77 - 49
Fabrikvej 11 fax: +45 86 28 81 86
DK-8260 Viby J Denmark e-mail: pcn@tbit.dk
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.