RFC 3319

Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers

📅 published July 2003, from ietf

RFC 3319 💖 DHCPv6 Options for SIP Servers ✨

Okay bestie, so this is RFC 3319 📞, from the Network Working Group, dated July 2003 🦋. It's on the Standards Track 🔥, written by Henning Schulzrinne of Columbia University and Bernie Volz of Ericsson 🫶. The header doesn't list anything it obsoletes or updates, so it's standing on its own 💅.

Status of This Memo 🌸

Okay, so this one is an Internet standards track protocol for the Internet community, and it's asking for discussion and suggestions for improvements 💬. If you want the current standardization state and status, check the current edition of the "Internet Official Protocol Standards" (STD 1) 📚. Distribution of this memo is unlimited 🌈.

Copyright (C) The Internet Society (2003). All Rights Reserved. 🔒

Abstract ✨

So basically, this doc defines a Dynamic Host Configuration Protocol version 6 (DHCPv6) option 🌐. The option holds a list of domain names or IPv6 addresses that can be mapped to one or more Session Initiation Protocol (SIP) outbound proxy servers 📡. It's just one of the many ways a SIP client can find the address of a local SIP server, and it's giving main character energy 👑.

1. Terminology 🧚

This doc uses the DHCP terminology defined in [1] 📖.

A SIP server is defined in RFC 3261 [2] 💅. This server MUST be an outbound proxy server, as defined in [3] 🔥. In this doc, a SIP server means the host that the outbound SIP proxy server is running on 🏠.

A SIP client is also defined in RFC 3261 [2] ✨. The client can be a user agent client or the client portion of a proxy server 🦋. In this doc, a SIP client means the host the SIP client is running on 💜.

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 BCP 14, RFC 2119 [4]. Those key words are the rules-of-the-game words, so they stay in caps exactly where they apply 🙈.

2. Introduction 🍓

Okay so SIP [2] is an application-layer control protocol 📞. It can set up, change, and end multimedia sessions or calls 🎶. A SIP system has a bunch of logical parts: user agents, proxy servers, redirect servers, and registrars 🧩. User agents MAY contain SIP clients, proxy servers always do 💅.

This doc specifies two DHCPv6 options [1] that let SIP clients find a local SIP server to use for all outbound SIP requests, which is called an outbound proxy server 🌸. (SIP clients MAY contact the address identified in the SIP URL directly, without involving a local SIP server. But in some situations, like when firewalls are present, or with local dialing plans, local emergency and other services need to be provided, so SIP clients need to use a local server for outbound requests 🚨.) This is one of many possible ways to locate the outbound SIP server, and manual configuration is another example 🫶.

3. SIP Server DHCPv6 Option 🎀

This doc defines two DHCPv6 options that describe a local outbound SIP proxy 🦋. One carries a list of domain names (Section 3.1), and the other carries a list of 128-bit (binary) IPv6 addresses (Section 3.2) 💖.

Since DHCPv6 doesn't have a shortage of option codes, the encoding byte found in the IPv4 DHCP option for SIP servers [6] gets skipped 🙌. That makes the option shorter and easier to parse, keeps the numeric addresses nicely word-aligned, and lets the client request either the numeric or the domain name option using the "option request option" ✨.

An implementation of this spec MUST support both options 🔥.

3.1. SIP Servers Domain Name List 📜

The option length is followed by a sequence of labels, encoded according to Section 3.1 of RFC 1035 [5]. Here's the quote from RFC 1035, copied word for word 🧾:

"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." RFC 1035 encoding was chosen to accommodate future internationalized domain name mechanisms.

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 Section 4.1 of RFC 3263 [3] to each one 🔁. The client only resolves the next domain name if the attempt to contact the first one failed, or yielded no common transport protocols between client and server, or denoted a domain administratively prohibited by client policy 🙅‍♀️. Domain names MUST be listed in order of preference 👑.

Using multiple domain names doesn't replace NAPTR or SRV records 💅. It just lets one DHCP server point to outbound proxy servers run by multiple providers 🌸.

The DHCPv6 option has the format shown in Fig. 1 🧚.

  • option-code: OPTION_SIP_SERVER_D (21)
  • option-length: the length of the SIP Server Domain Name List field in octets. It's variable 🍓.
    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      OPTION_SIP_SERVER_D      |         option-length         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                 SIP Server Domain Name List                   |
   |                              ...                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Figure 1: DHCPv6 option for SIP Server Domain Name List 🖼️

  • SIP Server Domain Name List: the domain names of the SIP outbound proxy servers for the client to use. The domain names are encoded as specified in Section 8 ("Representation and use of domain names") of the DHCPv6 specification [1] 💖.

3.2. SIP Servers IPv6 Address List 🦋

This option lists the IPv6 addresses of the SIP outbound proxy servers that are available to the client 🌐. Servers MUST be listed in order of preference ✨.

    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      OPTION_SIP_SERVER_A      |           option-len          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   |                   SIP server (IP address)                     |
   |                                                               |
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   |                   SIP server (IP address)                     |
   |                                                               |
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                              ...                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  • option-code: OPTION_SIP_SERVER_A (22) 🔢
  • option-length: the length of the options field in octets. It MUST be a multiple of 16 💅. (Yes, the spec really says MUST be a multiple of 16, so the 16-byte IPv6 addresses line up 🔥.)
Oops, I need to be honest here: the original spec uses "option-length" in this bullet but writes "must be a multiple of 16" in lowercase and then says "options" field. I've kept the wording exactly as the original has it, and the 16-byte rule is what matters 🙈.
  • SIP server: the IPv6 address of a SIP server for the client to use. The servers are listed in order of preference for use by the client 🌸.

Copyright (C) The Internet Society (2003). All Rights Reserved. 💖

okay so, the Internet Society basically says you're allowed to copy this doc and share it with anyone, no cap 🫶. You can even make derivative works that comment on it, explain it, or help people implement it, and you can publish and distribute those too, in whole or in part, with no restrictions of any kind. The one hard rule is that the copyright notice and this paragraph have to stay on every copy and every derivative work 📜.

Here's the catch: the document itself can't be changed in any way 🙅‍♀️. You can't remove the copyright notice or the references to the Internet Society or other Internet organizations. There are two exceptions, though. The first is if you're developing Internet standards, in which case you follow the copyright procedures in the Internet Standards process. The second is if you need to translate it into a language other than English 🌍. We love a multilingual icon 💅.

The permissions above are perpetual, which means they will never be revoked by the Internet Society or its successors or assigns 🦋. Forever and ever, bestie 🌈.

Disclaimer: This document and the information in it are 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 🫶. Big thank you to them for keeping the lights on for all these RFCs. We love a supportive sponsor 🌸.

📦 where this page comes from