[strongSwan-dev] does strongswan android client support sending NON_FIRST_FRAGMENTS_ALSO in notify payload

[Ravi Kanth Vanapalli]

Dear All,

Does Strongswan Android market app support sending NON_FIRST_FRAGMENTS_ALSO
in the first IKE_AUTH message to the gateway.

Also I have a query regarding this attribute NON_FIRST_FRAGMENTS_ALSO

RFC  5996 reads below
"
 The NON_FIRST_FRAGMENTS_ALSO notification is used for fragmentation control.
Both parties need to agree to sending non-first fragments before either
party does so. It is enabled only if NON_FIRST_FRAGMENTS_ALSO notification
is included in both the request proposing an SA and the response accepting
it. If the responder does not want to send or receive non-first fragments,
it only omits NON_FIRST_FRAGMENTS_ALSO notificationfrom its response, but
does not reject the whole Child SA creation."
"

Questions
1) Does this mean to support IKE layer fragmentation UE needs to send
NON_FIRST_FRAGMENTS_ALSO in the first IKE_AUTH message ?
2) Does the statement mean, only once initiator and responder agree on IKE
layer fragmentation with the use of this notification payload, does
fragmented IKE layer exchanges take place ?

Kindly help clarify this query.
-- 
Regards,
RaviKanth VN Vanapalli
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.strongswan.org/pipermail/dev/attachments/20150107/60ca223d/attachment.html>