[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Review of Management Authorization -00 document
OK. What I'm proposing in the -01 version is:
What does Web-based mean? Is it something other than HTTP?
I don't think we want to be specifying the "real" transport layer, e.g.
UDP, SCTP, etc. What we need to specify there is the "secure transport"
(which doesn't exactly fit into the classical ISO 7-layer model), e.g.
What I'm proposing for the -01 version is:
What does default mean? Insecure transport (e.g. TCP/UDP)?
Does SNMP over Default mean SNMP over UDP or TCP?
With respect to TLS/DTLS, what mode is intended? Mutual auth with certs?
Server-only auth? TLS-PSK?
What does it mean if multiple Management-Policy-Id attributes are
How are the policies merged? If this is implementation-specific, isn't
the result undefined?
Proposed text for the -01 version:
No precedence relationship is defined for multiple occurrences of the
Management-Policy-Id attribute. NAS behavior in such cases is not
predictable. Therefore, two or more occurrences of this attribute SHOULD
NOT be included in a single service provisioning message, such as
Access-Accept or CoA.
The content of the Management-Policy-Id attribute is expected to be the
of a management access policy of local significance to the NAS, within a
flat namespace of significance to the NAS. Overloading or subdividing
flat name with multi-part specifiers (e.g. Access=remote, Level=7) is
to lead to poor multi-vendor interoperability and SHOULD NOT be utilized.
If a simple flat policy name is not sufficient to the anticipated use
it is RECOMMEDNED that a Vendor Specific Attribute be used instead, rather
than overloading the semantics of Management-Policy-Id.
This looks OK.
to unsubscribe send a message to email@example.com with
the word 'unsubscribe' in a single line as the message text body.