[Isms] FW: COMMENT: draft-ietf-isms-radius-usage

> -----Original Message-----
> From: isms-bounces@ietf.org [mailto:isms-bounces@ietf.org] On Behalf Of
> Alexey Melnikov
> Sent: Sunday, May 03, 2009 8:44 AM
> To: iesg@ietf.org
> Cc: draft-ietf-isms-radius-usage@tools.ietf.org; isms-
> chairs@tools.ietf.org
> Subject: [Isms] COMMENT: draft-ietf-isms-radius-usage
> 
> Comment:
> 2.3.  SNMP Service Authorization
> 
>  [...]
> 
>    There are no combinations of RADIUS attributes that denote the
>    equivalent of SNMP noAuthNoPriv access, as RADIUS always involves the
>    authentication of a user (i.e. a principal) as a prerequisite for
>    authorization.  RADIUS can be used to to provide an "Authorize-Only"
> 
> Extra "to".
> 
>    service, but only when the request contains a "cookie" from a
>    previous successful authentication with the same RADIUS server (i.e.
>    the RADIUS State Attribute).
> 
> 
> 5.  Security Considerations
> 
>  [...]
> 
>    The Message-Authenticator (80) attribute [RFC3579] SHOULD be used
>    with RADIUS messages that are described in this memo.
> 
> Some explanation of why would be helpful here.
> 
> _______________________________________________
> Isms mailing list
> Isms@ietf.org
> https://www.ietf.org/mailman/listinfo/isms