RE: [Geopriv] draft-tschofenig-geopriv-l7-lcp-ps-02.txt

From: Winterbottom, James ^lt;James.Winterbottom@andrew.com>
Date: Thu Aug 31 2006 - 20:26:37 EDT

Ummm, I am sorry, but how many PIDF-LOs are only 60 bytes?

> -----Original Message-----
> From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
> Sent: Friday, 1 September 2006 10:23 AM
> To: Winterbottom, James
> Cc: Andrew Newton; GEOPRIV; John Schnizlein
> Subject: Re: [Geopriv] draft-tschofenig-geopriv-l7-lcp-ps-02.txt
>
> I'm sorry, but that is wrong. Each link only incurs the incremental
> cost of carrying 60 bytes if by value. You'd have to have a dozen
> server hops to compensate for one reference retrieval.
>
> On Aug 31, 2006, at 7:10 PM, Winterbottom, James wrote:
>
> > I might point out that the if the route determining proxy isn't the
> > first proxy, and TLS is used , then the solution argument below is
> > void
> > as the message size is propagated over each link when transported by
> > value, but only over one link where done by reference.
> >
> >> -----Original Message-----
> >> From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
> >> Sent: Friday, 1 September 2006 2:36 AM
> >> To: Andrew Newton
> >> Cc: GEOPRIV; John Schnizlein
> >> Subject: Re: [Geopriv] draft-tschofenig-geopriv-l7-lcp-ps-02.txt
> >>
> >>> 1) If the end host is required to send location by value but the
> >>> location is determined by the network, then that location must be
> > sent
> >>> from the network to the end host, and then from the end host to
the
> > next
> >>> hop. You are right that the first leg could be done by push
instead
> >>> pull, but it is still less efficient than delegating the task to
the
> >>> network.
> >>
> >> I don't think we're disagreeing, but since this gets mentioned a
lot,
> > it
> >> is probably worth qualifying this before the unqualified statement
> >> becomes accepted wisdom. This is only true if the client access
> >> bandwidth is dramatically more scarce or expensive than the
bandwidth
> >> used by the consumers of location information. A reference, due to
> >> the
> >> need to set up a TCP connection and wrap the request and response
in
> >> some kind of protocol, can easily turn a 60-byte (unsigned)
location
> >> object into a 500-byte network transaction, even without TLS. With
> > TLS,
> >> we're probably closer to 2000 bytes, although this is no more than
a
> >> rough guess.
> >>
> >> Henning
> >>
> >> _______________________________________________
> >> Geopriv mailing list
> >> Geopriv@ietf.org
> >> https://www1.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]
>

------------------------------------------------------------------------------------------------
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://www1.ietf.org/mailman/listinfo/geopriv
Received on Thu, 31 Aug 2006 19:26:37 -0500

This archive was generated by hypermail 2.1.8 : Thu Aug 31 2006 - 20:41:53 EDT