Network Working Group M.T. Rose Internet-Draft Invisible Worlds, Inc. Expires: January 11, 2001 July 13, 2000 Mapping the BXXP Framework onto SCTP draft-mrose-beep-sctpmapping-00 Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on January 11, 2001. Copyright Notice Copyright (C) The Internet Society (2000). All Rights Reserved. Abstract This memo describes how a BXXP session is mapped onto the Stream Control Transmission Protocol. Rose Expires January 11, 2001 [Page 1] Internet-Draft Mapping the BXXP Framework onto SCTP July 2000 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Session Management . . . . . . . . . . . . . . . . . . . . . . . 4 3. Data Exchange . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Special Behavior . . . . . . . . . . . . . . . . . . . . . . . . 6 References . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7 A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 8 Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 9 Rose Expires January 11, 2001 [Page 2] Internet-Draft Mapping the BXXP Framework onto SCTP July 2000 1. Introduction This memo describes how a BXXP[1] session is mapped onto the Stream Control Transmission Protocol[2]. Refer to Section 2.5 of [1] for an explanation of the mapping requirements. Rose Expires January 11, 2001 [Page 3] Internet-Draft Mapping the BXXP Framework onto SCTP July 2000 2. Session Management The mapping of BXXP session management onto the SCTP service is straight-forward. A BXXP session is established when a SCTP association is established between two BXXP peers: o the BXXP peer that issues an ASSOCIATE call is termed the initiator; and, o the BXXP peer that receives a COMMUNICATIONS UP notification is termed the listener. During association establishment, both BXXP peers request 256 outbound SCTP streams (the maxinum number of channels allowed by BXXP). A BXXP session is released when either peer issues the SHUTDOWN call, and the SCTP association is subsequently terminated. A BXXP session is terminated when either peer issues the ABORT call, and the SCTP associated is subsequently aborted. Rose Expires January 11, 2001 [Page 4] Internet-Draft Mapping the BXXP Framework onto SCTP July 2000 3. Data Exchange The mapping of BXXP data exchange onto the SCTP service is straight-forward. Messages on a given channel are reliably sent and received using the SEND and RECEIVE calls: o the mapping between BXXP channel numbers and SCTP stream identifiers is the identity function; and, o the "unorder" flag is not present to provide orderly delivery of messages on the same BXXP channel. Note that SCTP provides flow control for each BXXP channel (SCTP stream) directly, so no additional flow control mechanisms are necessary in this mapping (unlike the mapping[3] used over a single TCP connection). Rose Expires January 11, 2001 [Page 5] Internet-Draft Mapping the BXXP Framework onto SCTP July 2000 4. Special Behavior If use of a transport security profile is negotiated, then in addition to be used over BXXP channel (SCTP stream) zero, then, each time a BXXP channel is created, a new transport security context must be negotiated over the underlying SCTP stream. Rose Expires January 11, 2001 [Page 6] Internet-Draft Mapping the BXXP Framework onto SCTP July 2000 References [1] Rose, M.T., "The Blocks eXtensible eXchange Protocol Framework", draft-mrose-bxxp-framework-01 (work in progress), July 2000. [2] Stewart, R.R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer, H.J., Taylor, T., Rytina, I., Kalla, M., Zhang, L. and V. Paxson, "Stream Control Transmission Control Protocol", draft-ietf-sigtran-sctp-12 (work in progress), July 2000. [3] Rose, M.T., "Mapping the BXXP Framework onto TCP", draft-mrose-bxxp-tcpmapping-01 (work in progress), July 2000. Author's Address Marshall T. Rose Invisible Worlds, Inc. 1179 North McDowell Boulevard Petaluma, CA 94954-6559 US Phone: +1 707 789 3700 EMail: mrose@invisible.net URI: http://invisible.net/ Rose Expires January 11, 2001 [Page 7] Internet-Draft Mapping the BXXP Framework onto SCTP July 2000 Appendix A. Acknowledgements tbd... Rose Expires January 11, 2001 [Page 8] Internet-Draft Mapping the BXXP Framework onto SCTP July 2000 Full Copyright Statement Copyright (C) The Internet Society (2000). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgement Funding for the RFC editor function is currently provided by the Internet Society. Rose Expires January 11, 2001 [Page 9]