Network Working Group Brian Bidulock INTERNET-DRAFT OpenSS7 Corporation Expires in six months January 2, 2003 Session Identification Registration (SESSID) for Signalling User Adaptation Layers Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 or RFC 2026. 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 To learn the current status of any Internet-Draft, please check the Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 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...TUA01]. 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 compliant interfaces for SCCP to maintain the same semantic for SUA and TUA. B. Bidulock Version 0.1 Page 1 Internet Draft UA SESSID January 2, 2003 1. Introduction 1.1. Scope 1.2. Change History 1.3. Terminology 1.4. Overview 1.4.1. Multiple SGs 1.4.1.1. Fail-over of routesets between SGs 1.4.1.2. Redirection of routesets between SGs 1.5. 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.1 Page 2 Internet Draft UA SESSID January 2, 2003 6. Security 7. IANA Considerations Notes References M3UA. G. Sidebottom, K. Morneault and J. Pastor-Balbas, (eds), "Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)," RFC 3332, Internet Engineering Task Force - Signalling Transport Working Group (September, 2002). SUA14. J. Loughney, G. Sidebottom, L. Coene, G. Verwimp, J. Keller and B. Bidulock, "SS7 SCCP-User Adaptation Layer (SUA)," , Internet Engineering Task Force - Signalling Transport Working Group (June 30, 2002). Work In Progress. ISUA00. B. Bidulock, "SS7 ISUP-User Adaptation Layer (ISUA)," , Internet Engineering Task Force - Signalling Transport Working Group (January 5, 2003). Work In Progress. TUA01. B. Bidulock, "SS7 TCAP-User Adaptation Layer (TUA)," , Internet Engineering Task Force - Signalling Transport Working Group (January 2, 2003). Work In Progress. RFC 2119. S. Bradner, "Key words for use in RFCs to Indicate Requirement Levels," RFC 2119 - BCP 14, The Internet Society (March 1997). Author's Addresses Brian Bidulock Phone: +1-780-490-1141 OpenSS7 Corporation Email: bidulock@openss7.org 1469 Jeffreys Crescent URL: http//www.openss7.org/ Edmonton, AB T6L 6T1 Canada This Internet draft expires July, 2003. B. Bidulock Version 0.1 Page 3 Internet Draft UA SESSID January 2, 2003 List of Illustrations Table of Contents Status of this Memo ........................................... 1 Abstract ...................................................... 1 1 Introduction ................................................ 2 1.1 Scope ..................................................... 2 1.2 Change History ............................................ 2 1.3 Terminology ............................................... 2 1.4 Overview .................................................. 2 1.4.1 Multiple SGs ............................................ 2 1.5 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 Notes ......................................................... 3 References .................................................... 3 Author's Addresses ............................................ 3 List of Illustrations ......................................... 4 B. Bidulock Version 0.1 Page 4 Internet Draft UA SESSID January 2, 2003 Copyright Statement Copyright (C) The Internet Society (2003). 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 procedure for copyrights defined in the Internet Standards process must be followed, or as required to translate into languages other than English. The limited permission 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 MECHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. B. Bidulock Version 0.1 Page 5