JSON Encoding of Data Modeled with YANG

Note: This ballot was opened for revision 09 and is now closed.

(Benoît Claise) Yes

(Jari Arkko) No Objection

(Alia Atlas) No Objection

Deborah Brungard No Objection

(Ben Campbell) No Objection

Alissa Cooper No Objection

(Spencer Dawkins) No Objection

(Stephen Farrell) No Objection

Comment (2016-03-17 for -09)
No email
send info
- I would have thought that it'd be useful to point out any
issues with round-tripping, e.g. going from XML to JSON and
back to XML or vice-versa. But I didn't see any mention of
that. How come?

- I'm not sure if anyone has considered XMLDSIG or use of JOSE
with YANG. If one did, then this kind of mapping would not
allow one to preserve digital signatures without a lot of
work. I assume that that's considered ok. (Which it can be,
depending on how one does object level security, if one does
object level security.)

- It's not clear to me if the discussion of the secdir review
[1] concluded. It seemed to just stall. Is there more to be
said? (If so, be great if the shepherd would kick that

   [1] https://www.ietf.org/mail-archive/web/secdir/current/msg06408.html

(Joel Jaeggli) No Objection

Barry Leiba No Objection

(Terry Manderson) No Objection

Alvaro Retana No Objection

(Martin Stiemerling) No Objection