...

When subscription ruleset is installed a well known Rx channel is created. The well known channel name is wellKnown_Rx with Tx_Rx channel type. This channel is used for subscription requests ..., and is meant to be publicly shared with potential subscribers. In the future this channel will use Policies to restrict events to only subscription request, making your engine more secure.

Simple Subscription

A simple subscription only contains what is needed for basic secure communication. 

To establish a basic subscription between pico A and pico B:

1. Pico A sends a subscription request on pico B well known Rx. wrangler:subscription event is used for request and must include the following attributes:
   1. wellKnown_Tx - Pico B's well known ECI. Pico A must receive an ECI to contact Pico B. (This eci will be stored after the subscription has been accepted. Events should be sent to the outbound eci, not the original subscriber eci.)
2. Pico Pico A must receive a wellKnown_Rx channel to contact Pico B.  Pico A receives a wrangler:subscription event which includes a wellKnown_Tx attribute. wellKnown_Tx is Pico B's wellKnown_Rx .  Pico A creates a channel for the subscription which stores subscription information and provides a new Rx eci for this particular subscription.Pico A sends a wrangler:pending_subscription event to Pico B, using the channel given by the subscriber_eci in step one with the following attributes:is store as Rx.
3.  
   1. name - name of subscription.
   2. name_space - name space for subscription.
   3. my_role - Pico B's role in the subscription.
   4. subscriber_role - Pico A's role in the subscription.
   5. outbound_eci - Pico A's newly created inbound ECI.
   6. channel_type - the channel type for Pico B's yet to be created inbound ECI (the same as Pico A's).  
   7. attributes - the attributes for this subscription. These are used for Pico B's incoming channel's attributes. 
4. Pico B creates a channel for the subscription which stores subscription information in the new channel and provides a new inbound eci for this particular subscription.
   Pico A also raises an internal  wrangler:pending_subscription  event with the corresponding attributes above. 
5. Upon receiving the wrangler:pending_subscription event, Pico B, creates a pending subscription (channel mentioned above) and raises the wrangler:inbound_pending_subscription_added event. Pico A raises the wrangler:outbound_pending_subscription_added event.
   The state of each Picos subscription is static at this point. Pico A has an outgoing pending subscription and Pico B has an incoming pending subscription.
6. If Pico B wants to approve the subscription request, it raises the wrangler:pending_subscription_approval event with an attribute named subscription_name giving the name of the channel/subscription to approve.  Upon successfully creating the subscription. Pico B: 
   1. sends the wrangler:pending_subscription_approved event to Pico A on Pico B's outbound_eci value stored in its subscription.
   2. raises the wrangler:subscription_added event
7. Upon receiving the wrangler:pending_subscription_approved event, Pico A adds an outbound_eci to the subscription on its side and raises the wrangler:subscription_added event. 
   1. Pico A then raises the wrangler:sending_key event to faclitate a key exchange with the pico it is subscribing to.
8. If Pico B wants to reject the subscription, it raises the wrangler:subscription_cancellation event (internally) with an attribute named subscription_name - the name of the channel/subscription to reject. Pico B:
   1. sends the wrangler:subscription_removal event to Pico A on Picos B outbound_eci, which then raises the wrangler:subscription_removed event to itself.
   2. raises the wrangler:subscription_removal event, which raises the wrangler:subscription_removed event.

...