A.
 +A1.   IN
 A2.   IN, OFAULT? "NACK"
 A3.   (IN | IFAULT)
B. (REQ-REPLY)
 B1.   (IN | IFAULT), (OUT | OFAULT)
 +B2.   IN, (OUT | OFAULT)
 B3.   (IN, OUT, IFAULT?) | (IN, OFAULT)
C. (REQ-REPLIES)
 C1.   IN, (OUT* | OFAULT)
 +C2.   IN, OUT*   (+ FAULTS TBD)
 C4.   IN, OUT*, (OUT | OFAULT)?
 C5.   IN, (OUT | OFAULT)*
D.
 +D1.   OUT
 D2.   OUT, IFAULT? "NACK"
+E.     OUT, (IN | IFAULT)
+F.     OUT, IN* (+ FAULTS TBD)
G.     OUT, IN, OFAULT
H.     IN, OUT, IFAULT


<operation meep="rr">
 DIR     MSG   FAULT?
 ---------------------
 IN     MY:X     N
 OUT    MY:Y     N
 OUT    MY:Z1    Y
 OUT    MY:Z2    Y
 OUT    MY:Z3    Y
</operation>


new set (using the front +s in th first list):
A1. IN
B2. IN, (OUT | OFAULT)
C2. IN, OUT* (+ FAULTS TBD)
D1. OUT
E. OUT, (IN | IFAULT)
F. OUT, IN* (+ FAULTS TBD)

What is the general rule for faults?
   
+C21. IN, (OUT* | OFAULT)
 -> C21 is NOT acceptable.
+C22. IN, (OUT | OFAULT)*
 -> C22 is NOT acceptable.
C23. IN, OUT*, OFAULT?
 -> C23 is acceptable.

 - Can we have more than one fault?
   fault means "if you still care, start again". all bets off.


+F1. OUT, IN*, IFAULT?
+F2. OUT, (IN | IFAULT)(n)*
F3. OUT, (IN* | IFAULT)
  
#of "other" endpoints?
explicit termination?


final set (written from the server view):
 (A1, B2, C23, D1, E, F1 == 1 other endpoint)
 (F2 == N other endpoints)
                            (who needs to provide a definition)
A1.  IN                       Microsoft
B2.  IN, (OUT | OFAULT)       Microsoft
C23. IN, OUT*, OFAULT?        Microsoft
D1.  OUT                      Microsoft
E.   OUT, (IN | IFAULT)       Microsoft
F1.  OUT, IN*, IFAULT?        Microsoft
F2.  OUT, (IN | IFAULT)(n)*   Tibco/Amy
    (or is it out(n)? Is it b2 from the client view?)

FAULTS IN OP (NOT EXHAUSITVE)
+= FAULT in BINDING
   (NOT EXHAUSITVE)
(+= OTHERS NOT DECLARED ANYWHERE)