Please us an appropriate subject line : Re: [Geopriv] draft agenda: GEOPRIV @ IETF 70

[Robert Sparks <[e-mail]>]

Hi folks -

For _every_ post you send to this list, please look at the subject  
line and make sure it's still on topic.

The last several messages posted to _this_ topic are going to be  
really hard to find in the archive later.

RjS

On Nov 21, 2007, at 3:33 PM, Winterbottom, James wrote:

> Hi James,
>
> Sorry, I was just trying to present the use-case and document the
> existing requirements. Comes about as a force of habit with this WG...
> *8)
>
> Cheers
> James
>
>
>
>> -----Original Message-----
>> From: James M. Polk [mailto:[e-mail]]
>> Sent: Thursday, 22 November 2007 8:26 AM
>> To: Winterbottom, James; Marc Linsner; Stark, Barbara;
>> [e-mail]; [e-mail]
>> Subject: RE: [Geopriv] draft agenda: GEOPRIV @ IETF 70
>>
>> James
>>
>> You can reply without being so incredibly defensive, can't you?
>>
>> At 02:42 PM 11/21/2007, Winterbottom, James wrote:
>>> Content-class: urn:content-classes:message
>>> Content-Type: multipart/alternative;
>>>         boundary="----_=_NextPart_001_01C82C7E.FAF514D5"
>>>
>>> Marc,
>>>
>>> Suppose the identifier is a MAC address, since this has no formal
>>> URI representation  then what?
>>> Suppose HELD is bound to a transport other than HTTP, such as in
>>> <http://tools.ietf.org/html/draft-thomson-geopriv-held-beep-
>> 01>http://tools.ietf.org/html/draft-thomson-geopriv-held-beep-01,
>>> how are the parameters simply added to the URI? Does it even make
>>> sense to do so?
>>>
>>> <http://www.ietf.org/internet-drafts/draft-ietf-geopriv-l7-lcp-ps-
>>
> 06.txt>http://www.ietf.org/internet-drafts/draft-ietf-geopriv-l7- 
> lcp-ps-
>> 06.txt
>>> indicates that identifiers other than IP address will be required in
>>> some scenarios.
>>>
>>> <http://www.ietf.org/internet-drafts/draft-ietf-ecrit-phonebcp-
>> 03.txt>http://www.ietf.org/internet-drafts/draft-ietf-ecrit-phonebcp-
>> 03.txt
>>> identifies the need, in some situations, for an outbound proxy to
>>> insert location on-behalf-of the calling device. In this situation
>>> using HELD requires a formal way to express how the Device is being
>>> identified, and what the identifier represents.
>>>
>>> Please read the draft
>>> <http://tools.ietf.org/html/draft-winterbottom-geopriv-held- 
>>> identity-
>>
> extensions-04>http://tools.ietf.org/html/draft-winterbottom-geopriv- 
> held
> -
>> identity-extensions-04
>>> before jumping on to the attack.
>>>
>>> There are several architectures and deployments well underway that
>>> require this work. The ABNF definitions in the extensions draft have
>>> applicability beyond just HELD. I don't see a need to delay this  
>>> work
>> further.
>>>
>>> Cheers
>>> James
>>>
>>>
>>> ----------
>>> From: Marc Linsner [mailto:[e-mail]]
>>> Sent: Thursday, 22 November 2007 4:54 AM
>>> To: 'Stark, Barbara'; [e-mail]; [e-mail]
>>> Subject: RE: [Geopriv] draft agenda: GEOPRIV @ IETF 70
>>>
>>> Barbara,
>>>
>>> Remind me again why this can't be accomplished by putting the
>>> identifier in the uri?  ex:
>>> <mailto:[e-mail]>[e-mail]
>>>
>>> Thanks,
>>>
>>> -Marc-
>>>
>>>
>>>
>>>
>>> ----------
>>> From: Stark, Barbara [mailto:[e-mail]]
>>> Sent: Wednesday, November 21, 2007 12:17 PM
>>> To: [e-mail]; [e-mail]
>>> Subject: Re: [Geopriv] draft agenda: GEOPRIV @ IETF 70
>>>
>>> Robert,
>>> I think the HELD identity extensions is important. It's needed for
>>> LIS to LIS communication, which is critical where the entity who
>>> assigns the public IP address is not the same as the access  
>>> provider.
>>> Barbara
>>>
>>> ----- Original Message -----
>>> From: Robert Sparks <[e-mail]>
>>> To: GEOPRIV <[e-mail]>
>>> Sent: Tue Nov 20 15:09:03 2007
>>> Subject: [Geopriv] draft agenda: GEOPRIV @ IETF 70
>>>
>>> Folks -
>>>
>>> We have 2.5 hrs in Vancouver (Friday morning). Based on our  
>>> chartered
>>> work, list discussions, and agenda requests, here's the agenda I'm
>>> planning to follow:
>>>
>>> 15m     Administrivia   Chairs
>>> 30m     http-location-delivery  Mary (<- Lets finish this one!)
>>> 20m     Finishing geopriv-policy        Hannes/Cullen
>>> 30m     LIS Discovery   James W
>>> 10m     l7lcp-ps        Hannes
>>> 20m     pidf-lo-dynamic Henning
>>> 15m     dhcp-lbyr-uri-option    James P
>>> 10m     civicaddresses-austria  Karl
>>> 20m     Uncertainty and Confidence      James W
>>> 10m     HELD Dereference        James W
>>>
>>> As usual, we have many other requests to talk about other things -
>>> please take those to the list for now.
>>>
>>> This is a draft agenda and we can change it. Let me know if you  
>>> think
>>> I've missed something important.
>>>
>>> RjS
>>>
>>>
>>> _______________________________________________
>>> Geopriv mailing list
>>> [e-mail]
>>
>> <https://www1.ietf.org/mailman/listinfo/geopriv>https:// 
>> www1.ietf.org/m
> ai
>> lman/listinfo/geopriv
>>>
>>> *****
>>>
>>> The information transmitted is intended only for the person or
>>> entity to which it is addressed and may contain confidential,
>>> proprietary, and/or privileged material. Any review, retransmission,
>>> dissemination or other use of, or taking of any action in reliance
>>> upon this information by persons or entities other than the intended
>>> recipient is prohibited. If you received this in error, please
>>> contact the sender and delete the material from all computers. GA623
>>>
>>>
>>>
>>>
>>
>> --------------------------------------------------------------------- 
>> --
> --
>> -----------------------
>>> 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
>>> [e-mail]
>>> 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
[e-mail]
https://www1.ietf.org/mailman/listinfo/geopriv