Requirements for a Location-by-Reference Mechanism
draft-ietf-geopriv-lbyr-requirements-09
Yes
(Cullen Jennings)
No Objection
(Adrian Farrel)
(Jari Arkko)
(Lars Eggert)
(Pasi Eronen)
(Robert Sparks)
(Ron Bonica)
(Russ Housley)
Note: This ballot was opened for revision 09 and is now closed.
Alexey Melnikov Former IESG member
Yes
Yes
(2009-10-22)
Unknown
I like the document. 1. Introduction As justification for a LbyR model, consider the circumstance that in some mobile networks it is not efficient for the end host to periodically query the Location Information Server (LIS) for up-to- date location information. This is especially the case when ower Did you mean "owner"? availability is a constraint or when a location update is not immediately needed.
Cullen Jennings Former IESG member
Yes
Yes
()
Unknown
Adrian Farrel Former IESG member
No Objection
No Objection
()
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
()
Unknown
Lars Eggert Former IESG member
No Objection
No Objection
()
Unknown
Lisa Dusseault Former IESG member
No Objection
No Objection
(2009-10-22)
Unknown
Section 1 has the phrase "This is especially the case when ower availability is a constraint" -- I can't understand this phrase even if I try "owner" for "ower" Section 1 says "Note that this document makes no differentiation between a Location Server (LS), per [RFC3693], and a Location Information Server (LIS)," but diagram 1 explicitly differentiates between them so the Note is false.
Pasi Eronen Former IESG member
No Objection
No Objection
()
Unknown
Robert Sparks Former IESG member
No Objection
No Objection
()
Unknown
Ron Bonica Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown