[pcp] #62: Client-driven or server-driven auth retransmissions

["pcp issue tracker" <[e-mail]>]

#62: Client-driven or server-driven auth retransmissions

 Reported by Alper, Margaret, etc.

 PCP is currently a client-initiated request/response protocol with one-way
 notification.   EAP is often server-driven retransmissions.   This
 question centers around either having server-driven retransmissions or how
 to make EAP use client-driven retransmissions.

 Raw notes from Simon from October 2012 webex interim meeting:

 Slide 12: PANA Model
 - Requires server-initiated reauthentication.
 - Optionally to support liveness detection.
 - Tightly coupled.
 Alper: Retransmissions are driven by EAP. Not PANA's choice.
 Sam: No. You can design an EAP lower-layer where retransmissions are done
 by the client.
 Rafa Marin-Lopez: (did not understand)
 Sam: You can remove the reliability in EAP if we choose. Say PCP or PANA
 is responsible for retransmits.
 Rafa: You need retransmission.
 Sam: Yes but it can be done at either layer: EAP or elsewhere.
 Margaret: If we move it to the PCP layer, we can choose to do only
 client-initiated retransmission. Retransmissions don't need to be
 server-generated.
 Alper: You are reinventing ... (did not understand)
 Margaret: Send a description of how PANA can do only client-initiated
 retransmissions.

-- 
----------------------------+---------------------------------------------
 Reporter:  alper.yegin@…   |      Owner:  draft-ietf-pcp-authentication@…
     Type:  defect          |     Status:  new
 Priority:  major           |  Milestone:
Component:  authentication  |    Version:
 Severity:  -               |   Keywords:
----------------------------+---------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/pcp/trac/ticket/62>
pcp <http://tools.ietf.org/pcp/>