On 13/11/12 16:14, Rafa Marin Lopez wrote: > Hi Sam: > > In such a case, it sounds reasonable. No concern, at least, from my side. I agree.
> > Best regards. > > El 13/11/2012, a las 15:20, Sam Hartman escribió: > >>>>>>> "Gabriel" == Gabriel Lopez <[email protected]> writes: >> >> Gabriel> My concern is about to define RadSec mandatory for those >> Gabriel> institutions willing to deploy abfab. Let's suppose >> Gabriel> eduroam, institution A is requesting authentication to >> Gabriel> institution B, where A is abfab-aware, and B is a tipical >> Gabriel> eduroam member. Let's suppose: >> >> Ah! The IETF rarely if ever specifies what security technology you must >> use or deploy and I'm not proposing doing that in this case. I'm >> proposing that implementations of draft-ietf-abfab-aaa-saml--that is >> software implementing that spec--MUST be capable of using RADSEC. >> Whether you turn on RADSEC is up to whomever deploys the code. >> >> I absolutely agree with you that requiring people to use RADSEC in all >> ABFAB deployments would be inappropriate for the IETF to do. >> _______________________________________________ >> abfab mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/abfab > ------------------------------------------------------- > Rafael Marin Lopez, PhD > Dept. Information and Communications Engineering (DIIC) > Faculty of Computer Science-University of Murcia > 30100 Murcia - Spain > Telf: +34868888501 Fax: +34868884151 e-mail: [email protected] > ------------------------------------------------------- > > > > > _______________________________________________ > abfab mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/abfab _______________________________________________ abfab mailing list [email protected] https://www.ietf.org/mailman/listinfo/abfab
