> -----Original Message-----
> From: geopriv-bounces@ietf.org [mailto:geopriv-bounces@ietf.org] On
> Behalf Of geopriv issue tracker
> Sent: Wednesday, 29 July 2009 3:32 PM
> To: alexander.mayrhofer@nic.at
> Cc: geopriv@ietf.org
> Subject: [Geopriv] [geopriv] #11: Registry for URI parameters?
>
> #11: Registry for URI parameters?
> ----------------------------------------+------------------------------
> -----
> Reporter: alexander.mayrhofer@nic.at | Owner:
> Type: defect | Status: new
> Priority: major | Milestone:
> Component: geo-uri | Version:
> Severity: Active WG Document | Keywords:
> ----------------------------------------+------------------------------
> -----
> Currently, the draft defines one URI parameter - "crs", as a
> compromise to
> not conclude the use of other CRSes
>
> Q1) should the draft define a IANA URI parameter registry for the
> "geo"
> URI, and register the single "crs" parameter
>
> Q2) If yes, what action should be required for registering a parameter
> name
>
> (Note: from experience with the Enumservices, i would strongly oppose
> "expert review", and go for "standards action")
>
> --
> Ticket URL: <http://trac.tools.ietf.org/wg/geopriv/trac/ticket/11>
> geopriv <http://tools.ietf.org/geopriv/>
>
> _______________________________________________
> Geopriv mailing list
> Geopriv@ietf.org
> https://www.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://www.ietf.org/mailman/listinfo/geopriv
