RE: Review of Management Authorization -00 document

["David B. Nelson" <d.b.nelson@comcast.net>]

> What attributes go along with that?  User-Password?  CHAP-Password?

For the Access-Request, it is usually User-Name and User-Password, although
I suppose CHAP-Password is possible.

> > The Management-Transport-Protocol attribute could certainly be 
> > used in conjunction with the NAS-Port-Type attribute of Virtual 
> > (5), as is the current practice.
> 
> OK.  It would make sense to say that in the document.

That can easily be added, as explanatory material. 

> Is there a situation where NAS-Port-Type = Async (0) would make 
> much sense along with a Management-Transport-Protocol, attribute?

No.  That should also be called out in the document.

> > In that sense, the usage of the Management-Transport-Protocol attribute
> > usage as a hint is as important, or more important, than the
> > provisioning usage.
> 
> OK.  It might be useful to have an example or two to make this clear.

OK.

> The scenario here is to provide more info in the case where
> NAS-Port-Type=virtual, and Server-Type=NAS-Prompt, right?  I guess
> there are scenarios where this could make a difference to the RADIUS
> server (e.g. router mistakenly enables an insecure management protocol
> and RADIUS server wants to make sure it that only secure protocols are
> authorized).

Exactly.




--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>