Dear Benjamin,
I found that following sections may be the proper place to restrict the 1-to-1
mapping. I think we can have restrictions in section 3.1 only or in
3.1&4.2.1&4.2.5. I've not decided which one is better and hope to have others'
suggestions.
1. In section 3.1 Organization Identifier
Dear Benjamin,
I re-read the two paragraphs again and again. And I think I have the thought in
mind that "service message" may be the key words to make you confused.
In section 4.2, "the client MUST be notified using a service message", this
"service message" has a relatively broad meaning, that
Dear Linlin,
On Wed, Oct 31, 2018 at 02:19:45PM +0800, Linlin Zhou wrote:
> Dear Benjamin,
> Thanks for your input. We believe that relationship between an object and an
> organization should be 1-to-1, one organization ID with just one role.
> 1-to-many is an exception for the organization exte
Sorry for correction. The client can set "clientLinkProhibited" but can not
alter "ok". "ok" should be removed by the server.
Linlin Zhou
From: Linlin Zhou
Date: 2018-10-31 11:37
To: Benjamin Kaduk
CC: Eric Rescorla; draft-ietf-regext-org; regext-chairs; Pieter Vandepitte;
iesg; regext
Subje
