ILP-301 Added WirelineFormat and InteractionRole XID ENUM Specifications. Provi…
…ding these enable use in conduit implementations. Not required but helpful.
Showing
1 changed file
with
18 additions
and
0 deletions
| ... | @@ -41,5 +41,23 @@ | ... | @@ -41,5 +41,23 @@ | 
| 41 | <elem name="reserved" type="Tensor.uint16" multiplicity="1" ord="64"/> | 41 | <elem name="reserved" type="Tensor.uint16" multiplicity="1" ord="64"/> | 
| 42 | </struct> | 42 | </struct> | 
| 43 | 43 | ||
| 44 | <enum name="WirelineFormat" type="Tensor.uint8" default="undefined"> | ||
| 45 | <comment>Enum defines the wireline data format of XID interactions. These are defined to facilitate standard definitions within XID interactions independent of the | ||
| 46 | specific transport protocol or XID conduit.</comment> | ||
| 47 | <literal name ="undefined" value = "0"/> | ||
| 48 | <literal name ="binary" value = "1"/> | ||
| 49 | <literal name ="base64" value = "2"/> | ||
| 50 | <literal name ="hex" value = "3"/> | ||
| 51 | </enum> | ||
| 52 | |||
| 53 | <enum name="InteractionRole" type="Tensor.uint8" default="undefined"> | ||
| 54 | <comment>InteractionRole defines the role of the conduit in a XID interaction. | ||
| 55 | A Conduit port must adopt either the target or initiator role to preserve | ||
| 56 | interaction continuity and conventions.</comment> | ||
| 57 | <literal name ="undefined" value = "0"/> | ||
| 58 | <literal name ="target" value = "1"/> | ||
| 59 | <literal name ="initiator" value = "2"/> | ||
| 60 | </enum> | ||
| 61 | |||
| 44 | </namespace> | 62 | </namespace> | 
| 45 | </specification> | 63 | </specification> | ... | ... | 
- 
Please register or sign in to post a comment