Constrained RESTful Environments
charter-ietf-core-02

[Ballot comment]
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.

[Ballot comment]
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

?

[Ballot comment]

"working with DICE" is not that good an idea perhaps, as DICE may
be about to close. How will that work be (well) done if DICE closes?
This should be easy to unblock assuming the answer is "yes, there
is a gap that needs to be addressed and we'll work with the security
area to figure out a way to handle that."

[Ballot block]

"working with DICE" is not that good an idea perhaps, as DICE may
be about to close. How will that work be (well) done if DICE closes?
This should be easy to unblock assuming the answer is "yes, there
is a gap that needs to be addressed and we'll work with the security
area to figure out a way to handle that."

[Ballot block]
Two points I would like to discuss.

- "CoRE will also develop a way to make RESTCONF-style management functions
available via CoAP that is appropriate for constrained node networks.  This
will require very close coordination with NETCONF and other operations and
management working groups."

What is the goal of this coordination with NETCONF?
Could RESTCONF be reused? If not, why not?
If yes, will RESTCONF need to be modified?

- What is the data model (language) used for the resources? For example,
RESTCONF uses YANG
Maybe, this information is in this paragraph

CoRE will work on related data formats, such as alternative representations
of RFC 6690 link format and RFC 7390 group communication information.  The
working group will complete the SenML specification, again with
consideration to its adoption in OMA LWM2M.

However, I have no clue what the second sentence means.