2 Feb 2009 20:08
Protocol Action: 'GEOPRIV PIDF-LO Usage Clarification, Considerations and Recommendations' to Proposed Standard
The IESG <iesg-secretary <at> ietf.org>
2009-02-02 19:08:30 GMT
2009-02-02 19:08:30 GMT
The IESG has approved the following document: - 'GEOPRIV PIDF-LO Usage Clarification, Considerations and Recommendations ' <draft-ietf-geopriv-pdif-lo-profile-14.txt> as a Proposed Standard This document is the product of the Geographic Location/Privacy Working Group. The IESG contact persons are Cullen Jennings and Jon Peterson. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-geopriv-pdif-lo-profile-14.txt Technical Summary The Presence Information Data Format Location Object (PIDF-LO) specification provides a flexible and versatile means to represent location information. There are, however, circumstances that arise when information needs to be constrained in how it is represented. In these circumstances the range of options that need to be implemented are reduced. There is growing interest in being able to use location information contained in a PIDF-LO for routing applications. To allow successful interoperability between applications, location information needs to be normative and more tightly constrained than is currently specified in the RFC 4119 (PIDF-LO). This document makes recommendations on how to constrain, represent and interpret locations in a PIDF-LO. It further recommends a subset of GML that is mandatory to implement by applications involved in location based routing.(Continue reading)
>
> This stuff is already implemented and it is also referenced by
> specifications outside the IETF.
The following text is included on the first page of every Internet-Draft,
including this one:
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
EAP-FAST is a _proprietary_ protocol, but the "Internet-Draft" describing
its bizarre pirating of IANA-allocated EAP numbers can't be changed because
EAP-FAST has been "implemented"; yet for some even more bizarre reason, the
IESG seems to believe that the same people who ignore the transient nature
of Internet-Drafts will for some reason honor their weak-kneed "IESG Note"!
Now, yet another Internet-Draft can't be changed because it's been
implemented. If the people who implemented these attributes can read, then
they certainly would have designed their code in such a way that it's easily
modifiable; if not, too bad. Furthermore, the claim is that these
attributes are opaque to any RADIUS server, so the only code needing change
would be special purpose anyway. OTOH, maybe we should replace the
RSS Feed