Debian Codegraph @

rfc3939.html

raw
1 <pre>Network Working Group G. Parsons
2 Request for Comments: 3939 J. Maruszak
3 Category: Standards Track Nortel Networks
4 December 2004
5
6
7 <span class="h1">Calling Line Identification for Voice Mail Messages</span>
8
9 Status of this Memo
10
11 This document specifies an Internet standards track protocol for the
12 Internet community, and requests discussion and suggestions for
13 improvements. Please refer to the current edition of the "Internet
14 Official Protocol Standards" (STD 1) for the standardization state
15 and status of this protocol. Distribution of this memo is unlimited.
16
17 Copyright Notice
18
19 Copyright (C) The Internet Society (2004).
20
21 Abstract
22
23 This document describes a method for identifying the originating
24 calling party in the headers of a stored voice mail message. Two new
25 header fields are defined for this purpose: Caller_ID and
26 Called_Name. Caller_id is used to store sufficient information for
27 the recipient to callback, or reply to, the sender of the message.
28 Caller-name provides the name of the person sending the message.
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Parsons &amp; Maruszak Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc3939">RFC 3939</a> Calling Line Identification December 2004</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
60 <a href="#section-2">2</a>. Conventions Used in this Document. . . . . . . . . . . . . . . <a href="#page-3">3</a>
61 <a href="#section-3">3</a>. Calling Line Identification Field. . . . . . . . . . . . . . . <a href="#page-3">3</a>
62 <a href="#section-3.1">3.1</a>. Internal Call. . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
63 <a href="#section-3.2">3.2</a>. External Call. . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
64 <a href="#section-3.3">3.3</a>. Numbering Plan . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
65 <a href="#section-3.4">3.4</a>. Date Header. . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
66 <a href="#section-4">4</a>. Caller Name Field. . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
67 <a href="#section-5">5</a>. Formal Syntax. . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
68 <a href="#section-5.1">5.1</a>. Calling Line Identification Syntax . . . . . . . . . . . <a href="#page-6">6</a>
69 <a href="#section-5.2">5.2</a>. Caller Name Syntax . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
70 <a href="#section-5.3">5.3</a>. Examples . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
71 <a href="#section-6">6</a>. Other Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
72 <a href="#section-7">7</a>. Security Considerations. . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
73 <a href="#section-8">8</a>. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
74 <a href="#section-9">9</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
75 <a href="#section-9.1">9.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
76 <a href="#section-9.2">9.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
77 <a href="#section-10">10</a>. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
79 Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
80
81 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
82
83 There is currently a need for a mechanism to identify the originating
84 party of a voice mail message, outside of the "FROM" header
85 information. The telephone number and name of the caller are
86 typically available from the telephone network, but there is no
87 obvious header field to store this in an Internet Mail message.
88
89 This information is intended for use when the VPIM message format is
90 used for storing "Call Answer" voice messages in an Internet Mail
91 message store, i.e., the calling party leaves a voice message for the
92 recipient, who was unable to answer the call. The implication is
93 that there is no <a href="./rfc2822">RFC 2822</a> address known for the originator.
94
95 [<a id="ref-VPIMV2R2">VPIMV2R2</a>] suggests the originating number be included as an Internet
96 address, using the first method shown below. There are several other
97 ways to store this information, but they all involve some
98 manipulation of the "From" field. For example:
99
100 1. From: "416 555 1234" &lt;non-mail-user@host&gt;
101 2. From: "John Doe" &lt;4165551234@host&gt;
102 3. From: unknown:;
103
104
105
106
107
108 <span class="grey">Parsons &amp; Maruszak Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc3939">RFC 3939</a> Calling Line Identification December 2004</span>
111
112
113 Since any of these is a forced translation, it would be useful to
114 store the calling party's name and number as presented by the
115 telephone system to the called party without manipulation. This
116 would allow the calling party's information to be displayed to the
117 recipient (similar to it appearing on the telephone) and also allow
118 future determination of an Internet address for the originator (if
119 one exists). Note that there is no requirement to store meta-data
120 (e.g., type of number, presentation restricted), as this information
121 is not presented to the called party and is generally not available
122 to voice mail systems. The intent is to store the available
123 information to an analog (non-ISDN) phone (e.g., per [<a href="#ref-T1.401" title=" or Visual Message-Waiting Indicator Features">T1.401</a>] in
124 North America).
125
126 [<a id="ref-RFC2076">RFC2076</a>] currently lists "phone" as an Internet message header which
127 would hold the originating party's telephone number, but it is listed
128 as "non-standard", i.e., usage of this header is not generally
129 recommended. It also has no defined format, making the information
130 unparsable. There is no similar entry for the originator's name.
131
132 It is proposed that two new message header fields be included to hold
133 this information, namely the Calling Line Identification ("Caller-
134 ID") and Caller Name ("Caller-Name").
135
136 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions Used in this Document</span>
137
138 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
139 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
140 document are to be interpreted as described in <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
141
142 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Calling Line Identification Field</span>
143
144 The Calling Line Identification header ("Caller-ID") holds sufficient
145 information for the recipient's voice mail system to call back, or
146 reply to, the sender of the message. The number that is contained in
147 this header is supplied by the telephone system. The exact format of
148 the data received depends on the type of call, that is -- internal or
149 external call.
150
151 Note that for both options, the number field MUST contain only the
152 digits of the number and MUST be representable using the American
153 Standard Code for Information Interchange [<a href="#ref-ASCII" title="ANSI X3.4">ASCII</a>] character set; it
154 does not include any separating character (e.g., "-").
155
156 It is expected that default, likely to be the most common case, will
157 not have any numbering plan semantic associated with the number.
158 However, in the case that it is known, an optional "NumberingPlan"
159 parameter MAY be used to indicate the semantic.
160
161
162
163
164 <span class="grey">Parsons &amp; Maruszak Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc3939">RFC 3939</a> Calling Line Identification December 2004</span>
167
168
169 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Internal Call</span>
170
171 For an internal call (e.g., between two extensions within the same
172 company), it is sufficient to relay only the extension of the calling
173 party, based on the company dialing plan.
174
175 However, the support of longer numbers may be supported by the
176 enterprise phone system.
177
178 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. External Call</span>
179
180 For an international call, the calling party's number must be the
181 full international number as described in [<a href="#ref-E.164">E.164</a>], i.e., Country Code
182 (CC), National Destination Code (NDC), and Subscriber Number (SN).
183 Other information, such as prefixes or symbols (e.g., "+"), MUST NOT
184 be included. [<a href="#ref-E.164">E.164</a>] allows for numbers of up to 15 digits.
185
186 For a call within North America, it is also suggested that 15 digits
187 per [<a href="#ref-T1.625" title=" Telecommunications - Integrated Services Digital Network (ISDN) _ Calling Line identification Presentation and Restriction Supplementary Services">T1.625</a>] be supported. However, some service providers may only
188 support 10 digits as described in [<a href="#ref-T1.401" title=" or Visual Message-Waiting Indicator Features">T1.401</a>] and [<a href="#ref-GR-31-CORE" title="&quot;CLASS Feature: Calling Number Delivery&quot;">GR-31-CORE</a>]. Though
189 it is desirable that an international number not be truncated to 10
190 digits if it contains more, it is recognized that limitations of
191 various systems will cause this to happen.
192
193 Implementors of this specification should be aware that some phone
194 systems are known to truncate international numbers, even though this
195 behavior is undesirable.
196
197 Note that the other defined fields available to non-analog systems
198 (e.g., subaddress, redirecting number), as well as the meta-data, are
199 not intended to be stored in this header.
200
201 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Numbering Plan</span>
202
203 In this baseline case (i.e., analog lines), no numbering plan
204 information is known or implied. However, in the case that a
205 numbering plan is known, an optional "NumberingPlan" parameter MAY be
206 used to indicate the semantic. Only three semantics are defined:
207 "unknown", "local", and "e164". "unknown" is the default if no
208 numbering plan semantic is known (and the default if the parameter is
209 absent). "local" has meaning only within the domain of the voice
210 mail system that stored the message (i.e., the voice mail system
211 knows that the number belongs to a local numbering plan). "e164"
212 indicates that the number is as described in [<a href="#ref-E.164">E.164</a>]. "x-" may be
213 used to indicate enterprise or service specific dialing plans.
214
215
216
217
218
219
220 <span class="grey">Parsons &amp; Maruszak Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc3939">RFC 3939</a> Calling Line Identification December 2004</span>
223
224
225 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Date Header</span>
226
227 The date and time may be included by the telephone system with the
228 calling party's telephone number per [<a href="#ref-T1.401" title=" or Visual Message-Waiting Indicator Features">T1.401</a>]. This MAY be used, as
229 there is an existing "Date" Internet header to hold this information.
230 It is a local implementation decision whether this time or the local
231 system time will be recorded in the "Date" header.
232
233 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Caller Name Field</span>
234
235 The name of the person sending the message is also important.
236 Information about whether the call is internal or external may be
237 included if it is available. This information may not be available
238 on international calls.
239
240 Further, the exact format for this field is typically a service
241 provider option per [<a href="#ref-T1.641" title=" Telecommunications - Calling Name Identification Presentation">T1.641</a>]. It is possible for the caller's name
242 to be sent in one of several character sets depending on the service
243 provider signaling transport (e.g., ISDN-UP, SCCP, TCAP). These
244 include:
245
246 1) International Reference Alphabet (IRA), formerly know as
247 International Alphabet No.5 or IA5 [<a href="#ref-T.50">T.50</a>]
248 2) Latin Alphabet No. 1 [<a href="#ref-8859-1">8859-1</a>]
249 3) American National Standard Code for Information Interchange
250 [<a href="#ref-ASCII" title="ANSI X3.4">ASCII</a>]
251 4) Character Sets for the International Teletex Service [<a href="#ref-T.61">T.61</a>]
252
253 Of these, the IRA and T.61 character sets contain a number of options
254 that help specify national and application oriented versions. If
255 there is no agreement between parties to use these options, then the
256 7-bit character set in which the graphical characters of IRA, T.61,
257 and ASCII are coded exactly the same, will be assumed. Further, the
258 7-bit graphical characters of [<a href="#ref-8859-1">8859-1</a>] are the same as in [<a href="#ref-ASCII" title="ANSI X3.4">ASCII</a>].
259
260 Note that for delivery to customer equipment in North America, the
261 calling name MUST be presented in ASCII per [<a href="#ref-T1.401" title=" or Visual Message-Waiting Indicator Features">T1.401</a>].
262
263 As a result, for the caller name header defined in this document,
264 characters are represented with ASCII characters. However, if a name
265 is received that cannot be represented in 7-bit ASCII, it MAY be
266 stored using its native character set as defined in [<a href="./rfc2047" title="&quot;MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text &quot;">RFC2047</a>].
267
268 In telephone networks, the length of the name field MUST NOT exceed
269 50 characters, as defined in [<a href="#ref-T1.641" title=" Telecommunications - Calling Name Identification Presentation">T1.641</a>]. However, service providers
270 may choose to further limit this to 15 characters for delivery to
271 customer equipment, e.g., [<a href="#ref-T1.401" title=" or Visual Message-Waiting Indicator Features">T1.401</a>] and [<a href="#ref-GR-1188-CORE" title="&quot;CLASS Feature: Calling Name Delivery Generic Requirements&quot;">GR-1188-CORE</a>].
272
273
274
275
276 <span class="grey">Parsons &amp; Maruszak Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc3939">RFC 3939</a> Calling Line Identification December 2004</span>
279
280
281 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Formal Syntax</span>
282
283 Both Calling Line Identification and Caller Name follow the syntax
284 specification using the augmented Backus-Naur Form (BNF) as described
285 in [<a href="./rfc2234" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">RFC2234</a>]. While the semantics of these headers are defined in
286 sections <a href="#section-4">4</a> and <a href="#section-5">5</a>, the syntax uses the 'unstructured' token defined in
287 [<a href="./rfc2822" title="&quot;Internet Message Format&quot;">RFC2822</a>]:
288
289 unstructured = *([FWS] utext) [FWS]
290
291 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Calling Line Identification Syntax</span>
292
293 "Caller-ID" ":" 1*DIGIT [ "," "NumberingPlan="
294 ( "unknown" / "local" / "e164" / ietf-token / x-token ) ] CRLF
295
296 ietf-token := &lt;An extension token defined by a
297 standards-track RFC and registered
298 with IANA.&gt;
299
300 x-token := &lt;The two characters "X-" or "x-" followed, with
301 no intervening white space, by any token&gt;
302
303 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Caller Name Syntax</span>
304
305 "Caller-Name" ":" unstructured CRLF
306
307 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Examples</span>
308
309 To: [email protected]
310 Caller-ID: 6137684087
311 Caller-Name: Derrick Dunne
312
313 To: [email protected]
314 Caller-ID: 6139416900
315 Caller-Name: Jean Chretien
316
317 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Other Considerations</span>
318
319 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Compatibility with Other Internet Phone Numbers</span>
320
321 The intent of these headers are to record telephone number that is
322 sent by the analog phone system with an incoming call without
323 alteration or interpretation. If sufficient semantic is known or can
324 be inferred, this may be included in the NumberingPlan field. This
325 may allow it to be later translated into an addressable phone number.
326 Addressable or dialable phone numbers (which this document does not
327 define) are defined in other documents, such as GSTN address
328 [<a href="./rfc3191" title="&quot;Minimal GSTN address format in Internet Mail&quot;">RFC3191</a>] or telephone URL [<a href="./rfc2806" title="&quot;URLs for Telephone Calls&quot;">RFC2806</a>].
329
330
331
332 <span class="grey">Parsons &amp; Maruszak Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc3939">RFC 3939</a> Calling Line Identification December 2004</span>
335
336
337 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Usage</span>
338
339 There are a few scenarios of how this mechanism may fail that must be
340 considered. The first is mentioned in <a href="#section-3.2">section 3.2</a> - the truncation
341 of an international number to 10 digits. This could result in a
342 misinterpretation of the resulting number. For instance, an
343 international number (e.g., from Ireland) of the form "353 91 73
344 3307" could be truncated to "53 91 73 3307" if received in North
345 America, and interpreted as "539 917 3307" - a seemingly "North
346 American" style number. Thus, the recipient is left with incorrect
347 information to reply to the message, possibly with an annoyed callee
348 at the North American number.
349
350 The second scenario is the possibility of sending an internal
351 extension to an external recipient when a Call Answer message is
352 forwarded. This poses two problems, the recipient is given the wrong
353 phone number, and the company's dialing plan could be exposed.
354
355 The final concern deals with exercising character options that are
356 available in coding the Calling Name field. An international system
357 may send a message with coding options that are not available on the
358 receiving system, thus giving the recipient an incorrect Caller Name.
359
360 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
361
362 Note that unlisted and restricted numbers are not a concern as these
363 header fields are defined to contain what the called party would see
364 (e.g., 'Private Name'), as opposed to the complete details exchanged
365 between service providers.
366
367 However, it must also be noted that this mechanism allows the
368 explicit indication of phone numbers in the headers of an email
369 message (used to store voice messages). While the rationale for this
370 is reviewed in <a href="#section-1">section 1</a>, the recipient of this message may not be
371 aware that this information is contained in the headers unless the
372 user's client presents the information. Its use is intended to be
373 informative as it is when it appears on a telephone screen.
374
375 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
376
377 This document defines an IANA-administered registration space for
378 Caller-ID numbering plans in <a href="#section-5.1">section 5.1</a>. Each registry entry
379 consists of an identifying token and a short textual description of
380 the entry. There are three initial entries in this registry:
381
382 unknown - The number's semantics are unknown. This value is the
383 default in the absence of this parameter.
384
385
386
387
388 <span class="grey">Parsons &amp; Maruszak Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc3939">RFC 3939</a> Calling Line Identification December 2004</span>
391
392
393 local - The number only has meaning within the domain of the
394 sending system identified by the <a href="./rfc2822">RFC 2822</a> From field of
395 the message.
396
397 e164 - The number's semantics are described in [<a href="#ref-E.164">E.164</a>].
398
399 The only way to add additional entries (ietf-token in <a href="#section-5.1">section 5.1</a>) to
400 this registry is with a standards-track RFC.
401
402 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
403
404 <span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span>
405
406 [<a id="ref-VPIMV2R2">VPIMV2R2</a>] Vaudreuil, G. and G. Parsons, "Voice Profile for
407 Internet Mail - version 2 (VPIMv2)", <a href="./rfc3801">RFC 3801</a>, June
408 2004.
409
410 [<a id="ref-RFC2047">RFC2047</a>] Moore, K., "MIME (Multipurpose Internet Mail
411 Extensions) Part Three: Message Header Extensions for
412 Non-ASCII Text ", <a href="./rfc2047">RFC 2047</a>, November 1996.
413
414 [<a id="ref-RFC2822">RFC2822</a>] Resnick, P., "Internet Message Format", <a href="./rfc2822">RFC 2822</a>,
415 April 2001.
416
417 [<a id="ref-RFC2234">RFC2234</a>] Crocker, D. and P. Overell, "Augmented BNF for Syntax
418 Specifications: ABNF", <a href="./rfc2234">RFC 2234</a>, November 1997.
419
420 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
421 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
422
423 <span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
424
425 [<a id="ref-RFC2076">RFC2076</a>] Palme, J., "Common Internet Message Headers", <a href="./rfc2076">RFC</a>
426 <a href="./rfc2076">2076</a>, February 1997.
427
428 [<a id="ref-E.164">E.164</a>] ITU-T Recommendation E.164 (1997), "The international
429 public telecommunication numbering plan"
430
431 [<a id="ref-T.50">T.50</a>] ITU-T Recommendation T.50 (1992), "International
432 Reference Alphabet (IRA)"
433
434 [<a id="ref-T.61">T.61</a>] CCITT Recommendation T.61 (1988) (Withdrawn),
435 "Character Repertoire and Coded Character Sets for the
436 International Teletex Service"
437
438
439
440
441
442
443
444 <span class="grey">Parsons &amp; Maruszak Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc3939">RFC 3939</a> Calling Line Identification December 2004</span>
447
448
449 [<a id="ref-8859-1">8859-1</a>] ISO/IEC International Standard 8859-1 (1998),
450 Information Technology _ 8-bit single-byte coded
451 graphic character sets _ Part 1: Latin Alphabet No. 1
452
453 [<a id="ref-ASCII">ASCII</a>] American National Standards Institute (ANSI), Coded
454 Character Set - 7-Bit American National Standard Code
455 for Information Interchange, ANSI X3.4, 1986.
456
457 [<a id="ref-T1.401">T1.401</a>] American National Standards Institute (ANSI),
458 Telecommunications _ Network-to-Customer Installation
459 Interfaces _ Analog Voicegrade Switched Access Lines
460 with Calling Number Delivery, Calling Name Delivery,
461 or Visual Message-Waiting Indicator Features, ANSI
462 T1.6401.03-1998
463
464 [<a id="ref-T1.625">T1.625</a>] American National Standards Institute (ANSI),
465 Telecommunications - Integrated Services Digital
466 Network (ISDN) _ Calling Line identification
467 Presentation and Restriction Supplementary Services,
468 ANSI T1.625-1993
469
470 [<a id="ref-T1.641">T1.641</a>] American National Standards Institute (ANSI),
471 Telecommunications - Calling Name Identification
472 Presentation, ANSI T1.641-1995
473
474 [<a id="ref-GR-1188-CORE">GR-1188-CORE</a>] Telcordia Technologies, "CLASS Feature: Calling Name
475 Delivery Generic Requirements", GR-1188-CORE, Issue 2,
476 December 2000
477
478 [<a id="ref-GR-31-CORE">GR-31-CORE</a>] Telcordia Technologies, "CLASS Feature: Calling Number
479 Delivery", GR-31-CORE, Issue 1, June 2000
480
481 [<a id="ref-RFC3191">RFC3191</a>] Allocchio, C., "Minimal GSTN address format in
482 Internet Mail", <a href="./rfc3191">RFC 3191</a>, October 2001.
483
484 [<a id="ref-RFC2806">RFC2806</a>] Vaha-Sipila, A., "URLs for Telephone Calls", <a href="./rfc2806">RFC 2806</a>,
485 April 2000.
486
487 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgments</span>
488
489 The previous authors of versions of this document were Derrick Dunne
490 and Jason Collins. The current authors would like to thank Derrick
491 and Jason for their contributions.
492
493
494
495
496
497
498
499
500 <span class="grey">Parsons &amp; Maruszak Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc3939">RFC 3939</a> Calling Line Identification December 2004</span>
503
504
505 Authors' Addresses
506
507 Glenn Parsons
508 Nortel Networks
509 P.O. Box 3511, Station C
510 Ottawa, ON K1Y 4H7
511
512 Phone: +1-613-763-7582
513 EMail: [email protected]
514
515
516 Janusz Maruszak
517
518 Phone: +1-416-885-0221
519 EMail: [email protected]
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556 <span class="grey">Parsons &amp; Maruszak Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc3939">RFC 3939</a> Calling Line Identification December 2004</span>
559
560
561 Full Copyright Statement
562
563 Copyright (C) The Internet Society (2004).
564
565 This document is subject to the rights, licenses and restrictions
566 contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
567 retain all their rights.
568
569 This document and the information contained herein are provided on an
570 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
571 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
572 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
573 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
574 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
575 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
576
577 Intellectual Property
578
579 The IETF takes no position regarding the validity or scope of any
580 Intellectual Property Rights or other rights that might be claimed to
581 pertain to the implementation or use of the technology described in
582 this document or the extent to which any license under such rights
583 might or might not be available; nor does it represent that it has
584 made any independent effort to identify any such rights. Information
585 on the IETF's procedures with respect to rights in IETF Documents can
586 be found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
587
588 Copies of IPR disclosures made to the IETF Secretariat and any
589 assurances of licenses to be made available, or the result of an
590 attempt made to obtain a general license or permission for the use of
591 such proprietary rights by implementers or users of this
592 specification can be obtained from the IETF on-line IPR repository at
593 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
594
595 The IETF invites any interested party to bring to its attention any
596 copyrights, patents or patent applications, or other proprietary
597 rights that may cover technology that may be required to implement
598 this standard. Please address the information to the IETF at ietf-
599 [email protected].
600
601 Acknowledgement
602
603 Funding for the RFC Editor function is currently provided by the
604 Internet Society.
605
606
607
608
609
610
611
612 Parsons &amp; Maruszak Standards Track [Page 11]
613 </pre>