GEOPRIV Working Group Archives
By Date

Google
WWW ecotroph.net
SubjectAuthorDate
Re: [Geopriv] On the value of a DIFF -- RE: Virtual interimconsensus callsRoger Marshall
Re: [Geopriv] [VCARDDAV] The "geo" URI draftAlexander Mayrhofer
Re: [Geopriv] [VCARDDAV] The "geo" URI draftSimon Perreault
Re: [Geopriv] [VCARDDAV] The "geo" URI draftRichard Barnes
Re: [Geopriv] [VCARDDAV] The "geo" URI draftDan Brickley
[Geopriv] I-D Action:draft-ietf-geopriv-geo-uri-00.txtInternet-Drafts@ietf.org
Re: [Geopriv] [VCARDDAV] The "geo" URI draftRichard Barnes
Re: [Geopriv] [VCARDDAV] The "geo" URI draftMarc Berryman
Re: [Geopriv] On the value of a DIFF -- RE: Virtual interim consensus callsRichard Barnes
Re: [Geopriv] On the value of a DIFF -- RE: Virtual interim consensus callsAlexander Mayrhofer
[Geopriv] TestRichard Barnes
Re: [Geopriv] [VCARDDAV] The "geo" URI draftTed Hardie
Re: [Geopriv] [VCARDDAV] The "geo" URI draftTed Hardie
Re: [Geopriv] [VCARDDAV] The "geo" URI draftMarc Berryman
[Geopriv] TestRichard Barnes
Re: [Geopriv] [VCARDDAV] The "geo" URI draftSimon Perreault
Re: [Geopriv] [VCARDDAV] The "geo" URI draftTed Hardie
Re: [Geopriv] [VCARDDAV] The "geo" URI draftAlexey Melnikov
Re: [Geopriv] [VCARDDAV] The "geo" URI draftSimon Perreault
Re: [Geopriv] [VCARDDAV] The "geo" URI draftcreed@opengeospatial.org
Re: [Geopriv] [VCARDDAV] The "geo" URI draftTed Hardie
Re: [Geopriv] [VCARDDAV] The "geo" URI draftPeter Saint-Andre
Re: [Geopriv] [VCARDDAV] The "geo" URI draftAndy Mabbett
Re: [Geopriv] [VCARDDAV] The "geo" URI draftAndy Mabbett
Re: [Geopriv] [VCARDDAV] The "geo" URI draftAndy Mabbett
Re: [Geopriv] [VCARDDAV] The "geo" URI draftAndy Mabbett
[Geopriv] The "geo" URI draftAndy Mabbett
[Geopriv] [VCARDDAV] The "geo" URI draftAndy Mabbett
Re: [Geopriv] [VCARDDAV] The "geo" URI draftDan Brickley
Re: [Geopriv] The "geo" URI draftTatham Oddie
Re: [Geopriv] [VCARDDAV] The "geo" URI draftCarl Reed
Re: [Geopriv] The "geo" URI draftCarl Reed
Re: [Geopriv] [VCARDDAV] The "geo" URI draftTed Hardie
Re: [Geopriv] The "geo" URI draftThomson, Martin
[Geopriv] [geopriv] #1: Correct EPSG number for WGS84geopriv issue tracker
Re: [Geopriv] The "geo" URI draftMarc Berryman
[Geopriv] HELD ResponseTime parameter with value emergencyRoutingRosen, Brian
[Geopriv] [geopriv] #2: Add DHCPv6 option formatgeopriv issue tracker
[Geopriv] [geopriv] #3: GML Mappinggeopriv issue tracker
[Geopriv] [geopriv] #4: Uncertainty semantic for resolution fieldsgeopriv issue tracker
Re: [Geopriv] The "geo" URI draftRichard Barnes
[Geopriv] [geopriv] #5: Client guidance about the datum fieldgeopriv issue tracker
Re: [Geopriv] HELD ResponseTime parameter with value emergencyRoutingThomson, Martin
[Geopriv] Plan for 3825bisRichard Barnes
Re: [Geopriv] The "geo" URI draftPeter Saint-Andre
Re: [Geopriv] HELD ResponseTime parameter with valueemergencyRoutingWinterbottom, James
Re: [Geopriv] HELD ResponseTime parameter with value emergencyRoutingRichard Barnes
Re: [Geopriv] HELD ResponseTime parameter with value emergencyRoutingThomson, Martin
Re: [Geopriv] HELD ResponseTime parameter with valueemergencyRoutingRichard Barnes
Re: [Geopriv] HELD ResponseTime parameter with value emergencyRoutingDawson, Martin
Re: [Geopriv] HELD ResponseTime parameter with value emergencyRoutingRichard Barnes
Re: [Geopriv] HELD ResponseTime parameter withvalue emergencyRoutingWinterbottom, James
Re: [Geopriv] HELD ResponseTime parameter withvalue emergencyRoutingRichard Barnes
Re: [Geopriv] HELD ResponseTime parameter withvalue emergencyRoutingWinterbottom, James
[Geopriv] Updated residential gateway documentThomson, Martin
Re: [Geopriv] HELD ResponseTime parameter withvalue emergencyRoutingThomson, Martin
Re: [Geopriv] HELD ResponseTime parameter with value emergencyRoutingDawson, Martin
Re: [Geopriv] HELD ResponseTime parameter withvalue emergencyRoutingRichard Barnes
Re: [Geopriv] The "geo" URI draftRay.Bellis@nominet.org.uk
Re: [Geopriv] The "geo" URI draftAndy Mabbett
Re: [Geopriv] The "geo" URI draftAndy Mabbett
Re: [Geopriv] The "geo" URI draftAlexander Mayrhofer
Re: [Geopriv] The "geo" URI draftDan Brickley
Re: [Geopriv] [VCARDDAV] The "geo" URI draftAlexander Mayrhofer
Re: [Geopriv] The "geo" URI draftRichard Barnes
Re: [Geopriv] HELD ResponseTime parameter withvalue emergencyRoutingBrian Rosen
Re: [Geopriv] The "geo" URI draftRay.Bellis@nominet.org.uk
Re: [Geopriv] The "geo" URI draftAndy Mabbett
Re: [Geopriv] The "geo" URI draftRichard Barnes
Re: [Geopriv] The "geo" URI draftCarl Reed
Re: [Geopriv] [VCARDDAV] The "geo" URI draftCarl Reed
Re: [Geopriv] [VCARDDAV] The "geo" URI draftTed Hardie
Re: [Geopriv] [VCARDDAV] The "geo" URI draftRichard Barnes
[Geopriv] GEOPRIV Minutes from Virtual Interim, 21 May 2009Richard Barnes
Re: [Geopriv] [VCARDDAV] The "geo" URI draftTed Hardie
[Geopriv] The "geo" URI draftAndy Mabbett
Re: [Geopriv] [VCARDDAV] The "geo" URI draftThomson, Martin
Re: [Geopriv] HELD ResponseTime parameter withvalue emergencyRoutingThomson, Martin
Re: [Geopriv] [VCARDDAV] The "geo" URI draftThomson, Martin
Re: [Geopriv] [VCARDDAV] The "geo" URI draftDawson, Martin
[Geopriv] Update to uncertainty and confidence informational draftThomson, Martin
[Geopriv] draft-ietf-geopriv-geo-uri-00 brief commentsThomson, Martin
Re: [Geopriv] draft-ietf-geopriv-geo-uri-00 brief commentsAlexander Mayrhofer
Re: [Geopriv] HELD ResponseTime parameter withvalue emergencyRoutingRosen, Brian
Re: [Geopriv] [VCARDDAV] The "geo" URI draft - FYICarl Reed
Re: [Geopriv] HELD ResponseTime parameter withvalue emergencyRoutingThomson, Martin
Re: [Geopriv] draft-ietf-geopriv-geo-uri-00 brief commentsThomson, Martin
[Geopriv] -00 Strawman of RFC 3825bis for ReviewBernard Aboba
Re: [Geopriv] -00 Strawman of RFC 3825bis for ReviewThomson, Martin
Re: [Geopriv] -00 Strawman of RFC 3825bis for ReviewHannes Tschofenig
Re: [Geopriv] -00 Strawman of RFC 3825bis for ReviewBernard Aboba
Re: [Geopriv] -00 Strawman of RFC 3825bis for ReviewJames M. Polk
Re: [Geopriv] -00 Strawman of RFC 3825bis for ReviewHannes Tschofenig
Re: [Geopriv] -00 Strawman of RFC 3825bis for ReviewDRAGE, Keith (Keith)
Re: [Geopriv] -00 Strawman of RFC 3825bis for ReviewHannes Tschofenig
Re: [Geopriv] -00 Strawman of RFC 3825bis for ReviewDRAGE, Keith (Keith)
[Geopriv] [geopriv] #6: Authorshipgeopriv issue tracker
Re: [Geopriv] [geopriv] #6: Authorshipgeopriv issue tracker
Re: [Geopriv] [geopriv] #6: AuthorshipRichard Barnes
Re: [Geopriv] [geopriv] #1: Correct EPSG number for WGS84geopriv issue tracker
Re: [Geopriv] -00 Strawman of RFC 3825bis for ReviewCarl Reed
Re: [Geopriv] -00 Strawman of RFC 3825bis for ReviewCarl Reed
[Geopriv] Protocol Action: 'Carrying Location Objects in RADIUS and Diameter' to Proposed StandardThe IESG
Re: [Geopriv] [geopriv] #1: Correct EPSG number for WGS84James M. Polk
Re: [Geopriv] [geopriv] #1: Correct EPSG number for WGS84geopriv issue tracker
Re: [Geopriv] HELD ResponseTime parameter withvalue emergencyRoutingBrian Rosen
[Geopriv] I-D Action:draft-ietf-geopriv-rfc3825bis-00.txtInternet-Drafts@ietf.org
[Geopriv] Document Action: 'Implications of 'retransmission-allowed' for SIP Location Conveyance' to Informational RFCThe IESG
Re: [Geopriv] [geopriv] #1: Correct EPSG number for WGS84geopriv issue tracker
[Geopriv] [geopriv] #7: Identity CRS URN for each "datum"geopriv issue tracker
[Geopriv] [geopriv] #8: Altitude type of 0 == no altitudegeopriv issue tracker
Re: [Geopriv] [geopriv] #8: Altitude type of 0 == no altitudeGlen Zorn
Re: [Geopriv] [geopriv] #8: Altitude type of 0 == no altitudeRichard Barnes
Re: [Geopriv] [geopriv] #8: Altitude type of 0 == no altitudeThomson, Martin
Re: [Geopriv] [geopriv] #8: Altitude type of 0 == no altitudeThomson, Martin
Re: [Geopriv] [geopriv] #8: Altitude type of 0 == no altitudeWinterbottom, James
Re: [Geopriv] draft-ietf-geopriv-geo-uri-00 brief commentsAndy Mabbett
Re: [Geopriv] The "geo" URI draftAndy Mabbett
Re: [Geopriv] The "geo" URI draftAndy Mabbett
Re: [Geopriv] The "geo" URI draftAndy Mabbett
Re: [Geopriv] The "geo" URI draftAndy Mabbett
Re: [Geopriv] [geopriv] #8: Altitude type of 0 == no altitudecreed@opengeospatial.org
[Geopriv] WG Review: Recharter of Geographic Location/Privacy (geopriv)IESG Secretary
Re: [Geopriv] [geopriv] #8: Altitude type of 0 == no altitudeJames M. Polk
Re: [Geopriv] [geopriv] #8: Altitude type of 0 == no altitudeJames M. Polk
Re: [Geopriv] [geopriv] #8: Altitude type of 0 == no altitudeJames M. Polk
[Geopriv] Gen-ART Review of draft-ietf-geopriv-civic-address-recommendations-02McCann Peter-A001034
Re: [Geopriv] draft-ietf-geopriv-geo-uri-00 brief commentsThomson, Martin
Re: [Geopriv] [geopriv] #8: Altitude type of 0 == no altitudeAlexander Mayrhofer
Re: [Geopriv] [geopriv] #8: Altitude type of 0 == no altitudeRichard Barnes
Re: [Geopriv] [geopriv] #8: Altitude type of 0 == no altitudeJames M. Polk
[Geopriv] Datum field changes in RFC 3825bis (affecting Sections 2, 2.1 and 6.2)Bernard Aboba
Re: [Geopriv] Datum field changes in RFC 3825bis (affecting Sections 2, 2.1 and 6.2)Thomson, Martin
Re: [Geopriv] Datum field changes in RFC 3825bis (affecting Sections 2, 2.1 and 6.2)Bernard Aboba
Re: [Geopriv] Datum field changes in RFC 3825bis (affecting Sections 2, 2.1 and 6.2)Thomson, Martin
Re: [Geopriv] Datum field changes in RFC 3825bis (affecting Sections 2, 2.1 and 6.2)Bernard Aboba
Re: [Geopriv] Datum field changes in RFC 3825bis (affecting Sections 2, 2.1 and 6.2)Thomson, Martin
[Geopriv] [geopriv] #9: Split of RFC 3826 Datum field into three partsgeopriv issue tracker
Re: [Geopriv] [geopriv] #9: Split of RFC 3825 Datum field into three parts (was: Split of RFC 3826 Datum field into three parts)geopriv issue tracker
Re: [Geopriv] #8: Altitude type of 0 == no altitude - Guidance from the OGC Geodesy communityCarl Reed
Re: [Geopriv] #8: Altitude type of 0 == no altitude - Guidance from the OGC Geodesy communityRichard Barnes
Re: [Geopriv] Datum field changes in RFC 3825bis (affecting Sections 2, 2.1 and 6.2)James M. Polk
Re: [Geopriv] Datum field changes in RFC 3825bis (affecting Sections 2, 2.1 and 6.2)James M. Polk
Re: [Geopriv] #8: Altitude type of 0 == no altitude - Guidance from the OGC Geodesy communityJames M. Polk
Re: [Geopriv] #8: Altitude type of 0 == no altitude - Guidance from the OGC Geodesy communityThomson, Martin
Re: [Geopriv] #8: Altitude type of 0 == no altitude - Guidance from the OGC Geodesy communityJames M. Polk
Re: [Geopriv] #8: Altitude type of 0 == no altitude - Guidance from the OGC Geodesy communityThomson, Martin
Re: [Geopriv] #8: Altitude type of 0 == no altitude - Guidance from the OGC Geodesy communityJames M. Polk
Re: [Geopriv] #8: Altitude type of 0 == no altitude - Guidance from the OGC Geodesy communityThomson, Martin
Re: [Geopriv] #8: Altitude type of 0 == no altitude - Guidance from the OGC Geodesy communityCarl Reed
Re: [Geopriv] #8: Altitude type of 0 == no altitude - Guidance from the OGC Geodesy communityTed Hardie
Re: [Geopriv] #8: Altitude type of 0 == no altitude - Guidance from the OGC Geodesy communityJames M. Polk
Re: [Geopriv] WG Review: Recharter of Geographic Location/Privacy (geopriv)g.caron@bell.ca
Re: [Geopriv] WG Review: Recharter of Geographic Location/Privacy (geopriv)Ray.Bellis@nominet.org.uk
Re: [Geopriv] WG Review: Recharter ofGeographic Location/Privacy (geopriv)Tschofenig, Hannes (NSN - FI/Espoo)
Re: [Geopriv] WG Review: RecharterofGeographic Location/Privacy (geopriv)Winterbottom, James
Re: [Geopriv] WG Review: Recharter of Geographic Location/Privacy (geopriv)Bernard Aboba
Re: [Geopriv] WG Review: Recharter of Geographic Location/Privacy (geopriv)Cullen Jennings
Re: [Geopriv] WG Review: Recharter of GeographicLocation/Privacy (geopriv)Thomson, Martin
Re: [Geopriv] WG Review: Recharter of GeographicLocation/Privacy (geopriv)Brian Rosen
Re: [Geopriv] WG Review: Recharterof GeographicLocation/Privacy (geopriv)Dawson, Martin
Re: [Geopriv] WG Review: Recharterof GeographicLocation/Privacy (geopriv)James M. Polk
Re: [Geopriv] WG Review: Recharterof GeographicLocation/Privacy (geopriv)Dawson, Martin
Re: [Geopriv] WG Review: Recharterof GeographicLocation/Privacy (geopriv)Ray.Bellis@nominet.org.uk
Re: [Geopriv] WG Review: Recharterof GeographicLocation/Privacy (geopriv)Brian Rosen
Re: [Geopriv] WG Review:Recharterof GeographicLocation/Privacy (geopriv)Cullen Jennings
Re: [Geopriv] WGReview:Recharterof GeographicLocation/Privacy (geopriv)Winterbottom, James
Re: [Geopriv] Datum field changes in RFC 3825bis (affecting Sections 2, 2.1 and 6.2)DRAGE, Keith (Keith)
Re: [Geopriv] Datum field changes in RFC 3825bis (affecting Sections 2, 2.1 and 6.2)Thomson, Martin
Re: [Geopriv] Gen-ART Review of draft-ietf-geopriv-civic-address-recommendations-02Karl Heinz Wolf
Re: [Geopriv] Datum field changes in RFC 3825bis (affecting Sections 2, 2.1 and 6.2)DRAGE, Keith (Keith)
Re: [Geopriv] Datum field changes in RFC 3825bis (affecting Sections 2, 2.1 and 6.2)Thomson, Martin
[Geopriv] [geopriv] #10: Should not encourage use of "old" encodinggeopriv issue tracker
[Geopriv] Issue: version "negotiation"Bernard Aboba
Re: [Geopriv] Issue: version "negotiation"Thomson, Martin
Re: [Geopriv] Issue: version "negotiation"James M. Polk
Re: [Geopriv] Issue: version "negotiation"Bernard Aboba
Re: [Geopriv] Issue: version "negotiation"Ray.Bellis@nominet.org.uk
Re: [Geopriv] Issue: version "negotiation"James M. Polk
Re: [Geopriv] [geopriv] #10: Should not encourage use of "old" encodingJames M. Polk
[Geopriv] WG Action: RECHARTER: Geographic Location/Privacy (geopriv)IESG Secretary
Re: [Geopriv] Issue: version "negotiation"Gabor.Bajko@nokia.com
Re: [Geopriv] [geopriv] #10: Should not encourage use of "old" encodingGabor.Bajko@nokia.com
Re: [Geopriv] Issue: version "negotiation"James M. Polk
Re: [Geopriv] [geopriv] #10: Should not encourage use of "old" encodingJames M. Polk
[Geopriv] I-D Action:draft-ietf-geopriv-http-location-delivery-15.txtInternet-Drafts@ietf.org
[Geopriv] FW: I-DAction:draft-ietf-geopriv-http-location-delivery-15.txtMary Barnes
Re: [Geopriv] Issue: version "negotiation"Gabor.Bajko@nokia.com
Re: [Geopriv] Issue: version "negotiation"James M. Polk
Re: [Geopriv] Issue: version "negotiation"Gabor.Bajko@nokia.com
Re: [Geopriv] Issue: version "negotiation"James M. Polk
Re: [Geopriv] Issue: version "negotiation"Marc Linsner
Re: [Geopriv] Issue: version "negotiation"Ted Hardie
Re: [Geopriv] Issue: version "negotiation"Gabor.Bajko@nokia.com
Re: [Geopriv] I-DAction:draft-ietf-geopriv-http-location-delivery-15.txtBen Campbell
Re: [Geopriv] Issue: version "negotiation"Brian Rosen
Re: [Geopriv] Issue: version "negotiation"Gabor.Bajko@nokia.com
Re: [Geopriv] Issue: version "negotiation"Bernard Aboba
Re: [Geopriv] Issue: version "negotiation"James M. Polk
Re: [Geopriv] Issue: version "negotiation" (1 LCP?)James M. Polk
Re: [Geopriv] Issue: version "negotiation"Bernard Aboba
Re: [Geopriv] Issue: version "negotiation"James M. Polk
Re: [Geopriv] Issue: version "negotiation"Marc Linsner
Re: [Geopriv] Issue: version "negotiation"Stark, Barbara
Re: [Geopriv] Issue: version "negotiation"Thomson, Martin
Re: [Geopriv] [geopriv] #10: Server Version Support (was: Should not encourage use of "old" encoding)geopriv issue tracker
Re: [Geopriv] Issue: version "negotiation"Bernard Aboba
Re: [Geopriv] [geopriv] #10: Server Version Support (was: Should not encourage use of "old" encoding)James M. Polk
Re: [Geopriv] [geopriv] #10: Server Version Support (was: Should not encourage use of "old" encoding)Bernard Aboba
Re: [Geopriv] [geopriv] #10: Server Version Support (was: Should not encourage use of "old" encoding)Thomson, Martin
Re: [Geopriv] [geopriv] #10: Server Version Support (was: Should not encourage use of "old" encoding)James M. Polk
Re: [Geopriv] [geopriv] #10: Server Version Support (was: Should not encourage use of "old" encoding)Thomson, Martin
Re: [Geopriv] [geopriv] #10: Server Version Support (was: Should not encourage use of "old" encoding)James M. Polk
Re: [Geopriv] [geopriv] #10: Server Version Support (was: Should not encourage use of "old" encoding)Thomson, Martin
[Geopriv] loc-filters additional requirementsThomson, Martin
Re: [Geopriv] loc-filters additional requirementsBrian Rosen
Re: [Geopriv] [geopriv] #10: Server Version Support (was: Should not encourage use of "old" encoding)creed@opengeospatial.org
Re: [Geopriv] [geopriv] #10: Server Version Support (was: Should not encourage use of "old" encoding)James M. Polk
Re: [Geopriv] loc-filters additional requirementsThomson, Martin
Google
WWW ecotroph.net

This archive was generated by hypermail 2.1.8 : 01 Aug 2012 EDT