Draft: draft-ietf-jsonpath-base

Commentary: Fix a few nits noticed while skimming -06 
 LGTM with the suggested changes .
Paragraph (version A):
This document picks up Stefan Goessner's popular JSONPath proposal
dated 2007-02-21 JSONPath-orig and provides a normative definition
for it.
Paragraph (version B):
's popular JSONPath proposal dated 2007-02-21 JSONPath-orig and
provides a normative definition for it.
Paragraph (version A):
To be valid, strings on the right hand side of the "=~" regex
matching operator need to conform to I-D.draft-bormann-jsonpath-
iregexp.
Paragraph (version B):
To be valid, strings on the right-hand side of the "=~" regex
matching operator need to conform to I-D.draft-ietf-jsonpath-iregexp.
Paragraph (version A):
The syntax of regular expressions in the string-literals on the
right-hand side of "=~" is as defined in I-D.draft-bormann-jsonpath-
iregexp.
Paragraph (version B):
The syntax of regular expressions in the string-literals on the
right-hand side of "=~" is as defined in I-D.draft-ietf-jsonpath-
iregexp.
Paragraph (version A):
A regular-expression test yields true if and only if the value on the
left-hand side of "=~" is a string value and it matches the regular
expression on the right-hand side according to the semantics of I-
D.draft-bormann-jsonpath-iregexp.
Paragraph (version A):
The semantics of regular expressions are as defined in I-D.draft-
bormann-jsonpath-iregexp.
Paragraph (version B):
A regular-expression test yields true if and only if the value on the
left-hand side of "=~" is a string value and it matches the regular
expression on the right-hand side according to the semantics of I-
D.draft-ietf-jsonpath-iregexp.
Paragraph (version B):
The semantics of regular expressions are as defined in I-D.draft-
ietf-jsonpath-iregexp.
Paragraph (version A):
Attacks on availability may attempt to trigger unusually expensive
runtime performance exhibited by certain implementations in certain
cases.  (See RFC8949 for issues in hash-table implementations, and I-
D.draft-bormann-jsonpath-iregexp for performance issues in regular
expression implementations.)  Implementers need to be aware that good
average performance is not sufficient as long as an attacker can
choose to submit specially crafted JSONPath queries or arguments that
trigger surprisingly high, possibly exponential, CPU usage or, for
example via a naive recursive implementation of the descendant
selector, stack overflow.  Implementations need to have appropriate
resource management to mitigate these attacks.
Paragraph (version B):
Attacks on availability may attempt to trigger unusually expensive
runtime performance exhibited by certain implementations in certain
cases.  (See RFC8949 for issues in hash-table implementations, and I-
D.draft-ietf-jsonpath-iregexp for performance issues in regular
expression implementations.)  Implementers need to be aware that good
average performance is not sufficient as long as an attacker can
choose to submit specially crafted JSONPath queries or arguments that
trigger surprisingly high, possibly exponential, CPU usage or, for
example via a naive recursive implementation of the descendant
selector, stack overflow.  Implementations need to have appropriate
resource management to mitigate these attacks.