Skip to main content

IPv6-only and Dual Stack Hosts on the Same Network with DNS64
draft-wing-behave-dns64-config-03

Revision differences

Document history

Date Rev. By Action
2011-08-18
03 (System) Document has expired
2011-02-14
03 (System) New version available: draft-wing-behave-dns64-config-03.txt
2010-02-12
02 (System) New version available: draft-wing-behave-dns64-config-02.txt
2010-01-26
01 (System)
New version available: </tel>
            <tel>
              <parameters>
                  <type>
                    <text>home</text>
                    <text>voice</text>
                  </type>
              </parameters>
              <uri>tel:+1-555-555-0123</uri>
            </tel>
            <tel>

Gellens, et al.              Standards Track                  [Page 44]
RFC 7852                  Additional Call Data                July 2016

              <parameters>
                  <type>
                    <text>work</text>
                    <text>voice</text>
                    <text>main-number</text>
                  </type>
              </parameters>
              <uri>tel:+1-302-594-3100</uri>
            </tel>
            <email>
              <parameters><type><text>work</text></type>
              </parameters>
              <text>hannes.tschofenig@nsn.com</text>
            </email>
            <geo>
              <parameters><type><text>work</text></type>
              </parameters>
              <uri>geo:60.210796,24.812924</uri>
            </geo>
            <geo>
              <parameters><type><text>home</text></type>
              </parameters>
              <uri>geo:39.746537,-75.548027</uri>
            </geo>
            <key>
              <parameters>
                  <type><text>home</text></type>
              </parameters>
              <uri>https://www.example.com/key.asc</uri>
            </key>
            <tz><text>Finland/Helsinki</text></tz>
            <url>
              <parameters><type><text>home</text></type>
              </parameters>
              <uri>http://example.com/hannes.tschofenig
              </uri>
            </url>
        </vcard>
      </pi:DataProviderContact>
      </pi:EmergencyCallData.ProviderInfo>
      --boundary1--

      Figure 16: End Device Sending SIP INVITE with Additional Data

  In this example, information available to the access network provider
  is included in the call setup message only indirectly via the use of
  the location reference.  The PSAP has to retrieve it via a separate
  lookup step.  Since the access network provider and the VoIP service

Gellens, et al.              Standards Track                  [Page 45]
RFC 7852                  Additional Call Data                July 2016

  provider are two independent entities in this scenario, the access
  network provider is not involved in application-layer exchanges; the
  SIP INVITE transits the access network transparently, as illustrated
  in steps #1 and #2 (the access network does not alter the SIP
  INVITE).

  The VoIP service provider receives the message and determines, based
  on the service URN, that the incoming request is an emergency call.
  It performs typical emergency-services-related tasks (such as
  location-based routing) and adds additional data, namely service and
  subscriber information as well as data provider information #2, to
  the outgoing message.  For the example, we assume a VoIP service
  provider deploys a back-to-back user agent allowing additional data
  to be included in the body of the SIP message (rather than by
  reference), which allows us to illustrate the use of multiple data
  provider info blocks.  The resulting message is shown in Figure 17.
  The SIP INVITE is sent to the PSAP in step #3.

      INVITE sips:psap@example.org SIP/2.0
      Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9
      Max-Forwards: 70
      To: <urn:service:sos>
      From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl
      Call-ID: 3848276298220188511@example.com
      Call-Info: <http://wwww.example.com/hannes/photo.jpg>;
        purpose=icon,
        <http://www.example.com/hannes/>; purpose=info,
        <cid:1234567890@atlanta.example.com>;
        purpose=EmergencyCallData.ProviderInfo
        <cid:0123456789@atlanta.example.com>;
        purpose=EmergencyCallData.DeviceInfo
      Call-Info: <cid:bloorpyhex@atlanta.example.com>;
        purpose=EmergencyCallData.ServiceInfo
      Call-Info: <cid:aaabbb@atlanta.example.com>;
        purpose=EmergencyCallData.ProviderInfo
      Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o>
      Geolocation-Routing: yes
      Accept: application/sdp, application/pidf+xml,
        application/EmergencyCallData.ProviderInfo+xml
      CSeq: 31862 INVITE
      Contact: <sips:hannes@example.com>
      Content-Type: multipart/mixed; boundary=boundary1
      Content-Length: ...

      --boundary1
      Content-Type: application/sdp

      ...SDP goes here

Gellens, et al.              Standards Track                  [Page 46]
RFC 7852                  Additional Call Data                July 2016

      --boundary1
      Content-Type: application/EmergencyCallData.DeviceInfo+xml
      Content-ID: &draft-wing-behave-dns64-config-01.txt
2010-01-07
00 (System) New version available: draft-wing-behave-dns64-config-00.txt