idnits 2.17.1
draft-ietf-mediactrl-6231-iana-00.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
No issues found here.
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
No issues found here.
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
-- The draft header indicates that this document updates RFC6231, but the
abstract doesn't seem to directly say this. It does mention RFC6231
though, so this could be OK.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the IETF Trust and authors Copyright Line does not
match the current year
(Using the creation date from RFC6231, updated by this document, for
RFC5378 checks: 2008-06-10)
-- 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.)
-- The document date (February 12, 2012) is 4457 days in the past. Is this
intentional?
Checking references for intended status: Proposed Standard
----------------------------------------------------------------------------
(See RFCs 3967 and 4897 for information about using normative references
to lower-maturity documents in RFCs)
** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126)
Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 3 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 MEDIACTRL Working Group E. Burger
3 Internet-Draft Georgetown University
4 Updates: 6231 (if approved) February 12, 2012
5 Intended status: Standards Track
6 Expires: August 15, 2012
8 IANA Registry for MEDIACTRL Interactive Voice Response Control Package
9 draft-ietf-mediactrl-6231-iana-00.txt
11 Abstract
13 This document creates an IANA registry for the response codes for the
14 MEDIACTRL Interactive Voice Response Control Package, RFC6231.
16 Status of this Memo
18 This Internet-Draft is submitted in full conformance with the
19 provisions of BCP 78 and BCP 79.
21 Internet-Drafts are working documents of the Internet Engineering
22 Task Force (IETF). Note that other groups may also distribute
23 working documents as Internet-Drafts. The list of current Internet-
24 Drafts is at http://datatracker.ietf.org/drafts/current/.
26 Internet-Drafts are draft documents valid for a maximum of six months
27 and may be updated, replaced, or obsoleted by other documents at any
28 time. It is inappropriate to use Internet-Drafts as reference
29 material or to cite them other than as "work in progress."
31 This Internet-Draft will expire on August 15, 2012.
33 Copyright Notice
35 Copyright (c) 2012 IETF Trust and the persons identified as the
36 document authors. All rights reserved.
38 This document is subject to BCP 78 and the IETF Trust's Legal
39 Provisions Relating to IETF Documents
40 (http://trustee.ietf.org/license-info) in effect on the date of
41 publication of this document. Please review these documents
42 carefully, as they describe your rights and restrictions with respect
43 to this document. Code Components extracted from this document must
44 include Simplified BSD License text as described in Section 4.e of
45 the Trust Legal Provisions and are provided without warranty as
46 described in the Simplified BSD License.
48 Table of Contents
50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
51 2. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
52 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
53 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
54 5. Normative References . . . . . . . . . . . . . . . . . . . . . 7
55 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7
57 1. Introduction
59 This document creates an IANA registry for the response codes for the
60 MEDIACTRL Interactive Voice Response Control Package [RFC6231].
62 2. Security Considerations
64 None, other than those described in the MEDIACTRL Interactive Voice
65 Response Control Package. [RFC6231]
67 3. IANA Considerations
69 Please create the following registry. New status codes are assigned
70 using the Standards Action process defined in RFC5226 [RFC5226].
72 +-------+---------------+-----------------------+-------------------+
73 | Code | Summary | Description | Reference |
74 +-------+---------------+-----------------------+-------------------+
75 | 200 | OK | request has succeeded | RFC6231 |
76 | 400 | Syntax error | request is | RFC6231 |
77 | | | syntactically | |
78 | | | invalid: it is not | |
79 | | | valid with respect to | |
80 | | | the XML schema or it | |
81 | | | violates a | |
82 | | | co-occurrence | |
83 | | | constraint for a | |
84 | | | request element. | |
85 | 405 | dialogid | request uses a | RFC6231 |
86 | | already | dialogid identifier | |
87 | | exists | for a new dialog | |
88 | | | which is already used | |
89 | | | by another dialog on | |
90 | | | the MS. | |
91 | 406 | dialogid does | request uses a | RFC6231 |
92 | | not exist | dialogid identifier | |
93 | | | for an dialog which | |
94 | | | does not exist on the | |
95 | | | MS. | |
96 | 407 | connectionid | request uses a | RFC6231 |
97 | | does not | connectionid | |
98 | | exist | identifier for a | |
99 | | | connection which does | |
100 | | | not exist on the MS. | |
101 | 408 | conferenceid | request uses a | RFC6231 |
102 | | does not | conferenceid | |
103 | | exist | identifier for a | |
104 | | | conference which does | |
105 | | | not exist on the MS. | |
106 | 409 | Resource | request use a URI to | RFC6231 |
107 | | cannot be | reference an external | |
108 | | retrieved | resource (e.g. | |
109 | | | dialog, media or | |
110 | | | grammar) which cannot | |
111 | | | be retrieved within | |
112 | | | the timeout interval | |
113 | 410 | Dialog | request to prepare or | RFC6231 |
114 | | execution | start a dialog which | |
115 | | canceled | has been terminated | |
116 | | | by a | |
117 | | | | |
118 | 411 | Incompatible | request specifies a | RFC6231 |
119 | | stream | media stream | |
120 | | configuration | configuration which | |
121 | | | is in conflict with | |
122 | | | itself, or the | |
123 | | | connection or | |
124 | | | conference | |
125 | | | capabilities | |
126 | 412 | Media stream | request specifies an | RFC6231 |
127 | | not available | operation for which a | |
128 | | | media stream is not | |
129 | | | available. For | |
130 | | | example, playing a | |
131 | | | video media resource | |
132 | | | on an connection or | |
133 | | | conference without | |
134 | | | video streams. | |
135 | 413 | Control keys | the request contains | RFC6231 |
136 | | with same | a element | |
137 | | value | where some keys have | |
138 | | | the same value | |
139 | 419 | Other | requested operation | RFC6231 |
140 | | execution | cannot be executed by | |
141 | | error | the MS. | |
142 | 420 | Unsupported | request specifies a | RFC6231 |
143 | | URI scheme | URI whose scheme is | |
144 | | | not supported by the | |
145 | | | MS | |
146 | 421 | Unsupported | request references an | RFC6231. |
147 | | dialog | external dialog | |
148 | | language | language not | |
149 | | | supported by the MS | |
150 | 422 | Unsupported | request references a | RFC6231 |
151 | | playback | media resource for | |
152 | | format | playback whose format | |
153 | | | is not supported by | |
154 | | | the MS | |
155 | 423 | Unsupported | request references a | RFC6231 |
156 | | record format | media resource for | |
157 | | | recording whose | |
158 | | | format is not | |
159 | | | supported by the MS | |
160 | 424 | Unsupported | request references a | RFC6231 |
161 | | grammar | grammar whose format | |
162 | | format | is not supported by | |
163 | | | the MS | |
164 | 425 | Unsupported | request contains a | RFC6231 |
165 | | variable | prompt | |
166 | | configuration | element not supported | |
167 | | | by the MS | |
168 | 426 | Unsupported | request contains a | RFC6231 |
169 | | DTMF | prompt element | |
170 | | configuration | not supported by the | |
171 | | | MS | |
172 | 427 | Unsupported | request contains a | RFC6231 |
173 | | parameter | element not | |
174 | | | supported by the MS | |
175 | 428 | Unsupported | request contains a | RFC6231 |
176 | | media stream | element | |
177 | | configuration | whose configuration | |
178 | | | is not supported by | |
179 | | | the MS. | |
180 | 429 | Unsupported | request contains a | RFC6231 |
181 | | playback | element | |
182 | | configuration | which the MS is | |
183 | | | unable to play on the | |
184 | | | available output | |
185 | | | media streams | |
186 | 430 | Unsupported | request contains a | RFC6231 |
187 | | record | element | |
188 | | configuration | which the MS is | |
189 | | | unable to record with | |
190 | | | on the available | |
191 | | | input media streams | |
192 | 431 | Unsupported | the request contains | RFC6231 |
193 | | foreign | attributes or | |
194 | | namespace | elements from another | |
195 | | attribute or | namespace which the | |
196 | | element | MS does not support | |
197 | 432 | Unsupported | the request tries to | RFC6231 |
198 | | multiple | start another dialog | |
199 | | dialog | on the same | |
200 | | capability | conference or | |
201 | | | connection where a | |
202 | | | dialog is already | |
203 | | | running | |
204 | 433 | Unsupported | the request contains | RFC6231 |
205 | | collect and | and | |
206 | | record | elements and | |
207 | | capability | the MS does support | |
208 | | | these operations | |
209 | | | simultaneously | |
210 | 434 | Unsupported | the request contains | RFC6231 |
211 | | VAD | a element | |
212 | | capability | where Voice Activity | |
213 | | | Detection (VAD) is | |
214 | | | required, but the MS | |
215 | | | does not support VAD. | |
216 | 435 | Unsupported | the request contains | RFC6231 |
217 | | parallel | a prompt | |
218 | | playback | element whose | |
219 | | | configuration is not | |
220 | | | supported by the MS. | |
221 | 439 | Other | request requires | RFC6231 |
222 | | unsupported | another capability | |
223 | | capability | not supported by the | |
224 | | | MS | |
225 +-------+---------------+-----------------------+-------------------+
227 Table 1: status codes
229 4. Acknowledgements
231 I lifted the table in Section 3 directly from the excellent text
232 written by Scott McGlashan, Tim Melanchuk, and Chris Boulton in
233 RFC6231. Any transcription errors are mine.
235 5. Normative References
237 [RFC6231] McGlashan, S., Melanchuk, T., and C. Boulton, "An
238 Interactive Voice Response (IVR) Control Package for the
239 Media Control Channel Framework", RFC 6231, May 2011.
241 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
242 IANA Considerations Section in RFCs", BCP 26, RFC 5226,
243 May 2008.
245 Author's Address
247 Eric Burger
248 Georgetown University
249 37th and O St., NW
250 Washington, DC 20007
251 USA
253 Email: eburger@standardstrack.com