[Geopriv] Message Flow, again

From: Hannes Tschofenig ^lt;Hannes.Tschofenig@gmx.net>
Date: Thu Nov 22 2007 - 04:58:23 EST

In my previous mail I made a mistake and forgot to include the identity
extension. Without the identity extension the described message flow
wouldn't work.

Here is the updated message flow.

Consider a SIP INVITE message that arrives at the proxy. It does not
contain location information

  INVITE sips:bob@biloxi.example.com SIP/2.0
  Via: SIP/2.0/TLS pc33.atlanta.example.com
    ;branch=z9hG4bK74bf9
  Max-Forwards: 70
  To: Bob <sips:bob@biloxi.example.com>
  From: Alice <sips:alice@atlanta.example.com>;tag=9fxced76sl
  Call-ID: 3848276298220188511@atlanta.example.com
  Accept: application/sdp
  CSeq: 31862 INVITE
  Contact: <sips:alice@pc33.atlanta.example.com>

  ...SDP goes here as the only message body

Now, assume that a the proxy does location based routing and also wants
to allow the location recipient to obtain the location information. The
request contains the HELD identity extension containing the IP address
of UA sending the SIP INVITE message.

It constructs a HELD request:

<?xml version="1.0"?>
<locationRequest xmlns="urn:ietf:params:xml:ns:geopriv:held">
   <locationType exact="true">
    any
    locationURI
   </locationType>
   <heldDevice xmlns="urn:ietf:params:xml:ns:geopriv:held:id">
     <uri>ip:IPv4+192.0.2.5</uri>
   </heldDevice>
</locationRequest>

The LIS returns a response with a civic address and the LbyR.

<?xml version="1.0"?>
<locationResponse xmlns="urn:ietf:params:xml:ns:geopriv:held">

         <locationUriSet expires="2006-01-01T13:00:00">
         <locationURI>https://ls.example.com:9768/357yc6s64ceyoiuy5ax3o
         </locationURI>
         <locationURI>sips:9769+357yc6s64ceyoiuy5ax3o@ls.example.com
         </locationURI>
        </locationUriSet>
        <presence xmlns="urn:ietf:params:xml:ns:pidf:geopriv10"
               entity="pres:ae3be8585902e2253ce2@10.102.23.9">
        <tuple id="lisLocation">
         <status>
         <geopriv>
            <ca:civicAddress
             xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
             xml:lang="en-au">
             <ca:country>AU</ca:country>
             <ca:A1>NSW</ca:A1>
             <ca:A3>Wollongong</ca:A3>
             <ca:A4>Gwynneville</ca:A4>
             <ca:STS>Northfield Avenue</ca:STS>
             <ca:LMK>University of Wollongong</ca:LMK>
             <ca:FLR>2</ca:FLR>
             <ca:NAM>Andrew Corporation</ca:NAM>
             <ca:PC>2500</ca:PC>
             <ca:BLD>39</ca:BLD>
             <ca:SEAT>WS-183</ca:SEAT>
             <ca:POBOX>U40</ca:POBOX>
            </ca:civicAddress>
          </location-info>
          <usage-rules>
            <retransmission-allowed>false</retransmission-allowed>
            <retention-expiry>2007-05-25T12:35:02+10:00
            </retention-expiry>
          </usage-rules>
          <method>Wiremap</method>
          </geopriv>
         </status>
         <timestamp>2007-05-24T12:35:02+10:00</timestamp>
       </tuple>
       </presence>
      </locationResponse>

Based on the location by value the SIP proxy routes the call. It also
attaches a LbyR to the outgoing SIP message.

  INVITE sips:bob@biloxi.example.com SIP/2.0
  Via: SIP/2.0/TLS pc33.atlanta.example.com
    ;branch=z9hG4bK74bf9
  Max-Forwards: 70
  To: Bob <sips:bob@biloxi.example.com>
  From: Alice <sips:alice@atlanta.example.com>;tag=9fxced76sl
  Call-ID: 3848276298220188511@atlanta.example.com
  Geolocation: <sips:9769+357yc6s64ceyoiuy5ax3o@ls.example.com>
    ;inserted-by=proxy.atlanta.example.com ;recipient=endpoint
Accept: application/sdp
  CSeq: 31862 INVITE
  Contact: <sips:alice@pc33.atlanta.example.com>

  ...SDP goes here as the only message body

When the location recipient receives the message it runs a dereferencing
step.

Does my example make sense?

Ciao
Hannes

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www1.ietf.org/mailman/listinfo/geopriv
Received on Thu, 22 Nov 2007 10:58:23 +0100

This archive was generated by hypermail 2.1.8 : Thu Nov 22 2007 - 04:58:38 EST