Draft: draft-ietf-gnap-resource-servers

Commentary: Expands the definition of the resource set registration protocol , used by an RS to declare a resource set to an AS at runtime and receive a reference identifier for that resource set to hand to a client . 
 : heavycheckmark : Deploy Preview for gnap - resource - servers - editors - draft ready ! : hammer : Explore the source changes : : mag : Inspect the deploy log : : sunglasses : Browse the preview : 
 Registering a Resource Handle :  's note : It 's not an exact match here because the " resource_handle " returned now represents a collection of objects instead of a single one . Perhaps we should let this return a list of strings instead ? Or use a different syntax than the resource request ? Also , this borrows heavily from UMA 2 's " distributed authorization " model and , like UMA , might be better suited to an extension than the core protocol
Paragraph (version A):
If the RS needs to, it can post a set of resources as described in
the Resource Access Rights section of I-D.ietf-gnap-core-protocol to
the AS's resource registration endpoint.
Paragraph (version A):
The AS responds with a handle appropriate to represent the resources
list that the RS presented.
Paragraph (version A):
The RS MAY make this handle available as part of a discovery response
as described in I-D.ietf-gnap-core-protocol or as documentation to
developers.
Paragraph (version B):
If the RS needs to, it can post a set of resources as described in
the Resource Access Rights section of I-D.ietf-gnap-core-protocol to
the AS's resource registration endpoint along with information about
what the RS will need to validate the request.
Paragraph (version B):
REQUIRED.  The list of access rights associated with the request
in the format described in the "Resource Access Rights" section of
I-D.ietf-gnap-core-protocol.
Paragraph (version B):
REQUIRED.  The identification used to authenticate the resource
server making this call, either by value or by reference as
described in authentication.
Paragraph (version B):
OPTIONAL.  The token format required to access the identified
resource.  If the field is omitted, the token format is at the
discretion of the AS.  If the AS does not support the requested
token format, the AS MUST return an error to the RS.
Paragraph (version B):
OPTIONAL.  If present and set to "true", the RS expects to make a
token introspection request as described in introspection.  If
absent or set to "false", the RS does not anticipate needing to
make an introspection request for tokens relating to this resource
set.
Paragraph (version B):
The AS responds with a reference appropriate to represent the
resources list that the RS presented in its request as well as any
additional information the RS might need in future requests.
Paragraph (version B):
REQUIRED.  A single string representing the list of resources
registered in the request.  The RS MAY make this handle available
to a client instance as part of a discovery response as described
in I-D.ietf-gnap-core-protocol or as documentation to client
software developers.
Paragraph (version B):
OPTIONAL.  An instance identifier that the RS can use to refer to
itself in future calls to the AS, in lieu of sending its key by
value.
Paragraph (version B):
OPTIONAL.  The introspection endpoint of this AS, used to allow
the RS to perform token introspection.