Subject: [Pana] pana-pana Issue219: AD comments on Section 3

From: Yoshihiro Ohba <[email-masked]>
Date: Tue, 27 Dec 2005 11:51:46 -0500

>   o  Access phase: After a successful authentication and authorization
>      the host gains access to the network and can send and receive IP
>      data traffic through the EP(s).  At any time during this phase,
>      the PaC and PAA may optionally ping each other to test liveness
of
>      the PANA session on each end.
>  
>
So, is this a requirement that the PaC and PAA allow ICMP before the 
authentication is complete?

>   o  Re-authentication phase: During the access phase, the PAA must
>      initiate re-authentication before the PANA session lifetime
>      expires.  EAP is carried by PANA to perform authentication.  This
>      phase may be optionally triggered by both the PaC and the PAA
>      without any respect to the session lifetime.  The session moves
to
>      this phase from the access phase, and returns back there upon
>      successful re-authentication.
>
>   o  Termination phase: The PaC or PAA may choose to discontinue the
>      access service at any time.  An explicit disconnect message can
be
>      sent by either end.  If either the PaC or the PAA disconnects
>      without engaging in termination messaging, it is expected that
>      either the expiration of a finite session lifetime or failed
>      liveness tests would clean up the session at the other end.
>
>
>     PaC  PAA    Message
>   -----------------------------------------------------
>   // Discovery and handshake phase
>      ----->     PANA-PAA-Discover
>      <-----     PANA-Start-Request
>      ----->     PANA-Start-Answer
>
>   // Authentication and authorization phase
>      <-----     PANA-Auth-Request /* EAP Request */
>      ----->     PANA-Auth-Answer
>      ----->     PANA-Auth-Request /* EAP Response */
>      <-----     PANA-Auth-Answer
>      <-----     PANA-Bind-Request /* EAP Success */
>      ----->     PANA-Bind-Answer
>
>   // Access phase (IP data traffic allowed)
>      <-----     PANA-Ping-Request
>      ----->     PANA-Ping-Answer
>  
>
OK, I just learned that PANA has its own ping. If you were referring to 
PANA-ping earlier, please specify, I obviously thought this was ICMP 
echo request/reply.

>   // Termination phase
>      ----->     PANA-Termination-Request
>      <-----     PANA-Termination-Answer
>
>           Figure 1: Illustration of PANA messages in a session
>
>   Note that depending on the environment and deployment the protocol
>   flow depicted in Figure 1 can be abbreviated.
>  
>
How?

(e.g., ...can be abbreviated by collapsing some messages into one as 
described later in section foo...)

_______________________________________________
Pana mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/pana