BUDDHA

0 Basic

0.1 Types

Version ::= INTEGER { v1(1), v2(2), v3(3) }
Flavour ::= ENUMERATED { ericsson(1), nokia(2),
   cisco(3) }

• Version: Protocol version from v1 to v3.
• Flavour: Supported operating systems for optimization.

1 Authority

1.1 Server Controlled ABAC Features

ABAC is used as Erlang/OTP application for certificate enrollment.

Feature ::= SEQUENCE {
   id OCTET STRING,
   key OCTET STRING,
   value OCTET STRING,
   group OCTET STRING }

• id: Unique configuration identifier.
• key: Semantic name of the feature.
• value: Current operational parameter.
• group: Categorical domain isolation.

1.2 Auhthority Method

AuthorityMethod ::= ENUMERATED { announce(0), enroll(1),
   authenticate(2), revoke(3), renew(4), ... }

• announce: Authority presence discovery.
• enroll: PKI enrollment entry-point.
• authenticate: Identity verification via challenges.
• revoke: Decommissioning of credentials.
• renew: Extension of validity for certificates.

1.2 Authority

v1: Authority announce is being sent directly from device to device over UDP. Each device has its own CA. v2: Authority is a full mirror of CA CMP protocol.

Authority ::= SEQUENCE {
   id OCTET STRING,
   vsn Version,
   session OCTET STRING,
   type AuthorityMethod,
   cert OCTET STRING,
   settings SEQUENCE OF feature Feature, ... }

• id: Stable administrative authority ID.
• vsn: Authority protocol version.
• session: Stateful session token.
• type: Administrative action type.
• cert: X.509 certificate encoding.
• settings: Collection of active features.

2 Message

v1: Message is being sent directly from device to device over UDP. v2: Message is main object in the system and main table in the MNESIA database. Once MessageEventType delivered is sent — it is physically deleted from server.

2.1 Message Type

MessageType ::= ENUMERATED {
   normal(0), sys(1), reply(2),
   forward(3), ... }

• normal: Standard interpersonal communication.
• sys: System notification or control message.
• reply: Message tied to thread context.
• forward: Relayed content preserving context.

2.2 Message Feed

MessageFeed ::= CHOICE {
   private [1] Privatebox,
   chan [2] Streambox,
   mailbox [3] Mailbox,
   group [4] Groupbox }

• private: Single-user private delivery.
• chan: Targeting a broadcast or multicast stream.
• mailbox: Document-oriented priority delivery system.
• group: Context for multi-user conference.

2.3 Message

If Message.payload is not present then Message.files should be taken and vice versa.

Message ::= SEQUENCE {
   id OCTET STRING,
   vsn Version,
   session OCTET STRING,
   feed MessageFeed,
   payload ContentInfo OPTIONAL,
   type MessageType OPTIONAL,
   linkId OCTET STRING OPTIONAL,
   files SEQUENCE OF file File OPTIONAL,
   mentioned SEQUENCE OF name OCTET STRING OPTIONAL,
   ... }

• id: Unique identifier for tracking.
• vsn: Versioning of the message schema.
• session: Transient session identifier.
• feed: Dispatch routing information.
• payload: Secured CMS content.
• type: Semantic classification of the message.
• linkId: Reference to parent message ID.
• files: Identifiers for binary attachments.
• mentioned: Tagged entities for notification.

2.4 File

v1: File is being sent directly from device to device over UDP. v2: File is a full mirror of N2O FTP protocol.

    File ::= SEQUENCE {
       id OCTET STRING,
       mime OCTET STRING,
       payload ANY,
       parentid OCTET STRING }

• id: Packet id
• mime: RFC MIME content tagging.
• payload: CMS ContentInfo.
• parentid: Link to parent block.

3 Event

Event is an abstraction for server-directed push messages. v1: Event is being sent directly from device to device over UDP for Message Acknowledgments. v2: Event is controlled by server (mirrors XEP-0022).

3.1 Event

In ASN.1 BUDDHA Core there could be only Message or Presence Events.

Event ::= SEQUENCE {
   id OCTET STRING,
   vsn Version,
   session OCTET STRING,
   payload EventPayload, ... }

• id: Unique event sequence ID.
• vsn: Protocol version for encoding.
• session: Network session context.
• payload: Message or Presence content.

EventPayload ::= CHOICE {
   message   [1] MessageEvent,
   presence  [2] PresenceEvent, ... }

3.2 Message Event Type

Message Event Type covers XEP-0184 (Message Delivery Receipts), XEP-0425 (Message Retraction), XEP-0308 (Last Message Correction).

MessageEventType ::= ENUMERATED { received(1),
   delivered(2), read(3), edited(4), deleted(5),
   updated(6), ... }

• received: Transport accepted the message.
• delivered: Message reached target device.
• read: Recipient viewed the content.
• edited: Original content was modified.
• deleted: Remove message from storage.

3.3 Message Event

MessageEvent ::= SEQUENCE {
   type MessageEventType,
   messageId OCTET STRING OPTIONAL,
   feed MessageFeed OPTIONAL,
   actor OCTET STRING OPTIONAL,
   timestamp INTEGER OPTIONAL, ... }

• type: Specific lifecycle event.
• messageId: Identifier of affected message.
• feed: Communication channel context.
• actor: Entity that triggered the event.
• timestamp: Precise UTC time of event.

3.4 Presence Event Type

Presence Event Type covers RFC 3921 (Presence), XEP-0085 (Chat State Notifications).

PresenceEventType ::= ENUMERATED { online(1),
   offline(2), typing(3), ... }

• online: Available for interaction.
• offline: No longer reachable.
• typing: Content composition indicator.

3.5 Presence Event

PresenceEvent ::= SEQUENCE {
   type PresenceEventType,
   feed MessageFeed OPTIONAL,
   actor OCTET STRING OPTIONAL,
   timestamp INTEGER OPTIONAL, ... }

• type: Specific presence transition.
• feed: Optional channel context.
• actor: Entity with state change.
• timestamp: Time of presence update.