I realized after I sent this that my suggested text has a couple of
errors in t.
On 4/4/18 2:22 PM, Adam Roach wrote:
Fixing this should be pretty easy; the document simply needs text added that
describes the JSON structure explicitly, with clear indications of how values
are to be encoded. For example, the preceding text I quote becomes:
A SLURM file consists of a single JSON object containing the following
members:
o A "slurmVersion" member that MUST be set to 1, encoded as a number
o A "slurmTarget" member (Section 3.3) If more than one target line is
present, all targets MUST be acceptable to the RP. The "slurmTarget"
member is encoded as an array of zero or more objects. Each object in the
array contains exactly one member. In this version of SLURM, the member
may be named either:
I copied the "target line" language over without reading it carefully. I
don't think "line" makes sense here. Perhaps:
o A "slurmTarget" member (Section 3.3). The "slurmTarget" member is
encoded
as an array of zero or more objects, each representing a target. If
more than one target is present, all targets MUST be acceptable
to the
RP. Each object in the array contains exactly one member. In this
version of SLURM, the member may be named either:
* "asn", in which case it contains an ASN, or
This should should say "...an ASN, encoded as a number."
* "hostname", in which case it contains a Fully Qualified Domain
Name (FQDN).
o A "validationOutputFilters" member (Section 3.4), whose value is an
object. The object MUST contain exactly two members:
* A "prefixFilters" member, whose value is described in
Section 3.4.1
* A "bgpsecFilters" member, whose value is described in
Section 3.4.2
o A "locallyAddedAssertions" member (Section 3.5), whose value is an
object. The object MUST contain exactly two members:
* A "prefixAssertions" member, whose value is described in
Section 3.5.1
* A "bgpsecAssertions" member, whose value is described in
Section 3.5.2
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
