[IPsec] Getting there... 5 more issues

Yoav Nir writes: > Issue #168 - Identifier field in the EAP payload > > No discussion so far. I would just remove that sentence, because EAP > is specified in its own RFC, and we don't need to really specify > what goes in any of the fields. I would

Re: [IPsec] Getting there... 5 more issues

All of the proposed courses of action seem fine to me. --Paul Hoffman, Director --VPN Consortium ___ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec

[IPsec] Getting there... 5 more issues

Hi all. Wer'e down to single digits with the open issues on IKEv2bis. Here are 5 more. Issue #168 - Identifier field in the EAP payload 3.16: the text here, "...this field MAY be set to any value" implies that the Identifier field can be constant,