[SCTP Binding]

["Mr. Rob Godfrey" <robert.godfrey@jpmorgan.com>]

So I guess my open questions on the SCTP Binding are

1) How do we mark initiation of the AMQP communication

In TCP we use a header AMQPxxxx ... which TCP guarantees will arrive before any subsequent frames.  In SCTP am I correct in believing this guarantee would only hold true if all communication was on the same SCTP stream.

The open frame similarly is defined as having to be sent before any other AMQP traffic on the connection. 

2) Framing.  I believe that we can do away with the need for AMQP Framing when using SCTP.  The SCTP message carries all information that is currently held in an AMQP frame with the exception of the unused extended header.  Are others comfortable with this approach.

3) Closing a connection. Similar issues to opening in that we don't have the same total ordering guarantees.  In the case of a clean shutdown this is probably not a significant issue (all AMQP Sessions will have been "end"ed prior to the close being issued... the peer can take note of the close, and wait until all open sessions are ended... or timeout after some waiting period).  (There may be a vanishingly small corner case where a sender asyncronously begins, operates on, and ends a session... and this entire sequenec is "overtaken" by the close). 

4) Security... will we continue to use SASL... if so how does the layering work.  We also need to define the TLS equivalent layer.

What other areas have I ommitted?

-- Rob