Alper Yegin wrote:
Here is another spin-off thread...
2. With a little bit of work, I think you could eliminate the need for
the PCI and Pana-start messages. Using DHCP for discovery reduces the
need for these messages. In fact, one of the many "optimizations"
described here include carrying EAP directly in these messages,
existence proof that you don't need to provide your own handshake
before
encapsulating EAP.
I couldn't understand how DHCP helps. PCI is needed to let PaC trigger
the
PANA exchange. And the reason for a dedicated PSR is the aforementioned
design choice.
DHCP helps you to discover the PAA. Once you know the PAA, then you can
immediately send it an EAP message as a payload. The fact that the EAP
payload can be carried on your first PANA message effectively proves this.
Once the PaC discovers the PAA via DHCP, it can send a message (PCI) to the
PAA. But that message cannot carry any EAP payload, as EAP must be initiated
by the PAA per RFC 3748.
As for the need for PANA-Start, that goes back to your format re-structuring
suggestion. I'd like to think more about it.
Yes, its the PSR not the PCI. Apologies.
- Mark
Alper
_______________________________________________
Pana mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/pana
