Requirements for Telepresence Multistreams
draft-ietf-clue-telepresence-requirements-07
Yes
(Gonzalo Camarillo)
No Objection
(Adrian Farrel)
(Barry Leiba)
(Benoît Claise)
(Jari Arkko)
(Joel Jaeggli)
(Martin Stiemerling)
(Spencer Dawkins)
(Stewart Bryant)
Note: This ballot was opened for revision 07 and is now closed.
Gonzalo Camarillo Former IESG member
Yes
Yes
()
Unknown
Richard Barnes Former IESG member
Yes
Yes
(2014-02-05)
Unknown
It would be helpful to expand "CLUE" at some point.
Adrian Farrel Former IESG member
No Objection
No Objection
()
Unknown
Barry Leiba Former IESG member
No Objection
No Objection
()
Unknown
Benoît Claise Former IESG member
No Objection
No Objection
()
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
()
Unknown
Joel Jaeggli Former IESG member
No Objection
No Objection
()
Unknown
Martin Stiemerling Former IESG member
No Objection
No Objection
()
Unknown
Spencer Dawkins Former IESG member
No Objection
No Objection
()
Unknown
Stephen Farrell Former IESG member
No Objection
No Objection
(2014-02-05)
Unknown
No big deal, but... REQMT-1c: Seems to allow locations to be a bit too global and overly-precise, at least potentially. I mean this'd allow for a fine-precision global lat, long, alt to be used, rather than some relative/local dimensions. If this were a protocol that proposed such gloabl fine-grained location be used I'd DISUCSS that, but since this is probably just a little loose and could be implemented without such problems, this is just a nit really. (Similar comment for all REQMTs that say "identify in 3d" or similar.)
Stewart Bryant Former IESG member
No Objection
No Objection
()
Unknown