Bay Networks Radius Manuel d'utilisateur

Network Working Group D. Mitton Request for Comments: 2882 Nortel Networ

exchange, and use the Username field for information about the Mitton Informational [Page 11] RFC 288

This memo is not a complete survey by any means. It is a representative summary of practices that I am aware of at the time of writing. I

12. References [1] Rigney, C., Rubens, A., Simpson, W. and S. Willens, "Remote Authentication Dial In User Service (RADIUS)",

Mitton Informational [Page 15] RFC 2882 Extended RADIUS Practices

Mitton Informational [Page 16]

6.4 Authorization Changes . . . . . . . . . . . . . . . . . . . 11 7. Policy Services . . . . . . . . . . . . . . . . . . . . . . 11 8. Acco

change by vendors without notice. I would appreciate any direct input, preferably first hand, from implementors. 1.2. Presentation Withou

the numeric value (ala VSAs) which would to divide up the attribute value space. This technique has not seen any acceptance by the working g

Now that MS-CHAP RADIUS attributes have been published in RFC 2548 [9] as Microsoft VSA attributes, it will become typical that for NAS clie

4. New Messages A number of new message types have been introduced by various parties over time. The base specification has 6, vendors have a

5.2. Authentication Modes Additional message types have been added to negotiate passcode changes for token card servers. - Next Passcode

attached to the profile. The client should test for this returned value, to prevent normal dial-in users from gaining access via this profile

on a RADIUS environment. Some vendors have build NAS monitoring tools either into their RADIUS servers, either directly or as auxiliary deam