Doug
I mentioned my wish for the I-D to have a definition of the types used
and promptly noticed something along those lines in another I-D, which I
append below. It comes from an Informational Model and so does not
specify encoding, which this I-D would need, but I like the terms used
and the descriptions as far as they go. This I-D would only need a
subset.
Tom Petch
=========================================
int A type representing signed or unsigned integer numbers.
This information model does not define a precision nor
does it make a distinction between signed and unsigned
number ranges. This type is also used to represent
enumerations.
boolean A type representing a boolean value.
string A type representing a human-readable string consisting of
a (possibly restricted) subset of Unicode and ISO/IEC
10646 [ISO.10646] characters.
datetime A type representing a date and time using the Gregorian
calendar. The datetime format MUST conform to RFC 3339
[RFC3339].
uuid A type representing Universally Unique IDentifier (UUID(
as defined in RFC 4122 [RFC4122]. The UUID values are
expected to be unique within an installation of a large-
scale measurement system.
uri A type representing a Uniform Resource Identifier as
defined in STD 66 [RFC3986].
ip-address A type representing an IP address. This type supports
both IPv4 and IPv6 addresses.
counter A non-negative integer that monotonically increases.
Counters may have discontinuities and they are not
expected to persist across restarts.
credentials An opaque type representing credentials needed by a
cryptographic mechanism to secure communication. Data
models must expand this opaque type as needed and
required by the security protocols utilized.
data An opaque type representing data obtained from
measurements.
Names of objects are generally assumed to be unique within an
implementation.
----- Original Message -----
From: "Alan DeKok" <[email protected]>
To: "Douglas Gash (dcmgash)" <[email protected]>
Cc: <[email protected]>; <[email protected]>
Sent: Wednesday, May 17, 2017 3:54 PM
Subject: Re: [OPSAWG] draft-ietf-opsawg-tacacs-06 Contributions, Status
and Plans
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
