joey@geaclib.UUCP (Joey De Wiele) (01/10/89)
Remote Operations RO-U-REJECT Service I appear to be running into some conceptual problems in trying to "complete" my understanding of the X.500 Directory protocols. One problem I have is the implication of the Remote Operations RO-REJECT-U service. This service is used by the ROSE-user to reject a request of the other ROSE-user if it has detected a problem. Where does the responsibility for dealing with this service reside within an Application Protocol? For instance, there is nothing within the X.500 Directory Recommendations which describe how to handle this service. Is this a local matter? If anyone has experience with implementing ROSE-based protocols, I'd like to hear what you did with this service. Joey De Wiele
kmont@hpindda.HP.COM (Kevin Montgomery) (01/17/89)
/ hpindda:comp.protocols.iso / joey@geaclib.UUCP (Joey De Wiele) / 7:58 am Jan 10, 1989 / > Where does the responsibility for dealing with this service reside > within an Application Protocol? For instance, there is nothing within > the X.500 Directory Recommendations which describe how to handle this > service. Is this a local matter? Right off the top of my head (with no research whatsoever <- note disclaimer), I'd venture the RO-REJECT-U service would be used for rejecting Directory operations based on implementational constraints, for starters. For instance, what do you do if a READ operation is requested, and an error occurs which is not defined within the X.5xx suite of protocols (implementational error or otherwise)? I'm sure there are other mappings of services, but I don't have time at the moment to cross reference between X.519 and X.219 (dinnertime!). Will think more about it when I get a chance... > If anyone has experience with implementing ROSE-based protocols, I'd > like to hear what you did with this service. you can see the general utility in this service though, right? (might be nice for a ROSE-user to be able to reject operations) kevin@the_rose_proponents_guild