RE: [Geopriv] Geopriv L7 LCP Location-Per-Value

From: Dawson, Martin ^lt;Martin.Dawson@andrew.com>
Date: Tue Sep 19 2006 - 18:28:37 EDT

I'd actually find that quite a contentious step...

> -----Original Message-----
> From: Brian Rosen [mailto:br@brianrosen.net]
> Sent: Wednesday, 20 September 2006 4:13 AM
> To: Dawson, Martin; 'Hannes Tschofenig'; 'Abbott, Nadine B'
> Cc: geopriv@ietf.org
> Subject: RE: [Geopriv] Geopriv L7 LCP Location-Per-Value
>
> If I might jump in here, my opinion is that one way to make progress
on L7
> is to avoid contentious issues. So, we could try dealing solely with
an
> L7
> LbyV protocol, leaving the LbyR stuff behind for the moment.
>
> Similarly, we could make progress on a protocol with an abstract
> identifier,
> simultaneously looking into the security issues of using an IP address
as
> one possible concrete identifier.
>
> Brian
>
> > -----Original Message-----
> > From: Dawson, Martin [mailto:Martin.Dawson@andrew.com]
> > Sent: Tuesday, September 19, 2006 2:04 PM
> > To: Hannes Tschofenig; Abbott, Nadine B
> > Cc: geopriv@ietf.org
> > Subject: RE: [Geopriv] Geopriv L7 LCP Location-Per-Value
> >
> > Hi Hannes,
> >
> > Can you clarify your question?
> >
> > I think there is consensus that there should be a protocol that
provides
> > location-by-value. Did you mean inclusive with, or to the exclusion
of,
> > location-by-reference?
> >
> > Cheers,
> > Martin
> >
> > > -----Original Message-----
> > > From: Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net]
> > > Sent: Wednesday, 20 September 2006 12:10 AM
> > > To: Abbott, Nadine B
> > > Cc: geopriv@ietf.org
> > > Subject: Re: [Geopriv] Geopriv L7 LCP Location-Per-Value
> > >
> > > HI Nadine,
> > >
> > >
> > > Abbott, Nadine B schrieb:
> > > > Hi, Hannes,
> > > >
> > > > I assume you are talking about Location-by-Value (and not
something
> > else
> > > > entirely that I've missed)?
> > >
> > > Yes. Location-per-value / Location-by-Value (all the same)
> > >
> > > >
> > > > I certainly HOPE so. The need for a L7 protocol to provide
location
> > > > information was communicated to this working group about 1 1/2
years
> > > > ago.
> > >
> > > You comment is taken. I just want to make sure that we move
forward
> > with
> > > our discussion.
> > >
> > > >
> > > > We've had one proposal on the table for at least that long, and
> > lately,
> > > > others.
> > > > I hope we can come to a consensus that one of these meets the
> > Geopriv
> > > > LCP requirements.
> > >
> > > I hope so too.
> > >
> > > >
> > > > Since the community of access providers that identified this
need
> > have
> > > > also invested effort considering how they might implement the
> > > > longest-running contender, HELD, I myself would favor
concentrating
> > on
> > > > working out any issues that remain as obstacles to adopting it
as an
> > RFC
> > > > standard.
> > > Given the latest discussion I cannot say that we are making good
> > progress.
> > >
> > >
> > > Ciao
> > > Hanne
> > >
> > > > Thanks,
> > > > Nadine
> > > >
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net]
> > > > Sent: Tuesday, September 19, 2006 8:52 AM
> > > > To: GEOPRIV
> > > > Subject: [Geopriv] Geopriv L7 LCP Location-Per-Value
> > > >
> > > > Hi all,
> > > >
> > > > as some of you might have noticed we got a bit stuck with the
> > > > location-by-reference discussion.
> > > >
> > > > Do people agree that we want to work on a Geopriv L7 LCP
solution
> > for
> > > > transport of Location-Per-Value?
> > > >
> > > > Ciao
> > > > Hannes
> > > >
> > > > _______________________________________________
> > > > Geopriv mailing list
> > > > Geopriv@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/geopriv
> > > >
> > > >
> > >
> > >
> > > _______________________________________________
> > > 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]
> >
> > _______________________________________________
> > 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]

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www1.ietf.org/mailman/listinfo/geopriv
Received on Tue, 19 Sep 2006 17:28:37 -0500

This archive was generated by hypermail 2.1.8 : Tue Sep 19 2006 - 18:45:48 EDT