Re: [pcp] PCP Failure Scenarios - Re: draft-wing-pcp-proposed-packet-format-00

[Francis Dupont <[e-mail]>]

 In your previous mail you wrote:

   > "Static entries" mentioned above apply also for PCP-instructed ones.
   
=> I agree with Mohamed, here the term static is the strict opposite
of the dynamic one, and port forwarding entries are 'static' even they
can get a lifetime.

   I disagree according to
   http://datatracker.ietf.org/doc/draft-ietf-behave-v6v4-framework/
   
   "State:  "State" refers to dynamic information that is stored in a
         network element.  For example, if two systems are communicating
         using a TCP connection, each stores information about the
         connection, which is called "connection state".  In this context,
         the term refers to dynamic correlations between IP addresses on
         either side of a translator, or {IP address, transport protocol,
         transport port number} tuples on either side of the translator.
         Of stateful algorithms, there are at least two major flavors
         depending on the kind of state they maintain:"
   
   PCP entries are clearly dynamic state created by protocol exchange

=> but not 'dynamic state' in the behave meaning where everything not
in the forwarding plane is qualified as 'static'.

Regards

[e-mail]

PS: I like the security point of view because it makes very clear
port forwarding entries and behave dynamic states are two very different
things.