idnits 2.17.1 draft-ietf-spirits-sip-evt-package-02.txt: ** The Abstract section seems to be numbered 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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 6 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** 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 19 instances of too long lines in the document, the longest one being 5 characters in excess of 72. ** The abstract seems to contain references ([2], [3], [4], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 113 has weird spacing: '...essages are d...' == Line 150 has weird spacing: '... INDPs user...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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) -- Looks like a reference, but probably isn't: 'Lu' on line 175 -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' ** Downref: Normative reference to an Informational RFC: RFC 3136 (ref. '3') == Outdated reference: A later version (-03) exists of draft-ietf-spirits-in-01 -- Possible downref: Normative reference to a draft: ref. '4' Summary: 8 errors (**), 0 flaws (~~), 6 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group I. Faynberg 3 Internet Draft Lucent Technologies 4 J. Gato 5 Expires September 2002 Vodaphone 6 V. Gurbani 7 H. Lu 8 Lucent Technologies 10 Toward the Definition of the SIP Events Package for SPIRITS Protocol 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with all 15 provisions of Section 10 of RFC2026. 17 Internet-Drafts are working documents of the Internet Engineering Task 18 Force (IETF), its areas, and its working groups. Note that other groups 19 may also distribute working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference material 23 or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt. 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 1. Abstract 33 This document describes the definition of the SIP Event 34 Package for SPIRITS, based on on the structure defined in [1], the 35 SPIRITS protocol requirements documented in [2], the overall SPIRITS 36 Architecture presented in RFC 3136 [3], the discussion at the 37 Salt Lake City meeting, and the subsequent decisions. To this end, 38 the document defines the package and event names, and addresses 39 the SUBSCRIBE paramaters. 41 This document is not intended as a stand-alone one; instead, it is 42 expected to be a module of the future SPIRITS protocol RFC when merged 43 with the work developed in [4] and other protocol-specific contributions. 44 For this reason, this document is not self-sufficient; the information in 45 references [2] and [3] is essential in understanding this Internet-Draft. 47 Toward SPIRITS SIP Events Package-Faynberg-Gato-Gurbani-Lu February 2002 49 2. Conventions used in this document 51 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 52 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 53 document are to be interpreted as described in RFC 2119. 55 3. Introduction 57 The rest of this document is organized as follows: section 4 defines the 58 package; section 5 provides a table for IANA registration; and sections 59 6, 7, and 8 respectively contain, acknowledgements, references, and 60 authors' addresses. 62 4. Definition of the Packages' and Subpackages' Names 64 The SPIRITS events package, named "spirits," has two subpackages: 65 "INDPs," for the events that correspond to IN Detection points; 66 and "user-prof", for the events related to the user profile 67 information. The semantics of these packages is explained in 68 the following subsections. 70 4.1 Sub-package "INDPs" 72 INDPs is a terminal sub-package. The information specific to the IN 73 Detection Points (DPs), including the names of the DPs is encoded.. 74 According to [2], the following DPs are handled in this way: 76 "OAA" (origination_attempt_authorized) 77 "AI" (Analyzed Info) 78 "CI" (Collected_Info) 79 "OA" (O_Answer) 80 "OTS" (O_Term_Seized) 81 "TAns"(T_Answer) 82 "ONA" (O_No_Answer) 83 "RSF" (Route_Select_Failure) 84 "TNA" (T_No_Answer) 85 "OCB" (O_Called_Party_Busy) 86 "OMC" (O_Mid_Call) 87 "TMC" (T_Mid_Call) 88 "OA" (O_Abandon) 89 "OD" (O_Disconnect) 90 "Tab" (T_Abandon) 91 "TD" (T_Disconnect) 92 "TAA" (Termination_Attempt_Authorized) 93 "FSA" (Facility_Selected_and_Available) 94 "TB" (T_Busy) 96 Toward SPIRITS SIP Events Package-Faynberg-Gato-Gurbani-Lu February 2002 98 The DP information is XML-encoded and carried in 99 the body of the SUBSCRIBE, as shown in the following 100 example: 102 SUBSCRIBE sip:gateway.provide.com SIP/2.0 103 Events: spirits.INDPs 104 Content-Type: application/spirits-events 105 Content-Length: 27 107 108 109 110 ... 112 The XML schema and DTD for the bodies of both the SUBSCRIBE and 113 NOTIFY messages are described in the companion document. 115 4.2 Sub-package "user-prof" 117 Similarly, the "user-prof" sub-package is terminal. 119 Its specific events are 121 "LUS" (Location Update in the same VLR service area) 122 "LUA" (Location Update in another VLR service area) 123 "IA" (IMSI Attach) 124 "MSID" (MS-initated IMSI Detach) 125 "NID" (Network-initiated IMSI Detach) 127 An example of encoding this information 128 in the body of the SUBSCRIBE is as follows: 130 SUBSCRIBE sip:gateway.provide.com SIP/2.0 131 Events: spirits.INDPs 132 Content-Type: application/spirits-events 133 Content-Length: 27 135 136 137 138 ... 140 Figure 1 summarizes the package naming and the respective 141 functions of both packages as a tree, whose leaves denote 142 the XML-encoded information. 144 Toward SPIRITS SIP Events Package-Faynberg-Gato-Gurbani-Lu February 2002 146 spirits 147 /( 148 / ( 149 / ( 150 INDPs user-prof 151 / ( 152 / ( 153 / ( 154 +-----------------+ +--------------+ 155 | OAA, AI, CI, OA,| | LUS, LUA, IA | 156 | TAns, ONA, RSF, | | MSID, NID | 157 | TNA, OCB, OMC, | +--------------+ 158 | TMC, OA, OD, | 159 | Tab, TD, TAA, | 160 | FSA, TB, OTS | 161 +-----------------+ 163 Figure 1: The Tree for SPIRITS Subpackages 165 5. IANA Registration Information 167 The package names are further summarized in Table 1 for IANA 168 registration, in the format suggested in [1]. 170 Package Name Type Contact Reference 171 ------------ ---- ------- --------- 172 spirits package [Lu] [SPIRITS Protocol] 173 INDPs sub-package [Lu] [SPIRITS Protocol] 175 [Lu] Hui-Lan Lu 177 REFERENCES 178 ---------- 180 [SPIRITS Protocol] *TBD* 182 Table 1: Package Names for IANA Consideration 184 6. Acknowledgements 186 Toward SPIRITS SIP Events Package-Faynberg-Gato-Gurbani-Lu February 2002 188 The authors are grateful to Wayne Zeuch for providing us with the 189 break-out of DPs among the IN Capability sets and Lawrence Conroy for 190 many an incisive comments and suggestions. 192 7. References 194 [1] A. Roach, Event Notification in SIP, , Work in Progress. July 2001. 197 [2] Faynberg, I. (Ed.), J. Gato, H. Lu, and L. Slutsman , Work in Progress. February 2002. 200 [3] Slutsman, L (Ed.) et al, The Spirits Architecture. RFC 3136 201 Informational). June 2001. 203 [4] Brusilovsky, A. et al., On selection of IN parameters to be 204 carried by the SPIRITS Protocol. draft-ietf-spirits-in-01.txt. Work 205 in Progress. September 2001. 207 8. Authors' Addresses 209 Igor Faynberg 210 Bell Labs/Lucent Technologies 211 Room 4D-601A, 101 Crawfords Corner Road 212 Holmdel, New Jersey, 07733 213 Phone: (732) 949-0137 214 Email: faynberg@lucent.com 216 Jorge Gato Airtel 217 Vodaphone 218 Avda de Europa, 1. 219 28108 Alcobendas (Madrid). 220 Spain 221 Tel: +34 607 13 31 10 Fax. +34 607 13 30 57 222 Email: jgato@vodaphone.es 224 Vijay Gurbani 225 2000 Naperville Rd., Room 6G-440 226 Naperville, IL 60566-7033 USA 227 Phone: +1 630 224 0216 228 Email: vkg@lucent.com 230 Hui-Lan Lu 231 Bell Labs/Lucent Technologies 232 Room 4C-607A, 101 Crawfords Corner Road 233 Holmdel, New Jersey, 07733 235 Toward SPIRITS SIP Events Package-Faynberg-Gato-Gurbani-Lu February 2002 237 Phone: (732) 949-0321 238 Email: huilanlu@lucent.com 240 Full Copyright Statement 242 "Copyright (C) The Internet Society (date). All Rights Reserved. This 243 document and translations of it may be copied and furnished to others, 244 and derivative works that comment on or otherwise explain it or assist 245 in its implementation may be prepared, copied, published and 246 distributed, in whole or in part, without restriction of any kind, 247 provided that the above copyright notice and this paragraph are 248 included on all such copies and derivative works. However, this 249 document itself may not be modified in any way, such as by removing the 250 copyright notice or references to the Internet Society or other 251 Internet organizations, except as needed for the purpose of developing 252 Internet standards in which case the procedures for copyrights defined 253 in the Internet Standards process must be followed, or as required to 254 translate it into followed, or as required to translate it into 255 languages other than English. 257 The limited permissions granted above are perpetual and will not be 258 revoked by the Internet Society or its successors or assigns. 260 This document and the information contained herein is provided on an 261 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 262 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 263 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 264 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 265 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 267 Toward SPIRITS SIP Events Package-Faynberg-Gato-Gurbani-Lu February 2002