I talked to Jim Gould about this feedback yesterday. We didn't reach a 
conclusion, so I'm throwing this to the list to see if anyone else cares and 
might have a preference for a change proposal.

In Section 2.1 there's a description of the "custom" operation and how it uses 
an attribute named "op", but I can't find anything that describes the possible 
values for the attribute.

Section 2.2 talks about "Who" values, and it describes three different forms 
that MAY be used. The document says that "the possible set of Who values is up 
to server policy", and the Schema data type for the value is a 
length-restricted normalizedString. That all means that there's really no way 
to determine if a value is an Identifier, a Name, a Role or anything else (if 
it matters) and there's no way for a client to determine which is being used by 
a server. There's also no text I can find that explains how the value for this 
field is set.

My concern is that these unspecified bits might make it more difficult for 
clients and servers to develop interoperable implementations. Does it matter?

Scott

> -----Original Message-----
> From: regext [mailto:regext-boun...@ietf.org] On Behalf Of James Galvin
> Sent: Friday, August 18, 2017 9:57 AM
> To: Registration Protocols Extensions <regext@ietf.org>
> Subject: [EXTERNAL] [regext] review draft-ietf-regext-change-poll
>
> As the working group discussed at the last IETF meeting, the authors
> believe the following document is stable and ready for final review.
>
> https://datatracker.ietf.org/doc/draft-ietf-regext-change-poll/
>
> The chairs would like to ask for at least 3 people (other than the
> authors) to indicate they have read this document and agree that it is
> ready for publication.
>
> Please reply to this message if you have any comments or questions, or if
> you agree the document is ready for publication.
>
> Thanks,
>
> Antoin and Jim
>
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext

_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

Reply via email to