idnits 2.17.1 draft-ietf-spirits-architecture-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 6 longer pages, the longest (page 3) being 66 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 7 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 23 instances of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 341 has weird spacing: '...ragraph are...' == Line 345 has weird spacing: '...for the purp...' == Line 346 has weird spacing: '...ase the proc...' == Line 347 has weird spacing: '...andards proc...' == Line 348 has weird spacing: '...it into lang...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' Summary: 4 errors (**), 0 flaws (~~), 9 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group L. Slutsman (Ed.) 2 Internet Draft AT&T Labs 3 I. Faynberg 4 Expires April 2001 H. Lu 5 M. Weissman 6 Lucent Technologies 8 The SPIRITS Architecture 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance wit all 13 provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering Task 16 Force (IETF), its areas, and its working groups. Note that other groups 17 may also distribute working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference material 21 or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt. 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 Abstract 31 This document describes the architecture for supporting SPIRITS 32 services, which are those originating in the PSTN and necessitating the 33 interactions between the PSTN and the Internet. (Internet Call Waiting, 34 Internet Caller-ID Delivery, and Internet Call Forwarding are examples 35 of SPIRIT services.) Specifically, it defines the components 36 constituting the architecture and the interfaces between the components. 38 1. Introduction 40 This document describes the architecture for supporting SPIRITS 41 services, which are those originating in the PSTN and necessitating the 42 interactions between the PSTN and the Internet. (Internet Call Waiting, 43 Internet Caller-ID Delivery, and Internet Call Forwarding are examples 44 of SPIRIT services.) Specifically, it defines the components 45 constituting the architecture and the interfaces between the 46 components. 48 The rest of the document is organized as follows: 49 + Section 2 describes example SPIRITS services from the end-user point 50 of view; 52 April 2001 54 + Section 3 describes the SPIRITS architecture; 55 + Section 4 contains security consideration; 56 + Section 5 contains acknowledgments; 57 + Section 6 contains references; and 58 + Appendix contains the figure. 60 2. Brief Description of Example SPIRITS Services 62 To illustrate the motivation for the overall SPIRIT architecture, 63 this section provides a brief description of the example SPIRITS 64 services: 65 + Internet Call Waiting (ICW), 66 + Internet Caller-ID Delivery, and 67 + Internet Call Forwarding. 69 These services are considered from the end-user point of view under 70 the assumptions below: 72 + Service subscription (or cancellation) is a separate process and 73 may be done over the telephone, via postal mail, or over the Web. 75 + The subscriber's IP host (e.g., a PC) is loaded with the necessary 76 software [including a Personal Identification Number (PIN) and the IP 77 addresses of the SPIRITS servers] for realizing the SPIRITS services. 78 The software may be sent by postal mail or downloaded from the Web. 80 + The subscriber activates a SPIRITS service by an act of service 81 session registration, which can take place anytime after he (or she) 82 is connected to the Internet. The subscriber may specify the life 83 span of the session. As soon as the session ends, the SPIRITS service 84 is deactivated. Naturally, the subscriber should also be able to 85 deactivate a SPIRITS service anytime during the service session. 87 2.1 Internet Call Waiting (ICW) 89 The Internet call waiting service enables a subscriber engaged in an 90 Internet dial-up session to 92 o be notified of an incoming call to the very same telephone line 93 that is being used for the Internet connection; 95 o specify the desirable treatment of the call; and 97 o have the call handled as specified. 99 The details of the ICW service lie in the ways that a waiting call 100 can be treated [1]. Typical ways for handling a call include: 102 + Accept the incoming call over the PSTN by terminating the Internet 103 connection. (As switching cannot be done immediately, the caller may 104 hear an opening announcement followed by the "ringing" tone.) 106 + Forward the incoming call to another telephone number. The 108 April 2001 110 subscriber will remain connected to the Internet, while the caller 111 will hear an announcement indicating the call is being forwarded and 112 eventually be connected to the new destination number. 114 + Accept the incoming call by voice over IP. The subscriber will 115 answer the incoming call via the already established Internet 116 connection. (The proposed SPIRITS architecture, however, does not 117 reflect this feature.) 119 + Redirect the incoming call to voice mail. The subscriber will 120 remain connected to the Internet, while the caller will hear an 121 announcement inviting him (or her) to leave a message. 123 + Play a pre-recorded message to the calling party and disconnect the 124 call. The subscriber will remain connected to the Internet. 126 + Reject the incoming call. The subscriber will remain connected to 127 the Internet, while the caller will hear an announcement rejecting 128 the call. 130 The subscriber may specify the call treatment on the fly when 131 notified of an incoming call. Alternatively, the subscriber may 132 specify a priori a general treatment for all calls (e.g., re-directed 133 to voice mail) or call treatments tailored to the origination 134 numbers. As a result, when a call comes in, the subscriber won't be 135 presented the call but can examine afterwards the treatment and 136 outcome of the call from the log that is kept for all the calls 137 processed during the ICW service. Typical information recorded in the 138 log includes the incoming call date and time, calling party number, 139 calling party name, and call disposition. 141 2.2 Internet Caller-ID Delivery 143 This service allows the subscriber to see the caller's number or name 144 or both while being connected to the Internet. If the subscriber has 145 only one telephone line and is using the very line for the Internet 146 connection, the service is a subset of the ICW service and follows 147 the relevant description in Section 2.1. Otherwise, the subscriber's 148 IP host serves as an auxiliary device of the telephone to which the 149 call is first sent. 151 2.3 Internet Call Forwarding 153 The Internet call forwarding service allows a service subscriber to 154 forward an incoming call to another telephone number while being 155 connected to the Internet. If the subscriber has only one telephone 156 line and is using the very line for the Internet connection, the 157 service is a subset of the ICW service and follows the relevant 158 description in Section 2.1. Otherwise, the subscriber's IP host 159 serves as an auxiliary device of the telephone to which the call is 160 first sent. 162 3. SPIRITS Architecture 164 April 2001 166 Figure 1 of the Appendix depicts the SPIRITS architecture, which 167 includes the following entities: 169 1. Service Control Function (SCF) [2], which executes service logic, 170 interacts with the entities in the IP domain (e.g., the SPIRITS Proxy 171 and PINT Server) through the SPIRITS Client, and instructs the 172 switches on how to complete a call. Physically, the SCF may be 173 located in either stand-alone general-purpose computers called 174 Service Control Points (SCPs) or specialized pieces of equipment 175 called Service Nodes (SNs) [2]. 177 2. Service Switching Function (SSF) [2], which normally resides in a 178 switch and is responsible for the recognition of Intelligent Network 179 (IN) triggers and interactions with the SCF. 181 3. SPIRITS Client, which is responsible for receiving PSTN requests 182 from the SCF as well as sending responses back. It may be co-located 183 with the SCF. If not, it communicates with the SCF over the D 184 interface. 186 4. PINT Server, which receives PINT requests from the PINT Client and 187 relays them to the PSTN for execution over the E interface. 189 5. SPIRITS Proxy, which is co-located with the PINT Server and serves 190 as an intermediary between the SPIRITS Server and SPRITS Client via 191 the B and C interfaces, respectively. 193 6. PINT Client, which resides in the subscriber's IP host and is 194 responsible for initiating PINT requests, which are sent to the PINT 195 server over the A interface. 197 7. SPIRITS Server, which terminates PSTN requests and is responsible 198 for all interactions (e.g., incoming call notification and relaying 199 the call treatment) between the subscriber and the SPIRITS proxy. 201 The rest of the Section describes the interfaces between the entities 202 in detail. 204 3.1 Interface A 206 This interface is used for sending PINT request to PINT Server. Its 207 principal use is for service session registration and as a result 208 activation of a SPIRITS service (see Section 2). In addition, this 209 interface may be used for service subscription. 211 3.2 Interface B 213 This interface serves two main purposes: 1) to notify the subscriber 214 of incoming calls together with the calling number and name, if 215 available; and 2) to send to the SPRITS Proxy the subscriber's choice 216 of call disposition specified on the fly. 218 3.3 Interface C 220 April 2001 222 This interface is used for communications between the SPIRITS Client 223 and SPIRITS Proxy. The SPIRITS Proxy may in turn communicate with 224 the SPRITS Server, or may act as a virtual server, terminating the 225 requests without sending them down to the SPIRITS Server. 227 3.4 Interface D 229 This interface is for communications between the SPIRITS Client and 230 the SCF. Specifically, from the SCF to the SPIRITS Client, the 231 parameters associated with the applicable IN triggers are sent. From 232 the SPIRITS Client to SCF, the subscriber's call disposition is sent. 233 The SCF "transforms" the user's disposition into appropriate actions, 234 such as playing an announcement to the caller, and resuming the 235 suspended call processing in the SSP. 237 3.5 Interface E 239 This interface is for sending PINT requests to the SCF for execution. 241 4. Security Considerations 243 It is assumed that the interface C is between trusting entities. In 244 addition, the assumption that the PINT Client and SPIRITS Server are 245 collocated dictates that the security considerations for the A and B 246 interfaces are exactly the same. 248 5. Acknowledgments 250 We would like to thank Alec Brusilovsky and David Shraider for their 251 comments and input. The authors would like to extend their thanks to 252 Jorgen Bjorkner and Naoto Makinae, for there email discussion on the 253 joined PINT-SPIRITS architecture. 255 6. References 257 [1] Lu, H. (Editor), I. Faynberg, J. Voelker, M. Weissman, W. Zhang, 258 S. Rhim, J. Hwang, S. Ago, S. Moeenuddin, S. Hadvani, S. Nyckelgard, 259 J. Yoakum, and L. Robart, "Pre-SPIRITS Implementations of PSTN- 260 Initiated Services ", IETF Draft, work in progress. 262 [2] Faynberg, I., L. Gabuzda, M. Kaplan, and N.Shah, "The Intelligent 263 Network Standards: Their Application to Services", McGraw-Hill, 1997. 265 April 2001 267 Appendix 269 Subscriber's IP Network 270 IP Host 272 _______________ .................... 273 | _____________ | A . ________________ . 274 | |PINT Client|*******| PINT Server |******** 275 | |___________| | : |______________| : * 276 | ____________ | : * : * 277 | | SPIRITS | | B . _______*________ : * 278 | | Server |*******|SPIRITS Proxy | : * 279 | |___________| | : |______________| : * 280 |_______________| .........*.......... * 281 *C * 282 _________________ ______*________ * 283 | Subscriber | |SPIRITS Client | * 284 | Telephone | | | * 285 |_________________| |_______________| * 286 * * * E 287 * Line * D * 288 ++++++++++*+++++++++++ PSTN +++*+++++++++++++++*++ 289 * * * 290 +-------------------+ +-----------------+ 291 | Service Switching |*****| Service Control | 292 | Function | SS7 | Function | 293 +-------------------+ +-----------------+ 295 Figure 1: SPIRITS Architecture 297 Author's Addresses 299 Igor Faynberg 300 Lucent Technologies 301 Room 4D-601A 302 101 Crawfords Corner Road 303 Holmdel, NJ 07733-3030 US 304 E-mail: faynberg@lucent.com 305 Telephone: +1 732 949 0137 307 Hui-Lan Lu 308 Lucent Technologies Room 4C-607A 309 101 Crawfords Corner Road 310 Holmdel, NJ 07733-3030 US 311 E-mail: huilanlu@lucent.com 312 Telephone: +1 732 949 0321 314 Mark Weissman 315 Lucent Technologies 316 Room NE406B 317 200 Lucent Lane 318 Cary, NC 27511 320 April 2001 322 E-mail: maw1@lucent.com 323 Telephone: +1 919 463 3258 325 Lev Slutsman 326 AT&T Labs 327 Room D5-3D26 328 200 Laurel Avenue 329 Middletown, NJ 07748 330 E-mail: slutsman@att.com 331 Telephone: 732-420-3756 333 Full Copyright Statement 335 Copyright (C) The Internet Society (1998). All Rights Reserved. 337 This document and translations of it may be copied and furnished to 338 others, and derivative works that comment on or otherwise explain it 339 or assist in its implementation may be prepared, copied, published 340 and distributed, in whole or in part, without restriction of any 341 kind, provided that the above copyright notice and this paragraph are 342 included on all such copies and derivative works. However, this 343 document itself may not be modified in any way, such as by removing the 344 copyright notice or references to the Internet Society or other 345 Internet organizations, except as needed for the purpose of 346 developing Internet standards in which case the procedures for 347 copyrights defined in the Internet Standards process must be 348 followed, or as required to translate it into languages other than 349 English. The limited permissions granted above are perpetual and will 350 not be revoked by the Internet Society or its successors or assigns. 351 This document and the information contained herein is provided on an 352 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 353 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 354 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 355 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 356 FITNESS FOR A PARTICULAR PURPOSE. 358 April 2001