>>>>> "Josh" == Josh Howlett <[email protected]> writes:
>>
>> What Jim is saying is that RADIUS provides a reliable service to
>> EAP. That is, RADIUS is responsible for making sure that messages
>> reliably get from the NAS to the EAP server and back. I believe
>> he's approximately right and that the differences are not things
>> we need to worry abuot.
Josh> Right.
Josh> These aren't assumptions of the architecture, although I
Josh> believe it will end up being true in practice.
>>
>> I actually believe these are carefully crafted aspects of the
>> architecture.
Josh> Really? Neither RADIUS nor some potential host protocols use
Josh> reliable transports. It's obviously possible to use transports
Josh> that are reliable, but we don't constrain the architecture to
Josh> require the use of those. It's true that the GSS acceptor is
Josh> hidden from this by the API abstraction, but it's possible for
Josh> a GSS operation to fail because a token is lost by the
Josh> unreliable transport.
No, if RADIUS or the host protocol lose a message they are responsible
for retransmitting.
It's possible that a connection can fail because retransmissions fail
and RADIUS or the host protocol returns a protocol error.
Josh> Josh.
Josh> JANET(UK) is a trading name of The JNT Association, a company
Josh> limited by guarantee which is registered in England under
Josh> No. 2881024 and whose Registered Office is at Lumen House,
Josh> Library Avenue, Harwell Oxford, Didcot, Oxfordshire. OX11 0SG
_______________________________________________
abfab mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/abfab
