On Tue, Nov 02, 2021 at 12:04:25PM +0900, YASUOKA Masahiko wrote: > ok? > > Clarify that ANY can be used for several parameters of IPsec transform. > > Index: sbin/isakmpd/isakmpd.conf.5 > =================================================================== > RCS file: /cvs/src/sbin/isakmpd/isakmpd.conf.5,v > retrieving revision 1.135 > diff -u -p -r1.135 isakmpd.conf.5 > --- sbin/isakmpd/isakmpd.conf.5 17 Apr 2018 12:13:29 -0000 1.135 > +++ sbin/isakmpd/isakmpd.conf.5 2 Nov 2021 02:57:23 -0000 > @@ -726,7 +726,7 @@ See below. > Parameters for IPsec transform configuration > .Bl -tag -width Ds > .It Em AUTHENTICATION_ALGORITHM > -The optional authentication algorithm in the case of this > +The optional authentication algorithm or ANY in the case of this
hi. i think it would be clearer to add a comma after "algorithm", like you do below after "RFCs". it makes it clearer that only "ANY" relates to "being an ESP transform", and not "the optional authentication algorithm" as well. otherwise ok by me. jmc > being an ESP transform. > .It Em ENCAPSULATION_MODE > The encapsulation mode as given by the RFCs. > @@ -745,7 +745,8 @@ List of lifetimes, each element is a > .Aq Sy Lifetime > section name. > .It Em TRANSFORM_ID > -The transform ID as given by the RFCs. > +The transform ID as given by the RFCs, or ANY to denote that any > +transform proposed will be accepted. > .El > .It Aq Sy IPsec-ID > Parameters for IPsec ID configuration >
