[Swan-dev] encrypted informational message when in state R1?

[Antony Antony]

can you push this change to a branch first? and do test run? 

Also if you push to a branch do you mind if add some changes to it? 
How are you going to deal with all the macros we have  IS_* ?

-antony

On Tue, Mar 03, 2015 at 01:37:47PM -0500, Andrew Cagney wrote:
> On 18 February 2015 at 20:25, Paul Wouters <paul at nohats.ca> wrote:
> > On Wed, 18 Feb 2015, D. Hugh Redelmeier wrote:
> 
> > STATE_PARENT_R2 also suports informationals, like liveness probes.
> >
> >> I continue to think that these are terrible state names.
> >
> >
> > Everybody agrees.
> >
> >> STATE_PARENT_R1 => STATE_INIT_R
> >> STATE_PARENT_R2 => STATE_AUTH_R
> 
> > That would work, andso would:
> >
> > STATE_PARENT_I1 => STATE_INIT_I
> > STATE_PARENT_I2 => STATE_AUTH_I
> >
> > I'm not sure what STATE_PARENT_I3 should be called.
> 
> STATE_V2_ESTABLISHED.
> 
> I'll push the following rename:
> 
> STATE_PARENT_R1 -> STATE_V2_INIT_R
> STATE_PARENT_I1 -> STATE_V2_INIT_I
> STATE_PARENT_I2 -> STATE_V2_AUTH_I
> STATE_PARENT_I3 -> STATE_V2_ESTABLISHED
> 
> I'm going to leave STATE_PARENT_R2 unchanged for reasons that deserve
> a new thread.
> (btw the corresponding state_names table is out-of-date, I'll fix that).
> 
> Andrew
> _______________________________________________
> Swan-dev mailing list
> Swan-dev at lists.libreswan.org
> https://lists.libreswan.org/mailman/listinfo/swan-dev
>