[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ecrit] [Geopriv] Announce: Specifying Derived Location in aPIDF-LO
If you were generalizing it:
1. You would want some more generalized id I think. Perhaps that is what
you have, but I don't really see it so far. Specifically, it has to be
unique across PIDFs/XML documents/message bodies. A GUID might be
appropriate
2. You want to specify the relationship. "Derived from" is one
relationship. "Same target, different time" is another.
> -----Original Message-----
> From: Winterbottom, James [mailto:James.Winterbottom at andrew.com]
> Sent: Tuesday, July 29, 2008 5:41 PM
> To: Brian Rosen; Hannes Tschofenig; James M. Polk
> Cc: geopriv at ietf.org; ecrit at ietf.org
> Subject: RE: [Ecrit] [Geopriv] Announce: Specifying Derived Location in
> aPIDF-LO
>
> To be clear, this is expressing a relationship From ecrit-bounces at ietf.org Tue Jul 29 15:21:46 2008
Return-Path: <ecrit-bounces at ietf.org>
X-Original-To: ecrit-archive at megatron.ietf.org
Delivered-To: ietfarch-ecrit-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id B460628C15B;
Tue, 29 Jul 2008 15:21:46 -0700 (PDT)
X-Original-To: ecrit at core3.amsl.com
Delivered-To: ecrit at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 8B0F028C15B;
Tue, 29 Jul 2008 15:21:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.269
X-Spam-Level:
X-Spam-Status: No, score=-2.269 tagged_above=-999 required=5 tests=[AWL=0.330,
BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id QjNDYmZ-xayt; Tue, 29 Jul 2008 15:21:44 -0700 (PDT)
Received: from ebru.winwebhosting.com (ebru.winwebhosting.com [74.55.202.130])
by core3.amsl.com (Postfix) with ESMTP id 810993A687E;
Tue, 29 Jul 2008 15:21:44 -0700 (PDT)
Received: from neustargw.va.neustar.com ([209.173.53.233] helo=BROSLT61xp)
by ebru.winwebhosting.com with esmtpa (Exim 4.69)
(envelope-from <br at brianrosen.net>)
id 1KNxZh-0003x2-Na; Tue, 29 Jul 2008 17:21:46 -0500
From: "Brian Rosen" <br at brianrosen.net>
To: "'Winterbottom, James'" <James.Winterbottom at andrew.com>,
"'Hannes Tschofenig'" <Hannes.Tschofenig at gmx.net>,
"'James M. Polk'" <jmpolk at cisco.com>
References: <E51D5B15BFDEFD448F90BDD17D41CFF1049D1F08 at AHQEX1.andrew.com><488EF181.8080105 at gmx.net><XFE-SJC-2114yri2zmk00005db6 at xfe-sjc-211.amer.cisco.com><E51D5B15BFDEFD448F90BDD17D41CFF157C832 at AHQEX1.andrew.com><XFE-SJC-212ovvQ0Puz00005dc9 at xfe-sjc-212.amer.cisco.com><488F1A5D.6000001 at gmx.net>
<014501c8f191$5c8fa990$12178182 at cis.neustar.com>
<E51D5B15BFDEFD448F90BDD17D41CFF104A3408E at AHQEX1.andrew.com>
Date: Tue, 29 Jul 2008 18:21:49 -0400
Message-ID: <01d301c8f1c9$814d5ab0$12178182 at cis.neustar.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-reply-to: <E51D5B15BFDEFD448F90BDD17D41CFF104A3408E at AHQEX1.andrew.com>
Thread-Index: Acjxf6+kb2Ho2EMZRY2IM37m6hqGqwAAaPcwABCiDhMAAU464A==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-AntiAbuse: This header was added to track abuse,
please include it with any abuse report
X-AntiAbuse: Primary Hostname - ebru.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Source:
X-Source-Args:
X-Source-Dir:
Cc: geopriv at ietf.org, ecrit at ietf.org
Subject: Re: [Ecrit] [Geopriv] Announce: Specifying Derived Location in
aPIDF-LO
X-BeenThere: ecrit at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>,
<mailto:ecrit-request at ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ecrit>
List-Post: <mailto:ecrit at ietf.org>
List-Help: <mailto:ecrit-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>,
<mailto:ecrit-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ecrit-bounces at ietf.org
Errors-To: ecrit-bounces at ietf.org
If you were generalizing it:
1. You would want some more generalized id I think. Perhaps that is what
you have, but I don't really see it so far. Specifically, it has to be
unique across PIDFs/XML documents/message bodies. A GUID might be
appropriate
2. You want to specify the relationship. "Derived from" is one
relationship. "Same target, different time" is another.
> -----Original Message-----
> From: Winterbottom, James [mailto:James.Winterbottom at andrew.com]
> Sent: Tuesday, July 29, 2008 5:41 PM
> To: Brian Rosen; Hannes Tschofenig; James M. Polk
> Cc: geopriv at ietf.org; ecrit at ietf.org
> Subject: RE: [Ecrit] [Geopriv] Announce: Specifying Derived Location in
> aPIDF-LO
>
> To be clear, this is expressing a relationship between between any two things that
> have an XML <id> attribute.
> The draft shows how this can be done to link two location chunks providing
> the location chunks follow the rules laid out in PIDF-LO profile.
>
> Derived from is one way this can be used.
>
> Cheers
> James
>
>
> -----Original Message-----
> From: ecrit-bounces at ietf.org on behalf of Brian Rosen
> Sent: Tue 7/29/2008 10:39 AM
> To: 'Hannes Tschofenig'; 'James M. Polk'
> Cc: geopriv at ietf.org; ecrit at ietf.org
> Subject: Re: [Ecrit] [Geopriv] Announce: Specifying Derived Location in
> aPIDF-LO
>
> Actually, no.
>
> All you need to specify that a location is derived is to have the method
> token set to derived.
>
> James thinks there is value in linking the derived PIDF to the original
> PIDF.
>
> That is a separate question.
>
> I think there is some merit in the basic idea of linking.
>
> I wonder if this is a specific case of a more general notion: expressing a
> relationship between two PIDFs?
>
> Brian
>
>
> > -----Original Message-----
> > From: geopriv-bounces at ietf.org [mailto:geopriv-bounces at ietf.org] On
> Behalf
> > Of Hannes Tschofenig
> > Sent: Tuesday, July 29, 2008 9:26 AM
> > To: James M. Polk
> > Cc: geopriv at ietf.org; ecrit at ietf.org
> > Subject: Re: [Geopriv] [Ecrit] Announce: Specifying Derived Location in
> a
> > PIDF-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?
> > >
> >
> >
> > I am not sure why you guys are arguing around on this issue.
> >
> > * We know that location information is encoded in XML and not
> > particularly small.
> > * We also know that there are security issues with passing location
> > information around. Hence, we use security protocols.
> >
> > What we should think about is whether it makes sense to indicate that
> > location was derived. If you want to indicate that location was derived
> > then there is the question on how to express that fact.
> >
> > Ciao
> > Hannes
> >
> >
> >
> > _______________________________________________
> > Geopriv mailing list
> > Geopriv at ietf.org
> > https://www.ietf.org/mailman/listinfo/geopriv
>
> _______________________________________________
> Ecrit mailing list
> Ecrit at 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]
_______________________________________________
Ecrit mailing list
Ecrit at ietf.org
https://www.ietf.org/mailman/listinfo/ecrit
any two things that
> have an XML <id> attribute.
> The draft shows how this can be done to link two location chunks providing
> the location chunks follow the rules laid out in PIDF-LO profile.
>
> Derived from is one way this can be used.
>
> Cheers
> James
>
>
> -----Original Message-----
> From: ecrit-bounces at ietf.org on behalf of Brian Rosen
> Sent: Tue 7/29/2008 10:39 AM
> To: 'Hannes Tschofenig'; 'James M. Polk'
> Cc: geopriv at ietf.org; ecrit at ietf.org
> Subject: Re: [Ecrit] [Geopriv] Announce: Specifying Derived Location in
> aPIDF-LO
>
> Actually, no.
>
> All you need to specify that a location is derived is to have the method
> token set to derived.
>
> James thinks there is value in linking the derived PIDF to the original
> PIDF.
>
> That is a separate question.
>
> I think there is some merit in the basic idea of linking.
>
> I wonder if this is a specific case of a more general notion: expressing a
> relationship between two PIDFs?
>
> Brian
>
>
> > -----Original Message-----
> > From: geopriv-bounces at ietf.org [mailto:geopriv-bounces at ietf.org] On
> Behalf
> > Of Hannes Tschofenig
> > Sent: Tuesday, July 29, 2008 9:26 AM
> > To: James M. Polk
> > Cc: geopriv at ietf.org; ecrit at ietf.org
> > Subject: Re: [Geopriv] [Ecrit] Announce: Specifying Derived Location in
> a
> > PIDF-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?
> > >
> >
> >
> > I am not sure why you guys are arguing around on this issue.
> >
> > * We know that location information is encoded in XML and not
> > particularly small.
> > * We also know that there are security issues with passing location
> > information around. Hence, we use security protocols.
> >
> > What we should think about is whether it makes sense to indicate that
> > location was derived. If you want to indicate that location was derived
> > then there is the question on how to express that fact.
> >
> > Ciao
> > Hannes
> >
> >
> >
> > _______________________________________________
> > Geopriv mailing list
> > Geopriv at ietf.org
> > https://www.ietf.org/mailman/listinfo/geopriv
>
> _______________________________________________
> Ecrit mailing list
> Ecrit at 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]
_______________________________________________
Ecrit mailing list
Ecrit at ietf.org
https://www.ietf.org/mailman/listinfo/ecrit