Identity and Touchpoints
Marid Identity
Identity - any entity (human/avatar) that transmits/receives information through the marid network needs to have a unique identity. Unique can be to maridspace or to a specific marid server.
Other networks will converge in the marid network, so those unique identifiers will continue to be maintained by those networks. For instance, any email address is unique to the smtp network and is provided/verified by the email server hosting that email address.
Address book entries will contain both marid network entries and non-marid network entries (touchpoints). Entities in address book entries will in addition to non-marid network entries, contain a marid Identity.
Marid servers which interact will need to accept keys with an initial implementation of a whitelist. Anonymous marid identities are available from any server.
Implementation:
The Whitepages service will provide the ability to request/verify new Identities. There will be a single Whitepages service running on Maridspace.org which will maintain a larger community.
Initially, the unique key of the Identity will be created using the network identifier of the machine and a record primary key. Future implementations will include the ability to use OpenCA or some such authority.
When any message arrives into a service, the identity will be encoded within the header of the message. The service can verify the existence of the Identity from the issuing server.
Touchpoints
Touchpoint - a non-marid network connection point. The authentication, transport, and features of each touchpoint will be network specific. Marid servers will provide the translation/conversion of marid messages from one network to another.
Each identity will have many touchpoints which function as gateways into the marid network. Examples of touchpoint networks are: AIM, Yahoo IM, MSN IM, SMTP, SMS, Voice (POTS/PSTN), RSS (read-only), IRC, AIX/SIP, ICQ, FTP, HTTP (anonymous), SOAP. Some touchpoints provide location status like AIM, Yahoo IM, and possibly some Voice with gps enabled cell phones. IM Client status such as 'Away' will help determine location.
Implementation to follow.
Identity - any entity (human/avatar) that transmits/receives information through the marid network needs to have a unique identity. Unique can be to maridspace or to a specific marid server.
Other networks will converge in the marid network, so those unique identifiers will continue to be maintained by those networks. For instance, any email address is unique to the smtp network and is provided/verified by the email server hosting that email address.
Address book entries will contain both marid network entries and non-marid network entries (touchpoints). Entities in address book entries will in addition to non-marid network entries, contain a marid Identity.
Marid servers which interact will need to accept keys with an initial implementation of a whitelist. Anonymous marid identities are available from any server.
Implementation:
The Whitepages service will provide the ability to request/verify new Identities. There will be a single Whitepages service running on Maridspace.org which will maintain a larger community.
Initially, the unique key of the Identity will be created using the network identifier of the machine and a record primary key. Future implementations will include the ability to use OpenCA or some such authority.
When any message arrives into a service, the identity will be encoded within the header of the message. The service can verify the existence of the Identity from the issuing server.
Touchpoints
Touchpoint - a non-marid network connection point. The authentication, transport, and features of each touchpoint will be network specific. Marid servers will provide the translation/conversion of marid messages from one network to another.
Each identity will have many touchpoints which function as gateways into the marid network. Examples of touchpoint networks are: AIM, Yahoo IM, MSN IM, SMTP, SMS, Voice (POTS/PSTN), RSS (read-only), IRC, AIX/SIP, ICQ, FTP, HTTP (anonymous), SOAP. Some touchpoints provide location status like AIM, Yahoo IM, and possibly some Voice with gps enabled cell phones. IM Client status such as 'Away' will help determine location.
Implementation to follow.
Comments