| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This adds support for early versions of the draft that eventually
resulted in RFC 3947.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Since a proposal_t object is created for each transform contained in the
proposal payload, it does not work to simply remove the last proposal_t
object added to the list (there may be several other extracted from the
previous proposal payload).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
payload length
|
|
|
|
|
| |
According to RFC 5996 3.3.1, we MUST reuse the proposal number of
the selected proposal in the SA payload reply.
|
| |
|
|
|