DTLS-SRTP Handling in SIP Back-to-Back User Agents
draft-ietf-straw-b2bua-dtls-srtp-12
Yes
(Ben Campbell)
No Objection
(Alia Atlas)
(Alvaro Retana)
(Benoît Claise)
(Deborah Brungard)
(Jari Arkko)
(Spencer Dawkins)
(Terry Manderson)
Note: This ballot was opened for revision 08 and is now closed.
Ben Campbell Former IESG member
Yes
Yes
(for -08)
Unknown
Alia Atlas Former IESG member
No Objection
No Objection
(for -09)
Unknown
Alissa Cooper Former IESG member
(was Discuss)
No Objection
No Objection
(2016-04-12)
Unknown
Thanks for handling my DISCUSS points.
Alvaro Retana Former IESG member
No Objection
No Objection
(for -09)
Unknown
Barry Leiba Former IESG member
No Objection
No Objection
(2015-12-02 for -09)
Unknown
I support at least some of Alissa's and Stephen's DISCUSS points.
In particular, I'm not fully in agreement with Alissa on her point 1: We do sometimes (and should) make normative statements about how protocols should work and should be used, even with knowledge that those statements may (will) be ignored. Sometimes it's to keep the protocol tight; sometimes it's to provide a lever ("The IETF has a standard that says that what you're doing is wrong!").
Because of that, Alissa's point 2 is particularly important: We have to stop the general practice of watering down normative statement in protocols as a way of mollifying people who don't like them. If the right thing is to say "MUST do X", we should not say "SHOULD do X" because we know that some implementations don't and won't do X. In particular, here, if there's any value in this, it's necessary to be strict and clear to expose that value.
Benoît Claise Former IESG member
No Objection
No Objection
(for -09)
Unknown
Deborah Brungard Former IESG member
No Objection
No Objection
(for -09)
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
(for -09)
Unknown
Joel Jaeggli Former IESG member
No Objection
No Objection
(2015-12-02 for -09)
Unknown
Dan Romascanu performed the opsdir review
Kathleen Moriarty Former IESG member
(was No Record, Yes)
No Objection
No Objection
(2015-12-01 for -09)
Unknown
I like the idea of documenting the methods used for MiTM to provide ways to avoid that in practice, but support Alyssa'a discuss points to make this point more clear (purpose of this documentation) and her concerns about what happens in actual implementations. I'd like to hear more on whether this should be standards track or informational as well and will follow along with her discuss thread.
Spencer Dawkins Former IESG member
No Objection
No Objection
(for -09)
Unknown
Stephen Farrell Former IESG member
(was Discuss)
No Objection
No Objection
(2016-03-01 for -10)
Unknown
Thanks for addressing my discuss points. You still have a reference to 3.1.1 in section 5.1.2, which I guess should now be a reference to 5.1.1. I didn't check if there are any other similar internal references that need fixing.
Terry Manderson Former IESG member
No Objection
No Objection
(for -09)
Unknown