 |
 |

Current Status
So, how do you go about using BXXP?
First, get the specification [32] and read it. Next, define your own profile. Finally, get a TCP port number for your protocol and start implementing.
The BXXP specification defines five profiles itself: a channel management profile, three user authentication profiles, and a transport layer security profile. These provide good examples. Of course, we've been using BXXP internally for a year now, so if you want to look at a rather detailed profile definition, check out the Blocks Simple Exchange [31] profile. It addresses the issue of naming for its application domain, and, in doing so, opens the door for authorization.
Since we published BXXP as an Internet-draft for comments we've gotten some pretty good feedback. Prior to the next meeting of the IETF, we'll be publishing an updated specification along with a couple of open source implementations. So, you might want to wait a few weeks before you start implementation.
Next » References
Copyright © 2000 Invisible Worlds. All Rights Reserved.
|
 |