![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Hello, I have been implementing parts of the IDUP API and I have a few comments/questions about the specification: In chapter 2.3.2.2 the Target_Info parameter bundle is described. The bundle has a set of target names, the number of bad targets and a Bad_Target_Name. Shouldn't this be a set of Bad_Target_Name? The discussion in the following chapter heads in that direction. It might be possible to make the parameter bundle Bad_Target_Name to contain all the bad names but I suppose that each name could have a different status code. In chapter 2.3.2.3 the status code IDUP_S_MORE_OUTBUFFER_NEEDED is valid for all the SE calls, but what is expected if the single operations gets a buffer that is to small? Will the operation fail or should it be possible to call it again to get the rest of the data? I suppose that the first alternative is the better one and thus the no data is returned and the call must be made once more with a larger buffer. Is there any work going on with the c-bindings document? Version 0.3 is not very up to date... Regards /jo -- ---------------------------------------------------------------- Johan Otterström Sectra AB Phone +46 13 23 52 46 Teknikringen 2 Telefax +46 13 21 21 85 S-583 30 Linköping Mail mailto:jo at sectra.se SWEDEN WWW http://www.sectra.se ----------------------------------------------------------------
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.