Skip to main content

IP Security Maintenance and Extensions
charter-ietf-ipsecme-13

Yes

(Benjamin Kaduk)

No Objection

Roman Danyliw
(Adam Roach)
(Alissa Cooper)
(Alvaro Retana)
(Deborah Brungard)
(Magnus Westerlund)
(Martin Vigoureux)
(Suresh Krishnan)

Note: This ballot was opened for revision 12-00 and is now closed.

Ballot question: "Is this charter ready for external review?"

Roman Danyliw
No Objection
Éric Vyncke
No Objection
Comment (2019-12-19 for -12-00) Sent
While I have no objection to the charter, I would suggest to coordinate to compressed ESP/IKEv2 of this charter with the compression work done in LPWAN (mainly or only for the non-encrypted parts).
Benjamin Kaduk Former IESG member
Yes
Yes (for -12-00) Not sent

                            
Adam Roach Former IESG member
No Objection
No Objection (for -12-00) Not sent

                            
Alissa Cooper Former IESG member
No Objection
No Objection (for -12-00) Not sent

                            
Alvaro Retana Former IESG member
No Objection
No Objection (for -12-00) Not sent

                            
Barry Leiba Former IESG member
No Objection
No Objection (2019-12-15 for -12-00) Sent
Some wordsmithing on the two new paragraphs, mostly correcting grammar errors and awkward wording:

NEW
RFC8229, published in 2017, specifies how to encapsulate           
IKEv2 and ESP traffic in TCP.  Implementation experience has                    
revealed that not all situations are covered in RFC8229, and that may               
lead to interoperability problems or to suboptimal performance. The WG              
will provide a document to give implementors more guidance about how to use               
reliable stream transport in IKEv2 and clarify some issues that have been            
discovered. A possible starting point is draft-smyslov-ipsecme-tcp-guidelines.       
                                                                                    
The demand for Traffic Flow Confidentiality has been increasing in the user         
community, but the current method defined in RFC4303 (adding null           
padding to each ESP payload) is very inefficient in its use of network             
resources. The working group will develop an alternative TFC solution that          
uses network resources more efficiently.
END
Deborah Brungard Former IESG member
No Objection
No Objection (for -12-00) Not sent

                            
Magnus Westerlund Former IESG member
No Objection
No Objection (for -12-00) Not sent

                            
Martin Vigoureux Former IESG member
No Objection
No Objection (for -12-00) Not sent

                            
Suresh Krishnan Former IESG member
No Objection
No Objection (for -12-00) Not sent