9. IANA Considerations

   The usage of NAPTR records described here requires well known values
   for the service fields for each transport supported by SIP.  The
   table of mappings from service field values to transport protocols is
   to be maintained by IANA.  New entries in the table MAY be added
   through the publication of standards track RFCs, as described in RFC
   2434 [5].

   The registration in the RFC MUST include the following information:

      Service Field: The service field being registered.  An example for
         a new fictitious transport protocol called NCTP might be
         "SIP+D2N".

      Protocol: The specific transport protocol associated with that
         service field.  This MUST include the name and acronym for the
         protocol, along with reference to a document that describes the
         transport protocol.  For example - "New Connectionless
         Transport Protocol (NCTP), RFC ".

      Name and Contact Information: The name, address, email address and
         telephone number for the person performing the registration.

   The following values have been placed into the registry:

   Services Field               Protocol
   SIP+D2T                       TCP
   SIPS+D2T                      TCP
   SIP+D2U                       UDP
   SIP+D2S                       SCTP (RFC 2960prop)