1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
|
<pre>Network Working Group H. Schulzrinne
Request for Comments: 3361 Columbia University
Category: Standards Track August 2002
<span class="h1">Dynamic Host Configuration Protocol (DHCP-for-IPv4)</span>
<span class="h1">Option for Session Initiation Protocol (SIP) Servers</span>
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract
This document defines a Dynamic Host Configuration Protocol
(DHCP-for-IPv4) option that contains a list of domain names or IPv4
addresses that can be mapped to one or more Session Initiation
Protocol (SIP) outbound proxy servers. This is one of the many
methods that a SIP client can use to obtain the addresses of such a
local SIP server.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Terminology</span>
DHCP client: A DHCP [<a href="#ref-1" title=""Dynamic Host Configuration Protocol"">1</a>] client is an Internet host that uses
DHCP to obtain configuration parameters such as a network
address.
DHCP server: A DHCP server is an Internet host that returns
configuration parameters to DHCP clients.
SIP server: As defined in <a href="./rfc3261">RFC 3261</a> [<a href="#ref-2" title=""SIP: Session Initiation Protocol"">2</a>]. This server MUST be an
outbound proxy server, as defined in [<a href="#ref-3" title=""Session Initiation Protocol (SIP): Locating SIP Servers"">3</a>]. In the context of
this document, a SIP server refers to the host the SIP
server is running on.
SIP client: As defined in <a href="./rfc3261">RFC 3261</a>. The client can be a user
agent client or the client portion of a proxy server. In
the context of this document, a SIP client refers to the
host the SIP client is running on.
<span class="grey">Schulzrinne Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3361">RFC 3361</a> DHCPv4 Option for SIP Servers August 2002</span>
In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="#ref-4" title=""Key words for use in RFCs to indicate requirement levels"">4</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Introduction</span>
The Session Initiation Protocol (SIP) [<a href="#ref-2" title=""SIP: Session Initiation Protocol"">2</a>] is an application-layer
control protocol that can establish, modify and terminate multimedia
sessions or calls. A SIP system has a number of logical components:
user agents, proxy servers, redirect servers and registrars. User
agents MAY contain SIP clients, proxy servers always do.
This document specifies a DHCP option [<a href="#ref-1" title=""Dynamic Host Configuration Protocol"">1</a>,<a href="#ref-5" title=""DHCP options and BOOTP Vendor Extensions"">5</a>] that allows SIP clients
to locate a local SIP server that is to be used for all outbound SIP
requests, a so-called outbound proxy server. (SIP clients MAY
contact the address identified in the SIP URL directly, without
involving a local SIP server. However in some circumstances, for
example, when firewalls are present, SIP clients need to use a local
server for outbound requests.) This is one of many possible
solutions for locating the outbound SIP server; manual configuration
is an example of another.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. SIP Server DHCP Option</span>
The SIP server DHCP option carries either a 32-bit (binary) IPv4
address or, preferably, a DNS (<a href="./rfc1035">RFC 1035</a> [<a href="#ref-6" title=""Domain names - implementation and specification"">6</a>]) fully-qualified domain
name to be used by the SIP client to locate a SIP server.
The option has two encodings, specified by the encoding byte ('enc')
that follows the code byte. If the encoding byte has the value 0, it
is followed by a list of domain names, as described below (<a href="#section-3.1">Section</a>
<a href="#section-3.1">3.1</a>). If the encoding byte has the value 1, it is followed by one or
more IPv4 addresses (<a href="#section-3.2">Section 3.2</a>). All implementations MUST support
both encodings. The 'Len' field indicates the total number of octets
in the option following the 'Len' field, including the encoding byte.
A DHCP server MUST NOT mix the two encodings in the same DHCP
message, even if it sends two different instances of the same option.
Attempts to do so would result in incorrect client behavior as DHCP
processing rules call for the concatenation of multiple instances of
an option into a single option prior to processing the option [<a href="#ref-7" title=""Encoding Long DHCP Options"">7</a>].
The code for this option is 120.
<span class="grey">Schulzrinne Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3361">RFC 3361</a> DHCPv4 Option for SIP Servers August 2002</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Domain Name List</span>
If the 'enc' byte has a value of 0, the encoding byte is followed by
a sequence of labels, encoded according to <a href="./rfc1035#section-3.1">Section 3.1 of RFC 1035</a>
[<a href="#ref-6" title=""Domain names - implementation and specification"">6</a>], quoted below:
Domain names in messages are expressed in terms of a sequence
of labels. Each label is represented as a one octet length
field followed by that number of octets. Since every domain
name ends with the null label of the root, a domain name is
terminated by a length byte of zero. The high order two bits
of every length octet must be zero, and the remaining six bits
of the length field limit the label to 63 octets or less. To
simplify implementations, the total length of a domain name
(i.e., label octets and label length octets) is restricted to
255 octets or less.
<a href="./rfc1035">RFC 1035</a> encoding was chosen to accommodate future internationalized
domain name mechanisms.
The minimum length for this encoding is 3.
The option MAY contain multiple domain names, but these SHOULD refer
to different NAPTR records, rather than different A records. The
client MUST try the records in the order listed, applying the
mechanism described in <a href="./rfc3263#section-4.1">Section 4.1 of RFC 3263</a> [<a href="#ref-3" title=""Session Initiation Protocol (SIP): Locating SIP Servers"">3</a>] for each. The
client only resolves the subsequent domain names if attempts to
contact the first one failed or yielded no common transport protocols
between client and server or denote a domain administratively
prohibited by client policy.
Use of multiple domain names is not meant to replace NAPTR and
SRV records, but rather to allow a single DHCP server to
indicate outbound proxy servers operated by multiple providers.
Clients MUST support compression according to the encoding in <a href="#section-4.1.4">Section</a>
<a href="#section-4.1.4">4.1.4</a> of "Domain Names - Implementation And Specification" [<a href="#ref-6" title=""Domain names - implementation and specification"">6</a>].
Since the domain names are supposed to be different domains,
compression will likely have little effect, however.
If the length of the domain list exceeds the maximum permissible
within a single option (254 octets), then the domain list MUST be
represented in the DHCP message as specified in [<a href="#ref-7" title=""Encoding Long DHCP Options"">7</a>].
<span class="grey">Schulzrinne Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3361">RFC 3361</a> DHCPv4 Option for SIP Servers August 2002</span>
The DHCP option for this encoding has the following format:
Code Len enc DNS name of SIP server
+-----+-----+-----+-----+-----+-----+-----+-----+--
| 120 | n | 0 | s1 | s2 | s3 | s4 | s5 | ...
+-----+-----+-----+-----+-----+-----+-----+-----+--
As an example, consider the case where the server wants to offer two
outbound proxy servers, "example.com" and "example.net". These would
be encoded as follows:
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
|120|27 | 0 | 7 |'e'|'x'|'a'|'m'|'p'|'l'|'e'| 3 |'c'|'o'|'m'| 0 |
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
+---+---+---+---+---+---+---+---+---+---+---+---+---+ | 7
|'e'|'x'|'a'|'m'|'p'|'l'|'e'| 3 |'n'|'e'|'t'| 0 | +---+---+---
+---+---+---+---+---+---+---+---+---+---+
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> IPv4 Address List</span>
If the 'enc' byte has a value of 1, the encoding byte is followed by
a list of IPv4 addresses indicating SIP outbound proxy servers
available to the client. Servers MUST be listed in order of
preference.
Its minimum length is 5, and the length MUST be a multiple of 4 plus
one. The DHCP option for this encoding has the following format:
Code Len enc Address 1 Address 2
+-----+-----+-----+-----+-----+-----+-----+-----+--
| 120 | n | 1 | a1 | a2 | a3 | a4 | a1 | ...
+-----+-----+-----+-----+-----+-----+-----+-----+--
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
The security considerations in <a href="./rfc2131">RFC 2131</a> [<a href="#ref-1" title=""Dynamic Host Configuration Protocol"">1</a>], <a href="./rfc2543">RFC 2543</a> [<a href="#ref-2" title=""SIP: Session Initiation Protocol"">2</a>] and <a href="./rfc3263">RFC</a>
<a href="./rfc3263">3263</a> [<a href="#ref-3" title=""Session Initiation Protocol (SIP): Locating SIP Servers"">3</a>] apply. If an adversary manages to modify the response from
a DHCP server or insert its own response, a SIP user agent could be
led to contact a rogue SIP server, possibly one that then intercepts
call requests or denies service. A modified DHCP answer could also
omit host names that translated to TLS-based SIP servers, thus
facilitating intercept.
<span class="grey">Schulzrinne Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc3361">RFC 3361</a> DHCPv4 Option for SIP Servers August 2002</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
IANA has assigned a DHCP option number of 120 for the "SIP Servers
DHCP Option" defined in this document.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
Ralph Droms, Robert Elz, Wenyu Jiang, Peter Koch, Gautam Nair, Thomas
Narten, Erik Nordmark, Jonathan Rosenberg, Kundan Singh, Sven Ubik,
Bernie Volz and Dean Willis provided useful feedback through the
evolution of this document.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Bibliography</span>
[<a id="ref-1">1</a>] Droms, R., "Dynamic Host Configuration Protocol", <a href="./rfc2131">RFC 2131</a>, March
1997.
[<a id="ref-2">2</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP:
Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>, June 2002.
[<a id="ref-3">3</a>] Rosenberg, J. and H. Schulzrinne, "Session Initiation Protocol
(SIP): Locating SIP Servers", <a href="./rfc3263">RFC 3263</a>, June 2002.
[<a id="ref-4">4</a>] Bradner, S., "Key words for use in RFCs to indicate requirement
levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-5">5</a>] Alexander, S. and R. Droms, "DHCP options and BOOTP Vendor
Extensions", <a href="./rfc2132">RFC 2132</a>, March 1997.
[<a id="ref-6">6</a>] Mockapetris, P., "Domain names - implementation and
specification", STD 13, <a href="./rfc1035">RFC 1035</a>, November 1987.
[<a id="ref-7">7</a>] Lemon, T. and S. Cheshire, <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22Encoding+Long+DHCP+Options%22'>"Encoding Long DHCP Options"</a>, Work in
Progress.
<span class="grey">Schulzrinne Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc3361">RFC 3361</a> DHCPv4 Option for SIP Servers August 2002</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Author's Address</span>
Henning Schulzrinne
Dept. of Computer Science
Columbia University
1214 Amsterdam Avenue, MC 0401
New York, NY 10027
USA
EMail: schulzrinne@cs.columbia.edu
<span class="grey">Schulzrinne Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc3361">RFC 3361</a> DHCPv4 Option for SIP Servers August 2002</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Full Copyright Statement</span>
Copyright (C) The Internet Society (2002). 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 procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions 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
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Schulzrinne Standards Track [Page 7]
</pre>
|
