RE: RADEXT Issue 255 (NAS Management Authorization)

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

Glen Zorn writes...

> It's not at all clear to me that "Web services" qualifies as any type
> of protocol at all.

I wasn't proposing that we formally characterize embedded web management, as
it's deployed in many NASes today, as "web services".  There is something of
a nomenclature issue here, though, specifically how best to "name" the form
of management that uses an embedded web server to serve up web pages (HTML
content) over the HTTP application-layer protocol to a web browser
application?  The issue is not that HTML/HTTP fails describe the protocol,
but rather that other things besides management can be served in this
fashion. It's my understanding that lots of things are "tunneled" in HTTP
these days, firewall avoidance being but one reason.

What's important, at the end of the day, is that there be an unambiguous
binding between the values of this attribute and the framed (i.e.
non-textual) management mechanisms they represent.

> I think that the Attribute needs to be renamed -- maybe 
> "Framed-Management-Method"?

I have no objection to that choice of attribute name, but I'm wondering if
it really addresses the underlying issue.  The issue is to pick one
identifying characteristic of framed management to serve as the "name".  The
application layer protocol seemed a logical choice.

Does anyone else have thoughts to share on this, one way or another?



--
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/>