IESG review: Clarify RFC 2119 qualifiers in NSDB doc

Sean Turner says:
> s2.7: The FsnUuid is a required attribute - REQUIRED?
>
> s2.7/s2.8 Annotations/Descriptions: r/optional/OPTIONAL? X2

> s4.2.1: r/describes the required/describes the REQUIRED ?

> s5.1.5: r/must not/MUST NOT

Section 2.7 defines a conceptual FSN record, not wire protocol
requirements.  Thus in my opinion, RFC 2119 qualifiers are not
appropriate in this section.  To reduce confusion, I'm removing
the lower case "required" and "optional" language.

Also, we have, for example:

"An FSN record may also contain:

   Annotations:  optional name/value pairs"

We don't need both "may contain" and "optional".

Section 4.2.1 describes both required and optional attributes, so
the use of "required" here is not helpful.
IESG comment: Add concept of NSDB client in section 2

Sean Turner says:
> Is an NSDB client the same as a file-access client?  Ah now I
> see NSDB client is defined later in s5 - shouldn't it be listed in s2?
> Is an NSDB client just an administrator or a fileserver based on the
> users of the two sub-protocols in s5 t seems like it is?

And:

> So do I have it right that the protocols described in this document
> are only used by fileservers and admins and that a file-access client
> never needs to implement LDAP?
IESG review: Correct type in section 4.1 of NSDB doc

Sean Turner says:
> s4.1: r/NSBD/NSDB
IESG review: Clarify language in section 5 of NSDB doc

Sean Turner says:
> s5: There's three sub-sections in s5.  Is the following just a typo?
>
>  The NSDB sub-protocols are defined in the next two sub-sections.

It's not a typo, but we can be more clear here.
IESG review: Clarify meaning of "validity and consistency" (NSDB doc)

Sean Turner says:
> s5.1.1: When you say validity and consistency are talking about
> validating the schema?:
>
> The NSDB node that receives the request SHOULD check all of the
> attributes for validity and consistency

In addition to the document not being clear about what checking for
validity and consistency means, I don't see how not checking would be
an impedance to interoperability (ie, is an RFC 2119 qualifier like
SHOULD really appropriate here?).  In my opinion such validation
seems like an implementation quality issue, not an interoperability
issue.

In addition, the document ought to discuss how inconsistent or
invalid attribute values should be reported to LDAP clients, but
it does not.
IESG review: Correct usage of Unicode terminology in NSDB doc

Pete Resnick says:
> 2.8.1.2:
>
>   ...any non-ASCII UTF-8 code points and any URI-
>   reserved characters, such as the slash ("/") character, contained in
>   a component4 element MUST be represented by URI percent encoding.
>
> The phrase "non-ASCII UTF-8 code points" isn't correct. Change it to
> "non-ASCII characters". It's closer to right.
IESG review: Don't define encoding of "server" field in NSDB doc

Pete Resnick says:
> 2.8.1.3:
>
>   In its "server" field, the NFSv4 fs_location4 data type contains a
>   list of universal addresses or UTF-8 hostnames.
>
> This is in all likelihood a problem with 5661 as well. What exactly do
> you mean by "UTF-8 hostname"? Do you mean a U-Label as described in IDNA
> (RFC 5890, et. al.), or do you simply mean a US-ASCII hostname in a UTF-8
> string data type? If the former, you're going to have to say more. If the
> later, you should say "US-ASCII hostnames" instead.

The term "UTF-8 hostname" is nonsense, of course.  But this text
describes encoding already defined in section 12.6 of RFC3530bis.
We do not need to describe this again here, so it is replaced.
IESG review: Simplify ABNF describing FedFS annotations

Pete Resnick says:
> 4.2.1.6:
>
> I've never been clear on why 4512 did as much in the way of customized
> ABNF as it did. You could replace all of the ABNF you have in this
> section with:
>
>      ANNOTATION = KEY "=" VALUE
>      KEY = ITEM
>      VALUE = ITEM
>      ITEM = *WSP DQUOTE UTF8-octets DQUOTE *WSP
>
> DQUOTE and WSP are defined in 5234, and UTF8-octets is defined in 3629.