Network Working Group Brian Bidulock INTERNET-DRAFT OpenSS7 Corporation October 16, 2005 Expires in April 2006 Session Identification Registration (SESSID) for Signalling User Adaptation Layers Status of this Memo "By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79." 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 a "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 in April 2006. Copyright Copyright (C) The Internet Society (2005). Abstract This memo describes Session Id Registration (SESSID) that provides the ability for one (listening) Application Server to indicate that a session should be established with another (accepting) Application Server for connection- and transaction-oriented messaging in the SS7 Signalling User Adaptation Layers [M3UA-BIS..TUA]. Extension parameters and procedures are added by this memo in extension to those of the User Adaptation layers to provide a closer model to that of the XNS/XTI interfaces, where one interface may be designated as a `listener' and another designated as an `acceptor'. This permits ISO B. Bidulock Version 0.4 Page 1 Internet Draft UA SESSID October 16, 2005 compliant interfaces for SCCP to maintain the same semantic for SUA and TUA. 1. Introduction 1.1. Scope 1.2. Terminology 1.3. Overview 1.3.1. Multiple SGs 1.3.1.1. Fail-over of routesets between SGs 1.3.1.2. Redirection of routesets between SGs 1.4. Sample Configurations 2. Conventions The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL", when they appear in this document, are to be interpreted as described in [RFC 2119]. 3. Protocol Elements 3.1. Parameters 3.2. Messages 4. Procedures 4.1. AS and ASP State Maintenance 4.1.1. ASP State 4.1.2. AS State 4.1.3. ASP Up Procedures 4.1.4. ASP Down Procedures 4.1.5. ASP Active Procedures 4.1.6. ASP Inactive Procedures 4.1.7. Notify Procedures 5. Examples B. Bidulock Version 0.4 Page 2 Internet Draft UA SESSID October 16, 2005 6. Security 7. IANA Considerations 0. Change History This section provides historical information on the changes made to this draft. This section will be removed from the document when the document is finalized. 0.4. Changes from Version 0.3 to Version 0.4 0.3. Changes from Version 0.2 to Version 0.3 0.2. Changes from Version 0.1 to Version 0.2 0.1. Changes from Version 0.0 to Version 0.1 0.0. Version 0.0 0.0.0. Change Log $Log: draft-bidulock-sigtran-sessid-04.me,v $ Revision 0.9.2.3 2005/10/17 11:53:46 brian - updated drafts for republication Revision 0.9.2.2 2005/05/14 08:33:20 brian - copyright header correction Revision 0.9.2.1 2004/03/16 05:10:45 brian - Added drafts and figures. Revision 0.8.2.1 2003/07/28 13:12:21 brian Reformatting. B. Bidulock Version 0.4 Page 3 Internet Draft UA SESSID October 16, 2005 R. References [M3UA-BIS] Pastor, J., Morneault, K., "Signaling System 7 (SS7) Message Transfer Part 3 (MTP3)-User Adaptation Layer (M3UA)," , Internet Engineering Task Force - Signalling Transport Working Group (October 2005). Work In Progress [SUA] Loughney, J., Sidebottom, G., Coene, L., Verwimp, G., Keller, J. and Bidulock, B., "Signalling Connection Control Part User Adaptation Layer (SUA)," RFC 3868, Internet Engineering Task Force - Signalling Transport Working Group (October, 2004). [ISUA] Bidulock, B., "SS7 ISUP-User Adaptation Layer (ISUA)," , Internet Engineering Task Force - Signalling Transport Working Group (October 16, 2005). Work In Progress. [TUA] Bidulock, B., "SS7 TCAP-User Adaptation Layer (TUA)," , Internet Engineering Task Force - Signalling Transport Working Group (October 16, 2005). Work In Progress. R.1. Normative References [RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels," RFC 2119 - BCP 14, The Internet Society (March 1997). Author's Addresses Brian Bidulock OpenSS7 Corporation 1469 Jeffreys Crescent Edmonton, AB T6L 6T1 Canada Phone: +1-780-490-1141 Email: bidulock@openss7.org URL: http//www.openss7.org/ This draft expires April 2006. B. Bidulock Version 0.4 Page 4 Internet Draft UA SESSID October 16, 2005 Table of Contents Status of this Memo ............................................. 1 Copyright ....................................................... 1 Abstract ........................................................ 1 1 Introduction .................................................. 2 1.1 Scope ....................................................... 2 1.2 Terminology ................................................. 2 1.3 Overview .................................................... 2 1.3.1 Multiple SGs .............................................. 2 1.4 Sample Configurations ....................................... 2 2 Conventions ................................................... 2 3 Protocol Elements ............................................. 2 3.1 Parameters .................................................. 2 3.2 Messages .................................................... 2 4 Procedures .................................................... 2 4.1 AS and ASP State Maintenance ................................ 2 4.1.1 ASP State ................................................. 2 4.1.2 AS State .................................................. 2 4.1.3 ASP Up Procedures ......................................... 2 4.1.4 ASP Down Procedures ....................................... 2 4.1.5 ASP Active Procedures ..................................... 2 4.1.6 ASP Inactive Procedures ................................... 2 4.1.7 Notify Procedures ......................................... 2 5 Examples ...................................................... 2 6 Security ...................................................... 3 7 IANA Considerations ........................................... 3 0 Change History ................................................ 3 0.4 Changes from Version 0.3 to Version 0.4 ..................... 3 0.3 Changes from Version 0.2 to Version 0.3 ..................... 3 0.2 Changes from Version 0.1 to Version 0.2 ..................... 3 0.1 Changes from Version 0.0 to Version 0.1 ..................... 3 0.0 Version 0.0 ................................................. 3 0.0.0 Change Log ................................................ 3 R References .................................................... 4 R.1 Normative References ........................................ 4 Author's Addresses .............................................. 4 Table of Contents ............................................... 5 B. Bidulock Version 0.4 Page 5 Internet Draft UA SESSID October 16, 2005 Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address to the IETF at ietf-ipr@ietf.org. Disclaimer of Validity This document and the information contained herein is provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), 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. Full Copyright Statement Copyright (C) The Internet Society (2005). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. B. Bidulock Version 0.4 Page 6