[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IKEv2 status
Folks,
as you've seen, Charlie has posted a new draft. As a result, the following
issues in the Issue Tracker (https://roundup.machshav.com/ipsec) have been
marked as closed:
2: (Use different concatenation character)
3: (DH group negotiation)
4: (Remove duplicate text)
5: (ECN text in USE_TRANSPORT_MODE)
6: (Problems with changed encoding between IKE and IKEv2)
8: (IPcomp editorial suggestions)
9: (Identity protection)
11: (Nonce length)
12: (Payload 14 reuse from IKE)
13: (Clarification on Reserved Exchanged Types)
14: (Clarification on sending responses)
15: (Clarification on retransmission text)
17: (Traffic Selector types definition/allocation fix)
52: (Remove group from Appendix B.5)
53: (Key length attribute)
54: (Two reserved ranges for NOTIFY status numbers --- why ?)
56: (IKEv2 SCTP support)
58: (Remove section 2.24 (ECN support))
Those that submitted the issues, please verify that they have been addressed
appropriately (we believe they have).
The remaining issues are still open:
1: (Rekeyed SA use)
7: (Fragmentation negotiation (before/after IPsec processing)
10: (NAT Traversal support)
16: (Negotiate ToS in IKEv2)
41: (NAT traversal missing text)
55: (ICMP fields as selectors ?)
64: (Use the SPI of SA being rekeyed in a notify payload during rekey)
65: (EAP)
We are working on closing some of these in the next few days (1, 10, 41, 55,
64, 65). Issues 7 and 16 require discussion along with 2401bis; if that
discussion can be concluded quickly, then any necessary changes will be added
to the IKEv2 draft; otherwise, the draft will remain as is and will be amended
by additional RFCs as needed.
-Angelos