Ballot for charter-ietf-sframe
Yes
No Objection
Note: This ballot was opened for revision 00-02 and is now closed.
Ballot question: "Do we approve of this charter?"
Magnus and Erik had some concerns with the charter text that they chose not to BLOCK on, but I'm still looking into how to get them resolved just to be as thorough as possible.
It's not clear to me what exactly this last piece of text means: Input to the WG Proposals already existing relating to this charter proposal: https://datatracker.ietf.org/doc/html/draft-omara-sframe-00 It is just a pointer to existing work? Is it a statement that the WG should use (or maybe will use) this document as the base for discussion? Given that the document was the source of the discussion that led to this WG, I assume it's the latter. Please be clear.
I wonder whether this should be chartered in the Sec Area with an ART AD (Murray) set as responsible AD. I also think the last bit: Input to the WG Proposals already existing relating to this charter proposal: https://datatracker.ietf.org/doc/html/draft-omara-sframe-00 ...shouldn't be in the final charter text (it was fine to have it there during review). The draft is referenced in the milestone, and that should cover it.
This working group, however, will not specify the signaling required to configure SFrame encryption. In particular, considerations related to SIP or SDP are out of scope. This is because SFrame is intended to be applied as an additional layer on top of the base levels of protection that these protocols provide. [...] This text reads like it is saying that SIP and SDP provide "base levels of protection", which is not necessarily the case in the context of the protection that SFrame provides.