James,

Please look at the example below and tell me how this is twice the size of an existing PIDF-LO?
This is in the draft, and IS just adding a URI element, it is just that we have the flexibility to have the URI point to an element in the same document.

<?xml version="1.0" encoding="UTF-8"?>
     <presence xmlns="urn:ietf:params:xml:ns:pidf"
       xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
       xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
       xmlns:dl="urn:ietf:params:xml:ns:geopriv:derived"
       xmlns:gml="http://www.opengis.net/gml"
       xmlns:gs="http://www.opengis.net/pidflo/1.0"
       entity="pres:ness@example.com">

       <tuple id="ness">
         <status>
           <gp:geopriv>
             <gp:location-info>
               <civicAddress xml:lang="en-AU"
         dl:derivedFrom="held://lis.example.com:9128/xyz#freddy">
                 <country>AU</country>
                 <A1>NSW</A1>
                 <A3>     Wollongong
                 </A3><A4>North Wollongong
                 </A4>
                 <RD>Flinders</RD><STS>Street</STS>
                 <RDBR>Campbell Street</RDBR>
                 <PC>2500</PC>
                 <POBOX>Private Box 15</POBOX>
               </civicAddress>
             </gp:location-info>
             <gp:usage-rules/>
             <method>Derived</method>
           </gp:geopriv>
         </status>
         <timestamp>2008-07-24T12:28:04Z</timestamp>
       </tuple>
     </presence>



Next, please explain to me how an unencrypted plain-text UDP packet containing my SIP identity and my location information complies with 3863?

YOU go on and on and on about this stuff, yet then YOU turn around with complete and utter this kind of garbage. It would be  nice, just once, to see you say something constructive rather than feeling you always have to compete.

Cheers
James



-----Original Message-----
From: James M. Polk [mailto:jmpolk@cisco.com]
Sent: Tue 7/29/2008 8:10 AM
To: Winterbottom, James; Hannes Tschofenig
Cc: geopriv@ietf.org; ecrit@ietf.org
Subject: Re: [Geopriv] [Ecrit] Announce: Specifying Derived Location in  a PIDF-LO
 
At 07:53 AM 7/29/2008, Winterbottom, James wrote:
>If I use a reference to an external location how is this doubling 
>the size of the PIDF-LO?

Are there 2 (as in TWO) <location-info> elements?

that doubles the size

I see 2 in the example IN YOUR ID...  you've made this point in a 
previous message and I still see TWO <location-info> elements, where 
there should be only one in as many cases as we we can limit

this isn't *just* a URI element added to what's already there in the LO

>I also though that location information was generally only going be 
>sent if TLS was used, which would rule out the use of UDP as a 
>viable transport wouldn't it? Certainly I would be uncomfortable 
>sending my location in an unencrypted UDP packet as I hardly think 
>that that meets the general requirements of a using protocol.

James, YOU keep making these points as if everyone has YOUR values 
and uses protocols only YOUR way.  Are you (as a single entity) 
representative of the entire human race?


>Cheers
>James
>
>
>
>
>
>-----Original Message-----
>From: James M. Polk [mailto:jmpolk@cisco.com]
>Sent: Tue 7/29/2008 7:21 AM
>To: Hannes Tschofenig; Winterbottom, James
>Cc: geopriv@ietf.org; ecrit@ietf.org
>Subject: Re: [Ecrit] [Geopriv] Announce: Specifying Derived Location 
>in  a PIDF-LO
>
>At 05:31 AM 7/29/2008, Hannes Tschofenig wrote:
> >Sounds like a useful way to indicate the derived location
>
>this does not to me, as it greatly (almost doubles as far as I can
>see) the number of bytes in the LO.
>
>We shouldn't willfully put blinders up to the contraints of a viable,
>in fact built for, transport protocol (i.e., SIP and the
>considerations it has taken great lengths to go to towards MTU
>limitations of UDP over Ethernet).
>
>
>
>
> >Winterbottom, James wrote:
> >>
> >>http://tools.ietf.org/html/draft-winterbottom-geopriv-derived-loc-00
> >>
> >>
> >>
> >>Specifying Derived Location in a PIDF-LO
> >>
> >>
> >>
> >>Abstract
> >>
> >>    This document describes how specify that a location in a PIDF-LO has
> >>    been derived or converted from a different location.  The source
> >>    location may reside in the same PIDF-LO or be a remote document
> >>    referenced by a location URI and associated id fragement.
> >>
> >>
> >>
> >>
> >>
> >>Feedback appreciated.
> >>
> >>
> >>
> >>Cheers
> >>
> >>James
> >>
> >>
> >>
> >>
> >>
> >>
> >>------------------------------------------------------------------ 
> ------------------------------
> >>This message is for the designated recipient only and may
> >>contain privileged, proprietary, or otherwise private information.
> >>If you have received it in error, please notify the sender
> >>immediately and delete the original.  Any unauthorized use of
> >>this email is prohibited.
> >>------------------------------------------------------------------ 
> ------------------------------
> >>[mf2]
> >>
> >>------------------------------------------------------------------------
> >>
> >>_______________________________________________
> >>Geopriv mailing list
> >>Geopriv@ietf.org
> >>https://www.ietf.org/mailman/listinfo/geopriv
> >>
> >
> >_______________________________________________
> >Ecrit mailing list
> >Ecrit@ietf.org
> >https://www.ietf.org/mailman/listinfo/ecrit
>
>
>
>------------------------------------------------------------------------------------------------
>This message is for the designated recipient only and may
>contain privileged, proprietary, or otherwise private information.
>If you have received it in error, please notify the sender
>immediately and delete the original.  Any unauthorized use of
>this email is prohibited.
>------------------------------------------------------------------------------------------------
>[mf2]
>
>_______________________________________________
>Geopriv mailing list
>Geopriv@ietf.org
>https://www.ietf.org/mailman/listinfo/geopriv



------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv