Constrained RESTful Environments
charter-ietf-core-02
Yes
(Alia Atlas)
(Barry Leiba)
No Objection
(Alissa Cooper)
(Alvaro Retana)
(Benoît Claise)
(Brian Haberman)
(Deborah Brungard)
(Stephen Farrell)
Note: This ballot was opened for revision 01-03 and is now closed.
Ballot question: "Do we approve of this charter?"
Alia Atlas Former IESG member
Yes
Yes
(for -01-03)
Unknown
Barry Leiba Former IESG member
Yes
Yes
(for -01-03)
Unknown
Spencer Dawkins Former IESG member
Yes
Yes
(2016-03-26 for -01-03)
Unknown
I'm fine with rechartering CORE with roughly this charter (I'm a Yes), but just to make sure I understand, is it correct that the completed portfolio would include CoAP over HTTP (I didn't check the mapping RFC, but I'm guessing this includes HTTPS), and CoAP over TLS, and CoAP over TCP ?
Alissa Cooper Former IESG member
No Objection
No Objection
(for -01-03)
Unknown
Alvaro Retana Former IESG member
No Objection
No Objection
(for -01-03)
Unknown
Ben Campbell Former IESG member
No Objection
No Objection
(2016-03-28 for -01-03)
Unknown
I think Göran's review made a good point that the charter should explicitly mention that the group will keep privacy and pervasive monitoring in mind. I don't think the charter needs to call out specific solutions, but the topic should be a point of focus. I still think the charter is too long and goes into unnecessary technical detail. But I recognize much of that comes from the original charter so I will not push the point.
Benoît Claise Former IESG member
No Objection
No Objection
(for -01-03)
Unknown
Brian Haberman Former IESG member
No Objection
No Objection
(for -01-03)
Unknown
Deborah Brungard Former IESG member
No Objection
No Objection
(for -01-03)
Unknown
Stephen Farrell Former IESG member
No Objection
No Objection
(for -01-03)
Unknown