![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Hi Johan, > ---------- > From: Johan Otterstrvm[SMTP:jo at sectra.se] > Sent: Tuesday, May 05, 1998 11:16 AM > To: cat > Subject: Bad target names > > Hello, > > continuing my work with the IDUP-API I have a problem with the "hiding" > of the bad target names in the target info. It seems to me that a more > straighforward solution is to use a SET OF INTERNAL NAME as input and > SET OF Bad_Target_Name as output. Is there a reason to combine these > two? > The concept of parameter bundles has been used in this API simply to tie together parameters that are logically / conceptually related in some way. This is the case here: "target names" and "bad target names" don't *have* to be tied together (i.e., they could be separated as you suggest), but they seem so related that tying them together makes sense. For example, if a calling application wishes to sign a document (only) using IDUP, then it doesn't need the target names parameter. By extension, therefore, it doesn't need the bad target names parameter either. Parameter bundles are not used to "hide" parameters; they are used to "group" parameters. It seems to me that this particular grouping is reasonable here. -------------------------------------------- Carlisle Adams Entrust Technologies cadams at entrust.com --------------------------------------------
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.