Subject: Re: [pcp] #38: state maintenance: create a general failure model, discussing how to recover from failures

From: "pcp issue tracker" <[email-masked]>
Date: Tue, 08 Mar 2011 16:23:00 -0000

#38: state maintenance: create a general failure model, discussing how to
recover from failures

Comment(by dthaler@…):

 Q1: How do you handle recovery from a host crash?
 A: everything that wants to keep listening renews on a restart.

 Q2: What if both host and PCP server crash/reboot (e.g., power loss)?
 A: should be same as in Q1.

 Q3: How do you handle recovery from a PCP relay crash?  (Clients don't
 know that PCP relay rebooted since no multicast of Epoch=0)
 A: eventually clients will renew and things will be fixed, but it takes a
 while.  NAT-PMP sends a multicast but PCP does not.

 Q4: What if both PCP relay and PCP server crash?

-- 
---------------------------------------+------------------------------------
 Reporter:  Francis.Dupont@…           |       Owner:     
     Type:  enhancement                |      Status:  new
 Priority:  major                      |   Milestone:     
Component:  base                       |     Version:     
 Severity:  -                          |    Keywords:     
---------------------------------------+------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/pcp/trac/ticket/38#comment:1>
pcp <http://tools.ietf.org/pcp/>