RFC3261: SIP:8.1.1.2 To

8.1.1.2 To
8.1.1.2 To

   The To header field first and foremost specifies the desired "logical" recipient of the request, or the address-of-record of the user or resource that is the target of this request.  This may or may not be the ultimate recipient of the request.  The To header field MAY contain a SIP or SIPS URI, but it may also make use of other URI schemes (the tel URL (RFC 2806 [9]), for example) when appropriate. All SIP implementations MUST support the SIP URI scheme.  Any implementation that supports TLS MUST support the SIPS URI scheme. The To header field allows for a display name.

​To报头字段首先指定请求的所需“逻辑”收件人，或作为此请求目标的用户或资源的记录地址。这可能是也可能不是请求的最终接收者。To报头字段可以包含SIP或SIPS URI，但它也可以在适当的时候使用其他URI方案（例如，tel URL（RFC 2806[9]））。所有SIP实现都必须支持SIP URI方案。任何支持TLS的实现都必须支持SIPS URI方案。“To”报头字段允许显示名称。

   A UAC may learn how to populate the To header field for a particular request in a number of ways.  Usually the user will suggest the To header field through a human interface, perhaps inputting the URI manually or selecting it from some sort of address book.  Frequently, the user will not enter a complete URI, but rather a string of digits or letters (for example, "bob").  It is at the discretion of the UA to choose how to interpret this input.  Using the string to form the user part of a SIP URI implies that the UA wishes the name to be resolved in the domain to the right-hand side (RHS) of the at-sign in the SIP URI (for instance, sip:bob@example.com).  Using the string to form the user part of a SIPS URI implies that the UA wishes to communicate securely, and that the name is to be resolved in the domain to the RHS of the at-sign.  The RHS will frequently be the home domain of the requestor, which allows for the home domain to process the outgoing request.  This is useful for features like "speed dial" that require interpretation of the user part in the home domain.  The tel URL may be used when the UA does not wish to specify the domain that should interpret a telephone number that has been input by the user.  Rather, each domain through which the request passes would be given that opportunity.  As an example, a user in an airport might log in and send requests through an outbound proxy in the airport.  If they enter "411" (this is the phone number for local directory assistance in the United States), that needs to be interpreted and processed by the outbound proxy in the airport, not the user's home domain.  In this case, tel:411 would be the right choice.

UAC可以学习如何以多种方式填充特定请求的to报头字段。通常，用户会通过人机界面建议To头字段，可能手动输入URI或从某种地址簿中选择URI。通常，用户不会输入完整的URI，而是输入一串数字或字母（例如“bob”）。UA可自行决定如何解释该输入。使用该字符串形成SIP URI的用户部分意味着UA希望在域中将名称解析到SIP URI中at符号的右侧（RHS）（例如，SIP:bob@example.com).使用该字符串形成SIPS URI的用户部分意味着UA希望安全通信，并且该名称将在域中解析为at符号的RHS。RHS通常是请求者的主域，这允许主域处理传出的请求。这对于像“快速拨号”这样需要在主域中解释用户部分的功能非常有用。当UA不希望指定应当解释由用户输入的电话号码的域时，可以使用电话URL。相反，请求通过的每个域都将获得该机会。例如，机场中的用户可能会通过机场中的出站代理登录并发送请求。如果他们输入“411”（这是美国本地目录协助的电话号码），则需要由机场的出站代理进行解释和处理，而不是用户的主域。在这种情况下，电话：411将是正确的选择。

   A request outside of a dialog MUST NOT contain a To tag; the tag in the To field of a request identifies the peer of the dialog.  Since no dialog is established, no tag is present.

对话之外的请求不得包含To标记；请求的“To”字段中的标记标识对话的对等方。由于没有建立对话，因此不存在标记。

   For further information on the To header field, see Section 20.39. The following is an example of a valid To header field:

​有关To标头字段的更多信息，请参阅第20.39节。以下是有效的“收件人”标头字段的示例：​

      To: Carol <sip:carol@chicago.com>