Added description as receiver supplied (#121)

Added description as receiver supplied

1. Stream's description will help the admins of a multi stream transmitters distinguish between streams created for multiple receivers

Author: appsdesh

openid-sharedsignals-framework-1_0.md

@@ -926,6 +926,12 @@ min_verification_interval
   MAY respond with a 429 status code. An Event Transmitter SHOULD NOT respond
   with a 429 status code if an Event Receiver is not exceeding this frequency.
 
+description
+
+> **Receiver-Supplied**, An optinal string to describe the properties of the stream.
+  This is useful in multi stream systems to identify the stream for human actors. The
+  transmitter may truncate the string beyond allowed max length.
+
 TODO: consider adding a IANA Registry for stream configuration metadata, similar
 to Section 7.1.1 of {{RFC8414}}. This would allow other specs to add to
 the stream configuration.
@@ -973,7 +979,8 @@ Authorization: Bearer eyJ0b2tlbiI6ImV4YW1wbGUifQo=
     "urn:example:secevent:events:type_2",
     "urn:example:secevent:events:type_3",
     "urn:example:secevent:events:type_4"
-  ]
+  ],
+  "description" : "Stream for Receiver A using events type_2, type_3, type_4"
 }
 ~~~
 {: #figcreatestreamreq title="Example: Create Event Stream Request"}
@@ -1008,7 +1015,8 @@ Content-Type: application/json
   "events_delivered": [
     "urn:example:secevent:events:type_2",
     "urn:example:secevent:events:type_3"
-  ]
+  ],
+  "description" : "Stream for Receiver A using events type_2, type_3, type_4"
 }
 ~~~
 {: #figcreatestreamresp title="Example: Create Stream Response"}
@@ -1078,7 +1086,8 @@ Cache-Control: no-store
   "events_delivered": [
     "urn:example:secevent:events:type_2",
     "urn:example:secevent:events:type_3"
-  ]
+  ],
+  "description" : "Stream for Receiver A using events type_2, type_3, type_4"
 }
 ~~~
 {: title="Example: Read Stream Configuration Response" #figreadconfigresp}
@@ -1151,7 +1160,8 @@ Cache-Control: no-store
     "events_delivered": [
       "urn:example:secevent:events:type_2",
       "urn:example:secevent:events:type_3"
-    ]
+    ],
+    "description" : "Stream for Receiver A using events type_2, type_3, type_4"
   }
 ]
 ~~~
@@ -1253,6 +1263,7 @@ Authorization: Bearer eyJ0b2tlbiI6ImV4YW1wbGUifQo=
     "urn:example:secevent:events:type_3",
     "urn:example:secevent:events:type_4"
   ],
+  "description" : "Stream for Receiver B using events type_2, type_3, type_4"
 }
 ~~~
 {: title="Example: Update Stream Configuration Request" #figupdateconfigreq}
@@ -1288,7 +1299,8 @@ Cache-Control: no-store
   "events_delivered": [
     "urn:example:secevent:events:type_2",
     "urn:example:secevent:events:type_3"
-  ]
+  ],
+  "description" : "Stream for Receiver B using events type_2, type_3, type_4"
 }
 ~~~
 {: title="Example: Update Stream Configuration Response" #figupdateconfigresp}
@@ -1347,7 +1359,8 @@ Authorization: Bearer eyJ0b2tlbiI6ImV4YW1wbGUifQo=
     "urn:example:secevent:events:type_2",
     "urn:example:secevent:events:type_3",
     "urn:example:secevent:events:type_4"
-  ]
+  ],
+  "description" : "Stream for Receiver C"
 }
 ~~~
 {: title="Example: Replace Stream Configuration Request" #figreplaceconfigreq}
@@ -1383,7 +1396,8 @@ Cache-Control: no-store
   "events_delivered": [
     "urn:example:secevent:events:type_2",
     "urn:example:secevent:events:type_3"
-  ]
+  ],
+  "description" : "Stream for Receiver C"
 }
 ~~~
 {: title="Example: Replace Stream Configuration Response" #figreplaceconfigresp}