Constrained RESTful Environments

Note: This ballot was opened for revision 01-03 and is now closed.

Ballot question: "Do we approve of this charter?"

(Alia Atlas) Yes

(Spencer Dawkins) Yes

Comment (2016-03-26 for -01-03)
No email
send info
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


Barry Leiba Yes

Deborah Brungard No Objection

(Ben Campbell) No Objection

Comment (2016-03-28 for -01-03)
No email
send info
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) No Objection

Alissa Cooper No Objection

(Stephen Farrell) No Objection

(Brian Haberman) No Objection

Alvaro Retana No Objection