Devs,
I'm soliciting input from potential reviewers of upcoming
gerrit changes for RFC 9347 (AGGFRAG aka IPTFS) support. This
standard is an enhancement to ipsec that hides information
from traffic analysis.
My question is mainly about how to structure the commits with
respect to gerrit submissions: three separate gerrit submissions,
or three commits in one gerrit submission.
The three components are:
1. Changes to vnet/ipsec to support IPTFS, consisting of:
a. registration/callback mechanism by which a TFS plugin
can register its entry points
b. updates to the ipsec api to support TFS parameters
c. updates to SA addition and format to call into the TFS plugin
d. updates to esp encode/decode related to the additional
next-protocol value
This commit will be able to stand alone and, absent the
iptfs plugin, yield ipsec behavior unchanged from before.
2. A new iptfs plugin, which implements all of the timing,
encoding, and decoding for the RFC 9347 format.
3. Unit tests that exercise the TFS-specific parts of the API
and the encoding/decoding path of TFS.
Some of the unit tests are fine-grained and probably not needed for
everyday CI. I'm open to pointers on how to designate some test
functions as "optional" so they won't be added to the default CI runs.
thanks,
~!paul
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#27127): https://lists.fd.io/g/vpp-dev/message/27127
Mute This Topic: https://lists.fd.io/mt/120646438/21656
Group Owner: [email protected]
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
