NETCONF over Transport Layer Security (TLS)
RFC 5539
Yes
(Dan Romascanu)
No Objection
Lars Eggert
(Cullen Jennings)
(David Ward)
(Jari Arkko)
(Jon Peterson)
(Magnus Westerlund)
(Mark Townsley)
(Ron Bonica)
(Ross Callon)
(Russ Housley)
(Tim Polk)
Note: This ballot was opened for revision 07 and is now closed.
Lars Eggert
No Objection
Dan Romascanu Former IESG member
Yes
Yes
()
Unknown
Chris Newman Former IESG member
No Objection
No Objection
(2009-03-11)
Unknown
I support Jari and Tim's discuss positions. If there is a need for authentication mechanisms other than TLS client certificates for this transport, a simple protocol design pattern would be to write a SASL profile for netconf for use in conjunction with TLS. That's a rather simple project (a couple pages) and I'd be glad to assist if needed.
Cullen Jennings Former IESG member
No Objection
No Objection
()
Unknown
David Ward Former IESG member
No Objection
No Objection
()
Unknown
Jari Arkko Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Jon Peterson Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Magnus Westerlund Former IESG member
No Objection
No Objection
()
Unknown
Mark Townsley Former IESG member
No Objection
No Objection
()
Unknown
Pasi Eronen Former IESG member
No Objection
No Objection
(2009-03-12)
Unknown
Couple of minor comments/suggestions: Section 4 should explain what "third party authentication" means, since it's not obvious from the context, and the term is not used in any of the listed references either. To me, references RFC4642 and and RFC5277 don't look normative, so they probably should be in the Informative References section.
Ron Bonica Former IESG member
No Objection
No Objection
()
Unknown
Ross Callon Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Tim Polk Former IESG member
(was No Record, Discuss)
No Objection
No Objection
()
Unknown