Query for 'core:data' rights
Mike <[email protected]> Thu, 27 Jun 2002 06:20:39 -0700 (PDT)
| Newsgroups | gmane.ietf.apex |
|---|---|
| Message-ID | <[email protected]> |
Hi All, In section 4.4.4 "The Data Operation" ... ... C: <data content='cid:[email protected]'> <originator identity='[email protected]' /> <recipient identity='[email protected]' /> </data> S: <error code='537'>access denied</error> ... ... According to this, if '[email protected]' does not allow '[email protected]' to send messages to it, relay will send an <error> element with code as '537'. <error> elements means Beep 'ERR' message type as mentioned in section 9.1 "The APEX Core DTD" ... ... <!-- APEX messages, exchanged as application/beep+xml role MSG RPY ERR ====== === === === I attach ok error I or L bind ok error I or L terminate ok error I or L data ok error --> ... ... But according to section 4.4.4.1 "Relay Processing of Data" ... ... 3. An "ok" element is returned. ... ... 5. For each recipient: ... ... 3. Otherwise, if the recipient endpoint is in the same administrative domain as the relay, the APEX access service must check that the originator endpoint is allowed to communicate with the recipient endpoint (the access entries[10] whose "owner" is the recipient must contain a "core:data" token for the originator), and the recipient endpoint must be currently attached. ... ... If already <ok> element is sent for a request, how can one send the <error> request later if the recipient deoes not contain 'core:data' token for the originator? According to our understanding, it should dropped the message and if statusRequest option is specified then relay should send this information in statusResponse. If so, then the internet draft should be corrected or made more clear? <Mike> __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com