Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) Management
RFC 5607
Note: This ballot was opened for revision 07 and is now closed.
(Dan Romascanu) Yes
(Jari Arkko) (was Discuss) No Objection
Comment (2009-01-29)
No email
send info
send info
I find it unfortunate that the document does not define an attribute to distinguish SSH and other forms of command line protocols from each other. Or has such an attribute already been defined somewhere else? The document is silent on exactly how authentication from, say, SCP or is actually represented in RADIUS. Perhaps that is obvious? (But aren't there non-trivial details, depending on what kind of challenge or password mechanism is in use?) Or is authorize-only used? I support Pasi's Discuss.
(Ron Bonica) No Objection
(Ross Callon) No Objection
(Lisa Dusseault) No Objection
(Lars Eggert) No Objection
Comment (2009-01-27 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
send info
> | | |SHLD| MUST| | > Attribute Name Value Type |MUST| MAY | NOT| NOT|Encr| Don't abbreviate RC2119 terms: s/SHLD/SHOULD/.