<?xmlversion="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> <!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.5 (Ruby 3.1.2) -->version='1.0' encoding='utf-8'?> <!DOCTYPE rfc [ <!ENTITY nbsp " "> <!ENTITY zwsp "​"> <!ENTITY nbhy "‑"> <!ENTITY wj "⁠"><!ENTITY SELF "RFC nnnn">]><?rfc tocindent="yes"?> <?rfc strict="yes"?> <?rfc compact="yes"?> <?rfc comments="yes"?> <?rfc inline="yes"?> <?rfc docmapping="yes"?><!-- [rfced] *AD, the following changes were made after the document was approved for publication. Please review and let us know if you approve. https://author-tools.ietf.org/iddiff?url2=draft-ietf-gnap-core-protocol-20 --> <!-- [rfced] Please note that the title of the document has been updated as follows (added "GNAP"). Original: Grant Negotiation and Authorization Protocol Current: Grant Negotiation and Authorization Protocol (GNAP) --> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-gnap-core-protocol-19" number="9635" obsoletes="" updates="" submissionType="IETF" category="std" consensus="true" tocInclude="true" sortRefs="true"symRefs="true">symRefs="true" version="3" xml:lang="en" > <front> <title>Grant Negotiation and AuthorizationProtocol</title>Protocol (GNAP)</title> <seriesInfo name="RFC" value="9635"/> <author initials="J." surname="Richer" fullname="Justin Richer" role="editor"> <organization>Bespoke Engineering</organization> <address> <email>ietf@justin.richer.org</email> <uri>https://bspk.io/</uri> </address> </author> <author initials="F." surname="Imbault" fullname="Fabien Imbault"> <organization>acert.io</organization> <address> <email>fabien.imbault@acert.io</email> <uri>https://acert.io/</uri> </address> </author> <date year="2024"month="March" day="09"/> <area>Security</area> <workgroup>GNAP</workgroup> <keyword>Internet-Draft</keyword>month="September"/> <area>SEC</area> <workgroup>gnap</workgroup> <!-- [rfced] Please insert any keywords (beyond those that appear in the title) for use on https://www.rfc-editor.org/search. --> <keyword>example</keyword> <abstract><?line 158?> <t>GNAP<t>The Grant Negotiation and Authorization Protocol (GNAP) defines a mechanism for delegating authorization to a piece ofsoftware,software and conveying the results and artifacts of that delegation to the software. This delegation can include access to a set of APIs as well as subject information passed directly to the software.</t> </abstract> </front> <middle><?line 165?><sectionanchor="introduction"><name>Introduction</name> <t>This protocolanchor="introduction"> <name>Introduction</name> <t>GNAP allows a piece of software, the client instance, to request delegated authorization to resource servers and subject information. The delegated access to the resource server can be used by the client instance to access resources and APIs on behalf a resource owner, and delegated access to subject information can in turn be used by the client instance to make authentication decisions. This delegation is facilitated by an authorizationserverserver, usually on behalf of a resource owner. The end user operating the software can interact with the authorization server to authenticate, provide consent, and authorize the request as a resource owner.</t> <t>The process by which the delegation happens is known as a grant, and GNAP allows for the negotiation of the grant process over time by multiple parties acting in distinct roles.</t> <!-- [rfced] The following sentences refer to [I-D.ietf-gnap-resource-servers] as a "companion document". Is the intent for [I-D.ietf-gnap-resource-servers] and this document to be published together? Or may we remove "companion document" from these sentences? Original: The means for an authorization server and resource server to interoperate are discussed in the companion document, [I-D.ietf-gnap-resource-servers]. ... As discussed in the companion document, [I-D.ietf-gnap-resource-servers], the AS and RS can make use of stateless access tokens with an internal structure and format. Perhaps (remove "companion document"): The means for an authorization server and resource server to interoperate are discussed in [GNAP-RS]. ... As discussed in [GNAP-RS], the AS and RS can make use of stateless access tokens with an internal structure and format. --> <!-- [rfced] May we update "for the client instance" as follows to improve readability? Original: This specification also discusses discovery mechanisms for the client instance to configure itself dynamically. Perhaps: This specification also discusses discovery mechanisms that enable the client instance to configure itself dynamically. --> <t>This specification focuses on the portions of the delegation process facing the client instance. In particular, this specification defines interoperable methods for a client instance to request, negotiate, and receive access to information facilitated by the authorization server. This specification additionally defines methods for the client instance to access protected resources at a resource server. This specification also discusses discovery mechanisms for the client instance to configure itself dynamically. The means for an authorization server and resource server to interoperate are discussed in the companiondocument,document <xref target="I-D.ietf-gnap-resource-servers"/>.</t> <t>The focus of this protocol is to provide interoperability between the different parties acting in each role,and isnot to specify implementation details of each. Where appropriate, GNAP may make recommendations about internal implementation details, but these recommendations are to ensure the security of the overall deployment rather than to be prescriptive in the implementation.</t> <t>This protocol solves many of the same use cases as OAuth 2.0 <xref target="RFC6749"/>, OpenID Connect <xref target="OIDC"/>, and the family of protocols that have grown up around that ecosystem. However, GNAP is not an extension of OAuth 2.0 and is not intended to be directly compatible with OAuth 2.0. GNAP seeks to provide functionality and solve use cases that OAuth 2.0 cannot easily or cleanly address. <xref target="vs-oauth2"/> further details the protocol rationale compared to OAuth 2.0. GNAP and OAuth 2.0 will likely exist in parallel for many deployments, and considerations have been taken to facilitate the mapping and transition from existing OAuth 2.0 systems to GNAP. Some examples of these can be found in <xref target="example-oauth2"/>.</t> <sectionanchor="terminology"><name>Terminology</name> <t>Theanchor="terminology"> <name>Terminology</name> <t> The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described inBCP 14BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shownhere.</t> <?line -18?>here. </t> <t>This document contains non-normative examples of partial and complete HTTP messages, JSON structures, URIs, query components, keys, and other elements. Whenever possible, the document uses URI as a generic term, since it aligns with the recommendations in <xref target="RFC3986"/>recommendationsandmatchesbetterwithmatches the intent that the identifier may be reachable through various/generic means (compared to URLs). Some examples use a single trailing backslash<spanx style="verb">\</spanx>(<tt>\</tt>) to indicate line wrapping for long values, as per <xref target="RFC8792"/>. The<spanx style="verb">\</spanx><tt>\</tt> character and leading spaces on wrapped lines are not part of the value.</t> <t>This document uses the term "mutual TLS" as defined by <xref target="RFC8705"/>. The shortened form "MTLS" is used to mean the same thing.</t> <t>For brevity, the term "signature" on its own is used in this document to refer to both digital signatures (which use asymmetric cryptography) and keyed MACs (which use symmetric cryptography). Similarly, the verb "sign" refers to the generation of either a digital signature or a keyed MAC over a given signature base. The qualified term "digital signature" refers specifically to the output of an asymmetric cryptographic signing operation.</t> </section> <sectionanchor="roles"><name>Roles</name>anchor="roles"> <name>Roles</name> <t>The parties in GNAP perform actions under different roles. Roles are defined by the actions taken and the expectations leveraged on the role by the overall protocol.</t><figure title="Figure 1: Roles<figure> <name>Roles inGNAP"><artset><artworkGNAP</name> <artset> <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="432" width="472" viewBox="0 0 472 432" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,32 L 8,112" fill="none" stroke="black"/> <path d="M 8,240 L 8,288" fill="none" stroke="black"/> <path d="M 58,112 L 58,224" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 54,112 L 54,224" fill="none" stroke="black"/> <path d="M 104,240 L 104,288" fill="none" stroke="black"/> <path d="M 120,32 L 120,112" fill="none" stroke="black"/> <path d="M 128,144 L 128,192" fill="none" stroke="black"/> <path d="M 152,96 L 152,144" fill="none" stroke="black"/> <path d="M 170,192 L 170,240" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 166,192 L 166,240" fill="none" stroke="black"/> <path d="M 184,96 L 184,144" fill="none" stroke="black"/> <path d="M 216,144 L 216,192" fill="none" stroke="black"/> <path d="M 216,240 L 216,288" fill="none" stroke="black"/> <path d="M 224,32 L 224,112" fill="none" stroke="black"/> <path d="M 320,240 L 320,288" fill="none" stroke="black"/> <path d="M 328,32 L 328,112" fill="none" stroke="black"/> <path d="M 8,32 L 120,32" fill="none" stroke="black"/> <path d="M 224,32 L 328,32" fill="none" stroke="black"/> <path d="M 128,96 L 152,96" fill="none" stroke="black"/> <path d="M 184,96 L 216,96" fill="none" stroke="black"/> <path d="M 8,112 L 120,112" fill="none" stroke="black"/> <path d="M 224,112 L 328,112" fill="none" stroke="black"/> <path d="M 128,144 L 216,144" fill="none" stroke="black"/> <path d="M 128,192 L 216,192" fill="none" stroke="black"/> <path d="M 24,224 L 88,224" fill="none" stroke="black"/> <path d="M 232,224 L 304,224" fill="none" stroke="black"/> <path d="M 168,238 L 216,238" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 168,242 L 216,242" fill="none" stroke="black"/> <path d="M 24,304 L 88,304" fill="none" stroke="black"/> <path d="M 232,304 L 304,304" fill="none" stroke="black"/> <path d="M 8,366 L 40,366" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 8,370 L 40,370" fill="none" stroke="black"/> <path d="M 8,384 L 40,384" fill="none" stroke="black"/> <path d="M 24,224 C 15.16936,224 8,231.16936 8,240" fill="none" stroke="black"/> <path d="M 88,224 C 96.83064,224 104,231.16936 104,240" fill="none" stroke="black"/> <path d="M 232,224 C 223.16936,224 216,231.16936 216,240" fill="none" stroke="black"/> <path d="M 304,224 C 312.83064,224 320,231.16936 320,240" fill="none" stroke="black"/> <path d="M 24,304 C 15.16936,304 8,296.83064 8,288" fill="none" stroke="black"/> <path d="M 88,304 C 96.83064,304 104,296.83064 104,288" fill="none" stroke="black"/> <path d="M 232,304 C 223.16936,304 216,296.83064 216,288" fill="none" stroke="black"/> <path d="M 304,304 C 312.83064,304 320,296.83064 320,288" fill="none" stroke="black"/> <polygon class="arrowhead" points="224,96 212,90.4 212,101.6" fill="black" transform="rotate(0,216,96)"/> <polygon class="arrowhead" points="136,96 124,90.4 124,101.6" fill="black" transform="rotate(180,128,96)"/> <g class="text"> <text x="64" y="68">Authorization</text> <text x="276" y="68">Resource</text> <text x="60" y="84">Server</text> <text x="276" y="84">Server</text> <text x="172" y="164">Client</text> <text x="172" y="180">Instance</text> <text x="60" y="260">Resource</text> <text x="264" y="260">End</text> <text x="56" y="276">Owner</text> <text x="120" y="276">~</text> <text x="136" y="276">~</text> <text x="152" y="276">~</text> <text x="168" y="276">~</text> <text x="184" y="276">~</text> <text x="200" y="276">~</text> <text x="268" y="276">User</text> <text x="28"y="340">Legend</text>y="340">Legend:</text> <text x="88" y="372">indicates</text> <text x="176" y="372">interaction</text> <text x="256" y="372">between</text> <text x="296" y="372">a</text> <text x="328" y="372">human</text> <text x="368" y="372">and</text> <text x="420" y="372">computer</text> <text x="88" y="388">indicates</text> <text x="176" y="388">interaction</text> <text x="256" y="388">between</text> <text x="304" y="388">two</text> <text x="348" y="388">pieces</text> <text x="388" y="388">of</text> <text x="436" y="388">software</text> <text x="8" y="404">~</text> <text x="24" y="404">~</text> <text x="40" y="404">~</text> <text x="88" y="404">indicates</text> <text x="136" y="404">a</text> <text x="184" y="404">potential</text> <text x="272" y="404">equivalence</text> <text x="332" y="404">or</text> <text x="392" y="404">out-of-band</text> <text x="136" y="420">communication</text> <text x="224" y="420">between</text> <text x="280" y="420">roles</text> </g> </svg></artwork><artwork</artwork> <artwork type="ascii-art"><![CDATA[ +-------------+ +------------+ | | | | |Authorization| | Resource | | Server | | Server | | |<--+ +--->| | +-----+-------+ | | +------------+ ║ | | ║ +--+---+---+ ║ | Client | ║ | Instance | ║ +----+-----+ ║ ║ .----+----. ║ .----------. | | +=====+ | | Resource | | End | | Owner | ~ ~ ~ ~ ~ ~ | User | | | | | `---------` `----------`LegendLegend: ===== indicates interaction between a human and computer ----- indicates interaction between two pieces of software ~ ~ ~ indicates a potential equivalence or out-of-band communication between roles]]></artwork></artset></figure>]]></artwork> </artset> </figure> <dl> <dt>Authorization Server (AS):</dt> <dd><t>server<t>Server that grants delegated privileges to a particular instance of client software in the form of access tokens or other information (such as subject information). The AS is uniquely defined by the <em>grant endpoint URI</em>, which is the absolute URI where grant requests are started by clients.</t> </dd> <dt>Client:</dt> <dd><t>application<t>Application that consumes resources from one or severalRSs,resource servers, possibly requiring access privileges from one or severalASs.ASes. The client is operated by the enduseruser, or it runs autonomously on behalf of a resource owner. </t><t>Example:<t>For example, a client can be a mobile application, a web application, a back-end data processor, etc.</t> <t>Note:thisThis specification differentiates between a specific instance (the client instance, identified by its unique key) and the software running the instance (the client software). For some kinds of client software, there could be many instances of that software, each instance with a different key.</t> </dd> <dt>Resource Server (RS):</dt> <dd><t>server<t>Server that provides an API on protected resources, where operations on the API require a valid access token issued by a trusted AS.</t> </dd> <dt>Resource Owner (RO):</dt> <dd><t>subject<t>Subject entity that may grant or deny operations on resources it has authority upon. </t> <t>Note:theThe act of granting or denying an operation may be manual(i.e.(i.e., through an interaction with a physical person) or automatic(i.e.(i.e., through predefined organizational rules).</t> </dd> <dt>End user:</dt> <dd><t>natural<t>Natural person that operates a client instance. </t> <t>Note:thatThat natural person may or may not be the same entity as the RO.</t> </dd> </dl> <t>The design of GNAP does not assume any one deploymentarchitecture,architecture but instead attempts to define roles that can be fulfilled in a number of different ways for different use cases. As long as a given role fulfills all of its obligations and behaviors as defined by the protocol, GNAP does not make additional requirements on its structure or setup.</t> <t>Multiple roles can be fulfilled by the same party, and a given party can switch roles in different instances of the protocol. For example, in many instances, the RO and end userin many instancesare the same person, where a useris authorizingauthorizes the client instance to act on their own behalf at the RS. In this case, one party fulfillsboth ofthe roles of both RO andend-user roles,end user, but the roles themselves are still defined separately from each other to allow for other use cases where they are fulfilled by different parties.</t><t>For<t>As another example, in some complex scenarios, an RS receiving requests from one client instance can act as a client instance for a downstream secondary RS in order to fulfill the original request. In this case, one piece of software is both an RS and a client instance from different perspectives, and it fulfills these roles separately as far as the overall protocol is concerned.</t> <t>A single role need not be deployed as a monolithic service. For example, a client instance could have front-end components that are installed on the end user's device as well as a back-end system that the front-end communicates with. If both of these components participate in the delegation protocol, they are both considered part of the client instance. If there are several copies of the client software that run separately but all share the same key material, such as a deployed cluster, then this cluster is considered a single client instance. In these cases, the distinct components of what is considered a GNAP client instance may use any number of different communication mechanisms between them, all of which would be considered an implementation detail of the client instances and out of scope of GNAP.</t><t>For<t>As another example, an AS could likewise be built out of many constituent components in a distributed architecture. The component that the client instance calls directly could be different from the component that the RO interacts with to drive consent, since API calls and user interaction have different security considerations in many environments. Furthermore, the AS could need to collect identity claims about the RO from one system that deals with user attributes while generating access tokens at another system that deals with security rights. From the perspective of GNAP, all of these are pieces of the AS and together fulfill the role of the AS as defined by the protocol. These pieces may have their own internal communicationsmechanismsmechanisms, which are considered out of scope of GNAP.</t> </section> <sectionanchor="elements"><name>Elements</name>anchor="elements"> <name>Elements</name> <t>In addition to the roles above, the protocol also involves several elements that are acted upon by the roles throughout the process.</t> <dl> <dt>Access Token:</dt> <dd><t>a<t>A data artifact representing a set of rights and/or attributes. </t> <t>Note:anAn access token can be first issued to a client instance (requiring authorization by the RO) and subsequently rotated.</t> </dd> <!-- [rfced] May we update "and valid for a specific duration" as follows to create parallel structure? Original: Grant: (verb): to permit an instance of client software to receive some attributes at a specific time and valid for a specific duration and/or to exercise some set of delegated rights to access a protected resource; Perhaps: Grant: (verb): to permit an instance of client software to receive some attributes at a specific time and with a specific duration of validity and/or to exercise some set of delegated rights to access a protected resource. --> <dt>Grant:</dt> <dd> <t>(verb):toTo permit an instance of client software to receive some attributes at a specific time and valid for a specific duration and/or to exercise some set of delegated rights to access a protectedresource;</t>resource.</t> </dd> <dt/> <dd> <t>(noun):theThe act of granting permission to a client instance.</t> </dd> <dt>Privilege:</dt> <dd><t>right<t>Right or attribute associated with a subject. </t> <t>Note:theThe RO defines and maintains the rights and attributes associated to the protectedresource,resource and might temporarily delegate some set of those privileges to an end user. This process isreferedreferred to asprivilege delegation.</t>"privilege delegation".</t> </dd> <dt>Protected Resource:</dt> <dd><t>protected<t>Protected API(Application Programming Interface)that is served by an RS and that can be accessed by a client, if and only if a valid and sufficient access token is provided. </t> <t>Note:toTo avoid complex sentences, the specification document may simply refer to "resource" instead of "protected resource".</t> </dd> <dt>Right:</dt> <dd><t>ability<t>Ability given to a subject to perform a given operation on a resource under the control of an RS.</t> </dd> <dt>Subject:</dt> <dd><t>person<t>Person or organization. The subject decides whether and under which conditions its attributes can be disclosed to other parties.</t> </dd> <dt>Subject Information:</dt> <dd><t>set<t>Set of statements and attributes asserted by an AS about a subject. These statements can be used by the client instance as part of an authentication decision.</t> </dd> </dl> </section> <sectionanchor="trust"><name>Trust relationships</name>anchor="trust"> <name>Trust Relationships</name> <!-- [rfced] Is the text in quotation marks a direct quote from a source? If so, a citation and corresponding reference entry are needed. If the intent is that this document defines the trust objective, we will remove the quotation marks. Original: GNAP defines its trust objective as: "the RO trusts the AS to ensure access validation and delegation of protected resources to end users, through third party clients." Perhaps: GNAP defines its trust objective as follows: the RO trusts the AS to ensure access validation and delegation of protected resources to end users, through third-party clients. --> <t>GNAP defines its trust objective as: "the RO trusts the AS to ensure access validation and delegation of protected resources to end users, through third party clients."</t> <t>This trust objective can be decomposed into trust relationships between software elements and roles, especially the pairs end user/RO, end user/client, client/AS, RS/RO, AS/RO, and AS/RS. Trust of an agent by its pair can exist if the pair is informed that the agent has made a promise to follow the protocol in the past(e.g. pre-registration,(e.g., pre-registration and uncompromised cryptographic components) or if the pair is able to infer by indirect means that the agent has made such a promise(e.g.(e.g., a compliant client request). Each agent defines its own valuation function of promises given or received. Examples of such valuations can be the benefits from interacting with other agents(e.g.(e.g., safety in clientaccess,access and interoperability with identity standards), the cost of following the protocol (including its security and privacy requirements and recommendations), a ranking of promise importance(e.g.(e.g., a policy decision made by the AS), the assessment of one's vulnerability or risk of not being able to defend against threats, etc. Those valuations may depend on the context of the request. For instance, depending on the specific case in which GNAP is used, the AS may decide to either take into account or discard hints provided by the client, or the RS may refuse bearertokens, etc. depending on the specific case in which GNAP is used.tokens. Some promises can be affected by previous interactions (e.g., repeated requests).</t><t>Looking back on<t>Below are details of each trust relationship:</t><t><list style="symbols"> <t>end user/RO: this<dl spacing="normal"> <dt>end user/RO:</dt><dd>This relationship exists only when the end user and the RO are different, in which case the end user needs someout of bandout-of-band mechanism of getting the RO consent (see <xref target="authorization"/>). GNAP generally assumes that humans can beauthenticatedauthenticated, thanks to identity protocols (for instance, through an id_token assertion as described in <xreftarget="request-subject"/>).</t> <t>end user/client: thetarget="request-subject"/>).</dd> <dt>end user/client:</dt><dd>The client acts as a user agent. Depending on the technology used (browser,SPA,single-page application (SPA), mobile application,IoTInternet of Things (IoT) device, etc.), some interactions may or may not be possible (as described in <xref target="request-interact-start"/>). Client developers implement requirements and generally some recommendations or best practices, so that the end users may confidently use their software. However, end users might alsobe facingface an attacker's client software or apoorly-implemented client,poorly implemented client without even realizingit.</t> <t>end user/AS: whenit.</dd> <dt>end user/AS:</dt><dd>When the client supports the interaction feature (see <xref target="response-interact"/>), the end user interacts with the AS through an AS-provided interface. In many cases, this happens through a front-channel interaction through the end user's browser. See <xref target="security-front-channel"/> for some considerations in trusting theseinteractions.</t> <t>client/AS: Aninteractions.</dd> <dt>client/AS:</dt><dd>An honest AS maybe facingface an attacker's client (as discussed just above), or the reverse, and GNAP aimsat makingto make common attacks impractical. The core specification makes access tokens opaque to the client and defines the request/response scheme in detail, therefore avoiding extra trust hypotheses from this critical piece of software.YetYet, the AS may further define cryptographic attestations or optional rules to simplify the access of clients it already trusts, due to past behavior or organizational policies (see <xreftarget="request-client"/>).</t> <t>RS/RO:target="request-client"/>).</dd> <dt>RS/RO:</dt><dd>On behalf of the RO, the RS promisesit protectsto protect its resourceson behalf of the ROfrom unauthorizedaccess,access and only accepts valid access tokens issued by a trusted AS. In case tokens are key bound, proper validation of the proof method is expected from theRS.</t> <t>AS/RO: theRS.</dd> <dt>AS/RO:</dt><dd>The AS is expected to follow the decisions made by the RO,eitherthrough either interactive consent requests, repeated interactions, or automated rules (as described in <xref target="sequence"/>). Privacy considerations aim to reduce the risk of an honest but too-curiousAS,AS or the consequences of an unexpected user dataexposure.</t> <t>AS/RS: theexposure.</dd> <dt>AS/RS:</dt><dd>The AS promises to issue valid access tokens to legitimate client requests(i.e.(i.e., after carrying out appropriate due diligence, as defined in the GNAP protocol). Some optional configurations are covered by <xreftarget="I-D.ietf-gnap-resource-servers"/>.</t> </list></t>target="I-D.ietf-gnap-resource-servers"/>.</dd> </dl> <t>A global assumption made by GNAP is that authorization requests are security and privacy sensitive, and appropriate measures arerespectivelydetailed in Sections <xreftarget="security"/>target="security" format="counter"/> and <xreftarget="privacy"/>.</t>target="privacy" format="counter" />, respectively.</t> <!-- [rfced] May we clarify "such as [promise-theory]" as follows? Original: A formal trust model is out of scope of this specification, but one could be developed using techniques such as [promise-theory]. Perhaps: A formal trust model is out of scope of this specification, but one could be developed using techniques such as the Promise Theory [promise-theory]. --> <t>A formal trust model is out of scope of this specification, but one could be developed using techniques such as <xref target="promise-theory"/>.</t> </section> <sectionanchor="protocol"><name>Protocolanchor="protocol"> <name>Protocol Flow</name> <t>GNAP is fundamentally designed to allow delegated access to APIs and other information, such as subject information, using a multi-stage, stateful process. This process allows different parties to provide information into the system to alter and augment the state of the delegated access and its artifacts.</t> <t>The underlying requested grant moves through several states as different actions take place during theprotocol:</t>protocol, as shown in <xref target="state-diagram"/>.</t> <figuretitle="Figureanchor="state-diagram"> <name>State Diagram of a Grant Request throughout GNAP</name> <!-- [rfced] Is "throughout" the correct word choice here? Please review. Current: Figure 2: StatediagramDiagram of agrant requestGrant Request throughoutGNAP"><artset><artworkGNAP Perhaps: Figure 2: State Diagram of a Grant Request in GNAP Or: Figure 2: State Diagram of a Grant Request --> <artset> <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="432" width="584" viewBox="0 0 584 432" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 112,192 L 112,256" fill="none" stroke="black"/> <path d="M 216,192 L 216,256" fill="none" stroke="black"/> <path d="M 378,192 L 378,256" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 374,192 L 374,256" fill="none" stroke="black"/> <path d="M 376,320 L 376,384" fill="none" stroke="black"/> <path d="M 384,64 L 384,128" fill="none" stroke="black"/> <path d="M 424,128 L 424,176" fill="none" stroke="black"/> <path d="M 424,272 L 424,320" fill="none" stroke="black"/> <path d="M 440,48 L 440,64" fill="none" stroke="black"/> <path d="M 440,384 L 440,400" fill="none" stroke="black"/> <path d="M 464,64 L 464,128" fill="none" stroke="black"/> <path d="M 464,320 L 464,384" fill="none" stroke="black"/> <path d="M 474,192 L 474,256" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 470,192 L 470,256" fill="none" stroke="black"/> <path d="M 504,48 L 504,80" fill="none" stroke="black"/> <path d="M 504,368 L 504,400" fill="none" stroke="black"/> <path d="M 456,32 L 488,32" fill="none" stroke="black"/> <path d="M 384,64 L 464,64" fill="none" stroke="black"/> <path d="M 184,80 L 208,80" fill="none" stroke="black"/> <path d="M 344,80 L 376,80" fill="none" stroke="black"/> <path d="M 472,96 L 488,96" fill="none" stroke="black"/> <path d="M 200,112 L 216,112" fill="none" stroke="black"/> <path d="M 368,112 L 384,112" fill="none" stroke="black"/> <path d="M 384,128 L 464,128" fill="none" stroke="black"/> <path d="M 112,192 L 216,192" fill="none" stroke="black"/> <path d="M 376,190 L 472,190" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 376,194 L 472,194" fill="none" stroke="black"/> <path d="M 8,224 L 24,224" fill="none" stroke="black"/> <path d="M 88,224 L 104,224" fill="none" stroke="black"/> <path d="M 216,224 L 264,224" fill="none" stroke="black"/> <path d="M 336,224 L 368,224" fill="none" stroke="black"/> <path d="M 112,256 L 216,256" fill="none" stroke="black"/> <path d="M 376,254 L 472,254" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 376,258 L 472,258" fill="none" stroke="black"/> <path d="M 376,320 L 464,320" fill="none" stroke="black"/> <path d="M 208,336 L 248,336" fill="none" stroke="black"/> <path d="M 304,336 L 376,336" fill="none" stroke="black"/> <path d="M 472,352 L 488,352" fill="none" stroke="black"/> <path d="M 184,368 L 224,368" fill="none" stroke="black"/> <path d="M 344,368 L 368,368" fill="none" stroke="black"/> <path d="M 376,384 L 464,384" fill="none" stroke="black"/> <path d="M 456,416 L 488,416" fill="none" stroke="black"/> <path d="M 128,256 L 184,368" fill="none" stroke="black"/> <path d="M 172,264 L 208,336" fill="none" stroke="black"/> <path d="M 128,192 L 184,80" fill="none" stroke="black"/> <path d="M 164,184 L 200,112" fill="none" stroke="black"/> <path d="M 456,32 C 447.16936,32 440,39.16936 440,48" fill="none" stroke="black"/> <path d="M 488,32 C 496.83064,32 504,39.16936 504,48" fill="none" stroke="black"/> <path d="M 488,96 C 496.83064,96 504,88.83064 504,80" fill="none" stroke="black"/> <path d="M 488,352 C 496.83064,352 504,359.16936 504,368" fill="none" stroke="black"/> <path d="M 456,416 C 447.16936,416 440,408.83064 440,400" fill="none" stroke="black"/> <path d="M 488,416 C 496.83064,416 504,408.83064 504,400" fill="none" stroke="black"/> <polygon class="arrowhead" points="480,352 468,346.4 468,357.6" fill="black" transform="rotate(180,472,352)"/> <polygon class="arrowhead" points="480,96 468,90.4 468,101.6" fill="black" transform="rotate(180,472,96)"/> <polygon class="arrowhead" points="432,272 420,266.4 420,277.6" fill="black" transform="rotate(270,424,272)"/> <polygon class="arrowhead" points="432,176 420,170.4 420,181.6" fill="black" transform="rotate(90,424,176)"/> <polygon class="arrowhead" points="384,80 372,74.4 372,85.6" fill="black" transform="rotate(0,376,80)"/> <polygon class="arrowhead" points="376,368 364,362.4 364,373.6" fill="black" transform="rotate(0,368,368)"/> <polygon class="arrowhead" points="376,224 364,218.4 364,229.6" fill="black" transform="rotate(0,368,224)"/> <polygon class="arrowhead" points="180,264 168,258.4 168,269.6" fill="black" transform="rotate(243.43494882292202,172,264)"/> <polygon class="arrowhead" points="172,184 160,178.4 160,189.6" fill="black" transform="rotate(116.56505117707799,164,184)"/> <polygon class="arrowhead" points="112,224 100,218.4 100,229.6" fill="black" transform="rotate(0,104,224)"/> <g class="text"> <text x="548" y="68">Continue</text> <text x="228" y="84">Need</text> <text x="296" y="84">Interaction</text> <text x="424" y="100">Pending</text> <text x="244" y="116">Finish</text> <text x="320" y="116">Interaction</text> <text x="292" y="132">(approve/deny)</text> <text x="460" y="164">Cancel</text> <text x="56" y="228">Request</text> <text x="164" y="228">Processing</text> <text x="300" y="228">Finalize</text> <text x="424" y="228">Finalized</text> <text x="460" y="292">Revoke</text> <text x="500" y="292">or</text> <text x="468" y="308">Finalize</text> <text x="276" y="340">Update</text> <text x="420" y="356">Approved</text> <text x="236" y="372">No</text> <text x="296" y="372">Interaction</text> <text x="548" y="388">Continue</text> </g> </svg></artwork><artwork</artwork> <artwork type="ascii-art"><![CDATA[ .-----. | | +------+--+ | Continue .---Need Interaction---->| | | / | Pending |<--` / .--Finish Interaction--+ | / / (approve/deny) +----+----+ / / | / / | Cancel / v v +-+----------+ +===========+ | | ║ ║ ---Request-->| Processing +------Finalize---->║ Finalized ║ | | ║ ║ +-+----------+ +===========+ \ ^ ^ \ \ | Revoke or \ \ | Finalize \ \ +-----+----+ \ `-----Update---------+ | \ | Approved |<--. `-----No Interaction--->| | | +-------+--+ | Continue | | `-----`]]></artwork></artset></figure>]]></artwork> </artset> </figure> <t>The state of the grant request is defined and managed by the AS, though the client instance also needs to manage its view of the grant request over time. The means by which these roles manage their stateisare outside the scope of this specification.</t> <dl> <dt><em>Processing</em>:</dt><dd> <t>When<dd>When a<xref target="request">requestrequest foraccess</xref>access (<xref target="request"> </xref>) is received by the AS, a new grant request is created and placed in the <em>processing</em> state by the AS. This state is also entered when an existing grant request is updated by the client instance and when interaction is completed. In this state, the AS processes the context of the grant request to determine whether interaction with the end user or RO is required for approval of the request. The grant request has to exit this state before a response can be returned to the client instance. If approval is required, the request moves to the <em>pending</em>statestate, and the AS returns a<xref target="response-continue">continue response</xref>continue response (<xref target="response-continue"> </xref>) along with any appropriate<xref target="response-interact">interaction responses</xref>.interaction responses (<xref target="response-interact"> </xref>). If no such approval is required, such as when the client instance is acting on its own behalf or the AS can determine that access has been fulfilled, the request moves to the <em>approved</em> state where<xref target="response-token">accessaccess tokens for APIaccess</xref>access (<xref target="response-token"> </xref>) and<xref target="response-subject">subject information</xref>subject information (<xref target="response-subject"> </xref>) can be issued to the client instance. If the AS determines that no additional processing can occur (such as a timeout or an unrecoverable error), the grant request is moved to the <em>finalized</em> state and isterminated.</t> </dd>terminated.</dd> <dt><em>Pending</em>:</dt><dd> <t>When<dd>When a request needs to be approved byaan RO, or interaction with the end user is required, the grant request enters a state of <em>pending</em>. In this state, no access tokens can begrantedgranted, and no subject information can be released to the client instance. While a grant request is in this state, the AS seeks to gather the required<xref target="authorization">consentconsent andauthorization</xref>authorization (<xref target="authorization"> </xref>) for the requested access. A grant request in this state is always associated with a <em>continuation access token</em> bound to the client instance's key (see <xref target="response-continue"/> for details of the continuation access token). If no<xref target="request-interact-finish">interactioninteraction finishmethod</xref>method (<xref target="request-interact-finish"> </xref>) is associated with this request, the client instance can send a<xref target="continue-poll">pollingpolling continuerequest</xref>request (<xref target="continue-poll"> </xref>) to the AS. This returns a<xref target="response-continue">continue response</xref>continue response (<xref target="response-continue"> </xref>) while the grant request remains in this state, allowing the client instance to continue to check the state of the pending grant request. If an<xref target="request-interact-finish">interactioninteraction finishmethod</xref>method (<xref target="request-interact-finish"> </xref>) is specified in the grant request, the client instance can<xref target="continue-after-interaction">continuecontinue the request afterinteraction</xref>interaction (<xref target="continue-after-interaction"> </xref>) to the AS to move this request to the <em>processing</em> state to be re-evaluated by the AS. Note that this occurs whether the grant request has been approved or denied by the RO, since the AS needs to take into account the full context of the request before determining the next step for the grant request. When other information is made available in the context of the grant request, such as through the asynchronous actions of the RO, the AS moves this request to the <em>processing</em> state to be re-evaluated. If the AS determines that no additional interaction can occur,such ase.g., all the interaction methods have timed out or a<xref target="continue-delete">revocation request</xref>revocation request (<xref target="continue-delete"> </xref>) is received from the client instance, the grant request can be moved to the <em>finalized</em>state.</t> </dd>state.</dd> <dt><em>Approved</em>:</dt><dd> <t>When<dd>When a request has been approved by an RO and no further interaction with the end user is required, the grant request enters a state of <em>approved</em>. In this state, responses to the client instance can include<xref target="response-token">accessaccess tokens for APIaccess</xref>access (<xref target="response-token"> </xref>) and<xref target="response-subject">subject information</xref>.subject information (<xref target="response-subject"> </xref>). If continuation and updates are allowed for this grant request, the AS can include the<xref target="response-continue">continuation response</xref>.continuation response (<xref target="response-continue"> </xref>). In this state,<xref target="continue-after-interaction">post-interactionpost-interaction continuationrequests</xref>requests (<xref target="continue-after-interaction"> </xref>) are not allowed and will result in an error, since all interaction is assumed to have been completed. If the client instance sends a<xref target="continue-poll">pollingpolling continuerequest</xref>request (<xref target="continue-poll"> </xref>) while the request is in this state,<xref target="response-token">newnew accesstokens</xref>tokens (<xref target="response-token"> </xref>) can be issued in the response. Note that this always creates a new access token, but any existing access tokens could be rotated and revoked using the<xref target="token-management">tokentoken managementAPI</xref>.API (<xref target="token-management"> </xref>). The client instance can send an<xref target="continue-modify">updateupdate continuationrequest</xref>request (<xref target="continue-modify"> </xref>) to modify the requested access, causing the AS to move the request back to the <em>processing</em> state for re-evaluation. If the AS determines that no additional tokens can beissued,issued and that no additional updates are to be accepted(such as(e.g., the continuation access tokens have expired), the grant is moved to the <em>finalized</em>state.</t> </dd>state.</dd> <dt><em>Finalized</em>:</dt><dd> <t>After<dd>After the access tokens are issued, if the AS does not allow any additional updates on the grant request, the grant request enters the <em>finalized</em> state. This state is also entered when an existing grant request is<xref target="continue-delete">revokedrevoked by the clientinstance</xref>instance (<xref target="continue-delete"> </xref>) or otherwise revoked by the AS (such as through out-of-band action by the RO). This state can also be entered if the AS determines that no additional processing is possible, forexampleexample, if the RO has denied the requested access or if interaction is required but no compatible interaction methods are available. Once in this state, no new access tokens can be issued, no subject information can be returned, and no interactions can take place. Once in this state, the grant request is dead and cannot be revived. If future access is desired by the client instance, a new grant request can be created, unrelated to this grantrequest.</t> </dd>request.</dd> </dl> <t>While it is possible to deploy an AS in a stateless environment, GNAP is a statefulprotocolprotocol, and such deployments will need a way to manage the current state of the grant request in a secure and deterministic fashion without relying on other components, such as the client software, to keep track of the current state.</t> </section> <sectionanchor="sequence"><name>Sequences</name>anchor="sequence"> <name>Sequences</name> <t>GNAP can be used in a variety of ways to allow the core delegation process to take place. Many portions of this process are conditionally present depending on the context of the deployments, and not every step in this overview will happen in all circumstances.</t> <t>Note that a connection between roles in this process does not necessarily indicate that a specific protocol message is sent across the wire between the components fulfilling the roles inquestion,question or that a particular step is required every time. For example, for a client instance interested in only getting subject informationdirectly,directly and not calling an RS, all steps involving the RS below do not apply.</t> <t>In some circumstances, the information needed at a given stage is communicated out of band or ispreconfiguredpre-configured between the components or entities performing the roles. For example, one entity can fulfill multiple roles,andso explicit communication between the roles is not necessary within the protocol flow.AdditionallyAdditionally, some components may not be involved in all use cases. For example, a client instance could be calling the AS just to get direct user information and have no need to get an access token to call an RS.</t> <sectionanchor="sequence-overall"><name>Overallanchor="sequence-overall"> <name>Overall Protocol Sequence</name> <t>The following diagram provides a general overview of GNAP, including many different optional phases and connections. The diagrams in the following sections provide views of GNAP under more specific circumstances. These additional diagrams use the same conventions as the overall diagram below.</t><figure title="Figure 3: Overall sequence of GNAP"><artset><artwork<figure> <name>Overall Sequence of GNAP</name> <artset> <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="624" width="456" viewBox="0 0 456 624" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,48 L 8,64" fill="none" stroke="black"/> <path d="M 8,176 L 8,512" fill="none" stroke="black"/> <path d="M 58,80 L 58,112" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 54,80 L 54,112" fill="none" stroke="black"/> <path d="M 58,144 L 58,176" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 54,144 L 54,176" fill="none" stroke="black"/> <path d="M 80,176 L 80,512" fill="none" stroke="black"/> <path d="M 112,48 L 112,64" fill="none" stroke="black"/> <path d="M 152,224 L 152,328" fill="none" stroke="black"/> <path d="M 152,376 L 152,440" fill="none" stroke="black"/> <path d="M 152,456 L 152,512" fill="none" stroke="black"/> <path d="M 192,48 L 192,64" fill="none" stroke="black"/> <path d="M 250,80 L 250,112" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 246,80 L 246,112" fill="none" stroke="black"/> <path d="M 250,144 L 250,224" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 246,144 L 246,224" fill="none" stroke="black"/> <path d="M 280,224 L 280,328" fill="none" stroke="black"/> <path d="M 280,376 L 280,440" fill="none" stroke="black"/> <path d="M 280,456 L 280,512" fill="none" stroke="black"/> <path d="M 296,48 L 296,64" fill="none" stroke="black"/> <path d="M 344,176 L 344,512" fill="none" stroke="black"/> <path d="M 448,176 L 448,512" fill="none" stroke="black"/> <path d="M 24,32 L 96,32" fill="none" stroke="black"/> <path d="M 208,32 L 280,32" fill="none" stroke="black"/> <path d="M 24,80 L 96,80" fill="none" stroke="black"/> <path d="M 208,80 L 280,80" fill="none" stroke="black"/> <path d="M 8,176 L 80,176" fill="none" stroke="black"/> <path d="M 344,176 L 448,176" fill="none" stroke="black"/> <path d="M 152,224 L 280,224" fill="none" stroke="black"/> <path d="M 80,240 L 104,240" fill="none" stroke="black"/> <path d="M 120,240 L 144,240" fill="none" stroke="black"/> <path d="M 88,256 L 104,256" fill="none" stroke="black"/> <path d="M 120,256 L 152,256" fill="none" stroke="black"/> <path d="M 80,288 L 104,288" fill="none" stroke="black"/> <path d="M 120,288 L 144,288" fill="none" stroke="black"/> <path d="M 88,304 L 104,304" fill="none" stroke="black"/> <path d="M 120,304 L 152,304" fill="none" stroke="black"/> <path d="M 80,336 L 208,336" fill="none" stroke="black"/> <path d="M 224,336 L 336,336" fill="none" stroke="black"/> <path d="M 88,368 L 208,368" fill="none" stroke="black"/> <path d="M 224,368 L 336,368" fill="none" stroke="black"/> <path d="M 80,400 L 104,400" fill="none" stroke="black"/> <path d="M 120,400 L 144,400" fill="none" stroke="black"/> <path d="M 88,416 L 104,416" fill="none" stroke="black"/> <path d="M 128,416 L 152,416" fill="none" stroke="black"/> <path d="M 80,448 L 208,448" fill="none" stroke="black"/> <path d="M 232,448 L 336,448" fill="none" stroke="black"/> <path d="M 80,480 L 104,480" fill="none" stroke="black"/> <path d="M 128,480 L 144,480" fill="none" stroke="black"/> <path d="M 8,512 L 80,512" fill="none" stroke="black"/> <path d="M 152,512 L 280,512" fill="none" stroke="black"/> <path d="M 344,512 L 448,512" fill="none" stroke="black"/> <path d="M 8,558 L 40,558" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 8,562 L 40,562" fill="none" stroke="black"/> <path d="M 8,576 L 40,576" fill="none" stroke="black"/> <path d="M 24,32 C 15.16936,32 8,39.16936 8,48" fill="none" stroke="black"/> <path d="M 96,32 C 104.83064,32 112,39.16936 112,48" fill="none" stroke="black"/> <path d="M 208,32 C 199.16936,32 192,39.16936 192,48" fill="none" stroke="black"/> <path d="M 280,32 C 288.83064,32 296,39.16936 296,48" fill="none" stroke="black"/> <path d="M 24,80 C 15.16936,80 8,72.83064 8,64" fill="none" stroke="black"/> <path d="M 96,80 C 104.83064,80 112,72.83064 112,64" fill="none" stroke="black"/> <path d="M 208,80 C 199.16936,80 192,72.83064 192,64" fill="none" stroke="black"/> <path d="M 280,80 C 288.83064,80 296,72.83064 296,64" fill="none" stroke="black"/> <polygon class="arrowhead" points="344,448 332,442.4 332,453.6" fill="black" transform="rotate(0,336,448)"/> <polygon class="arrowhead" points="344,368 332,362.4 332,373.6" fill="black" transform="rotate(0,336,368)"/> <polygon class="arrowhead" points="344,336 332,330.4 332,341.6" fill="black" transform="rotate(0,336,336)"/> <polygon class="arrowhead" points="152,480 140,474.4 140,485.6" fill="black" transform="rotate(0,144,480)"/> <polygon class="arrowhead" points="152,400 140,394.4 140,405.6" fill="black" transform="rotate(0,144,400)"/> <polygon class="arrowhead" points="152,288 140,282.4 140,293.6" fill="black" transform="rotate(0,144,288)"/> <polygon class="arrowhead" points="152,240 140,234.4 140,245.6" fill="black" transform="rotate(0,144,240)"/> <polygon class="arrowhead" points="96,416 84,410.4 84,421.6" fill="black" transform="rotate(180,88,416)"/> <polygon class="arrowhead" points="96,368 84,362.4 84,373.6" fill="black" transform="rotate(180,88,368)"/> <polygon class="arrowhead" points="96,304 84,298.4 84,309.6" fill="black" transform="rotate(180,88,304)"/> <polygon class="arrowhead" points="96,256 84,250.4 84,261.6" fill="black" transform="rotate(180,88,256)"/> <g class="text"> <text x="40" y="52">End</text> <text x="76"y="52">user</text>y="52">User</text> <text x="128" y="52">~</text> <text x="144" y="52">~</text> <text x="160" y="52">~</text> <text x="176" y="52">~</text> <text x="244" y="52">Resource</text> <text x="224" y="68">Owner</text> <text x="268" y="68">(RO)</text> <text x="56" y="132">(A)</text> <text x="248" y="132">(B)</text> <text x="44" y="196">Client</text> <text x="104" y="196">(1)</text> <text x="396" y="196">Resource</text> <text x="44" y="212">Instance</text> <text x="396" y="212">Server</text> <text x="396" y="228">(RS)</text> <text x="112" y="244">2</text> <text x="216" y="244">Authorization</text> <text x="112" y="260">3</text> <text x="220" y="260">Server</text> <text x="220" y="276">(AS)</text> <text x="112" y="292">4</text> <text x="112" y="308">5</text> <text x="216" y="340">6</text> <text x="152" y="356">|</text> <text x="280" y="356">|</text> <text x="320" y="356">(7)</text> <text x="216" y="372">8</text> <text x="112" y="404">9</text> <text x="116" y="420">10</text> <text x="220" y="452">11</text> <text x="316" y="468">(12)</text> <text x="116" y="484">13</text> <text x="28"y="548">Legend</text>y="548">Legend:</text> <text x="88" y="564">indicates</text> <text x="136" y="564">a</text> <text x="180" y="564">possible</text> <text x="264" y="564">interaction</text> <text x="332" y="564">with</text> <text x="360" y="564">a</text> <text x="392" y="564">human</text> <text x="88" y="580">indicates</text> <text x="140" y="580">an</text> <text x="200" y="580">interaction</text> <text x="280" y="580">between</text> <text x="348" y="580">protocol</text> <text x="408" y="580">roles</text> <text x="8" y="596">~</text> <text x="24" y="596">~</text> <text x="40" y="596">~</text> <text x="88" y="596">indicates</text> <text x="136" y="596">a</text> <text x="184" y="596">potential</text> <text x="272" y="596">equivalence</text> <text x="332" y="596">or</text> <text x="392" y="596">out-of-band</text> <text x="120" y="612">communication</text> <text x="208" y="612">between</text> <text x="264" y="612">roles</text> </g> </svg></artwork><artwork</artwork> <artwork type="ascii-art"><![CDATA[ .----------. .----------. | End user | ~ ~ ~ ~ | Resource | | | | Owner (RO) | `----+-----` `-----+----` ║ ║ ║ ║ (A) (B) ║ ║ ║ ║ +-----+--+ ║ +------------+ | Client | (1) ║ | Resource | |Instance| ║ | Server | | | +-----------+---+ | (RS) | | +--(2)-->| Authorization | | | | |<-(3)---+ Server | | | | | | (AS) | | | | +--(4)-->| | | | | |<-(5)---+ | | | | | | | | | | +---------------(6)------------->| | | | | | (7) | | | |<--------------(8)------------->| | | | | | | | | +--(9)-->| | | | | |<-(10)--+ | | | | | | | | | | +---------------(11)------------>| | | | | | (12) | | | +--(13)->| | | | | | | | | | +--------+ +---------------+ +------------+LegendLegend: ===== indicates a possible interaction with a human ----- indicates an interaction between protocol roles ~ ~ ~ indicates a potential equivalence or out-of-band communication between roles]]></artwork></artset></figure> <t><list style="symbols"> <t>(A)]]></artwork> </artset> </figure> <ul spacing="normal"> <li>(A) The end user interacts with the client instance to indicate a need for resources on behalf of the RO. This could identify the RS that the client instance needs to call, the resources needed, or the RO that is needed to approve the request. Note that the RO and end user are often the same entity in practice, but GNAP makes no general assumption that theyare.</t>are. </li> <li> <t>(1) The client instance determines what access is needed and which AS to approach for access. Note that for most situations, the client instance is pre-configured with which AS to talk to and which kinds of access it needs, but some more dynamic processes are discussed in <xref target="rs-request-without-token"/>.</t> </li> <li> <t>(2) The client instance<xref target="request">requestsrequests access at theAS</xref>.</t>AS (<xref target="request"> </xref>).</t> </li> <li> <t>(3) The AS processes the request and determines what is needed to fulfill the request(See(see <xref target="authorization"/>). The AS sends its<xref target="response">responseresponse to the clientinstance</xref>.</t>instance (<xref target="response"> </xref>).</t> </li> <li> <t>(B) If interaction is required, the AS<xref target="authorization">interactsinteracts with theRO</xref>RO (<xref target="authorization"> </xref>) to gather authorization. The interactive component of the AS can function using a variety of possiblemechanismsmechanisms, including web page redirects, applications, challenge/response protocols, or other methods. The RO approves the request for the client instance being operated by the end user. Note that the RO and end user are often the same entity in practice, and many of GNAP's interaction methods allow the client instance to facilitate the end user interacting with the AS in order to fulfill the role of the RO.</t> </li> <li> <t>(4) The client instance<xref target="continue-request">continuescontinues the grant at theAS</xref>.AS (<xref target="continue-request"> </xref>). This action could occur in response to receiving a signal that<xref target="interaction-finish">interactioninteraction hasfinished</xref>finished (<xref target="interaction-finish"> </xref>) or through a periodic polling mechanism, depending on the interaction capabilities of the client software and the options active in the grant request.</t> </li> <li> <t>(5) If the AS determines that access can be granted, it returns a<xref target="response">responseresponse to the clientinstance</xref>instance (<xref target="response"> </xref>), including an<xref target="response-token">access token</xref>access token (<xref target="response-token"> </xref>) for calling the RS and any<xref target="response-subject">directlydirectly returnedinformation</xref>information (<xref target="response-subject"> </xref>) about the RO.</t> </li> <li> <t>(6) The client instance<xref target="use-access-token">usesuses the accesstoken</xref>token (<xref target="use-access-token"> </xref>) to call the RS.</t> </li> <li> <t>(7) The RS determines if the token is sufficient for the request by examining the token. The means of the RS determining this access are out of scope of this specification, but some options are discussed in <xref target="I-D.ietf-gnap-resource-servers"/>.</t> </li> <li> <t>(8) The client instance<xref target="use-access-token">callscalls theRS</xref>RS (<xref target="use-access-token"> </xref>) using the access token until the RS or client instancedeterminedetermines that the token is no longer valid.</t> </li> <li> <t>(9) When the token no longer works, the client instance<xref target="rotate-access-token">rotatesrotates the accesstoken</xref>.</t>token (<xref target="rotate-access-token"> </xref>).</t> </li> <li> <t>(10) The AS issues a<xref target="response-token">newnew accesstoken</xref>token (<xref target="response-token"> </xref>) to the client instance with the same rights as the original access token returned in (5).</t> </li> <li> <t>(11) The client instance<xref target="use-access-token">usesuses the new accesstoken</xref>token (<xref target="use-access-token"> </xref>) to call the RS.</t> </li> <li> <t>(12) The RS determines if the new token is sufficient for the request, as in (7).</t> </li> <li> <t>(13) The client instance<xref target="revoke-access-token">disposesdisposes of thetoken</xref>token (<xref target="revoke-access-token"> </xref>) once the client instance has completed its access of the RS and no longer needs the token.</t></list></t></li> </ul> <t>The following sections and <xref target="examples"/> contain specific guidance on how to use GNAP in different situations and deployments. For example, it is possible for the client instance to never request an access token and never call an RS, just as it is possible to have no end user involved in the delegation process.</t> </section> <sectionanchor="sequence-redirect"><name>Redirect-basedanchor="sequence-redirect"> <name>Redirect-Based Interaction</name> <t>In this example flow, the client instance is a web application that wants access to resources on behalf of the current user, who acts as both the end user and the resource owner (RO). Since the client instance is capable of directing the user to an arbitrary URI and receiving responses from the user's browser, interaction here is handled through front-channel redirects using the user's browser. The redirection URI used for interaction is a service hosted by the AS in this example. The client instance uses a persistent session with the user to ensure the same user that is starting the interaction is the user that returns from the interaction.</t><figure title="Figure 4: Diagram<figure> <name>Diagram of aredirect-based interaction"><artset><artworkRedirect-Based Interaction</name> <artset> <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="496" width="576" viewBox="0 0 576 496" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,32 L 8,480" fill="none" stroke="black"/> <path d="M 80,32 L 80,480" fill="none" stroke="black"/> <path d="M 360,32 L 360,64" fill="none" stroke="black"/> <path d="M 360,96 L 360,160" fill="none" stroke="black"/> <path d="M 360,192 L 360,288" fill="none" stroke="black"/> <path d="M 360,320 L 360,408" fill="none" stroke="black"/> <path d="M 360,456 L 360,480" fill="none" stroke="black"/> <path d="M 432,32 L 432,64" fill="none" stroke="black"/> <path d="M 432,96 L 432,160" fill="none" stroke="black"/> <path d="M 432,192 L 432,288" fill="none" stroke="black"/> <path d="M 432,320 L 432,408" fill="none" stroke="black"/> <path d="M 432,456 L 432,480" fill="none" stroke="black"/> <path d="M 480,400 L 480,464" fill="none" stroke="black"/> <path d="M 512,48 L 512,304" fill="none" stroke="black"/> <path d="M 552,400 L 552,464" fill="none" stroke="black"/> <path d="M 568,48 L 568,304" fill="none" stroke="black"/> <path d="M 8,32 L 80,32" fill="none" stroke="black"/> <path d="M 360,32 L 432,32" fill="none" stroke="black"/> <path d="M 528,32 L 552,32" fill="none" stroke="black"/> <path d="M 88,78 L 104,78" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 88,82 L 104,82" fill="none" stroke="black"/> <path d="M 120,78 L 136,78" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 120,82 L 136,82" fill="none" stroke="black"/> <path d="M 264,78 L 512,78" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 264,82 L 512,82" fill="none" stroke="black"/> <path d="M 80,112 L 104,112" fill="none" stroke="black"/> <path d="M 120,112 L 144,112" fill="none" stroke="black"/> <path d="M 280,112 L 352,112" fill="none" stroke="black"/> <path d="M 88,144 L 104,144" fill="none" stroke="black"/> <path d="M 120,144 L 136,144" fill="none" stroke="black"/> <path d="M 304,144 L 360,144" fill="none" stroke="black"/> <path d="M 80,174 L 104,174" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 80,178 L 104,178" fill="none" stroke="black"/> <path d="M 120,174 L 136,174" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 120,178 L 136,178" fill="none" stroke="black"/> <path d="M 352,174 L 504,174" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 352,178 L 504,178" fill="none" stroke="black"/> <path d="M 512,192 L 568,192" fill="none" stroke="black"/> <path d="M 440,206 L 464,206" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 440,210 L 464,210" fill="none" stroke="black"/> <path d="M 480,206 L 504,206" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 480,210 L 504,210" fill="none" stroke="black"/> <path d="M 440,254 L 464,254" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 440,258 L 464,258" fill="none" stroke="black"/> <path d="M 480,254 L 504,254" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 480,258 L 504,258" fill="none" stroke="black"/> <path d="M 512,272 L 568,272" fill="none" stroke="black"/> <path d="M 88,302 L 104,302" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 88,306 L 104,306" fill="none" stroke="black"/> <path d="M 120,302 L 136,302" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 120,306 L 136,306" fill="none" stroke="black"/> <path d="M 360,302 L 512,302" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 360,306 L 512,306" fill="none" stroke="black"/> <path d="M 528,320 L 552,320" fill="none" stroke="black"/> <path d="M 80,336 L 104,336" fill="none" stroke="black"/> <path d="M 120,336 L 144,336" fill="none" stroke="black"/> <path d="M 296,336 L 352,336" fill="none" stroke="black"/> <path d="M 88,368 L 104,368" fill="none" stroke="black"/> <path d="M 120,368 L 160,368" fill="none" stroke="black"/> <path d="M 280,368 L 360,368" fill="none" stroke="black"/> <path d="M 480,400 L 552,400" fill="none" stroke="black"/> <path d="M 80,416 L 104,416" fill="none" stroke="black"/> <path d="M 128,416 L 144,416" fill="none" stroke="black"/> <path d="M 248,416 L 472,416" fill="none" stroke="black"/> <path d="M 88,448 L 104,448" fill="none" stroke="black"/> <path d="M 128,448 L 144,448" fill="none" stroke="black"/> <path d="M 264,448 L 472,448" fill="none" stroke="black"/> <path d="M 480,464 L 552,464" fill="none" stroke="black"/> <path d="M 8,480 L 80,480" fill="none" stroke="black"/> <path d="M 360,480 L 432,480" fill="none" stroke="black"/> <path d="M 528,32 C 519.16936,32 512,39.16936 512,48" fill="none" stroke="black"/> <path d="M 552,32 C 560.83064,32 568,39.16936 568,48" fill="none" stroke="black"/> <path d="M 528,320 C 519.16936,320 512,312.83064 512,304" fill="none" stroke="black"/> <path d="M 552,320 C 560.83064,320 568,312.83064 568,304" fill="none" stroke="black"/> <polygon class="arrowhead" points="512,256 500,250.4 500,261.6" fill="black" transform="rotate(0,504,256)"/> <polygon class="arrowhead" points="512,208 500,202.4 500,213.6" fill="black" transform="rotate(0,504,208)"/> <polygon class="arrowhead" points="512,176 500,170.4 500,181.6" fill="black" transform="rotate(0,504,176)"/> <polygon class="arrowhead" points="480,416 468,410.4 468,421.6" fill="black" transform="rotate(0,472,416)"/> <polygon class="arrowhead" points="448,256 436,250.4 436,261.6" fill="black" transform="rotate(180,440,256)"/> <polygon class="arrowhead" points="448,208 436,202.4 436,213.6" fill="black" transform="rotate(180,440,208)"/> <polygon class="arrowhead" points="360,336 348,330.4 348,341.6" fill="black" transform="rotate(0,352,336)"/> <polygon class="arrowhead" points="360,112 348,106.4 348,117.6" fill="black" transform="rotate(0,352,112)"/> <polygon class="arrowhead" points="96,448 84,442.4 84,453.6" fill="black" transform="rotate(180,88,448)"/> <polygon class="arrowhead" points="96,368 84,362.4 84,373.6" fill="black" transform="rotate(180,88,368)"/> <polygon class="arrowhead" points="96,304 84,298.4 84,309.6" fill="black" transform="rotate(180,88,304)"/> <polygon class="arrowhead" points="96,144 84,138.4 84,149.6" fill="black" transform="rotate(180,88,144)"/> <polygon class="arrowhead" points="96,80 84,74.4 84,85.6" fill="black" transform="rotate(180,88,80)"/> <g class="text"> <text x="44" y="52">Client</text> <text x="396" y="52">AS</text> <text x="536" y="52">End</text> <text x="44" y="68">Instance</text> <text x="540" y="68">User</text> <text x="112" y="84">1</text> <text x="168" y="84">Start</text> <text x="224" y="84">Session</text> <text x="112" y="116">2</text> <text x="184" y="116">Request</text> <text x="244" y="116">Access</text> <text x="112" y="148">3</text> <text x="192" y="148">Interaction</text> <text x="268" y="148">Needed</text> <text x="112" y="180">4</text> <text x="180" y="180">Redirect</text> <text x="232" y="180">for</text> <text x="296" y="180">Interaction</text> <text x="472" y="212">5</text> <text x="472" y="228">AuthN</text> <text x="540" y="228">RO</text> <text x="472" y="260">6</text> <text x="472" y="276">AuthZ</text> <text x="536" y="292">End</text> <text x="112" y="308">7</text> <text x="180" y="308">Redirect</text> <text x="232" y="308">for</text> <text x="300" y="308">Continuation</text> <text x="540" y="308">User</text> <text x="112" y="340">8</text> <text x="188" y="340">Continue</text> <text x="256" y="340">Request</text> <text x="112" y="372">9</text> <text x="192" y="372">Grant</text> <text x="244" y="372">Access</text> <text x="116" y="420">10</text> <text x="180" y="420">Access</text> <text x="224" y="420">API</text> <text x="516" y="420">RS</text> <text x="360" y="436">|</text> <text x="432" y="436">|</text> <text x="116" y="452">11</text> <text x="168" y="452">API</text> <text x="220" y="452">Response</text> </g> </svg></artwork><artwork</artwork> <artwork type="ascii-art"><![CDATA[ +--------+ +--------+ .----. | Client | | AS | | End | |Instance| | | | User | | |<=(1)== Start Session ===============================+ | | | | | | | | +--(2)--- Request Access --------->| | | | | | | | | | | |<-(3)-- Interaction Needed -------+ | | | | | | | | | | +==(4)== Redirect for Interaction ===================>| | | | | | +------+ | | | |<==(5)==>| | | | | | AuthN | RO | | | | | | | | | | |<==(6)==>| | | | | | AuthZ +------+ | | | | | End | | |<=(7)== Redirect for Continuation ===================+ User | | | | | `----` | +--(8)--- Continue Request ------->| | | | | | | |<-(9)----- Grant Access ----------+ | | | | | | | | | +--------+ | +--(10)-- Access API ---------------------------->| RS | | | | | | | | |<-(11)-- API Response ---------------------------| | | | | | +--------+ +--------+ +--------+]]></artwork></artset></figure> <t><list style="numbers">]]></artwork> </artset> </figure> <ol spacing="normal" type="1"><li> <t>The client instance establishes a session with the user, in the role of the end user.</t> </li> <li> <t>The client instance<xref target="request">requestsrequests access to theresource</xref>.resource (<xref target="request"> </xref>). The client instance indicates that it can<xref target="request-interact-redirect">redirectredirect to an arbitraryURI</xref>URI (<xref target="request-interact-redirect"> </xref>) and<xref target="request-interact-callback-redirect">receivereceive a redirect from thebrowser</xref>.browser (<xref target="request-interact-callback-redirect"> </xref>). The client instance stores verification information for its redirect in the session created in (1).</t> </li> <li> <t>The AS determines that interaction is needed and<xref target="response">responds</xref>responds (<xref target="response"> </xref>) with a<xref target="response-interact-redirect">URIURI to send the userto</xref>to (<xref target="response-interact-redirect"> </xref>) and<xref target="response-interact-finish">informationinformation needed to verify theredirect</xref>redirect (<xref target="response-interact-finish"> </xref>) in (7). The AS also includes information the client instance will need to<xref target="response-continue">continuecontinue therequest</xref>request (<xref target="response-continue"> </xref>) in (8). The AS associates this continuation information with an ongoing request that will be referenced in (4), (6), and (8).</t> </li> <li> <t>The client instance stores the verification and continuation information from (3) in the session from (1). The client instance then<xref target="interaction-redirect">redirectsredirects the user to theURI</xref>URI (<xref target="interaction-redirect"> </xref>) given by the AS in (3). The user's browser loads the interaction redirect URI. The AS loads the pending request based on the incoming URI generated in (3).</t> </li> <li> <t>The user authenticates at the AS, taking on the role of the RO.</t> </li> <li> <t>As the RO, the user authorizes the pending request from the client instance.</t> </li> <li> <t>When the AS is done interacting with the user, the AS<xref target="interaction-callback">redirectsredirects the userback</xref>back (<xref target="interaction-callback"> </xref>) to the client instance using the redirect URI provided in (2). The redirect URI is augmented with an interaction reference that the AS associates with the ongoing request created in (2) and referenced in (4). The redirect URI is also augmented with a hash of the security information provided in (2) and (3). The client instance loads the verification information from (2) and (3) from the session created in (1). The client instance<xref target="interaction-hash">calculatescalculates ahash</xref>hash (<xref target="interaction-hash"> </xref>) based on this information and continues only if the hash validates. Note that the client instance needs to ensure that the parameters for the incoming request match those that it is expecting from the session created in (1). The client instance also needs to be prepared for the end user never being returned to the client instance and handle timeouts appropriately.</t> </li> <li> <t>The client instance loads the continuation information from (3) and sends the interaction reference from (7) in a request to<xref target="continue-after-interaction">continuecontinue therequest</xref>.request (<xref target="continue-after-interaction"> </xref>). The AS validates the interactionreferencereference, ensuring that the reference is associated with the request being continued.</t> </li> <li> <t>If the request has been authorized, the AS grants access to the information in the form of<xref target="response-token">access tokens</xref>access tokens (<xref target="response-token"> </xref>) and<xref target="response-subject">directdirect subjectinformation</xref>information (<xref target="response-subject"> </xref>) to the client instance.</t> </li> <li> <t>The client instance<xref target="use-access-token">usesuses the accesstoken</xref>token (<xref target="use-access-token"> </xref>) to call the RS.</t> </li> <li> <t>The RS validates the access token and returns an appropriate response for the API.</t></list></t></li> </ol> <t>An example set of protocol messages for this method can be found in <xref target="example-auth-code"/>.</t> </section> <sectionanchor="sequence-user-code"><name>User-codeanchor="sequence-user-code"> <name>User Code Interaction</name> <t>In this example flow, the client instance is a device that is capable of presenting a short, human-readable code to the user and directing the user to enter that code at a known URI. The user enters the code at a URI that is an interactive service hosted by the AS in this example. The client instance is not capable of presenting an arbitrary URI to the user, nor is it capable of accepting incoming HTTP requests from the user's browser. The client instance polls the AS while it is waiting for the RO to authorize the request. The user's interaction is assumed to occur on a secondary device. In thisexampleexample, it is assumed that the user is both the end user and RO. Note that since the user is not assumed to be interacting with the client instance through the same web browser used for interaction at the AS, the user is not shown as being connected to the client instance in this diagram.</t><figure title="Figure 5: Diagram<figure> <name>Diagram of auser-code-based interaction"><artset><artworkUser-Code-Based Interaction</name> <artset> <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="560" width="576" viewBox="0 0 576 560" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,32 L 8,544" fill="none" stroke="black"/> <path d="M 80,32 L 80,544" fill="none" stroke="black"/> <path d="M 360,32 L 360,112" fill="none" stroke="black"/> <path d="M 360,144 L 360,472" fill="none" stroke="black"/> <path d="M 360,520 L 360,544" fill="none" stroke="black"/> <path d="M 432,32 L 432,112" fill="none" stroke="black"/> <path d="M 432,144 L 432,472" fill="none" stroke="black"/> <path d="M 432,520 L 432,544" fill="none" stroke="black"/> <path d="M 480,464 L 480,528" fill="none" stroke="black"/> <path d="M 512,48 L 512,416" fill="none" stroke="black"/> <path d="M 552,464 L 552,528" fill="none" stroke="black"/> <path d="M 568,48 L 568,416" fill="none" stroke="black"/> <path d="M 8,32 L 80,32" fill="none" stroke="black"/> <path d="M 360,32 L 432,32" fill="none" stroke="black"/> <path d="M 528,32 L 552,32" fill="none" stroke="black"/> <path d="M 80,64 L 104,64" fill="none" stroke="black"/> <path d="M 120,64 L 144,64" fill="none" stroke="black"/> <path d="M 280,64 L 352,64" fill="none" stroke="black"/> <path d="M 88,96 L 104,96" fill="none" stroke="black"/> <path d="M 120,96 L 136,96" fill="none" stroke="black"/> <path d="M 304,96 L 360,96" fill="none" stroke="black"/> <path d="M 80,126 L 104,126" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 80,130 L 104,130" fill="none" stroke="black"/> <path d="M 120,126 L 152,126" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 120,130 L 152,130" fill="none" stroke="black"/> <path d="M 312,126 L 504,126" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 312,130 L 504,130" fill="none" stroke="black"/> <path d="M 440,158 L 464,158" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 440,162 L 464,162" fill="none" stroke="black"/> <path d="M 480,158 L 512,158" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 480,162 L 512,162" fill="none" stroke="black"/> <path d="M 512,192 L 568,192" fill="none" stroke="black"/> <path d="M 440,206 L 464,206" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 440,210 L 464,210" fill="none" stroke="black"/> <path d="M 480,206 L 504,206" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 480,210 L 504,210" fill="none" stroke="black"/> <path d="M 80,240 L 104,240" fill="none" stroke="black"/> <path d="M 120,240 L 144,240" fill="none" stroke="black"/> <path d="M 328,240 L 352,240" fill="none" stroke="black"/> <path d="M 440,254 L 464,254" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 440,258 L 464,258" fill="none" stroke="black"/> <path d="M 480,254 L 504,254" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 480,258 L 504,258" fill="none" stroke="black"/> <path d="M 88,272 L 104,272" fill="none" stroke="black"/> <path d="M 128,272 L 144,272" fill="none" stroke="black"/> <path d="M 344,272 L 360,272" fill="none" stroke="black"/> <path d="M 440,302 L 464,302" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 440,306 L 464,306" fill="none" stroke="black"/> <path d="M 480,302 L 504,302" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 480,306 L 504,306" fill="none" stroke="black"/> <path d="M 440,350 L 464,350" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 440,354 L 464,354" fill="none" stroke="black"/> <path d="M 480,350 L 504,350" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 480,354 L 504,354" fill="none" stroke="black"/> <path d="M 512,384 L 568,384" fill="none" stroke="black"/> <path d="M 80,400 L 104,400" fill="none" stroke="black"/> <path d="M 128,400 L 144,400" fill="none" stroke="black"/> <path d="M 328,400 L 352,400" fill="none" stroke="black"/> <path d="M 88,432 L 104,432" fill="none" stroke="black"/> <path d="M 128,432 L 168,432" fill="none" stroke="black"/> <path d="M 288,432 L 360,432" fill="none" stroke="black"/> <path d="M 528,432 L 552,432" fill="none" stroke="black"/> <path d="M 480,464 L 552,464" fill="none" stroke="black"/> <path d="M 80,480 L 104,480" fill="none" stroke="black"/> <path d="M 128,480 L 144,480" fill="none" stroke="black"/> <path d="M 248,480 L 472,480" fill="none" stroke="black"/> <path d="M 88,512 L 104,512" fill="none" stroke="black"/> <path d="M 128,512 L 144,512" fill="none" stroke="black"/> <path d="M 264,512 L 480,512" fill="none" stroke="black"/> <path d="M 480,528 L 552,528" fill="none" stroke="black"/> <path d="M 8,544 L 80,544" fill="none" stroke="black"/> <path d="M 360,544 L 432,544" fill="none" stroke="black"/> <path d="M 528,32 C 519.16936,32 512,39.16936 512,48" fill="none" stroke="black"/> <path d="M 552,32 C 560.83064,32 568,39.16936 568,48" fill="none" stroke="black"/> <path d="M 528,432 C 519.16936,432 512,424.83064 512,416" fill="none" stroke="black"/> <path d="M 552,432 C 560.83064,432 568,424.83064 568,416" fill="none" stroke="black"/> <polygon class="arrowhead" points="512,352 500,346.4 500,357.6" fill="black" transform="rotate(0,504,352)"/> <polygon class="arrowhead" points="512,304 500,298.4 500,309.6" fill="black" transform="rotate(0,504,304)"/> <polygon class="arrowhead" points="512,256 500,250.4 500,261.6" fill="black" transform="rotate(0,504,256)"/> <polygon class="arrowhead" points="512,208 500,202.4 500,213.6" fill="black" transform="rotate(0,504,208)"/> <polygon class="arrowhead" points="512,128 500,122.4 500,133.6" fill="black" transform="rotate(0,504,128)"/> <polygon class="arrowhead" points="480,480 468,474.4 468,485.6" fill="black" transform="rotate(0,472,480)"/> <polygon class="arrowhead" points="448,352 436,346.4 436,357.6" fill="black" transform="rotate(180,440,352)"/> <polygon class="arrowhead" points="448,304 436,298.4 436,309.6" fill="black" transform="rotate(180,440,304)"/> <polygon class="arrowhead" points="448,256 436,250.4 436,261.6" fill="black" transform="rotate(180,440,256)"/> <polygon class="arrowhead" points="448,208 436,202.4 436,213.6" fill="black" transform="rotate(180,440,208)"/> <polygon class="arrowhead" points="448,160 436,154.4 436,165.6" fill="black" transform="rotate(180,440,160)"/> <polygon class="arrowhead" points="360,400 348,394.4 348,405.6" fill="black" transform="rotate(0,352,400)"/> <polygon class="arrowhead" points="360,240 348,234.4 348,245.6" fill="black" transform="rotate(0,352,240)"/> <polygon class="arrowhead" points="360,64 348,58.4 348,69.6" fill="black" transform="rotate(0,352,64)"/> <polygon class="arrowhead" points="96,512 84,506.4 84,517.6" fill="black" transform="rotate(180,88,512)"/> <polygon class="arrowhead" points="96,432 84,426.4 84,437.6" fill="black" transform="rotate(180,88,432)"/> <polygon class="arrowhead" points="96,272 84,266.4 84,277.6" fill="black" transform="rotate(180,88,272)"/> <polygon class="arrowhead" points="96,96 84,90.4 84,101.6" fill="black" transform="rotate(180,88,96)"/> <g class="text"> <text x="44" y="52">Client</text> <text x="396" y="52">AS</text> <text x="536" y="52">End</text> <text x="44" y="68">Instance</text> <text x="112" y="68">1</text> <text x="184" y="68">Request</text> <text x="244" y="68">Access</text> <text x="540" y="68">User</text> <text x="112" y="100">2</text> <text x="192" y="100">Interaction</text> <text x="268" y="100">Needed</text> <text x="112" y="132">3</text> <text x="192" y="132">Display</text> <text x="244" y="132">User</text> <text x="284" y="132">Code</text> <text x="472" y="164">4</text> <text x="452" y="180">Open</text> <text x="488" y="180">URI</text> <text x="472" y="212">5</text> <text x="540" y="212">RO</text> <text x="472" y="228">AuthN</text> <text x="112" y="244">9</text> <text x="188" y="244">Continue</text> <text x="256" y="244">Request</text> <text x="304" y="244">(A)</text> <text x="472" y="260">6</text> <text x="116" y="276">10</text> <text x="168" y="276">Not</text> <text x="200" y="276">Yet</text> <text x="248" y="276">Granted</text> <text x="308" y="276">(Wait)</text> <text x="468" y="276">Code</text> <text x="472" y="308">7</text> <text x="472" y="324">AuthZ</text> <text x="472" y="356">8</text> <text x="468" y="372">Complete</text> <text x="116" y="404">11</text> <text x="188" y="404">Continue</text> <text x="256" y="404">Request</text> <text x="304" y="404">(B)</text> <text x="536" y="404">End</text> <text x="540" y="420">User</text> <text x="116" y="436">12</text> <text x="200" y="436">Grant</text> <text x="252" y="436">Access</text> <text x="116" y="484">13</text> <text x="180" y="484">Access</text> <text x="224" y="484">API</text> <text x="516" y="484">RS</text> <text x="360" y="500">|</text> <text x="432" y="500">|</text> <text x="116" y="516">14</text> <text x="168" y="516">API</text> <text x="220" y="516">Response</text> </g> </svg></artwork><artwork</artwork> <artwork type="ascii-art"><![CDATA[ +--------+ +--------+ .----. | Client | | AS | | End | |Instance+--(1)--- Request Access --------->| | | User | | | | | | | | |<-(2)-- Interaction Needed -------+ | | | | | | | | | | +==(3)==== Display User Code ========================>| | | | | | | | | | | |<==(4)===+ | | | | |Open URI | | | | | | +------+ | | | |<==(5)==>| RO | | | | | AuthN | | | +--(9)--- Continue Request (A) --->| | | | | | | |<==(6)==>| | | |<-(10)-- Not Yet Granted (Wait) --+ | Code | | | | | | | | | | | |<==(7)==>| | | | | | AuthZ | | | | | | | | | | | |<==(8)==>| | | | | |Complete | | | | | | +------+ | +--(11)-- Continue Request (B) --->| | | End | | | | | | User | | |<-(12)----- Grant Access ---------+ | `----` | | | | | | | | +--------+ | +--(13)-- Access API ---------------------------->| RS | | | | | | | | |<-(14)-- API Response ---------------------------+ | | | | | +--------+ +--------+ +--------+]]></artwork></artset></figure> <t><list style="numbers">]]></artwork> </artset> </figure> <ol spacing="normal" type="1"><li> <t>The client instance<xref target="request">requestsrequests access to theresource</xref>.resource (<xref target="request"> </xref>). The client instance indicates that it can<xref target="request-interact-usercode">displaydisplay a usercode</xref>.</t>code (<xref target="request-interact-usercode"> </xref>).</t> </li> <li> <t>The AS determines that interaction is needed and<xref target="response">responds</xref>responds (<xref target="response"> </xref>) with a<xref target="response-interact-usercode">useruser code to communicate to theuser</xref>.user (<xref target="response-interact-usercode"> </xref>). The AS also includes information the client instance will need to<xref target="response-continue">continuecontinue therequest</xref>request (<xref target="response-continue"> </xref>) in (8) and (10). The AS associates this continuation information with an ongoing request that will be referenced in (4), (6), (8), and (10).</t> </li> <li> <t>The client instance stores the continuation information from (2) for use in (8) and (10). The client instance then<xref target="interaction-usercode">communicatescommunicates the code to theuser</xref>user (<xref target="interaction-usercode"> </xref>) given by the AS in (2).</t> </li> <li> <t>The users directs their browser to the user code URI. This URI is stable and can be communicated via the client software's documentation, the AS documentation, or the client software itself. Since it is assumed that the RO will interact with the AS through a secondary device, the client instance does not provide a mechanism to launch the RO's browser at this URI.</t> </li> <li> <t>The end user authenticates at the AS, taking on the role of the RO.</t> </li> <li> <t>The RO enters the code communicated in (3) to the AS. The AS validates this code against a current request in process.</t> </li> <li> <t>As the RO, the user authorizes the pending request from the client instance.</t> </li> <li> <t>When the AS is done interacting with the user, the AS indicates to the RO that the request has been completed.</t> </li> <li> <t>Meanwhile, the client instance loads the continuation information stored at (3) and<xref target="continue-request">continuescontinues therequest</xref>.request (<xref target="continue-request"> </xref>). The AS determines which ongoing access request is referenced here and checks its state.</t> </li> <li> <t>If the access request has not yet been authorized by the RO in (6), the AS responds to the client instance to<xref target="response-continue">continuecontinue therequest</xref>request (<xref target="response-continue"> </xref>) at a future time through additional polled continuation requests. This response can include updated continuation information as well as information regarding how long the client instance should wait before calling again. The client instance replaces its stored continuation information from the previous response (2). Note that the AS may need to determine that the RO has not approved the request in a sufficient amount of time and return an appropriate error to the client instance.</t> </li> <li> <t>The client instance continues to<xref target="continue-poll">pollpoll theAS</xref>AS (<xref target="continue-poll"> </xref>) with the new continuation information in (9).</t> </li> <li> <t>If the request has been authorized, the AS grants access to the information in the form of<xref target="response-token">access tokens</xref>access tokens (<xref target="response-token"> </xref>) and<xref target="response-subject">directdirect subjectinformation</xref>information (<xref target="response-subject"> </xref>) to the client instance.</t> </li> <li> <t>The client instance<xref target="use-access-token">usesuses the accesstoken</xref>token (<xref target="use-access-token"> </xref>) to call the RS.</t> </li> <li> <t>The RS validates the access token and returns an appropriate response for the API.</t></list></t></li> </ol> <t>An example set of protocol messages for this method can be found in <xref target="example-device"/>.</t> </section> <sectionanchor="sequence-async"><name>Asynchronousanchor="sequence-async"> <name>Asynchronous Authorization</name> <t>In this example flow, the end user and RO roles are fulfilled by different parties, and the RO does not interact with the client instance. The AS reaches out asynchronously to the RO during the request process to gather the RO's authorization for the client instance's request. The client instance polls the AS while it is waiting for the RO to authorize the request.</t><figure title="Figure 6: Diagram<figure> <name>Diagram of anasynchronous authorization process,Asynchronous Authorization Process, withno end user interaction"><artset><artworkNo End-User Interaction</name> <artset> <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="416" width="576" viewBox="0 0 576 416" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,32 L 8,400" fill="none" stroke="black"/> <path d="M 80,32 L 80,400" fill="none" stroke="black"/> <path d="M 360,32 L 360,328" fill="none" stroke="black"/> <path d="M 360,376 L 360,400" fill="none" stroke="black"/> <path d="M 432,32 L 432,328" fill="none" stroke="black"/> <path d="M 432,376 L 432,400" fill="none" stroke="black"/> <path d="M 480,320 L 480,384" fill="none" stroke="black"/> <path d="M 512,48 L 512,240" fill="none" stroke="black"/> <path d="M 552,320 L 552,384" fill="none" stroke="black"/> <path d="M 568,48 L 568,240" fill="none" stroke="black"/> <path d="M 8,32 L 80,32" fill="none" stroke="black"/> <path d="M 360,32 L 432,32" fill="none" stroke="black"/> <path d="M 528,32 L 552,32" fill="none" stroke="black"/> <path d="M 80,64 L 104,64" fill="none" stroke="black"/> <path d="M 120,64 L 144,64" fill="none" stroke="black"/> <path d="M 280,64 L 352,64" fill="none" stroke="black"/> <path d="M 88,96 L 104,96" fill="none" stroke="black"/> <path d="M 120,96 L 136,96" fill="none" stroke="black"/> <path d="M 336,96 L 360,96" fill="none" stroke="black"/> <path d="M 440,110 L 464,110" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 440,114 L 464,114" fill="none" stroke="black"/> <path d="M 480,110 L 504,110" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 480,114 L 504,114" fill="none" stroke="black"/> <path d="M 80,144 L 104,144" fill="none" stroke="black"/> <path d="M 120,144 L 144,144" fill="none" stroke="black"/> <path d="M 328,144 L 352,144" fill="none" stroke="black"/> <path d="M 440,158 L 464,158" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 440,162 L 464,162" fill="none" stroke="black"/> <path d="M 480,158 L 504,158" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 480,162 L 504,162" fill="none" stroke="black"/> <path d="M 88,176 L 104,176" fill="none" stroke="black"/> <path d="M 120,176 L 136,176" fill="none" stroke="black"/> <path d="M 336,176 L 360,176" fill="none" stroke="black"/> <path d="M 440,206 L 464,206" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 440,210 L 464,210" fill="none" stroke="black"/> <path d="M 480,206 L 504,206" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 480,210 L 504,210" fill="none" stroke="black"/> <path d="M 80,256 L 104,256" fill="none" stroke="black"/> <path d="M 120,256 L 144,256" fill="none" stroke="black"/> <path d="M 328,256 L 352,256" fill="none" stroke="black"/> <path d="M 528,256 L 552,256" fill="none" stroke="black"/> <path d="M 88,288 L 104,288" fill="none" stroke="black"/> <path d="M 120,288 L 168,288" fill="none" stroke="black"/> <path d="M 288,288 L 360,288" fill="none" stroke="black"/> <path d="M 480,320 L 552,320" fill="none" stroke="black"/> <path d="M 80,336 L 104,336" fill="none" stroke="black"/> <path d="M 128,336 L 144,336" fill="none" stroke="black"/> <path d="M 248,336 L 472,336" fill="none" stroke="black"/> <path d="M 88,368 L 104,368" fill="none" stroke="black"/> <path d="M 128,368 L 144,368" fill="none" stroke="black"/> <path d="M 264,368 L 480,368" fill="none" stroke="black"/> <path d="M 480,384 L 552,384" fill="none" stroke="black"/> <path d="M 8,400 L 80,400" fill="none" stroke="black"/> <path d="M 360,400 L 432,400" fill="none" stroke="black"/> <path d="M 528,32 C 519.16936,32 512,39.16936 512,48" fill="none" stroke="black"/> <path d="M 552,32 C 560.83064,32 568,39.16936 568,48" fill="none" stroke="black"/> <path d="M 528,256 C 519.16936,256 512,248.83064 512,240" fill="none" stroke="black"/> <path d="M 552,256 C 560.83064,256 568,248.83064 568,240" fill="none" stroke="black"/> <polygon class="arrowhead" points="512,208 500,202.4 500,213.6" fill="black" transform="rotate(0,504,208)"/> <polygon class="arrowhead" points="512,160 500,154.4 500,165.6" fill="black" transform="rotate(0,504,160)"/> <polygon class="arrowhead" points="512,112 500,106.4 500,117.6" fill="black" transform="rotate(0,504,112)"/> <polygon class="arrowhead" points="480,336 468,330.4 468,341.6" fill="black" transform="rotate(0,472,336)"/> <polygon class="arrowhead" points="448,208 436,202.4 436,213.6" fill="black" transform="rotate(180,440,208)"/> <polygon class="arrowhead" points="448,160 436,154.4 436,165.6" fill="black" transform="rotate(180,440,160)"/> <polygon class="arrowhead" points="448,112 436,106.4 436,117.6" fill="black" transform="rotate(180,440,112)"/> <polygon class="arrowhead" points="360,256 348,250.4 348,261.6" fill="black" transform="rotate(0,352,256)"/> <polygon class="arrowhead" points="360,144 348,138.4 348,149.6" fill="black" transform="rotate(0,352,144)"/> <polygon class="arrowhead" points="360,64 348,58.4 348,69.6" fill="black" transform="rotate(0,352,64)"/> <polygon class="arrowhead" points="96,368 84,362.4 84,373.6" fill="black" transform="rotate(180,88,368)"/> <polygon class="arrowhead" points="96,288 84,282.4 84,293.6" fill="black" transform="rotate(180,88,288)"/> <polygon class="arrowhead" points="96,176 84,170.4 84,181.6" fill="black" transform="rotate(180,88,176)"/> <polygon class="arrowhead" points="96,96 84,90.4 84,101.6" fill="black" transform="rotate(180,88,96)"/> <g class="text"> <text x="44" y="52">Client</text> <text x="396" y="52">AS</text> <text x="540" y="52">RO</text> <text x="44" y="68">Instance</text> <text x="112" y="68">1</text> <text x="184" y="68">Request</text> <text x="244" y="68">Access</text> <text x="112" y="100">2</text> <text x="160" y="100">Not</text> <text x="192" y="100">Yet</text> <text x="240" y="100">Granted</text> <text x="300" y="100">(Wait)</text> <text x="472" y="116">3</text> <text x="472" y="132">AuthN</text> <text x="112" y="148">6</text> <text x="188" y="148">Continue</text> <text x="256" y="148">Request</text> <text x="304" y="148">(A)</text> <text x="472" y="164">4</text> <text x="112" y="180">7</text> <text x="160" y="180">Not</text> <text x="192" y="180">Yet</text> <text x="240" y="180">Granted</text> <text x="300" y="180">(Wait)</text> <text x="472" y="180">AuthZ</text> <text x="472" y="212">5</text> <text x="472" y="228">Completed</text> <text x="112" y="260">8</text> <text x="188" y="260">Continue</text> <text x="256" y="260">Request</text> <text x="304" y="260">(B)</text> <text x="112" y="292">9</text> <text x="200" y="292">Grant</text> <text x="252" y="292">Access</text> <text x="116" y="340">10</text> <text x="180" y="340">Access</text> <text x="224" y="340">API</text> <text x="516" y="340">RS</text> <text x="360" y="356">|</text> <text x="432" y="356">|</text> <text x="116" y="372">11</text> <text x="168" y="372">API</text> <text x="220" y="372">Response</text> </g> </svg></artwork><artwork</artwork> <artwork type="ascii-art"><![CDATA[ +--------+ +--------+ .----. | Client | | AS | | RO | |Instance+--(1)--- Request Access --------->| | | | | | | | | | | |<-(2)-- Not Yet Granted (Wait) ---+ | | | | | | |<==(3)==>| | | | | | AuthN | | | +--(6)--- Continue Request (A) --->| | | | | | | |<==(4)==>| | | |<-(7)-- Not Yet Granted (Wait) ---+ | AuthZ | | | | | | | | | | | |<==(5)==>| | | | | |Completed| | | | | | | | | +--(8)--- Continue Request (B) --->| | `----` | | | | | |<-(9)------ Grant Access ---------+ | | | | | | | | | +--------+ | +--(10)-- Access API ---------------------------->| RS | | | | | | | | |<-(11)-- API Response ---------------------------+ | | | | | +--------+ +--------+ +--------+]]></artwork></artset></figure> <t><list style="numbers">]]></artwork> </artset> </figure> <ol spacing="normal" type="1"><li> <t>The client instance<xref target="request">requestsrequests access to theresource</xref>.resource (<xref target="request"> </xref>). The client instance does not send any interaction modes to the server, indicating that it does not expect to interact with the RO. The client instance can also signal which RO it requires authorization from, if known, by using the<xref target="request-subject">subject request</xref>subject request section (<xref target="request-subject"> </xref>) and<xref target="request-user">user request</xref> sections.user request section (<xref target="request-user"> </xref>). It's also possible for the AS to determine which RO needs to be contacted by the nature of what access is being requested.</t> </li> <li> <t>The AS determines that interaction is needed, but the client instance cannot interact with the RO. The AS<xref target="response">responds</xref>responds (<xref target="response"> </xref>) with the information the client instance will need to<xref target="response-continue">continuecontinue therequest</xref>request (<xref target="response-continue"> </xref>) in (6) and (8), including a signal that the client instance should wait before checking the status of the request again. The AS associates this continuation information with an ongoing request that will be referenced in (3), (4), (5), (6), and (8).</t> </li> <li> <t>The AS determines which RO to contact based on the request in (1), through a combination of the<xref target="request-user">user request</xref>,user request (<xref target="request-user"> </xref>), the<xref target="request-subject">subject request</xref>,subject request (<xref target="request-subject"> </xref>), the<xref target="request-token">access request</xref>,access request (<xref target="request-token"> </xref>), and other policy information. The AS contacts the RO and authenticates them.</t> </li> <li> <t>The RO authorizes the pending request from the client instance.</t> </li> <li> <t>When the AS is done interacting with the RO, the AS indicates to the RO that the request has been completed.</t> </li> <li> <t>Meanwhile, the client instance loads the continuation information stored at (2) and<xref target="continue-request">continuescontinues therequest</xref>.request (<xref target="continue-request"> </xref>). The AS determines which ongoing access request is referenced here and checks its state.</t> </li> <li> <t>If the access request has not yet been authorized by the RO in (6), the AS responds to the client instance to<xref target="response-continue">continuecontinue therequest</xref>request (<xref target="response-continue"> </xref>) at a future time through additional polling. Note that this response is not an error message, since no error has yet occurred. This response can include refreshed credentials as well as information regarding how long the client instance should wait before calling again. The client instance replaces its stored continuation information from the previous response (2). Note that the AS may need to determine that the RO has not approved the request in a sufficient amount of time and return an appropriate error to the client instance.</t> </li> <li> <t>The client instance continues to<xref target="continue-poll">pollpoll theAS</xref>AS (<xref target="continue-poll"></xref>) with the new continuation information from (7).</t> </li> <li> <t>If the request has been authorized, the AS grants access to the information in the form of<xref target="response-token">access tokens</xref>access tokens (<xref target="response-token"> </xref>) and<xref target="response-subject">directdirect subjectinformation</xref>information (<xref target="response-subject"> </xref>) to the client instance.</t> </li> <li> <t>The client instance<xref target="use-access-token">usesuses the accesstoken</xref>token (<xref target="use-access-token"> </xref>) to call the RS.</t> </li> <li> <t>The RS validates the access token and returns an appropriate response for the API.</t></list></t></li> </ol> <t>An example set of protocol messages for this method can be found in <xref target="example-async"/>.</t> <t>Additional considerations for asynchronous interactions like this are discussed in <xref target="security-async"/>.</t> </section> <sectionanchor="sequence-no-user"><name>Software-onlyanchor="sequence-no-user"> <name>Software-Only Authorization</name> <t>In this example flow, the AS policy allows the client instance to make a call on its own behalf, without the need for an RO to be involved at runtime to approve the decision. Since there is no explicit RO, the client instance does not interact with an RO.</t><figure title="Figure 7: Diagram<figure> <name>Diagram of asoftware-only authorization,Software-Only Authorization, withno end userNo End User orexplicit resource owner"><artset><artworkExplicit Resource Owner</name> <artset> <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="208" width="488" viewBox="0 0 488 208" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,32 L 8,192" fill="none" stroke="black"/> <path d="M 80,32 L 80,192" fill="none" stroke="black"/> <path d="M 312,32 L 312,120" fill="none" stroke="black"/> <path d="M 312,168 L 312,192" fill="none" stroke="black"/> <path d="M 384,32 L 384,120" fill="none" stroke="black"/> <path d="M 384,168 L 384,192" fill="none" stroke="black"/> <path d="M 408,112 L 408,176" fill="none" stroke="black"/> <path d="M 480,112 L 480,176" fill="none" stroke="black"/> <path d="M 8,32 L 80,32" fill="none" stroke="black"/> <path d="M 312,32 L 384,32" fill="none" stroke="black"/> <path d="M 80,64 L 104,64" fill="none" stroke="black"/> <path d="M 120,64 L 144,64" fill="none" stroke="black"/> <path d="M 280,64 L 304,64" fill="none" stroke="black"/> <path d="M 88,96 L 104,96" fill="none" stroke="black"/> <path d="M 120,96 L 152,96" fill="none" stroke="black"/> <path d="M 272,96 L 312,96" fill="none" stroke="black"/> <path d="M 408,112 L 480,112" fill="none" stroke="black"/> <path d="M 80,128 L 104,128" fill="none" stroke="black"/> <path d="M 120,128 L 144,128" fill="none" stroke="black"/> <path d="M 248,128 L 400,128" fill="none" stroke="black"/> <path d="M 88,160 L 104,160" fill="none" stroke="black"/> <path d="M 120,160 L 144,160" fill="none" stroke="black"/> <path d="M 264,160 L 408,160" fill="none" stroke="black"/> <path d="M 408,176 L 480,176" fill="none" stroke="black"/> <path d="M 8,192 L 80,192" fill="none" stroke="black"/> <path d="M 312,192 L 384,192" fill="none" stroke="black"/> <polygon class="arrowhead" points="408,128 396,122.4 396,133.6" fill="black" transform="rotate(0,400,128)"/> <polygon class="arrowhead" points="312,64 300,58.4 300,69.6" fill="black" transform="rotate(0,304,64)"/> <polygon class="arrowhead" points="96,160 84,154.4 84,165.6" fill="black" transform="rotate(180,88,160)"/> <polygon class="arrowhead" points="96,96 84,90.4 84,101.6" fill="black" transform="rotate(180,88,96)"/> <g class="text"> <text x="44" y="52">Client</text> <text x="348" y="52">AS</text> <text x="44" y="68">Instance</text> <text x="112" y="68">1</text> <text x="184" y="68">Request</text> <text x="244" y="68">Access</text> <text x="112" y="100">2</text> <text x="184" y="100">Grant</text> <text x="236" y="100">Access</text> <text x="112" y="132">3</text> <text x="180" y="132">Access</text> <text x="224" y="132">API</text> <text x="444" y="132">RS</text> <text x="312" y="148">|</text> <text x="384" y="148">|</text> <text x="112" y="164">4</text> <text x="168" y="164">API</text> <text x="220" y="164">Response</text> </g> </svg></artwork><artwork</artwork> <artwork type="ascii-art"><![CDATA[ +--------+ +--------+ | Client | | AS | |Instance+--(1)--- Request Access --->| | | | | | | |<-(2)---- Grant Access -----+ | | | | | +--------+ | +--(3)--- Access API ------------------->| RS | | | | | | | | |<-(4)--- API Response ------------------+ | | | | | +--------+ +--------+ +--------+]]></artwork></artset></figure> <t><list style="numbers">]]></artwork> </artset> </figure> <ol spacing="normal" type="1"><li> <t>The client instance<xref target="request">requestsrequests access to theresource</xref>.resource (<xref target="request"> </xref>). The client instance does not send any interaction modes to the server.</t> </li> <li> <t>The AS determines that the request has been authorized based on the identity of the client instance making the request and the<xref target="request-token">access requested</xref>.access requested (<xref target="request-token"> </xref>). The AS grants access to the resource in the form of<xref target="response-token">access tokens</xref>access tokens (<xref target="response-token"> </xref>) to the client instance. Note that<xref target="response-subject">directdirect subjectinformation</xref>information (<xref target="response-subject"> </xref>) is not generally applicable in this use case, as there is no user involved.</t> </li> <li> <t>The client instance<xref target="use-access-token">usesuses the accesstoken</xref>token (<xref target="use-access-token"> </xref>) to call the RS.</t> </li> <li> <t>The RS validates the access token and returns an appropriate response for the API.</t></list></t></li> </ol> <t>An example set of protocol messages for this method can be found in <xref target="example-no-user"/>.</t> </section> <sectionanchor="sequence-refresh"><name>Refreshinganchor="sequence-refresh"> <name>Refreshing an Expired Access Token</name> <t>In this example flow, the client instance receives an access token to access a resource server through some valid GNAP process. The client instance uses that token at the RS for some time, but eventually the access token expires. The client instance then gets a refreshed access token by rotating the expired access token's value at the AS using the token management API.</t><figure title="Figure<!--[rfced] To reflect the title of Section 1.6.6 ("Refreshing an Expired Access Token"), may we update the title of Figure 8 as follows? Original: Figure 8: Figure 8: Diagram of the process of refreshing an accesstoken"><artset><artworktoken Perhaps: Figure 8: Diagram of the Process of Refreshing an Expired Access Token --> <figure> <name>Diagram of the Process of Refreshing an Access Token</name> <artset> <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="400" width="504" viewBox="0 0 504 400" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,32 L 8,384" fill="none" stroke="black"/> <path d="M 80,32 L 80,384" fill="none" stroke="black"/> <path d="M 320,128 L 320,288" fill="none" stroke="black"/> <path d="M 392,128 L 392,288" fill="none" stroke="black"/> <path d="M 424,32 L 424,384" fill="none" stroke="black"/> <path d="M 496,32 L 496,384" fill="none" stroke="black"/> <path d="M 8,32 L 80,32" fill="none" stroke="black"/> <path d="M 424,32 L 496,32" fill="none" stroke="black"/> <path d="M 80,64 L 104,64" fill="none" stroke="black"/> <path d="M 120,64 L 144,64" fill="none" stroke="black"/> <path d="M 280,64 L 416,64" fill="none" stroke="black"/> <path d="M 88,96 L 104,96" fill="none" stroke="black"/> <path d="M 120,96 L 144,96" fill="none" stroke="black"/> <path d="M 264,96 L 424,96" fill="none" stroke="black"/> <path d="M 320,128 L 392,128" fill="none" stroke="black"/> <path d="M 80,144 L 104,144" fill="none" stroke="black"/> <path d="M 120,144 L 144,144" fill="none" stroke="black"/> <path d="M 288,144 L 312,144" fill="none" stroke="black"/> <path d="M 88,176 L 104,176" fill="none" stroke="black"/> <path d="M 120,176 L 144,176" fill="none" stroke="black"/> <path d="M 296,176 L 320,176" fill="none" stroke="black"/> <path d="M 80,240 L 104,240" fill="none" stroke="black"/> <path d="M 120,240 L 144,240" fill="none" stroke="black"/> <path d="M 288,240 L 312,240" fill="none" stroke="black"/> <path d="M 88,272 L 104,272" fill="none" stroke="black"/> <path d="M 120,272 L 144,272" fill="none" stroke="black"/> <path d="M 280,272 L 320,272" fill="none" stroke="black"/> <path d="M 320,288 L 392,288" fill="none" stroke="black"/> <path d="M 80,320 L 104,320" fill="none" stroke="black"/> <path d="M 120,320 L 144,320" fill="none" stroke="black"/> <path d="M 264,320 L 416,320" fill="none" stroke="black"/> <path d="M 88,352 L 104,352" fill="none" stroke="black"/> <path d="M 120,352 L 144,352" fill="none" stroke="black"/> <path d="M 272,352 L 424,352" fill="none" stroke="black"/> <path d="M 8,384 L 80,384" fill="none" stroke="black"/> <path d="M 424,384 L 496,384" fill="none" stroke="black"/> <polygon class="arrowhead" points="424,320 412,314.4 412,325.6" fill="black" transform="rotate(0,416,320)"/> <polygon class="arrowhead" points="424,64 412,58.4 412,69.6" fill="black" transform="rotate(0,416,64)"/> <polygon class="arrowhead" points="320,240 308,234.4 308,245.6" fill="black" transform="rotate(0,312,240)"/> <polygon class="arrowhead" points="320,144 308,138.4 308,149.6" fill="black" transform="rotate(0,312,144)"/> <polygon class="arrowhead" points="96,352 84,346.4 84,357.6" fill="black" transform="rotate(180,88,352)"/> <polygon class="arrowhead" points="96,272 84,266.4 84,277.6" fill="black" transform="rotate(180,88,272)"/> <polygon class="arrowhead" points="96,176 84,170.4 84,181.6" fill="black" transform="rotate(180,88,176)"/> <polygon class="arrowhead" points="96,96 84,90.4 84,101.6" fill="black" transform="rotate(180,88,96)"/> <g class="text"> <text x="44" y="52">Client</text> <text x="460" y="52">AS</text> <text x="44" y="68">Instance</text> <text x="112" y="68">1</text> <text x="184" y="68">Request</text> <text x="244" y="68">Access</text> <text x="112" y="100">2</text> <text x="176" y="100">Grant</text> <text x="228" y="100">Access</text> <text x="112" y="148">3</text> <text x="180" y="148">Access</text> <text x="244" y="148">Resource</text> <text x="356" y="148">RS</text> <text x="112" y="180">4</text> <text x="184" y="180">Success</text> <text x="252" y="180">Response</text> <text x="144" y="212">(</text> <text x="172" y="212">Time</text> <text x="220" y="212">Passes</text> <text x="256" y="212">)</text> <text x="112" y="244">5</text> <text x="180" y="244">Access</text> <text x="244" y="244">Resource</text> <text x="112" y="276">6</text> <text x="176" y="276">Error</text> <text x="236" y="276">Response</text> <text x="112" y="324">7</text> <text x="180" y="324">Rotate</text> <text x="232" y="324">Token</text> <text x="112" y="356">8</text> <text x="184" y="356">Rotated</text> <text x="240" y="356">Token</text> </g> </svg></artwork><artwork</artwork> <artwork type="ascii-art"><![CDATA[ +--------+ +--------+ | Client | | AS | |Instance+--(1)--- Request Access ----------------->| | | | | | | |<-(2)--- Grant Access --------------------+ | | | | | | | +--------+ | | | +--(3)--- Access Resource --->| RS | | | | | | | | | | |<-(4)--- Success Response ---+ | | | | | | | | | | | ( Time Passes ) | | | | | | | | | | | +--(5)--- Access Resource --->| | | | | | | | | | | |<-(6)--- Error Response -----+ | | | | | +--------+ | | | | | | | +--(7)--- Rotate Token ------------------->| | | | | | | |<-(8)--- Rotated Token -------------------+ | | | | | +--------+ +--------+]]></artwork></artset></figure> <t><list style="numbers">]]></artwork> </artset> </figure> <ol spacing="normal" type="1"><li> <t>The client instance<xref target="request">requestsrequests access to theresource</xref>.</t>resource (<xref target="request"> </xref>).</t> </li> <li> <t>The AS<xref target="response">grantsgrants access to theresource</xref>resource (<xref target="response"> </xref>) with an<xref target="response-token">access token</xref>access token (<xref target="response-token"> </xref>) usable at the RS. The access token response includes a token management URI.</t> </li> <li> <t>The client instance<xref target="use-access-token">usesuses the accesstoken</xref>token (<xref target="use-access-token"> </xref>) to call the RS.</t> </li> <li> <t>The RS validates the access token and returns an appropriate response for the API.</t> </li> <li> <t>Time passes and the client instance uses the access token to call the RS again.</t> </li> <li> <t>The RS validates the access token and determines that the access token is expired. The RS responds to the client instance with an error.</t> </li> <li> <!-- [rfced] Clarification of sections a) Would it be helpful to include a section number to clarify "token rotation section"? Perhaps Section 6.1? Original: The client instance uses the access token (Section 7.2) in this call as well as the appropriate key, see the token rotation section for details. Perhaps: The client instance uses the access token (Section 7.2) in this call as well as the appropriate key; see Section 6.1 for details. b) Would it also be helpful to add a section pointer here to clarify "section on subject information"? Perhaps Section 3.4? Original: Note that the AS can restrict the subject information returned and it might not match what the client instance requested, see the section on subject information for details. Perhaps: Note that the AS can restrict the subject information returned, and it might not match what the client instance requested; see Section 3.4 for details. c) FYI - We updated "as specified in requesting a single access token (Section 2.1.1)" as follows. Please let us know any concerns. Original: Each object MUST conform to the request format for a single access token request, as specified in requesting a single access token (Section 2.1.1). Updated: Each object MUST conform to the request format for a single access token request, as specified in Section 2.1.1. --> <t>The client instance calls the token management URI returned in (2) to<xref target="rotate-access-token">rotaterotate the accesstoken</xref>.token (<xref target="rotate-access-token"> </xref>). The client instance<xref target="use-access-token">usesuses the accesstoken</xref>token (<xref target="use-access-token"> </xref>) in this call as well as the appropriatekey,key; see the token rotation section for details.</t> </li> <li> <t>The AS validates the rotationrequestrequest, including the signature and keys presented in(7)(7), and refreshes the<xref target="response-token-single">access token</xref>.access token (<xref target="response-token-single"> </xref>). The response includes a new version of the access token and can also include updated token management information, which the client instance will store in place of the values returned in (2).</t></list></t></li> </ol> </section> <sectionanchor="sequence-user"><name>Requestinganchor="sequence-user"> <name>Requesting Subject Information Only</name> <t>In this scenario, the client instance does not call an RS and does not request an access token. Instead, the client instance only requests and is returned<xref target="response-subject">directdirect subjectinformation</xref>.information (<xref target="response-subject"></xref>). Many different interaction modes can be used in this scenario, so these are shown only in the abstract as functions of the AS here.</t><figure title="Figure 9: Diagram<figure> <name>Diagram of theprocessProcess ofrequestingRequesting andreleasing subject informationReleasing Subject Information apart fromaccess tokens"><artset><artworkAccess Tokens</name> <artset> <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="384" width="576" viewBox="0 0 576 384" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,32 L 8,368" fill="none" stroke="black"/> <path d="M 80,32 L 80,368" fill="none" stroke="black"/> <path d="M 360,32 L 360,128" fill="none" stroke="black"/> <path d="M 360,160 L 360,256" fill="none" stroke="black"/> <path d="M 360,288 L 360,368" fill="none" stroke="black"/> <path d="M 432,32 L 432,128" fill="none" stroke="black"/> <path d="M 432,160 L 432,256" fill="none" stroke="black"/> <path d="M 432,288 L 432,368" fill="none" stroke="black"/> <path d="M 512,48 L 512,272" fill="none" stroke="black"/> <path d="M 568,48 L 568,272" fill="none" stroke="black"/> <path d="M 8,32 L 80,32" fill="none" stroke="black"/> <path d="M 360,32 L 432,32" fill="none" stroke="black"/> <path d="M 528,32 L 552,32" fill="none" stroke="black"/> <path d="M 80,80 L 104,80" fill="none" stroke="black"/> <path d="M 120,80 L 144,80" fill="none" stroke="black"/> <path d="M 280,80 L 352,80" fill="none" stroke="black"/> <path d="M 88,112 L 104,112" fill="none" stroke="black"/> <path d="M 120,112 L 136,112" fill="none" stroke="black"/> <path d="M 304,112 L 360,112" fill="none" stroke="black"/> <path d="M 80,142 L 104,142" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 80,146 L 104,146" fill="none" stroke="black"/> <path d="M 120,142 L 136,142" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 120,146 L 136,146" fill="none" stroke="black"/> <path d="M 336,142 L 504,142" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 336,146 L 504,146" fill="none" stroke="black"/> <path d="M 512,160 L 568,160" fill="none" stroke="black"/> <path d="M 440,174 L 464,174" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 440,178 L 464,178" fill="none" stroke="black"/> <path d="M 480,174 L 504,174" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 480,178 L 504,178" fill="none" stroke="black"/> <path d="M 440,222 L 464,222" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 440,226 L 464,226" fill="none" stroke="black"/> <path d="M 480,222 L 504,222" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 480,226 L 504,226" fill="none" stroke="black"/> <path d="M 512,240 L 568,240" fill="none" stroke="black"/> <path d="M 88,270 L 104,270" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 88,274 L 104,274" fill="none" stroke="black"/> <path d="M 120,270 L 136,270" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 120,274 L 136,274" fill="none" stroke="black"/> <path d="M 312,270 L 512,270" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 312,274 L 512,274" fill="none" stroke="black"/> <path d="M 528,288 L 552,288" fill="none" stroke="black"/> <path d="M 80,304 L 104,304" fill="none" stroke="black"/> <path d="M 120,304 L 144,304" fill="none" stroke="black"/> <path d="M 296,304 L 352,304" fill="none" stroke="black"/> <path d="M 88,336 L 104,336" fill="none" stroke="black"/> <path d="M 120,336 L 160,336" fill="none" stroke="black"/> <path d="M 280,336 L 360,336" fill="none" stroke="black"/> <path d="M 8,368 L 80,368" fill="none" stroke="black"/> <path d="M 360,368 L 432,368" fill="none" stroke="black"/> <path d="M 528,32 C 519.16936,32 512,39.16936 512,48" fill="none" stroke="black"/> <path d="M 552,32 C 560.83064,32 568,39.16936 568,48" fill="none" stroke="black"/> <path d="M 528,288 C 519.16936,288 512,280.83064 512,272" fill="none" stroke="black"/> <path d="M 552,288 C 560.83064,288 568,280.83064 568,272" fill="none" stroke="black"/> <polygon class="arrowhead" points="512,224 500,218.4 500,229.6" fill="black" transform="rotate(0,504,224)"/> <polygon class="arrowhead" points="512,176 500,170.4 500,181.6" fill="black" transform="rotate(0,504,176)"/> <polygon class="arrowhead" points="512,144 500,138.4 500,149.6" fill="black" transform="rotate(0,504,144)"/> <polygon class="arrowhead" points="448,224 436,218.4 436,229.6" fill="black" transform="rotate(180,440,224)"/> <polygon class="arrowhead" points="448,176 436,170.4 436,181.6" fill="black" transform="rotate(180,440,176)"/> <polygon class="arrowhead" points="360,304 348,298.4 348,309.6" fill="black" transform="rotate(0,352,304)"/> <polygon class="arrowhead" points="360,80 348,74.4 348,85.6" fill="black" transform="rotate(0,352,80)"/> <polygon class="arrowhead" points="96,336 84,330.4 84,341.6" fill="black" transform="rotate(180,88,336)"/> <polygon class="arrowhead" points="96,272 84,266.4 84,277.6" fill="black" transform="rotate(180,88,272)"/> <polygon class="arrowhead" points="96,112 84,106.4 84,117.6" fill="black" transform="rotate(180,88,112)"/> <g class="text"> <text x="44" y="52">Client</text> <text x="396" y="52">AS</text> <text x="536" y="52">End</text> <text x="44" y="68">Instance</text> <text x="540" y="68">User</text> <text x="112" y="84">1</text> <text x="184" y="84">Request</text> <text x="244" y="84">Access</text> <text x="112" y="116">2</text> <text x="192" y="116">Interaction</text> <text x="268" y="116">Needed</text> <text x="112" y="148">3</text> <text x="188" y="148">Facilitate</text> <text x="280" y="148">Interaction</text> <text x="472" y="180">4</text> <text x="540" y="180">RO</text> <text x="472" y="196">AuthN</text> <text x="472" y="228">5</text> <text x="472" y="244">AuthZ</text> <text x="536" y="260">End</text> <text x="112" y="276">6</text> <text x="172" y="276">Signal</text> <text x="252" y="276">Continuation</text> <text x="540" y="276">User</text> <text x="112" y="308">7</text> <text x="188" y="308">Continue</text> <text x="256" y="308">Request</text> <text x="112" y="340">8</text> <text x="192" y="340">Grant</text> <text x="244" y="340">Access</text> </g> </svg></artwork><artwork</artwork> <artwork type="ascii-art"><![CDATA[ +--------+ +--------+ .----. | Client | | AS | | End | |Instance| | | | User | | +--(1)--- Request Access --------->| | | | | | | | | | | |<-(2)-- Interaction Needed -------+ | | | | | | | | | | +==(3)== Facilitate Interaction =====================>| | | | | | +------+ | | | |<==(4)==>| RO | | | | | AuthN | | | | | | | | | | | |<==(5)==>| | | | | | AuthZ +------+ | | | | | End | | |<=(6)== Signal Continuation =========================+ User | | | | | `----` | +--(7)--- Continue Request ------->| | | | | | | |<-(8)----- Grant Access ----------+ | | | | | +--------+ +--------+]]></artwork></artset></figure> <t><list style="numbers">]]></artwork> </artset> </figure> <ol spacing="normal" type="1"><li> <t>The client instance<xref target="request">requestsrequests access to subjectinformation</xref>.</t>information (<xref target="request"> </xref>).</t> </li> <li> <t>The AS determines that interaction is needed and<xref target="response">responds</xref>responds (<xref target="response"> </xref>) with appropriate information for<xref target="response-interact">facilitatingfacilitating userinteraction</xref>.</t>interaction (<xref target="response-interact"> </xref>).</t> </li> <li> <t>The client instance facilitates<xref target="authorization">thethe user interacting with theAS</xref>AS (<xref target="authorization"> </xref>) as directed in (2).</t> </li> <li> <t>The user authenticates at the AS, taking on the role of the RO.</t> </li> <li> <t>As the RO, the user authorizes the pending request from the client instance.</t> </li> <li> <t>When the AS is done interacting with the user, the AS returns the user to the client instance and signals continuation.</t> </li> <li> <t>The client instance loads the continuation information from (2) and calls the AS to<xref target="continue-request">continuecontinue therequest</xref>.</t>request (<xref target="continue-request"> </xref>).</t> </li> <li> <t>If the request has been authorized, the AS grants access to the requested<xref target="response-subject">directdirect subjectinformation</xref>information (<xref target="response-subject"> </xref>) to the client instance. At this stage, the user is generally considered "logged in" to the client instance based on the identifiers and assertions provided by the AS. Note that the AS can restrict the subject informationreturnedreturned, and it might not match what the client instancerequested,requested; see the section on subject information for details.</t></list></t></li> </ol> </section> <sectionanchor="sequence-cross-user"><name>Cross-Useranchor="sequence-cross-user"> <name>Cross-User Authentication</name> <t>In this scenario, the end user and resource owner are two different people. Here, the client instance already knows who the end user is, likely through a separate authentication process. The end user, operating the client instance, needs to get subject information about another person in the system, the RO. The RO is given an opportunity to release this information using an asynchronous interaction method with the AS. This scenario would apply, for instance, when the end user is an agent in acall-centercall center and the resource owner is a customer authorizing thecall centercall-center agent to access their account on their behalf.</t><figure title="Figure 10: Diagram<figure> <name>Diagram ofcross-user authorization, whereCross-User Authorization, Where theend userEnd User and ROare different"><artset><artworkAre Different</name> <artset> <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="480" width="576" viewBox="0 0 576 480" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,48 L 8,448" fill="none" stroke="black"/> <path d="M 64,48 L 64,448" fill="none" stroke="black"/> <path d="M 136,96 L 136,464" fill="none" stroke="black"/> <path d="M 208,96 L 208,464" fill="none" stroke="black"/> <path d="M 360,96 L 360,464" fill="none" stroke="black"/> <path d="M 432,96 L 432,464" fill="none" stroke="black"/> <path d="M 512,48 L 512,448" fill="none" stroke="black"/> <path d="M 568,48 L 568,448" fill="none" stroke="black"/> <path d="M 24,32 L 48,32" fill="none" stroke="black"/> <path d="M 528,32 L 552,32" fill="none" stroke="black"/> <path d="M 72,62 L 216,62" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 72,66 L 216,66" fill="none" stroke="black"/> <path d="M 232,62 L 248,62" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 232,66 L 248,66" fill="none" stroke="black"/> <path d="M 360,62 L 504,62" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 360,66 L 504,66" fill="none" stroke="black"/> <path d="M 136,96 L 208,96" fill="none" stroke="black"/> <path d="M 360,96 L 432,96" fill="none" stroke="black"/> <path d="M 64,110 L 88,110" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 64,114 L 88,114" fill="none" stroke="black"/> <path d="M 104,110 L 128,110" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 104,114 L 128,114" fill="none" stroke="black"/> <path d="M 208,160 L 232,160" fill="none" stroke="black"/> <path d="M 248,160 L 264,160" fill="none" stroke="black"/> <path d="M 320,160 L 352,160" fill="none" stroke="black"/> <path d="M 216,192 L 232,192" fill="none" stroke="black"/> <path d="M 248,192 L 264,192" fill="none" stroke="black"/> <path d="M 320,192 L 360,192" fill="none" stroke="black"/> <path d="M 440,206 L 464,206" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 440,210 L 464,210" fill="none" stroke="black"/> <path d="M 480,206 L 504,206" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 480,210 L 504,210" fill="none" stroke="black"/> <path d="M 440,254 L 464,254" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 440,258 L 464,258" fill="none" stroke="black"/> <path d="M 480,254 L 504,254" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 480,258 L 504,258" fill="none" stroke="black"/> <path d="M 440,302 L 464,302" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 440,306 L 464,306" fill="none" stroke="black"/> <path d="M 480,302 L 504,302" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 480,306 L 504,306" fill="none" stroke="black"/> <path d="M 216,320 L 232,320" fill="none" stroke="black"/> <path d="M 248,320 L 272,320" fill="none" stroke="black"/> <path d="M 344,320 L 360,320" fill="none" stroke="black"/> <path d="M 208,352 L 232,352" fill="none" stroke="black"/> <path d="M 248,352 L 272,352" fill="none" stroke="black"/> <path d="M 336,352 L 352,352" fill="none" stroke="black"/> <path d="M 216,384 L 232,384" fill="none" stroke="black"/> <path d="M 256,384 L 272,384" fill="none" stroke="black"/> <path d="M 336,384 L 360,384" fill="none" stroke="black"/> <path d="M 72,398 L 88,398" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 72,402 L 88,402" fill="none" stroke="black"/> <path d="M 112,398 L 136,398" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 112,402 L 136,402" fill="none" stroke="black"/> <path d="M 24,464 L 48,464" fill="none" stroke="black"/> <path d="M 136,464 L 208,464" fill="none" stroke="black"/> <path d="M 360,464 L 432,464" fill="none" stroke="black"/> <path d="M 528,464 L 552,464" fill="none" stroke="black"/> <path d="M 24,32 C 15.16936,32 8,39.16936 8,48" fill="none" stroke="black"/> <path d="M 48,32 C 56.83064,32 64,39.16936 64,48" fill="none" stroke="black"/> <path d="M 528,32 C 519.16936,32 512,39.16936 512,48" fill="none" stroke="black"/> <path d="M 552,32 C 560.83064,32 568,39.16936 568,48" fill="none" stroke="black"/> <path d="M 24,464 C 15.16936,464 8,456.83064 8,448" fill="none" stroke="black"/> <path d="M 48,464 C 56.83064,464 64,456.83064 64,448" fill="none" stroke="black"/> <path d="M 528,464 C 519.16936,464 512,456.83064 512,448" fill="none" stroke="black"/> <path d="M 552,464 C 560.83064,464 568,456.83064 568,448" fill="none" stroke="black"/> <polygon class="arrowhead" points="512,304 500,298.4 500,309.6" fill="black" transform="rotate(0,504,304)"/> <polygon class="arrowhead" points="512,256 500,250.4 500,261.6" fill="black" transform="rotate(0,504,256)"/> <polygon class="arrowhead" points="512,208 500,202.4 500,213.6" fill="black" transform="rotate(0,504,208)"/> <polygon class="arrowhead" points="512,64 500,58.4 500,69.6" fill="black" transform="rotate(0,504,64)"/> <polygon class="arrowhead" points="448,304 436,298.4 436,309.6" fill="black" transform="rotate(180,440,304)"/> <polygon class="arrowhead" points="448,256 436,250.4 436,261.6" fill="black" transform="rotate(180,440,256)"/> <polygon class="arrowhead" points="448,208 436,202.4 436,213.6" fill="black" transform="rotate(180,440,208)"/> <polygon class="arrowhead" points="360,352 348,346.4 348,357.6" fill="black" transform="rotate(0,352,352)"/> <polygon class="arrowhead" points="360,160 348,154.4 348,165.6" fill="black" transform="rotate(0,352,160)"/> <polygon class="arrowhead" points="224,384 212,378.4 212,389.6" fill="black" transform="rotate(180,216,384)"/> <polygon class="arrowhead" points="224,320 212,314.4 212,325.6" fill="black" transform="rotate(180,216,320)"/> <polygon class="arrowhead" points="224,192 212,186.4 212,197.6" fill="black" transform="rotate(180,216,192)"/> <polygon class="arrowhead" points="136,112 124,106.4 124,117.6" fill="black" transform="rotate(0,128,112)"/> <polygon class="arrowhead" points="80,400 68,394.4 68,405.6" fill="black" transform="rotate(180,72,400)"/> <polygon class="arrowhead" points="80,64 68,58.4 68,69.6" fill="black" transform="rotate(180,72,64)"/> <g class="text"> <text x="32" y="52">End</text> <text x="540" y="52">RO</text> <text x="36" y="68">User</text> <text x="224" y="68">1</text> <text x="292" y="68">Identify</text> <text x="340" y="68">RO</text> <text x="96" y="116">2</text> <text x="172" y="116">Client</text> <text x="396" y="116">AS</text> <text x="84" y="132">RO</text> <text x="108" y="132">ID</text> <text x="172" y="132">Instance</text> <text x="240" y="164">3</text> <text x="292" y="164">Req.</text> <text x="240" y="196">4</text> <text x="292" y="196">Res.</text> <text x="472" y="212">5</text> <text x="472" y="228">AuthN</text> <text x="472" y="260">6</text> <text x="472" y="276">AuthZ</text> <text x="472" y="308">7</text> <text x="240" y="324">8</text> <text x="308" y="324">Finish</text> <text x="472" y="324">Completed</text> <text x="240" y="356">9</text> <text x="304" y="356">Cont.</text> <text x="244" y="388">10</text> <text x="304" y="388">Subj.</text> <text x="100" y="404">11</text> <text x="300" y="404">Info</text> <text x="100" y="420">Return</text> <text x="84" y="436">RO</text> <text x="92" y="452">Info</text> </g> </svg></artwork><artwork</artwork> <artwork type="ascii-art"><![CDATA[ .----. .----. | End | | RO | | User |<=================(1)== Identify RO ==================>| | | | | | | | +--------+ +--------+ | | | +==(2)==>| Client | | AS | | | | | RO ID |Instance| | | | | | | | | | | | | | | | +--(3)-- Req. ---->| | | | | | | | | | | | | | | |<-(4)-- Res. -----+ | | | | | | | | |<==(5)==>| | | | | | | | AuthN | | | | | | | | | | | | | | | |<==(6)==>| | | | | | | | AuthZ | | | | | | | | | | | | | | | |<==(7)==>| | | | | |<-(8)--- Finish --+ |Completed| | | | | | | | | | | | | +--(9)--- Cont. -->| | | | | | | | | | | | | | | |<-(10)-- Subj. ---+ | | | | |<=(11)==+ | Info | | | | | | Return | | | | | | | | RO | | | | | | | | Info | | | | | | `----` +--------+ +--------+ `----`]]></artwork></artset></figure>]]></artwork> </artset> </figure> <t>Precondition: The end user is authenticated to the client instance, and the client instance has an identifier representing the end user that it can present to the AS. This identifier should be unique to the particular session with the client instance and the AS. The client instance is also known to the AS and allowed to access this advanced functionality where the information of someone other than the end user is returned to the client instance.</t><t><list style="numbers"><ol spacing="normal" type="1"><li> <t>The RO communicates a human-readable identifier to the end user, such as an email address or account number. This communication happens out of band from the protocol, such as over the phone between parties. Note that the RO is not interacting with the client instance.</t> </li> <li> <t>The end user communicates the identifier to the client instance. The means by which the identifier is communicated to the client instanceisare out of scope for this specification.</t> </li> <!-- [rfced] We have a few questions about the sentence below. a) May we update "subject information request (Section 2.2) sub_ids field" as follows? b) We see '"user" field' (not 'user information field') in Section 2.4. Should the sentence be updated accordingly? c) Is "of the request" needed at the end of the sentence? The sentence begins with "The request includes...". Original: The request includes the RO's identifier in the subject information request (Section 2.2) sub_ids field, and the end user's identifier in the user information field (Section 2.4) of the request. Perhaps: The request includes the RO's identifier in the sub_ids field of the subject information request (Section 2.2) and the end user's identifier in the "user" field (Section 2.4). --> <li> <t>The client instance<xref target="request">requestsrequests access to subjectinformation</xref>.information (<xref target="request"> </xref>). The request includes the RO's identifier in the<xref target="request-subject">subjectsubject informationrequest</xref> <spanx style="verb">sub_ids</spanx> field,request (<xref target="request-subject"> </xref>) <tt>sub_ids</tt> field and the end user's identifier in the<xref target="request-user">useruser informationfield</xref>field (<xref target="request-user"> </xref>) of the request. The request includes no interaction start methods, since the end user is not expected to be the one interacting with the AS. The request does include the<xref target="request-interact-callback-push">push basedpush-based interaction finishmethod</xref>method (<xref target="request-interact-callback-push"> </xref>) to allow the AS to signal to the client instance when the interaction with the RO has concluded.</t> </li> <li> <t>The AS sees that theidentifieridentifiers for the end user and subject being requested are different. The AS determines that it can reach out to the RO asynchronously for approval. While it is doing so, the AS returns a<xref target="response-continue">continuation response</xref>continuation response (<xref target="response-continue"> </xref>) with a<spanx style="verb">finish</spanx><tt>finish</tt> nonce to allow the client instance to continue the grant request after interaction with the RO has concluded.</t> </li> <li> <t>The AS contacts the RO and has them authenticate to the system. The means for doing this are outside the scope of this specification, but the identity of the RO is known from the subject identifier sent in (3).</t> </li> <li> <t>The RO is prompted to authorize the end user's request via the client instance. Since the end user was identified in (3) via the user field, the AS can show this information to the RO during the authorization request.</t> </li> <li> <t>The RO completes the authorization with the AS. The AS marks the request as <em>approved</em>.</t> </li> <li> <t>The RO pushes the<xref target="interaction-pushback">interactioninteraction finishmessage</xref>message (<xref target="interaction-pushback"> </xref>) to the client instance. Note that in the case the RO cannot be reached or the RO denies the request, the AS still sends the interaction finish message to the client instance, after which the client instance can negotiate next steps if possible.</t> </li> <li> <t>The client instance validates the interaction finish message and<xref target="continue-after-interaction">continuescontinues the grantrequest</xref>.</t>request (<xref target="continue-after-interaction"> </xref>).</t> </li> <li> <t>The AS returns the RO's<xref target="response-subject">subject information</xref>subject information (<xref target="response-subject"> </xref>) to the client instance.</t> </li> <li> <t>The client instance can display or otherwise utilize the RO's user information in its session with the end user. Note that since the client instance requested different sets of user information in (3), the client instance does not conflate the end user with the RO.</t></list></t></li> </ol> <t>Additional considerations for asynchronous interactions like this are discussed in <xref target="security-async"/>.</t> </section> </section> </section> <sectionanchor="request"><name>Requestinganchor="request"> <name>Requesting Access</name> <t>To start a request, the client instance sends an HTTP POST with a JSON <xreftarget="RFC8259">JSON</xref>target="RFC8259"> </xref> document to the grant endpoint of the AS. The grant endpoint is a URI that uniquely identifies the AS to client instances and serves as the identifier for the AS. The document is a JSON object where each field represents a different aspect of the client instance's request. Each field is described in detail in asectionsubsection below.</t> <dl><dt><spanx style="verb">access_token</spanx><dt><tt>access_token</tt> (object / array of objects):</dt> <dd> <t>Describes the rights and properties associated with the requested access token. <bcp14>REQUIRED</bcp14> if requesting an access token. See <xref target="request-token"/>.</t> </dd><dt><spanx style="verb">subject</spanx><dt><tt>subject</tt> (object):</dt> <dd> <t>Describes the information about the RO that the client instance is requesting to be returned directly in the response from the AS. <bcp14>REQUIRED</bcp14> if requesting subject information. See <xref target="request-subject"/>.</t> </dd><dt><spanx style="verb">client</spanx><dt><tt>client</tt> (object / string):</dt> <dd> <t>Describes the client instance that is making this request, including the key that the client instance will use to protect thisrequest andrequest, any continuation requests at theASAS, and any user-facing information about the client instance used in interactions. <bcp14>REQUIRED</bcp14>. See <xref target="request-client"/>.</t> </dd><dt><spanx style="verb">user</spanx><dt><tt>user</tt> (object / string):</dt> <dd> <t>Identifies the end user to the AS in a manner that the AS can verify, either directly or by interacting with the end user to determine their status as the RO. <bcp14>OPTIONAL</bcp14>. See <xref target="request-user"/>.</t> </dd><dt><spanx style="verb">interact</spanx><dt><tt>interact</tt> (object):</dt> <dd> <t>Describes the modes that the client instance supports for allowing the RO to interact with the AS and modes for the client instance to receive updates when interaction is complete. <bcp14>REQUIRED</bcp14> if interaction is supported. See <xref target="request-interact"/>.</t> </dd> </dl> <!--[rfced] FYI - We have updated instances of "are defined by" and "are defined in" to be "can be defined in". Please let us know of any objections. Some examples: Original: Additional assertion formats are defined by the GNAP Assertion Formats Registry (Section 11.6). Additional fields are defined in the GNAP Subject Information Request Fields Registry (Section 11.5). Additional fields are defined in the GNAP Client Instance Fields Registry (Section 11.7). This specification defines the following values for the method parameter, with other values defined by the GNAP Interaction Finish Methods Registry (Section 11.10): Current: Additional assertion formats can be defined in the "GNAP Assertion Formats" registry (Section 11.6). Additional fields can be defined in the "GNAP Subject Information Request Fields" registry (Section 11.5). Additional fields can be defined in the "GNAP Client Instance Fields" registry (Section 11.7). This specification defines the following values for the method parameter; additional values can be defined in the GNAP Interaction Finish Methods" registry (Section 11.10): --> <t>Additional members of this request object can be defined by extensions using the<xref target="IANA-grant-request">GNAP"GNAP Grant RequestParameters Registry</xref>.</t>Parameters" registry (<xref target="IANA-grant-request"></xref>).</t> <t>A non-normative example of a grant request is below:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "access_token": { "access": [ { "type": "photo-api", "actions": [ "read", "write", "dolphin" ], "locations": [ "https://server.example.net/", "https://resource.local/other" ], "datatypes": [ "metadata", "images" ] }, "dolphin-metadata" ] }, "client": { "display": { "name": "My Client Display Name", "uri": "https://example.net/client" }, "key": { "proof": "httpsig", "jwk": { "kty": "RSA", "e": "AQAB", "kid": "xyz-1", "alg": "RS256", "n": "kOB5rR4Jv0GMeL...." } } }, "interact": { "start": ["redirect"], "finish": { "method": "redirect", "uri": "https://client.example.net/return/123455", "nonce": "LKLTI25DK82FX4T4QFZC" } }, "subject": { "sub_id_formats": ["iss_sub", "opaque"], "assertion_formats": ["id_token"] } }]]></sourcecode></figure>]]></sourcecode> <t>Sending a request to the grant endpoint creates a grant request in the <em>processing</em> state. The AS processes this request to determine whether interaction or authorization are necessary (moving to the <em>pending</em>state),state) or if access can be granted immediately (moving to the <em>approved</em> state).</t> <t>The request <bcp14>MUST</bcp14> be sent as a JSON object in the content of the HTTP POST request with Content-Type<spanx style="verb">application/json</spanx>.<tt>application/json</tt>. A key proofing mechanism <bcp14>MAY</bcp14> define an alternative content type, as long as the content is formed from the JSON object. For example, the attachedJWSJSON Web Signature (JWS) key proofing mechanism (see <xref target="attached-jws"/>) places the JSON object into the payload of a JWS wrapper, which is in turn sent as the message content.</t> <sectionanchor="request-token"><name>Requestinganchor="request-token"> <name>Requesting Access to Resources</name> <t>If the client instance is requesting one or more access tokens for the purpose of accessing an API, the client instance <bcp14>MUST</bcp14> include an<spanx style="verb">access_token</spanx><tt>access_token</tt> field. This field <bcp14>MUST</bcp14> be an object (for a<xref target="request-token-single">singlesingle accesstoken</xref>)token (<xref target="request-token-single"> </xref>)) or an array of these objects (for<xref target="request-token-multiple">multiplemultiple accesstokens</xref>),tokens (<xref target="request-token-multiple"> </xref>)), as described in the followingsections.</t>subsections.</t> <sectionanchor="request-token-single"><name>Requestinganchor="request-token-single"> <name>Requesting a Single Access Token</name> <t>To request a single access token, the client instance sends an<spanx style="verb">access_token</spanx><tt>access_token</tt> object composed of the following fields.</t> <dl><dt><spanx style="verb">access</spanx><dt><tt>access</tt> (array of objects/strings):</dt> <dd> <t>Describes the rights that the client instance is requesting for the access token to be used at the RS. <bcp14>REQUIRED</bcp14>. See <xref target="resource-access-rights"/>.</t> </dd><dt><spanx style="verb">label</spanx><dt><tt>label</tt> (string):</dt> <dd> <!-- [rfced] Would rephrasing "multiple access tokens request", "multiple access tokens response structure", and "multiple access tokens structure" as follows improve readability? Current: If this field is included in the request, the AS MUST include the same label in the token response (Section 3.2). REQUIRED if used as part of a multiple access tokens request (Section 2.1.2); OPTIONAL otherwise. ... All approved access requests are returned in the multiple access token response structure (Section 3.2.2) using the values of the label fields in the request. ... If the client instance requested a single access token (Section 2.1.1), the AS MUST NOT respond with the multiple access tokens structure. ... Each object MUST have a unique label field, corresponding to the token labels chosen by the client instance in the multiple access tokens request (Section 2.1.2). ... In such cases, the AS MUST respond with a multiple access tokens structure containing one access token. Perhaps: If this field is included in the request, the AS MUST include the same label in the token response (Section 3.2). REQUIRED if used as part of a request for multiple access tokens (Section 2.1.2); OPTIONAL otherwise. ... All approved access requests are returned in the response structure for multiple access tokens (Section 3.2.2) using the values of the label fields in the request. ... If the client instance requested a single access token (Section 2.1.1), the AS MUST NOT respond with the structure for multiple access tokens. ... Each object MUST have a unique label field, corresponding to the token labels chosen by the client instance in the request for multiple access tokens (Section 2.1.2). ... In such cases, the AS MUST respond with a structure for multiple access tokens containing one access token. --> <t>A unique name chosen by the client instance to refer to the resulting access token. The value of this field is opaque to the AS and is not intended to be exposed to or used by the end user. If this field is included in the request, the AS <bcp14>MUST</bcp14> include the same label in the<xref target="response-token">token response</xref>.token response (<xref target="response-token"> </xref>). <bcp14>REQUIRED</bcp14> if used as part of a<xref target="request-token-multiple">multiplemultiple accesstoken request</xref>,tokens request (<xref target="request-token-multiple"> </xref>); <bcp14>OPTIONAL</bcp14> otherwise.</t> </dd><dt><spanx style="verb">flags</spanx><dt><tt>flags</tt> (array of strings):</dt> <dd> <t>A set of flags that indicate desired attributes or behavior to be attached to the access token by the AS. <bcp14>OPTIONAL</bcp14>.</t> </dd> </dl> <t>The values of the<spanx style="verb">flags</spanx><tt>flags</tt> field defined by this specification are as follows:</t> <dl><dt><spanx style="verb">"bearer"</spanx>:</dt><dt><tt>"bearer"</tt>:</dt> <dd> <t>If this flag is included, the access token being requested is a bearer token. If this flag is omitted, the access token is bound to the key used by the client instance in this request (or that key's most recentrotation)rotation), and the access token <bcp14>MUST</bcp14> be presented using the same key and proofing method. Methods for presenting bound and bearer access tokens are described in <xref target="use-access-token"/>. See <xref target="security-bearer-tokens"/> for additional considerations on the use of bearer tokens.</t> </dd> </dl> <t>Flag values <bcp14>MUST NOT</bcp14> be included more than once. If the request includes a flag value multiple times, the AS <bcp14>MUST</bcp14> return an<spanx style="verb">invalid_flag</spanx><tt>invalid_flag</tt> error defined in <xref target="response-error"/>.</t> <t>Additional flags can be defined by extensions using the<xref target="IANA-token-flags">GNAP"GNAP Access TokenFlags Registry</xref>.</t>Flags" registry (<xref target="IANA-token-flags"></xref>).</t> <t>In the following non-normative example, the client instance is requesting access to a complex resource described by a pair of access request object.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "access_token": { "access": [ { "type": "photo-api", "actions": [ "read", "write", "delete" ], "locations": [ "https://server.example.net/", "https://resource.local/other" ], "datatypes": [ "metadata", "images" ] }, { "type": "walrus-access", "actions": [ "foo", "bar" ], "locations": [ "https://resource.other/" ], "datatypes": [ "data", "pictures", "walrus whiskers" ] } ], "label": "token1-23" }]]></sourcecode></figure>]]></sourcecode> <t>If access is approved, the resulting access token is valid for the described resource. Since the "bearer" flag is not provided in this example, the token is bound to the client instance's key (or its most recent rotation). The token is labeled "token1-23". The token response structure is described in <xref target="response-token-single"/>.</t> </section> <sectionanchor="request-token-multiple"><name>Requestinganchor="request-token-multiple"> <name>Requesting Multiple Access Tokens</name> <t>To request that multiple access tokenstobe returned in a single response, the client instance sends an array of objects as the value of the<spanx style="verb">access_token</spanx><tt>access_token</tt> parameter. Each object <bcp14>MUST</bcp14> conform to the request format for a single access token request, as specified in <xreftarget="request-token-single">requesting a single access token</xref>.target="request-token-single"></xref>. Additionally, each object in the array <bcp14>MUST</bcp14> include the<spanx style="verb">label</spanx><tt>label</tt> field, and all values of these fields <bcp14>MUST</bcp14> be unique within the request. If the client instance does not include a<spanx style="verb">label</spanx><tt>label</tt> value for any entry in thearray,array or the values of the<spanx style="verb">label</spanx><tt>label</tt> field are not unique within the array, the AS <bcp14>MUST</bcp14> return an "invalid_request" error (<xref target="response-error"/>).</t> <t>The following non-normative example shows a request for two separate accesstokens, <spanx style="verb">token1</spanx>tokens: <tt>token1</tt> and<spanx style="verb">token2</spanx>.</t> <figure><sourcecode<tt>token2</tt>.</t> <sourcecode type="json"><![CDATA[ "access_token": [ { "label": "token1", "access": [ { "type": "photo-api", "actions": [ "read", "write", "dolphin" ], "locations": [ "https://server.example.net/", "https://resource.local/other" ], "datatypes": [ "metadata", "images" ] }, "dolphin-metadata" ] }, { "label": "token2", "access": [ { "type": "walrus-access", "actions": [ "foo", "bar" ], "locations": [ "https://resource.other/" ], "datatypes": [ "data", "pictures", "walrus whiskers" ] } ], "flags": [ "bearer" ] } ]]]></sourcecode></figure>]]></sourcecode> <t>All approved access requests are returned in the<xref target="response-token-multiple">multiplemultiple accesstoken response</xref>tokens response structure (<xref target="response-token-multiple"> </xref>) using the values of the<spanx style="verb">label</spanx><tt>label</tt> fields in the request.</t> </section> </section> <sectionanchor="request-subject"><name>Requestinganchor="request-subject"> <name>Requesting Subject Information</name> <t>If the client instance is requesting information about the RO from the AS, it sends a<spanx style="verb">subject</spanx><tt>subject</tt> field as a JSON object. This object <bcp14>MAY</bcp14> contain the following fields.</t> <dl><dt><spanx style="verb">sub_id_formats</spanx><dt><tt>sub_id_formats</tt> (array of strings):</dt> <dd> <t>An array of subject identifier subject formats requested for the RO, as defined by <xref target="RFC9493"/>. <bcp14>REQUIRED</bcp14> if subject identifiers are requested.</t> </dd><dt><spanx style="verb">assertion_formats</spanx><dt><tt>assertion_formats</tt> (array of strings):</dt> <dd> <t>An array of requested assertion formats. Possible values include<spanx style="verb">id_token</spanx><tt>id_token</tt> for an OpenID Connect ID Token(<xref target="OIDC"/>)<xref target="OIDC"/> and<spanx style="verb">saml2</spanx><tt>saml2</tt> for aSAMLSecurity Assertion Markup Language (SAML) 2 assertion(<xref target="SAML2"/>).<xref target="SAML2"/>. Additional assertion formatsarecan be definedbyin the<xref target="IANA-assertion-formats">GNAP"GNAP AssertionFormats Registry</xref>.Formats" registry (<xref target="IANA-assertion-formats"></xref>). <bcp14>REQUIRED</bcp14> if assertions are requested.</t> </dd><dt><spanx style="verb">sub_ids</spanx><dt><tt>sub_ids</tt> (array of objects):</dt> <dd> <t>An array of subject identifiers representing the subject for which information is being requested. Each object is a subject identifier as defined by <xref target="RFC9493"/>. All identifiers in the<spanx style="verb">sub_ids</spanx><tt>sub_ids</tt> array <bcp14>MUST</bcp14> identify the same subject. If omitted, the AS <bcp14>SHOULD</bcp14> assume that subject information requests are about the current user and <bcp14>SHOULD</bcp14> require direct interaction or proof of presence before releasing information. <bcp14>OPTIONAL</bcp14>.</t> </dd> </dl> <t>Additional fieldsarecan be defined in the<xref target="IANA-subject-request">GNAP"GNAP Subject Information RequestFields Registry</xref>.</t> <figure><sourcecodeFields" registry (<xref target="IANA-subject-request"></xref>).</t> <sourcecode type="json"><![CDATA[ "subject": { "sub_id_formats": [ "iss_sub", "opaque" ], "assertion_formats": [ "id_token", "saml2" ] }]]></sourcecode></figure>]]></sourcecode> <t>The AS can determine the RO's identity and permission for releasing this information through<xref target="authorization">interactioninteraction with theRO</xref>,RO (<xref target="authorization"> </xref>), AS policies, or<xref target="request-user">assertionsassertions presented by the clientinstance</xref>.instance (<xref target="request-user"> </xref>). If this is determined positively, the AS <bcp14>MAY</bcp14><xref target="response-subject">returnreturn the RO's information in itsresponse</xref>response (<xref target="response-subject"> </xref>) as requested.</t> <t>Subject identifier types requested by the client instance serve only to identify the RO in the context of the AS and can't be used as communication channels by the client instance, as discussed in <xref target="response-subject"/>.</t> </section> <sectionanchor="request-client"><name>Identifyinganchor="request-client"> <name>Identifying the Client Instance</name> <!-- [rfced] Is "_accepted_" correct here? We do not see "accepted" in the list of states in Section 1.5. Should this be updated to "_approved_"? Original: Note that once a grant has been created and is in the _pending_ or _accepted_ states, the AS can determine which client is associated with the grant by dereferencing the continuation access token sent in the continuation request (Section 5). --> <t>When sending a new grant request to the AS, the client instance <bcp14>MUST</bcp14> identify itself by including its client information in the<spanx style="verb">client</spanx><tt>client</tt> field of the request and by signing the request with its unique key as described in <xref target="binding-keys"/>. Note that once a grant has been created and is in either the <em>pending</em> or the <em>accepted</em>states,state, the AS can determine which client is associated with the grant by dereferencing the continuation access token sent in the<xref target="continue-request">continuation request</xref>.continuation request (<xref target="continue-request"> </xref>). As a consequence, the<spanx style="verb">client</spanx><tt>client</tt> field is not sent or accepted for continuation requests.</t> <t>Client information is sent by value as an object or by reference as a string (see <xref target="request-instance"/>).</t> <t>When client instance information is sent by value, the<spanx style="verb">client</spanx><tt>client</tt> field of the request consists of a JSON object with the following fields.</t> <dl><dt><spanx style="verb">key</spanx><dt><tt>key</tt> (object / string):</dt> <dd> <t>The public key of the client instance to be used in this request as described in <xref target="key-format"/> or a reference to a key as described in <xref target="key-reference"/>. <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">class_id</spanx><dt><tt>class_id</tt> (string):</dt> <dd> <t>An identifier string that the AS can use to identify the client software comprising this client instance. The contents and format of this field are up to the AS. <bcp14>OPTIONAL</bcp14>.</t> </dd><dt><spanx style="verb">display</spanx><dt><tt>display</tt> (object):</dt> <dd> <t>An object containing additional information that the AS <bcp14>MAY</bcp14> display to the RO during interaction, authorization, and management. <bcp14>OPTIONAL</bcp14>.(<xref target="request-display"/>)</t>See <xref target="request-display"/>.</t> </dd> </dl><figure><sourcecode<sourcecode type="json"><![CDATA[ "client": { "key": { "proof": "httpsig", "jwk": { "kty": "RSA", "e": "AQAB", "kid": "xyz-1", "alg": "RS256", "n": "kOB5rR4Jv0GMeLaY6_It_r3ORwdf8ci_JtffXyaSx8..." } }, "class_id": "web-server-1234", "display": { "name": "My Client Display Name", "uri": "https://example.net/client" } }]]></sourcecode></figure>]]></sourcecode> <t>Additional fieldsarecan be defined in the<xref target="IANA-client-instance">GNAP"GNAP Client InstanceFields Registry</xref>.</t>Fields" registry (<xref target="IANA-client-instance"></xref>).</t> <t>Absent additional attestations, profiles, or trust mechanisms, both the<spanx style="verb">display</spanx><tt>display</tt> and<spanx style="verb">class_id</spanx><tt>class_id</tt> fields are self-declarative, presented by the client instance. The AS needs to exercise caution in their interpretation, taking them as a hint but not as absolute truth. The<spanx style="verb">class_id</spanx><tt>class_id</tt> field can be used in a variety of ways to help the AS make sense of the particular context in which the client instance is operating. In corporate environments, for example, different levels of trust might apply depending on security policies. This field aims to help the AS adjust its own access decisions for different classes of client software. It is possible to configure a set of values and rules during apre-registration,pre-registration and then have the client instances provide them later in runtime as a hint to the AS. In other cases, the client runs with a specific AS in mind, so a single hardcoded value would be acceptable (for instance, aset topset-top box with a<spanx style="verb">class_id</spanx><tt>class_id</tt> claiming to be "FooBarTV version 4"). While the client instance may not have contacted the AS yet, the value of this<spanx style="verb">class_id</spanx><tt>class_id</tt> field can be evaluated by the AS according to a broader context of dynamic use, alongside other related information available elsewhere (for instance, corresponding fields in a certificate). If the AS is not able to interpret or validate the class_id field, it <bcp14>MUST</bcp14> either return an<spanx style="verb">invalid_client</spanx><tt>invalid_client</tt> error (<xref target="response-error"/>) or interpret the request as if the class_id were not present. See additional discussion of client instance impersonation in <xref target="security-impersonation"/>.</t> <t>The client instance <bcp14>MUST</bcp14> prove possession of any presented key by the<spanx style="verb">proof</spanx><tt>proof</tt> mechanism associated with the key in the request. Key proofing methods are defined in the<xref target="IANA-key-proof-methods">GNAP"GNAP Key ProofingMethods Registry</xref>Methods" registry (<xref target="IANA-key-proof-methods"></xref>), and an initial set of methods is described in <xref target="binding-keys"/>.</t> <t>If the same public key is sent by value on different access requests, the AS <bcp14>MUST</bcp14> treat these requests as coming from the same client instance for purposes of identification, authentication, and policy application.</t> <t>If the AS does not know the client instance's public key ahead of time, the AS can choose how to process the unknown key. Common approaches include:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>Allowing the request and requiring RO authorization in a trust-on-first-use model</t> </li> <li> <t>Limiting the client's requested access to only certain APIs and information</t> </li> <li> <t>Denying the request entirely by returning an<spanx style="verb">invalid_client</spanx><tt>invalid_client</tt> error (<xref target="response-error"/>)</t></list></t></li> </ul> <t>The client instance <bcp14>MUST NOT</bcp14> send a symmetric key by value in the<spanx style="verb">key</spanx><tt>key</tt> field of the request, as doing so would expose the key directly instead of simply proving possession of it. See considerations on symmetric keys in <xref target="security-symmetric"/>. To use symmetric keys, the client instance can send the<spanx style="verb">key</spanx><tt>key</tt> by reference (<xref target="key-reference"/>) or send the entire client identity by reference (<xref target="request-instance"/>).</t> <t>The client instance's key can be pre-registered with the AS ahead of time and associated with a set of policies and allowable actions pertaining to that client. If this pre-registration includes other fields that can occur in the<spanx style="verb">client</spanx><tt>client</tt> request object described in this section, such as<spanx style="verb">class_id</spanx><tt>class_id</tt> or<spanx style="verb">display</spanx>,<tt>display</tt>, the pre-registered values <bcp14>MUST</bcp14> take precedence over any values given at runtime. Additional fields sent during a request but not present in a pre-registered client instance record at the AS <bcp14>SHOULD NOT</bcp14> be added to the client's pre-registered record. See additional considerations regarding client instance impersonation in <xref target="security-impersonation"/>.</t> <t>A client instance that is capable of talking to multipleAS'sASes <bcp14>SHOULD</bcp14> use a different key for each AS to prevent a class of mix-up attacks as described in <xreftarget="security-cuckoo"/>target="security-cuckoo"/>, unless other mechanisms can be used to assure the identity of the AS for a given request.</t> <sectionanchor="request-instance"><name>Identifyinganchor="request-instance"> <name>Identifying the Client Instance by Reference</name> <t>If the client instance has an instance identifier that the AS can use to determine appropriate key information, the client instance can send this instance identifier as a direct reference value in lieu of the<spanx style="verb">client</spanx><tt>client</tt> object. The instance identifier <bcp14>MAY</bcp14> be assigned to a client instance at runtime through a grant response (<xref target="response-dynamic-handles"/>) or <bcp14>MAY</bcp14> be obtained in another fashion, such as a static registration process at the AS.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "client": "client-541-ab"]]></sourcecode></figure>]]></sourcecode> <t>When the AS receives a request with an instance identifier, the AS <bcp14>MUST</bcp14> ensure that the key used to<xref target="binding-keys">signsign therequest</xref>request (<xref target="binding-keys"> </xref>) is associated with the instance identifier.</t> <t>If the AS does not recognize the instance identifier, the request <bcp14>MUST</bcp14> be rejected with an<spanx style="verb">invalid_client</spanx><tt>invalid_client</tt> error (<xref target="response-error"/>).</t> </section> <sectionanchor="request-display"><name>Providinganchor="request-display"> <name>Providing Displayable Client Instance Information</name> <t>If the client instance has additional information to display to the RO during any interactions at the AS, it <bcp14>MAY</bcp14> send that information in the "display" field. This field is a JSON object that declares information to present to the RO during any interactive sequences.</t> <dl><dt><spanx style="verb">name</spanx><dt><tt>name</tt> (string):</dt> <dd> <t>Display name of the client software. <bcp14>RECOMMENDED</bcp14>.</t> </dd><dt><spanx style="verb">uri</spanx><dt><tt>uri</tt> (string):</dt> <dd> <t>User-facing information about the client software, such as a web page. This URI <bcp14>MUST</bcp14> be an absolute URI. <bcp14>OPTIONAL</bcp14>.</t> </dd><dt><spanx style="verb">logo_uri</spanx> (string)</dt><dt><tt>logo_uri</tt> (string):</dt> <dd> <t>Display image to represent the client software. This URI <bcp14>MUST</bcp14> be an absolute URI. The logo <bcp14>MAY</bcp14> be passed by value by using a data: URI <xref target="RFC2397"/> referencing an imagemediatype.media type. <bcp14>OPTIONAL</bcp14>.</t> </dd> </dl><figure><sourcecode<sourcecode type="json"><![CDATA[ "display": { "name": "My Client Display Name", "uri": "https://example.net/client", "logo_uri": "data:image/png;base64,Eeww...=" }]]></sourcecode></figure>]]></sourcecode> <t>Additional display fieldsarecan be definedbyin the<xref target="IANA-client-instance-display">GNAP"GNAP Client Instance DisplayFields Registry</xref>.</t>Fields" registry (<xref target="IANA-client-instance-display"></xref>).</t> <t>The AS <bcp14>SHOULD</bcp14> use these values during interaction with the RO. The values are for informational purposes only and <bcp14>MUST NOT</bcp14> be taken as authentic proof of the client instance's identity or source. The AS <bcp14>MAY</bcp14> restrict display values to specific client instances, as identified by their keys in <xref target="request-client"/>. See additional considerations for displayed client information in <xref target="security-impersonation"/> and for the<spanx style="verb">logo_uri</spanx><tt>logo_uri</tt> in particular in <xref target="security-client-hosted-logo"/>.</t> </section> <sectionanchor="request-key-authenticate"><name>Authenticatinganchor="request-key-authenticate"> <name>Authenticating the Client Instance</name> <t>If the presented key is known to the AS and is associated with a single instance of the client software, the process of presenting a key and proving possession of that key is sufficient to authenticate the client instance to the AS. The AS <bcp14>MAY</bcp14> associate policies with the client instance identified by this key, such as limiting which resources can be requested and which interaction methods can be used. For example, only specific client instances with certain known keys might be trusted with access tokens without the AS interacting directly with theRORO, as in <xref target="example-no-user"/>.</t> <t>The presentation of a key allows the AS to strongly associate multiple successive requests from the same client instance with each other. This is true when the AS knows the key ahead of time and can use the key to authenticate the client instance, but it is also true if the key is ephemeral and created just for this series of requests. Assuchsuch, the AS <bcp14>MAY</bcp14> allow for client instances to make requests with unknown keys. This pattern allows for ephemeral clientinstances, suchinstances (such as single-pageapplications,applications) and client software with many individual long-livedinstances, suchinstances (such as mobileapplications,applications) to generate key pairs per instance and use the keys within the protocol without having to go through a separate registration step. The AS <bcp14>MAY</bcp14> limit which capabilities are made available to client instances with unknown keys. For example, the AS could have a policy saying that onlypreviously-registeredpreviously registered client instances can request particularresources,resources or that all client instances with unknown keys have to be interactively approved by an RO.</t> </section> </section> <sectionanchor="request-user"><name>Identifyinganchor="request-user"> <name>Identifying the User</name> <t>If the client instance knows the identity of the end user through one or more identifiers or assertions, the client instance <bcp14>MAY</bcp14> send that information to the AS in the "user" field. The client instance <bcp14>MAY</bcp14> pass this information by value or by reference(See(see <xref target="request-user-reference"/>).</t> <dl><dt><spanx style="verb">sub_ids</spanx><dt><tt>sub_ids</tt> (array of objects):</dt> <dd> <t>An array of subject identifiers for the end user, as defined by <xref target="RFC9493"/>. <bcp14>OPTIONAL</bcp14>.</t> </dd><dt><spanx style="verb">assertions</spanx><dt><tt>assertions</tt> (array ofobjects)</dt>objects):</dt> <dd> <t>An array containing assertions asobjectsobjects, each containing the assertion format and the assertion value as the JSON string serialization of the assertion, as defined in <xref target="response-subject"/>. <bcp14>OPTIONAL</bcp14>.</t> </dd> </dl><figure><sourcecode<sourcecode type="json"><![CDATA[ "user": { "sub_ids": [ { "format": "opaque", "id": "J2G8G8O4AZ" } ], "assertions": [ { "format": "id_token", "value": "eyj..." } ] }]]></sourcecode></figure>]]></sourcecode> <t>Subject identifiers are hints to the AS in determining the RO and <bcp14>MUST NOT</bcp14> be taken as authoritative statements that a particular RO is present at the client instance and acting as the end user.</t> <t>Assertions presented by the client instance <bcp14>SHOULD</bcp14> be validated by the AS. While the details of such validation are outside the scope of this specification, common validation steps include verifying the signature of the assertion against a trusted signing key, verifying the audience and issuer of the assertion map to expected values, and verifying the time window for the assertion itself. However, note that in many use cases, some of these common steps are relaxed. For example, an AS acting as an identity provider (IdP) could expect that assertions being presented using this mechanism were issued by the AS to the client software. The AS would verify that the AS is the issuer of the assertion, not the audience, and that the client instance is instead the audience of the assertion. Similarly, an AS might accept arecently-expiredrecently expired assertion in order to help bootstrap a new session with a specific end user.</t> <t>If the identified end user does not match the RO present at the AS during an interactionstep,step and the AS is not explicitly allowing a cross-user authorization, the AS <bcp14>SHOULD</bcp14> reject the request with an<spanx style="verb">unknown_user</spanx><tt>unknown_user</tt> error (<xref target="response-error"/>).</t> <t>If the AS trusts the client instance to present verifiable assertions or known subject identifiers, such as an opaque identifier issued by the AS for this specific client instance, the AS <bcp14>MAY</bcp14> decide, based on its policy, to skip interaction with the RO, even if the client instance provides one or more interaction modes in its request.</t> <t>See <xref target="security-assertions"/> for considerationsthatfor the AShas to makewhen accepting and processing assertions from the client instance.</t> <sectionanchor="request-user-reference"><name>Identifyinganchor="request-user-reference"> <name>Identifying the User by Reference</name> <t>The AS can identify the current end user to the client instance with a referencewhichthat can be used by the client instance to refer to the end user across multiple requests. If the client instance has a reference for the end user at this AS, the client instance <bcp14>MAY</bcp14> pass that reference as a string. The format of this string is opaque to the client instance.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "user": "XUT2MFM1XBIKJKSDU8QM"]]></sourcecode></figure>]]></sourcecode> <t>One means of dynamically obtaining such a user reference is from the AS returning an<spanx style="verb">opaque</spanx><tt>opaque</tt> subject identifier as described in <xref target="response-subject"/>. Other means of configuring a client instance with a user identifier are out of scope of this specification. The lifetime and validity of these user referencesisare determined by theASAS, and this lifetime is not exposed to the client instance in GNAP. As such, a client instance using such a user reference is likely to keep using that reference untilsuch a time asit stops working.</t> <t>User reference identifiers are not intended to be human-readable user identifiers or structured assertions. For the client instance to send either of these, the client can use the full<xref target="request-user">useruser requestobject</xref>object (<xref target="request-user"> </xref>) instead.</t> <t>If the AS does not recognize the user reference, it <bcp14>MUST</bcp14> return an<spanx style="verb">unknown_user</spanx><tt>unknown_user</tt> error (<xref target="response-error"/>).</t> </section> </section> <sectionanchor="request-interact"><name>Interactinganchor="request-interact"> <name>Interacting with the User</name> <t>Often, the AS will require<xref target="authorization">interactioninteraction with theRO</xref>RO (<xref target="authorization"> </xref>) in order to approve a requested delegation to the client instance for both access to resources and direct subject information. Manytimestimes, the end user using the client instance is the same person as the RO, and the client instance can directly drive interaction with the end user by facilitating the process through means such as redirection to a URI or launching an application. Other times, the client instance can provide information to start the RO's interaction on a secondary device, or the client instance will wait for the RO to approve the request asynchronously. The client instance could also be signaled that interaction has concluded through a callback mechanism.</t> <t>The client instance declares the parameters for interaction methods that it can support using the<spanx style="verb">interact</spanx><tt>interact</tt> field.</t> <t>The<spanx style="verb">interact</spanx><tt>interact</tt> field is a JSON object with three keys whose values declare how the client can initiate and complete the request, as well as provide hints to the AS about user preferences such as locale. A client instance <bcp14>MUST NOT</bcp14> declare an interaction mode it does not support. The client instance <bcp14>MAY</bcp14> send multiple modes in the same request. There is no preference order specified in this request. An AS <bcp14>MAY</bcp14><xref target="response-interact">respondrespond to any, all, or none of the presented interactionmodes</xref>modes (<xref target="response-interact"> </xref>) in a request, depending on its capabilities and what is allowed to fulfill the request.</t> <dl><dt><spanx style="verb">start</spanx><dt><tt>start</tt> (array of objects/strings):</dt> <dd> <t>Indicates how the client instance can start an interaction. <bcp14>REQUIRED</bcp14>.(<xref target="request-interact-start"/>)</t>See <xref target="request-interact-start"/>.</t> </dd><dt><spanx style="verb">finish</spanx><dt><tt>finish</tt> (object):</dt> <dd> <t>Indicates how the client instance can receive an indication that interaction has finished at the AS. <bcp14>OPTIONAL</bcp14>.(<xref target="request-interact-finish"/>)</t>See <xref target="request-interact-finish"/>.</t> </dd><dt><spanx style="verb">hints</spanx><dt><tt>hints</tt> (object):</dt> <dd> <t>Provides additional information to inform the interaction process at the AS. <bcp14>OPTIONAL</bcp14>.(<xref target="request-interact-hint"/>)</t>See <xref target="request-interact-hint"/>.</t> </dd> </dl> <t>In the following non-normative example, the client instance is indicating that it can<xref target="request-interact-redirect">redirect</xref>redirect (<xref target="request-interact-redirect"> </xref>) the end user to an arbitrary URI and can receive a<xref target="request-interact-callback-redirect">redirect</xref>redirect (<xref target="request-interact-callback-redirect"> </xref>) through a browser request. Note that the client instance does not accept a push-style callback. The pattern of using a redirect for both interaction start and finish is common for web-based client software.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "interact": { "start": ["redirect"], "finish": { "method": "redirect", "uri": "https://client.example.net/return/123455", "nonce": "LKLTI25DK82FX4T4QFZC" } }]]></sourcecode></figure>]]></sourcecode> <t>In the following non-normative example, the client instance is indicating that it can display a<xref target="request-interact-usercode">user code</xref>user code (<xref target="request-interact-usercode"> </xref>) and direct the end user to an<xref target="request-interact-redirect">arbitrary URI</xref>,arbitrary URI (<xref target="request-interact-redirect"> </xref>), but it cannot accept a redirect or push callback. This pattern is common for deviceswiththat have robust display capabilities butthatexpect the use of a secondary device to facilitate end-user interaction with the AS, such as a set-top box capable of displaying an interaction URL as a QR code.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "interact": { "start": ["redirect", "user_code"] }]]></sourcecode></figure>]]></sourcecode> <t>In the following non-normative example, the client instance is indicating that itcan notcannot start any interaction with theend-user,end user but that the AS can<xref target="request-interact-callback-push">pushpush an interaction finishmessage</xref>message (<xref target="request-interact-callback-push"> </xref>) when authorization from the RO is received asynchronously. This pattern is common for scenarios where a service needs to be authorized, but the RO is able to be contacted separately from the GNAP transaction itself, such as through a push notification or existing interactive session on a secondary device.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "interact": { "start": [], "finish": { "method": "push", "uri": "https://client.example.net/return/123455", "nonce": "LKLTI25DK82FX4T4QFZC" } }]]></sourcecode></figure>]]></sourcecode> <!-- [rfced] May we update the "if" clause at the beginning of this sentence as follows to improve readability? Original: If the client instance does not provide a suitable interaction mechanism, the AS cannot contact the RO asynchronously, and the AS determines that interaction is required, then the AS MUST return an invalid_interaction error (Section 3.6) since the client instance will be unable to complete the request without authorization. Perhaps: If 1) the client instance does not provide a suitable interaction mechanism, 2) the AS cannot contact the RO asynchronously, and 3) the AS determines that interaction is required, then the AS MUST return an invalid_interaction error (Section 3.6) since the client instance will be unable to complete the request without authorization. --> <t>If the client instance does not provide a suitable interaction mechanism, the AS cannot contact the RO asynchronously, and the AS determines that interaction is required, then the AS <bcp14>MUST</bcp14> return an<spanx style="verb">invalid_interaction</spanx><tt>invalid_interaction</tt> error (<xref target="response-error"/>) since the client instance will be unable to complete the request without authorization.</t> <sectionanchor="request-interact-start"><name>Startanchor="request-interact-start"> <name>Start Mode Definitions</name> <t>If the client instance is capable of starting interaction with the end user, the client instance indicates this by sending an array of start modes under the<spanx style="verb">start</spanx><tt>start</tt> key. Each interaction startmodesmode has a unique identifying name. Interaction start modes are specified in the array either by a string, which consists of the start mode name on its own, or by a JSON object with the required field<spanx style="verb">mode</spanx>:</t><tt>mode</tt>:</t> <dl><dt><spanx style="verb">mode</spanx>:</dt><dt><tt>mode</tt>:</dt> <dd> <t>The interaction start mode. <bcp14>REQUIRED</bcp14>.</t> </dd> </dl> <t>Interaction start modes defined as objects <bcp14>MAY</bcp14> define additional parameters to be required in the object.</t> <t>The<spanx style="verb">start</spanx><tt>start</tt> array can contain both string-type and object-type modes.</t> <t>This specification defines the following interaction start modes:</t> <dl><dt><spanx style="verb">"redirect"</spanx><dt><tt>"redirect"</tt> (string):</dt> <dd> <t>Indicates that the client instance can direct the end user to an arbitrary URI for interaction. See <xreftarget="request-interact-redirect"/></t>target="request-interact-redirect"/>.</t> </dd><dt><spanx style="verb">"app"</spanx><dt><tt>"app"</tt> (string):</dt> <dd> <t>Indicates that the client instance can launch an application on the end user's device for interaction. See <xreftarget="request-interact-app"/></t>target="request-interact-app"/>.</t> </dd><dt><spanx style="verb">"user_code"</spanx><dt><tt>"user_code"</tt> (string):</dt> <dd> <t>Indicates that the client instance can communicate a short, human-readableshortcode to the end user for use with a stable URI. See <xreftarget="request-interact-usercode"/></t>target="request-interact-usercode"/>.</t> </dd><dt><spanx style="verb">"user_code_uri"</spanx><dt><tt>"user_code_uri"</tt> (string):</dt> <dd> <t>Indicates that the client instance can communicate a short, human-readableshortcode to the end user for use with a short, dynamic URI. See <xreftarget="request-interact-usercodeuri"/></t>target="request-interact-usercodeuri"/>.</t> </dd> </dl> <t>Additional start modesarecan be defined in the<xref target="IANA-interaction-start-modes">GNAP"GNAP Interaction StartModes Registry</xref>.</t>Modes" registry (<xref target="IANA-interaction-start-modes"> </xref>).</t> <sectionanchor="request-interact-redirect"><name>Redirectanchor="request-interact-redirect"> <name>Redirect to an Arbitrary URI</name> <t>If the client instance is capable of directing the end user to a URI defined by the AS at runtime, the client instance indicates this by including<spanx style="verb">redirect</spanx><tt>redirect</tt> in the array under the<spanx style="verb">start</spanx><tt>start</tt> key. The means by which the client instance will activate this URIisare out of scope of this specification, but common methods include an HTTP redirect, launching a browser on the end user's device, providing a scannable image encoding, and printing out a URI to an interactive console. While this URI is generally hosted at the AS, the client instance can make no assumptions about its contents, composition, or relationship to the grant endpoint URI.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "interact": { "start": ["redirect"] }]]></sourcecode></figure>]]></sourcecode> <t>If this interaction mode is supported for this client instance and request, the AS returns a redirect interaction response<xref target="response-interact-redirect"/>.(<xref target="response-interact-redirect"/>). The client instance manages this interaction method as described in <xref target="interaction-redirect"/>.</t> <t>See <xref target="security-front-channel"/> for more considerations regarding the use of front-channel communication techniques.</t> </section> <sectionanchor="request-interact-app"><name>Openanchor="request-interact-app"> <name>Open anApplication-specificApplication-Specific URI</name> <t>If the client instance can open a URI associated with an application on the end user's device, the client instance indicates this by including<spanx style="verb">app</spanx><tt>app</tt> in the array under the<spanx style="verb">start</spanx><tt>start</tt> key. The means by which the client instance determines the application to open with this URI are out of scope of this specification.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "interact": { "start": ["app"] }]]></sourcecode></figure>]]></sourcecode> <t>If this interaction mode is supported for this client instance and request, the AS returns an app interaction response with an app URI payload (<xref target="response-interact-app"/>). The client instance manages this interaction method as described in <xref target="interaction-app"/>.</t> </section> <sectionanchor="request-interact-usercode"><name>Displayanchor="request-interact-usercode"> <name>Display a Short User Code</name> <t>If the client instance is capable of displaying or otherwise communicating a short, human-entered code to the RO, the client instance indicates this by including<spanx style="verb">user_code</spanx><tt>user_code</tt> in the array under the<spanx style="verb">start</spanx><tt>start</tt> key. This code is to be entered at a static URI that does not change at runtime. The client instance has no reasonable means to communicate a dynamic URI to the RO,andso this URI is usually communicated out of band to the RO through documentation or other messaging outside of GNAP. While this URI is generally hosted at the AS, the client instance can make no assumptions about its contents, composition, or relationship to the grant endpoint URI.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "interact": { "start": ["user_code"] }]]></sourcecode></figure>]]></sourcecode> <t>If this interaction mode is supported for this client instance and request, the AS returns a user code as specified in <xref target="response-interact-usercode"/>. The client instance manages this interaction method as described in <xref target="interaction-usercode"/>.</t> </section> <sectionanchor="request-interact-usercodeuri"><name>Displayanchor="request-interact-usercodeuri"> <name>Display a Short User Code and URI</name> <t>If the client instance is capable of displaying or otherwise communicating a short, human-entered code along with a short, human-entered URI to the RO, the client instance indicates this by including<spanx style="verb">user_code_uri</spanx><tt>user_code_uri</tt> in the array under the<spanx style="verb">start</spanx><tt>start</tt> key. This code is to be entered at the dynamic URL given in the response. While this URL is generally hosted at the AS, the client instance can make no assumptions about its contents, composition, or relationship to the grant endpoint URI.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "interact": { "start": ["user_code_uri"] }]]></sourcecode></figure>]]></sourcecode> <t>If this interaction mode is supported for this client instance and request, the AS returns a user code and interaction URL as specified in <xref target="response-interact-usercodeuri"/>. The client instance manages this interaction method as described in <xref target="interaction-usercodeuri"/>.</t> </section> </section> <sectionanchor="request-interact-finish"><name>Interactionanchor="request-interact-finish"> <name>Interaction Finish Methods</name> <t>If the client instance is capable of receiving a message from the AS indicating that the RO has completed their interaction, the client instance indicates this by sending the following members of an object under the<spanx style="verb">finish</spanx><tt>finish</tt> key.</t> <dl><dt><spanx style="verb">method</spanx><dt><tt>method</tt> (string):</dt> <dd> <t>The callback method that the AS will use to contact the client instance. <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">uri</spanx><!--[rfced] We are having some difficulty parsing "send an HTTP POST request" in the following text. May we update it as follows? Original: uri (string): Indicates the URI that the AS will either send the RO to after interaction or send an HTTP POST request. Perhaps: uri (string): Indicates the URI that the AS will either send the RO to or send an HTTP POST request to after interaction. --> <dt><tt>uri</tt> (string):</dt> <dd> <t>Indicates the URI that the AS will either send the RO to after interaction or send an HTTP POST request. This URI <bcp14>MAY</bcp14> be unique per request and <bcp14>MUST</bcp14> be hosted by or accessiblebyto the client instance. This URI <bcp14>MUST</bcp14> be an absoluteURI,URI and <bcp14>MUST NOT</bcp14> contain any fragment component. If the client instance needs any state information to tie to thefront channelfront-channel interaction response, it <bcp14>MUST</bcp14> use a unique callback URI to link to that ongoing state. The allowable URIs and URI patterns <bcp14>MAY</bcp14> be restricted by the AS based on the client instance's presented key information. The callback URI <bcp14>SHOULD</bcp14> be presented to the RO during the interaction phase before redirect. <bcp14>REQUIRED</bcp14> for<spanx style="verb">redirect</spanx><tt>redirect</tt> and<spanx style="verb">push</spanx><tt>push</tt> methods.</t> </dd><dt><spanx style="verb">nonce</spanx><dt><tt>nonce</tt> (string):</dt> <dd> <t>Unique ASCII string value to be used in the calculation of the "hash" query parameter sent to the callbackURI,URI. It must be sufficiently random to be unguessable by an attacker. It <bcp14>MUST</bcp14> be generated by the client instance as a unique value for this request. <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">hash_method</spanx><dt><tt>hash_method</tt> (string):</dt> <dd> <t>An identifier of a hash calculation mechanism to be used for the callback hash in <xref target="interaction-hash"/>, as defined in the<xref target="HASH-ALG">IANA NamedIANA "Named Information Hash AlgorithmRegistry</xref>.Registry" <xref target="HASH-ALG"></xref>. If absent, the default value is<spanx style="verb">sha-256</spanx>.<tt>sha-256</tt>. <bcp14>OPTIONAL</bcp14>.</t> </dd> </dl> <t>This specification defines the following values for the<spanx style="verb">method</spanx> parameter, with other<tt>method</tt> parameter; additional values can be definedbyin the<xref target="IANA-interaction-finish-methods">GNAP"GNAP Interaction FinishMethods Registry</xref>:</t>Methods" registry (<xref target="IANA-interaction-finish-methods"> </xref>):</t> <dl><dt><spanx style="verb">"redirect"</spanx>:</dt><dt><tt>"redirect"</tt>:</dt> <dd> <t>Indicates that the client instance can receive a redirect from the end user's device after interaction with the RO has concluded. See <xreftarget="request-interact-callback-redirect"/></t>target="request-interact-callback-redirect"/>.</t> </dd><dt><spanx style="verb">"push"</spanx>:</dt><dt><tt>"push"</tt>:</dt> <dd> <t>Indicates that the client instance can receive an HTTP POST request from the AS after interaction with the RO has concluded. See <xreftarget="request-interact-callback-push"/></t>target="request-interact-callback-push"/>.</t> </dd> </dl> <t>If interaction finishing is supported for this client instance and request, the AS will<xref target="response-interact-finish">returnreturn anonce</xref>nonce (<xref target="response-interact-finish"> </xref>) used by the client instance to validate the callback. All interaction finish methods <bcp14>MUST</bcp14> use this nonce to allow the client to verify the connection between the pending interaction request and the callback. GNAP does this through the use of the interaction hash, defined in <xref target="interaction-hash"/>. All requests to the callback URI <bcp14>MUST</bcp14> be processed as described in <xref target="interaction-finish"/>.</t> <t>All interaction finish methods <bcp14>MUST</bcp14> require presentation of an interaction reference for continuing this grant request. This means that the interaction reference <bcp14>MUST</bcp14> be returned by the AS and <bcp14>MUST</bcp14> be presented by the client as described in <xref target="continue-after-interaction"/>. The means by which the interaction reference is returned to the client instanceisare specific to the interaction finish method.</t> <sectionanchor="request-interact-callback-redirect"><name>Receiveanchor="request-interact-callback-redirect"> <name>Receive an HTTP CallbackThroughthrough the Browser</name> <t>A finish<spanx style="verb">method</spanx><tt>method</tt> value of<spanx style="verb">redirect</spanx><tt>redirect</tt> indicates that the client instance will expect a request from the RO's browser using the HTTP method GET as described in <xref target="interaction-callback"/>.</t> <!-- [rfced] Please review the use of "MUST" here, especially in relation to "or". Does "MUST" apply to all verbs in the series? Original: The URI MUST be accessible from an HTTP GET request and MUST be protected by HTTPS, be hosted on a server local to the RO's browser ("localhost"), or use an application-specific URI scheme that is loaded on the end user's device. Perhaps: The URI MUST be accessible from an HTTP GET request, be protected by HTTPS, be hosted on a server local to the RO's browser ("localhost"), or use an application-specific URI scheme that is loaded on the end user's device. Or: The URI MUST be accessible from an HTTP GET request, be protected by HTTPS, and be hosted on a server local to the RO's browser ("localhost"), or it MUST use an application-specific URI scheme that is loaded on the end user's device. --> <t>The client instance's URI <bcp14>MUST</bcp14> be protected by HTTPS, be hosted on a server local to the RO's browser ("localhost"), or use an application-specific URI scheme that is loaded on the end user's device.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "interact": { "finish": { "method": "redirect", "uri": "https://client.example.net/return/123455", "nonce": "LKLTI25DK82FX4T4QFZC" } }]]></sourcecode></figure>]]></sourcecode> <t>Requests to the callback URI <bcp14>MUST</bcp14> be processed by the client instance as described in <xref target="interaction-callback"/>.</t> <t>Since the incoming request to the callback URI is from the RO's browser, this method is usually used when the RO and end user are the same entity. See <xref target="security-sessions"/> for considerations on ensuring the incoming HTTP message matches the expected context of the request. See <xref target="security-front-channel"/> for more considerations regarding the use of front-channel communication techniques.</t> </section> <sectionanchor="request-interact-callback-push"><name>Receiveanchor="request-interact-callback-push"> <name>Receive an HTTP Direct Callback</name> <t>A finish<spanx style="verb">method</spanx><tt>method</tt> value of<spanx style="verb">push</spanx><tt>push</tt> indicates that the client instance will expect a request from the AS directly using the HTTP method POST as described in <xref target="interaction-pushback"/>.</t> <t>The client instance's URI <bcp14>MUST</bcp14> be protected by HTTPS, be hosted on a server local to the RO's browser ("localhost"), or use an application-specific URI scheme that is loaded on the end user's device.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "interact": { "finish": { "method": "push", "uri": "https://client.example.net/return/123455", "nonce": "LKLTI25DK82FX4T4QFZC" } }]]></sourcecode></figure>]]></sourcecode> <t>Requests to the callback URI <bcp14>MUST</bcp14> be processed by the client instance as described in <xref target="interaction-pushback"/>.</t> <t>Since the incoming request to the callback URI is from the AS and not from the RO's browser, this request is not expected to have any shared session information from the start method. See Sections <xreftarget="security-sessions"/>target="security-sessions" format="counter"/> and <xreftarget="security-polling"/>target="security-polling" format="counter"/> for more considerations regarding the use of back-channel and polling mechanisms like this.</t> </section> </section> <sectionanchor="request-interact-hint"><name>Hints</name>anchor="request-interact-hint"> <name>Hints</name> <t>The<spanx style="verb">hints</spanx><tt>hints</tt> key is an object describing one or more suggestions from the client instance that the AS can use to help drive user interaction.</t> <t>This specification defines the followingpropertiesproperty under the<spanx style="verb">hints</spanx><tt>hints</tt> key:</t> <dl><dt><spanx style="verb">ui_locales</spanx><dt><tt>ui_locales</tt> (array of strings):</dt> <dd> <t>Indicates the end user's preferred locales that the AS can use during interaction, particularly before the RO has authenticated. <bcp14>OPTIONAL</bcp14>. <xref target="request-interact-locale"/></t> </dd> </dl> <t>The followingsections detailsubsection details requests for interaction hints. Additional interaction hintsarecan be defined in the<xref target="IANA-interaction-hints">GNAP"GNAP InteractionHints Registry</xref>.</t>Hints" registry (<xref target="IANA-interaction-hints"> </xref>).</t> <sectionanchor="request-interact-locale"><name>Indicateanchor="request-interact-locale"> <name>Indicate Desired Interaction Locales</name> <t>If the client instance knows the end user's locale and language preferences, the client instance can send this information to the AS using the<spanx style="verb">ui_locales</spanx><tt>ui_locales</tt> field with an array of locale strings as defined by <xref target="RFC5646"/>.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "interact": { "hints": { "ui_locales": ["en-US", "fr-CA"] } }]]></sourcecode></figure>]]></sourcecode> <t>If possible, the AS <bcp14>SHOULD</bcp14> use one of the locales in the array, with preference to the first item in the array supported by the AS. If none of the given locales are supported, the AS <bcp14>MAY</bcp14> use a default locale.</t> </section> </section> </section> </section> <sectionanchor="response"><name>Grantanchor="response"> <name>Grant Response</name> <t>In response to a client instance's request, the AS responds with a JSON object as the HTTP content. Each possible field is detailed in thesectionssubsections below.</t> <dl><dt><spanx style="verb">continue</spanx><dt><tt>continue</tt> (object):</dt> <dd> <t>Indicates that the client instance can continue the request by making one or more continuation requests. <bcp14>REQUIRED</bcp14> if continuation calls are allowed for this client instance on this grant request. See <xref target="response-continue"/>.</t> </dd><dt><spanx style="verb">access_token</spanx><dt><tt>access_token</tt> (object / array of objects):</dt> <dd> <t>A single access token or set of access tokens that the client instance can use to call the RS on behalf of the RO. <bcp14>REQUIRED</bcp14> if an access token is included. See <xref target="response-token"/>.</t> </dd><dt><spanx style="verb">interact</spanx><dt><tt>interact</tt> (object):</dt> <dd> <t>Indicates that interaction through some set of defined mechanisms needs to take place. <bcp14>REQUIRED</bcp14> if interaction is expected. See <xref target="response-interact"/>.</t> </dd><dt><spanx style="verb">subject</spanx><dt><tt>subject</tt> (object):</dt> <dd> <t>Claims about the RO as known and declared by the AS. <bcp14>REQUIRED</bcp14> if subject information is included. See <xref target="response-subject"/>.</t> </dd><dt><spanx style="verb">instance_id</spanx><dt><tt>instance_id</tt> (string):</dt> <dd> <t>An identifier this client instance can use to identify itself when making future requests. <bcp14>OPTIONAL</bcp14>. See <xref target="response-dynamic-handles"/>.</t> </dd><dt><spanx style="verb">error</spanx><dt><tt>error</tt> (object or string):</dt> <dd> <t>An error code indicating that something has gone wrong. <bcp14>REQUIRED</bcp14> for an error condition. See <xref target="response-error"/>.</t> </dd> </dl> <t>Additional fields can be defined by extensions to GNAP in the<xref target="IANA-grant-response">GNAP"GNAP Grant ResponseParameters Registry</xref>.</t>Parameters" registry (<xref target="IANA-grant-response"> </xref>).</t> <t>In the following non-normative example, the AS is returning an<xref target="response-interact-redirect">interaction URI</xref>,interaction URI (<xref target="response-interact-redirect"> </xref>), a<xref target="response-interact-finish">callback nonce</xref>,callback nonce (<xref target="response-interact-finish"> </xref>), and a<xref target="response-continue">continuation response</xref>.</t> <figure><sourcecodecontinuation response (<xref target="response-continue"> </xref>).</t> <sourcecode type="json"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 { "interact": { "redirect": "https://server.example.com/interact/4CF492ML\ VMSW9MKMXKHQ", "finish": "MBDOFXG4Y5CVJCX821LH" }, "continue": { "access_token": { "value": "80UPRY5NM33OMUKMKSKU", }, "uri": "https://server.example.com/tx" } }]]></sourcecode></figure>]]></sourcecode> <t>In the following non-normative example, the AS is returning a bearer<xref target="response-token-single">access token</xref>access token (<xref target="response-token-single"> </xref>) with a management URI and a<xref target="response-subject">subject identifier</xref>subject identifier (<xref target="response-subject"> </xref>) in the form of an opaque identifier.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "access_token": { "value": "OS9M2PMHKUR64TB8N6BW7OZB8CDFONP219RP1LT0", "flags": ["bearer"], "manage": { "uri": "https://server.example.com/token/PRY5NM33O", "access_token": { "value": "B8CDFONP21-4TB8N6.BW7ONM" } } }, "subject": { "sub_ids": [ { "format": "opaque", "id": "J2G8G8O4AZ" } ] } }]]></sourcecode></figure>]]></sourcecode> <t>In the following non-normative example, the AS is returning set of<xref target="response-subject">subject identifiers</xref>,subject identifiers (<xref target="response-subject"> </xref>), simultaneously as an opaque identifier, an email address, and a decentralized identifier (DID), formatted as a set of Subject Identifiers as defined in <xref target="RFC9493"/>.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "subject": { "sub_ids": [ { "format": "opaque", "id": "J2G8G8O4AZ" }, { "format": "email", "email": "user@example.com" }, { "format": "did", "url": "did:example:123456" } ] } }]]></sourcecode></figure>]]></sourcecode> <t>The response <bcp14>MUST</bcp14> be sent as a JSON object in the content of the HTTP response with Content-Type<spanx style="verb">application/json</spanx>,<tt>application/json</tt>, unless otherwise specified by the specific response (e.g., an empty response with no Content-Type).</t> <t>The authorization server <bcp14>MUST</bcp14> include the HTTP Cache-Control response header field <xref target="RFC9111"/> with a value set to "no-store".</t> <sectionanchor="response-continue"><name>Requestanchor="response-continue"> <name>Request Continuation</name> <t>If the AS determines that the grant request can be continued by the client instance, the AS responds with the<spanx style="verb">continue</spanx><tt>continue</tt> field. This field contains a JSON object with the following properties.</t> <dl><dt><spanx style="verb">uri</spanx><dt><tt>uri</tt> (string):</dt> <dd> <t>The URI at which the client instance can make continuation requests. This URI <bcp14>MAY</bcp14> vary perrequest,request or <bcp14>MAY</bcp14> be stable at the AS. This URI <bcp14>MUST</bcp14> be an absolute URI. The client instance <bcp14>MUST</bcp14> use this value exactly as given when making a<xref target="continue-request">continuation request</xref>.continuation request (<xref target="continue-request"> </xref>). <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">wait</spanx><dt><tt>wait</tt> (integer):</dt> <dd> <t>The amount of time in integer seconds the client instance <bcp14>MUST</bcp14> wait after receiving this request continuation response and calling the continuation URI. The value <bcp14>SHOULD NOT</bcp14> be less than five seconds, and omission of the value <bcp14>MUST</bcp14> be interpreted as five seconds. <bcp14>RECOMMENDED</bcp14>.</t> </dd><dt><spanx style="verb">access_token</spanx><dt><tt>access_token</tt> (object):</dt> <dd> <t>A unique access token for continuing the request, called the "continuation access token". The value of this property <bcp14>MUST</bcp14> be an object in the format specified in <xref target="response-token-single"/>. This access token <bcp14>MUST</bcp14> be bound to the client instance's key used in the request and <bcp14>MUST NOT</bcp14> be a bearer token. As a consequence, the<spanx style="verb">flags</spanx><tt>flags</tt> array of this access token <bcp14>MUST NOT</bcp14> contain the string<spanx style="verb">bearer</spanx><tt>bearer</tt>, and the<spanx style="verb">key</spanx><tt>key</tt> field <bcp14>MUST</bcp14> be omitted. This access token <bcp14>MUST NOT</bcp14> have a<spanx style="verb">manage</spanx><tt>manage</tt> field. The client instance <bcp14>MUST</bcp14> present the continuation access token in all requests to the continuation URI as described in <xref target="use-access-token"/>. <bcp14>REQUIRED</bcp14>.</t> </dd> </dl><figure><sourcecode<sourcecode type="json"><![CDATA[ { "continue": { "access_token": { "value": "80UPRY5NM33OMUKMKSKU" }, "uri": "https://server.example.com/continue", "wait": 60 } }]]></sourcecode></figure>]]></sourcecode> <t>This field is <bcp14>REQUIRED</bcp14> if the grant request is in the <em>pending</em> state, as the field contains the information needed by the client request to continue the request as described in <xref target="continue-request"/>. Note that the continuation access token is bound to the client instance'skey, and thereforekey; therefore, the client instance <bcp14>MUST</bcp14> sign all continuation requests with its key as described in <xref target="binding-keys"/> and <bcp14>MUST</bcp14> present the continuation access token in its continuation request.</t> </section> <sectionanchor="response-token"><name>Accessanchor="response-token"> <name>Access Tokens</name> <t>If the AS has successfully granted one or more access tokens to the client instance, the AS responds with the<spanx style="verb">access_token</spanx><tt>access_token</tt> field. This field contains either a single access token as described in <xref target="response-token-single"/> or an array of access tokens as described in <xref target="response-token-multiple"/>.</t> <t>The client instance uses any access tokens in this response to call the RS as described in <xref target="use-access-token"/>.</t> <t>The grant request <bcp14>MUST</bcp14> be in the <em>approved</em> state to include this field in the response.</t> <sectionanchor="response-token-single"><name>Singleanchor="response-token-single"> <name>Single Access Token</name> <t>If the client instance has requested a single access token and the AS has granted that access token, the AS responds with the "access_token" field. The value of this field is an object with the following properties.</t> <dl><dt><spanx style="verb">value</spanx><dt><tt>value</tt> (string):</dt> <dd> <t>The value of the access token as a string. The value is opaque to the client instance. The value <bcp14>MUST</bcp14> be limited to the<spanx style="verb">token68</spanx><tt>token68</tt> character set defined in <xref section="11.2" sectionFormat="of"target="HTTP"/>target="RFC9110"/> to facilitate transmission over HTTP headers and within other protocols without requiring additional encoding. <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">label</spanx><dt><tt>label</tt> (string):</dt> <dd> <t>The value of the<spanx style="verb">label</spanx><tt>label</tt> the client instance provided in the associated<xref target="request-token">token request</xref>,token request (<xref target="request-token"> </xref>), if present. <bcp14>REQUIRED</bcp14> for multiple access tokens or if a<spanx style="verb">label</spanx><tt>label</tt> was included in the single access tokenrequest,request; <bcp14>OPTIONAL</bcp14> for a single access token where no<spanx style="verb">label</spanx><tt>label</tt> was included in the request.</t> </dd><dt><spanx style="verb">manage</spanx><!-- [rfced] Would it be helpful to combine these definitions, either with a semicolon or in some other way? Original: manage (object): Access information for the token management API for this access token. The management URI for this access token. Perhaps: manage (object): Access information for the token management API for this access token; the management URI for this access token. --> <dt><tt>manage</tt> (object):</dt> <dd> <t>Access information for the token management API for this access token. The management URI for this access token. If provided, the client instance <bcp14>MAY</bcp14> manage its access token as described in <xref target="token-management"/>. This management API is a function of the AS and is separate from the RS the client instance is requesting access to. <bcp14>OPTIONAL</bcp14>.</t> </dd><dt><spanx style="verb">access</spanx><dt><tt>access</tt> (array of objects/strings):</dt> <dd> <t>A description of the rights associated with this access token, as defined in <xref target="resource-access-rights"/>. If included, this <bcp14>MUST</bcp14> reflect the rights associated with the issued access token. These rights <bcp14>MAY</bcp14> vary from what was requested by the client instance. <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">expires_in</spanx><dt><tt>expires_in</tt> (integer):</dt> <dd> <t>The number of seconds in which the access will expire. The client instance <bcp14>MUST NOT</bcp14> use the access token past this time. Note that the access token <bcp14>MAY</bcp14> be revoked by the AS or RS at any point prior to its expiration. <bcp14>OPTIONAL</bcp14>.</t> </dd><dt><spanx style="verb">key</spanx><dt><tt>key</tt> (object / string):</dt> <dd> <t>The key that the token is bound to, if different from the client instance's presented key. The key <bcp14>MUST</bcp14> be an object or string in a format described in <xref target="key-format"/>. The client instance <bcp14>MUST</bcp14> be able to dereference or process the key information in order to be able to<xref target="use-access-token">signsign subsequent requests using the accesstoken</xref>.token (<xref target="use-access-token"> </xref>). When the key is provided by value from the AS, the token shares some security properties with bearer tokens as discussed in <xref target="security-as-keys"/>. It is <bcp14>RECOMMENDED</bcp14> that keys returned for use with access tokens be key references as described in <xref target="key-reference"/> that the client instance can correlate to its known keys. <bcp14>OPTIONAL</bcp14>.</t> </dd><dt><spanx style="verb">flags</spanx><dt><tt>flags</tt> (array of strings):</dt> <dd> <t>A set of flags that represent attributes or behaviors of the access token issued by the AS. <bcp14>OPTIONAL</bcp14>.</t> </dd> </dl> <t>The value of the<spanx style="verb">manage</spanx><tt>manage</tt> field is an object with the following properties:</t><t><spanx style="verb">uri</spanx> (string): The<!-- [rfced] Please review "MUST NOT include the access token value" and "MUST NOT include the value of the access token being managed". Are these saying the same thing? Original: This URI MUST NOT include the access token value and SHOULD be different for each access token issued in a request and MUST NOT include the value of the access token being managed. --> <dl> <dt><tt>uri</tt> (string):</dt> <dd>The URI of the token management API for this access token. This URI <bcp14>MUST</bcp14> be an absolute URI. This URI <bcp14>MUST NOT</bcp14> include the access tokenvalue andvalue, <bcp14>SHOULD</bcp14> be different for each access token issued in arequestrequest, and <bcp14>MUST NOT</bcp14> include the value of the access token being managed.<bcp14>REQUIRED</bcp14>.</t> <dl> <dt><spanx style="verb">access_token</spanx><bcp14>REQUIRED</bcp14>.</dd> <dt><tt>access_token</tt> (object):</dt> <dd> <t>A unique access token for continuing the request, called the "token management access token". The value of this property <bcp14>MUST</bcp14> be an object in the format specified in <xref target="response-token-single"/>. This access token <bcp14>MUST</bcp14> be bound to the client instance's key used in the request (or its most recent rotation) and <bcp14>MUST NOT</bcp14> be a bearer token. As a consequence, the<spanx style="verb">flags</spanx><tt>flags</tt> array of this access token <bcp14>MUST NOT</bcp14> contain the string<spanx style="verb">bearer</spanx><tt>bearer</tt>, and the<spanx style="verb">key</spanx><tt>key</tt> field <bcp14>MUST</bcp14> be omitted. This access token <bcp14>MUST NOT</bcp14> have a<spanx style="verb">manage</spanx><tt>manage</tt> field. This access token <bcp14>MUST NOT</bcp14> have the same value as the token it is managing. The client instance <bcp14>MUST</bcp14> present the continuation access token in all requests to the continuation URI as described in <xref target="use-access-token"/>. <bcp14>REQUIRED</bcp14>.</t> </dd> </dl> <t>The values of the<spanx style="verb">flags</spanx><tt>flags</tt> field defined by this specification are as follows:</t> <dl><dt><spanx style="verb">"bearer"</spanx>:</dt><dt><tt>"bearer"</tt>:</dt> <dd><t>This flag indicates<t>Flag indicating whether the token is a bearer token, not bound to a key and proofing mechanism. If the<spanx style="verb">bearer</spanx><tt>bearer</tt> flag is present, the access token is a bearer token, and the<spanx style="verb">key</spanx><tt>key</tt> field in this response <bcp14>MUST</bcp14> be omitted. See <xref target="security-bearer-tokens"/> for additional considerations on the use of bearer tokens.</t> </dd><dt><spanx style="verb">"durable"</spanx>:</dt><dt><tt>"durable"</tt>:</dt> <dd> <t>Flag indicating a hint of AS behavior on token rotation. If this flag is present, then the client instance can expect apreviously-issuedpreviously issued access token to continue to work after it has been<xref target="rotate-access-token">rotated</xref>rotated (<xref target="rotate-access-token"> </xref>) or the underlying grant request has been<xref target="continue-modify">modified</xref>,modified (<xref target="continue-modify"> </xref>), resulting in the issuance of new access tokens. If this flag is omitted, the client instance can anticipate a given access token could stop working after token rotation or grant request modification. Note that a token flagged as<spanx style="verb">durable</spanx><tt>durable</tt> can still expire or be revoked through any normal means.</t> </dd> </dl> <t>Flag values <bcp14>MUST NOT</bcp14> be included more than once.</t> <t>Additional flags can be defined by extensions using the<xref target="IANA-token-flags">GNAP"GNAP Access TokenFields Registry</xref>.</t>Flags" registry (<xref target="IANA-token-flags"></xref>).</t> <t>If the<spanx style="verb">bearer</spanx><tt>bearer</tt> flag and the<spanx style="verb">key</spanx><tt>key</tt> field in this response are omitted, the token is bound to the<xref target="request-client">keykey used by the clientinstance</xref>instance (<xref target="request-client"> </xref>) in its request for access. If the<spanx style="verb">bearer</spanx><tt>bearer</tt> flag isomitted,omitted and the<spanx style="verb">key</spanx><tt>key</tt> field is present, the token is bound to the key and proofing mechanism indicated in the<spanx style="verb">key</spanx><tt>key</tt> field. The means by which the AS determines how to bind an access token to a key other than that presented by the client instanceisare out of scope for this specification, but common practices include pre-registering specific keys in a static fashion.</t> <t>The client software <bcp14>MUST</bcp14> reject any access token where the<spanx style="verb">flags</spanx><tt>flags</tt> field contains the<spanx style="verb">bearer</spanx><tt>bearer</tt> flag and the<spanx style="verb">key</spanx><tt>key</tt> field is present with any value.</t> <!-- [rfced] We are having trouble understanding how the text starting with "with a management URI..." connects with the rest of the sentence. Please review. Original: The following non-normative example shows a single access token bound to the client instance's key used in the initial request, with a management URI, and that has access to three described resources (one using an object and two described by reference strings). Perhaps: The following non-normative example shows a single access token bound to the client instance's key used in the initial request. The access token has a management URI and has access to three described resources (one using an object and two described by reference strings). --> <t>The following non-normative example shows a single access token bound to the client instance's key used in the initial request, with a management URI, and that has access to three described resources (one using an object and two described by reference strings).</t><figure><sourcecode<sourcecode type="json"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 "access_token": { "value": "OS9M2PMHKUR64TB8N6BW7OZB8CDFONP219RP1LT0", "manage": { "uri": "https://server.example.com/token/PRY5NM33O", "access_token": { "value": "B8CDFONP21-4TB8N6.BW7ONM" } }, "access": [ { "type": "photo-api", "actions": [ "read", "write", "dolphin" ], "locations": [ "https://server.example.net/", "https://resource.local/other" ], "datatypes": [ "metadata", "images" ] }, "read", "dolphin-metadata" ] }]]></sourcecode></figure>]]></sourcecode> <t>The following non-normative example shows a single bearer access token with access to two described resources.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "access_token": { "value": "OS9M2PMHKUR64TB8N6BW7OZB8CDFONP219RP1LT0", "flags": ["bearer"], "access": [ "finance", "medical" ] }]]></sourcecode></figure>]]></sourcecode> <t>If the client instance<xref target="request-token-single">requestedrequested a single accesstoken</xref>,token (<xref target="request-token-single"> </xref>), the AS <bcp14>MUST NOT</bcp14> respond with the multiple accesstokentokens structure.</t> </section> <sectionanchor="response-token-multiple"><name>Multipleanchor="response-token-multiple"> <name>Multiple Access Tokens</name> <t>If the client instance has requested multiple access tokens and the AS has granted at least one of them, the AS responds with the "access_token" field. The value of this field is a JSON array, the members of which are distinct access tokens as described in <xref target="response-token-single"/>. Each object <bcp14>MUST</bcp14> have a unique<spanx style="verb">label</spanx><tt>label</tt> field, corresponding to the token labels chosen by the client instance in the<xref target="request-token-multiple">multiplemultiple accesstoken request</xref>.</t>tokens request (<xref target="request-token-multiple"> </xref>).</t> <t>In the following non-normative example, two tokens are issued under the names<spanx style="verb">token1</spanx><tt>token1</tt> and<spanx style="verb">token2</spanx>,<tt>token2</tt>, and only the first token has a management URI associated with it.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 "access_token": [ { "label": "token1", "value": "OS9M2PMHKUR64TB8N6BW7OZB8CDFONP219RP1LT0", "manage": { "uri": "https://server.example.com/token/PRY5NM33O", "access_token": { "value": "B8CDFONP21-4TB8N6.BW7ONM" } }, "access": [ "finance" ] }, { "label": "token2", "value": "UFGLO2FDAFG7VGZZPJ3IZEMN21EVU71FHCARP4J1", "access": [ "medical" ] } }]]></sourcecode></figure>]]></sourcecode> <t>Each access token corresponds to one of the objects in the<spanx style="verb">access_token</spanx><tt>access_token</tt> array of the client instance's<xref target="request-token-multiple">request</xref>.</t>request (<xref target="request-token-multiple"> </xref>).</t> <t>The AS <bcp14>MAY</bcp14> refuse to issue one or more of the requested accesstokens,tokens for any reason. In suchcasescases, the refused token is omitted from theresponseresponse, and all of the other issued access tokens are included in the response under their respective requested labels. If the client instance<xref target="request-token-multiple">requestedrequested multiple accesstokens</xref>,tokens (<xref target="request-token-multiple"> </xref>), the AS <bcp14>MUST NOT</bcp14> respond with a single access token structure, even if only a single access token is granted. In such cases, the AS <bcp14>MUST</bcp14> respond with a multiple accesstokentokens structure containing one access token.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "access_token": [ { "label": "token2", "value": "8N6BW7OZB8CDFONP219-OS9M2PMHKUR64TBRP1LT0", "manage": { "uri": "https://server.example.com/token/PRY5NM33O", "access_token": { "value": "B8CDFONP21-4TB8N6.BW7ONM" } }, "access": [ "fruits" ] } ]]]></sourcecode></figure>]]></sourcecode> <t>The parameters of each access token are separate. For example, each access token is expected to have a unique value and (if present) label, and each access token likely has different access rights associated with it. Each access token could also be bound to different keys with different proofing mechanisms.</t> </section> </section> <sectionanchor="response-interact"><name>Interactionanchor="response-interact"> <name>Interaction Modes</name> <t>If the client instance has indicated a<xref target="request-interact">capabilitycapability to interact with the RO in itsrequest</xref>,request (<xref target="request-interact"> </xref>) and the AS has determined that interaction is both supported and necessary, the AS responds to the client instance with any of the following values in the<spanx style="verb">interact</spanx><tt>interact</tt> field of the response. There is no preference order for interaction modes in the response, and it is up to the client instance to determine which ones to use. All supported interaction methods are included in the same<spanx style="verb">interact</spanx><tt>interact</tt> object.</t> <dl><dt><spanx style="verb">redirect</spanx><dt><tt>redirect</tt> (string):</dt> <dd> <t>Redirect to an arbitrary URI. <bcp14>REQUIRED</bcp14> if the<spanx style="verb">redirect</spanx><tt>redirect</tt> interaction start mode is possible for this request. See <xref target="response-interact-redirect"/>.</t> </dd><dt><spanx style="verb">app</spanx><dt><tt>app</tt> (string):</dt> <dd> <t>Launch of an application URI. <bcp14>REQUIRED</bcp14> if the<spanx style="verb">app</spanx><tt>app</tt> interaction start mode is possible for this request. See <xref target="response-interact-app"/>.</t> </dd><dt><spanx style="verb">user_code</spanx><dt><tt>user_code</tt> (string):</dt> <dd> <t>Display a short user code. <bcp14>REQUIRED</bcp14> if the<spanx style="verb">user_code</spanx><tt>user_code</tt> interaction start mode is possible for this request. See <xref target="response-interact-usercode"/>.</t> </dd><dt><spanx style="verb">user_code_uri</spanx><dt><tt>user_code_uri</tt> (object):</dt> <dd> <t>Display a short user code and URI. <bcp14>REQUIRED</bcp14> if the<spanx style="verb">user_code_uri</spanx><tt>user_code_uri</tt> interaction start mode is possible for this request. <xref target="response-interact-usercodeuri"/></t> </dd><dt><spanx style="verb">finish</spanx><dt><tt>finish</tt> (string):</dt> <dd> <t>A unique ASCII string value provided by the AS as a nonce. This is used by the client instance to verify the callback after interaction is completed. <bcp14>REQUIRED</bcp14> if the interaction finish method requested by the client instance is possible for this request. See <xref target="response-interact-finish"/>.</t> </dd><dt><spanx style="verb">expires_in</spanx><dt><tt>expires_in</tt> (integer):</dt> <dd> <t>The number of integer seconds after which this set of interaction responses will expire and no longer be usable by the client instance. If the interaction methods expire, the client <bcp14>MAY</bcp14>re-startrestart the interaction process for this grant request by sending an<xref target="continue-modify">update</xref>update (<xref target="continue-modify"> </xref>) with a new<xref target="request-interact">interaction request</xref> section.interaction request section (<xref target="request-interact"> </xref>). <bcp14>OPTIONAL</bcp14>. If omitted, the interaction response modes returned do not expire but <bcp14>MAY</bcp14> be invalidated by the AS at any time.</t> </dd> </dl> <t>Additional interaction mode responses can be defined in the<xref target="IANA-interaction-response">GNAP"GNAP Interaction ModeResponses Registry</xref>.</t>Responses" registry (<xref target="IANA-interaction-response"> </xref>).</t> <t>The AS <bcp14>MUST NOT</bcp14> respond with any interaction mode that the client instance did not indicate in itsrequest. Therequest, and the AS <bcp14>MUST NOT</bcp14> respond with any interaction mode that the AS does not support. Since interaction responses include secret or unique information, the AS <bcp14>SHOULD</bcp14> respond to each interaction mode only once in an ongoing request, particularly if the client instance<xref target="continue-modify">modifiesmodifies itsrequest</xref>.</t>request (<xref target="continue-modify"> </xref>).</t> <t>The grant request <bcp14>MUST</bcp14> be in the <em>pending</em> state to include this field in the response.</t> <sectionanchor="response-interact-redirect"><name>Redirectionanchor="response-interact-redirect"> <name>Redirection to anarbitraryArbitrary URI</name> <t>If the client instance indicates that it can<xref target="request-interact-redirect">redirectredirect to an arbitraryURI</xref>URI (<xref target="request-interact-redirect"> </xref>) and the AS supports this mode for the client instance's request, the AS responds with the "redirect" field, which is a string containing the URI for the end user to visit. This URI <bcp14>MUST</bcp14> be unique for the request and <bcp14>MUST NOT</bcp14> contain any security-sensitive information such as user identifiers or access tokens.</t><figure><artwork><![CDATA[<artwork><![CDATA[ "interact": { "redirect": "https://interact.example.com/4CF492MLVMSW9MKMXKHQ" }]]></artwork></figure>]]></artwork> <t>The URI returned is a function of the AS, but the URI itself <bcp14>MAY</bcp14> be completely distinct from the grant endpoint URI that the client instance uses to<xref target="request">request access</xref>,request access (<xref target="request"> </xref>), allowing an AS to separate itsuser-interactiveuser-interaction functionality from its back-end security functionality. The AS will need to dereference the specific grant request and its information from the URI alone. If the AS does not directly host the functionality accessed through the redirect URI, then the means for the interaction functionality to communicate with the rest of the AS are out of scope for this specification.</t> <t>The client instance sends the end user to the URI to interact with the AS. The client instance <bcp14>MUST NOT</bcp14> alter the URI in any way. The means for the client instance to send the end user to this URIisare out of scope of this specification, but common methods include an HTTP redirect, launching the system browser, displaying a scannable code, or printing out the URI in an interactive console. See details of the interaction in <xref target="interaction-redirect"/>.</t> </section> <sectionanchor="response-interact-app"><name>Launchanchor="response-interact-app"> <name>Launch of anapplicationApplication URI</name> <t>If the client instance indicates that it can<xref target="request-interact-app">launchlaunch an applicationURI</xref>URI (<xref target="request-interact-app"> </xref>) and the AS supports this mode for the client instance's request, the AS responds with the "app" field, which is a string containing the URI for the client instance to launch. This URI <bcp14>MUST</bcp14> be unique for the request and <bcp14>MUST NOT</bcp14> contain any security-sensitive information such as user identifiers or access tokens.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "interact": { "app": "https://app.example.com/launch?tx=4CF492MLV" }]]></sourcecode></figure>]]></sourcecode> <t>The means for the launched application to communicate with the AS are out of scope for this specification.</t> <t>The client instance launches the URI as appropriate on itsplatform, andplatform; the means for the client instance to launch this URIisare out of scope of this specification. The client instance <bcp14>MUST NOT</bcp14> alter the URI in any way. The client instance <bcp14>MAY</bcp14> attempt to detect if an installed application will service the URI being sent before attempting to launch the application URI. See details of the interaction in <xref target="interaction-app"/>.</t> </section> <sectionanchor="response-interact-usercode"><name>Displayanchor="response-interact-usercode"> <name>Display of a Short User Code</name> <t>If the client instance indicates that it can<xref target="request-interact-usercode">displaydisplay ashortshort, user-typeablecode</xref>code (<xref target="request-interact-usercode"> </xref>) and the AS supports this mode for the client instance's request, the AS responds with a "user_code" field. This field is string containing a unique short code that the user can type into a web page. To facilitate usability, this string <bcp14>MUST</bcp14> consist only of characters that can be easily typed by the end user (such as ASCII letters or numbers) and <bcp14>MUST</bcp14> be processed by the AS in a case-insensitive manner (see <xref target="interaction-usercode"/>). The string <bcp14>MUST</bcp14> be randomly generated so as to be unguessable by an attacker within the time it is accepted. The time in which this code will be accepted <bcp14>SHOULD</bcp14> be short lived, such as several minutes. It is <bcp14>RECOMMENDED</bcp14> that this code beno more thanbetween six and eight characters in length.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "interact": { "user_code": "A1BC3DFF" }]]></sourcecode></figure>]]></sourcecode> <t>The client instance <bcp14>MUST</bcp14> communicate the "user_code" value to the end user in some fashion, such as displaying it on a screen or reading it out audibly. This code is used by the interaction component of the AS as a means of identifying the pending grant request and does not function as an authentication factor for the RO.</t> <t>The URI that the end user is intended to enter the code into <bcp14>MUST</bcp14> be stable, since the client instance is expected to have no means of communicating a dynamic URI to the end user at runtime.</t> <t>As this interaction mode is designed to facilitate interaction via a secondary device, it is not expected that the client instance redirect the end user to the URI where the code is entered. If the client instance is capable of communicatingana short arbitrary URI to the end user for use with the user code, the client instance <bcp14>SHOULD</bcp14> instead use the<xref target="request-interact-usercodeuri">"user_code_uri"</xref> mode."user_code_uri" mode (<xref target="request-interact-usercodeuri"></xref>). If the client instance is capable of communicating a long arbitrary URI to the end user, such as through a scannable code, the client instance <bcp14>SHOULD</bcp14> use the<xref target="request-interact-redirect">"redirect"</xref>"redirect" mode (<xref target="request-interact-redirect"> </xref>) for thispurposepurpose, instead of or in addition to the user code mode.</t> <t>See details of the interaction in <xref target="interaction-usercode"/>.</t> </section> <sectionanchor="response-interact-usercodeuri"><name>Displayanchor="response-interact-usercodeuri"> <name>Display of a Short User Code and URI</name> <t>If the client instance indicates that it can<xref target="request-interact-usercode">displaydisplay ashortshort, user-typeablecode</xref>code (<xref target="request-interact-usercode"> </xref>) and the AS supports this mode for the client instance's request, the AS responds with a "user_code_uri" object that contains the following members.</t> <dl><dt><spanx style="verb">code</spanx><dt><tt>code</tt> (string):</dt> <dd> <t>A unique short code that the end user can type into a provided URI. To facilitate usability, this string <bcp14>MUST</bcp14> consist only of characters that can be easily typed by the end user (such as ASCII letters or numbers) and <bcp14>MUST</bcp14> be processed by the AS in a case-insensitive manner (see <xref target="interaction-usercodeuri"/>). The string <bcp14>MUST</bcp14> be randomly generated so as to be unguessable by an attacker within the time it is accepted. The time in which this code will be accepted <bcp14>SHOULD</bcp14> be short lived, such as several minutes. It is <bcp14>RECOMMENDED</bcp14> that this code beno more thanbetween six and eight characters in length. <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">uri</spanx><dt><tt>uri</tt> (string):</dt> <dd> <t>The interaction URI that the client instance will direct the RO to. This URI <bcp14>MUST</bcp14> be short enough to be communicated to the end user by the client instance. It is <bcp14>RECOMMENDED</bcp14> that this URI be short enough for an end user to type in manually. The URI <bcp14>MUST NOT</bcp14> contain the<spanx style="verb">code</spanx><tt>code</tt> value. This URI <bcp14>MUST</bcp14> be an absolute URI. <bcp14>REQUIRED</bcp14>.</t> </dd> </dl><figure><sourcecode<sourcecode type="json"><![CDATA[ "interact": { "user_code_uri": { "code": "A1BC3DFF", "uri": "https://s.example/device" } }]]></sourcecode></figure>]]></sourcecode> <t>The client instance <bcp14>MUST</bcp14> communicate the "code" to the end user in some fashion, such as displaying it on a screen or reading it out audibly. This code is used by the interaction component of the AS as a means of identifying the pending grant request and does not function as an authentication factor for the RO.</t> <t>The client instance <bcp14>MUST</bcp14> also communicate the URI to the end user. Since it is expected that the end user will continue interaction on a secondary device, the URI needs to be short enough to allow the end user to type or copy it to a secondary device without mistakes.</t> <t>The URI returned is a function of the AS, but the URI itself <bcp14>MAY</bcp14> be completely distinct from the grant endpoint URI that the client instance uses to<xref target="request">request access</xref>,request access (<xref target="request"> </xref>), allowing an AS to separate itsuser-interactiveuser-interaction functionality from its back-end security functionality. If the AS does not directly host the functionality accessed through the given URI, then the means for the interaction functionality to communicate with the rest of the AS are out of scope for this specification.</t> <t>See details of the interaction in <xref target="interaction-usercode"/>.</t> </section> <sectionanchor="response-interact-finish"><name>Interactionanchor="response-interact-finish"> <name>Interaction Finish</name> <t>If the client instance indicates that it can<xref target="request-interact-finish">receivereceive a post-interaction redirect or push at aURI</xref>URI (<xref target="request-interact-finish"> </xref>) and the AS supports this mode for the client instance's request, the AS responds with a<spanx style="verb">finish</spanx><tt>finish</tt> field containing a nonce that the client instance will use in validating the callback as defined in <xref target="interaction-finish"/>.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "interact": { "finish": "MBDOFXG4Y5CVJCX821LH" }]]></sourcecode></figure>]]></sourcecode> <t>When the interaction is completed, the interaction component of the AS <bcp14>MUST</bcp14> contact the client instance using the means defined by the finish method as described in <xref target="interaction-finish"/>.</t> <t>If the AS returns the finish field, the client instance <bcp14>MUST NOT</bcp14> continue a grant request before it receives the associated interaction reference on the callback URI. See details in <xref target="interaction-finish"/>.</t> </section> </section> <sectionanchor="response-subject"><name>Returninganchor="response-subject"> <name>Returning Subject Information</name> <t>If information about the RO is requested and the AS grants the client instance access to that data, the AS returns the approved information in the "subject" response field. The AS <bcp14>MUST</bcp14> return the<spanx style="verb">subject</spanx><tt>subject</tt> field only in cases where the AS is sure that the RO and the end user are the same party. This can be accomplished through some forms of<xref target="authorization">interactioninteraction with theRO</xref>.</t>RO (<xref target="authorization"> </xref>).</t> <t>This field is an object with the following properties.</t> <dl><dt><spanx style="verb">sub_ids</spanx><dt><tt>sub_ids</tt> (array of objects):</dt> <dd> <t>An array of subject identifiers for the RO, as defined by <xref target="RFC9493"/>. <bcp14>REQUIRED</bcp14> if returning subject identifiers.</t> </dd><dt><spanx style="verb">assertions</spanx><dt><tt>assertions</tt> (array of objects):</dt> <dd> <t>An array containing assertions asobjectsobjects, each containing the assertion object described below. <bcp14>REQUIRED</bcp14> if returning assertions.</t> </dd><dt><spanx style="verb">updated_at</spanx><dt><tt>updated_at</tt> (string):</dt> <dd> <t>Timestamp asan <xref target="RFC3339"/>a datestring,string as described in <xref target="RFC3339"/>, indicating when the identified account was last updated. The client instance <bcp14>MAY</bcp14> use this value to determine if it needs to request updated profile information through an identity API. The definition of such an identity API is out of scope for this specification. <bcp14>RECOMMENDED</bcp14>.</t> </dd> </dl> <t>Assertion objects contain the following fields:</t> <dl><dt><spanx style="verb">format</spanx><dt><tt>format</tt> (string):</dt> <dd> <t>The assertion format. Possible formats are listed in <xref target="assertion-formats"/>. Additional assertion formatsarecan be definedbyin the<xref target="IANA-assertion-formats">GNAP"GNAP AssertionFormats Registry</xref>.Formats" registry (<xref target="IANA-assertion-formats"> </xref>). <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">value</spanx><dt><tt>value</tt> (string):</dt> <dd> <t>The assertion value as the JSON string serialization of the assertion. <bcp14>REQUIRED</bcp14>.</t> </dd> </dl> <t>The following non-normative example contains an opaque identifier and an OpenID Connect ID Token:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "subject": { "sub_ids": [ { "format": "opaque", "id": "XUT2MFM1XBIKJKSDU8QM" } ], "assertions": [ { "format": "id_token", "value": "eyj..." } ] }]]></sourcecode></figure>]]></sourcecode> <t>Subject identifiers returned by the AS <bcp14>SHOULD</bcp14> uniquely identify the RO at the AS. Some forms of subjectidentifieridentifiers are opaque to the client instance (such as the subject of an issuer and subject pair), whileothersother forms (such as email address and phone number) are intended to allow the client instance to correlate the identifier with other account information at the client instance. The client instance <bcp14>MUST NOT</bcp14> request or use any returned subject identifiers for communication purposes (see <xref target="request-subject"/>). That is, a subject identifier returned in the format of an email address or a phone number only identifies the RO to the AS and does not indicate that the AS has validated that the represented email address or phone number in the identifier is suitable for communication with the current user. To get such information, the client instance <bcp14>MUST</bcp14> use an identity protocol to request and receive additional identity claims. The details of an identity protocol and associated schema are outside the scope of this specification.</t> <t>The AS <bcp14>MUST</bcp14> ensure that the returned subject information represents the RO. In most cases, the AS will also ensure that the returned subject information represents the end user authenticated interactively at the AS. The AS <bcp14>SHOULD NOT</bcp14>re-usereuse subject identifiers for multiple different ROs.</t> <t>The "sub_ids" and "assertions" response fields are independent of each other. That is, a returned assertion <bcp14>MAY</bcp14> use a different subject identifier than other assertions and subject identifiers in the response. However, all subject identifiers and assertions returned <bcp14>MUST</bcp14> refer to the same party.</t> <t>The client instance <bcp14>MUST</bcp14> interpret all subject information in the context of the AS from which the subject information is received, as is discussed in Section 6 of <xref target="SP80063C"/>. For example, one AS could return an email identifier of "user@example.com" for one RO, and a different AS could return that same email identifier of "user@example.com" for a completely different RO. A client instance talking to bothAS'sASes needs to differentiate between these two accounts by accounting for the AS source of each identifier and not assuming that either has a canonical claim on the identifier without additional configuration and trust agreements. Otherwise, a rogue AS could exploit this to take over a targeted account asserted by a different AS.</t> <t>Extensions to this specification <bcp14>MAY</bcp14> define additional response properties in the<xref target="IANA-subject-response">GNAP"GNAP Subject Information ResponseFields Registry</xref>.</t>Fields" registry (<xref target="IANA-subject-response"> </xref>).</t> <t>The grant request <bcp14>MUST</bcp14> be in the <em>approved</em> state to return this field in the response.</t> <t>See <xref target="security-assertions"/> for considerations that the client instance has to make when accepting and processing assertions from the AS.</t> <sectionanchor="assertion-formats"><name>Assertionanchor="assertion-formats"> <name>Assertion Formats</name> <t>The following assertion formats are defined in this specification:</t> <dl><dt><spanx style="verb">id_token</spanx>:</dt><dt><tt>id_token</tt>:</dt> <dd> <t>An OpenID Connect ID Token(<xref target="OIDC"/>),<xref target="OIDC"/>, inJWTJSON Web Token (JWT) compact format as a single string.</t> </dd><dt><spanx style="verb">saml2</spanx>:</dt><dt><tt>saml2</tt>:</dt> <dd> <t>A SAML 2 assertion(<xref target="SAML2"/>),<xref target="SAML2"/>, encoded as a single base64url string with no padding.</t> </dd> </dl> </section> </section> <sectionanchor="response-dynamic-handles"><name>Returninganchor="response-dynamic-handles"> <name>Returning aDynamically-boundDynamically Bound Client Instance Identifier</name> <t>Many parts of the client instance's request can be passed as either a value or a reference. The use of a reference in place of a value allows for a client instance to optimize requests to the AS.</t> <t>Some references, such as for the<xref target="request-instance">clientclient instance'sidentity</xref>identity (<xref target="request-instance"> </xref>) or the<xref target="resource-access-reference">requested resources</xref>,requested resources (<xref target="resource-access-reference"> </xref>), can be managed statically through an admin console or developer portal provided by the AS or RS. The developer of the client software can include these values in their code for a more efficient and compact request.</t> <t>If desired, the AS <bcp14>MAY</bcp14> also generate and return an instance identifier dynamically to the client instance in the response to facilitate multiple interactions with the same client instance over time. The client instance <bcp14>SHOULD</bcp14> use this instance identifier in future requests in lieu of sending the associated data values in the<spanx style="verb">client</spanx><tt>client</tt> field.</t> <t>Dynamically generated client instance identifiers are string values that <bcp14>MUST</bcp14> be protected by the client instance as secrets. Instance identifier values <bcp14>MUST</bcp14> be unguessable and <bcp14>MUST NOT</bcp14> contain any information that would compromise any party if revealed. Instance identifier values are opaque to the client instance, and their content is determined by the AS. The instance identifier <bcp14>MUST</bcp14> be unique per client instance at the AS.</t> <dl><dt><spanx style="verb">instance_id</spanx><dt><tt>instance_id</tt> (string):</dt> <dd> <t>A string value used to represent the information in the<spanx style="verb">client</spanx><tt>client</tt> object that the client instance can use in a future request, as described in <xref target="request-instance"/>. <bcp14>OPTIONAL</bcp14>.</t> </dd> </dl> <t>The following non-normative example shows an instance identifieralong sidealongside an issued access token.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "instance_id": "7C7C4AZ9KHRS6X63AJAO", "access_token": { "value": "OS9M2PMHKUR64TB8N6BW7OZB8CDFONP219RP1LT0" } }]]></sourcecode></figure>]]></sourcecode> </section> <sectionanchor="response-error"><name>Erroranchor="response-error"> <name>Error Response</name> <t>If the AS determines that the request cannot be completed for any reason, it responds to the client instance with an<spanx style="verb">error</spanx><tt>error</tt> field in the response message. This field is either an object or a string.</t> <t>When returned as an object, the object contains the following fields:</t> <dl><dt><spanx style="verb">code</spanx><dt><tt>code</tt> (string):</dt> <dd> <t>A single ASCII error code defining the error. The value <bcp14>MUST</bcp14> be defined in the<xref target="IANA-error-code">GNAP"GNAP ErrorCodes Registry</xref>.Codes" registry (<xref target="IANA-error-code"> </xref>). <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">description</spanx><dt><tt>description</tt> (string):</dt> <dd> <t>A human-readable string description of the error intended for the developer of the client. The value is chosen by the implementation. <bcp14>OPTIONAL</bcp14>.</t> </dd> </dl> <t>This specification defines the following<spanx style="verb">code</spanx><tt>code</tt> values:</t> <dl><dt><spanx style="verb">"invalid_request"</spanx>:</dt><dt><tt>"invalid_request"</tt>:</dt> <dd> <t>The request is missing a required parameter, includes an invalid parametervaluevalue, or is otherwise malformed.</t> </dd><dt><spanx style="verb">"invalid_client"</spanx>:</dt><dt><tt>"invalid_client"</tt>:</dt> <dd> <t>The request was made from a client that was not recognized or allowed by the AS, or the client's signature validation failed.</t> </dd><dt><spanx style="verb">"invalid_interaction"</spanx></dt><dt><tt>"invalid_interaction"</tt>:</dt> <dd> <t>The client instance has provided an interaction reference that is incorrect for thisrequestrequest, or the interaction modes in use have expired.</t> </dd><dt><spanx style="verb">"invalid_flag"</spanx></dt><dt><tt>"invalid_flag"</tt>:</dt> <dd> <t>The flag configuration is not valid.</t> </dd><dt><spanx style="verb">"invalid_rotation"</spanx></dt><dt><tt>"invalid_rotation"</tt>:</dt> <dd> <t>The token rotation request is not valid.</t> </dd><dt><spanx style="verb">"key_rotation_not_supported"</spanx></dt><dt><tt>"key_rotation_not_supported"</tt>:</dt> <dd> <t>The AS does not allow rotation of this access token's key.</t> </dd><dt><spanx style="verb">"invalid_continuation"</spanx>:</dt><dt><tt>"invalid_continuation"</tt>:</dt> <dd> <t>The continuation of the referenced grant could not be processed.</t> </dd><dt><spanx style="verb">"user_denied"</spanx>:</dt><dt><tt>"user_denied"</tt>:</dt> <dd> <t>The RO denied the request.</t> </dd><dt><spanx style="verb">"request_denied"</spanx>:</dt><dt><tt>"request_denied"</tt>:</dt> <dd> <t>The request was denied for an unspecified reason.</t> </dd><dt><spanx style="verb">"unknown_user"</spanx>:</dt><dt><tt>"unknown_user"</tt>:</dt> <dd> <t>The user presented in the request is not known to the AS or does not match the user present during interaction.</t> </dd><dt><spanx style="verb">"unknown_interaction"</spanx>:</dt><dt><tt>"unknown_interaction"</tt>:</dt> <dd> <t>The interaction integrity could not be established.</t> </dd><dt><spanx style="verb">"too_fast"</spanx>:</dt><dt><tt>"too_fast"</tt>:</dt> <dd> <t>The client instance did not respect the timeout in the wait response before the next call.</t> </dd><dt><spanx style="verb">"too_many_attempts"</spanx>:</dt><dt><tt>"too_many_attempts"</tt>:</dt> <dd> <t>A limit has been reached in the total number of reasonable attempts. This number is either defined statically or adjusted based on runtime conditions by the AS.</t> </dd> </dl> <t>Additional error codes can be defined in the<xref target="IANA-error-code">GNAP"GNAP ErrorCodes Registry</xref>.</t>Codes" registry (<xref target="IANA-error-code"> </xref>).</t> <t>For example, if the RO denied the request while interacting with the AS, the AS would return the following error when the client instance tries to continue the grant request:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "error": { "code": "user_denied", "description": "The RO denied the request" } }]]></sourcecode></figure>]]></sourcecode> <t>Alternatively, the AS <bcp14>MAY</bcp14> choose to only return the error as codes and provide the error as a string. Since the<spanx style="verb">description</spanx><tt>description</tt> field is not intended to be machine-readable, the following response is considered functionally equivalent to the previous example for the purposes of the client software's understanding:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "error": "user_denied" }]]></sourcecode></figure>]]></sourcecode> <t>If an error state is reached but the grant is in the <em>pending</em> state (and therefore the client instance can continue), the AS <bcp14>MAY</bcp14> include the<spanx style="verb">continue</spanx><tt>continue</tt> field in the response along with the<spanx style="verb">error</spanx>,<tt>error</tt>, as defined in <xref target="response-continue"/>. This allows the client instance to modify its request for access, potentially leading to prompting the RO again. Other fields <bcp14>MUST NOT</bcp14> be included in the response.</t> </section> </section> <sectionanchor="authorization"><name>Determininganchor="authorization"> <name>Determining Authorization and Consent</name> <t>When the client instance makes its<xref target="request">initial request</xref>initial request (<xref target="request"> </xref>) to the AS for delegated access, it is capable of asking for several different kinds of information in response:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>the access being requested, in the<spanx style="verb">access_token</spanx><tt>access_token</tt> request parameter</t> </li> <li> <t>the subject information being requested, in the<spanx style="verb">subject</spanx><tt>subject</tt> request parameter</t> </li> <li> <t>any additional requested information defined by extensions of this protocol</t></list></t></li> </ul> <t>When the grant request is in the <em>processing</em> state, the AS determines what authorizations and consents are required to fulfill this requested delegation. The details of how the AS makes this determination are out of scope for this document. However, there are several common patterns defined and supported by GNAP for fulfilling these requirements, including information sent by the client instance, information gathered through the interaction process, and information supplied by external parties. An individual AS can define its own policies and processes for deciding when and how to gather the necessary authorizations andconsent,consent and how those are applied to the grant request.</t> <t>To facilitate the AS fulfilling this request, the client instance sends information about the actions the client software can take, including:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>starting interaction with the end user, in the<spanx style="verb">interact</spanx><tt>interact</tt> request parameter</t> </li> <li> <t>receiving notification that interaction with the RO has concluded, in the<spanx style="verb">interact</spanx><tt>interact</tt> request parameter</t> </li> <li> <t>any additional capabilities defined by extensions of this protocol</t></list></t></li> </ul> <t>The client instance can also supply information directly to the AS in its request. The client instance can send several kinds of things, including:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>the identity of the client instance, known from the keys or identifiers in the<spanx style="verb">client</spanx><tt>client</tt> request parameter</t> </li> <li> <t>the identity of the end user, in the<spanx style="verb">user</spanx><tt>user</tt> request parameter</t> </li> <li> <t>any additional information presented by the client instance in the request defined by extensions of this protocol</t></list></t></li> </ul> <t>The AS will process this presented information in the context of the client instance's request and can only trust the information as much as it trusts the presentation and context of that request. If the AS determines that the information presented in the initial request is sufficient for granting the requested access, the AS <bcp14>MAY</bcp14> move the grant request to the <em>approved</em> state and return results <xref target="response">immediately in its response</xref> with access tokens and subject information.</t> <t>If the AS determines that additional runtime authorization is required, the AS can either deny the request outright (if there is no possible recovery) or move the grant request to the <em>pending</em> state and use a number of means at its disposal to gather that authorization from the appropriate ROs,including for example:</t> <t><list style="symbols">including:</t> <ul spacing="normal"> <li> <t>starting interaction with the end user facilitated by the client software, such as a redirection or user code</t> </li> <li> <t>challenging the client instance through a challenge-response mechanism</t> </li> <li> <t>requesting that the client instance present specific additional information, such as a user's credential or an assertion</t> </li> <li> <t>contacting an RO through an out-of-band mechanism, such as a push notification</t> </li> <li> <t>executing an auxiliary software process through an out-of-band mechanism, such as querying a digital wallet</t></list></t></li> </ul> <!-- [rfced] Please clarify "authorization and consent gathering process". Is "authorization" gathered, or just consent? Original: The authorization and consent gathering process in GNAP is left deliberately flexible to allow for a wide variety of different deployments, interactions, and methodologies. Perhaps: The authorization and consent-gathering process in GNAP is left deliberately flexible to allow for a wide variety of different deployments, interactions, and methodologies. Or: The process of gathering authorization and consent in GNAP is left deliberately flexible to allow for a wide variety of different deployments, interactions, and methodologies. --> <t>The authorization and consent gathering process in GNAP is left deliberately flexible to allow for a wide variety of different deployments, interactions, and methodologies. In this process, the AS can gather consent from the RO or apply the RO's policy as necessitated by the access that has been requested. The AS can sometimes determine which RO needs to prompt for consent based on what has been requested by the client instance, such as a specific RS record, an identified subject, or a request requiring specific access such as approval by an administrator. In other cases, the request is applied to whichever RO is present at the time of consent gathering. This pattern is especially prevalent when the end user is sent to the AS for an interactive session, during which the end user takes on the role of the RO. In these cases, the end user is delegating their own access as RO to the client instance.</t> <t>The client instance can indicate that it is capable of facilitating interaction with the end user, another party, or another piece of software through its<xref target="request-interact-start">interaction start</xref> request.interaction start request (<xref target="request-interact-start"></xref>). Here, the AS usually needs to interact directly with the end user to determine their identity, determine their status as an RO, and collect their consent. If the AS has determined that authorization is required and the AS can support one or more of the requested interaction start methods, the AS returns the associated<xref target="response-interact">interactioninteraction startresponses</xref>.responses (<xref target="response-interact"> </xref>). The client instance <bcp14>SHOULD</bcp14><xref target="interaction-start">initiateinitiate one or more of these interactionmethods</xref>methods (<xref target="interaction-start"> </xref>) in order to facilitate the granting of the request. If more than one interaction start method is available, the means by which the client chooses which methods to followisare out of scope of this specification.</t> <t>After starting interaction, the client instance can then make a<xref target="continue-request">continuation request</xref>continuation request (<xref target="continue-request"> </xref>) either in response to a signal indicating the<xref target="interaction-finish">finishfinish of theinteraction</xref>,interaction (<xref target="interaction-finish"> </xref>), after a time-based polling, or through some other method defined by an extension of this specification through the<xref target="IANA-interaction-response">GNAP"GNAP Interaction ModeResponses registry</xref>.</t>Responses" registry (<xref target="IANA-interaction-response"></xref>).</t> <t>If the grant request is not in the <em>approved</em> state, the client instance can repeat the interaction process by sending a<xref target="continue-modify">grantgrant updaterequest</xref>request (<xref target="continue-modify"></xref>) with new<xref target="request-interact">interaction</xref> methods.</t>interaction methods (<xref target="request-interact"> </xref>).</t> <t>The client instance <bcp14>MUST</bcp14> use each interaction method once at mostonce,if a response can be detected. The AS <bcp14>MUST</bcp14> handle any interact request as a one-time-use mechanism and <bcp14>SHOULD</bcp14> apply suitable timeouts to any interaction start methods provided, including user codes and redirection URIs. The client instance <bcp14>SHOULD</bcp14> apply suitable timeouts to any interaction finish method.</t> <t>In order to support client software deployed in disadvantaged network conditions, the AS <bcp14>MAY</bcp14> allow for processing of the same interaction method multiple times if the AS can determine that the request is from the same party and the results are idempotent. For example, if a client instance launches a redirect to the AS but does not receive a response within a reasonable time, the client software can launch the redirect again, assuming that it never reached the AS in the first place. However, if the AS in question receives both requests, it could mistakenly process them separately, creating an undefined state for the client instance. If the AS can determine that both requests come from the same origin or under the same session, and the requests both came before any additional state change to the grant occurs, the AS can reasonably conclude that the initial response was not received and the same response can be returned to the client instance.</t> <t>If the AS instead has a means of contacting the RO directly, it could do so without involving the client instance in itsconsent gatheringconsent-gathering process. For example, the AS could push a notification to a known RO and have the RO approve the pending request asynchronously. These interactions can be through an interface of the AS itself (such as a hosted web page), through another application (such as something installed on the RO's device), through a messaging fabric, or any other means.</t> <!-- [rfced] Please review "can do anything it needs to determine" here. Would updating as follows be helpful? Original: When interacting with an RO, the AS can do anything it needs to determine the authorization of the requested grant, including: Perhaps: When interacting with an RO, the AS can use various strategies to determine the authorization of the requested grant, including: --> <t>When interacting with an RO, the AS can do anything it needs to determine the authorization of the requested grant, including:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>authenticate theRO,RO through a local account or some othermeansmeans, such as federated login</t> </li> <li> <t>validate the RO through presentation of claims, attributes, or other information</t> </li> <li> <t>prompt the RO for consent for the requested delegation</t> </li> <li> <t>describe to the RO what information is being released, to whom, and for what purpose</t> </li> <li> <t>provide warnings to the RO about potential attacks or negative effects of allowing the information</t> </li> <li> <t>allow the RO to modify the client instance's requested access, including limiting or expanding that access</t> </li> <li> <t>provide the RO with artifacts such as receipts to facilitate an audit trail of authorizations</t> </li> <li> <t>allow the RO to deny the requested delegation</t></list></t></li> </ul> <!-- [rfced] Will readers know that "N" and "M" refer to here? Original: Alternatively, the AS could require N of M possible RO's to approve a given request. --> <t>The AS is also allowed to request authorization from more than one RO, if the AS deems fit. For example, a medical record might need to be released by both an attending nurse and a physician, or both owners of a bank account need to sign off on a transfer request. Alternatively, the AS could require N of M possibleRO'sROs to approve a given request. In some circumstances, the AS could even determine that the end user present during the interaction is not the appropriate RO for a given request and reach out to the appropriate RO asynchronously.</t> <t>The RO is also allowed to define an automated policy at the AS to determine which kind of end user can get access to theresource,resource and under whichcondition.conditions. For instance, such a condition might require the end userloginto log in andthe acceptance ofaccept the RO's legal provisions. Alternatively, client software could be acting without an end user, and the RO's policy allows issuance of access tokens to specific instances of that client software without human interaction.</t><t>While<!-- [rfced] May we update the text starting with ", and for determining..." as follows for clarity? Original: While all of these cases are supported by GNAP, the details of their implementation, and for determining which RO's or related policies are required for a given request, are out of scope for this specification. Perhaps: While all of these cases are supported by GNAP, the details of their implementation and the methods for determining which ROs or related policies are required for a given request are out of scope for this specification. --> <t>While all of these cases are supported by GNAP, the details of their implementation, and for determining which ROs or related policies are required for a given request, are out of scope for this specification.</t> <sectionanchor="interaction-start"><name>Startinganchor="interaction-start"> <name>Starting InteractionWithwith the End User</name> <t>When a grant request is in the <em>pending</em> state, the interaction start methods sent by the client instance can be used to facilitate interaction with the end user. To initiate an interaction start method indicated by the<xref target="response-interact">interactioninteraction startresponses</xref>responses (<xref target="response-interact"> </xref>) from the AS, the client instance follows the steps defined by that interaction start mode. The actions of the client instance required for the interaction start modes defined in this specification are described in the followingsections.subsections. Interaction start modes defined in extensions to this specification <bcp14>MUST</bcp14> define the expected actions of the client software when that interaction start mode is used.</t> <t>If the client instance does not start an interaction start mode within an AS-determined amount of time, the AS <bcp14>MUST</bcp14> reject attempts to use the interaction start modes. If the client instance has already begun one interaction start mode and the interaction has been successfully completed, the AS <bcp14>MUST</bcp14> reject attempts to use other interaction start modes. For example, if a user code has been successfully entered for a grant request, the AS will need to reject requests to an arbitrary redirect URI on the same grant request in order to prevent an attacker from capturing and altering an active authorization process.</t> <sectionanchor="interaction-redirect"><name>Interactionanchor="interaction-redirect"> <name>Interaction at a Redirected URI</name> <t>When the end user is directed to an arbitrary URI through the<xref target="response-interact-redirect">"redirect"</xref> mode,"redirect" mode (<xref target="response-interact-redirect"> </xref>), the client instance facilitates opening the URI through the end user's web browser. The client instance could launch the URI through the system browser, provide a clickable link, redirect the user through HTTP response codes, or display the URI in a form the end user can use tolaunchlaunch, such as a multidimensional barcode. In all cases, the URI is accessed with an HTTP GET request, and the resulting page is assumed to allow direct interaction with the end user through an HTTP user agent. With this method, it is common (though not required) for the RO to be the same party as the end user, since the client instance has to communicate the redirection URI to the end user.</t> <t>In many cases, the URI indicates a web page hosted at the AS, allowing the AS to authenticate the end user as the RO and interactively provide consent. The URI value is used to identify the grant request being authorized. If the URI cannot be associated with a currently active request, the AS <bcp14>MUST</bcp14> display an error to the RO and <bcp14>MUST NOT</bcp14> attempt to redirect the RO back to any clientinstanceinstance, even if a<xref target="request-interact-callback-redirect">redirectredirect finish method issupplied</xref>.supplied (<xref target="request-interact-callback-redirect"> </xref>). If the URI is not hosted by the AS directly, the means of communication between the AS and the service provided by this URI are out of scope for this specification.</t> <t>The client instance <bcp14>MUST NOT</bcp14> modify the URI when launchingit,it; inparticularparticular, the client instance <bcp14>MUST NOT</bcp14> add any parameters to the URI. The URI <bcp14>MUST</bcp14> be reachable from the end user's browser, though the URI <bcp14>MAY</bcp14> be opened on a separate device from the client instance itself. The URI <bcp14>MUST</bcp14> be accessible from an HTTP GET request and <bcp14>MUST</bcp14> be protected by HTTPS, be hosted on a server local to the RO's browser ("localhost"), or use an application-specific URI scheme that is loaded on the end user's device.</t> </section> <sectionanchor="interaction-usercode"><name>Interactionanchor="interaction-usercode"> <name>Interaction at the Static User Code URI</name> <t>When the end user is directed to enter a short code through the<xref target="response-interact-usercode">"user_code"</xref> mode,"user_code" mode (<xref target="response-interact-usercode"> </xref>), the client instance communicates the user code to the end user and directs the end user to enter that code at an associated URI. The client instance <bcp14>MAY</bcp14> format the user code in such a way as to facilitate memorability and transfer of the code, so long as this formatting does not alter the value as accepted at the user code URI. For example, a client instance receiving the user code "A1BC3DFF" could choose to display this to the user as "A1BC 3DFF", breaking up the long string into two shorter strings.</t> <t>When processing input codes, the AS <bcp14>MUST</bcp14> transform the input string to remove invalid characters. In the above example, the space in between the two parts would be removed upon its entry into the interactive form at the user code URI. Additionally, the AS <bcp14>MUST</bcp14> treat user input as case insensitive. For example, if the user inputs the string "a1bc 3DFF", the AS will treat the input the same as "A1BC3DFF". To facilitate this, it is <bcp14>RECOMMENDED</bcp14> that the AS use only ASCII letters and numbers as valid characters for the user code.</t> <t>It is <bcp14>RECOMMENDED</bcp14> that the AS choose from character values that are easily copied and typed without ambiguity. For example, some glyphs have multiple Unicode code points for the same visual character, and theend-userend user could potentially type a different character than what the AS has returned. For additional considerations of internationalized character strings, see <xreftarget="RFC8264"/></t>target="RFC8264"/>.</t> <t>This mode is designed to be used when the client instance is not able to communicate or facilitate launching an arbitrary URI. The associated URI could be statically configured with the client instance or in the client software's documentation. As a consequence, these URIs <bcp14>SHOULD</bcp14> be short. The user code URI <bcp14>MUST</bcp14> be reachable from the end user's browser, though the URI is usually opened on a separate device from the client instance itself. The URI <bcp14>MUST</bcp14> be accessible from an HTTP GET request and <bcp14>MUST</bcp14> be protected by HTTPS, be hosted on a server local to the RO's browser ("localhost"), or use an application-specific URI scheme that is loaded on the end user's device.</t> <t>In many cases, the URI indicates a web page hosted at the AS, allowing the AS to authenticate the end user as the RO and interactively provide consent. The value of the user code is used to identify the grant request being authorized. If the user code cannot be associated with a currently active request, the AS <bcp14>MUST</bcp14> display an error to the RO and <bcp14>MUST NOT</bcp14> attempt to redirect the RO back to any clientinstanceinstance, even if a<xref target="request-interact-callback-redirect">redirectredirect finish method issupplied</xref>.supplied (<xref target="request-interact-callback-redirect"> </xref>). If the interaction component at the user code URI is not hosted by the AS directly, the means of communication between the AS and this URI, including communication of the user code itself, are out of scope for this specification.</t> <t>When the RO enters this code at the user code URI, the AS <bcp14>MUST</bcp14> uniquely identify the pending request that the code was associated with. If the AS does not recognize the entered code, the interaction component <bcp14>MUST</bcp14> display an error to the user. If the AS detects too many unrecognized code enter attempts, the interaction component <bcp14>SHOULD</bcp14> display an error to the user indicating too many attempts and <bcp14>MAY</bcp14> take additional actions such as slowing down the input interactions. The user should be warned as such an error state is approached, if possible.</t> </section> <sectionanchor="interaction-usercodeuri"><name>Interactionanchor="interaction-usercodeuri"> <name>Interaction at a Dynamic User Code URI</name> <t>When the end user is directed to enter a short code through the<xref target="response-interact-usercodeuri">"user_code_uri"</xref> mode,"user_code_uri" mode (<xref target="response-interact-usercodeuri"> </xref>), the client instance communicates the user code and associated URI to the end user and directs the end user to enter that code at the URI. The client instance <bcp14>MAY</bcp14> format the user code in such a way as to facilitate memorability and transfer of the code, so long as this formatting does not alter the value as accepted at the user code URI. For example, a client instance receiving the user code "A1BC3DFF" could choose to display this to the user as "A1BC 3DFF", breaking up the long string into two shorter strings.</t> <t>When processing input codes, the AS <bcp14>MUST</bcp14> transform the input string to remove invalid characters. In the above example, the space in between the two parts would be removed upon its entry into the interactive form at the user code URI. Additionally, the AS <bcp14>MUST</bcp14> treat user input as case insensitive. For example, if the user inputs the string "a1bc 3DFF", the AS will treat the input the same as "A1BC3DFF". To facilitate this, it is <bcp14>RECOMMENDED</bcp14> that the AS use only ASCII letters and numbers as valid characters for the user code.</t> <t>This mode is used when the client instance is not able to facilitate launching a complex arbitrary URI but can communicate arbitrary values like URIs. As a consequence, these URIs <bcp14>SHOULD</bcp14> be short enough to allow the URI to be typed by the end user, such as a total length of 20 characters or fewer. The client instance <bcp14>MUST NOT</bcp14> modify the URI when communicating it to the end user; in particular the client instance <bcp14>MUST NOT</bcp14> add any parameters to the URI. The user code URI <bcp14>MUST</bcp14> be reachable from the end user's browser, though the URI is usually be opened on a separate device from the client instance itself. The URI <bcp14>MUST</bcp14> be accessible from an HTTP GET request and <bcp14>MUST</bcp14> be protected by HTTPS, be hosted on a server local to the RO's browser ("localhost"), or use an application-specific URI scheme that is loaded on the end user's device.</t> <t>In many cases, the URI indicates a web page hosted at the AS, allowing the AS to authenticate the end user as the RO and interactively provide consent. The value of the user code is used to identify the grant request being authorized. If the user code cannot be associated with a currently active request, the AS <bcp14>MUST</bcp14> display an error to the RO and <bcp14>MUST NOT</bcp14> attempt to redirect the RO back to any clientinstanceinstance, even if a<xref target="request-interact-callback-redirect">redirectredirect finish method issupplied</xref>.supplied (<xref target="request-interact-callback-redirect"> </xref>). If the interaction component at the user code URI is not hosted by the AS directly, the means of communication between the AS and this URI, including communication of the user code itself, are out of scope for this specification.</t> <t>When the RO enters this code at the given URI, the AS <bcp14>MUST</bcp14> uniquely identify the pending request that the code was associated with. If the AS does not recognize the entered code, the interaction component <bcp14>MUST</bcp14> display an error to the user. If the AS detects too many unrecognized code enter attempts, the interaction component <bcp14>SHOULD</bcp14> display an error to the user indicating too many attempts and <bcp14>MAY</bcp14> take additional actions such as slowing down the input interactions. The user should be warned as such an error state is approached, if possible.</t> </section> <sectionanchor="interaction-app"><name>Interactionanchor="interaction-app"> <name>Interaction through an Application URI</name> <t>When the client instance is directed to launch an application through the<xref target="response-interact-app">"app"</xref> mode,"app" mode (<xref target="response-interact-app"> </xref>), the client launches the URI as appropriate to the system, such as through a deep link or custom URI scheme registered to a mobile application. The means by which the AS and the launched application communicate with each other and perform any of the required actions are out of scope for this specification.</t> </section> </section> <sectionanchor="interaction-finish"><name>Post-Interactionanchor="interaction-finish"> <name>Post-Interaction Completion</name> <t>If an interaction<xref target="response-interact-finish">"finish"</xref>"finish" method (<xref target="response-interact-finish"> </xref>) is associated with the current request, the AS <bcp14>MUST</bcp14> follow the appropriate method upon completion of interaction in order to signal the client instance to continue, except for some limited error cases discussed below. If a finish method is not available, the AS <bcp14>SHOULD</bcp14> instruct the RO to return to the client instance upon completion. In such cases, it is expected that the client instance will poll the continuation endpoint as described in <xref target="continue-poll"/>.</t> <t>The AS <bcp14>MUST</bcp14> create an interaction reference and associate that reference with the current interaction and the underlying pending request. The interaction reference value is an ASCII string consisting of only unreserved characters per <xref section="2.3" sectionFormat="of" target="RFC3986"/>. The interaction reference value <bcp14>MUST</bcp14> be sufficiently random so as not to be guessable by an attacker. The interaction reference <bcp14>MUST</bcp14> be one-time-use to prevent interception and replay attacks.</t> <t>The AS <bcp14>MUST</bcp14> calculate a hash value based on the clientinstance andinstance, ASnoncesnonces, and the interaction reference, as described in <xref target="interaction-hash"/>. The client instance will use this value to validate the "finish" call.</t> <t>All interaction finish methods <bcp14>MUST</bcp14> define a way to convey the hash and interaction reference back to the client instance. When an interaction finish method is used, the client instance <bcp14>MUST</bcp14> present the interaction reference back to the AS as part of its<xref target="continue-after-interaction">continuation request</xref>.</t>continuation request (<xref target="continue-after-interaction"> </xref>).</t> <t>Note that in many error cases, such as when the RO has denied access, the "finish" method is still enacted by the AS. This pattern allows the client instance to potentially recover from the error state by modifying its request or providing additional information directly to the AS in a continuation request. The AS <bcp14>MUST NOT</bcp14> follow the "finish" method in the following circumstances:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>The AS has determined that any URIs involved with the finish method are dangerous or blocked.</t> </li> <li> <t>The AS cannot determine which ongoing grant request is being referenced.</t> </li> <li> <t>The ongoing grant request has beencancelledcanceled or otherwise blocked.</t></list></t></li> </ul> <sectionanchor="interaction-callback"><name>Completinganchor="interaction-callback"> <name>Completing Interaction with a Browser Redirect to the Callback URI</name> <t>When using the<spanx style="verb">redirect</spanx><tt>redirect</tt> interaction finish method defined in Sections <xreftarget="request-interact-callback-redirect"/>target="request-interact-callback-redirect" format="counter"/> and <xreftarget="response-interact-finish"/>,target="response-interact-finish" format="counter"/>, the AS signals to the client instance that interaction is complete and the request can be continued by directing the RO (in their browser) back to the client instance's redirect URI.</t> <t>The AS secures this redirect by adding the hash and interaction reference as query parameters to the client instance's redirect URI.</t> <dl><dt><spanx style="verb">hash</spanx>:</dt><dt><tt>hash</tt>:</dt> <dd> <t>The interaction hash value as described in <xref target="interaction-hash"/>. <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">interact_ref</spanx>:</dt><dt><tt>interact_ref</tt>:</dt> <dd> <t>The interaction reference generated for this interaction. <bcp14>REQUIRED</bcp14>.</t> </dd> </dl> <t>The means of directing the RO to this URI are outside the scope of this specification, but common options include redirecting the RO from a web page and launching the system browser with the target URI. See <xref target="security-redirect-status-codes"/> for considerations on which HTTP status code to use when redirecting a request that potentially contains credentials.</t><figure><artwork><![CDATA[<artwork><![CDATA[ NOTE: '\' line wrapping per RFC 8792 https://client.example.net/return/123455\ ?hash=x-gguKWTj8rQf7d7i3w3UhzvuJ5bpOlKyAlVpLxBffY\ &interact_ref=4IFWWIKYBC2PQ6U56NL1]]></artwork></figure>]]></artwork> <t>The client instance <bcp14>MUST</bcp14> be able to process a request on the URI. If the URI is HTTP, the request <bcp14>MUST</bcp14> be an HTTP GET.</t> <t>When receiving the request, the client instance <bcp14>MUST</bcp14> parse the query parameters to extract the hash and interaction reference values. The client instance <bcp14>MUST</bcp14> calculate and validate the hash value as described in <xref target="interaction-hash"/>. If the hash validates, the client instance sends a continuation request to the AS as described in <xreftarget="continue-after-interaction"/>target="continue-after-interaction"/>, using the interaction reference value received here. If the hash does not validate, the client instance <bcp14>MUST NOT</bcp14> send the interaction reference to the AS.</t> </section> <sectionanchor="interaction-pushback"><name>Completinganchor="interaction-pushback"> <name>Completing Interaction with a Direct HTTP Request Callback</name> <t>When using the<spanx style="verb">push</spanx><tt>push</tt> interaction finish method defined in Sections <xreftarget="request-interact-callback-redirect"/>target="request-interact-callback-redirect" format="counter"/> and <xreftarget="response-interact-finish"/>,target="response-interact-finish" format="counter"/>, the AS signals to the client instance that interaction is complete and the request can be continued by sending an HTTP POST request to the client instance's callback URI.</t> <t>The HTTP message content is a JSON object consisting of the following two fields:</t> <dl><dt><spanx style="verb">hash</spanx><dt><tt>hash</tt> (string):</dt> <dd> <t>The interaction hash value as described in <xref target="interaction-hash"/>. <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">interact_ref</spanx> (string)</dt><dt><tt>interact_ref</tt> (string):</dt> <dd> <t>The interaction reference generated for this interaction. <bcp14>REQUIRED</bcp14>.</t> </dd> </dl><figure><sourcecode<sourcecode type="json"><![CDATA[ POST /push/554321 HTTP/1.1 Host: client.example.net Content-Type: application/json { "hash": "pjdHcrti02HLCwGU3qhUZ3wZXt8IjrV_BtE3oUyOuKNk", "interact_ref": "4IFWWIKYBC2PQ6U56NL1" }]]></sourcecode></figure>]]></sourcecode> <t>Since the AS is making an outbound connection to a URI supplied by an outside party (the client instance), the AS <bcp14>MUST</bcp14> protect itself againstSSRFServer-Side Request Forgery (SSRF) attacks when making thiscallcall, as discussed in <xref target="security-ssrf"/>.</t> <t>When receiving the request, the client instance <bcp14>MUST</bcp14> parse the JSON object and validate the hash value as described in <xref target="interaction-hash"/>. If either fails, the client instance <bcp14>MUST</bcp14> return an<spanx style="verb">unknown_interaction</spanx><tt>unknown_interaction</tt> error (<xref target="response-error"/>). If the hash validates, the client instance sends a continuation request to the AS as described in <xreftarget="continue-after-interaction"/>target="continue-after-interaction"/>, using the interaction reference value received here.</t> </section> <sectionanchor="interaction-hash"><name>Calculatinganchor="interaction-hash"> <name>Calculating theinteraction hash</name>Interaction Hash</name> <!-- [rfced] Will readers know what the "related sections" are? Please clarify. Original: This security mechanism allows the client instance to protect itself against several kinds of session fixation and injection attacks as discussed in Section 13.25 and related sections. --> <t>The "hash" parameter in the request to the client instance's callback URI ties thefront channelfront-channel response to an ongoing request by using values known only to the parties involved. This security mechanism allows the client instance to protect itself against several kinds of session fixation and injection attacks as discussed in <xref target="security-interact-hash"/> and related sections. The AS <bcp14>MUST</bcp14> always provide this hash, and the client instance <bcp14>MUST</bcp14> validate the hash when received.</t> <t>To calculate the "hash" value, the party doing the calculation creates a hash base string by concatenating the following values in the following order using a single newline (0x0A) character to separate them:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>the "nonce" value sent by the client instance in the<xref target="request-interact-finish">interactioninteraction "finish" section of the initialrequest</xref></t>request (<xref target="request-interact-finish"> </xref>)</t> </li> <li> <t>the AS's nonce value from<xref target="response-interact-finish">thethe interaction finishresponse</xref></t>response (<xref target="response-interact-finish"> </xref>)</t> </li> <li> <t>the "interact_ref" returned from the AS as part of the<xref target="interaction-finish">interactioninteraction finishmethod</xref></t>method (<xref target="interaction-finish"> </xref>)</t> </li> <li> <t>the grant endpoint URI the client instance used to make its<xref target="request">initial request</xref></t> </list></t>initial request (<xref target="request"> </xref>)</t> </li> </ul> <t>There is no padding or whitespace before or after any of thelines,lines and no trailing newline character. The following non-normative example shows a constructed hash base string consisting of these four elements.</t><figure><artwork><![CDATA[<artwork><![CDATA[ VJLO6A4CATR0KRO MBDOFXG4Y5CVJCX821LH 4IFWWIKYB2PQ6U56NL1 https://server.example.com/tx]]></artwork></figure>]]></artwork> <t>The party then hashes the bytes of the ASCII encoding of this string with the appropriate algorithm based on the "hash_method" parameter under the "finish" key of the<xref target="request-interact-finish">interactioninteraction finishrequest</xref>.request (<xref target="request-interact-finish"> </xref>). The resulting byte array from the hash function is then encoded using URL-Safe Base64 with no padding <xref target="RFC4648"/>. The resulting string is the hash value.</t> <t>If provided, the "hash_method" value <bcp14>MUST</bcp14> be one of the hash name strings defined in the<xref target="HASH-ALG">IANA NamedIANA "Named Information Hash AlgorithmRegistry</xref>.Registry" <xref target="HASH-ALG"></xref>. If the "hash_method" value is not present in the client instance's request, the algorithm defaults to "sha-256".</t> <!-- [rfced] FYI - We updated "above example hash base string" as follows. Please review. Original: The following is the encoded "sha-256" hash of the above example hash base string. The following is the encoded "sha3-512" hash of the above example hash base string. Updated: The following is the encoded "sha-256" hash of the hash base string in the example above. The following is the encoded "sha3-512" hash of the hash base string in the example above. --> <t>For example, the "sha-256" hash method consists of hashing the input string with the 256-bit SHA2 algorithm. The following is the encoded "sha-256" hash of theabove examplehash basestring.</t> <figure><artwork><![CDATA[string in the example above. </t> <artwork><![CDATA[ x-gguKWTj8rQf7d7i3w3UhzvuJ5bpOlKyAlVpLxBffY]]></artwork></figure> <t>For]]></artwork> <t>As another example, the "sha3-512" hash method consists of hashing the input string with the 512-bit SHA3 algorithm. The following is the encoded "sha3-512" hash of theabove examplehash basestring.</t> <figure><artwork><![CDATA[string in the example above. </t> <artwork><![CDATA[ NOTE: '\' line wrapping per RFC 8792 pyUkVJSmpqSJMaDYsk5G8WCvgY91l-agUPe1wgn-cc5rUtN69gPI2-S_s-Eswed8iB4\ PJ_a5Hg6DNi7qGgKwSQ]]></artwork></figure>]]></artwork> </section> </section> </section> <sectionanchor="continue-request"><name>Continuinganchor="continue-request"> <name>Continuing a Grant Request</name> <t>While it is possible for the AS to return an approved<xref target="response">grant response</xref>grant response (<xref target="response"> </xref>) with all the client instance's requested information (including<xref target="response-token">access tokens</xref>access tokens (<xref target="response-token"> </xref>) and<xref target="response-subject">subject information</xref>)subject information (<xref target="response-subject"></xref>)) immediately, it's more common that the AS will place the grant request into the <em>pending</em> state and require communication with the client instance several times over the lifetime of a grant request. This is often part of facilitating<xref target="authorization">interaction</xref>,interaction (<xref target="authorization"> </xref>), but it could also be used to allow the AS and client instance to continue negotiating the parameters of the<xref target="request">originaloriginal grantrequest</xref>request (<xref target="request"> </xref>) through modification of the request.</t> <t>The ability to continue an already-started request allows the client instance to perform several important functions, including presenting additional information from interaction, modifying the initial request, and revoking a grant request in progress.</t> <t>To enable this ongoing negotiation, the AS provides a continuation API to the client software. The AS returns a<spanx style="verb">continue</spanx><tt>continue</tt> field<xref target="response-continue">inin theresponse</xref>response (<xref target="response-continue"> </xref>) that contains information the client instance needs to access this API, including a URI to access as well as a special access token to use during the requests, called the<em>continuation"continuation accesstoken</em>.</t>token".</t> <t>All requests to the continuation API are protected by a bound continuation access token. The continuation access token is bound to the same key and method the client instance used to make the initial request (or its most recent rotation). As a consequence, when the client instance makes any calls to the continuation URI, the client instance <bcp14>MUST</bcp14> present the continuation access token as described in <xref target="use-access-token"/> and present proof of the client instance's key (or its most recent rotation) by signing the request as described in <xref target="binding-keys"/>. The AS <bcp14>MUST</bcp14> validate the signature and ensure that it is bound to the appropriate key for the continuation access token.</t> <t>Access tokens other than the continuation access tokens <bcp14>MUST NOT</bcp14> be usable for continuation requests. Conversely, continuation access tokens <bcp14>MUST NOT</bcp14> be usable to make authorized requests toRS's,RSs, even if co-located within the AS.</t> <t>In the following non-normative example, the client instance makes a POST request to a unique URI and signs the request with HTTP Message Signatures:</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /continue/KSKUOMUKM HTTP/1.1 Authorization: GNAP 80UPRY5NM33OMUKMKSKU Host: server.example.com Content-Length: 0 Signature-Input: sig1=... Signature: sig1=...]]></sourcecode></figure>]]></sourcecode> <t>The AS <bcp14>MUST</bcp14> be able to tell from the client instance's request which specific ongoing request is being accessed, using a combination of the continuation URI and the continuation access token. If the AS cannot determine a single active grant request to map the continuation request to, the AS <bcp14>MUST</bcp14> return an<spanx style="verb">invalid_continuation</spanx><tt>invalid_continuation</tt> error (<xref target="response-error"/>).</t> <t>In the following non-normative example, the client instance makes a POST request to a stable continuation endpoint URI with the<xref target="continue-after-interaction">interaction reference</xref>,interaction reference (<xref target="continue-after-interaction"> </xref>), includes the access token, and signs with HTTP Message Signatures:</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /continue HTTP/1.1 Host: server.example.com Content-Type: application/json Authorization: GNAP 80UPRY5NM33OMUKMKSKU Signature-Input: sig1=... Signature: sig1=... Content-Digest: sha-256=... { "interact_ref": "4IFWWIKYBC2PQ6U56NL1" }]]></sourcecode></figure>]]></sourcecode> <t>In the following non-normative alternative example, the client instance had been provided a continuation URI unique to this ongoing grant request:</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /tx/rxgIIEVMBV-BQUO7kxbsp HTTP/1.1 Host: server.example.com Content-Type: application/json Authorization: GNAP eyJhbGciOiJub25lIiwidHlwIjoiYmFkIn0 Signature-Input: sig1=... Signature: sig1=... Content-Digest: sha-256=... { "interact_ref": "4IFWWIKYBC2PQ6U56NL1" }]]></sourcecode></figure>]]></sourcecode> <t>In both cases, the AS determines which grant is being asked for based on the URI and continuation access token provided.</t> <t>If a<spanx style="verb">wait</spanx><tt>wait</tt> parameter was included in the<xref target="response-continue">continuation response</xref>,continuation response (<xref target="response-continue"> </xref>), the client instance <bcp14>MUST NOT</bcp14> call the continuation URI prior to waiting the number of seconds indicated. If no<spanx style="verb">wait</spanx><tt>wait</tt> period is indicated, the client instance <bcp14>MUST NOT</bcp14> poll immediately and <bcp14>SHOULD</bcp14> wait at least 5 seconds. If the client instance does not respect the given wait period, the AS <bcp14>MUST</bcp14> return the<spanx style="verb">too_fast</spanx><tt>too_fast</tt> error (<xref target="response-error"/>).</t> <t>The response from the AS is a JSON object of a grant response and <bcp14>MAY</bcp14> contain any of the fields described in <xref target="response"/>, as described in more detail in thesectionssubsections below.</t> <t>If the AS determines that the client instance can make further requests to the continuation API, the AS <bcp14>MUST</bcp14> include a new<xref target="response-continue">"continue" response</xref>."continue" response (<xref target="response-continue"> </xref>). The new<spanx style="verb">continue</spanx><tt>continue</tt> response <bcp14>MUST</bcp14> include a continuation access token as well, and this token <bcp14>SHOULD</bcp14> be a new access token, invalidating the previous access token. If the AS does not return a new<spanx style="verb">continue</spanx><tt>continue</tt> response, the client instance <bcp14>MUST NOT</bcp14> make an additional continuation request. If a client instance does so, the AS <bcp14>MUST</bcp14> return an<spanx style="verb">invalid_continuation</spanx><tt>invalid_continuation</tt> error (<xref target="response-error"/>).</t> <t>For continuation functions that require the client instance to sendamessage content, the content <bcp14>MUST</bcp14> be a JSON object.</t> <t>For all requests to the grant continuation API, the AS <bcp14>MAY</bcp14> make use of long polling mechanisms such as those discussed in <xref target="RFC6202"/>. That is to say, instead of returning the current status immediately, the long polling technique allows the AS additional time to process and fulfill the request before returning the HTTP response to the client instance. For example, when the AS receives a continuation request but the grant request is in the <em>processing</em> state, the AS could wait until the grant request has moved to the <em>pending</em> or <em>approved</em> state before returning the response message.</t> <sectionanchor="continue-after-interaction"><name>Continuing Afteranchor="continue-after-interaction"> <name>Continuing after a Completed Interaction</name> <t>When the AS responds to the client instance's<spanx style="verb">finish</spanx><tt>finish</tt> method as in <xref target="interaction-callback"/>, this response includes an interaction reference. The client instance <bcp14>MUST</bcp14> include that value as the field<spanx style="verb">interact_ref</spanx><tt>interact_ref</tt> in a POST request to the continuation URI.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /continue HTTP/1.1 Host: server.example.com Content-Type: application/json Authorization: GNAP 80UPRY5NM33OMUKMKSKU Signature-Input: sig1=... Signature: sig1=... Content-Digest: sha-256=... { "interact_ref": "4IFWWIKYBC2PQ6U56NL1" }]]></sourcecode></figure>]]></sourcecode> <t>Since the interaction reference is a one-time-use value as described in <xref target="interaction-callback"/>, if the client instance needs to make additional continuation calls after this request, the client instance <bcp14>MUST NOT</bcp14> include the interaction reference in subsequent calls. If the AS detects a client instance submitting an interaction reference when the request is not in the <em>pending</em> state, the AS <bcp14>MUST</bcp14> return a<spanx style="verb">too_many_attempts</spanx><tt>too_many_attempts</tt> error (<xref target="response-error"/>) and <bcp14>SHOULD</bcp14> invalidate the ongoing request by moving it to the <em>finalized</em> state.</t> <t>If the grant request is in the <em>approved</em> state, the<xref target="response">grant response</xref>grant response (<xref target="response"> </xref>) <bcp14>MAY</bcp14> contain anynewly-created <xref target="response-token">access tokens</xref>newly created access tokens (<xref target="response-token"> </xref>) ornewly-released <xref target="response-subject">subject information</xref>.newly released subject information (<xref target="response-subject"> </xref>). The response <bcp14>MAY</bcp14> contain a new<xref target="response-continue">"continue" response</xref>"continue" response (<xref target="response-continue"> </xref>) as described above. The response <bcp14>SHOULD NOT</bcp14> contain any<xref target="response-interact">interaction responses</xref>.</t>interaction responses (<xref target="response-interact"> </xref>).</t> <!-- [rfced] How should "a new interaction responses" be updated? Should this be singular or plural? Note that this occurs in Sections 5.1 and 5.2. Original: If the grant request is in the _pending_ state, the grant response (Section 3) MUST NOT contain access tokens or subject information, and MAY contain a new interaction responses (Section 3.3) to any interaction methods that have not been exhausted at the AS. Perhaps (plural): If the grant request is in the _pending_ state, the grant response (Section 3) MUST NOT contain access tokens or subject information and MAY contain new interaction responses (Section 3.3) to any interaction methods that have not been exhausted at the AS. Or (singular): If the grant request is in the _pending_ state, the grant response (Section 3) MUST NOT contain access tokens or subject information and MAY contain a new interaction response (Section 3.3) to any interaction methods that have not been exhausted at the AS. --> <t>If the grant request is in the <em>pending</em> state, the<xref target="response">grant response</xref>grant response (<xref target="response"> </xref>) <bcp14>MUST NOT</bcp14> contain access tokens or subjectinformation,information and <bcp14>MAY</bcp14> contain a new<xref target="response-interact">interaction responses</xref>interaction responses (<xref target="response-interact"> </xref>) to any interaction methods that have not been exhausted at the AS.</t> <t>For example, if the request is successful in causing the AS to issue access tokens and release opaque subject claims, the response could look like this:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 { "access_token": { "value": "OS9M2PMHKUR64TB8N6BW7OZB8CDFONP219RP1LT0", "manage": { "uri": "https://server.example.com/token/PRY5NM33O", "access_token": { "value": "B8CDFONP21-4TB8N6.BW7ONM" } } }, "subject": { "sub_ids": [ { "format": "opaque", "id": "J2G8G8O4AZ" } ] } }]]></sourcecode></figure>]]></sourcecode> <t>With the above example, the client instancecan notcannot make an additional continuation request because a<spanx style="verb">continue</spanx><tt>continue</tt> field is not included.</t> <t>In the following non-normative example, the RO has denied the client instance'srequestrequest, and the AS responds with the following response:</t><figure><artwork><![CDATA[<artwork><![CDATA[ { "error": "user_denied", "continue": { "access_token": { "value": "33OMUKMKSKU80UPRY5NM" }, "uri": "https://server.example.com/continue", "wait": 30 } }]]></artwork></figure>]]></artwork> <t>In the preceding example, the AS includes the<spanx style="verb">continue</spanx><tt>continue</tt> field in the response. Therefore, the client instance can continue the grant negotiation process, perhaps modifying the request as discussed in <xref target="continue-modify"/>.</t> </section> <sectionanchor="continue-poll"><name>Continuing Duringanchor="continue-poll"> <name>Continuing during Pending Interaction (Polling)</name> <t>When the client instance does not include a<spanx style="verb">finish</spanx><tt>finish</tt> parameter, the client instance will often need to poll the AS until the RO has authorized the request. To do so, the client instance makes a POST request to the continuation URI as in <xreftarget="continue-after-interaction"/>,target="continue-after-interaction"/> but does not include message content.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /continue HTTP/1.1 Host: server.example.com Authorization: GNAP 80UPRY5NM33OMUKMKSKU Signature-Input: sig1=... Signature: sig1=...]]></sourcecode></figure>]]></sourcecode> <t>If the grant request is in the <em>approved</em> state, the<xref target="response">grant response</xref>grant response (<xref target="response"> </xref>) <bcp14>MAY</bcp14> contain anynewly-created <xref target="response-token">access tokens</xref>newly created access tokens (<xref target="response-token"> </xref>) ornewly-released <xref target="response-subject">subject claims</xref>.newly released subject claims (<xref target="response-subject"> </xref>). The response <bcp14>MAY</bcp14> contain a new<xref target="response-continue">"continue" response</xref>"continue" response (<xref target="response-continue"> </xref>) as described above. If a<spanx style="verb">continue</spanx><tt>continue</tt> field is included, it <bcp14>SHOULD</bcp14> include a<spanx style="verb">wait</spanx><tt>wait</tt> field to facilitate a reasonable polling rate by the client instance. The response <bcp14>SHOULD NOT</bcp14> contain<xref target="response-interact">interaction responses</xref>.</t>interaction responses (<xref target="response-interact"> </xref>).</t> <t>If the grant request is in the <em>pending</em> state, the<xref target="response">grant response</xref>grant response (<xref target="response"> </xref>) <bcp14>MUST NOT</bcp14> contain access tokens or subjectinformation,information and <bcp14>MAY</bcp14> contain a new<xref target="response-interact">interaction responses</xref>interaction responses (<xref target="response-interact"> </xref>) to any interaction methods that have not been exhausted at the AS.</t> <t>For example, if the request has not yet been authorized by the RO, the AS could respond by telling the client instance to make another continuation request in the future. In the following non-normative example, a new, unique access token has been issued for the call, which the client instance will use in its next continuation request.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "continue": { "access_token": { "value": "33OMUKMKSKU80UPRY5NM" }, "uri": "https://server.example.com/continue", "wait": 30 } }]]></sourcecode></figure>]]></sourcecode> <t>If the request is successful in causing the AS to issue access tokens and release subject information, the response could look like the following non-normative example:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 { "access_token": { "value": "OS9M2PMHKUR64TB8N6BW7OZB8CDFONP219RP1LT0", "manage": { "uri": "https://server.example.com/token/PRY5NM33O", "access_token": { "value": "B8CDFONP21-4TB8N6.BW7ONM" } } }, "subject": { "sub_ids": [ { "format": "opaque", "id": "J2G8G8O4AZ" } ] } }]]></sourcecode></figure>]]></sourcecode> <t>See <xref target="security-polling"/> for considerations on polling for continuation without an interaction<spanx style="verb">finish</spanx><tt>finish</tt> method.</t> <t>In error conditions, the AS responds to the client instance withthean error code as discussed in <xref target="response-error"/>. For example, if the client instance has polled too many times before the RO has approved the request, the AS would respond with a message like the following:</t><figure><artwork><![CDATA[<artwork><![CDATA[ { "error": "too_many_attempts" }]]></artwork></figure>]]></artwork> <t>Since this response does not include a<spanx style="verb">continue</spanx><tt>continue</tt> section, the client instance cannot continue to poll the AS for additional updates and the grant request is <em>finalized</em>. If the client instance still needs access to the resource, it will need to start with a new grant request.</t> </section> <sectionanchor="continue-modify"><name>Modifyinganchor="continue-modify"> <name>Modifying an Existing Request</name> <t>The client instance might need to modify an ongoing request, depending on whether or not tokens have already been issued or subject information has already been released. In such cases, the client instance makes an HTTP PATCH request to the continuation URI and includes any fields it needs to modify. Fields that aren't included in the request are considered unchanged from the original request.</t> <t>A grant request associated with a modification request <bcp14>MUST</bcp14> be in the <em>approved</em> or <em>pending</em> state. When the AS receives a valid modification request, the AS <bcp14>MUST</bcp14> place the grant request into the <em>processing</em> state and re-evaluate the authorization in the new context created by the update request, since the extent and context of the request could have changed.</t> <t>The client instance <bcp14>MAY</bcp14> include the<spanx style="verb">access_token</spanx><tt>access_token</tt> and<spanx style="verb">subject</spanx><tt>subject</tt> fields as described in Sections <xreftarget="request-token"/>target="request-token" format="counter"/> and <xreftarget="request-subject"/>.target="request-subject" format="counter"/>. Inclusion of these fields override any values in the initial request, which <bcp14>MAY</bcp14> trigger additional requirements and policies by the AS. For example, if the client instance is asking for more access, the AS could require additional interaction with the RO to gather additional consent. If the client instance is asking for more limited access, the AS could determine that sufficient authorization has been granted to the client instance and return the more limited access rights immediately. If the grant request was previously in the <em>approved</em> state, the AS could decide to remember the larger scale of access rights associated with the grant request, allowing the client instance to make subsequent requests of different subsets of granted access. The details of this processing are out of scope for this specification, but a one possible approach is as follows:</t><t><list style="numbers"><ol spacing="normal" type="1"><li> <t>A client instance requests access to<spanx style="verb">Foo</spanx>,<tt>Foo</tt>, and this is granted by the RO. This results in an accesstoken, <spanx style="verb">AT1</spanx>.</t>token: <tt>AT1</tt>.</t> </li> <li> <t>The client instance later modifies the grant request to include<spanx style="verb">Foo</spanx><tt>Foo</tt> and<spanx style="verb">Bar</spanx><tt>Bar</tt> together. Since the client instance was previously granted<spanx style="verb">Foo</spanx><tt>Foo</tt> under this grant request, the RO is prompted to allow the client instance access to<spanx style="verb">Foo</spanx><tt>Foo</tt> and<spanx style="verb">Bar</spanx><tt>Bar</tt> together. This results in a new accesstoken, <spanx style="verb">AT2</spanx>token: <tt>AT2</tt>. This access token has access to both<spanx style="verb">Foo</spanx><tt>Foo</tt> and<spanx style="verb">Bar</spanx>.<tt>Bar</tt>. The rights of the original access token<spanx style="verb">AT1</spanx><tt>AT1</tt> are not modified.</t> </li> <li> <t>The client instance makes another grant modification to ask only for<spanx style="verb">Bar</spanx>.<tt>Bar</tt>. Since the client instance was previously granted<spanx style="verb">Foo</spanx><tt>Foo</tt> and<spanx style="verb">Bar</spanx><tt>Bar</tt> together under this grant request, the RO is notpromptedprompted, and the access to<spanx style="verb">Bar</spanx><tt>Bar</tt> is granted in a new accesstoken, <spanx style="verb">AT3</spanx>.token: <tt>AT3</tt>. This new access token does not allow access to<spanx style="verb">Foo</spanx>.</t><tt>Foo</tt>.</t> </li> <li> <t>The original access token<spanx style="verb">AT1</spanx> expires<tt>AT1</tt> expires, and the client seeks a new access token to replace it. The client instance makes another grant modification to ask only for<spanx style="verb">Foo</spanx>.<tt>Foo</tt>. Since the client instance was previously granted<spanx style="verb">Foo</spanx><tt>Foo</tt> and<spanx style="verb">Bar</spanx><tt>Bar</tt> together under this grant request, the RO is notpromptedprompted, and the access to<spanx style="verb">Foo</spanx><tt>Foo</tt> is granted in a new accesstoken, <spanx style="verb">AT4</spanx>.token: <tt>AT4</tt>. This new access token does not allow access to<spanx style="verb">Bar</spanx>.</t> </list></t><tt>Bar</tt>.</t> </li> </ol> <t>All four access tokens are independent of each other and associated with the same underlying grant request. Each of these access tokens could possibly also be rotated using token management, if available. For example, instead of asking for a new token to replace<spanx style="verb">AT1</spanx>,<tt>AT1</tt>, the client instance could ask for a refresh of<spanx style="verb">AT1</spanx><tt>AT1</tt> using the rotation method of the token management API. This would result in a refreshed<spanx style="verb">AT1</spanx><tt>AT1</tt> with a different token value and expiration from the original<spanx style="verb">AT1</spanx><tt>AT1</tt> but with the same access rights of allowing only access to<spanx style="verb">Foo</spanx>.</t><tt>Foo</tt>.</t> <t>The client instance <bcp14>MAY</bcp14> include the<spanx style="verb">interact</spanx><tt>interact</tt> field as described in <xref target="request-interact"/>. Inclusion of this field indicates that the client instance is capable of driving interaction with the end user, and this field replaces any values from a previous request. The AS <bcp14>MAY</bcp14> respond to any of the interaction responses as described in <xref target="response-interact"/>, just like it would to a new request.</t> <t>The client instance <bcp14>MAY</bcp14> include the<spanx style="verb">user</spanx><tt>user</tt> field as described in <xref target="request-user"/> to present new assertions or information about the end user. The AS <bcp14>SHOULD</bcp14> check that this presented user information is consistent with any user information previously presented by the client instance or otherwise associated with this grant request.</t> <t>The client instance <bcp14>MUST NOT</bcp14> include the<spanx style="verb">client</spanx><tt>client</tt> section of the request, since the client instance is assumed not to have changed. Modification of client instance information, including rotation of keys associated with the client instance, is outside the scope of this specification.</t> <t>The client instance <bcp14>MUST NOT</bcp14> include post-interaction responses such as those described in <xref target="continue-after-interaction"/>.</t> <t>Modification requests <bcp14>MUST NOT</bcp14> alterpreviously-issuedpreviously issued access tokens. Instead, any access tokens issued from a continuation are considered new, separate access tokens. The AS <bcp14>MAY</bcp14> revokepreviously-issuedpreviously issued access tokens after a modification has occurred.</t> <t>If the modified request can be granted immediately by the AS (the grant request is in the <em>approved</em> state), the<xref target="response">grant response</xref>grant response (<xref target="response"> </xref>) <bcp14>MAY</bcp14> contain anynewly-created <xref target="response-token">access tokens</xref>newly created access tokens (<xref target="response-token"> </xref>) ornewly-released <xref target="response-subject">subject claims</xref>.newly released subject claims (<xref target="response-subject"> </xref>). The response <bcp14>MAY</bcp14> contain a new<xref target="response-continue">"continue" response</xref>"continue" response (<xref target="response-continue"> </xref>) as described above. If interaction can occur, the response <bcp14>SHOULD</bcp14> contain<xref target="response-interact">interaction responses</xref>interaction responses (<xref target="response-interact"> </xref>) as well.</t> <t>For example, a client instance initially requests a set of resources using references:</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /tx HTTP/1.1 Host: server.example.com Content-Type: application/json Signature-Input: sig1=... Signature: sig1=... Content-Digest: sha-256=... { "access_token": { "access": [ "read", "write" ] }, "interact": { "start": ["redirect"], "finish": { "method": "redirect", "uri": "https://client.example.net/return/123455", "nonce": "LKLTI25DK82FX4T4QFZC" } }, "client": "987YHGRT56789IOLK" }]]></sourcecode></figure>]]></sourcecode> <t>Access is granted by the RO, and a token is issued by the AS. In its final response, the AS includes a<spanx style="verb">continue</spanx><tt>continue</tt> field, which includes a separate access token for accessing the continuation API:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "continue": { "access_token": { "value": "80UPRY5NM33OMUKMKSKU" }, "uri": "https://server.example.com/continue", "wait": 30 }, "access_token": { "value": "RP1LT0-OS9M2P_R64TB", "access": [ "read", "write" ] } }]]></sourcecode></figure>]]></sourcecode> <t>This<spanx style="verb">continue</spanx><tt>continue</tt> field allows the client instance to make an eventual continuation call. Some time later, the client instance realizes that it no longer needs "write" access and therefore modifies its ongoing request, here asking for just "read" access instead of both "read" and "write" as before.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ PATCH /continue HTTP/1.1 Host: server.example.com Content-Type: application/json Authorization: GNAP 80UPRY5NM33OMUKMKSKU Signature-Input: sig1=... Signature: sig1=... Content-Digest: sha-256=... { "access_token": { "access": [ "read" ] } ... }]]></sourcecode></figure>]]></sourcecode> <t>The AS replaces the previous<spanx style="verb">access</spanx><tt>access</tt> from the first request, allowing the AS to determine if anypreviously-grantedpreviously granted consent already applies. In this case, the AS would determine that reducing the breadth of the requested access means that new access tokens can be issued to the client instance without additional interaction or consent. The AS would likely revokepreviously-issuedpreviously issued access tokens that had the greater access rights associated with them, unless they had been issued with the<spanx style="verb">durable</spanx><tt>durable</tt> flag.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "continue": { "access_token": { "value": "M33OMUK80UPRY5NMKSKU" }, "uri": "https://server.example.com/continue", "wait": 30 }, "access_token": { "value": "0EVKC7-2ZKwZM_6N760", "access": [ "read" ] } }]]></sourcecode></figure> <t>For]]></sourcecode> <t>As another example, the client instance initially requests read-only access but later needs to step up its access. The initial request could look like the following HTTPmessage.</t> <figure><sourcecodemessage:</t> <sourcecode type="http-message"><![CDATA[ POST /tx HTTP/1.1 Host: server.example.com Content-Type: application/json Signature-Input: sig1=... Signature: sig1=... Content-Digest: sha-256=... { "access_token": { "access": [ "read" ] }, "interact": { "start": ["redirect"], "finish": { "method": "redirect", "uri": "https://client.example.net/return/123455", "nonce": "LKLTI25DK82FX4T4QFZC" } }, "client": "987YHGRT56789IOLK" }]]></sourcecode></figure>]]></sourcecode> <t>Access is granted by the RO, and a token is issued by the AS. In its final response, the AS includes a<spanx style="verb">continue</spanx><tt>continue</tt> field:</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ { "continue": { "access_token": { "value": "80UPRY5NM33OMUKMKSKU" }, "uri": "https://server.example.com/continue", "wait": 30 }, "access_token": { "value": "RP1LT0-OS9M2P_R64TB", "access": [ "read" ] } }]]></sourcecode></figure>]]></sourcecode> <t>This allows the client instance to make an eventual continuation call. The client instance later realizes that it now needs "write" access in addition to the "read" access. Since this is an expansion of what it asked for previously, the client instance also includes a new interaction section in case the AS needs to interact with the RO again to gather additional authorization. Note that the client instance's nonce and callback are different from the initial request. Since the original callback was already used in the initialexchange,exchange and the callback is intended forone-time-use,one-time use, a new one needs to be included in order to use the callback again.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ PATCH /continue HTTP/1.1 Host: server.example.com Content-Type: application/json Authorization: GNAP 80UPRY5NM33OMUKMKSKU Signature-Input: sig1=... Signature: sig1=... Content-Digest: sha-256=... { "access_token": { "access": [ "read", "write" ] }, "interact": { "start": ["redirect"], "finish": { "method": "redirect", "uri": "https://client.example.net/return/654321", "nonce": "K82FX4T4LKLTI25DQFZC" } } }]]></sourcecode></figure>]]></sourcecode> <t>From here, the AS can determine that the client instance is asking for more than it was previously granted, but since the client instance has also provided a mechanism to interact with the RO, the AS can use that to gather the additional consent. The protocol continues as it would with a new request. Since the old access tokens are good for a subset of the rights requested here, the AS might decide to not revoke them. However, any access tokens granted after this update process are new access tokens and do not modify the rights of existing access tokens.</t> </section> <sectionanchor="continue-delete"><name>Revokinganchor="continue-delete"> <name>Revoking a Grant Request</name> <t>If the client instance wishes to cancel an ongoing grant request and place it into the <em>finalized</em> state, the client instance makes an HTTP DELETE request to the continuation URI.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ DELETE /continue HTTP/1.1 Host: server.example.com Content-Type: application/json Authorization: GNAP 80UPRY5NM33OMUKMKSKU Signature-Input: sig1=... Signature: sig1=...]]></sourcecode></figure>]]></sourcecode> <t>If the request is successfully revoked, the AS responds with HTTP status codeHTTP204 (No Content). The AS <bcp14>SHOULD</bcp14> revoke all associated access tokens, if possible. The AS <bcp14>SHOULD</bcp14> disable all token rotation and other token management functions on such access tokens, if possible. Once the grant request is in the <em>finalized</em> state, it <bcp14>MUST NOT</bcp14> be moved to any other state.</t> <t>If the request is not revoked, the AS responds with an<spanx style="verb">invalid_continuation</spanx><tt>invalid_continuation</tt> error (<xref target="response-error"/>).</t> </section> </section> <sectionanchor="token-management"><name>Tokenanchor="token-management"> <name>Token Management</name> <t>If an access token response includes the<spanx style="verb">manage</spanx><tt>manage</tt> field as described in <xref target="response-token-single"/>, the client instance <bcp14>MAY</bcp14> call this URI to manage the access token with the rotate and revoke actions defined in the followingsections.subsections. Other actions are undefined by this specification.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "access_token": { "value": "OS9M2PMHKUR64TB8N6BW7OZB8CDFONP219RP1LT0", "flags": ["bearer"], "manage": { "uri": "https://server.example.com/token/PRY5NM33O", "access_token": { "value": "B8CDFONP21-4TB8N6.BW7ONM" } } } }]]></sourcecode></figure>]]></sourcecode> <t>The token management access token issued under the<spanx style="verb">manage</spanx><tt>manage</tt> field is used to protect all calls to the token management API. The client instance <bcp14>MUST</bcp14> present proof of the key associated with the token along with the value of the token management accesstoken value.</t>token.</t> <t>The AS <bcp14>MUST</bcp14> validate the proof and ensure that it is associated with the token management access token.</t> <t>The AS <bcp14>MUST</bcp14> uniquely identify the token being managed from the token management URI, the token management access token, or a combination of both.</t> <sectionanchor="rotate-access-token"><name>Rotatinganchor="rotate-access-token"> <name>Rotating the Access Token Value</name> <t>If the client instance has an access token and that access token expires, the client instance might want to rotate the access token to a new value without expiration. Rotating an access token consists of issuing a new access token in place of an existing access token, with the same rights and properties as the original token, apart from an updated token value and expiration time.</t> <t>To rotate an access token, the client instance makes an HTTP POST to the token management URI with no message content, sending the access token in the authorization header as described in <xref target="use-access-token"/> and signing the request with the appropriate key.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /token/PRY5NM33O HTTP/1.1 Host: server.example.com Authorization: GNAP B8CDFONP21-4TB8N6.BW7ONM Signature-Input: sig1=... Signature: sig1=... Content-Digest: sha-256=...]]></sourcecode></figure>]]></sourcecode> <t>The client instancecan notcannot request to alter the access rights associated with the access token during a rotation request. To get an access token with different access rights for this grant request, the client instance has to call the<xref target="continue-modify">continuationcontinuation API'supdate</xref>update functionality (<xref target="continue-modify"> </xref>) to get a new access token. The client instance can also create a new grant request with the required access rights.</t> <t>The AS validates that the token management access token presented is associated with the management URI, that the AS issued the token to the given client instance, and that the presented key is the correct key for the token management access token. The AS determines which access token is being rotated from the token management URI, the token management access token, or both.</t> <t>If the token is validated and the key is appropriate for the request, the AS <bcp14>MUST</bcp14> invalidate the current access token value associated with this URI, if possible. Note that stateless access tokens can make proactive revocation difficult within asystem,system; see <xref target="security-stateless-tokens"/>.</t> <t>For successful rotations, the AS responds with an HTTP 200 withaJSON-formatted message content consisting of the rotated access token in the<spanx style="verb">access_token</spanx><tt>access_token</tt> field described in <xref target="response-token-single"/>. The value of the access token <bcp14>MUST NOT</bcp14> be the same as the current value of the access token used to access the management API. The response <bcp14>MUST</bcp14> include an access token management URI, and the value of this URI <bcp14>MAY</bcp14> be different from the URI used by the client instance to make the rotation call. The client instance <bcp14>MUST</bcp14> use this new URI to manage the rotated access token.</t> <t>The access rights in the<spanx style="verb">access</spanx><tt>access</tt> array for the rotated access token <bcp14>MUST</bcp14> be included in the response and <bcp14>MUST</bcp14> be the same as the token before rotation.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 { "access_token": { "value": "FP6A8H6HY37MH13CK76LBZ6Y1UADG6VEUPEER5H2", "manage": { "uri": "https://server.example.com/token/PRY5NM33O", "access_token": { "value": "B8CDFONP21-4TB8N6.BW7ONM" } }, "expires_in": 3600, "access": [ { "type": "photo-api", "actions": [ "read", "write", "dolphin" ], "locations": [ "https://server.example.net/", "https://resource.local/other" ], "datatypes": [ "metadata", "images" ] }, "read", "dolphin-metadata" ] } }]]></sourcecode></figure>]]></sourcecode> <t>If the AS is unable or unwilling to rotate the value of the access token, the AS responds with an<spanx style="verb">invalid_rotation</spanx><tt>invalid_rotation</tt> error (<xref target="response-error"/>). Upon receiving such an error, the client instance <bcp14>MUST</bcp14> consider the access token to not have changed its state.</t> <sectionanchor="rotate-access-token-key"><name>Bindinganchor="rotate-access-token-key"> <name>Binding a New Key to the Rotated Access Token</name> <t>If the client instance wishes to bind a new presentation key to an access token, the client instance <bcp14>MUST</bcp14> present both the new key and the proof of previous key material in the access token rotation request. The client instance makes an HTTP POST as a JSON object with the following field:</t> <dl><dt><spanx style="verb">key</spanx>:</dt><dt><tt>key</tt>:</dt> <dd> <t>The new key value or reference in the format described in <xref target="key-format"/>. Note that keys passed by value are always public keys. <bcp14>REQUIRED</bcp14> when doing key rotation.</t> </dd> </dl> <t>The<spanx style="verb">proof</spanx><tt>proof</tt> method and parameters for the new key <bcp14>MUST</bcp14> be the same as those established for the previous key.</t> <t>The client instance <bcp14>MUST</bcp14> prove possession of both thecurrently-boundcurrently bound key and thenewly-requestednewly requested key simultaneously in the rotation request. Specifically, the signature from the previous key <bcp14>MUST</bcp14> cover the value or reference of the new key, and the signature of the new key <bcp14>MUST</bcp14> cover the signature value of the old key. The means of doing sovariesvary depending on the proofing method in use. For example, the HTTP Message Signatures proofing method uses multiple signatures in the request as described in <xreftarget="httpsig-rotate"/>, astarget="httpsig-rotate"/>. This is shown inthisthe following example.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /token/PRY5NM33O HTTP/1.1 Host: server.example.com Authorization: GNAP B8CDFONP21-4TB8N6.BW7ONM Signature-Input: \ sig1=("@method" "@target-uri" "content-digest" \ "authorization"),\ sig2=("@method" "@target-uri" "content-digest" \ "authorization" "signature";key="sig1" \ "signature-input";key="sig1") Signature: sig1=..., sig2=... Content-Digest: sha-256=... { "key": { "proof": "httpsig", "jwk": { "kty": "RSA", "e": "AQAB", "kid": "xyz-2", "alg": "RS256", "n": "kOB5rR4Jv0GMeLaY6_It_r3ORwdf8ci_JtffXyaSx8xY..." } } }]]></sourcecode></figure>]]></sourcecode> <t>Failure to present the appropriate proof of either the new key or the previous key for the access token, as defined by the proof method, <bcp14>MUST</bcp14> result in an<spanx style="verb">invalid_rotation</spanx><tt>invalid_rotation</tt> error code from the AS (<xref target="response-error"/>).</t> <t>An attempt to change the<spanx style="verb">proof</spanx><tt>proof</tt> method or parameters, including an attempt to rotate the key of a bearer token (which has no key), <bcp14>MUST</bcp14> result in an<spanx style="verb">invalid_rotation</spanx><tt>invalid_rotation</tt> error code returned from the AS (<xref target="response-error"/>).</t> <t>If the AS does not allow rotation of the access token's key for any reason, including but not limited to lack of permission for this client instance or lack of capability by the AS, the AS <bcp14>MUST</bcp14> return a<spanx style="verb">key_rotation_not_supported</spanx><tt>key_rotation_not_supported</tt> error code (<xref target="response-error"/>).</t> </section> </section> <sectionanchor="revoke-access-token"><name>Revokinganchor="revoke-access-token"> <name>Revoking the Access Token</name> <t>If the client instance wishes to revoke the access token proactively, such as when a user indicates to the client instance that they no longer wish for it to have access or the client instance application detects that it is being uninstalled, the client instance can use the token management URI to indicate to the AS that the AS <bcp14>SHOULD</bcp14> invalidate the access token for all purposes.</t> <t>The client instance makes an HTTP DELETE request to the token management URI, presenting the access token and signing the request with the appropriate key.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ DELETE /token/PRY5NM33O HTTP/1.1 Host: server.example.com Authorization: GNAP B8CDFONP21-4TB8N6.BW7ONM Signature-Input: sig1=... Signature: sig1=...]]></sourcecode></figure>]]></sourcecode> <t>If the key presented is associated with the token (or the client instance, in the case of a bearer token), the AS <bcp14>MUST</bcp14> invalidate the access token, if possible, and return an HTTP204responsecode.</t> <figure><sourcecodecode 204.</t> <sourcecode type="http-message"><![CDATA[ 204 No Content]]></sourcecode></figure>]]></sourcecode> <t>Though the AS <bcp14>MAY</bcp14> revoke an access token at any time for any reason, the token management function is specifically for the client instance's use. If the access token has already expired or has been revoked through other means, the AS <bcp14>SHOULD</bcp14> honor the revocation request to the token management URI as valid, since the end result isstillthat the token is still notbeing usable.</t>usable. </t> </section> </section> <sectionanchor="secure-requests"><name>Securinganchor="secure-requests"> <name>Securing Requests from the Client Instance</name> <t>In GNAP, the client instance secures its requests to an AS and RS by presenting an access token,presentingproof of a key that it possesses (aka, a "key proof"), or both an access token and key proof together.</t><t><list style="symbols"><ul spacing="normal"> <li> <t>When an access token is used with a key proof, this is a bound token request. This type of request is used for calls to the RS as well as the AS during grant negotiation.</t> </li> <li> <t>When a key proof is used with no access token, this is a non-authorized signed request. This type of request is used for calls to the AS to initiate a grant negotiation.</t> </li> <li> <t>When an access token is used with no key proof, this is a bearer token request. This type of request is used only for calls to theRS,RS and only with access tokens that are not bound to any key as described in <xref target="response-token-single"/>.</t> </li> <li> <t>When neither an access token nor key proof are used, this is an unsecured request. This type of request is used optionally for calls to the RS as part of an RS-first discovery process as described in <xref target="rs-request-without-token"/>.</t></list></t></li> </ul> <sectionanchor="key-format"><name>Keyanchor="key-format"> <name>Key Formats</name> <t>Several different places in GNAP require the presentation of key material by value or by reference. Key material sent by value is sent using a JSON object with several fields described in this section.</t> <t>All keys are associated with a specific key proofing method. The proofing method associated with the key is indicated using the<spanx style="verb">proof</spanx><tt>proof</tt> field of the key object.</t> <dl><dt><spanx style="verb">proof</spanx><dt><tt>proof</tt> (string or object):</dt> <dd> <t>The form of proof that the client instance will use when presenting the key. The valid values of this field and the processing requirements for each are detailed in <xref target="binding-keys"/>. <bcp14>REQUIRED</bcp14>.</t> </dd> </dl> <t>A key presented by value <bcp14>MUST</bcp14> be a public key and <bcp14>MUST</bcp14> be presented inone andonly one supported format, as discussed in <xref target="security-multiple-key-formats"/>. Note that while most formats present the full value of the public key, some formats present a value cryptographically derived from the public key. See additional discussion of the presentation of public keys in <xref target="security-symmetric"/>.</t> <dl><dt><spanx style="verb">jwk</spanx><dt><tt>jwk</tt> (object):</dt> <dd> <t>The public key and its properties represented as a JSON Web Key (JWK) <xref target="RFC7517"/>. A JWK <bcp14>MUST</bcp14> contain the<spanx style="verb">alg</spanx><tt>alg</tt> (Algorithm) and<spanx style="verb">kid</spanx><tt>kid</tt> (Key ID) parameters. The<spanx style="verb">alg</spanx><tt>alg</tt> parameter <bcp14>MUST NOT</bcp14> be "none". The<spanx style="verb">x5c</spanx><tt>x5c</tt> (X.509 Certificate Chain) parameter <bcp14>MAY</bcp14> be used to provide the X.509 representation of the provided public key. <bcp14>OPTIONAL</bcp14>.</t> </dd><dt><spanx style="verb">cert</spanx><dt><tt>cert</tt> (string):</dt> <dd><t>PEM<t>The Privacy-Enhanced Mail (PEM) serialized value of the certificate used to sign the request, with optional internal whitespace per <xref target="RFC7468"/>. The PEM header and footer are optionally removed. <bcp14>OPTIONAL</bcp14>.</t> </dd><dt><spanx style="verb">cert#S256</spanx><dt><tt>cert#S256</tt> (string):</dt> <dd> <t>The certificate thumbprint calculated as per OAuth-MTLS <xreftarget="RFC8705">OAuth-MTLS</xref>target="RFC8705"> </xref> in base64 URL encoding. Note that this format does not include the full public key. <bcp14>OPTIONAL</bcp14>.</t> </dd> </dl> <t>Additional key formatsarecan be defined in the<xref target="IANA-key-formats">GNAP"GNAP KeyFormats Registry</xref>.</t>Formats" registry (<xref target="IANA-key-formats"> </xref>).</t> <t>The following non-normative example shows a single key presented in two different formats. The example key is intended to be used with the<xref target="httpsig-binding">HTTPHTTP MessageSignatures</xref>Signatures proofingmechanism,mechanism (<xref target="httpsig-binding"> </xref>), as indicated by the<spanx style="verb">httpsig</spanx><tt>httpsig</tt> value of the<spanx style="verb">proof</spanx><tt>proof</tt> field.</t> <t>As aJSON Web Key:</t> <figure><sourcecodeJWK:</t> <sourcecode type="json"><![CDATA[ "key": { "proof": "httpsig", "jwk": { "kty": "RSA", "e": "AQAB", "kid": "xyz-1", "alg": "RS256", "n": "kOB5rR4Jv0GMeLaY6_It_r3ORwdf8ci_JtffXyaSx8xY..." } }]]></sourcecode></figure>]]></sourcecode> <t>As a certificate in PEM format:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "key": { "proof": "httpsig", "cert": "MIIEHDCCAwSgAwIBAgIBATANBgkqhkiG9w0BAQsFA..." }]]></sourcecode></figure>]]></sourcecode> <t>When the key is presented in GNAP, proof of this key material <bcp14>MUST</bcp14> be used to bind the request, the nature of which varies with the location in the protocol where the key is used. For a key used as part of a client instance's initial request in <xref target="request-client"/>, the key value represents the client instance's public key, and proof of that key <bcp14>MUST</bcp14> be presented in that request. For a key used as part of an access token response in <xref target="response-token-single"/>, the proof of that key <bcp14>MUST</bcp14> be used when the client instance later presents the access token to the RS.</t> <sectionanchor="key-reference"><name>Keyanchor="key-reference"> <name>Key References</name> <t>Keys in GNAP can also be passed by reference such that the party receiving the reference will be able to determine the appropriate keying material for use in that part of the protocol.Key references areA key reference is a single opaque string.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "key": "S-P4XJQ_RYJCRTSU1.63N3E"]]></sourcecode></figure>]]></sourcecode> <t>Keys referenced in this manner <bcp14>MAY</bcp14> be shared symmetric keys. See the additional considerations for symmetric keys in <xref target="security-symmetric"/>. The key reference <bcp14>MUST NOT</bcp14> contain any unencrypted private or shared symmetric key information.</t> <t>Keys referenced in this manner <bcp14>MUST</bcp14> be bound to a single proofing mechanism.</t> <t>The means of dereferencing this reference to a key value and proofing mechanism are out of scope for this specification. Commonly, key references are created by the AS andaredo not necessarilyneededneed to be understood by the client. These types of key references are an internal reference to the AS, such as an identifier of a record in a database. In other applications, it can be useful to use key references that are resolvable by both clients and the AS, which could be accomplished by a client publishing a public key at a URI, for example. For interoperability, this method could later be described as an extension, but doing so is out of scope for this specification.</t> </section> <sectionanchor="key-protection"><name>Keyanchor="key-protection"> <name>Key Protection</name> <t>The security of GNAP relies on the cryptographic security of the keys themselves. When symmetric keys are used in GNAP, a key management system or secure key derivation mechanism <bcp14>MUST</bcp14> be used to supply the keys. Symmetric keys <bcp14>MUST NOT</bcp14> be ahuman memorablehuman-memorable password or a value derived from one. Symmetric keys <bcp14>MUST NOT</bcp14> be passed by value from the client instance to the AS.</t> <t>Additional security considerations apply when rotating keys (see <xreftarget="security-key-rotation">rotating keys</xref>.</t>target="security-key-rotation"> </xref>).</t> </section> </section> <sectionanchor="use-access-token"><name>Presentinganchor="use-access-token"> <name>Presenting Access Tokens</name> <t>Access tokens are issued to client instances in GNAP to allow the client instance to make an authorized call to an API. The method the client instance uses to send an access token depends on whether the token is bound to akey, andkey and, ifsoso, which proofing method is associated with the key. This information is conveyed by the<spanx style="verb">key</spanx><tt>key</tt> parameter and the<spanx style="verb">bearer</spanx><tt>bearer</tt> flag in<xref target="response-token-single">thethe access token responsestructure</xref>.</t>structure (<xref target="response-token-single"> </xref>).</t> <t>If the<spanx style="verb">flags</spanx><tt>flags</tt> field does not contain the<spanx style="verb">bearer</spanx><tt>bearer</tt> flag and the<spanx style="verb">key</spanx><tt>key</tt> is absent, the access token <bcp14>MUST</bcp14> be sent using the same key and proofing mechanism that the client instance used in its initial request (or its most recent rotation).</t> <t>If the<spanx style="verb">flags</spanx><tt>flags</tt> field does not contain the<spanx style="verb">bearer</spanx><tt>bearer</tt> flag and the<spanx style="verb">key</spanx><tt>key</tt> value is an object as described in <xref target="key-format"/>, the access token <bcp14>MUST</bcp14> be sent using the key and proofing mechanism defined by the value of the<spanx style="verb">proof</spanx><tt>proof</tt> field within the key object.</t> <t>The access token <bcp14>MUST</bcp14> be sent using the HTTP "Authorization" request header field and the "GNAP" authorization scheme along with a key proof as described in <xref target="binding-keys"/> for the key bound to the access token. For example, an access token bound using HTTP Message Signatures would be sent as follows:</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 GET /stuff HTTP/1.1 Host: resource.example.com Authorization: GNAP 80UPRY5NM33OMUKMKSKU Signature-Input: sig1=("@method" "@target-uri" "authorization")\ ;created=1618884473;keyid="gnap-rsa";nonce="NAOEJF12ER2";tag="gnap" Signature: sig1=:FQ+EjWqc38uLFByKa5y+c4WyYYwCTGUhidWKfr5L1Cha8FiPEw\ DxG7nWttpBLS/B6VLfkZJogPbclySs9MDIsAIJwHnzlcJjwXWR2lfvm2z3X7EkJHm\ Zp4SmyKOS34luAiKR1xwf32NYFolHmZf/SbHZJuWvQuS4U33C+BbsXz8MflFH1Dht\ H/C1E5i244gSbdLCPxzABc/Q0NHVSLo1qaouYIvnxXB8OT3K7mwWjsLh1GC5vFThb\ 3XQ363r6f0OPRa4qWHhubR/d/J/lNOjbBdjq9AJ69oqNJ+A2XT+ZCrVasEJE0OBvD\ auQoiywhb8BMB7+PEINsPk5/8UvaNxbw==:]]></sourcecode></figure>]]></sourcecode> <t>If the<spanx style="verb">flags</spanx><tt>flags</tt> field contains the<spanx style="verb">bearer</spanx><tt>bearer</tt> flag, the access token is a bearer token that <bcp14>MUST</bcp14> be sent using the<spanx style="verb">Authorization Request Header Field</spanx><tt>Authorization request header field</tt> method defined in <xref target="RFC6750"/>.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ Authorization: Bearer OS9M2PMHKUR64TB8N6BW7OZB8CDFONP219RP1LT0]]></sourcecode></figure>]]></sourcecode> <t>The<spanx style="verb">Form-Encoded<tt>Form-Encoded BodyParameter</spanx>Parameter</tt> and<spanx style="verb">URI<tt>URI QueryParameter</spanx>Parameter</tt> methods of <xref target="RFC6750"/> <bcp14>MUST NOT</bcp14> be used for GNAP access tokens.</t> </section> <sectionanchor="binding-keys"><name>Provinganchor="binding-keys"> <name>Proving Possession of a Key with a Request</name> <t>Any keys presented by the client instance to the AS or RS <bcp14>MUST</bcp14> be validated as part of the request in which they are presented. The type of binding used is indicated by the<spanx style="verb">proof</spanx><tt>proof</tt> parameter of the key object in <xref target="key-format"/>. Key proof methods are specified either by a string, which consists of the key proof method name on its own, or by a JSON object with the required field<spanx style="verb">method</spanx>:</t><tt>method</tt>:</t> <dl><dt><spanx style="verb">method</spanx>:</dt><dt><tt>method</tt>:</dt> <dd> <t>The name of the key proofing method to be used. <bcp14>REQUIRED</bcp14>.</t> </dd> </dl> <t>Individual methods defined as objects <bcp14>MAY</bcp14> define additional parameters as members in this object.</t> <t>Values for the<spanx style="verb">method</spanx><tt>method</tt> defined by this specification are as follows:</t> <dl><dt><spanx style="verb">"httpsig"</spanx><dt><tt>"httpsig"</tt> (string or object):</dt> <dd> <t>HTTPSigningsigning signature headers. See <xref target="httpsig-binding"/>.</t> </dd><dt><spanx style="verb">"mtls"</spanx><dt><tt>"mtls"</tt> (string):</dt> <dd> <t>Mutual TLS certificate verification. See <xref target="mtls"/>.</t> </dd><dt><spanx style="verb">"jwsd"</spanx><dt><tt>"jwsd"</tt> (string):</dt> <dd> <t>A detached JWS signature header. See <xref target="detached-jws"/>.</t> </dd><dt><spanx style="verb">"jws"</spanx><dt><tt>"jws"</tt> (string):</dt> <dd> <t>Attached JWSpayload.Payload. See <xref target="attached-jws"/>.</t> </dd> </dl> <t>Additional proofing methodsarecan be definedbyin the<xref target="IANA-key-proof-methods">GNAP"GNAP Key ProofingMethods Registry</xref>.</t>Methods" registry (<xref target="IANA-key-proof-methods"> </xref>).</t> <t>Proof methods <bcp14>MAY</bcp14> be defined as both an object and a string. For example, the<spanx style="verb">httpsig</spanx><tt>httpsig</tt> method can be specified as an object with its parameters explicitly declared, such as:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "proof": { "method": "httpsig", "alg": "ecdsa-p384-sha384", "content-digest-alg": "sha-256" } }]]></sourcecode></figure>]]></sourcecode> <t>The<spanx style="verb">httpsig</spanx><tt>httpsig</tt> method also defines default behavior when it is passed as a string form, using the signature algorithm specified by the associated key material and the content digest is calculated using sha-256. This configuration can be selected using the following shortened form:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "proof": "httpsig" }]]></sourcecode></figure>]]></sourcecode> <t>All key binding methods used by this specification <bcp14>MUST</bcp14> cover all relevant portions of the request, including anything that would change the nature of the request, to allow for secure validation of the request. Relevant aspects include the URI being called, the HTTP method being used, any relevant HTTP headers and values, and the HTTP message content itself. The verifier of the signed message <bcp14>MUST</bcp14> validate all components of the signed message to ensure that nothing has been tampered with or substituted in a way that would change the nature of the request.KeyDefinitions of key bindingmethod definitionsmethods <bcp14>MUST</bcp14> enumerate how these requirements are fulfilled.</t> <t>When a key proofing mechanism is bound to an access token, the key being presented <bcp14>MUST</bcp14> be the key associated with the accesstokentoken, and the access token <bcp14>MUST</bcp14> be covered by the signature method of the proofing mechanism.</t><t>The key binding methods in this section <bcp14>MAY</bcp14> be used by other components making calls as part of GNAP, such as the extensions allowing the RS to make calls to<!-- [rfced] Please clarify theAStext starting with "the sections below are definedin <xref target="I-D.ietf-gnap-resource-servers"/>.in...". Original: To facilitate this extended use, the sections below are defined in generic terms of the "signer" and "verifier" of the HTTP message.In the core functions of GNAP specified inPerhaps: To facilitate thisdocument,extended use, the"signer" issubsections below use theclient instancegeneric terms "signer" andthe"verifier" for the HTTP message. Or: To facilitate this extended use, "signer" and "verifier" are used as generic terms in the subsections below. --> <t>The key binding methods in this section <bcp14>MAY</bcp14> be used by other components making calls as part of GNAP, such as the extensions allowing the RS to make calls to the AS defined in <xref target="I-D.ietf-gnap-resource-servers"/>. To facilitate this extended use, the sections below are defined in generic terms of the "signer" and "verifier" of the HTTP message. In the core functions of GNAP specified in this document, the "signer" is the client instance, and the "verifier" is the AS (for grant requests) or RS (for resource requests), as appropriate.</t> <t>When used for delegation in GNAP, these key binding mechanisms allow the AS to ensure that the keys presented by the client instance in the initial request are in control of the party calling any follow-up or continuation requests. To facilitate this requirement, the<xref target="response-continue">continuation response</xref>continuation response (<xref target="response-continue"> </xref>) includes an access token bound to the<xref target="request-client">clientclient instance'skey</xref>,key (<xref target="request-client"> </xref>), and that key (or its most recent rotation) <bcp14>MUST</bcp14> be proved in all continuation requests (<xref target="continue-request"/>). Token management requests (<xref target="token-management"/>) are similarly bound to either the access token's own key or, in the case of bearer tokens, the client instance's key.</t> <t>In the followingsections,subsections, unless otherwise noted, the<spanx style="verb">RS256</spanx> JOSE Signature Algorithm<tt>RS256</tt> JSON Object Signing and Encryption (JOSE) signature algorithm (defined in <xref section="3.3" sectionFormat="of" target="RFC7518"/>) is applied using the following RSA key (presented here in JWK format):</t><figure><sourcecode<sourcecode type="json"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 { "kid": "gnap-rsa", "p": "xS4-YbQ0SgrsmcA7xDzZKuVNxJe3pCYwdAe6efSy4hdDgF9-vhC5gjaRk\ i1wWuERSMW4Tv44l5HNrL-Bbj_nCJxr_HAOaesDiPn2PnywwEfg3Nv95Nn-\ eilhqXRaW-tJKEMjDHu_fmJBeemHNZI412gBnXdGzDVo22dvYoxd6GM", "kty": "RSA", "q": "rVdcT_uy-CD0GKVLGpEGRR7k4JO6Tktc8MEHkC6NIFXihk_6vAIOCzCD6\ LMovMinOYttpRndKoGTNdJfWlDFDScAs8C5n2y1STCQPRximBY-bw39-aZq\ JXMxOLyPjzuVgiTOCBIvLD6-8-mvFjXZk_eefD0at6mQ5qV3U1jZt88", "d": "FHlhdTF0ozTliDxMBffT6aJVKZKmbbFJOVNten9c3lXKB3ux3NAb_D2dB\ 7inp9EV23oWrDspFtvCvD9dZrXgRKMHofkEpo_SSvBZfgtH-OTkbY_TqtPF\ FLPKAw0JX5cFPnn4Q2xE4n-dQ7tpRCKl59vZLHBrHShr90zqzFp0AKXU5fj\ b1gC9LPwsFA2Fd7KXmI1drQQEVq9R-o18Pnn4BGQNQNjO_VkcJTiBmEIVT_\ KJRPdpVJAmbgnYWafL_hAfeb_dK8p85yurEVF8nCK5oO3EPrqB7IL4UqaEn\ 5Sl3u0j8x5or-xrrAoNz-gdOv7ONfZY6NFoa-3f8q9wBAHUuQ", "e": "AQAB", "qi": "ogpNEkDKg22Rj9cDV_-PJBZaXMk66Fp557RT1tafIuqJRHEufSOYnsto\ bWPJ0gHxv1gVJw3gm-zYvV-wTMNgr2wVsBSezSJjPSjxWZtmT2z68W1DuvK\ kZy15vz7Jd85hmDlriGcXNCoFEUsGLWkpHH9RwPIzguUHWmTt8y0oXyI", "dp": "dvCKGI2G7RLh3WyjoJ_Dr6hZ3LhXweB3YcY3qdD9BnxZ71mrLiMQg4c_\ EBnwqCETN_5sStn2cRc2JXnvLP3G8t7IFKHTT_i_TSTacJ7uT04MSa053Y3\ RfwbvLjRNPR0UKAE3ZxROUoIaVNuU_6-QMf8-2ilUv2GIOrCN87gP_Vk", "alg": "RS256", "dq": "iMZmELaKgT9_W_MRT-UfDWtTLeFjIGRW8aFeVmZk9R7Pnyt8rNzyN-IQ\ M40ql8u8J6vc2GmQGfokLlPQ6XLSCY68_xkTXrhoU1f-eDntkhP7L6XawSK\ Onv5F2H7wyBQ75HUmHTg8AK2B_vRlMyFKjXbVlzKf4kvqChSGEz4IjQ", "n": "hYOJ-XOKISdMMShn_G4W9m20mT0VWtQBsmBBkI2cmRt4Ai8BfYdHsFzAt\ YKOjpBR1RpKpJmVKxIGNy0g6Z3ad2XYsh8KowlyVy8IkZ8NMwSrcUIBZGYX\ jHpwjzvfGvXH_5KJlnR3_uRUp4Z4Ujk2bCaKegDn11V2vxE41hqaPUnhRZx\ e0jRETddzsE3mu1SK8dTCROjwUl14mUNo8iTrTm4n0qDadz8BkPo-uv4BC0\ bunS0K3bA_3UgVp7zBlQFoFnLTO2uWp_muLEWGl67gBq9MO3brKXfGhi3kO\ zywzwPTuq-cVQDyEN7aL0SxCb3Hc4IdqDaMg8qHUyObpPitDQ" }]]></sourcecode></figure>]]></sourcecode> <t>Key proofing methods <bcp14>SHOULD</bcp14> define a mechanism to allow the rotation of keys discussed in <xref target="rotate-access-token-key"/>. Key rotation mechanisms <bcp14>MUST</bcp14> define a way for presenting proof of two keys simultaneously with the following attributes:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>The value of or reference to the new key material <bcp14>MUST</bcp14> be signed by the existing key. Generally speaking, this amounts to using the existing key to sign the content of the messagewhichthat contains the new key.</t> </li> <li> <t>The signature of the old key <bcp14>MUST</bcp14> be signed by the new key. Generally speaking, this means including the signature value of the old key under the coverage of the new key.</t></list></t></li> </ul> <sectionanchor="httpsig-binding"><name>HTTPanchor="httpsig-binding"> <name>HTTP Message Signatures</name> <t>This method is indicated by the method value<spanx style="verb">httpsig</spanx><tt>httpsig</tt> and can be declared in either object form or string form.</t> <t>When the proof method is specified in object form, the following parameters are defined:</t> <dl><dt><spanx style="verb">alg</spanx>:</dt><dt><tt>alg</tt>:</dt> <dd> <t>The HTTP signature algorithm, from theHTTP"HTTP SignatureAlgorithmAlgorithms" registry. <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">content-digest-alg</spanx>:</dt><dt><tt>content-digest-alg</tt>:</dt> <dd> <t>The algorithm used for the Content-Digest field, used to protect the content when present in the message. <bcp14>REQUIRED</bcp14>.</t> </dd> </dl> <t>This example uses theECDSAElliptic Curve Digital Signature Algorithm (ECDSA) signing algorithm over the P384 curve and the SHA-512 hashing algorithm for the content digest.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "proof": { "method": "httpsig", "alg": "ecdsa-p384-sha384", "content-digest-alg": "sha-512" } }]]></sourcecode></figure>]]></sourcecode> <t>When the proof method is specified in string form, the signing algorithm <bcp14>MUST</bcp14> be derived from the key material (such as using the JWS algorithm in a JWK formatted key), and the content digest algorithm <bcp14>MUST</bcp14> be<spanx style="verb">sha-256</spanx>.</t> <figure><sourcecode<tt>sha-256</tt>.</t> <sourcecode type="json"><![CDATA[ { "proof": "httpsig" }]]></sourcecode></figure>]]></sourcecode> <t>When using this method, the signer creates an HTTP Message Signature as described in <xref target="RFC9421"/>. The covered components of the signature <bcp14>MUST</bcp14> include the following:</t> <dl><dt><spanx style="verb">"@method"</spanx>:</dt><dt><tt>"@method"</tt>:</dt> <dd> <t>The method used in the HTTP request.</t> </dd><dt><spanx style="verb">"@target-uri"</spanx>:</dt><dt><tt>"@target-uri"</tt>:</dt> <dd> <t>The full request URI of the HTTP request.</t> </dd> </dl> <t>When the message contains request content, the covered components <bcp14>MUST</bcp14> also include the following:</t> <dl><dt><spanx style="verb">"content-digest"</spanx>:</dt><dt><tt>"content-digest"</tt>:</dt> <dd> <t>The Content-Digest header as defined in <xref target="RFC9530"/>. When the request message has content, the signer <bcp14>MUST</bcp14> calculate this field value and include the field in the request. The verifier <bcp14>MUST</bcp14> validate this field value. <bcp14>REQUIRED</bcp14> when the message request contains message content.</t> </dd> </dl> <t>When the request is bound to an access token, the covered components <bcp14>MUST</bcp14> also include the following:</t> <dl><dt><spanx style="verb">"authorization"</spanx>:</dt><dt><tt>"authorization"</tt>:</dt> <dd> <t>The Authorization header used to present the access token as discussed in <xref target="use-access-token"/>.</t> </dd> </dl> <t>Other message components <bcp14>MAY</bcp14> also be included.</t> <t>The signer <bcp14>MUST</bcp14> include the<spanx style="verb">tag</spanx><tt>tag</tt> signature parameter with the value<spanx style="verb">gnap</spanx>,<tt>gnap</tt>, and the verifier <bcp14>MUST</bcp14> verify that the parameter exists with this value. The signer <bcp14>MUST</bcp14> include the<spanx style="verb">created</spanx><tt>created</tt> signature parameter with a timestamp of when the signature was created, and the verifier <bcp14>MUST</bcp14> ensure that the creation timestamp is sufficiently close to the current time given expected network delay and clock skew. The signer <bcp14>SHOULD</bcp14> include the<spanx style="verb">nonce</spanx><tt>nonce</tt> parameter with a unique and unguessable value. When included, the verifier <bcp14>MUST</bcp14> determine that the nonce value is unique within a reasonably short time period such as several minutes.</t> <t>If the signer's key presented is a JWK, the<spanx style="verb">keyid</spanx><tt>keyid</tt> parameter of the signature <bcp14>MUST</bcp14> be set to the<spanx style="verb">kid</spanx><tt>kid</tt> value of the JWK, and the signing algorithm used <bcp14>MUST</bcp14> be the JWS algorithm denoted by the key's<spanx style="verb">alg</spanx><tt>alg</tt> field of the JWK.</t> <t>The explicit<spanx style="verb">alg</spanx><tt>alg</tt> signature parameter <bcp14>MUST NOT</bcp14> be included in the signature, since the algorithm will be derivedeitherfrom either the key material orfromthe<spanx style="verb">proof</spanx><tt>proof</tt> value.</t> <t>In the following non-normative example, the message content isthe followinga JSON object:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 { "access_token": { "access": [ "dolphin-metadata" ] }, "interact": { "start": ["redirect"], "finish": { "method": "redirect", "uri": "https://client.foo/callback", "nonce": "VJLO6A4CAYLBXHTR0KRO" } }, "client": { "key": { "proof": "httpsig", "jwk": { "kid": "gnap-rsa", "kty": "RSA", "e": "AQAB", "alg": "PS512", "n": "hYOJ-XOKISdMMShn_G4W9m20mT0VWtQBsmBBkI2cmRt4Ai8Bf\ YdHsFzAtYKOjpBR1RpKpJmVKxIGNy0g6Z3ad2XYsh8KowlyVy8IkZ8NMwSrcUIBZG\ YXjHpwjzvfGvXH_5KJlnR3_uRUp4Z4Ujk2bCaKegDn11V2vxE41hqaPUnhRZxe0jR\ ETddzsE3mu1SK8dTCROjwUl14mUNo8iTrTm4n0qDadz8BkPo-uv4BC0bunS0K3bA_\ 3UgVp7zBlQFoFnLTO2uWp_muLEWGl67gBq9MO3brKXfGhi3kOzywzwPTuq-cVQDyE\ N7aL0SxCb3Hc4IdqDaMg8qHUyObpPitDQ" } } "display": { "name": "My Client Display Name", "uri": "https://client.foo/" }, } }]]></sourcecode></figure>]]></sourcecode> <t>This content is hashed for the Content-Digest header using<spanx style="verb">sha-256</spanx><tt>sha-256</tt> into the following encoded value:</t><figure><artwork><![CDATA[<artwork><![CDATA[ sha-256=:q2XBmzRDCREcS2nWo/6LYwYyjrlN1bRfv+HKLbeGAGg=:]]></artwork></figure>]]></artwork> <t>The HTTP message signature input string is calculated to be the following:</t><figure><artwork><![CDATA[<artwork><![CDATA[ NOTE: '\' line wrapping per RFC 8792 "@method": POST "@target-uri": https://server.example.com/gnap "content-digest": \ sha-256=:q2XBmzRDCREcS2nWo/6LYwYyjrlN1bRfv+HKLbeGAGg=: "content-length": 988 "content-type": application/json "@signature-params": ("@method" "@target-uri" "content-digest" \ "content-length" "content-type");created=1618884473\ ;keyid="gnap-rsa";nonce="NAOEJF12ER2";tag="gnap"]]></artwork></figure>]]></artwork> <t>This leads to the following full HTTP message request:</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 POST /gnap HTTP/1.1 Host: server.example.com Content-Type: application/json Content-Length: 988 Content-Digest: sha-256=:q2XBmzRDCREcS2nWo/6LYwYyjrlN1bRfv+HKLbeGAG\ g=: Signature-Input: sig1=("@method" "@target-uri" "content-digest" \ "content-length" "content-type");created=1618884473\ ;keyid="gnap-rsa";nonce="NAOEJF12ER2";tag="gnap" Signature: sig1=:c2uwTa6ok3iHZsaRKl1ediKlgd5cCAYztbym68XgX8gSOgK0Bt\ +zLJ19oGjSAHDjJxX2gXP2iR6lh9bLMTfPzbFVn4Eh+5UlceP+0Z5mES7v0R1+eHe\ OqBl0YlYKaSQ11YT7n+cwPnCSdv/6+62m5zwXEEftnBeA1ECorfTuPtau/yrTYEvD\ 9A/JqR2h9VzAE17kSlSSsDHYA6ohsFqcRJavX29duPZDfYgkZa76u7hJ23yVxoUpu\ 2J+7VUdedN/72N3u3/z2dC8vQXbzCPTOiLru12lb6vnBZoDbUGsRR/zHPauxhj9T+\ 218o5+tgwYXw17othJSxIIOZ9PkIgz4g==: { "access_token": { "access": [ "dolphin-metadata" ] }, "interact": { "start": ["redirect"], "finish": { "method": "redirect", "uri": "https://client.foo/callback", "nonce": "VJLO6A4CAYLBXHTR0KRO" } }, "client": { "key": { "proof": "httpsig", "jwk": { "kid": "gnap-rsa", "kty": "RSA", "e": "AQAB", "alg": "PS512", "n": "hYOJ-XOKISdMMShn_G4W9m20mT0VWtQBsmBBkI2cmRt4Ai8Bf\ YdHsFzAtYKOjpBR1RpKpJmVKxIGNy0g6Z3ad2XYsh8KowlyVy8IkZ8NMwSrcUIBZG\ YXjHpwjzvfGvXH_5KJlnR3_uRUp4Z4Ujk2bCaKegDn11V2vxE41hqaPUnhRZxe0jR\ ETddzsE3mu1SK8dTCROjwUl14mUNo8iTrTm4n0qDadz8BkPo-uv4BC0bunS0K3bA_\ 3UgVp7zBlQFoFnLTO2uWp_muLEWGl67gBq9MO3brKXfGhi3kOzywzwPTuq-cVQDyE\ N7aL0SxCb3Hc4IdqDaMg8qHUyObpPitDQ" } } "display": { "name": "My Client Display Name", "uri": "https://client.foo/" }, } }]]></sourcecode></figure>]]></sourcecode> <!-- [rfced] Should "HTTP Message" here read "HTTP message" (lowercase "message") or "HTTP Message Signature"? Original: If the HTTP Message includes content, the verifier MUST calculate and verify the value of the Content-Digest header. --> <t>The verifier <bcp14>MUST</bcp14> ensure that the signature covers all required message components. If the HTTP Message includes content, the verifier <bcp14>MUST</bcp14> calculate and verify the value of the<spanx style="verb">Content-Digest</spanx><tt>Content-Digest</tt> header. The verifier <bcp14>MUST</bcp14> validate the signature against the expected key of the signer.</t> <t>A received message <bcp14>MAY</bcp14> include multiple signatures, each with its own label. The verifier <bcp14>MUST</bcp14> examine all included signatures until it finds (at least) onethat'sthat is acceptable according to its policy and meets the requirements in this section.</t> <sectionanchor="httpsig-rotate"><name>Keyanchor="httpsig-rotate"> <name>Key RotationusingUsing HTTP Message Signatures</name> <t>When rotating a key using HTTP Message Signatures, the message, which includes the new public key value or reference, is first signed with the old key following all of the requirements in <xref target="httpsig-binding"/>. The message is then signed again with the new key by following all of the requirements in <xref target="httpsig-binding"/>againagain, with the following additional requirements:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>The covered components <bcp14>MUST</bcp14> include the Signature and Signature-Input values from the signature generated with the oldkey</t>key.</t> </li> <li> <t>The tag value <bcp14>MUST</bcp14> be<spanx style="verb">gnap-rotate</spanx></t> </list></t><tt>gnap-rotate</tt>.</t> </li> </ul> <t>For example, the following request to the token management endpoint for rotating a token value contains the new key in the request. The message is first signed using the oldkeykey, and the resulting signature is placed in "old-key":</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 POST /token/PRY5NM33 HTTP/1.1 Host: server.example.com Authorization: GNAP 4398.34-12-asvDa.a Content-Digest: sha-512=:Fb/A5vnawhuuJ5xk2RjGrbbxr6cvinZqd4+JPY85u/\ JNyTlmRmCOtyVhZ1Oz/cSS4tsYen6fzpCwizy6UQxNBQ==: Signature-Input: old-key=("@method" "@target-uri" "content-digest" \ "authorization");created=1618884475;keyid="test-key-ecc-p256"\ ;tag="gnap" Signature: old-key=:vN4IKYsJl2RLFe+tYEm4dHM4R4BToqx5D2FfH4ge5WOkgxo\ dI2QRrjB8rysvoSEGvAfiVJOWsGcPD1lU639Amw==: { "key": { "proof": "httpsig", "jwk": { "kty": "RSA", "e": "AQAB", "kid": "xyz-2", "alg": "RS256", "n": "kOB5rR4Jv0GMeLaY6_It_r3ORwdf8ci_JtffXyaSx8xY..." } } }]]></sourcecode></figure>]]></sourcecode> <t>The signer then creates a new signature using the new key, adding the signature input and value to the signature base.</t><figure><artwork><![CDATA[<artwork><![CDATA[ NOTE: '\' line wrapping per RFC 8792 "@method": POST "@target-uri": https://server.example.com/token/PRY5NM33 "content-digest": sha-512=:Fb/A5vnawhuuJ5xk2RjGrbbxr6cvinZqd4+JPY85\ u/JNyTlmRmCOtyVhZ1Oz/cSS4tsYen6fzpCwizy6UQxNBQ==: "authorization": GNAP 4398.34-12-asvDa.a "signature";key="old-key": :YdDJjDn2Sq8FR82e5IcOLWmmf6wILoswlnRcz+n\ M+e8xjFDpWS2YmiMYDqUdri2UiJsZx63T1z7As9Kl6HTGkQ==: "signature-input";key="old-key": ("@method" "@target-uri" \ "content-digest" "authorization");created=1618884475\ ;keyid="test-key-ecc-p256";tag="gnap" "@signature-params": ("@method" "@target-uri" "content-digest" \ "authorization" "signature";key="old-key" "signature-input"\ ;key="old-key");created=1618884480;keyid="xyz-2" ;tag="gnap-rotate"]]></artwork></figure>]]></artwork> <t>This signature is then added to the message:</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 POST /token/PRY5NM33 HTTP/1.1 Host: server.example.com Authorization: GNAP 4398.34-12-asvDa.a Content-Digest: sha-512=:Fb/A5vnawhuuJ5xk2RjGrbbxr6cvinZqd4+JPY85u/\ JNyTlmRmCOtyVhZ1Oz/cSS4tsYen6fzpCwizy6UQxNBQ==: Signature-Input: old-key=("@method" "@target-uri" "content-digest" \ "authorization");created=1618884475;keyid="test-key-ecc-p256"\ ;tag="gnap", \ new-key=("@method" "@target-uri" "content-digest" \ "authorization" "signature";key="old-key" "signature-input"\ ;key="old-key");created=1618884480;keyid="xyz-2" ;tag="gnap-rotate" Signature: old-key=:vN4IKYsJl2RLFe+tYEm4dHM4R4BToqx5D2FfH4ge5WOkgxo\ dI2QRrjB8rysvoSEGvAfiVJOWsGcPD1lU639Amw==:, \ new-key=:VWUExXQ0geWeTUKhCfDT7WJyT++OHSVbfPA1ukW0o7mmstdbvIz9iOuH\ DRFzRBm0MQPFVMpLDFXQdE3vi2SL3ZjzcX2qLwzAtyRB9+RsV2caAA80A5ZGMoo\ gUsKPk4FFDN7KRUZ0vT9Mo9ycx9Dq/996TOWtAmq5z0YUYEwwn+T6+NcW8rFtms\ s1ZfXG0EoAfV6ve25p+x40Y1rvDHsfkakTRB4J8jWVDybSe39tjIKQBo3uicDVw\ twewBMNidIa+66iF3pWj8w9RSb0cncEgvbkHgASqaZeXmxxG4gM8p1HH9v/OqQT\ Oggm5gTWmCQs4oxEmWsfTOxefunfh3X+Qw==: { "key": { "proof": "httpsig", "jwk": { "kty": "RSA", "e": "AQAB", "kid": "xyz-2", "alg": "RS256", "n": "kOB5rR4Jv0GMeLaY6_It_r3ORwdf8ci_JtffXyaSx8xY..." } } }]]></sourcecode></figure>]]></sourcecode> <t>The verifier <bcp14>MUST</bcp14> validate both signatures before processing the request for key rotation.</t> </section> </section> <sectionanchor="mtls"><name>Mutualanchor="mtls"> <name>Mutual TLS</name> <t>This method is indicated by the method value<spanx style="verb">mtls</spanx><tt>mtls</tt> in string form.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "proof": "mtls" }]]></sourcecode></figure>]]></sourcecode> <t>The signer presents its TLS client certificate during TLS negotiation with the verifier.</t> <t>In the following non-normative example, the certificate is communicated to the application through the Client-Cert header field from a TLS reverse proxy as per <xref target="RFC9440"/>, leading to the following full HTTP request message:</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /gnap HTTP/1.1 Host: server.example.com Content-Type: application/jose Content-Length: 1567 Client-Cert: \ :MIIC6jCCAdKgAwIBAgIGAXjw74xPMA0GCSqGSIb3DQEBCwUAMDYxNDAyBgNVBAMM\ K05JWU15QmpzRGp5QkM5UDUzN0Q2SVR6a3BEOE50UmppOXlhcEV6QzY2bVEwHhcN\ MjEwNDIwMjAxODU0WhcNMjIwMjE0MjAxODU0WjA2MTQwMgYDVQQDDCtOSVlNeUJq\ c0RqeUJDOVA1MzdENklUemtwRDhOdFJqaTl5YXBFekM2Nm1RMIIBIjANBgkqhkiG\ 9w0BAQEFAAOCAQ8AMIIBCgKCAQEAhYOJ+XOKISdMMShn/G4W9m20mT0VWtQBsmBB\ kI2cmRt4Ai8BfYdHsFzAtYKOjpBR1RpKpJmVKxIGNy0g6Z3ad2XYsh8KowlyVy8I\ kZ8NMwSrcUIBZGYXjHpwjzvfGvXH/5KJlnR3/uRUp4Z4Ujk2bCaKegDn11V2vxE4\ 1hqaPUnhRZxe0jRETddzsE3mu1SK8dTCROjwUl14mUNo8iTrTm4n0qDadz8BkPo+\ uv4BC0bunS0K3bA/3UgVp7zBlQFoFnLTO2uWp/muLEWGl67gBq9MO3brKXfGhi3k\ OzywzwPTuq+cVQDyEN7aL0SxCb3Hc4IdqDaMg8qHUyObpPitDQIDAQABMA0GCSqG\ SIb3DQEBCwUAA4IBAQBnYFK0eYHy+hVf2D58usj39lhL5znb/q9G35GBd/XsWfCE\ wHuLOSZSUmG71bZtrOcx0ptle9bp2kKl4HlSTTfbtpuG5onSa3swRNhtKtUy5NH9\ W/FLViKWfoPS3kwoEpC1XqKY6l7evoTCtS+kTQRSrCe4vbNprCAZRxz6z1nEeCgu\ NMk38yTRvx8ihZpVOuU+Ih+dOtVe/ex5IAPYxlQsvtfhsUZqc7IyCcy72WHnRHlU\ fn3pJm0S5270+Yls3Iv6h3oBAP19i906UjiUTNH3g0xMW+V4uLxgyckt4wD4Mlyv\ jnaQ7Z3sR6EsXMocAbXHIAJhwKdtU/fLgdwL5vtx: { "access_token": { "access": [ "dolphin-metadata" ] }, "interact": { "start": ["redirect"], "finish": { "method": "redirect", "uri": "https://client.foo/callback", "nonce": "VJLO6A4CAYLBXHTR0KRO" } }, "client": { "key": { "proof": "mtls", "cert": "MIIC6jCCAdKgAwIBAgIGAXjw74xPMA0GCSqGSIb3DQEBCwUAMD\ YxNDAyBgNVBAMMK05JWU15QmpzRGp5QkM5UDUzN0Q2SVR6a3BEOE50UmppOXlhcEV\ 6QzY2bVEwHhcNMjEwNDIwMjAxODU0WhcNMjIwMjE0MjAxODU0WjA2MTQwMgYDVQQD\ DCtOSVlNeUJqc0RqeUJDOVA1MzdENklUemtwRDhOdFJqaTl5YXBFekM2Nm1RMIIBI\ jANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAhYOJ+XOKISdMMShn/G4W9m20mT\ 0VWtQBsmBBkI2cmRt4Ai8BfYdHsFzAtYKOjpBR1RpKpJmVKxIGNy0g6Z3ad2XYsh8\ KowlyVy8IkZ8NMwSrcUIBZGYXjHpwjzvfGvXH/5KJlnR3/uRUp4Z4Ujk2bCaKegDn\ 11V2vxE41hqaPUnhRZxe0jRETddzsE3mu1SK8dTCROjwUl14mUNo8iTrTm4n0qDad\ z8BkPo+uv4BC0bunS0K3bA/3UgVp7zBlQFoFnLTO2uWp/muLEWGl67gBq9MO3brKX\ fGhi3kOzywzwPTuq+cVQDyEN7aL0SxCb3Hc4IdqDaMg8qHUyObpPitDQIDAQABMA0\ GCSqGSIb3DQEBCwUAA4IBAQBnYFK0eYHy+hVf2D58usj39lhL5znb/q9G35GBd/Xs\ WfCEwHuLOSZSUmG71bZtrOcx0ptle9bp2kKl4HlSTTfbtpuG5onSa3swRNhtKtUy5\ NH9W/FLViKWfoPS3kwoEpC1XqKY6l7evoTCtS+kTQRSrCe4vbNprCAZRxz6z1nEeC\ guNMk38yTRvx8ihZpVOuU+Ih+dOtVe/ex5IAPYxlQsvtfhsUZqc7IyCcy72WHnRHl\ Ufn3pJm0S5270+Yls3Iv6h3oBAP19i906UjiUTNH3g0xMW+V4uLxgyckt4wD4Mlyv\ jnaQ7Z3sR6EsXMocAbXHIAJhwKdtU/fLgdwL5vtx" } "display": { "name": "My Client Display Name", "uri": "https://client.foo/" }, }, "subject": { "formats": ["iss_sub", "opaque"] } }]]></sourcecode></figure>]]></sourcecode> <t>The verifier compares the TLS client certificate presented during mutual TLS negotiation to the expected key of the signer. Since the TLS connection covers the entire message, there are no additional requirements to check.</t> <t>Note that in many instances, the verifier will not do a full certificate chain validation of the presented TLS client certificate, as the means of trust for this certificate could be in something other than a PKI system, such as a static registration or trust-on-first-use. See Sections <xreftarget="security-mtls"/>target="security-mtls" format="counter"/> and <xreftarget="security-mtls-patterns"/>target="security-mtls-patterns" format="counter"/> for some additional considerations for this key proofing method.</t> <sectionanchor="key-rotation-using-mtls"><name>Keyanchor="key-rotation-using-mtls"> <name>Key RotationusingUsing MTLS</name> <t>Since it is not possible to present two client authenticated certificates to a mutual TLS connection simultaneously, dynamic key rotation for this proofing method is not defined. Instead, key rotation for MTLS-based client instances is expected to be managed through deployment practices, as discussed in <xref target="security-mtls-patterns"/>.</t> </section> </section> <sectionanchor="detached-jws"><name>Detachedanchor="detached-jws"> <name>Detached JWS</name> <t>This method is indicated by the method value<spanx style="verb">jwsd</spanx><tt>jwsd</tt> in string form.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "proof": "jwsd" }]]></sourcecode></figure>]]></sourcecode> <t>The signer creates a JSON Web Signature (JWS) <xref target="RFC7515"/> object asfollows:</t>follows.</t> <t>To protect the request, the JOSE header of the signature contains the following claims:</t> <dl><dt><spanx style="verb">kid</spanx><dt><tt>kid</tt> (string):</dt> <dd> <!-- [rfced] Please review the text starting with "REQUIRED", and let us know if any updates are needed. Note that this text appears twice in the document. Original: kid (string): The key identifier. REQUIRED if the key is presented in JWK format, this MUST be the value of the kid field of the key. Perhaps: kid (string): The key identifier. REQUIRED if the key is presented in JWK format. This MUST be the value of the kid field of the key. Or kid (string): The key identifier. REQUIRED if the key is presented in JWK format, and MUST be the value of the kid field of the key. --> <!-- [rfced] To create complete sentences, the verb phrases "MUST be appropriate to the key presented" and what "MUST NOT be none" need subjects. May we update as suggested below? Note that this text appears twice in the document. Original: alg (string): The algorithm used to sign the request. MUST be appropriate to the key presented. If the key is presented as a JWK, this MUST be equal to the alg parameter of the key. MUST NOT be none. REQUIRED. Perhaps: alg (string): The algorithm used to sign the request. The algorithm MUST be appropriate to the key presented. If the key is presented as a JWK, this MUST be equal to the alg parameter of the key. This MUST NOT be none. REQUIRED. --> <t>The key identifier. <bcp14>REQUIRED</bcp14> if the key is presented in JWK format, this <bcp14>MUST</bcp14> be the value of the<spanx style="verb">kid</spanx><tt>kid</tt> field of the key.</t> </dd><dt><spanx style="verb">alg</spanx><dt><tt>alg</tt> (string):</dt> <dd> <t>The algorithm used to sign the request. <bcp14>MUST</bcp14> be appropriate to the key presented. If the key is presented as a JWK, this <bcp14>MUST</bcp14> be equal to the<spanx style="verb">alg</spanx><tt>alg</tt> parameter of the key. <bcp14>MUST NOT</bcp14> be<spanx style="verb">none</spanx>.<tt>none</tt>. <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">typ</spanx><dt><tt>typ</tt> (string):</dt> <dd> <t>The type header, value "gnap-binding-jwsd". <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">htm</spanx><dt><tt>htm</tt> (string):</dt> <dd> <t>The HTTPMethodmethod used to make this request, as a case-sensitive ASCII string. Note that most public HTTP methods are in uppercase ASCII by convention. <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">uri</spanx><dt><tt>uri</tt> (string):</dt> <dd> <t>The HTTP URI used for this request. This value <bcp14>MUST</bcp14> be an absolute URI, including all path and query components and no fragmentcomponent.components. <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">created</spanx><dt><tt>created</tt> (integer):</dt> <dd> <t>A timestamp of when the signature was created, in integer seconds since UNIX Epoch. <bcp14>REQUIRED</bcp14>.</t> </dd> </dl> <t>When the request is bound to an access token, the JOSE header <bcp14>MUST</bcp14> also include the following:</t> <dl><dt><spanx style="verb">ath</spanx><dt><tt>ath</tt> (string):</dt> <dd> <t>The hash of the access token. The value <bcp14>MUST</bcp14> be the result of Base64url encoding (with no padding) the SHA-256 digest of the ASCII encoding of the associated access token's value. <bcp14>REQUIRED</bcp14>.</t> </dd> </dl> <t>If the HTTP request hascontent, suchcontent (such as an HTTP POST or PUTmethod,method), the payload of the JWS object is the Base64url encoding (without padding) of the SHA256 digest of the bytes of the content. If the request being made does not havecontent, suchcontent (such as an HTTP GET, OPTIONS, or DELETEmethod,method), the JWS signature is calculated over an empty payload.</t> <t>The signer presents the signed object in compact form <xref target="RFC7515"/> in the Detached-JWSHTTP Headerheader field.</t> <t>In the following non-normative example, the JOSEHeaderheader contains the following parameters:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "alg": "RS256", "kid": "gnap-rsa", "uri": "https://server.example.com/gnap", "htm": "POST", "typ": "gnap-binding-jwsd", "created": 1618884475 }]]></sourcecode></figure>]]></sourcecode> <t>The request content is the following JSON object:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 { "access_token": { "access": [ "dolphin-metadata" ] }, "interact": { "start": ["redirect"], "finish": { "method": "redirect", "uri": "https://client.foo/callback", "nonce": "VJLO6A4CAYLBXHTR0KRO" } }, "client": { "key": { "proof": "jwsd", "jwk": { "kid": "gnap-rsa", "kty": "RSA", "e": "AQAB", "alg": "RS256", "n": "hYOJ-XOKISdMMShn_G4W9m20mT0VWtQBsmBBkI2cmRt4Ai8Bf\ YdHsFzAtYKOjpBR1RpKpJmVKxIGNy0g6Z3ad2XYsh8KowlyVy8IkZ8NMwSrcUIBZG\ YXjHpwjzvfGvXH_5KJlnR3_uRUp4Z4Ujk2bCaKegDn11V2vxE41hqaPUnhRZxe0jR\ ETddzsE3mu1SK8dTCROjwUl14mUNo8iTrTm4n0qDadz8BkPo-uv4BC0bunS0K3bA_\ 3UgVp7zBlQFoFnLTO2uWp_muLEWGl67gBq9MO3brKXfGhi3kOzywzwPTuq-cVQDyE\ N7aL0SxCb3Hc4IdqDaMg8qHUyObpPitDQ" } } "display": { "name": "My Client Display Name", "uri": "https://client.foo/" }, } }]]></sourcecode></figure>]]></sourcecode> <t>This is hashed to the followingBase64 encodedBase64-encoded value:</t><figure><artwork><![CDATA[<artwork><![CDATA[ PGiVuOZUcN1tRtUS6tx2b4cBgw9mPgXG3IPB3wY7ctc]]></artwork></figure>]]></artwork> <t>This leads to the following full HTTP request message:</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 POST /gnap HTTP/1.1 Host: server.example.com Content-Type: application/json Content-Length: 983 Detached-JWS: eyJhbGciOiJSUzI1NiIsImNyZWF0ZWQiOjE2MTg4ODQ0NzUsImh0b\ SI6IlBPU1QiLCJraWQiOiJnbmFwLXJzYSIsInR5cCI6ImduYXAtYmluZGluZytqd3\ NkIiwidXJpIjoiaHR0cHM6Ly9zZXJ2ZXIuZXhhbXBsZS5jb20vZ25hcCJ9.PGiVuO\ ZUcN1tRtUS6tx2b4cBgw9mPgXG3IPB3wY7ctc.fUq-SV-A1iFN2MwCRW_yolVtT2_\ TZA2h5YeXUoi5F2Q2iToC0Tc4drYFOSHIX68knd68RUA7yHqCVP-ZQEd6aL32H69e\ 9zuMiw6O_s4TBKB3vDOvwrhYtDH6fX2hP70cQoO-47OwbqP-ifkrvI3hVgMX9TfjV\ eKNwnhoNnw3vbu7SNKeqJEbbwZfpESaGepS52xNBlDNMYBQQXxM9OqKJaXffzLFEl\ -Xe0UnfolVtBraz3aPrPy1C6a4uT7wLda3PaTOVtgysxzii3oJWpuz0WP5kRujzDF\ wX_EOzW0jsjCSkL-PXaKSpZgEjNjKDMg9irSxUISt1C1T6q3SzRgfuQ { "access_token": { "access": [ "dolphin-metadata" ] }, "interact": { "start": ["redirect"], "finish": { "method": "redirect", "uri": "https://client.foo/callback", "nonce": "VJLO6A4CAYLBXHTR0KRO" } }, "client": { "key": { "proof": "jwsd", "jwk": { "kid": "gnap-rsa", "kty": "RSA", "e": "AQAB", "alg": "RS256", "n": "hYOJ-XOKISdMMShn_G4W9m20mT0VWtQBsmBBkI2cmRt4Ai8Bf\ YdHsFzAtYKOjpBR1RpKpJmVKxIGNy0g6Z3ad2XYsh8KowlyVy8IkZ8NMwSrcUIBZG\ YXjHpwjzvfGvXH_5KJlnR3_uRUp4Z4Ujk2bCaKegDn11V2vxE41hqaPUnhRZxe0jR\ ETddzsE3mu1SK8dTCROjwUl14mUNo8iTrTm4n0qDadz8BkPo-uv4BC0bunS0K3bA_\ 3UgVp7zBlQFoFnLTO2uWp_muLEWGl67gBq9MO3brKXfGhi3kOzywzwPTuq-cVQDyE\ N7aL0SxCb3Hc4IdqDaMg8qHUyObpPitDQ" } } "display": { "name": "My Client Display Name", "uri": "https://client.foo/" }, } }]]></sourcecode></figure>]]></sourcecode> <t>When the verifier receives the Detached-JWS header, it <bcp14>MUST</bcp14> parse and validate the JWS object. The signature <bcp14>MUST</bcp14> be validated against the expected key of the signer. If the HTTP message request contains content, the verifier <bcp14>MUST</bcp14> calculate the hash of the content just as the signer does, with no normalization or transformation of the request. All required fields <bcp14>MUST</bcp14> bepresentpresent, and their values <bcp14>MUST</bcp14> be valid. All fields <bcp14>MUST</bcp14> match the corresponding portions of the HTTP message. For example, the<spanx style="verb">htm</spanx><tt>htm</tt> field of the JWS header has to be the same as the HTTP verb used in the request.</t> <!--[rfced] May we number the two ways listed in this sentence and clarify the text as follows? Original: Note that this proof method depends on a specific cryptographic algorithm, SHA-256, in two ways: the ath hash algorithm is hardcoded, and computing the payload of the detached/attached signature also uses a hardcoded hash. Perhaps: Note that this proof method depends on a specific cryptographic algorithm, SHA-256, in two ways: 1) the ath hash algorithm is hardcoded and 2) the payload of the detached/attached signature is computed using a hardcoded hash. --> <t>Note that this proof method depends on a specific cryptographic algorithm, SHA-256, in two ways: the<spanx style="verb">ath</spanx><tt>ath</tt> hash algorithm is hardcoded, and computing the payload of the detached/attached signature also uses a hardcoded hash. A future version of this document may address crypto-agility for both these uses by replacing ath with a new header that upgrades thealgorithm,algorithm and possibly defining a new JWS header that indicates the HTTP content's hash method.</t> <sectionanchor="key-rotation-using-detached-jws"><name>Keyanchor="key-rotation-using-detached-jws"> <name>Key RotationusingUsing Detached JWS</name> <t>When rotating a key using Detached JWS, the message, which includes the new public key value or reference, is first signed with the old key as described above using a JWS object with<spanx style="verb">typ</spanx><tt>typ</tt> header value "gnap-binding-rotation-jwsd". The value of the JWS object is then taken as the payload of a new JWS object, to be signed by the new key using the parameters above.</t> <t>The value of the new JWS object is sent in the Detached-JWS header.</t> </section> </section> <sectionanchor="attached-jws"><name>Attachedanchor="attached-jws"> <name>Attached JWS</name> <t>This method is indicated by the method value<spanx style="verb">jws</spanx><tt>jws</tt> in string form.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "proof": "jws" }]]></sourcecode></figure>]]></sourcecode> <t>The signer creates a JWS <xref target="RFC7515"/> object asfollows:</t>follows.</t> <t>To protect the request, the JWS header contains the followingclaims.</t>claims:</t> <dl><dt><spanx style="verb">kid</spanx><dt><tt>kid</tt> (string):</dt> <dd> <t>The key identifier. <bcp14>REQUIRED</bcp14> if the key is presented in JWK format, this <bcp14>MUST</bcp14> be the value of the<spanx style="verb">kid</spanx><tt>kid</tt> field of the key.</t> </dd><dt><spanx style="verb">alg</spanx><dt><tt>alg</tt> (string):</dt> <dd> <t>The algorithm used to sign the request. <bcp14>MUST</bcp14> be appropriate to the key presented. If the key is presented as a JWK, this <bcp14>MUST</bcp14> be equal to the<spanx style="verb">alg</spanx><tt>alg</tt> parameter of the key. <bcp14>MUST NOT</bcp14> be<spanx style="verb">none</spanx>.<tt>none</tt>. <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">typ</spanx><dt><tt>typ</tt> (string):</dt> <dd> <t>The type header, value "gnap-binding-jws". <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">htm</spanx><dt><tt>htm</tt> (string):</dt> <dd> <t>The HTTPMethodmethod used to make this request, as a case-sensitive ASCII string. (Note that most public HTTP methods are in uppercase.) <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">uri</spanx><dt><tt>uri</tt> (string):</dt> <dd> <t>The HTTP URI used for this request, including all path and query components and no fragmentcomponent.components. <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">created</spanx><dt><tt>created</tt> (integer):</dt> <dd> <t>A timestamp of when the signature was created, in integer seconds since UNIX Epoch. <bcp14>REQUIRED</bcp14>.</t> </dd> </dl> <t>When the request is bound to an access token, the JOSE header <bcp14>MUST</bcp14> also include the following:</t> <dl><dt><spanx style="verb">ath</spanx><dt><tt>ath</tt> (string):</dt> <dd> <t>The hash of the access token. The value <bcp14>MUST</bcp14> be the result of Base64url encoding (with no padding) the SHA-256 digest of the ASCII encoding of the associated access token's value. <bcp14>REQUIRED</bcp14>.</t> </dd> </dl> <t>If the HTTP request hascontent, suchcontent (such as an HTTP POST or PUTmethod,method), the payload of the JWS object is the JSON serialized content of the request, and the object is signed according to JWS and serialized into compact form <xref target="RFC7515"/>. The signer presents the JWS as the content of the request along with a content type of<spanx style="verb">application/jose</spanx>.<tt>application/jose</tt>. The verifier <bcp14>MUST</bcp14> extract the payload of the JWS and treat it as the request content for further processing.</t> <t>If the request being made does not havecontent, suchcontent (such as an HTTP GET, OPTIONS, or DELETEmethod,method), the JWS signature is calculated over an empty payload and passed in the<spanx style="verb">Detached-JWS</spanx><tt>Detached-JWS</tt> header as described in <xref target="detached-jws"/>.</t> <t>In the following non-normative example, the JOSE header contains the following parameters:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ { "alg": "RS256", "kid": "gnap-rsa", "uri": "https://server.example.com/gnap", "htm": "POST", "typ": "gnap-binding-jws", "created": 1618884475 }]]></sourcecode></figure>]]></sourcecode> <t>The request content, used as the JWS Payload, is the following JSON object:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 { "access_token": { "access": [ "dolphin-metadata" ] }, "interact": { "start": ["redirect"], "finish": { "method": "redirect", "uri": "https://client.foo/callback", "nonce": "VJLO6A4CAYLBXHTR0KRO" } }, "client": { "key": { "proof": "jws", "jwk": { "kid": "gnap-rsa", "kty": "RSA", "e": "AQAB", "alg": "RS256", "n": "hYOJ-XOKISdMMShn_G4W9m20mT0VWtQBsmBBkI2cmRt4Ai8Bf\ YdHsFzAtYKOjpBR1RpKpJmVKxIGNy0g6Z3ad2XYsh8KowlyVy8IkZ8NMwSrcUIBZG\ YXjHpwjzvfGvXH_5KJlnR3_uRUp4Z4Ujk2bCaKegDn11V2vxE41hqaPUnhRZxe0jR\ ETddzsE3mu1SK8dTCROjwUl14mUNo8iTrTm4n0qDadz8BkPo-uv4BC0bunS0K3bA_\ 3UgVp7zBlQFoFnLTO2uWp_muLEWGl67gBq9MO3brKXfGhi3kOzywzwPTuq-cVQDyE\ N7aL0SxCb3Hc4IdqDaMg8qHUyObpPitDQ" } } "display": { "name": "My Client Display Name", "uri": "https://client.foo/" }, }, "subject": { "formats": ["iss_sub", "opaque"] } }]]></sourcecode></figure>]]></sourcecode> <t>This leads to the following full HTTP request message:</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 POST /gnap HTTP/1.1 Host: server.example.com Content-Type: application/jose Content-Length: 1047 eyJhbGciOiJSUzI1NiIsImNyZWF0ZWQiOjE2MTg4ODQ0NzUsImh0bSI6IlBPU1QiLCJ\ raWQiOiJnbmFwLXJzYSIsInR5cCI6ImduYXAtYmluZGluZytqd3NkIiwidXJpIjoiaH\ R0cHM6Ly9zZXJ2ZXIuZXhhbXBsZS5jb20vZ25hcCJ9.CnsKICAgICJhY2Nlc3NfdG9r\ ZW4iOiB7CiAgICAgICAgImFjY2VzcyI6IFsKICAgICAgICAgICAgImRvbHBoaW4tbWV\ 0YWRhdGEiCiAgICAgICAgXQogICAgfSwKICAgICJpbnRlcmFjdCI6IHsKICAgICAgIC\ Aic3RhcnQiOiBbInJlZGlyZWN0Il0sCiAgICAgICAgImZpbmlzaCI6IHsKICAgICAgI\ CAgICAgIm1ldGhvZCI6ICJyZWRpcmVjdCIsCiAgICAgICAgICAgICJ1cmkiOiAiaHR0\ cHM6Ly9jbGllbnQuZm9vL2NhbGxiYWNrIiwKICAgICAgICAgICAgIm5vbmNlIjogIlZ\ KTE82QTRDQVlMQlhIVFIwS1JPIgogICAgICAgIH0KICAgIH0sCiAgICAiY2xpZW50Ij\ ogewogICAgICAicHJvb2YiOiAiandzIiwKICAgICAgImtleSI6IHsKICAgICAgICAia\ ndrIjogewogICAgICAgICAgICAia2lkIjogImduYXAtcnNhIiwKICAgICAgICAgICAg\ Imt0eSI6ICJSU0EiLAogICAgICAgICAgICAiZSI6ICJBUUFCIiwKICAgICAgICAgICA\ gImFsZyI6ICJSUzI1NiIsCiAgICAgICAgICAgICJuIjogImhZT0otWE9LSVNkTU1TaG\ 5fRzRXOW0yMG1UMFZXdFFCc21CQmtJMmNtUnQ0QWk4QmZZZEhzRnpBdFlLT2pwQlIxU\ nBLcEptVkt4SUdOeTBnNlozYWQyWFlzaDhLb3dseVZ5OElrWjhOTXdTcmNVSUJaR1lY\ akhwd2p6dmZHdlhIXzVLSmxuUjNfdVJVcDRaNFVqazJiQ2FLZWdEbjExVjJ2eEU0MWh\ xYVBVbmhSWnhlMGpSRVRkZHpzRTNtdTFTSzhkVENST2p3VWwxNG1VTm84aVRyVG00bj\ BxRGFkejhCa1BvLXV2NEJDMGJ1blMwSzNiQV8zVWdWcDd6QmxRRm9GbkxUTzJ1V3Bfb\ XVMRVdHbDY3Z0JxOU1PM2JyS1hmR2hpM2tPenl3endQVHVxLWNWUUR5RU43YUwwU3hD\ YjNIYzRJZHFEYU1nOHFIVXlPYnBQaXREUSIKICAgICAgICB9CiAgICAgIH0KICAgICA\ gImRpc3BsYXkiOiB7CiAgICAgICAgIm5hbWUiOiAiTXkgQ2xpZW50IERpc3BsYXkgTm\ FtZSIsCiAgICAgICAgInVyaSI6ICJodHRwczovL2NsaWVudC5mb28vIgogICAgICB9L\ AogICAgfSwKICAgICJzdWJqZWN0IjogewogICAgICAgICJmb3JtYXRzIjogWyJpc3Nf\ c3ViIiwgIm9wYXF1ZSJdCiAgICB9Cn0K.MwNoVMQp5hVxI0mCs9LlOUdFtkDXaA1_eT\ vOXq7DOGrtDKH7q4vP2xUq3fH2jRAZqnobo0WdPP3eM3NH5QUjW8pa6_QpwdIWkK7r-\ u_52puE0lPBp7J4U2w4l9gIbg8iknsmWmXeY5F6wiGT8ptfuEYGgmloAJd9LIeNvD3U\ LW2h2dz1Pn2eDnbyvgB0Ugae0BoZB4f69fKWj8Z9wvTIjk1LZJN1PcL7_zT8Lrlic9a\ PyzT7Q9ovkd1s-4whE7TrnGUzFc5mgWUn_gsOpsP5mIIljoEEv-FqOW2RyNYulOZl0Q\ 8EnnDHV_vPzrHlUarbGg4YffgtwkQhdK72-JOxYQ]]></sourcecode></figure>]]></sourcecode> <t>When the verifier receives an attached JWS request, it <bcp14>MUST</bcp14> parse and validate the JWS object. The signature <bcp14>MUST</bcp14> be validated against the expected key of the signer. All required fields <bcp14>MUST</bcp14> bepresentpresent, and their values <bcp14>MUST</bcp14> be valid. All fields <bcp14>MUST</bcp14> match the corresponding portions of the HTTP message. For example, the<spanx style="verb">htm</spanx><tt>htm</tt> field of the JWS header has to be the same as the HTTP verb used in the request.</t> <t>Note that this proof method depends on a specific cryptographic algorithm, SHA-256, in two ways: the<spanx style="verb">ath</spanx><tt>ath</tt> hash algorithm is hardcoded, and computing the payload of the detached/attached signature also uses a hardcoded hash. A future version of this document may address crypto-agility for both these uses by replacing ath with a new header that upgrades thealgorithm,algorithm and possibly defining a new header that indicates the HTTP content's hash method.</t> <sectionanchor="key-rotation-using-attached-jws"><name>Keyanchor="key-rotation-using-attached-jws"> <name>Key RotationusingUsing Attached JWS</name> <t>When rotating a key using Attached JWS, the message, which includes the new public key value or reference, is first signed with the old key using a JWS object with<spanx style="verb">typ</spanx><tt>typ</tt> header value "gnap-binding-rotation-jws". The value of the JWS object is then taken as the payload of a new JWS object, to be signed by the new key.</t> </section> </section> </section> </section> <sectionanchor="resource-access-rights"><name>Resourceanchor="resource-access-rights"> <name>Resource Access Rights</name> <t>GNAP provides a rich structure for describing the protected resources hosted by RSs and accessed by client software. This structure is used when the client instance<xref target="request-token">requestsrequests an accesstoken</xref>token (<xref target="request-token"> </xref>) and when an<xref target="response-token">accessaccess token isreturned</xref>.returned (<xref target="response-token"> </xref>). GNAP's structure is designed to be analogous to the OAuth 2.0 Rich AuthorizationRequestRequests data structure defined in <xref target="RFC9396"/>.</t> <t>The root of this structure is a JSON array. The elements of the JSON array represent rights of access that are associated with the access token. Individual rights of access can be defined by the RS as either an object or a string. The resulting access is the union of all elements within the array.</t> <t>The access associated with the access token is described using objects that each contain multiple dimensions of access. Each object contains a <bcp14>REQUIRED</bcp14><spanx style="verb">type</spanx><tt>type</tt> property that determines the type of API that the token is used for and the structure of the rest of the object. There is no expected interoperability between different<spanx style="verb">type</spanx><tt>type</tt> definitions.</t> <dl><dt><spanx style="verb">type</spanx><dt><tt>type</tt> (string):</dt> <dd> <t>The type of resource request as a string. This field <bcp14>MAY</bcp14> define which other fields are allowed in the request object. <bcp14>REQUIRED</bcp14>.</t> </dd> </dl> <t>The value of the<spanx style="verb">type</spanx><tt>type</tt> field is under the control of the AS. This field <bcp14>MUST</bcp14> be compared using an exact byte match of the string value against known types by the AS. The AS <bcp14>MUST</bcp14> ensure that there is no collision between different authorization data types that it supports. The AS <bcp14>MUST NOT</bcp14> do any collation or normalization of data types during comparison. It is <bcp14>RECOMMENDED</bcp14> that designers of general-purpose APIs use a URI for this field to avoid collisions between multiple API types protected by a single AS.</t> <t>While it is expected that many APIs will have their own properties, this specification defines a set of common data fields that are designed to be usable across different types of APIs. This specification does not require the use of these common fields by an API definition but, instead, provides them as reusable generic components for API designers to make use of. The allowable values of all fields are determined by the API being protected, as defined by a particular<spanx style="verb">type</spanx><tt>type</tt> value.</t> <dl><dt><spanx style="verb">actions</spanx><dt><tt>actions</tt> (array of strings):</dt> <dd> <t>The types of actions the client instance will take at the RS as an array ofstrings. Forstrings (for example, a client instance asking for a combination of "read" and "write"access.</t>access).</t> </dd><dt><spanx style="verb">locations</spanx><dt><tt>locations</tt> (array of strings):</dt> <dd> <t>The location of the RS as an array of strings. These strings are typically URIs identifying the location of the RS.</t> </dd><dt><spanx style="verb">datatypes</spanx><dt><tt>datatypes</tt> (array of strings):</dt> <dd> <t>The kinds of data available to the client instance at the RS's API as an array ofstrings. Forstrings (for example, a client instance asking for access to raw "image" data and "metadata" at a photographAPI.</t>API).</t> </dd><dt><spanx style="verb">identifier</spanx><dt><tt>identifier</tt> (string):</dt> <dd> <t>A string identifier indicating a specific resource at theRS. ForRS (for example, a patient identifier for a medical API or a bank account number for a financialAPI.</t>API).</t> </dd><dt><spanx style="verb">privileges</spanx><dt><tt>privileges</tt> (array of strings):</dt> <dd> <t>The types or levels of privilege being requested at theresource. Forresource (for example, a client instance asking foradministrative level access,administrative-level access or access when the resource owner is no longeronline.</t>online).</t> </dd> </dl> <t>The following non-normative exampleis describingdescribes three kinds of access (read, write, and delete) to each of two different locations and two different data types(metadata,(metadata and images) for a single access token using the fictitious<spanx style="verb">photo-api</spanx><tt>photo-api</tt> type definition.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "access": [ { "type": "photo-api", "actions": [ "read", "write", "delete" ], "locations": [ "https://server.example.net/", "https://resource.local/other" ], "datatypes": [ "metadata", "images" ] } ]]]></sourcecode></figure>]]></sourcecode> <t>While the exact semantics of interpreting the fields of an access request objectisare subject to the definition of the<spanx style="verb">type</spanx>,<tt>type</tt>, it is expected that the access requested for each object in the array is the cross-product of all fields of the object. That is to say, the object represents a request for all<spanx style="verb">actions</spanx><tt>actions</tt> listed to be used at all<spanx style="verb">locations</spanx><tt>locations</tt> listed for all possible<spanx style="verb">datatypes</spanx><tt>datatypes</tt> listed within the object. Assuming the request above was granted, the client instance could assume that it would be able to do a<spanx style="verb">read</spanx><tt>read</tt> action against the<spanx style="verb">images</spanx><tt>images</tt> on the first server as well as a<spanx style="verb">delete</spanx><tt>delete</tt> action on the<spanx style="verb">metadata</spanx><tt>metadata</tt> of the second server, or any other combination of these fields, using the same access token.</t> <t>To request a different combination of access, such as requesting one of the possible<spanx style="verb">actions</spanx><tt>actions</tt> against one of the possible<spanx style="verb">locations</spanx><tt>locations</tt> and a different choice of possible<spanx style="verb">actions</spanx><tt>actions</tt> against a different one of the possible<spanx style="verb">locations</spanx>,<tt>locations</tt>, the client instance can include multiple separate objects in the<spanx style="verb">resources</spanx><tt>resources</tt> array. The total access rights for the resulting access tokenisare the union of all objects. The following non-normative example uses the same fictitious<spanx style="verb">photo-api</spanx><tt>photo-api</tt> type definition to request a single access token with more specifically targeted access rights by using two discrete objects within the request.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "access": [ { "type": "photo-api", "actions": [ "read" ], "locations": [ "https://server.example.net/" ], "datatypes": [ "images" ] }, { "type": "photo-api", "actions": [ "write", "delete" ], "locations": [ "https://resource.local/other" ], "datatypes": [ "metadata" ] } ]]]></sourcecode></figure>]]></sourcecode> <!-- [rfced] May we update the text starting with "while simultaneously requesting" as follows to improve clarity? Original: The access requested here is for read access to images on one server while simultaneously requesting write and delete access for metadata on a different server, but importantly without requesting write or delete access to images on the first server. Perhaps: The access requested here is for read access to images on one server and for simultaneous write and delete access for metadata on a different server (importantly, without requesting write or delete access to images on the first server). --> <t>The access requested here is for<spanx style="verb">read</spanx><tt>read</tt> access to<spanx style="verb">images</spanx><tt>images</tt> on one server while simultaneously requesting<spanx style="verb">write</spanx><tt>write</tt> and<spanx style="verb">delete</spanx><tt>delete</tt> access for<spanx style="verb">metadata</spanx><tt>metadata</tt> on a different server, but importantly without requesting<spanx style="verb">write</spanx><tt>write</tt> or<spanx style="verb">delete</spanx><tt>delete</tt> access to<spanx style="verb">images</spanx><tt>images</tt> on the first server.</t> <t>It is anticipated that API designers will use a combination of common fields defined in this specification as well as fields specific to the API itself. The following non-normative example shows the use of both common and API-specific fields as part of two different fictitious API<spanx style="verb">type</spanx><tt>type</tt> values. The first access request includes the<spanx style="verb">actions</spanx>, <spanx style="verb">locations</spanx>,<tt>actions</tt>, <tt>locations</tt>, and<spanx style="verb">datatypes</spanx><tt>datatypes</tt> fields specified here as well as the API-specific<spanx style="verb">geolocation</spanx><tt>geolocation</tt> field. The second access request includes the<spanx style="verb">actions</spanx><tt>actions</tt> and<spanx style="verb">identifier</spanx><tt>identifier</tt> fields specified here as well as the API-specific<spanx style="verb">currency</spanx><tt>currency</tt> field.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "access": [ { "type": "photo-api", "actions": [ "read", "write" ], "locations": [ "https://server.example.net/", "https://resource.local/other" ], "datatypes": [ "metadata", "images" ], "geolocation": [ { lat: -32.364, lng: 153.207 }, { lat: -35.364, lng: 158.207 } ] }, { "type": "financial-transaction", "actions": [ "withdraw" ], "identifier": "account-14-32-32-3", "currency": "USD" } ]]]></sourcecode></figure>]]></sourcecode> <t>If this request is approved, the resulting access token's access rights will be the union of the requested types of access for each of the two APIs, just as above.</t> <sectionanchor="resource-access-reference"><name>Requestinganchor="resource-access-reference"> <name>Requesting ResourcesByby Reference</name> <t>Instead of sending an<xref target="resource-access-rights">objectobject describing the requestedresource</xref>,resource (<xref target="resource-access-rights"> </xref>), access rights <bcp14>MAY</bcp14> be communicated as a string known to the AS representing the access being requested. Just like access rights communicated as an object, access rights communicated as reference strings indicate a specific access at a protected resource. In the following non-normative example, three distinct resource access rights are being requested.</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "access": [ "read", "dolphin-metadata", "some other thing" ]]]></sourcecode></figure>]]></sourcecode> <t>This value is opaque to the client instance and <bcp14>MAY</bcp14> be any valid JSONstring, and thereforestring; therefore, it could include spaces,unicodeUnicode characters, and properly escaped string sequences. However, in somesituationssituations, the value is intended to be seen and understood by the client software's developer. In such cases, the API designer choosing any such human-readable strings <bcp14>SHOULD</bcp14> take steps to ensure the string values are not easily confused by a developer, such as by limiting the strings to easily disambiguated characters.</t> <t>This functionality is similar in practice to OAuth 2.0's<spanx style="verb">scope</spanx><tt>scope</tt> parameter <xref target="RFC6749"/>, where a single string represents the set of access rights requested by the client instance. As such, the reference string could contain any valid OAuth 2.0 scopevaluevalue, as in <xref target="example-oauth2"/>. Note that the reference string here is not bound to the same character restrictions asinOAuth 2.0's<spanx style="verb">scope</spanx><tt>scope</tt> definition.</t> <t>A single<spanx style="verb">access</spanx><tt>access</tt> array <bcp14>MAY</bcp14> include both object-type and string-type resource items. In this non-normative example, the client instance is requesting access to a<spanx style="verb">photo-api</spanx><tt>photo-api</tt> and<spanx style="verb">financial-transaction</spanx><tt>financial-transaction</tt> API type as well as the reference values of<spanx style="verb">read</spanx>, <spanx style="verb">dolphin-metadata</spanx>,<tt>read</tt>, <tt>dolphin-metadata</tt>, and<spanx style="verb">some<tt>some otherthing</spanx>.</t> <figure><sourcecodething</tt>.</t> <sourcecode type="json"><![CDATA[ "access": [ { "type": "photo-api", "actions": [ "read", "write", "delete" ], "locations": [ "https://server.example.net/", "https://resource.local/other" ], "datatypes": [ "metadata", "images" ] }, "read", "dolphin-metadata", { "type": "financial-transaction", "actions": [ "withdraw" ], "identifier": "account-14-32-32-3", "currency": "USD" }, "some other thing" ]]]></sourcecode></figure>]]></sourcecode> <t>The requested access is the union of all elements of the array, including both objects and reference strings.</t> <t>In order to facilitate the use of both object and reference strings to access the same kind of APIs, the API designer can define a clear mapping between these forms. One possible approach for choosing reference string values is to use the same value as the<spanx style="verb">type</spanx><tt>type</tt> parameter from thefully-specifiedfully specified object, with the API defining a set of default behaviors in this case. For example, an API definition could declare the following string:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "access": [ "photo-api" ]]]></sourcecode></figure>]]></sourcecode> <t>As being equivalent to the followingfully-definedfully defined object:</t><figure><sourcecode<sourcecode type="json"><![CDATA[ "access": [ { "type": "photo-api", "actions": [ "read", "write", "delete" ], "datatypes": [ "metadata", "image" ] } ]]]></sourcecode></figure>]]></sourcecode> <t>The exact mechanisms for relating reference strings is up to the API designer. These are enforced by the AS, and the details are out of scope for this specification.</t> </section> </section> <sectionanchor="discovery"><name>Discovery</name>anchor="discovery"> <name>Discovery</name> <t>By design, GNAP minimizes the need for any pre-flight discovery. To begin a request, the client instance only needs to know the grant endpoint of the AS (a single URI) and which keys it will use to sign the request. Everything else can be negotiated dynamically in the course of the protocol.</t> <t>However, the AS can have limits on its allowed functionality. If the client instance wants to optimize its calls to the AS before making a request, it <bcp14>MAY</bcp14> send an HTTP OPTIONS request to the grant request endpoint to retrieve the server's discovery information. The AS <bcp14>MUST</bcp14> respond with a JSON document with Content-Type<spanx style="verb">application/json</spanx><tt>application/json</tt> containing a single object with the following fields:</t> <dl><dt><spanx style="verb">grant_request_endpoint</spanx><dt><tt>grant_request_endpoint</tt> (string):</dt> <dd> <t>The location of the AS's grant request endpoint. The location <bcp14>MUST</bcp14> be an absolute URL <xref target="RFC3986"/> with a scheme component (which <bcp14>MUST</bcp14> be "https"), a host component, andoptionally,optionally port,pathpath, and query components and no fragment components. This URL <bcp14>MUST</bcp14> match the URL the client instance used to make the discovery request. <bcp14>REQUIRED</bcp14>.</t> </dd><dt><spanx style="verb">interaction_start_modes_supported</spanx><dt><tt>interaction_start_modes_supported</tt> (array of strings):</dt> <dd> <!-- [rfced] Please review the use of "section" in the following sentences and let us know if any updates are needed. For some instances of "section", we see usage with both "section" and "field" in the document: client section vs. client field continue section vs. continue field key section vs. key field For others, we just see usage with "section" (note inconsistency with first): interaction finish section vs. interaction "finish" section interaction section interaction start section subject request section subject identifier section subject assertion section interaction request section user request section Current: * the "nonce" value sent by the client instance in the interaction "finish" section of the initial request (Section 2.5.2) Since this response does not include a continue section, the client instance cannot continue to poll the AS for additional updates and the grant request is _finalized_. Since this is an expansion of what it asked for previously, the client instance also includes a new interaction section in case the AS needs to interact with the RO again to gather additional authorization. The client instance MUST NOT include the client section of the request, since the client instance is assumed not to have changed. The client instance can also signal which RO it requires authorization from, if known, by using the subject request section (Section 2.2) and user request section (Section 2.4). If the interaction methods expire, the client MAY restart the interaction process for this grant request by sending an update (Section 5.3) with a new interaction request section (Section 2.5). The values of this list correspond to the possible values for the interaction start section of the request (Section 2.5.1) and MUST be values from the "GNAP Interaction Start Modes" registry (Section 11.9). The values of this list correspond to the possible values for the method element of the interaction finish section of the request (Section 2.5.2) and MUST be values from the "GNAP Interaction Finish Methods" registry (Section 11.10). The values of this list correspond to possible values of the proof field of the key section of the request (Section 7.1) and MUST be values from the "GNAP Key Proofing Methods" registry (Section 11.16). The values of this list correspond to possible values of the subject identifier section of the request (Section 2.2) and MUST be values from the "Subject Identifier Formats" registry established by [RFC9493]. The values of this list correspond to possible values of the subject assertion section of the request (Section 2.2) and MUST be values from the "GNAP Assertion Formats" registry (Section 11.6). --> <t>A list of the AS's interaction start methods. The values of this list correspond to the possible values for the<xref target="request-interact-start">interactioninteraction startsection</xref>section of the request (<xref target="request-interact-start"> </xref>) and <bcp14>MUST</bcp14> be values from the<xref target="IANA-interaction-start-modes">GNAP"GNAP Interaction StartModes Registry</xref>.Modes" registry (<xref target="IANA-interaction-start-modes"> </xref>). <bcp14>OPTIONAL</bcp14>.</t> </dd><dt><spanx style="verb">interaction_finish_methods_supported</spanx><dt><tt>interaction_finish_methods_supported</tt> (array of strings):</dt> <dd> <t>A list of the AS's interaction finish methods. The values of this list correspond to the possible values for the method element of the<xref target="request-interact-finish">interactioninteraction finishsection</xref>section of the request (<xref target="request-interact-finish"> </xref>) and <bcp14>MUST</bcp14> be values from the<xref target="IANA-interaction-finish-methods">GNAP"GNAP Interaction FinishMethods Registry</xref>.Methods" registry (<xref target="IANA-interaction-finish-methods"> </xref>). <bcp14>OPTIONAL</bcp14>.</t> </dd><dt><spanx style="verb">key_proofs_supported</spanx><dt><tt>key_proofs_supported</tt> (array of strings):</dt> <dd> <t>A list of the AS's supported key proofing mechanisms. The values of this list correspond to possible values of the<spanx style="verb">proof</spanx><tt>proof</tt> field of the<xref target="key-format">key section</xref>key section of the request (<xref target="key-format"> </xref>) and <bcp14>MUST</bcp14> be values from the<xref target="IANA-key-proof-methods">GNAP"GNAP Key ProofingMethods Registry</xref>.Methods" registry (<xref target="IANA-key-proof-methods"> </xref>). <bcp14>OPTIONAL</bcp14>.</t> </dd><dt><spanx style="verb">sub_id_formats_supported</spanx><!--[rfced] FYI, the "Subject Identifier Formats" registry is not included in RFC 9493. It was renamed from "Security Event Identifier Formats" to "Subject Identifier Formats" per Erratum ID 7727 (https://www.rfc-editor.org/errata/eid7727). Would it be helpful to either 1) include a citation to the registry rather than to RFC 9493 or 2) include a citation to the erratum in addition to the citation for RFC 9493? Link to registry: https://www.iana.org/assignments/secevent Original: sub_id_formats_supported (array of strings): A list of the AS's supported subject identifier formats. The values of this list correspond to possible values of the subject identifier section (Section 2.2) of the request and MUST be values from the Subject Identifier Formats Registry established by [RFC9493]. OPTIONAL. Perhaps (citation to registry): sub_id_formats_supported (array of strings): A list of the AS's supported subject identifier formats. The values of this list correspond to possible values of the subject identifier section of the request (Section 2.2) and MUST be values from the "Subject Identifier Formats" registry [IANA.Subj-ID-Formats]. OPTIONAL. ... [IANA.Subj-ID-Formats] IANA, "Subject Identifier Formats", <https://www.iana.org/assignments/secevent>. Or (citation to erratum): sub_id_formats_supported (array of strings): A list of the AS's supported subject identifier formats. The values of this list correspond to possible values of the subject identifier section of the request (Section 2.2) and MUST be values from the "Subject Identifier Formats" registry [RFC9493] [Err7727]. OPTIONAL. ... [Err7727] RFC Errata, Erratum ID 7727, RFC 9493, <https://www.rfc-editor.org/errata/eid7727>. --> <dt><tt>sub_id_formats_supported</tt> (array of strings):</dt> <dd> <t>A list of the AS's supported subject identifier formats. The values of this list correspond to possible values of the<xref target="request-subject">subjectsubject identifiersection</xref>section of the request (<xref target="request-subject"> </xref>) and <bcp14>MUST</bcp14> be values from theSubject"Subject IdentifierFormats RegistryFormats" registry established by <xref target="RFC9493"/>. <bcp14>OPTIONAL</bcp14>.</t> </dd><dt><spanx style="verb">assertion_formats_supported</spanx><dt><tt>assertion_formats_supported</tt> (array of strings):</dt> <dd> <t>A list of the AS's supported assertion formats. The values of this list correspond to possible values of the<xref target="request-subject">subjectsubject assertionsection</xref>section of the request (<xref target="request-subject"> </xref>) and <bcp14>MUST</bcp14> be values from the<xref target="IANA-assertion-formats">GNAP"GNAP AssertionFormats Registry</xref>.Formats" registry (<xref target="IANA-assertion-formats"> </xref>). <bcp14>OPTIONAL</bcp14>.</t> </dd><dt><spanx style="verb">key_rotation_supported</spanx><dt><tt>key_rotation_supported</tt> (boolean):</dt> <dd> <t>The boolean "true" indicates that<xref target="rotate-access-token-key">rotationrotation of access token bound keys by theclient</xref>client (<xref target="rotate-access-token-key"> </xref>) is supported by the AS. The absence of this field or a boolean "false" value indicates that this feature is not supported.</t> </dd> </dl> <t>The information returned from this method is for optimization purposes only. The AS <bcp14>MAY</bcp14> deny any request, or any portion of a request, even if it lists a capability as supported. For example, if a given client instance can be registered with the<spanx style="verb">mtls</spanx><tt>mtls</tt> key proofingmechanism,mechanism but the AS also returns other proofing methods from the discovery document, then the AS will still deny a request from that client instance using a different proofing mechanism. Similarly, an AS with<spanx style="verb">key_rotation_supported</spanx><tt>key_rotation_supported</tt> set to "true" can still deny any request for rotating any access token's key for a variety of reasons.</t> <t>Additional fields can be defined in the<xref target="IANA-as-discovery">GNAP"GNAP Authorization Server DiscoveryFields Registry</xref>.</t>Fields" registry (<xref target="IANA-as-discovery"> </xref>).</t> <sectionanchor="rs-request-without-token"><name>RS-firstanchor="rs-request-without-token"> <name>RS-First Method of AS Discovery</name> <t>If the client instance calls an RS without an accesstoken,token or with an invalid access token, the RS <bcp14>SHOULD</bcp14> be explicit about the fact that GNAP needs to be used to access the resource by responding with the WWW-Authenticate header field and a GNAP challenge.</t> <t>In some situations, the client instance might want to know with which specific AS it needs to negotiate for access to that RS. The RS <bcp14>MAY</bcp14> additionally return the following <bcp14>OPTIONAL</bcp14> parameters:</t> <dl><dt><spanx style="verb">as_uri</spanx>:</dt><dt><tt>as_uri</tt>:</dt> <dd> <t>The URI of the grant endpoint of the GNAP AS. Used by the client instance to call the AS to request an access token.</t> </dd><dt><spanx style="verb">referrer</spanx>:</dt><dt><tt>referrer</tt>:</dt> <dd> <t>The URI of the GNAP RS. Sent by the client instance in the Referer header as part of the grant request.</t> </dd><dt><spanx style="verb">access</spanx>:</dt><dt><tt>access</tt>:</dt> <dd> <t>An opaque access reference as defined in <xref target="resource-access-reference"/>. <bcp14>MUST</bcp14> be sufficient for at least the action the client instance was attempting to take at the RS and <bcp14>MAY</bcp14> allow additional access rights as well. Sent by the client as an access right in the grant request.</t> </dd> </dl> <t>The client instance <bcp14>SHOULD</bcp14> then use both the<spanx style="verb">referrer</spanx><tt>referrer</tt> and<spanx style="verb">access</spanx><tt>access</tt> parameters in its access token request. The client instance <bcp14>MUST</bcp14> check that the<spanx style="verb">referrer</spanx><tt>referrer</tt> parameter is equal to the URI of the RS using the simple string comparison method in <xref section="6.2.1" sectionFormat="of" target="RFC3986"/>.</t> <t>The means for the RS to determine the value for the<spanx style="verb">access</spanx><tt>access</tt> reference are out of scope of this specification, but some dynamic methods are discussed in <xref target="I-D.ietf-gnap-resource-servers"/>.</t> <t>When receiving the following response from the RS:</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 WWW-Authenticate: \ GNAP as_uri=https://as.example/tx\ ;access=FWWIKYBQ6U56NL1\ ;referrer=https://rs.example]]></sourcecode></figure>]]></sourcecode> <t>The client instance then makes a request to the<spanx style="verb">as_uri</spanx><tt>as_uri</tt> as described in <xref target="request"/>, with the value of<spanx style="verb">referrer</spanx><tt>referrer</tt> passed as an HTTP Referer header field and the<spanx style="verb">access</spanx><tt>access</tt> reference passed unchanged into the<spanx style="verb">access</spanx><tt>access</tt> array in the<spanx style="verb">access_token</spanx><tt>access_token</tt> portion of the request. The client instance <bcp14>MAY</bcp14> request additional resources and other information.</t> <t>In the following non-normative example, the client instance is requesting a single access token using the opaque access reference<spanx style="verb">FWWIKYBQ6U56NL1</spanx><tt>FWWIKYBQ6U56NL1</tt> received from the RS in addition to the<spanx style="verb">dolphin-metadata</spanx><tt>dolphin-metadata</tt> that the client instance has been configured with out of band.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /tx HTTP/1.1 Host: as.example Referer: https://rs.example/resource Content-Type: application/json Signature-Input: sig1=... Signature: sig1=... Content-Digest: sha-256=... { "access_token": { "access": [ "FWWIKYBQ6U56NL1", "dolphin-metadata" ] }, "client": "KHRS6X63AJ7C7C4AZ9AO" }]]></sourcecode></figure>]]></sourcecode> <t>The client instance includes the Referer header field as a way for the AS to know that the process is initiated through a discovery process at the RS.</t> <t>If issued, the resulting access token would contain sufficient access to be used at both referenced resources.</t> <t>Security considerations, especially related to the potential of a<xref target="security-compromised-rs">compromised RS</xref>compromised RS (<xref target="security-compromised-rs"> </xref>) redirecting the requests of an otherwise properly authenticated client, need to be carefully considered when allowing such a discovery process. This risk can be mitigated by an alternative pre-registration process so that the client knows which AS protects which RS. There are also privacy considerations related to revealing which AS is protecting a givenresource,resource; these are discussed in <xref target="privacy-correlation-client"/>.</t> </section> <sectionanchor="grant-discovery"><name>Dynamic grantanchor="grant-discovery"> <name>Dynamic Grant Endpoint Discovery</name> <!-- [rfced] This sentence uses both "contextual" and "contextually". Are both needed? Original: Advanced use cases could define contextual methods for contextually providing this endpoint to the client instance securely. Perhaps: Advanced use cases could define contextual methods for securely providing this endpointdiscovery</name>to the client instance. --> <t>Additional methods of discovering the appropriate grant endpoint for a given application are outside the scope of this specification. This limitation is intentional, as many applications rely on static configuration between the client instance and AS, as is common in OAuth 2.0. However, the dynamic nature of GNAP makes it a prime candidate for other extensions defining methods for discovery of the appropriate AS grant endpoint at runtime. Advanced use cases could define contextual methods for contextually providing this endpoint to the client instance securely. Furthermore, GNAP's design intentionally requires the client instance to only know the grant endpoint and not additional parameters, since other functions and values can be disclosed and negotiated during the grant process.</t> </section> </section> <sectionanchor="Acknowledgements"><name>Acknowledgements</name> <t>The editors would like to thank the feedback of the following individuals for their reviews, implementations, and contributions: <contact fullname="Åke Axeland" asciiFullname="Ake Axeland"/>, Aaron Parecki, Adam Omar Oueidat, Andrii Deinega, Annabelle Backman, Dick Hardt, Dmitri Zagidulin, Dmitry Barinov, Fabien Imbault, Florian Helmschmidt, Francis Pouatcha, George Fletcher, Haardik Haardik, Hamid Massaoud, Jacky Yuan, Joseph Heenan, Justin Richer, Kathleen Moriarty, Leif Johansson, Mike Jones, Mike Varley, Nat Sakimura, Takahiko Kawasaki, Takahiro Tsuchiya, Yaron Sheffer.</t> <t>The editors would also like to thank the GNAP working group design team of Kathleen Moriarty, Fabien Imbault, Dick Hardt, Mike Jones, and Justin Richer, who incorporated elements from the XAuth and XYZ proposals to create the first version of this document.</t> <t>In addition, the editors would like to thank Aaron Parecki and Mike Jones for insights into how to integrate identity and authentication systems into the core protocol, and Justin Richer and Dick Hardt for the use cases, diagrams, and insights provided in the XYZ and XAuth proposals that have been incorporated here. The editors would like to especially thank Mike Varley and the team at SecureKey for feedback and development of early versions of the XYZ protocol that fed into this standards work.</t> <t>Finally, the editors want to acknowledge the immense contributions of Aaron Parecki to the content of this document. We thank him for his insight, input, and hard work, without which GNAP would not have grown to what it is.</t> </section> <section anchor="IANA"><name>IANAanchor="IANA"> <name>IANA Considerations</name> <t>IANAis requested to addhas added values to existing registriesand to createas well as created 16 registries forthe Grant Negotiation and Authorization ProtocolGNAP andto populatepopulated those registries with initial values as described in this section.</t> <t>All use of value typing is based on<xref target="RFC8259"/>data types in <xref target="RFC8259"/> and <bcp14>MUST</bcp14> be one of the following: number, object, string, boolean, or array. When the type is array, the contents of the array <bcp14>MUST</bcp14> be specified, as in "array of objects" when one subtype is allowed or "array of strings/objects" when multiple simultaneous subtypes are allowed. When the type is object, the structure of the object <bcp14>MUST</bcp14> be specified in the definition. If a parameter is available in different types, each type <bcp14>SHOULD</bcp14> be registered separately.</t> <t>General guidance for extension parameters is found in <xref target="extensions"/>.</t> <sectionanchor="http-authentication-scheme-registration"><name>HTTPanchor="http-authentication-scheme-registration"> <name>HTTP Authentication Scheme Registration</name><t>This specification requests registration<t>IANA has registered of the following scheme in the "Hypertext Transfer Protocol (HTTP) Authentication Scheme Registry" definedbein <xref section="18.5" sectionFormat="of"target="HTTP"/>:</t> <t><list style="symbols"> <t>Authenticationtarget="RFC9110"/>:</t> <dl> <dt>Authentication SchemeName: <spanx style="verb">GNAP</spanx></t> <t>Reference: <xrefName:</dt><dd>GNAP</dd> <dt>Reference:</dt><dd><xref target="use-access-token"/> of&SELF;</t> </list></t>RFC 9635</dd> </dl> </section> <sectionanchor="media-type-registration"><name>Mediaanchor="media-type-registration"> <name>Media Type Registration</name><t>This<!-- [rfced] IANA FLAG: FYI - We made the following updates in the "Media Type Registration" section. Please review and let us know any concerns. Note that we will ask IANA to update the templates to match the edited document prior to publication. https://www.iana.org/assignments/media-types/application/gnap-binding-jws https://www.iana.org/assignments/media-types/application/gnap-binding-jwsd https://www.iana.org/assignments/media-types/application/gnap-binding-rotation-jws https://www.iana.org/assignments/media-types/application/gnap-binding-rotation-jwsd a) We created subsections in the "Media Type Registration" sectionrequests registrationto improve readability of the templates. Please review the titles of the subsections and suggest any improvements. b) We added the following from the template in RFC 6838. Deprecated alias names for this type: n/a c) We updated "n/a" to "N/A" in the templates for the media types per Section 5.6 of RFC 6838, which states: "N/A", written exactly that way, can be used in any field if desired to emphasize the fact that it does not apply or that the question was not omitted by accident. --> <!-- [rfced] IANA FLAG: We suggest updating the paragraphs about expectations of the DE to use bulleted lists. These paragraphs appear in Sections 10.3-10.18 and contain multiple sentences that each start with "The DE is expected to ensure that...". Here is one example (from Section 10.3): Original: The Designated Expert (DE) is expected to ensure that all registrations follow the template presented in Section 11.3.1. The DE is expected to ensure that the request parameter's definition is sufficiently orthogonal to existing functionality provided by existing parameters. The DE is expected to ensure that registrations for the same name with different types are sufficiently close in functionality so as not to cause confusion for developers. The DE is expected to ensure that the request parameter's definition specifies the expected behavior of the AS in response to the request parameter for each potential state of the grant request. Perhaps: The designated expert (DE) is expected to ensure the following: * All registrations follow the template presented in Section 11.3.1. * The request parameter's definition is sufficiently orthogonal to existing functionality provided by existing parameters. * Registrations for the same name with different types are sufficiently close in functionality so as not to cause confusion for developers. * The request parameter's definition specifies the expected behavior of the AS in response to the request parameter for each potential state of the grant request. Or: The designated expert (DE) is expected to do the following: * Ensure that all registrations follow the template presented in Section 11.3.1. * Ensure that the request parameter's definition is sufficiently orthogonal to existing functionality provided by existing parameters. * Ensure that registrations for the same name with different types are sufficiently close in functionality so as not to cause confusion for developers. * Ensure that the request parameter's definition specifies the expected behavior of the AS in response to the request parameter for each potential state of the grant request. --> <!-- [rfced] IANA FLAG: FYI - We made the following changes. Please let us know any concerns. a) In Section 10.10.1, we updated "Method" in the registration template to "Mode" (as in the table in Section 10.10.2). Original: Method: An identifier for the interaction finish method. Current: Mode: An identifier for the interaction finish method. b) In 10.11.1, we updated "Name" in the registration template to "Mode" (as in the table in Section 10.11.2). Original: Name: An identifier for the parameter. Current: Mode: An identifier for the parameter. --> <t>Per this section, IANA has registered the following media types <xref target="RFC2046"/> in the "Media Types" registry <xref target="IANA.MediaTypes"/>in the manneras described in <xref target="RFC6838"/>.</t><t>To indicate<section anchor="media-type-reg1"> <name>application/gnap-binding-jwsd</name> <t>This media type indicates that the content is a GNAP message to be bound with a detached JWSmechanism:</t> <t><list style="symbols"> <t>Type name: application</t> <t>Subtype name: gnap-binding-jwsd</t> <t>Required parameters: n/a</t> <t>Optional parameters: n/a</t> <t>Encoding considerations: binary</t> <t>Security considerations: Seemechanism.</t> <dl spacing="normal"> <dt>Type name:</dt><dd>application</dd> <dt>Subtype name:</dt><dd>gnap-binding-jwsd</dd> <dt>Required parameters:</dt><dd>N/A</dd> <dt>Optional parameters:</dt><dd>N/A</dd> <dt>Encoding considerations:</dt><dd>binary</dd> <dt>Security considerations:</dt><dd>See <xref target="security"/> of&SELF;</t> <t>Interoperability considerations: n/a</t> <t>Published specification: &SELF;</t> <t>ApplicationsRFC 9635.</dd> <dt>Interoperability considerations:</dt><dd>N/A</dd> <dt>Published specification:</dt><dd>RFC 9635</dd> <dt>Applications that use this mediatype: GNAP</t> <t>Fragmenttype:</dt><dd>GNAP</dd> <dt>Fragment identifierconsiderations: n/a</t> <t>Additional information: <list style="symbols"> <t>Magic number(s): n/a</t> <t>File extension(s): n/a</t> <t>Macintoshconsiderations:</dt><dd>N/A</dd> <dt>Additional information:</dt><dd> <t><br/></t> <dl spacing="compact"> <dt>Deprecated alias names for this type:</dt><dd>N/A</dd> <dt>Magic number(s):</dt><dd>N/A</dd> <dt>File extension(s):</dt><dd>N/A</dd> <dt>Macintosh file typecode(s): n/a</t> </list></t> <t>Personcode(s):</dt><dd>N/A</dd> </dl> </dd> <dt>Person & email address to contact for furtherinformation: IETFinformation:</dt><dd>IETF GNAP WorkingGroup, txauth@ietf.org</t> <t>Intended usage: COMMON</t> <t>Restrictions on usage: none</t> <t>Author: IETFGroup (txauth@ietf.org)</dd> <dt>Intended usage:</dt><dd>COMMON</dd> <dt>Restrictions on usage:</dt><dd>none</dd> <dt>Author:</dt><dd>IETF GNAP WorkingGroup, txauth@ietf.org</t> <t>Change Controller: IETF</t> <t>Provisional registration? No</t> </list></t> <t>To indicateGroup (txauth@ietf.org)</dd> <dt>Change Controller:</dt><dd>IETF</dd> </dl> </section> <section anchor="media-type-reg2"> <name>application/gnap-binding-jws</name> <t>This media type indicates that the content is a GNAP message to be bound with an attached JWSmechanism:</t> <t><list style="symbols"> <t>Type name: application</t> <t>Subtype name: gnap-binding-jws</t> <t>Required parameters: n/a</t> <t>Optional parameters: n/a</t> <t>Encoding considerations: binary</t> <t>Security considerations: Seemechanism.</t> <dl spacing="normal"> <dt>Type name:</dt><dd>application</dd> <dt>Subtype name:</dt><dd>gnap-binding-jws</dd> <dt>Required parameters:</dt><dd>N/A</dd> <dt>Optional parameters:</dt><dd>N/A</dd> <dt>Encoding considerations:</dt><dd>binary</dd> <dt>Security considerations:</dt><dd>See <xref target="security"/> of&SELF;</t> <t>Interoperability considerations: n/a</t> <t>Published specification: &SELF;</t> <t>ApplicationsRFC 9635.</dd> <dt>Interoperability considerations:</dt><dd>N/A</dd> <dt>Published specification:</dt><dd>RFC 9635</dd> <dt>Applications that use this mediatype: GNAP</t> <t>Fragmenttype:</dt><dd>GNAP</dd> <dt>Fragment identifierconsiderations: n/a</t> <t>Additional information: <list style="symbols"> <t>Magic number(s): n/a</t> <t>File extension(s): n/a</t> <t>Macintoshconsiderations:</dt><dd>N/A</dd> <dt>Additional information:</dt><dd> <t><br/></t> <dl spacing="compact"> <dt>Deprecated alias names for this type:</dt><dd>N/A</dd> <dt>Magic number(s):</dt><dd>N/A</dd> <dt>File extension(s):</dt><dd>N/A</dd> <dt>Macintosh file typecode(s): n/a</t> </list></t> <t>Personcode(s):</dt><dd>N/A</dd> </dl> </dd> <dt>Person & email address to contact for furtherinformation: IETFinformation:</dt><dd>IETF GNAP WorkingGroup, txauth@ietf.org</t> <t>Intended usage: COMMON</t> <t>Restrictions on usage: none</t> <t>Author: IETFGroup (txauth@ietf.org)</dd> <dt>Intended usage:</dt><dd>COMMON</dd> <dt>Restrictions on usage:</dt><dd>none</dd> <dt>Author:</dt><dd>IETF GNAP WorkingGroup, txauth@ietf.org</t> <t>Change Controller: IETF</t> <t>Provisional registration? No</t> </list></t> <t>To indicateGroup (txauth@ietf.org)</dd> <dt>Change Controller:</dt><dd>IETF</dd> </dl> </section> <section anchor="media-type-reg3"> <name>application/gnap-binding-rotation-jwsd</name> <t>This media type indicates that the content is a GNAP token rotation message to be bound with a detached JWSmechanism:</t> <t><list style="symbols"> <t>Type name: application</t> <t>Subtype name: gnap-binding-rotation-jwsd</t> <t>Required parameters: n/a</t> <t>Optional parameters: n/a</t> <t>Encoding considerations: binary</t> <t>Security considerations: Seemechanism.</t> <dl spacing="normal"> <dt>Type name:</dt><dd>application</dd> <dt>Subtype name:</dt><dd>gnap-binding-rotation-jwsd</dd> <dt>Required parameters:</dt><dd>N/A</dd> <dt>Optional parameters:</dt><dd>N/A</dd> <dt>Encoding considerations:</dt><dd>binary</dd> <dt>Security considerations:</dt><dd>See <xref target="security"/> of&SELF;</t> <t>Interoperability considerations: n/a</t> <t>Published specification: &SELF;</t> <t>ApplicationsRFC 9635.</dd> <dt>Interoperability considerations:</dt><dd>N/A</dd> <dt>Published specification:</dt><dd>RFC 9635</dd> <dt>Applications that use this mediatype: GNAP</t> <t>Fragmenttype:</dt><dd>GNAP</dd> <dt>Fragment identifierconsiderations: n/a</t> <t>Additional information: <list style="symbols"> <t>Magic number(s): n/a</t> <t>File extension(s): n/a</t> <t>Macintoshconsiderations:</dt><dd>N/A</dd> <dt>Additional information:</dt><dd> <t><br/></t> <dl spacing="compact"> <dt>Deprecated alias names for this type:</dt><dd>N/A</dd> <dt>Magic number(s):</dt><dd>N/A</dd> <dt>File extension(s):</dt><dd>N/A</dd> <dt>Macintosh file typecode(s): n/a</t> </list></t> <t>Personcode(s):</dt><dd>N/A</dd> </dl> </dd> <dt>Person & email address to contact for furtherinformation: IETFinformation:</dt><dd>IETF GNAP WorkingGroup, txauth@ietf.org</t> <t>Intended usage: COMMON</t> <t>Restrictions on usage: none</t> <t>Author: IETFGroup (txauth@ietf.org)</dd> <dt>Intended usage:</dt><dd>COMMON</dd> <dt>Restrictions on usage:</dt><dd>none</dd> <dt>Author:</dt><dd>IETF GNAP WorkingGroup, txauth@ietf.org</t> <t>Change Controller: IETF</t> <t>Provisional registration? No</t> </list></t> <t>To indicateGroup (txauth@ietf.org)</dd> <dt>Change Controller:</dt><dd>IETF</dd> </dl> </section> <section anchor="media-type-reg4"> <name>application/gnap-binding-rotation-jws</name> <t>This media type indicates that the content is a GNAP token rotation message to be bound with an attached JWSmechanism:</t> <t><list style="symbols"> <t>Type name: application</t> <t>Subtype name: gnap-binding-rotation-jws</t> <t>Required parameters: n/a</t> <t>Optional parameters: n/a</t> <t>Encoding considerations: binary</t> <t>Security considerations: Seemechanism.</t> <dl spacing="normal"> <dt>Type name:</dt><dd>application</dd> <dt>Subtype name:</dt><dd>gnap-binding-rotation-jws</dd> <dt>Required parameters:</dt><dd>N/A</dd> <dt>Optional parameters:</dt><dd>N/A</dd> <dt>Encoding considerations:</dt><dd>binary</dd> <dt>Security considerations:</dt><dd>See <xref target="security"/> of&SELF;</t> <t>Interoperability considerations: n/a</t> <t>Published specification: &SELF;</t> <t>ApplicationsRFC 9635.</dd> <dt>Interoperability considerations:</dt><dd>N/A</dd> <dt>Published specification:</dt><dd>RFC 9635</dd> <dt>Applications that use this mediatype: GNAP</t> <t>Fragmenttype:</dt><dd>GNAP</dd> <dt>Fragment identifierconsiderations: n/a</t> <t>Additional information: <list style="symbols"> <t>Magic number(s): n/a</t> <t>File extension(s): n/a</t> <t>Macintoshconsiderations:</dt><dd>N/A</dd> <dt>Additional information:</dt><dd> <t><br/></t> <dl spacing="compact"> <dt>Deprecated alias names for this type:</dt><dd>N/A</dd> <dt>Magic number(s):</dt><dd>N/A</dd> <dt>File extension(s):</dt><dd>N/A</dd> <dt>Macintosh file typecode(s): n/a</t> </list></t> <t>Personcode(s):</dt><dd>N/A</dd> </dl> </dd> <dt>Person & email address to contact for furtherinformation: IETFinformation:</dt><dd>IETF GNAP WorkingGroup, txauth@ietf.org</t> <t>Intended usage: COMMON</t> <t>Restrictions on usage: none</t> <t>Author: IETFGroup (txauth@ietf.org)</dd> <dt>Intended usage:</dt><dd>COMMON</dd> <dt>Restrictions on usage:</dt><dd>none</dd> <dt>Author:</dt><dd>IETF GNAP WorkingGroup, txauth@ietf.org</t> <t>Change Controller: IETF</t> <t>Provisional registration? No</t> </list></t>Group (txauth@ietf.org)</dd> <dt>Change Controller:</dt><dd>IETF</dd> </dl> </section> </section> <sectionanchor="IANA-grant-request"><name>GNAPanchor="IANA-grant-request"> <name>GNAP Grant Request Parameters</name> <t>This document defines a GNAP grant request, for which IANAis asked to createhas created andmaintainmaintains a new registry titled "GNAP Grant Request Parameters". Initial values for this registry are given in <xref target="IANA-grant-request-contents"/>. Future assignments and modifications to existingassignmentassignments are to be made through the Specification Required registration policy <xref target="RFC8126"/>.</t> <!-- [rfced] IANA Flag: For alignment with the IANA registry, would it be appropriate to change "Specification document(s)" to "Reference(s)" in the descriptions and the column headers throughout Section 10? Example from Section 10.3.1: Specification document(s): Reference to the document(s) that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required. --> <t>TheDesignated Expertdesignated expert (DE) is expected to ensure that all registrations follow the template presented in <xref target="IANA-grant-request-template"/>. The DE is expected to ensure that the request parameter's definition is sufficiently orthogonal to existing functionality provided by existing parameters. The DE is expected to ensure that registrations for the same name with different types are sufficiently close in functionality so as not to cause confusion for developers. The DE is expected to ensure that the request parameter's definition specifies the expected behavior of the AS in response to the request parameter for each potential state of the grant request.</t> <sectionanchor="IANA-grant-request-template"><name>Registrationanchor="IANA-grant-request-template"> <name>Registration Template</name> <dl newline="true"> <dt>Name:</dt> <dd> <t>An identifier for the parameter.</t> </dd> <dt>Type:</dt> <dd> <t>The JSON type allowed for the value.</t> </dd> <dt>Specification document(s):</dt> <dd> <t>Reference tothe document(s)one or more documents that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required.</t> </dd> </dl> </section> <sectionanchor="IANA-grant-request-contents"><name>Initialanchor="IANA-grant-request-contents"> <name>Initial Contents</name><texttable> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Type</ttcol> <ttcol align='left'>Specification document(s)</ttcol> <c>access_token</c> <c>object</c> <c><xref<table> <thead> <tr> <th align="left">Name</th> <th align="left">Type</th> <th align="left">Specification document(s)</th> </tr> </thead> <tbody> <tr> <td align="left">access_token</td> <td align="left">object</td> <td align="left"> <xref target="request-token-single"/> of&SELF;</c> <c>access_token</c> <c>array of objects</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">access_token</td> <td align="left">array of objects</td> <td align="left"> <xref target="request-token-multiple"/> of&SELF;</c> <c>subject</c> <c>object</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">subject</td> <td align="left">object</td> <td align="left"> <xref target="request-subject"/> of&SELF;</c> <c>client</c> <c>object</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">client</td> <td align="left">object</td> <td align="left"> <xref target="request-client"/> of&SELF;</c> <c>client</c> <c>string</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">client</td> <td align="left">string</td> <td align="left"> <xref target="request-instance"/> of&SELF;</c> <c>user</c> <c>object</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">user</td> <td align="left">object</td> <td align="left"> <xref target="request-user"/> of&SELF;</c> <c>user</c> <c>string</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">user</td> <td align="left">string</td> <td align="left"> <xref target="request-user-reference"/> of&SELF;</c> <c>interact</c> <c>object</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">interact</td> <td align="left">object</td> <td align="left"> <xref target="request-interact"/> of&SELF;</c> <c>interact_ref</c> <c>string</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">interact_ref</td> <td align="left">string</td> <td align="left"> <xref target="continue-after-interaction"/> of&SELF;</c> </texttable>RFC 9635</td> </tr> </tbody> </table> </section> </section> <sectionanchor="IANA-token-flags"><name>GNAPanchor="IANA-token-flags"> <name>GNAP Access Token Flags</name> <t>This document definesaGNAP access token flags, for which IANAis asked to createhas created andmaintainmaintains a new registry titled "GNAP Access Token Flags". Initial values for this registry are given in <xref target="IANA-token-flags-contents"/>. Future assignments and modifications to existingassignmentassignments are to be made through the Specification Required registration policy <xref target="RFC8126"/>.</t> <t>The DE is expected to ensure that all registrations follow the template presented in <xref target="IANA-token-flags-template"/>. The DE is expected to ensure that the flag specifies whether it applies to requests for tokens to the AS, responses with tokens from the AS, or both.</t> <sectionanchor="IANA-token-flags-template"><name>Registrationanchor="IANA-token-flags-template"> <name>Registration Template</name> <dl newline="true"> <dt>Name:</dt> <dd> <t>An identifier for the parameter.</t> </dd> <dt>Allowed Use:</dt> <dd> <t>Where the flag is allowed to occur. Possible values are "Request", "Response", and "Request, Response".</t> </dd> <dt>Specification document(s):</dt> <dd> <t>Reference tothe document(s)one or more documents that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required.</t> </dd> </dl> </section> <sectionanchor="IANA-token-flags-contents"><name>Initialanchor="IANA-token-flags-contents"> <name>Initial Contents</name><texttable> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Allowed Use</ttcol> <ttcol align='left'>Specification document(s)</ttcol> <c>bearer</c> <c>Request, Response</c> <c><xref target="request-token-single"/><table> <thead> <tr> <th align="left">Name</th> <th align="left">Allowed Use</th> <th align="left">Specification document(s)</th> </tr> </thead> <tbody> <tr> <td align="left">bearer</td> <td align="left">Request, Response</td> <td align="left"> Sections <xref target="request-token-single" format="counter"/> and <xreftarget="response-token-single"/>target="response-token-single" format="counter"/> of&SELF;</c> <c>durable</c> <c>Response</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">durable</td> <td align="left">Response</td> <td align="left"> <xref target="response-token-single"/> of&SELF;</c> </texttable>RFC 9635</td> </tr> </tbody> </table> </section> </section> <sectionanchor="IANA-subject-request"><name>GNAPanchor="IANA-subject-request"> <name>GNAP Subject Information Request Fields</name> <t>This document defines a means to request subject information from the AS to the client instance, for which IANAis asked to createhas created andmaintainmaintains a new registry titled "GNAP Subject Information Request Fields". Initial values for this registry are given in <xref target="IANA-subject-request-contents"/>. Future assignments and modifications to existingassignmentassignments are to be made through the Specification Required registration policy <xref target="RFC8126"/>.</t> <t>The DE is expected to ensure that all registrations follow the template presented in <xref target="IANA-subject-request-template"/>. The DE is expected to ensure that registrations for the same name with different types are sufficiently close in functionality so as not to cause confusion for developers.</t> <sectionanchor="IANA-subject-request-template"><name>Registrationanchor="IANA-subject-request-template"> <name>Registration Template</name> <dl newline="true"> <dt>Name:</dt> <dd> <t>An identifier for the parameter.</t> </dd> <dt>Type:</dt> <dd> <t>The JSON type allowed for the value.</t> </dd> <dt>Specification document(s):</dt> <dd> <t>Reference tothe document(s)one or more documents that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required.</t> </dd> </dl> </section> <sectionanchor="IANA-subject-request-contents"><name>Initialanchor="IANA-subject-request-contents"> <name>Initial Contents</name><texttable> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Type</ttcol> <ttcol align='left'>Specification document(s)</ttcol> <c>sub_id_formats</c> <c>array of strings</c> <c><xref<table> <thead> <tr> <th align="left">Name</th> <th align="left">Type</th> <th align="left">Specification document(s)</th> </tr> </thead> <tbody> <tr> <td align="left">sub_id_formats</td> <td align="left">array of strings</td> <td align="left"> <xref target="request-subject"/> of&SELF;</c> <c>assertion_formats</c> <c>array of strings</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">assertion_formats</td> <td align="left">array of strings</td> <td align="left"> <xref target="request-subject"/> of&SELF;</c> <c>sub_ids</c> <c>array of objects</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">sub_ids</td> <td align="left">array of objects</td> <td align="left"> <xref target="request-subject"/> of&SELF;</c> </texttable>RFC 9635</td> </tr> </tbody> </table> </section> </section> <sectionanchor="IANA-assertion-formats"><name>GNAPanchor="IANA-assertion-formats"> <name>GNAP Assertion Formats</name> <t>This document defines a means to pass identity assertions between the AS and client instance, for which IANAis asked to createhas created andmaintainmaintains a new registry titled "GNAP Assertion Formats". Initial values for this registry are given in <xref target="IANA-assertion-formats-contents"/>. Future assignments and modifications to existingassignmentassignments are to be made through the Specification Required registration policy <xref target="RFC8126"/>.</t> <t>The DE is expected to ensure that all registrations follow the template presented in <xref target="IANA-assertion-formats-template"/>. The DE is expected to ensure that the definition specifies the serialization format of the assertion value as used within GNAP.</t> <sectionanchor="IANA-assertion-formats-template"><name>Registrationanchor="IANA-assertion-formats-template"> <name>Registration Template</name> <dl newline="true"> <dt>Name:</dt> <dd> <t>An identifier for the assertion format.</t> </dd> <dt>Specification document(s):</dt> <dd> <t>Reference tothe document(s)one or more documents that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required.</t> </dd> </dl> </section> <sectionanchor="IANA-assertion-formats-contents"><name>Initialanchor="IANA-assertion-formats-contents"> <name>Initial Contents</name><texttable> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Specification document(s)</ttcol> <c>id_token</c> <c><xref<table> <thead> <tr> <th align="left">Name</th> <th align="left">Specification document(s)</th> </tr> </thead> <tbody> <tr> <td align="left">id_token</td> <td align="left"> <xref target="assertion-formats"/> of&SELF;</c> <c>saml2</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">saml2</td> <td align="left"> <xref target="assertion-formats"/> of&SELF;</c> </texttable>RFC 9635</td> </tr> </tbody> </table> </section> </section> <sectionanchor="IANA-client-instance"><name>GNAPanchor="IANA-client-instance"> <name>GNAP Client Instance Fields</name> <t>This document defines a means to send information about the client instance, for which IANAis asked to createhas created andmaintainmaintains a new registry titled "GNAP Client Instance Fields". Initial values for this registry are given in <xref target="IANA-client-instance-contents"/>. Future assignments and modifications to existingassignmentassignments are to be made through the Specification Required registration policy <xref target="RFC8126"/>.</t> <t>The DE is expected to ensure that all registrations follow the template presented in <xref target="IANA-client-instance-template"/>. The DE is expected to ensure that registrations for the same name with different types are sufficiently close in functionality so as not to cause confusion for developers.</t> <sectionanchor="IANA-client-instance-template"><name>Registrationanchor="IANA-client-instance-template"> <name>Registration Template</name> <dl newline="true"> <dt>Name:</dt> <dd> <t>An identifier for the parameter.</t> </dd> <dt>Type:</dt> <dd> <t>The JSON type allowed for the value.</t> </dd> <dt>Specification document(s):</dt> <dd> <t>Reference tothe document(s)one or more documents that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required.</t> </dd> </dl> </section> <sectionanchor="IANA-client-instance-contents"><name>Initialanchor="IANA-client-instance-contents"> <name>Initial Contents</name><texttable> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Type</ttcol> <ttcol align='left'>Specification document(s)</ttcol> <c>key</c> <c>object</c> <c><xref<table> <thead> <tr> <th align="left">Name</th> <th align="left">Type</th> <th align="left">Specification document(s)</th> </tr> </thead> <tbody> <tr> <td align="left">key</td> <td align="left">object</td> <td align="left"> <xref target="key-format"/> of&SELF;</c> <c>key</c> <c>string</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">key</td> <td align="left">string</td> <td align="left"> <xref target="key-reference"/> of&SELF;</c> <c>class_id</c> <c>string</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">class_id</td> <td align="left">string</td> <td align="left"> <xref target="request-client"/> of&SELF;</c> <c>display</c> <c>object</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">display</td> <td align="left">object</td> <td align="left"> <xref target="request-display"/> of&SELF;</c> </texttable>RFC 9635</td> </tr> </tbody> </table> </section> </section> <sectionanchor="IANA-client-instance-display"><name>GNAPanchor="IANA-client-instance-display"> <name>GNAP Client Instance Display Fields</name> <t>This document defines a means to sendend-user facingend-user-facing displayable information about the client instance, for which IANAis asked to createhas created andmaintainmaintains a new registry titled "GNAP Client Instance Display Fields". Initial values for this registry are given in <xref target="IANA-client-instance-display-contents"/>. Future assignments and modifications to existingassignmentassignments are to be made through the Specification Required registration policy <xref target="RFC8126"/>.</t> <t>The DE is expected to ensure that all registrations follow the template presented in <xref target="IANA-client-instance-display-template"/>. The DE is expected to ensure that registrations for the same name with different types are sufficiently close in functionality so as not to cause confusion for developers.</t> <sectionanchor="IANA-client-instance-display-template"><name>Registrationanchor="IANA-client-instance-display-template"> <name>Registration Template</name> <dl newline="true"> <dt>Name:</dt> <dd> <t>An identifier for the parameter.</t> </dd> <dt>Type:</dt> <dd> <t>The JSON type allowed for the value.</t> </dd> <dt>Specification document(s):</dt> <dd> <t>Reference tothe document(s)one or more documents that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required.</t> </dd> </dl> </section> <sectionanchor="IANA-client-instance-display-contents"><name>Initialanchor="IANA-client-instance-display-contents"> <name>Initial Contents</name><texttable> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Type</ttcol> <ttcol align='left'>Specification document(s)</ttcol> <c>name</c> <c>string</c> <c><xref<table> <thead> <tr> <th align="left">Name</th> <th align="left">Type</th> <th align="left">Specification document(s)</th> </tr> </thead> <tbody> <tr> <td align="left">name</td> <td align="left">string</td> <td align="left"> <xref target="request-display"/> of&SELF;</c> <c>uri</c> <c>string</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">uri</td> <td align="left">string</td> <td align="left"> <xref target="request-display"/> of&SELF;</c> <c>logo_uri</c> <c>string</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">logo_uri</td> <td align="left">string</td> <td align="left"> <xref target="request-display"/> of&SELF;</c> </texttable>RFC 9635</td> </tr> </tbody> </table> </section> </section> <sectionanchor="IANA-interaction-start-modes"><name>GNAPanchor="IANA-interaction-start-modes"> <name>GNAP Interaction Start Modes</name> <t>This document defines a means for the client instance to begin interaction between theend-userend user and the AS, for which IANAis asked to createhas created andmaintainmaintains a new registry titled "GNAP Interaction Start Modes". Initial values for this registry are given in <xref target="IANA-interaction-start-modes-contents"/>. Future assignments and modifications to existingassignmentassignments are to be made through the Specification Required registration policy <xref target="RFC8126"/>.</t> <t>The DE is expected to ensure that all registrations follow the template presented in <xref target="IANA-interaction-start-modes-template"/>. The DE is expected to ensure that registrations for the same name with different types are sufficiently close in functionality so as not to cause confusion for developers. The DE is expected to ensure that any registration using an "object" type declares all additional parameters, their optionality, and their purpose. The DE is expected to ensure that the start mode clearly defines what actions the client is expected to take to begin interaction, what the expected user experience is, and any security considerations for this communication from either party. The DE is expected to ensure that the start mode documents incompatibilities with other start modes or finish methods, if applicable. The DE is expected to ensure that the start mode provides enough information to uniquely identify the grant request during the interaction. For example,tnin the<spanx style="verb">redirect</spanx><tt>redirect</tt> and<spanx style="verb">app</spanx><tt>app</tt> modes, this is done using a unique URI (including its parameters). In the<spanx style="verb">user_code</spanx><tt>user_code</tt> and<spanx style="verb">user_code_uri</spanx> mode,<tt>user_code_uri</tt> modes, this is done using the value of the user code.</t> <sectionanchor="IANA-interaction-start-modes-template"><name>Registrationanchor="IANA-interaction-start-modes-template"> <name>Registration Template</name> <dl newline="true"> <dt>Mode:</dt> <dd> <t>An identifier for the interaction start mode.</t> </dd> <dt>Type:</dt> <dd> <t>The JSON type for the value, either "string" or "object", as described in <xref target="request-interact-start"/>.</t> </dd> <dt>Specification document(s):</dt> <dd> <t>Reference tothe document(s)one or more documents that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required.</t> </dd> </dl> </section> <sectionanchor="IANA-interaction-start-modes-contents"><name>Initialanchor="IANA-interaction-start-modes-contents"> <name>Initial Contents</name><texttable> <ttcol align='left'>Mode</ttcol> <ttcol align='left'>Type</ttcol> <ttcol align='left'>Specification document(s)</ttcol> <c>redirect</c> <c>string</c> <c><xref<table> <thead> <tr> <th align="left">Mode</th> <th align="left">Type</th> <th align="left">Specification document(s)</th> </tr> </thead> <tbody> <tr> <td align="left">redirect</td> <td align="left">string</td> <td align="left"> <xref target="request-interact-redirect"/> of&SELF;</c> <c>app</c> <c>string</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">app</td> <td align="left">string</td> <td align="left"> <xref target="request-interact-app"/> of&SELF;</c> <c>user_code</c> <c>string</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">user_code</td> <td align="left">string</td> <td align="left"> <xref target="request-interact-usercode"/> of&SELF;</c> <c>user_code_uri</c> <c>string</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">user_code_uri</td> <td align="left">string</td> <td align="left"> <xref target="request-interact-usercodeuri"/> of&SELF;</c> </texttable>RFC 9635</td> </tr> </tbody> </table> </section> </section> <sectionanchor="IANA-interaction-finish-methods"><name>GNAPanchor="IANA-interaction-finish-methods"> <name>GNAP Interaction Finish Methods</name> <t>This document defines a means for the client instance to be notified of the end of interaction between theend-userend user and the AS, for which IANAis asked to createhas created andmaintainmaintains a new registry titled "GNAP Interaction Finish Methods". Initial values for this registry are given in <xref target="IANA-interaction-finish-methods-contents"/>. Future assignments and modifications to existingassignmentassignments are to be made through the Specification Required registration policy <xref target="RFC8126"/>.</t> <t>The DE is expected to ensure that all registrations follow the template presented in <xref target="IANA-interaction-finish-methods-template"/>. The DE is expected to ensure that all finish methods clearly define what actions the AS is expected to take, what listening methods the client instance needs to enable, and any security considerations for this communication from either party. The DE is expected to ensure that all finish methods document incompatibilities with any start modes, if applicable.</t> <sectionanchor="IANA-interaction-finish-methods-template"><name>Registrationanchor="IANA-interaction-finish-methods-template"> <name>Registration Template</name> <dl newline="true"><dt>Method:</dt><dt>Mode:</dt> <dd> <t>An identifier for the interaction finish method.</t> </dd> <dt>Specification document(s):</dt> <dd> <t>Reference tothe document(s)one or more documents that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required.</t> </dd> </dl> </section> <sectionanchor="IANA-interaction-finish-methods-contents"><name>Initialanchor="IANA-interaction-finish-methods-contents"> <name>Initial Contents</name><texttable> <ttcol align='left'>Mode</ttcol> <ttcol align='left'>Specification document(s)</ttcol> <c>redirect</c> <c><xref<table> <thead> <tr> <th align="left">Mode</th> <th align="left">Specification document(s)</th> </tr> </thead> <tbody> <tr> <td align="left">redirect</td> <td align="left"> <xref target="request-interact-callback-redirect"/> of&SELF;</c> <c>push</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">push</td> <td align="left"> <xref target="request-interact-callback-push"/> of&SELF;</c> </texttable>RFC 9635</td> </tr> </tbody> </table> </section> </section> <sectionanchor="IANA-interaction-hints"><name>GNAPanchor="IANA-interaction-hints"> <name>GNAP Interaction Hints</name> <t>This document defines a set of hints that a client instance can provide to the AS to facilitate interaction with the end user, for which IANAis asked to createhas created andmaintainmaintains a new registry titled "GNAP Interaction Hints". Initial values for this registry are given in <xref target="IANA-interaction-hints-contents"/>. Future assignments and modifications to existingassignmentassignments are to be made through the Specification Required registration policy <xref target="RFC8126"/>.</t> <t>The DE is expected to ensure that all registrations follow the template presented in <xref target="IANA-interaction-hints-template"/>. The DE is expected to ensure that all interaction hints clearly document the expected behaviors of the AS in response to thehint,hint and that an AS not processing the hint does not impede the operation of the AS or client instance.</t> <sectionanchor="IANA-interaction-hints-template"><name>Registrationanchor="IANA-interaction-hints-template"> <name>Registration Template</name> <dl newline="true"><dt>Name:</dt><dt>Mode:</dt> <dd> <t>An identifier for the parameter.</t> </dd> <dt>Specification document(s):</dt> <dd> <t>Reference tothe document(s)one or more documents that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required.</t> </dd> </dl> </section> <sectionanchor="IANA-interaction-hints-contents"><name>Initialanchor="IANA-interaction-hints-contents"> <name>Initial Contents</name><texttable> <ttcol align='left'>Mode</ttcol> <ttcol align='left'>Specification document(s)</ttcol> <c>ui_locales</c> <c><xref<table> <thead> <tr> <th align="left">Mode</th> <th align="left">Specification document(s)</th> </tr> </thead> <tbody> <tr> <td align="left">ui_locales</td> <td align="left"> <xref target="request-interact-hint"/> of&SELF;</c> </texttable>RFC 9635</td> </tr> </tbody> </table> </section> </section> <sectionanchor="IANA-grant-response"><name>GNAPanchor="IANA-grant-response"> <name>GNAP Grant Response Parameters</name> <t>This document defines a GNAP grant response, for which IANAis asked to createhas created andmaintainmaintains a new registry titled "GNAP Grant Response Parameters". Initial values for this registry are given in <xref target="IANA-grant-response-contents"/>. Future assignments and modifications to existingassignmentassignments are to be made through the Specification Required registration policy <xref target="RFC8126"/>.</t> <t>The DE is expected to ensure that all registrations follow the template presented in <xref target="IANA-grant-response-template"/>. The DE is expected to ensure that the response parameter's definition is sufficiently orthogonal to existing functionality provided by existing parameters. The DE is expected to ensure that registrations for the same name with different types are sufficiently close in functionality so as not to cause confusion for developers. The DE is expected to ensure that the response parameter's definition specifies grant states for which the client instance can expect this parameter to appear in a response message.</t> <sectionanchor="IANA-grant-response-template"><name>Registrationanchor="IANA-grant-response-template"> <name>Registration Template</name> <dl newline="true"> <dt>Name:</dt> <dd> <t>An identifier for the parameter.</t> </dd> <dt>Type:</dt> <dd> <t>The JSON type allowed for the value.</t> </dd> <dt>Specification document(s):</dt> <dd> <t>Reference tothe document(s)one or more documents that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required.</t> </dd> </dl> </section> <sectionanchor="IANA-grant-response-contents"><name>Initialanchor="IANA-grant-response-contents"> <name>Initial Contents</name><texttable> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Type</ttcol> <ttcol align='left'>Specification document(s)</ttcol> <c>continue</c> <c>object</c> <c><xref<table> <thead> <tr> <th align="left">Name</th> <th align="left">Type</th> <th align="left">Specification document(s)</th> </tr> </thead> <tbody> <tr> <td align="left">continue</td> <td align="left">object</td> <td align="left"> <xref target="response-continue"/> of&SELF;</c> <c>acces_token</c> <c>object</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">acces_token</td> <td align="left">object</td> <td align="left"> <xref target="response-token-single"/> of&SELF;</c> <c>acces_token</c> <c>array of objects</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">acces_token</td> <td align="left">array of objects</td> <td align="left"> <xref target="response-token-multiple"/> of&SELF;</c> <c>interact</c> <c>object</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">interact</td> <td align="left">object</td> <td align="left"> <xref target="response-interact"/> of&SELF;</c> <c>subject</c> <c>object</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">subject</td> <td align="left">object</td> <td align="left"> <xref target="response-subject"/> of&SELF;</c> <c>instance_id</c> <c>string</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">instance_id</td> <td align="left">string</td> <td align="left"> <xref target="response-dynamic-handles"/> of&SELF;</c> <c>error</c> <c>object</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">error</td> <td align="left">object</td> <td align="left"> <xref target="response-error"/> of&SELF;</c> </texttable>RFC 9635</td> </tr> </tbody> </table> </section> </section> <sectionanchor="IANA-interaction-response"><name>GNAPanchor="IANA-interaction-response"> <name>GNAP Interaction Mode Responses</name> <t>This document defines a means for the AS to providetothe client instance with information that is required to complete a particular interaction mode, for which IANAis asked to createhas created andmaintainmaintains a new registry titled "GNAP Interaction Mode Responses". Initial values for this registry are given in <xref target="IANA-interaction-response-contents"/>. Future assignments and modifications to existingassignmentassignments are to be made through the Specification Required registration policy <xref target="RFC8126"/>.</t> <t>The DE is expected to ensure that all registrations follow the template presented in <xref target="IANA-interaction-response-template"/>. If the name of the registration matches the name of an interaction start mode, the DE is expected to ensure that the response parameter is unambiguously associated with the interaction start mode of the same name.</t> <sectionanchor="IANA-interaction-response-template"><name>Registrationanchor="IANA-interaction-response-template"> <name>Registration Template</name> <dl newline="true"> <dt>Name:</dt> <dd> <t>An identifier for the parameter.</t> </dd> <dt>Specification document(s):</dt> <dd> <t>Reference tothe document(s)one or more documents that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required.</t> </dd> </dl> </section> <sectionanchor="IANA-interaction-response-contents"><name>Initialanchor="IANA-interaction-response-contents"> <name>Initial Contents</name><texttable> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Specification document(s)</ttcol> <c>redirect</c> <c><xref<table> <thead> <tr> <th align="left">Name</th> <th align="left">Specification document(s)</th> </tr> </thead> <tbody> <tr> <td align="left">redirect</td> <td align="left"> <xref target="response-interact"/> of&SELF;</c> <c>app</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">app</td> <td align="left"> <xref target="response-interact"/> of&SELF;</c> <c>user_code</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">user_code</td> <td align="left"> <xref target="response-interact"/> of&SELF;</c> <c>user_code_uri</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">user_code_uri</td> <td align="left"> <xref target="response-interact"/> of&SELF;</c> <c>finish</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">finish</td> <td align="left"> <xref target="response-interact"/> of&SELF;</c> <c>expires_in</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">expires_in</td> <td align="left"> <xref target="response-interact"/> of&SELF;</c> </texttable>RFC 9635</td> </tr> </tbody> </table> </section> </section> <sectionanchor="IANA-subject-response"><name>GNAPanchor="IANA-subject-response"> <name>GNAP Subject Information Response Fields</name> <t>This document defines a means to return subject information from the AS to the client instance, for which IANAis asked to createhas created andmaintainmaintains a new registry titled "GNAP Subject Information Response Fields". Initial values for this registry are given in <xref target="IANA-subject-response-contents"/>. Future assignments and modifications to existingassignmentassignments are to be made through the Specification Required registration policy <xref target="RFC8126"/>.</t> <t>The DE is expected to ensure that all registrations follow the template presented in <xref target="IANA-subject-response-template"/>. The DE is expected to ensure that registrations for the same name with different types are sufficiently close in functionality so as not to cause confusion for developers.</t> <sectionanchor="IANA-subject-response-template"><name>Registrationanchor="IANA-subject-response-template"> <name>Registration Template</name> <dl newline="true"> <dt>Name:</dt> <dd> <t>An identifier for the parameter.</t> </dd> <dt>Type:</dt> <dd> <t>The JSON type allowed for the value.</t> </dd> <dt>Specification document(s):</dt> <dd> <t>Reference tothe document(s)one or more documents that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required.</t> </dd> </dl> </section> <sectionanchor="IANA-subject-response-contents"><name>Initialanchor="IANA-subject-response-contents"> <name>Initial Contents</name><texttable> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Type</ttcol> <ttcol align='left'>Specification document(s)</ttcol> <c>sub_ids</c> <c>array of objects</c> <c><xref<table> <thead> <tr> <th align="left">Name</th> <th align="left">Type</th> <th align="left">Specification document(s)</th> </tr> </thead> <tbody> <tr> <td align="left">sub_ids</td> <td align="left">array of objects</td> <td align="left"> <xref target="response-subject"/> of&SELF;</c> <c>assertions</c> <c>array of objects</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">assertions</td> <td align="left">array of objects</td> <td align="left"> <xref target="response-subject"/> of&SELF;</c> <c>updated_at</c> <c>string</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">updated_at</td> <td align="left">string</td> <td align="left"> <xref target="response-subject"/> of&SELF;</c> </texttable>RFC 9635</td> </tr> </tbody> </table> </section> </section> <sectionanchor="IANA-error-code"><name>GNAPanchor="IANA-error-code"> <name>GNAP Error Codes</name> <t>This document defines a set of errors that the AS can return to the client instance, for which IANAis asked to createhas created andmaintainmaintains a new registry titled "GNAP Error Codes". Initial values for this registry are given in <xref target="IANA-error-code-contents"/>. Future assignments and modifications to existingassignmentassignments are to be made through the Specification Required registration policy <xref target="RFC8126"/>.</t> <t>The DE is expected to ensure that all registrations follow the template presented in <xref target="IANA-error-code-template"/>. The DE is expected to ensure that the error response is sufficiently unique from other errors to provide actionable information to the client instance. The DE is expected to ensure that the definition of the error response specifies all conditions in which the error response isreturned,returned andwhatthe client instance's expectedaction is.</t>action.</t> <sectionanchor="IANA-error-code-template"><name>Registrationanchor="IANA-error-code-template"> <name>Registration Template</name> <dl newline="true"> <dt>Error:</dt> <dd> <t>A unique string code for the error.</t> </dd> <dt>Specification document(s):</dt> <dd> <t>Reference tothe document(s)one or more documents that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required.</t> </dd> </dl> </section> <!-- [rfced] IANA FLAG: Table 13 includes a list of items from Section 3.6 ("Error Response") but does not include "unknown_user" from that list. We also do not see "unknown_user" in the "GNAP Error Codes" registry at https://www.iana.org/assignments/gnap/gnap.xhtml. Please review and let us know if updates are needed. --> <sectionanchor="IANA-error-code-contents"><name>Initialanchor="IANA-error-code-contents"> <name>Initial Contents</name><texttable> <ttcol align='left'>Error</ttcol> <ttcol align='left'>Specification document(s)</ttcol> <c>invalid_request</c> <c><xref<table> <thead> <tr> <th align="left">Error</th> <th align="left">Specification document(s)</th> </tr> </thead> <tbody> <tr> <td align="left">invalid_request</td> <td align="left"> <xref target="response-error"/> of&SELF;</c> <c>invalid_client</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">invalid_client</td> <td align="left"> <xref target="response-error"/> of&SELF;</c> <c>invalid_interaction</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">invalid_interaction</td> <td align="left"> <xref target="response-error"/> of&SELF;</c> <c>invalid_flag</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">invalid_flag</td> <td align="left"> <xref target="response-error"/> of&SELF;</c> <c>invalid_rotation</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">invalid_rotation</td> <td align="left"> <xref target="response-error"/> of&SELF;</c> <c>key_rotation_not_supported</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">key_rotation_not_supported</td> <td align="left"> <xref target="response-error"/> of&SELF;</c> <c>invalid_continuation</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">invalid_continuation</td> <td align="left"> <xref target="response-error"/> of&SELF;</c> <c>user_denied</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">user_denied</td> <td align="left"> <xref target="response-error"/> of&SELF;</c> <c>request_denied</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">request_denied</td> <td align="left"> <xref target="response-error"/> of&SELF;</c> <c>unknown_interaction</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">unknown_interaction</td> <td align="left"> <xref target="response-error"/> of&SELF;</c> <c>too_fast</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">too_fast</td> <td align="left"> <xref target="response-error"/> of&SELF;</c> <c>too_many_attempts</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">too_many_attempts</td> <td align="left"> <xref target="response-error"/> of&SELF;</c> </texttable>RFC 9635</td> </tr> </tbody> </table> </section> </section> <sectionanchor="IANA-key-proof-methods"><name>GNAPanchor="IANA-key-proof-methods"> <name>GNAP Key Proofing Methods</name> <t>This document defines methods that the client instance can use to prove possession of a key, for which IANAis asked to createhas created andmaintainmaintains a new registry titled "GNAP Key Proofing Methods". Initial values for this registry are given in <xref target="IANA-key-proof-methods-contents"/>. Future assignments and modifications to existingassignmentassignments are to be made through the Specification Required registration policy <xref target="RFC8126"/>.</t> <t>The DE is expected to ensure that all registrations follow the template presented in <xref target="IANA-key-proof-methods-template"/>. The DE is expected to ensure that registrations for the same name with different types are sufficiently close in functionality so as not to cause confusion for developers. The DE is expected to ensure that the proofing method provides sufficient coverage of and binding to the protocol messages to which it is applied. The DE is expected to ensure that the proofing method definition clearly enumerates how all requirements in <xref target="binding-keys"/> are fulfilled by the definition.</t> <sectionanchor="IANA-key-proof-methods-template"><name>Registrationanchor="IANA-key-proof-methods-template"> <name>Registration Template</name> <dl newline="true"> <dt>Method:</dt> <dd> <t>A unique string code for the key proofing method.</t> </dd> <dt>Type:</dt> <dd> <t>The JSON type allowed for the value.</t> </dd> <dt>Specification document(s):</dt> <dd> <t>Reference tothe document(s)one or more documents that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required.</t> </dd> </dl> </section> <sectionanchor="IANA-key-proof-methods-contents"><name>Initialanchor="IANA-key-proof-methods-contents"> <name>Initial Contents</name><texttable> <ttcol align='left'>Method</ttcol> <ttcol align='left'>Type</ttcol> <ttcol align='left'>Specification document(s)</ttcol> <c>httpsig</c> <c>string</c> <c><xref<table> <thead> <tr> <th align="left">Method</th> <th align="left">Type</th> <th align="left">Specification document(s)</th> </tr> </thead> <tbody> <tr> <td align="left">httpsig</td> <td align="left">string</td> <td align="left"> <xref target="httpsig-binding"/> of&SELF;</c> <c>httpsig</c> <c>object</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">httpsig</td> <td align="left">object</td> <td align="left"> <xref target="httpsig-binding"/> of&SELF;</c> <c>mtls</c> <c>string</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">mtls</td> <td align="left">string</td> <td align="left"> <xref target="mtls"/> of&SELF;</c> <c>jwsd</c> <c>string</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">jwsd</td> <td align="left">string</td> <td align="left"> <xref target="detached-jws"/> of&SELF;</c> <c>jws</c> <c>string</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">jws</td> <td align="left">string</td> <td align="left"> <xref target="attached-jws"/> of&SELF;</c> </texttable>RFC 9635</td> </tr> </tbody> </table> </section> </section> <sectionanchor="IANA-key-formats"><name>GNAPanchor="IANA-key-formats"> <name>GNAP Key Formats</name> <t>This document defines formats for a public key value, for which IANAis asked to createhas created andmaintainmaintains a new registry titled "GNAP Key Formats". Initial values for this registry are given in <xref target="IANA-key-formats-contents"/>. Future assignments and modifications to existingassignmentassignments are to be made through the Specification Required registration policy <xref target="RFC8126"/>.</t> <t>The DE is expected to ensure that all registrations follow the template presented in <xref target="IANA-key-formats-template"/>. The DE is expected to ensure that the key format specifies the structure and serialization of the key material.</t> <sectionanchor="IANA-key-formats-template"><name>Registrationanchor="IANA-key-formats-template"> <name>Registration Template</name> <dl newline="true"> <dt>Format:</dt> <dd> <t>A unique string code for the key format.</t> </dd> <dt>Specification document(s):</dt> <dd> <t>Reference tothe document(s)one or more documents that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required.</t> </dd> </dl> </section> <sectionanchor="IANA-key-formats-contents"><name>Initialanchor="IANA-key-formats-contents"> <name>Initial Contents</name><texttable> <ttcol align='left'>Format</ttcol> <ttcol align='left'>Specification document(s)</ttcol> <c>jwk</c> <c><xref<table> <thead> <tr> <th align="left">Format</th> <th align="left">Specification document(s)</th> </tr> </thead> <tbody> <tr> <td align="left">jwk</td> <td align="left"> <xref target="key-format"/> of&SELF;</c> <c>cert</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">cert</td> <td align="left"> <xref target="key-format"/> of&SELF;</c> <c>cert#S256</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">cert#S256</td> <td align="left"> <xref target="key-format"/> of&SELF;</c> </texttable>RFC 9635</td> </tr> </tbody> </table> </section> </section> <sectionanchor="IANA-as-discovery"><name>GNAPanchor="IANA-as-discovery"> <name>GNAP Authorization Server Discovery Fields</name> <t>This document defines a discovery document for an AS, for which IANAis asked to createhas created andmaintainmaintains a new registry titled "GNAP Authorization Server Discovery Fields". Initial values for this registry are given in <xref target="IANA-as-discovery-contents"/>. Future assignments and modifications to existingassignmentassignments are to be made through the Specification Required registration policy <xref target="RFC8126"/>.</t> <t>The DE is expected to ensure that all registrations follow the template presented in <xref target="IANA-as-discovery-template"/>. The DE is expected to ensure that registrations for the same name with different types are sufficiently close in functionality so as not to cause confusion for developers. The DE is expected to ensure that the values in the discovery document are sufficient to provide optimization and hints to the clientinstance,instance but that knowledge of the discovered value is not required for starting a transaction with the AS.</t> <sectionanchor="IANA-as-discovery-template"><name>Registrationanchor="IANA-as-discovery-template"> <name>Registration Template</name> <dl newline="true"> <dt>Name:</dt> <dd> <t>An identifier for the parameter.</t> </dd> <dt>Type:</dt> <dd> <t>The JSON type allowed for the value.</t> </dd> <dt>Specification document(s):</dt> <dd> <t>Reference tothe document(s)one or more documents that specify the value, preferably including a URI that can be used to retrieve a copy of the document(s). An indication of the relevant sections may also be included but is not required.</t> </dd> </dl> </section> <sectionanchor="IANA-as-discovery-contents"><name>Initialanchor="IANA-as-discovery-contents"> <name>Initial Contents</name><texttable> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Type</ttcol> <ttcol align='left'>Specification document(s)</ttcol> <c>grant_request_endpoint</c> <c>string</c> <c><xref<table> <thead> <tr> <th align="left">Name</th> <th align="left">Type</th> <th align="left">Specification document(s)</th> </tr> </thead> <tbody> <tr> <td align="left">grant_request_endpoint</td> <td align="left">string</td> <td align="left"> <xref target="discovery"/> of&SELF;</c> <c>interaction_start_modes_supported</c> <c>array of strings</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">interaction_start_modes_supported</td> <td align="left">array of strings</td> <td align="left"> <xref target="discovery"/> of&SELF;</c> <c>interaction_finish_methods_supported</c> <c>array of strings</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">interaction_finish_methods_supported</td> <td align="left">array of strings</td> <td align="left"> <xref target="discovery"/> of&SELF;</c> <c>key_proofs_supported</c> <c>array of strings</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">key_proofs_supported</td> <td align="left">array of strings</td> <td align="left"> <xref target="discovery"/> of&SELF;</c> <c>sub_id_formats_supported</c> <c>array of strings</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">sub_id_formats_supported</td> <td align="left">array of strings</td> <td align="left"> <xref target="discovery"/> of&SELF;</c> <c>assertion_formats_supported</c> <c>array of strings</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">assertion_formats_supported</td> <td align="left">array of strings</td> <td align="left"> <xref target="discovery"/> of&SELF;</c> <c>key_rotation_supported</c> <c>boolean</c> <c><xrefRFC 9635</td> </tr> <tr> <td align="left">key_rotation_supported</td> <td align="left">boolean</td> <td align="left"> <xref target="discovery"/> of&SELF;</c> </texttable> </section>RFC 9635</td> </tr> </tbody> </table> </section> </section><section anchor="implementation"><name>Implementation Status</name> <ul empty="true"><li> <t>Note: To be removed by RFC editor before publication.</t> </li></ul> <t><strong>GNAP Authorization Service in Rust</strong> implementation by David Skyberg. <eref target="https://github.com/dskyberg/gnap">https://github.com/dskyberg/gnap</eref> Prototype implementation of AS and client in Rust. MIT license.</t> <t><strong>GNAP JS Client</strong> from Interop Alliance, implementation by Dmitri Zagidulin. <eref target="https://github.com/interop-alliance/gnap-client-js">https://github.com/interop-alliance/gnap-client-js</eref> Prototype implementation of client in JavaScript. MIT License.</t> <t><strong>Rafiki</strong> from Interledger Foundation. <eref target="https://github.com/interledger/rafiki">https://github.com/interledger/rafiki</eref> Production implementation of AS in JavaScript. Apache 2.0 license.</t> <t><strong>Sample GNAP Client in PHP</strong> implementation by Aaron Parecki. <eref target="https://github.com/aaronpk/gnap-client-php">https://github.com/aaronpk/gnap-client-php</eref> Prototype implementation of web application client and CLI client in PHP, with common support library. CC0 license.</t> <t><strong>SUNET Auth Server</strong> from SUNET. <eref target="https://github.com/SUNET/sunet-auth-server">https://github.com/SUNET/sunet-auth-server</eref> Production implementation of AS in Python. BSD license.</t> <t><strong>Trustbloc</strong> from Gen Digital. <eref target="https://github.com/trustbloc/docs/blob/main/readthedocs/designs/auth.md">https://github.com/trustbloc/docs/blob/main/readthedocs/designs/auth.md</eref> Production implementation of AS and client in Go. Apache 2.0 license.</t> <t><strong>Verified.ME</strong> from SecureKey. <eref target="https://verified.me/">https://verified.me/</eref> Production implementation of AS, client and RS. Proprietary license.</t> <t><strong>XYZ</strong> from Bespoke Engineering, implementation by Justin Richer. <eref target="https://github.com/bspk/oauth.xyz-java">https://github.com/bspk/oauth.xyz-java</eref> Advanced prototype implementation of AS, client, and RS in Java, with common support library. Prototype implementation of SPA client in JavaScript. Apache 2.0 license.</t></section> <sectionanchor="security"><name>Securityanchor="security"> <name>Security Considerations</name> <t>In addition to the normative requirements in this document, implementors are strongly encouraged to consider these additional security considerations in implementations and deployments of GNAP.</t> <sectionanchor="security-tls"><name>TLSanchor="security-tls"> <name>TLS Protection in Transit</name> <t>All requests in GNAP made over untrusted network connections have to be made over TLS as outlined in <xref target="BCP195"/> to protect the contents of the request and response from manipulation and interception by an attacker. This includes all requests from a client instance to the AS, all requests from the client instance to an RS, and any requests back to a client instance such as the push-based interaction finish method. Additionally, all requests between a browser and other components, such as during redirect-based interaction, need to be made over TLS or use equivalent protection such as a network connection local to the browser ("localhost").</t> <t>Even though requests from the client instance to the AS are signed, the signature method alone does not protect the request from interception by an attacker. TLS protects the response as well as the request, preventing an attacker from intercepting requested information as it is returned. This is particularly important in the core protocol for security artifacts such as nonces and for personal information such as subject information.</t> <!-- [rfced] We have updated this sentence as follows (removed "While", updated "associated" to "associated with", and added a semicolon). Please review and let us know any concerns. Original: While the keys and signatures associated a bound access token will prevent an attacker from using a stolen token, without TLS an attacker would be able to watch the data being sent to the RS and returned from the RS during legitimate use of the client instance under attack. Updated: The keys and signatures associated with a bound access token will prevent an attacker from using a stolen token; however, without TLS, an attacker would be able to watch the data being sent to the RS and returned from the RS during legitimate use of the client instance under attack. --> <t>The use of key-bound access tokens does not negate the requirement for protecting calls to the RS with TLS.While theThe keys and signatures associated with a bound access token will prevent an attacker from using a stolentoken,token; however, withoutTLSTLS, an attacker would be able to watch the data being sent to the RS and returned from the RS during legitimate use of the client instance under attack. Additionally, withoutTLSTLS, an attacker would be able to profile the calls made between the client instance and RS, possibly gaining information about the functioning of the API between the client software and RS software that wouldbeotherwise be unknown to the attacker.</t> <t>Note that connections from the end user and RO's browser also need to bebeprotected with TLS. This applies during initial redirects to an AS's components during interaction, during any interaction with the resource owner, and during any redirect back to the client instance. Without TLS protection on these portions of the process, an attacker could wait for a valid request to start and then take over the resource owner's interaction session.</t> </section> <sectionanchor="security-signing"><name>Signinganchor="security-signing"> <name>Signing Requests from the Client Software</name> <t>Even though all requests in GNAP need to be transmitted over TLS or its equivalent, the use of TLS alone is not sufficient to protect all parts of a multi-party and multi-stage protocol like GNAP, and TLS is not targeted at tying multiple requests to each other over time. To account for this, GNAP makes use of message-level protection and key presentation mechanisms that strongly associate a request with a key held by the client instance (see <xref target="secure-requests"/>).</t> <t>During the initial request from a client instance to the AS, the client instance has to identify and prove possession of a cryptographic key. If the key is known to the AS,such as if it ise.g., previously registered or dereferenceable to a trusted source, the AS can associate a set of policies to the client instance identified by the key. Without the requirement that the client instance prove that it holds that key, the AS could not trust that the connection came from any particular client and could not apply any associated policies.</t> <t>Even more importantly, the client instance proving possession of a key on the first request allows the AS to associate future requests with each other by binding all future requests in that transaction to the same key. The access token used for grant continuation is bound to the same key and proofing mechanism used by the client instance in its initialrequest, whichrequest; this means that the client instance needs to prove possession of that same key in futurerequests allowingrequests, which allows the AS to be sure that the same client instance is executing the follow-ups for a given ongoing grant request. Therefore, the AS has to ensure that all subsequent requests for a grant are associated with the same key that started thegrant,grant or with the most recent rotation of that key. This need holds true even if the initial key is previously unknown to the AS, such as would be the case when a client instance creates an ephemeral key for its request. Without this ongoing association, an attacker would be able to impersonate a client instance in the midst of a grant request, potentially stealing access tokens and subject information with impunity.</t> <t>Additionally, all access tokens in GNAP default to be associated with the key that was presented during the grant request that created the access token. This association allows an RS to know that the presenter of the access token is the same party that the token was issued to, as identified by their keys. While non-bound bearer tokens are an option in GNAP, these types of tokens have their owntradeoffstrade-offs, which are discussed in <xref target="security-bearer-tokens"/>.</t> <!-- [rfced] Please clarify the phrases indicated for the following sentences. a) "using Section 7.3.2" Original: In other words, it is not possible with TLS alone to know that the same party is making a set of calls over time, since each time a new TLS connection is established, both the client and the server (or the server only when using Section 7.3.2) have to validate the other party's identity. Perhaps: In other words, it is not possible with TLS alone to know that the same party is making a set of calls over time, since each time a new TLS connection is established, both the client and the server (or the server only when using mutual TLS (Section 7.3.2)) have to validate the other party's identity. b) "using [RFC9111]" Original: To compensate for this, the TTRP could inject the TLS client certificate into the forwarded request as a header parameter using [RFC9111], giving the downstream system access to the certificate information. Perhaps: To compensate for this, the TTRP could inject the TLS client certificate into the forwarded request as a header parameter using HTTP caching [RFC9111], giving the downstream system access to the certificate information. c) "using [RFC9421]" Original: The TTRP could provide some additional assurance, for example, by adding its own signature to the Client-Cert header field using [RFC9421]. Perhaps: The TTRP could provide some additional assurance, for example, by adding its own signature to the Client-Cert header field [RFC9421]. --> <t>TLS functions at the transport layer, ensuring that only the parties on either end of that connection can read the information passed along that connection. Each time a new connection is made, such as for a new HTTP request, a new trustis re-establishedthat is mostly unrelated to previousconnections.connections is re-established. While modern TLS does make use of session resumption, this still needs to be augmented with authentication methods to determine the identity of parties on the connections. In other words, it is not possible with TLS alone to know that the same party is making a set of calls over time, since each time a new TLS connection is established, both the client and the server (or the server only when using <xref target="mtls"/>) have to validate the other party's identity. Such a verification can be achieved via methods described in <xref target="RFC9525"/>, but these are not enough to establish the identity of the client instance in many cases.</t> <t>To counter this, GNAP defines a set of key binding methods in <xref target="binding-keys"/> thatallowallows authentication and proof of possession by the caller, which is usually the client instance. These methods are intended to be used in addition to TLS on all connections.</t> </section> <sectionanchor="security-mtls"><name>MTLSanchor="security-mtls"> <name>MTLS Message Integrity</name> <t>The<xref target="mtls">MTLSMTLS key proofingmechanism</xref>mechanism (<xref target="mtls"> </xref>) provides a means for a client instance to present a key using a certificate at the TLS layer. Since TLS protects the entire HTTP message in transit, verification of the TLS client certificate presented with the message provides a sufficient binding between the two. However, since TLS is functioning at a separate layer from HTTP, there is no direct connection between the TLS key presentation and the message itself, other than the fact that the message was presented over the TLS channel. That is to say, any HTTP message can be presented over the TLS channel in question with the same level of trust. The verifier is responsible for ensuring the key in the TLS client certificate is the one expected for a particular request. For example, if the request is a<xref target="request">grant request</xref>,grant request (<xref target="request"> </xref>), the AS needs to compare the TLS client certificate presented at the TLS layer to the key identified in the request content itself (either by value or through a referenced identifier).</t> <t>Furthermore, the prevalence of theTLS-terminatingTLS terminating reverse proxy (TTRP) pattern in deployments adds a wrinkle to the situation. In this common pattern, the TTRP validates the TLS connection and then forwards the HTTP message contents onward to an internal system for processing. The system processing the HTTP message no longer has access to the original TLS connection's information and context. To compensate for this, the TTRP could inject the TLS client certificate into the forwarded request as a header parameter using <xref target="RFC9111"/>, giving the downstream system access to the certificate information. The TTRP has to be trusted to provide accurate certificate information, and the connection between the TTRP and the downstream system also has to be protected. The TTRP could provide some additional assurance, for example, by adding its own signature to the Client-Cert header field using <xref target="RFC9421"/>. This signature would be effectively ignored by GNAP (since it would not use GNAP's<spanx style="verb">tag</spanx><tt>tag</tt> parameter value) but would be understood by the downstream service as part of its deployment.</t> <t>Additional considerations for different types of deployment patterns and key distribution mechanisms for MTLS are found in <xref target="security-mtls-patterns"/>.</t> </section> <sectionanchor="security-mtls-patterns"><name>MTLSanchor="security-mtls-patterns"> <name>MTLS Deployment Patterns</name> <t>GNAP does not specify how a client instance's keys could be made known to the AS ahead of time. The Public Key Infrastructure (PKI) can be used to manage the keys used by client instances when calling the AS, allowing the AS to trust a root key from a trusted authority. This method is particularly relevant to the MTLS key proofing method, where the client instance presents its certificate to the AS as part of the TLS connection. An AS using PKI to validate the MTLS connection would need to ensure that the presented certificate was issued by a trusted certificate authority before allowing the connection to continue. PKI-based certificates would allow a key to be revoked and rotated through management at the certificate authority without requiring additional registration or management at the AS. The PKI required to managemutually-authenticatedmutually authenticated TLS has historically been difficult to deploy, especially at scale, but it remains an appropriate solution for systems where the required management overhead is not an impediment.</t> <t>MTLS in GNAP need not use a PKI backing, as self-signed certificates and certificates from untrusted authorities can still be presented as part of a TLS connection. In this case, the verifier would validate the connection but accept whatever certificate was presented by the client software. This specific certificate can then be bound to all future connections from that client software by being bound to the resulting access tokens, in a trust-on-first-use pattern. See <xref target="security-mtls"/> for more considerations on MTLS as a key proofing mechanism.</t> </section> <sectionanchor="security-keys"><name>Protectionanchor="security-keys"> <name>Protection of Client Instance Key Material</name> <t>Client instances are identified by their unique keys, and anyone with access to a client instance's key material will be able to impersonate that client instance to all parties. This is true for both calls to the AS as well as calls to an RS using an access token bound to the client instance's unique key. As a consequence, it is of utmost importance for a client instance to protect its private key material.</t> <!-- [rfced] May we update "a keypair on-device" in one of the following ways? Original: The client software can securely generate a keypair on-device and present the public key, along with proof of holding the associated private key, to the AS as part of the initial request. Perhaps: The client software can securely generate a key pair on the device and present the public key, along with proof of holding the associated private key, to the AS as part of the initial request. Or: The client software can securely generate an on-device keypair and present the public key, along with proof of holding the associated private key, to the AS as part of the initial request. --> <t>Different types of client software have different methods for creating, managing, and registering keys. GNAP explicitly allows for ephemeral clients such as single-page applications (SPAs) and single-user clients (such as mobile applications) to create and present their own keys during the initial grant request without any explicit pre-registration step. The client software can securely generate akeypairkey pair on-device and present the public key, along with proof of holding the associated private key, to the AS as part of the initial request. To facilitate trust in these ephemeral keys, GNAP further allows for an extensible set of client information to be passed with the request. This information can include device posture and third-party attestations of the client software's provenance and authenticity, depending on the needs and capabilities of the client software and its deployment.</t> <t>From GNAP's perspective, each distinct key is a different client instance. However, multiple client instances can be grouped together by an AS policy and treated similarly to each other. For instance, if an AS knows of several different keys for different servers within a cluster, the AS can decide that authorization of one of these servers applies to all other servers within the cluster. An AS that chooses to do this needs to be careful with how it groups different client keys together in its policy, since the breach of one instance would have direct effects on the others in the cluster.</t> <t>Additionally, if an end user controls multiple instances of a single type of client software, such as having an application installed on multiple devices, each of these instances is expected to have a separate key and be issued separate access tokens. However, if the AS is able to group these separate instances together as described above, it can streamline the authorization process for new instances of the same client software. For example, if two client instances can present proof of a valid installation of a piece of client software, the AS would be able to associate the approval of the first instance of this software to all related instances. The AS could then choose to bypass an explicit prompt of the resource owner for approval during authorization, since such approval has already been given. An AS doing such a process would need to take assurance measures that the different instances are in fact correlated and authentic, as well asensuringensure that the expected resource owner is in control of the client instance.</t> <t>Finally, if multiple instances of client software each have the same key, then from GNAP's perspective, these are functionally the same client instance as GNAP has no reasonable way to differentiate between them. This situation could happen if multiple instances within a cluster can securely share secret information among themselves. Even though there are multiple copies of the software, the shared key makes these copies all present as a single instance. It is considered bad practice to share keys between copies of software unless they are very tightly integrated with each other and can be closely managed. It is particularly bad practice to allow an end user to copy keys between client instances and to willingly use the same key in multiple instances.</t> </section> <sectionanchor="security-as"><name>Protectionanchor="security-as"> <name>Protection of Authorization Server</name> <t>The AS performs critical functions in GNAP, including authenticating client software, managing interactions with end users to gather consent and provide notice, and issuing access tokens for client instances to present to resource servers. As such, protecting the AS is central to any GNAP deployment.</t> <t>If an attacker is able to gain control over an AS, they would be able to create fraudulent tokens and manipulate registration information to allow for malicious clients. These tokens and clients would be trusted by other components in the ecosystem under the protection of the AS.</t> <t>If the ASis usinguses signed access tokens, an attacker in control of the AS's signing keys would be able to manufacture fraudulent tokens for use atRS'sRSs under the protection of the AS.</t> <t>If an attacker is able to impersonate an AS, they would be able to trick legitimate client instances into making signed requests for informationwhichthat could potentially be proxied to a real AS. To combat this, all communications to the AS need to be made over TLS or its equivalent, and the software making the connection has to validate the certificate chain of the host it is connecting to.</t> <t>Consequently, protecting, monitoring, and auditing the AS is paramount to preserving the security of a GNAP-protected ecosystem. The AS presents attackers with a valuable target for attack. Fortunately, the core focus and function of the AS is to provide security for the ecosystem, unlike the RS whose focus is to provide an API or the client software whose focus is to access the API.</t> </section> <sectionanchor="security-symmetric"><name>Symmetricanchor="security-symmetric"> <name>Symmetric and Asymmetric Client Instance Keys</name> <t>Many of the cryptographic methods used by GNAP forkey-proofingkey proofing can support both asymmetric and symmetric cryptography, and they can be extended to use a wide variety of mechanisms.ImplementersImplementors will findusefulthe available guidelines on cryptographic key management provided in <xreftarget="RFC4107"/>.target="RFC4107"/> useful. While symmetric cryptographic systems have some benefits in speed and simplicity, they have a distinct drawbackthat-- both parties need access to the same key in order to do both signing and verification of the message. When more than two parties share the same symmetric key, data origin authentication is not provided. Any party that knows the symmetric key can compute a valid MAC; therefore, the contents could originate from any one of the parties.</t> <t>Use of symmetric cryptography means that when the client instance calls the AS to request a token, the AS needs to know the exact value of the client instance's key (or be able to derive it) in order to validate the key proof signature. With asymmetric keys, the client needsonlyto only send its public key to the AS to allow for verification that the client holds the associated private key, regardless of whether or not that key was pre-registeredor notwith the AS.</t> <t>Symmetric keys also have the expected advantage of providing better protection against quantum threats in the future. Also, these types of keys (and their secure derivations) are widely supported among many cloud-based key management systems.</t> <t>When used to bind to an access token, a key value must be known by the RS in order to validate the proof signature on the request. Common methods for communicating these proofing keys include putting information in a structured access token and allowing the RS to look up the associated key material against the value of the access token. With symmetric cryptography, both of these methods would expose the signing key to theRS, andRS and, in the case ofana structured access token, potentially to any party that can see the access token itself unless the token's payload has been encrypted. Any of these parties would then be able to make calls using the access token by creating a valid signature using the shared key. With asymmetric cryptography, the RS needs toknowonly know the public key associated with the token in order to validate therequest, and thereforerequest; therefore, the RS cannot create any new signed calls.</t> <t>While both signing approaches are allowed, GNAP treats these two classes of keys somewhat differently. Only the public portion of asymmetric keys are allowed to be sent by value in requests to the AS when establishing a connection. Since sending a symmetric key (or the private portion of an asymmetric key) would expose the signing material to any parties on the request path, including any attackers, sending these kinds of keys by value is prohibited. Symmetric keys can still be used by client instances, but only if the client instance can send a reference to the key and not its value. This approach allows the AS to use pre-registered symmetric keys as well as key derivation schemes to take advantage of symmetric cryptographybutwithout requiring key distribution at runtime, which would expose the keys in transit.</t> <t>Both the AS and client software can use systems such as hardware security modules to strengthen their key security storage and generation for both asymmetric and symmetric keys (see also <xref target="key-protection"/>).</t> </section> <sectionanchor="security-access-tokens"><name>Generationanchor="security-access-tokens"> <name>Generation of Access Tokens</name> <t>Thecontentcontents of access tokens need to be such that only the generating AS would be able to create them, and the contents cannot be manipulated by an attacker to gain different or additional access rights.</t> <t>One method for accomplishing this is to use a cryptographically random value for the access token, generated by the AS using a secure randomization function with sufficiently high entropy. The odds of an attacker guessing the output of the randomization function to collide with a valid access token are exceedingly small, and eventhenthen, the attacker would not have any control over what the access token would represent since that information would be held close by the AS.</t> <t>Another method for accomplishing this is to use a structured token that is cryptographically signed. In this case, the payload of the access token declares to the RS what the token is good for, but the signature applied by the AS during token generation covers this payload. Only the AS can create such asignature and thereforesignature; therefore, only the AS can create such a signed token. The odds of an attacker being able to guess a signature value with a useful payload are exceedingly small. This technique only works if all targetedRS'sRSs check the signature of the access token. Any RS that does not validate the signature of all presented tokens would be susceptible to injection of a modified or falsified token. Furthermore, an AS has to carefully protect the keys used to sign access tokens, since anyone with access to these signing keys would be able to createseemingly-validseemingly valid access tokens using them.</t> </section> <sectionanchor="security-bearer-tokens"><name>Beareranchor="security-bearer-tokens"> <name>Bearer Access Tokens</name> <!-- [rfced] Please clarify "is able capture of the token value". Original: It also means that any party that is able capture of the token value in storage or in transit is able to use the access token. Perhaps: It also means that any party that is able to capture the token value in storage or in transit is able to use the access token. --> <t>Bearer access tokens can be used by any party that has access to the token itself, without any additional information. As a natural consequence, any RS that a bearer token is presented to has the technical capability of presenting that bearer token to another RS, as long as the token is valid. It also means that any party that is able capture of the token value in storage or in transit is able to use the access token. While bearer tokens are inherently simpler, this simplicity has been misapplied and abused in making needlessly insecure systems. The downsides of bearer tokens have become more pertinent lately as stronger authentication systems have caused some attacks to shift to target tokens and APIs.</t> <t>In GNAP, key-bound access tokens are the default due to their higher security properties. While bearer tokens can be used in GNAP, their use should be limited to cases where the simplicity benefits outweigh the significant security downsides. One common deployment pattern is to use a gateway that takes in key-bound tokens on theoutside,outside and verifies the signatures on the incomingrequests,requests but translates the requests to a bearer token for use by trusted internal systems. The bearer tokens are never issued or available outside of the internal systems, greatly limiting the exposure of theless secureless-secure tokens but allowing the internal deployment to benefit from the advantages of bearer tokens.</t> </section> <sectionanchor="security-bound-tokens"><name>Key-Boundanchor="security-bound-tokens"> <name>Key-Bound Access Tokens</name> <t>Key-bound access tokens, as the name suggests, are bound to a specific key and must be presented along with proof of that key during use. The key itself is not presented at the same time as the token, so even if a token value is captured, it cannot be used to make a new request. This is particularly true for an RS, which will see the token value but will not see the keys used to make the request (assuming asymmetric cryptography is in use, see <xref target="security-symmetric"/>).</t> <t>Key-bound access tokens provide this additional layer of protection only when the RS checks the signature of the message presented with the token. Acceptance of an invalid presentation signature, or failure to check the signature entirely, would allow an attacker to make calls with a captured access token without having access to the related signing key material.</t> <t>In addition to validating the signature of the presentation message itself, the RS also needs to ensure that the signing key used is appropriate for the presented token. If an RS does not ensure that the right keys were used to sign a message with a specific token, an attacker would be able to capture an access token and sign the request with their own keys, thereby negating the benefits of using key-bound access tokens.</t> <t>The RS also needs to ensure that sufficient portions of the message are covered by the signature. Any items outside the signature could still affect the API's processing decisions, but these items would not be strongly bound to the token presentation. As such, an attacker could capture a validrequest,request and then manipulate portions of the request outside of the signature envelope in order to cause unwanted actions at the protected API.</t> <t>Some key-bound tokens are susceptible to replay attacks, depending on the details of the signing method used.KeyTherefore, key proofing mechanisms used with access tokensthereforeneed to usereplay protectionreplay-protection mechanisms covered under the signature such as a per-message nonce, a reasonably short time validity window, or other uniqueness constraints. The details of using these will vary depending on the key proofing mechanism inuse, but foruse. For example, HTTP Message Signatureshashave both a<spanx style="verb">created</spanx><tt>created</tt> and<spanx style="verb">nonce</spanx><tt>nonce</tt> signature parameter as well as the ability to cover significant portions of the HTTP message. All of these can be used to limit the attack surface.</t> </section> <sectionanchor="security-credentials"><name>Exposureanchor="security-credentials"> <name>Exposure ofEnd-userEnd-User Credentials to Client Instance</name> <t>As a delegation protocol, one of the main goals of GNAP is to prevent the client software from being exposed to any credentials or information about the end user or resource owner as a requirement of the delegation process. By using the variety of interaction mechanisms, the resource owner can interact with the AS without ever authenticating to the clientsoftware,software and without the client software having to impersonate the resource owner through replay of their credentials.</t> <t>Consequently, no interaction methods defined in the GNAP core require the end user to enter their credentials, but it is technologically possible for an extension to be defined to carry such values. Such an extension would be dangerous as it would allow rogue client software to directly collect, store, and replay the end user's credentials outside of any legitimate use within a GNAP request.</t> <t>The concerns of such an extension could be mitigated through use of a challenge and response unlocked by the end user's credentials. For example, the AS presents a challenge as part of an interaction start method, and the client instance signs that challenge using a key derived from a password presented by the end user. It would be possible for the client software to collect this password in a secure software enclave without exposing the password to the rest of the client software or putting it across the wire to the AS. The AS can validate this challenge response against a known password for the identified end user. While an approach such as this does not remove all of the concerns surrounding such a password-based scheme, it is at least possible to implement in a more secure fashion than simply collecting and replaying the password. Even so, such schemes should only ever be used by trusted clients due to the ease of abusing them.</t> </section> <sectionanchor="security-mixup"><name>Mixinganchor="security-mixup"> <name>Mixing Up Authorization Servers</name> <t>If a client instance is able to work with multipleAS'sASes simultaneously, it is possible for an attacker to add a compromised AS to the client instance's configuration and cause the client software to start a request at the compromised AS. This AS could then proxy the client's request to a valid AS in order to attempt to get the resource owner to approve access for the legitimate client instance.</t> <!-- [rfced] [AXELAND2021] mentions several types of attacks. Would it help readers to specify the attack type or applicable section(s) in [AXELAND2021]? Original: See [AXELAND2021] for details of one such attack, which has been since addressed in this document by including the grant endpoint in the interaction hash calculation. Perhaps: See Sections 4.5.5 and 5.5 of [AXELAND2021] for details of one such attack, which has been since addressed in this document by including the grant endpoint in the interaction hash calculation. --> <!-- [rfced] Should "Section 11.31" in the first sentence below be updated to "Section 11.12" (as used in the second sentence for "mix-up attacks")? Section 11.31 does mention "mix-up attacks" but with a pointer to Section 11.12. Section 11.12 doesn't specifically use the term "mix-up attack", but the title is "Mixing Up Authorization Servers". Current: A client instance that is capable of talking to multiple ASes SHOULD use a different key for each AS to prevent a class of mix-up attacks as described in Section 11.31 unless other mechanisms can be used to assure the identity of the AS for a given request. ... This strong binding also helps against some forms of AS mix-up attacks (Section 11.12). --> <t>A client instance needs to always be aware of which AS it is talking to throughout a grantprocess,process and ensure that any callback for one AS does not get conflated with the callback to different AS. The interaction finish hash calculation in <xref target="interaction-hash"/> allows a client instance to protect against this kind of substitution, but only if the client instance validates the hash. If the client instance does not use an interaction finish method or does not check the interaction finish hash value, the compromised AS can be granted a valid access token on behalf of the resource owner. See <xref target="AXELAND2021"/> for details of one such attack, which has beensinceaddressed in this document by including the grant endpoint in the interaction hash calculation. Note that the client instance still needs to validate the hash for the attack to be prevented.</t> </section> <sectionanchor="security-client-userinfo"><name>Processinganchor="security-client-userinfo"> <name>Processing of Client-Presented User Information</name> <t>GNAP allows the client instance to present assertions and identifiers of the current user to the AS as part of the initial request. This information should only ever be taken by the AS as a hint, since the AS has no way to tell if the represented person is present at the clientsoftware,software without using an interaction mechanism. This information does not guarantee the given user is there, but it does constitute a statement by the client software that the AS can take into account.</t> <t>For example, if a specific user is claimed to be present prior to interaction, but a different user is shown to be present during interaction, the AS can either determine this to be an error or signal to the client instance through returned subject information that the current user has changed from what the client instance thought. This user information can also be used by the AS to streamline the interaction process when the user is present. For example, instead of having the user type in their account identifier during interaction at a redirected URI, the AS can immediately challenge the user for their account credentials. Alternatively, if an existing session is detected, the AS can determine that it matches the identifier provided by the client and subsequently skip an explicit authentication event by the resource owner.</t> <t>In cases where the AS trusts the client software more completely, due to policy orbyprevious approval of a given client instance, the AS can take this user information as a statement that the user is present and could issue access tokens and release subject information without interaction. The AS should only take such action in very limited circumstances, as a client instance could assert whatever it likes for the user's identifiers in its request. The AS can limit the possibility of this by issuing randomized opaque identifiers to client instances to represent differentend userend-user accounts after an initial login.</t> <t>When a client instance presents an assertion to the AS, the AS needs to evaluate that assertion. Since the AS is unlikely to be the intended audience of an assertion held by the client software, the AS will need to evaluate the assertion in a different context. Even in this case, the AS can still evaluate that the assertion was generated by a trusted party, was appropriately signed, and is within any time validity windows stated by the assertion. If the client instance's audience identifier is known to the AS and can be associated with the client instance's presented key, the AS can also evaluate that the appropriate client instance is presenting the claimed assertion. All of this will prevent an attacker from presenting a manufacturedassertion,assertion or one captured from an untrusted system. However, without validating the audience of the assertion, a captured assertion could be presented by the client instance to impersonate a given end user. In such cases, the assertion offers little more protection than a simple identifier would.</t> <t>A special case exists where the AS is the generator of the assertion being presented by the client instance. In these cases, the AS can validate that it did issue the assertion and it is associated with the client instance presenting the assertion.</t> </section> <sectionanchor="security-registration"><name>Clientanchor="security-registration"> <name>Client Instance Pre-registration</name> <t>Each client instance is identified by its own unique key, and for some kinds of client software such as a web server or backend system, this identification can be facilitated by registering a single key for a piece of client software ahead of time. This registration can be associated with a set of display attributes to be used during the authorizationprocess, identifyingprocess to identify the client software to the user. In these cases, it can be assumed that only one instance of client software will exist, likely to serve many different users.</t> <!-- [rfced] Please clarify how the text beginning with "or be limited to..." connects to the rest of the sentence. Original: The registration record can also limit a given client to ask for certain kinds of information and access, or be limited to specific interaction mechanisms at runtime. Perhaps: The registration record can also limit a given client to ask for certain kinds of information and access, to prevent being limited to specific interaction mechanisms at runtime. --> <t>A client's registration record needs to include its identifying key. Furthermore, it is the case that any clients using symmetric cryptography for key proofing mechanisms need to have their keys pre-registered. The registration should also include any information that would aid in the authorization process, such as a display name and logo. The registration record can also limit a given client to ask for certain kinds of information and access, or be limited to specific interaction mechanisms at runtime.</t> <!-- [rfced] Please confirm that "rest" is the correct word choice here. Would "rely" or something similar would be a better? If updating to "rely", we will also update "in determining" to "to determine". Original: In these cases, an AS needs to rest on the trust decisions that have been determined prior to runtime in determining what rights and tokens to grant to a given client instance. Perhaps: In these cases, an AS needs to rely on the trust decisions that have been determined prior to runtime to determine what rights and tokens to grant to a given client instance. --> <t>It also is sensible to pre-register client instances when the software is acting autonomously, without the need for a runtime approval by a resource owner or any interaction with an end user. In these cases, an AS needs to rest on the trust decisions that have been determined prior to runtime in determining what rights and tokens to grant to a given client instance.</t> <t>However, it does not make sense to pre-register many types of clients. Single-page applications (SPAs) and mobile/desktop applications in particular present problems with pre-registration. For SPAs, the instances are ephemeral innaturenature, and long-term registration of a single instance leads to significant storage and management overhead at the AS. For mobile applications, each installation of the client software is a separate instance, and sharing a key among all instances would be detrimental to security as the compromise of any single installation would compromise all copies for all users.</t> <t>An AS can treat these classes of client software differently from each other, perhaps by allowing access to certain high-value APIs only to pre-registered knownclients,clients or by requiring an activeend userend-user delegation of authority to any client software not pre-registered.</t> <t>An AS can also provide warnings and caveats to resource owners during the authorization process, allowing the user to make an informed decision regarding the software they are authorizing. For example, if the AS hasdone vetting ofvetted the client software and this specific instance, it can present a different authorization screen compared to a client instance that is presenting all of its information at runtime.</t> <t>Finally, an AS can use platform attestations and other signals from the client instance at runtime to determine whether or not the software making the request islegitimate or not.legitimate. The details of such attestations are outside the scope of the core protocol, but the<spanx style="verb">client</spanx><tt>client</tt> portion of a grant request provides a natural extension point to such information through the<xref target="IANA-client-instance">Client"GNAP Client InstanceFields registry</xref>.</t>Fields" registry (<xref target="IANA-client-instance"> </xref>).</t> </section> <sectionanchor="security-impersonation"><name>Clientanchor="security-impersonation"> <name>Client Instance Impersonation</name> <t>If client instances are allowed to set their own user-facing display information, such as a display name and website URL, a malicious client instance could impersonate legitimate client software for the purposes of tricking users into authorizing the malicious client.</t> <t>Requiring clients to pre-register does not fully mitigate this problem since many pre-registration systems have self-service portals for management of client registration, allowing authenticated developers to enter self-asserted information into the management portal.</t> <t>An AS can mitigate this by actively filtering all self-asserted values presented by client software, both dynamically as part of GNAP and through a registration portal, to limit the kinds of impersonation thatwouldcould be done.</t> <t>An AS can also warn the resource owner about the provenance of the information it is displaying, allowing the resource owner to make a more informed delegation decision. For example, an AS can visually differentiate between a client instance that can be traced back to a specific developer's registration and an instance that has self-asserted its own display information.</t> </section> <sectionanchor="security-client-hosted-logo"><name>Client-Hostedanchor="security-client-hosted-logo"> <name>Client-Hosted Logo URI</name> <t>The<spanx style="verb">logo_uri</spanx><tt>logo_uri</tt> client display field defined in <xref target="request-display"/> allows the client instance to specify a URI from which an image can be fetched for display during authorization decisions. When the URI points to an externally hosted resource (as opposed to a data: URI), the<spanx style="verb">logo_uri</spanx><tt>logo_uri</tt> field presents challenges in addition to the considerations in <xref target="security-impersonation"/>.</t> <t>When a<spanx style="verb">logo_uri</spanx><tt>logo_uri</tt> is externally hosted, the client software (or the host of the asset) can change the contents of the logo without informing the AS. Since the logo is considered an aspect of the client software's identity, this flexibility allows for a moredynamically-manageddynamically managed client instance that makes use of the distributed systems.</t> <t>However, this same flexibility allows the host of the asset to change the hosted file in a malicious way, such as replacing the image content with malicious software for download or imitating a different piece of client software. Additionally, the act of fetching the URI could accidentally leak information to the image host in the HTTP Referer header field, if one is sent. Even though GNAP intentionally does not include security parameters in front-channelURI'sURIs wherever possible, the AS still should take steps to ensure that this information does not leak accidentally, such as setting a referrer policy on image links or displaying images only frompagedpages served from a URI with no sensitive security or identity information.</t> <t>To avoid these issues, the AS can insist on the use of data: URIs, though that might not be practical for all types of client software. Alternatively, the AS could pre-fetch the content of the URI and present its own copy to the resource owner instead. This practice opens the AS to potential SSRF attacks, as discussed in <xref target="security-ssrf"/>.</t> </section> <sectionanchor="security-browser-interception"><name>Interceptionanchor="security-browser-interception"> <name>Interception of Information in the Browser</name> <t>Most information passed through theweb-browserweb browser is susceptible to interception and possible manipulation by elements within the browser such as scripts loaded within pages. Information in the URI is exposed through browser and server logs, and it can also leak to other parties through HTTP<spanx style="verb">Referer</spanx><tt>Referer</tt> headers.</t> <t>GNAP's design limits the information passed directly through the browser, allowing for opaque URIs in most circumstances. For the redirect-based interaction finish mechanism, named query parameters are used to carry unguessable opaque values. For these, GNAP requires creation and validation of a cryptographic hash to protect the query parameters added to the URI and associate them with an ongoing grant process and values not passed in the URI. The client instance has to properly validate this hash to prevent an attacker from injecting an interaction reference intended for a different AS or client instance.</t> <t>Several interaction start mechanisms use URIs created by the AS and passed to the client instance. While these URIs are opaque to the client instance, it's possible for the AS to include parameters, paths, and other pieces of information that could leak security data or be manipulated by a party in the middle of the transaction. An AS implementation can avoid this problem by creating URIs using unguessable values that are randomized for each new grant request.</t> </section> <sectionanchor="security-callback-uri"><name>Callbackanchor="security-callback-uri"> <name>Callback URI Manipulation</name> <t>The callback URI used in interaction finish mechanisms is defined by the client instance. This URI is opaque to theAS,AS but can contain information relevant to the client instance's operations. In particular, the client instance can include state information to allow the callback request to be associated with an ongoing grant request.</t> <t>Since this URI is exposed to the end user's browser, it is susceptible to both logging and manipulation in transit before the request is made to the client software. As such, a client instance should never put security-critical or private information into the callback URI in a cleartext form. For example, if the client software includes a post-redirect target URI in its callback URI to the AS, this target URI could be manipulated by an attacker, creating an open redirector at the client. Instead, a client instance can use an unguessable identifier in the URI that can then be used by the client software to look up the details of the pending request. Since this approach requires some form of statefulness by the client software during the redirection process, clients that are not capable of holding state through a redirect should not use redirect-based interaction mechanisms.</t> </section> <sectionanchor="security-redirect-status-codes"><name>Redirectionanchor="security-redirect-status-codes"> <name>Redirection Status Codes</name> <!-- [rfced] Status codes a) In Section 13.19, we added the description of the error codes mentioned. Please review for correctness. b) Will "HTTP 200" here be clear to readers? Would it be helpful to update as follows? Original: For successful rotations, the AS responds with an HTTP 200 with a JSON-formatted message content consisting of the rotated access token in the access_token field described in Section 3.2.1. Perhaps: For successful rotations, the AS responds with an HTTP status code 200 (OK) with JSON-formatted message content consisting of the rotated access token in the access_token field described in Section 3.2.1. --> <t>Asalreadydescribed in <xref target="I-D.ietf-oauth-security-topics"/>, a server should never usetheHTTP307status code 307 (Temporary Redirect) to redirect a request that potentially contains user credentials. If an HTTP redirect is used for such a request,theHTTP status code 303"See Other"(See Other) should be used instead.</t><t>The status<t>Status code307,307 (Temporary Redirect), as defined in the HTTP standard <xreftarget="HTTP"/>,target="RFC9110"/>, requires the user agent to preserve the method and content of a request, thus submitting the content of the POST request to the redirect target. <!--[rfced] Please clarify "allowed not to rewrite a POST request into a GET request" in the second sentence. Original: In the HTTP standard<xref target="HTTP"/>,[HTTP], only the status code 303 unambiguously enforces rewriting the HTTP POST request to an HTTP GET request, which eliminates the POST content from the redirected request. For all other status codes, including status code 302, user agents are allowed not to rewrite a POST request into a GET request and thus to resubmit the contents. Perhaps: In the HTTP standard [HTTP], only the status code 303 unambiguously enforces rewriting the HTTP POST request to an HTTP GET request, which eliminates the POST content from the redirected request. For all other status codes, including status code 302, user agents are do not have to rewrite a POST request into a GET request and thus can resubmit the contents. --> In the HTTP standard <xref target="RFC9110"/>, only status code 303 (See Other) unambiguously enforces rewriting the HTTP POST request to an HTTP GET request, which eliminates the POST content from the redirected request. For all other status codes, including status code 302 (Found), user agents are allowed not to rewrite a POST request into a GET request and thus to resubmit the contents.</t> <!-- [rfced] Is "directly redirect" okay here? Or would "immediately redirect" or something else be better? Original: The AS checks the credentials and, if successful, may directly redirect the RO to the client instance's redirect URI. Perhaps: The AS checks the credentials and, if successful, may immediately redirect the RO to the client instance's redirect URI. --> <t>The use of status code 307 (Temporary Redirect) results in a vulnerability when using the<xref target="response-interact-finish"><spanx style="verb">redirect</spanx><tt>redirect</tt> interaction finishmethod</xref>.method (<xref target="response-interact-finish"> </xref>). With this method, the AS potentially prompts the RO to enter their credentials in a form that is then submitted back to the AS (using an HTTP POST request). The AS checks the credentials and, if successful, may directly redirect the RO to the client instance's redirect URI. Due to the use of status code307,307 (Temporary Redirect), the RO's user agent now transmits the RO's credentials to the client instance. A malicious client instance can then use the obtained credentials to impersonate the RO at the AS.</t> <t>Redirection away from the initial URI in an interaction session could also leak information found in that initial URI through the HTTP Referer header field, which would be sent by the user agent to the redirect target. To avoid such leakage, a server can first redirect to an internal interstitial page without any identifying or sensitive information on the URI before processing the request. When the user agent is ultimately redirected from this page, no part of the original interaction URI will be found in the Referer header.</t> </section> <sectionanchor="security-as-response"><name>Interceptionanchor="security-as-response"> <name>Interception of Responses from the AS</name> <t>Responses from the AS contain information vital to both the security and privacy operations of GNAP. This information includes nonces used in cryptographic calculations, subject identifiers, assertions, public keys, and information about what client software is requesting and was granted.</t> <t>In addition, if bearer tokens are used or keys are issued alongside a bound access token, the response from the AS contains all information necessary for use of the contained access token. Any party that is capable of viewing such a response, such as an intermediary proxy, would be able to exfiltrate and use this token. If the access token is instead bound to the client instance's presented key, intermediaries no longer have sufficient information to use the token. They can still, however, gain information about the end user as well as the actions of the client software.</t> </section> <sectionanchor="security-key-distribution"><name>Keyanchor="security-key-distribution"> <name>Key Distribution</name> <t>GNAP does not define ways for the client instances keys to be provided to the client instances, particularly in light of how those keys are made known to the AS. These keys could be generated dynamically on the client software or pre-registered at the AS in a static developer portal. The keys for client instances could also be distributed as part of the deployment process of instances of the client software. For example, an application installation framework could generate akeypairkey pair for each copy of clientsoftware,software and then both install it into the client software upon installation andregisteringregister that instance with the AS.</t> <t>Alternatively, it's possible for the AS to generate keys to be used with access tokens that are separate from the keys used by the client instance to request tokens. In this method, the AS would generate the asymmetrickeypairkey pair or symmetric key and return the public key or keyreference,reference to the client instance alongside the access token itself. The means for the AS to return generated key values to the client instance are out of scope, since GNAP does not allow the transmission of private or shared key information within the protocol itself.</t> <t>Additionally, if the token is bound to a key other than the client instance's presented key, this opens a possible attack surface for an attacker's AS to request an access token and then substitute their own key material in the response to the client instance. The attacker's AS would need to be able to use the same key as the client instance, but this setup would allow an attacker's AS to make use of a compromised key within a system. This attack can be prevented by only binding access tokens to the client instance's presentedkeys,keys and by having client instances have a strong association between which keys they expect to use and the AS they expect to use them on. This attack is also only able to be propagated on client instances that talk to more than one AS at runtime, which can be limited by the client software.</t> </section> <sectionanchor="security-key-rotation"><name>Keyanchor="security-key-rotation"> <name>Key Rotation Policy</name> <t>When keys are rotated, there could be a delay in the propagation of that rotation to various components in the AS's ecosystem. The AS can define its own policy regarding the timeout of thepreviously-boundpreviously bound key, either making it immediately obsolete or allowing for a limited grace period during which both thepreviously-boundpreviously bound key and the current key can be used for signing requests. Such a grace period can be useful when there are multiple running copies of the client that are coordinated with each other. For example, the client software could be deployed as a cloud service with multiple orchestrated nodes. Each of these copies is deployed using the samekey and thereforekey; therefore, all the nodes represent the same client instance to the AS. In such cases, it can be difficult, or even impossible, to update the keys on all these copies in the same instant.</t> <t>The needfor accommodatingto accommodate such known delays in the system needs to be balanced with the risk of allowing an old key to still be used. Narrowly restricting the exposure opportunities for exploit at the AS in terms of time, place, and method makes exploit significantly more difficult, especially if the exception happens only once. For example, the AS can reject requests from thepreviously-boundpreviously bound key (or any previous one before it) to cause rotation to a newkey,key or at least ensure that the rotation happens in an idempotent way to the same new key.</t> <t>See also the related considerations for token values in <xref target="security-network-management"/>.</t> </section> <sectionanchor="security-polling"><name>Interactionanchor="security-polling"> <name>Interaction Finish Modes and Polling</name> <t>During the interaction process, the client instance usually hands control of the user experience over to another component, be it the system browser, another application, or some action the resource owner is instructed to take on another device. By using an interaction finish method, the client instance can be securely notified by the AS when the interaction is completed and the next phase of the protocol should occur. This process includes information that the client instance can use to validate the finish call from the AS and prevent some injection, session hijacking, and phishing attacks.</t> <t>Some types of client deployment are unable to receive an interaction finish message. Without an interaction finish method to notify it, the client instance will need to poll the grant continuation API while waiting for the resource owner to approve or deny the request. An attacker could take advantage of this situation by capturing the interaction start parameters and phishing a legitimate user into authorizing the attacker's waiting client instance, which would in turn have no way of associating the completed interaction from the targeted user with the start of the request from the attacker.</t> <t>However, it is important to note that this pattern is practically indistinguishable from some legitimate use cases. For example, a smart device emits a code for the resource owner to enter on a separate device. The smart device has to poll because the expected behavior is that the interaction will take place on the separate device, without a way to return information to the original device's context.</t> <t>As such, developers need to weigh the risks of forgoing an interaction finish method against the deployment capabilities of the client software and its environment. Due to the increased security, an interaction finish method should be employed whenever possible.</t> </section> <sectionanchor="security-sessions"><name>Sessionanchor="security-sessions"> <name>Session Management for Interaction Finish Methods</name> <t>When using an interaction finish method such as<spanx style="verb">redirect</spanx><tt>redirect</tt> or<spanx style="verb">push</spanx>,<tt>push</tt>, the client instance receives an unsolicited inbound request from an unknown party over HTTPS. The client instance needs to be able to successfully associate this incoming request with a specific pending grant request being managed by the client instance. If the client instance is not careful and precise about this, an attacker could associate their own session at the client instance with a stolen interaction response. The means of preventing thisvariesvary by the type of client software and interaction methods in use. Some common patterns are enumerated here.</t> <t>If the end user interacts with the client instance through a web browser and the<spanx style="verb">redirect</spanx><tt>redirect</tt> interaction finish method is used, the client instance can ensure that the incoming HTTP request from the finish method is presented in the same browser session that the grant request was started in. This technique is particularly useful when the<spanx style="verb">redirect</spanx><tt>redirect</tt> interaction start mode is used as well, since in manycasescases, the end user will follow the redirection with the same browser that they are using to interact with the client instance. The client instance can then store the relevant pending grant information in the session, either in the browser storage directly (such as with a single-page application) or in an associated session store on a back-end server. In both cases, when the incoming request reaches the client instance, the session information can be used to ensure that the same party that started the request is present as the request finishes.</t> <t>Ensuring that the same party that started a request is present when that request finishes can prevent phishing attacks, where an attacker starts a request at an honest client instance and tricks an honest RO into authorizing it. For example, if an honest end user (that also acts as the RO) wants to start a request through a client instance controlled by the attacker, the attacker can start a request at an honest client instance and then redirect the honest end user to the interaction URI from the attackers session with the honest client instance. If the honest end user then fails to realize that they are not authorizing the attacker-controlled client instance (with which it started its request) but instead the honest client instance when interacting with the AS, the attacker's session with the honest client instance would be authorized. This would give the attacker access to the honest end user's resources that the honest client instance is authorized to access. However, if after theinteractioninteraction, the AS redirects the honest end user back to the client instance whose grant request the end user just authorized, the honest end user is redirected to the honest client instance. The honest client instance can then detect that the end user is not the party that started the request, since the request at the honest client instance was started by the attacker. This detection can prevent the attack. This is related to the discussion in <xref target="security-impersonation"/>, because again the attack can be prevented by the AS informing the user as much as possible about the client instance that is to be authorized.</t> <t>If the end user does not interact with the client instance through a web browser or the interaction start method does not use the same browser or device that the end user is interacting through (such as the launch of a second device through a scannable code or presentation of a usercode)code), the client instance will not be able to strongly associate an incoming HTTP request with an established session with the end user. This is also true when the<spanx style="verb">push</spanx><tt>push</tt> interaction finish method is used, since the HTTP request comes directly from the interaction component of the AS. In these circumstances, the client instance can at least ensure that the incoming HTTP request can be uniquely associated with an ongoing grant request by making the interaction finish callback URI unique for the grant when making the<xref target="request-interact-finish">interaction request</xref>.interaction request (<xref target="request-interact-finish"> </xref>). Mobile applications and other client instances that generally serve only a single end user at a time can use this unique incoming URL to differentiate between a legitimate incoming request and an attacker's stolen request.</t> </section> <sectionanchor="security-interact-hash"><name>Calculatinganchor="security-interact-hash"> <name>Calculating Interaction Hash</name> <t>While the use of GNAP's signing mechanisms and token-protected grant API provides significant security protections to the protocol, the interaction reference mechanism is susceptible to monitoring, capture, and injection by an attacker. To combat this, GNAP requires the calculation and verification of an interaction hash. A client instance might be tempted to skip this step, but doing so leaves the client instance open to injection and manipulation by an attacker that could lead to additional issues.</t> <t>The calculation of the interaction hash value provides defense in depth, allowing a client instance to protect itself from spurious injection of interaction references when using an interaction finish method. The AS is protected during this attack through the continuation access token being bound to the expected interaction reference, but without hash calculation, the attacker could cause the client to make an HTTP request on command, which could itself be manipulated -- for example, by including a malicious value in the interaction reference designed to attack the AS. With both of these in place, an attacker attempting to substitute the interaction reference is stopped in several places.</t><figure title="Figure 11: Interaction hash attack"><artset><artwork<figure> <name>Interaction Hash Attack</name> <artset> <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="448" width="456" viewBox="0 0 456 448" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,48 L 8,416" fill="none" stroke="black"/> <path d="M 64,48 L 64,416" fill="none" stroke="black"/> <path d="M 120,48 L 120,224" fill="none" stroke="black"/> <path d="M 120,256 L 120,272" fill="none" stroke="black"/> <path d="M 120,336 L 120,368" fill="none" stroke="black"/> <path d="M 120,400 L 120,416" fill="none" stroke="black"/> <path d="M 192,48 L 192,224" fill="none" stroke="black"/> <path d="M 192,256 L 192,272" fill="none" stroke="black"/> <path d="M 192,336 L 192,368" fill="none" stroke="black"/> <path d="M 192,400 L 192,416" fill="none" stroke="black"/> <path d="M 248,32 L 248,160" fill="none" stroke="black"/> <path d="M 248,224 L 248,304" fill="none" stroke="black"/> <path d="M 248,336 L 248,432" fill="none" stroke="black"/> <path d="M 320,32 L 320,160" fill="none" stroke="black"/> <path d="M 320,224 L 320,304" fill="none" stroke="black"/> <path d="M 320,336 L 320,432" fill="none" stroke="black"/> <path d="M 376,32 L 376,432" fill="none" stroke="black"/> <path d="M 448,32 L 448,432" fill="none" stroke="black"/> <path d="M 24,32 L 48,32" fill="none" stroke="black"/> <path d="M 136,32 L 176,32" fill="none" stroke="black"/> <path d="M 248,32 L 320,32" fill="none" stroke="black"/> <path d="M 376,32 L 448,32" fill="none" stroke="black"/> <path d="M 192,94 L 208,94" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 192,98 L 208,98" fill="none" stroke="black"/> <path d="M 224,94 L 240,94" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 224,98 L 240,98" fill="none" stroke="black"/> <path d="M 320,112 L 336,112" fill="none" stroke="black"/> <path d="M 352,112 L 368,112" fill="none" stroke="black"/> <path d="M 328,128 L 344,128" fill="none" stroke="black"/> <path d="M 360,128 L 376,128" fill="none" stroke="black"/> <path d="M 200,142 L 216,142" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 200,146 L 216,146" fill="none" stroke="black"/> <path d="M 232,142 L 248,142" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 232,146 L 248,146" fill="none" stroke="black"/> <path d="M 192,174 L 216,174" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 192,178 L 216,178" fill="none" stroke="black"/> <path d="M 232,174 L 368,174" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 232,178 L 368,178" fill="none" stroke="black"/> <path d="M 200,206 L 336,206" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 200,210 L 336,210" fill="none" stroke="black"/> <path d="M 352,206 L 376,206" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 352,210 L 376,210" fill="none" stroke="black"/> <path d="M 64,238 L 88,238" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 64,242 L 88,242" fill="none" stroke="black"/> <path d="M 104,238 L 240,238" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 104,242 L 240,242" fill="none" stroke="black"/> <path d="M 320,256 L 336,256" fill="none" stroke="black"/> <path d="M 352,256 L 368,256" fill="none" stroke="black"/> <path d="M 328,272 L 344,272" fill="none" stroke="black"/> <path d="M 360,272 L 376,272" fill="none" stroke="black"/> <path d="M 72,286 L 216,286" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 72,290 L 216,290" fill="none" stroke="black"/> <path d="M 232,286 L 248,286" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 232,290 L 248,290" fill="none" stroke="black"/> <path d="M 64,318 L 88,318" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 64,322 L 88,322" fill="none" stroke="black"/> <path d="M 104,318 L 368,318" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 104,322 L 368,322" fill="none" stroke="black"/> <path d="M 72,350 L 88,350" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 72,354 L 88,354" fill="none" stroke="black"/> <path d="M 104,350 L 120,350" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 104,354 L 120,354" fill="none" stroke="black"/> <path d="M 64,382 L 88,382" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 64,386 L 88,386" fill="none" stroke="black"/> <path d="M 104,382 L 240,382" fill="none"stroke="black"/><pathstroke="black"/> <path d="M 104,386 L 240,386" fill="none" stroke="black"/> <path d="M 320,400 L 336,400" fill="none" stroke="black"/> <path d="M 352,400 L 368,400" fill="none" stroke="black"/> <path d="M 24,432 L 48,432" fill="none" stroke="black"/> <path d="M 136,432 L 176,432" fill="none" stroke="black"/> <path d="M 248,432 L 320,432" fill="none" stroke="black"/> <path d="M 376,432 L 448,432" fill="none" stroke="black"/> <path d="M 24,32 C 15.16936,32 8,39.16936 8,48" fill="none" stroke="black"/> <path d="M 48,32 C 56.83064,32 64,39.16936 64,48" fill="none" stroke="black"/> <path d="M 136,32 C 127.16936,32 120,39.16936 120,48" fill="none" stroke="black"/> <path d="M 176,32 C 184.83064,32 192,39.16936 192,48" fill="none" stroke="black"/> <path d="M 24,432 C 15.16936,432 8,424.83064 8,416" fill="none" stroke="black"/> <path d="M 48,432 C 56.83064,432 64,424.83064 64,416" fill="none" stroke="black"/> <path d="M 136,432 C 127.16936,432 120,424.83064 120,416" fill="none" stroke="black"/> <path d="M 176,432 C 184.83064,432 192,424.83064 192,416" fill="none" stroke="black"/> <polygon class="arrowhead" points="376,400 364,394.4 364,405.6" fill="black" transform="rotate(0,368,400)"/> <polygon class="arrowhead" points="376,320 364,314.4 364,325.6" fill="black" transform="rotate(0,368,320)"/> <polygon class="arrowhead" points="376,256 364,250.4 364,261.6" fill="black" transform="rotate(0,368,256)"/> <polygon class="arrowhead" points="376,176 364,170.4 364,181.6" fill="black" transform="rotate(0,368,176)"/> <polygon class="arrowhead" points="376,112 364,106.4 364,117.6" fill="black" transform="rotate(0,368,112)"/> <polygon class="arrowhead" points="336,272 324,266.4 324,277.6" fill="black" transform="rotate(180,328,272)"/> <polygon class="arrowhead" points="336,128 324,122.4 324,133.6" fill="black" transform="rotate(180,328,128)"/> <polygon class="arrowhead" points="248,384 236,378.4 236,389.6" fill="black" transform="rotate(0,240,384)"/> <polygon class="arrowhead" points="248,240 236,234.4 236,245.6" fill="black" transform="rotate(0,240,240)"/> <polygon class="arrowhead" points="248,96 236,90.4 236,101.6" fill="black" transform="rotate(0,240,96)"/> <polygon class="arrowhead" points="208,208 196,202.4 196,213.6" fill="black" transform="rotate(180,200,208)"/> <polygon class="arrowhead" points="208,144 196,138.4 196,149.6" fill="black" transform="rotate(180,200,144)"/> <polygon class="arrowhead" points="80,352 68,346.4 68,357.6" fill="black" transform="rotate(180,72,352)"/> <polygon class="arrowhead" points="80,288 68,282.4 68,293.6" fill="black" transform="rotate(180,72,288)"/> <g class="text"> <text x="36" y="52">User</text> <text x="156" y="52">Attacker</text> <text x="284" y="52">Client</text> <text x="412" y="52">AS</text> <text x="284" y="68">Instance</text> <text x="216" y="100">1</text> <text x="344" y="116">2</text> <text x="352" y="132">3</text> <text x="224" y="148">4</text> <text x="224" y="180">5</text> <text x="248" y="196">|</text> <text x="320" y="196">|</text> <text x="344" y="212">6</text> <text x="96" y="244">A</text> <text x="344" y="260">B</text> <text x="352" y="276">C</text> <text x="224" y="292">D</text> <text x="120" y="308">|</text> <text x="192" y="308">|</text> <text x="96" y="324">E</text> <text x="96" y="356">7</text> <text x="96" y="388">F</text> <text x="344" y="404">G</text> </g> </svg></artwork><artwork</artwork> <artwork type="ascii-art"><![CDATA[ .----. .------. +--------+ +--------+ | User | |Attacker| | Client | | AS | | | | | |Instance| | | | | | | | | | | | | | +=(1)=>| | | | | | | | | +-(2)->| | | | | | | |<-(3)-+ | | | | |<=(4)=+ | | | | | | | | | | | | | | +==(5)================>| | | | | | | | | | | | | |<================(6)==+ | | | | | | | | | | +==(A)================>| | | | | | | | | +-(B)->| | | | | | | |<-(C)-+ | | |<=================(D)=+ | | | | | | | | | | | | +==(E)================================>| | | | | | | | | | | |<=(7)=+ | | | | | | | | | | | | | | +==(F)================>| | | | | | | | | +-(G)->| | | | | | | | | | `----` `------` +--------+ +--------+]]></artwork></artset></figure> <t><list style="symbols">]]></artwork> </artset> </figure> <ul spacing="normal"> <li> <t>Prerequisites: The client instance can allow multiple end users to access the same AS. The attacker is attempting to associate their rights with the target user's session.</t> </li> <li> <t>(1) The attacker starts a session at the client instance.</t> </li> <li> <t>(2) The client instance creates a grant request with nonce CN1.</t> </li> <li> <t>(3) The AS responds to the grant request with a need to interact, nonce SN1, and a continuation token, CT1.</t> </li> <li> <t>(4) The client instructs the attacker to interact at the AS.</t> </li> <li> <t>(5) The attacker interacts at the AS.</t> </li> <li> <t>(6) The AS completes the interact finish with interactrefreference IR1 and interact hash IH1 calculated from (CN1 + SN1 + IR1 + AS). The attacker prevents IR1 from returning to the client instance.</t> </li> <li> <t>(A) The target user starts a session at the client instance.</t> </li> <li> <t>(B) The client instance creates a grant request with nonce CN2.</t> </li> <li> <t>(C) The AS responds to the grant request with a need to interact, nonce SN2, and a continuation token, CT2.</t> </li> <li> <t>(D) The client instance instructs the user to interact at the AS.</t> </li> <li> <t>(E) The target user interacts at the AS.</t> </li> <li> <t>(7) Before the target user can complete their interaction, the attacker delivers their own interactrefreference IR1 into the user's session. The attacker cannot calculate the appropriate hash because the attacker does not have access to CN2 and SN2.</t> </li> <li> <t>(F) The target user triggers the interaction finish in their own session with the attacker's IR1.</t> </li> <li> <t>(G) If the client instance is checking the interaction hash, the attack stops here because the hash calculation of (CN2 + SN2 + IR1 + AS) will fail. If the client instance does not check the interaction hash, the client instance will be tricked into submitting the interaction reference to the AS. Here, the AS will reject the interaction request because it is presented against CT2 and not CT1 as expected. However, an attacker who has potentially injected CT1 as the value of CT2 would be able to continue the attack.</t></list></t></li> </ul> <t>Even with additional checks in place, client instances using interaction finish mechanisms are responsible for checking the interaction hash to provide security to the overall system.</t> </section> <sectionanchor="security-client-storage"><name>Storageanchor="security-client-storage"> <name>Storage of InformationDuringduring Interaction and Continuation</name> <t>When starting an interactive grant request, a client application has a number of protocol elements that it needs to manage, including nonces, references, keys, access tokens, and other elements. During the interaction process, the client instance usually hands control of the user experience over to another component, be it the system browser, another application, or some action the resource owner is instructed to take on another device. In order for the client instance to make its continuation call, it will need to recall all of these protocol elements at a future time.UsuallyUsually, this means the client instance will need to store these protocol elements in some retrievable fashion.</t> <t>If the security protocol elements are stored on the end user's device, such as in browser storage or in local application data stores, capture and exfiltration of this information could allow an attacker to continue a pending transaction instead of the client instance. Client software can make use of secure storage mechanisms, including hardware-based key and data storage, to prevent such exfiltration.</t> <t>Note that in GNAP, the client instance has to choose its interaction finish URI prior to making the first call to the AS. As such, the interaction finish URI will often have a unique identifier for the ongoing request, allowing the client instance to access the correct portion of its storage. Since this URI is passed to other parties and often used through a browser, this URI should not contain any security-sensitive information that would be valuable to an attacker, such as any token identifier, nonce, or user information. Instead, a cryptographically random value is suggested, and that value should be used to index into a secure session or storage mechanism.</t> </section> <sectionanchor="security-continuation"><name>Denialanchor="security-continuation"> <name>Denial of Service (DoS) through Grant Continuation</name> <t>When a client instance starts off an interactive process, it will eventually need to continue the grant request in a subsequent message to the AS. It's possible for a naive client implementation to continuously send continuation requests to the AS while waiting for approval, especially if no interaction finish method is used. Such constant requests could overwhelm the AS's ability to respond to both these and other requests.</t> <t>To mitigate this for well-behaved client software, the continuation response contains a<spanx style="verb">wait</spanx><tt>wait</tt> parameter that is intended to tell the client instance how long it should wait until making its next request. This value can be used to back off client software that is checking too quickly by returning increasing wait times for a single client instance.</t> <t>If client software ignores the<spanx style="verb">wait</spanx><tt>wait</tt> value and makes its continuation calls tooquickly,quickly or if the client software assumes the absence of the<spanx style="verb">wait</spanx><tt>wait</tt> values means it should poll immediately, the AS can choose to return errors to the offending client instance, including possibly canceling the ongoing grant request. With well-meaning clientsoftwaresoftware, these errors can indicate a need to change the client software's programmed behavior.</t> </section> <sectionanchor="security-random-exhaustion"><name>Exhaustionanchor="security-random-exhaustion"> <name>Exhaustion of Random Value Space</name> <t>Several parts of the GNAP process make use of unguessable randomized values, such as nonces, tokens, user codes, and randomized URIs. Since these values are intended to be unique, a sufficiently powerful attacker could make a large number of requests to trigger generation of randomized values in an attempt to exhaust the random number generation space. While this attack is particularly applicable to the AS, client software could likewise be targeted by an attacker triggering new grant requests against an AS.</t> <t>To mitigate this, software can ensure that its random values are chosen from a significantly large pool so that exhaustion of that pool is prohibitive for an attacker. Additionally, the random values can be time-boxed in such a wayasthat their validity windows are reasonably short. Since many of the random values used within GNAP are used within limited portions of the protocol, it is reasonable for a particular random value to be valid for only a small amount of time. For example, the nonces used for interaction finish hash calculation need only to be valid while the client instance is waiting for the finish callback and can be functionally expired when the interaction has completed. Similarly, artifacts like access tokens and the interaction reference can be limited to have lifetimes tied to their functional utility. Finally, each different category of artifact (nonce, token, reference, identifier, etc.) can be generated from a separate random pool of values instead of a single global value space.</t> </section> <sectionanchor="security-front-channel"><name>Front-channelanchor="security-front-channel"> <name>Front-Channel URIs</name> <t>Some interaction methods in GNAP make use of URIs accessed through the end user's browser, known collectively as front-channel communication. These URIs are most notably present in the<spanx style="verb">redirect</spanx><tt>redirect</tt> interaction<spanx style="verb">start</spanx><tt>start</tt> method and the<spanx style="verb">redirect</spanx><tt>redirect</tt> interaction<spanx style="verb">finish</spanx><tt>finish</tt> mode. Since these URIs are intended to be given to the end user, the end user and their browser will be subjected to anything hosted at that URI including viruses, malware, and phishing scams. This kind of risk is inherent to all redirection-based protocols, includingGNAPGNAP, when used in this way.</t> <t>When talking to a new or unknown AS, a client instance might want to check the URI from the interaction<spanx style="verb">start</spanx><tt>start</tt> against a blocklist and warn the end user before redirecting them. Many client instances will provide an interstitial message prior to redirection in order to prepare the user for control of the user experience being handed to the domain of the AS, and such a method could be used to warn the user of potentialthreats. Forthreats (for instance, a rogue AS impersonating a well-known serviceprovider.provider). Client software can also prevent this by managing an allowlist of known and trustedAS's.</t>ASes.</t> <t>Alternatively, an attacker could start a GNAP request with a known and trusted AS but include their own attack site URI as the callback for the redirect<spanx style="verb">finish</spanx><tt>finish</tt> method. The attacker would then send the interaction<spanx style="verb">start</spanx><tt>start</tt> URI to the victim and get them to click on it. Since the URI is at the known AS, the victim is inclined to do so. The victim will then be prompted to approve the attacker's application, and in mostcircumstancescircumstances, the victim will then be redirected to the attacker's site whether or not the user approved the request. The AS could mitigate this partially by using a blocklist and allowlist of interaction<spanx style="verb">finish</spanx><tt>finish</tt> URIs during the client instance's initial request, but this approach can be especially difficult if the URI has any dynamic portion chosen by the client software. The AS can couple these checks with policies associated with the client instance that has been authenticated in the request. If the AS has any doubt about the interaction finish URI, the AS can provide an interstitial warning to the end user before processing the redirect.</t> <t>Ultimately, all protocols that use redirect-based communication through the user's browser are susceptible to having an attacker try to co-opt one or more of those URIs in order to harm the user. It is the responsibility of the AS and the client software to provide appropriate warnings, education, and mitigation to protect end users.</t> </section> <sectionanchor="security-assertions"><name>Processinganchor="security-assertions"> <name>Processing Assertions</name> <t>Identity assertions can be used in GNAP to convey subject information, both from the AS to the client instance in a<xref target="response-subject">response</xref>response (<xref target="response-subject"> </xref>) and from the client instance to the AS in a<xref target="request-subject">request</xref>.request (<xref target="request-subject"> </xref>). In both of these circumstances, when an assertion is passed in GNAP, the receiver of the assertion needs to parse and process the assertion. As assertions are complex artifacts with their own syntax and security, special care needs to be taken to prevent the assertion values from being used as an attack vector.</t> <t>All assertion processing needs to account for the security aspects of the assertion format in use. In particular, the processor needs to parse the assertion from a JSON stringobject,object and apply the appropriate cryptographic processes to ensure the integrity of the assertion.</t> <!-- [rfced] Would it be helpful to include a reference entry for "the XML standard" here? If so, please provide the reference entry. Original: There are many well-known security vulnerabilities in XML parsers, and the XML standard itself can be attacked through the use of processing instructions and entity expansions to cause problems with the processor. --> <t>For example, when SAML 2 assertions are used, the receiver has to parse an XML document. There are many well-known security vulnerabilities in XML parsers, and the XML standard itself can be attacked through the use of processing instructions and entity expansions to cause problems with the processor. Therefore, any system capable of processing SAML 2 assertions also needs to have a secure and correct XML parser. In addition to this, the SAML 2 specification uses XML Signatures, which have their own implementation problems that need to be accounted for. Similar requirements exist for OpenID Connect's ID token, which is based on theJSON Web Token (JWT)JWT format and the relatedJSON Object Signing And Encryption (JOSE)JOSE cryptography suite.</t> </section> <sectionanchor="security-cuckoo"><name>Stolenanchor="security-cuckoo"> <name>Stolen Token Replay</name> <t>If a client instance can request tokens at multipleAS's,ASes and the client instance uses the same keys to make its requests across those differentAS's,ASes, then it is possible for an attacker to replay a stolen token issued by an honest AS from a compromised AS, thereby binding the stolen token to the client instance's key in a different context. The attacker can manipulate the client instance into using the stolen token at an RS, particularly at an RS that is expecting a token from the honest AS. Since the honest AS issued the token and the client instance presents the token with its expected bound key, the attack succeeds.</t> <t>This attack has several preconditions. In this attack, the attacker does not need access to the client instance's key and cannot use the stolen token directly at the RS, but the attacker is able to get the access token value in some fashion. The client instance also needs to be configured to talk to multipleAS's,ASes, including the attacker's controlled AS. Finally, the client instance needs to be able to be manipulated by the attacker to call the RS while using a token issued from the stolen AS. The RS does not need to be compromised or made to trust the attacker's AS.</t> <t>To protect against this attack, the client instance can use a different key for each AS that it talks to. Since the replayed token will be bound to the key used at the honest AS, the uncompromised RS will reject the call since the client instance will be using the key used at the attacker's AS instead with the same token. When the MTLS key proofing method is used, a client instance can use self-signed certificates to use a different key for each AS that it talks to, as discussed in <xref target="security-mtls-patterns"/>.</t> <t>Additionally, the client instance can keep a strong association between the RS and a specific AS that it trusts to issue tokens for that RS. This strong binding also helps against some forms of<xref target="security-mixup">ASAS mix-upattacks</xref>.attacks (<xref target="security-mixup"> </xref>). Managing this binding is outside the scope of GNAP core, but it can be managed either as a configuration element for the client instance or dynamically through<xref target="rs-request-without-token">discoveringdiscovering the AS from theRS</xref>.</t> <t>TheRS (<xref target="rs-request-without-token"> </xref>).</t> <!-- [rfced] The following sentence appears in Section 13.31 ("Stolen Token Replay"). [HELMSCHMIDT2022] describes three attacks, but none use the term "stolen token". Would clarification be helpful? Perhaps an indication of the attack or a pointer to a specific section in [HELMSCHMIDT2022] would help readers. Original: The details of this attack are available in<xref target="HELMSCHMIDT2022"/>[HELMSCHMIDT2022] with additional discussion and considerations. --> <t>The details of this attack, with additional discussion andconsiderations.</t>considerations, are available in <xref target="HELMSCHMIDT2022"/>.</t> </section> <sectionanchor="security-stateless-tokens"><name>Self-containedanchor="security-stateless-tokens"> <name>Self-Contained Stateless Access Tokens</name> <t>The contents and format of the access token are at the discretion of theAS,AS and are opaque to the client instance within GNAP. As discussed in the companion document, <xref target="I-D.ietf-gnap-resource-servers"/>, the AS and RS can make use of stateless access tokens with an internal structure and format. These access tokens allow an RS to validate the token without having to make any external calls at runtime, allowing for benefits in some deployments, the discussion of whichareis outside the scope of this specification.</t> <t>However, the use of such self-contained access tokens has an effect on the ability of the AS to provide certain functionality defined within this specification. Specifically, since the access token is self-contained, it is difficult or impossible for an AS to signal to allRS'sRSs within an ecosystem when a specific access token has been revoked. Therefore, an AS in such an ecosystem should probably not offer token revocation functionality to client instances, since the client instance's calls to such an endpointisare effectively meaningless. However, a client instance calling the token revocation function will also throw out its copy of the token, so such a placebo endpoint might not be completely meaningless. Token rotation is similarly difficult because the AS has to revoke the old access token after a rotation call has been made. If the access tokens are completely self-contained and non-revocable, this means that there will be a period of time during which both the old and new access tokens are valid and usable, which is an increased security risk for the environment.</t> <t>These problems can be mitigated by keeping the validity time windows of self-contained access tokens reasonably short, limiting the time after a revocation event that a revoked token could be used. Additionally, the AS could proactively signal toRS'sRSs under its control identifiers for revoked tokens that have yet to expire. This type of information push would be expected to be relatively small and infrequent, and its implementation is outside the scope of this specification.</t> </section> <sectionanchor="security-network-management"><name>Networkanchor="security-network-management"> <name>Network Problems and Token and Grant Management</name> <t>If a client instance makes a call to rotate an access token but the network connection is dropped before the client instance receives the response with the new access token, the system as a whole can end up in an inconsistent state, where the AS has already rotated the old access token and invalidated it, but the client instance only has access to the invalidated access token and not the newly rotated token value. If the client instance retries the rotation request, it would fail because the client is no longer presenting a valid and current access token. A similar situation can occur during grant continuation, where the same client instance calls to continue or update a grant request without successfully receiving the results of the update.</t> <t>To combat this, both<xref target="continue-request">grant Management</xref> and <xref target="token-management">token management</xref>grant management (<xref target="continue-request"> </xref>) and token management (<xref target="token-management"> </xref>) can be designed to be idempotent, where subsequent calls to the same function with the same credentials are meant to produce the same results. For example, multiple calls to rotate the same access token need to result in the same rotated token value, within a reasonable time window.</t> <t>In practice, an AS can holdon toonto an old token value for such limited purposes. For example, to support rotating access tokens over unreliable networks, the AS receives the initial request to rotate an access token and creates a new token value and returns it. The AS also marks the old token value as having been used to create thenewly-rotatednewly rotated token value. If the AS sees the old token value within a small enough time window, such as a few seconds since the first rotation attempt, the AS can return the same rotated access token value. Furthermore, once the system has seen thenewly-rotatednewly rotated token in use, the original token can be discarded because the client instance has proved that it did receive the token. The result of this is a system that is eventually self-consistent without placing an undue complexity burden on the client instance to manage problematic networks.</t> </section> <sectionanchor="security-ssrf"><name>Server-sideanchor="security-ssrf"> <name>Server-Side Request Forgery (SSRF)</name> <t>There are several places within GNAP where a URI can be given to apartyparty, causing it to fetch that URI during normal operation of the protocol. If an attacker is able to control the value of one of these URIs within the protocol, the attacker could cause the target system to execute a request on a URI that is within reach of the target system but normally unavailable to the attacker.For example,Examples include an attacker sending a URL of<spanx style="verb">http://localhost/admin</spanx><tt>http://localhost/admin</tt> to cause the server to access an internal function onitself,itself or<spanx style="verb">https://192.168.0.14/</spanx><tt>https://192.168.0.14/</tt> to call a service behind a firewall. Even if the attacker does not gain access to the results of the call, the side effects of such requests coming from a trusted host can be problematic to the security and sanctity of such otherwise unexposed endpoints. This can be particularly problematic if such a URI is used to call non-HTTP endpoints, such as remote code execution services local to the AS.</t> <t>In GNAP, the most vulnerable place in the core protocol is the<xref target="interaction-pushback">push-basedpush-based post-interaction finishmethod</xref>,method (<xref target="interaction-pushback"> </xref>), as the client instance is less trusted than the AS and can use this method to make the AS call an arbitrary URI. While it is not required by the protocol, the AS can fetch otherclient-instance providedURIs provided by the client instance, such as the logo image or home page, for verification or privacy-preserving purposes before displaying them to the resource owner as part of a consent screen. Even if the AS does not fetch these URIs, their use in GNAP's normal operation could cause an attack against the end user's browser as it fetches these same attack URIs. Furthermore, extensions to GNAP that allow or require URI fetch could also be similarly susceptible, such as a system for having the AS fetch a client instance's keys from a presented URI instead of the client instance presenting the key by value. Such extensions are outside the scope of this specification, but any system deploying such an extension would need to be aware of this issue.</t> <!-- [rfced] Should "push based interaction finish" be updated to "push-based interaction finish method" (with "method")? Or is the current okay? Original: For example, an AS that supports the push based interaction finish can compare the callback URI in the interaction request to a known URI for a pre-registered client instance, or it can ensure that the URI is not on a blocklist of sensitive URLs such as internal network addresses. Perhaps: For example, an AS that supports the push-based interaction finish method can compare the callback URI in the interaction request to a known URI for a pre-registered client instance, or it can ensure that the URI is not on a blocklist of sensitive URLs such as internal network addresses. --> <t>To help mitigate this problem, similar approachesto protectingthat protect parties against<xref target="security-front-channel">malicious redirects</xref>malicious redirects (<xref target="security-front-channel"> </xref>) can be used. For example, all URIs that can result in a direct request being made by a party in the protocol can be filtered through an allowlist or blocklist. For example, an AS that supports the<spanx style="verb">push</spanx> based<tt>push</tt>-based interaction<spanx style="verb">finish</spanx><tt>finish</tt> can compare the callback URI in the interaction request to a known URI for a pre-registered client instance, or it can ensure that the URI is not on a blocklist of sensitive URLs such as internal network addresses. However, note that because these types of calls happen outside of the view of human interaction, it is not usually feasible to provide notification and warning to someone before the request needs to be executed, as is the case with redirection URLs. As such, SSRF is somewhat more difficult to manage at runtime, and systems should generally refuse to fetch a URI if unsure.</t> </section> <sectionanchor="security-multiple-key-formats"><name>Multipleanchor="security-multiple-key-formats"> <name>Multiple Key Formats</name> <t>All keys presented by value are only allowed to be inonlya single format. While it would seem beneficial to allow keys to be sent in multipleformats,formats in case the receiver doesn't understand one or more of the formats used, therewould beare security issues with such a feature. If multiple keys formatswereare allowed, receivers of these key definitions would need to be able to make sure that it's the same key represented in each field and not simply use one of the key formats without checking for equivalence. If equivalencewereis not carefully checked, it is possible for an attacker to insert their own key into one of the formats without needing to have control over the other formats. This could potentially lead to a situation where one key is used by part of the system (such as identifying the client instance) and a different key in a different format in the same message is used for other things (such as calculating signature validity). However, in such cases, it is impossible for the receiver to ensure that all formats contain the same key information since it is assumed that the receiver cannot understand all of the formats.</t> <t>To combat this, all keys presented by value have to be in exactly one supported format known by the receiver as discussed in <xref target="key-format"/>. In most cases, a client instance is going to be configured with its keys in a single format, and it will simply present that formatas-isas is to the AS in its request. A client instance capable of multiple formats can use<xref target="discovery">AS discovery</xref>AS discovery (<xref target="discovery"> </xref>) to determine which formats are supported, if desired. An AS should be generous in supporting many different key formats to allow different types of client software and client instance deployments. An AS implementation should try to support multiple formats to allow a variety of client software to connect.</t> </section> <sectionanchor="security-async"><name>Asynchronousanchor="security-async"> <name>Asynchronous Interactions</name> <t>GNAP allows the RO to be contacted by the AS asynchronously, outside the regular flow of the protocol. This allows for some advanced use cases, such as cross-user authentication or information release, but such advanced use cases have some distinct issues that implementors need to be fully aware of before using these features.</t> <t>First, in many applications, the return ofasubject information to the client instance could indicate to the client instance that theend-userend user is the party represented by that information, functionally allowing theend-userend user to authenticate to the client application. While the details of a fully functional authentication protocol are outside the scope of GNAP, it is a common exercise for a client instance tobe requestingrequest information about the end user. This is facilitated bytheseveral<xref target="interaction-start">interaction methods</xref>interaction methods (<xref target="interaction-start"> </xref>) defined in GNAP that allow the end user to begin interaction directly with the AS. However, when the subject of the information is intentionally not theend-user,end user, the client application will need some way to differentiate between requests for authentication of the end user and requests for information about a different user. Confusing these states could lead to an attacker having their account associated with a privileged user. Client instances can mitigate this by having distinct code paths for primaryend userend-user authentication and for requesting subject information about secondary users, such as in a call center. In such use cases, the client software used by the resource owner (the caller) and theend-userend user (the agent) are generally distinct, allowing the AS to differentiate between the agent's corporate device making the request and the caller's personal device approving the request.</t> <t>Second,RO's interactingROs that interact asynchronously do not usually have the same context as an end user in an application attempting to perform the task needing authorization. As such, the asynchronous requests for authorization coming to the RO from the AS might have very little to do with what the RO is doing at the time. This situation can consequently lead to authorization fatigue on the part of the RO, where any incoming authorization request is quickly approved and dispatched without the RO making a proper verification of the request. An attacker can exploit this fatigue and get the RO to authorize the attacker's system for access. To mitigate this, AS systems deploying asynchronous authorization should only prompt the RO when the RO is expecting such a request, and significant user experience engineering efforts need to be employed to ensure that the RO can clearly make the appropriate security decision. Furthermore, auditcapability,capability and the ability to undo access decisions that may beongoing, isongoing are particularly important in the asynchronous case.</t> </section> <sectionanchor="security-compromised-rs"><name>Compromisedanchor="security-compromised-rs"> <name>Compromised RS</name> <t>An attacker may aim to gain access to confidential or sensitive resources. The measures for hardening and monitoring resource server systems (beyond protection with access tokens)isare out of the scope of this document, but the use of GNAP to protect a system does not absolve the resource server of following best practices. GNAP generally considers that a breach canoccur,occur and therefore advises to prefer key-bound tokens whenever possible, which at least limits the impact of access token leakage by a compromised or malicious RS.</t> </section> <sectionanchor="security-as-keys"><name>AS-Providedanchor="security-as-keys"> <name>AS-Provided Token Keys</name> <t>While the most commontoken issuancetoken-issuance pattern is to bind the access token to the client instance's presented key, it is possible for the AS to provide a binding key along with an access token, as shown by the<spanx style="verb">key</spanx><tt>key</tt> field of the token response in <xref target="response-token-single"/>. This practice allows for an AS to generate and manage the keys associated with tokens independently of the keys known to client instances.</t> <t>If the key material is returned by value from the AS, then the client instance will simply use this key value when presenting the token. This can be exploited by an attacker to issue a compromised token to an unsuspecting client, assuming that the client instance trusts the attacker's AS to issue tokens for the target RS. In this attack, the attacker first gets a token bound to a key under the attacker's control. This token is likely bound to an authorization or account controlled by the attacker. The attacker thenre-issuesreissues that same token to the client instance, this time acting as an AS. The attacker can return their own key to the client instance, tricking the client instance into using the attacker's token. Such an attack is also possible when the key is returned by reference, if the attacker is able to provide a reference meaningful to the client instance that references a key under the attacker's control. This substitution attack is similar to some of the main issues found with bearer tokens as discussed in <xref target="security-bearer-tokens"/>.</t><t>Returning<!-- [rfced] Would removing "only" (2 instances) and "further" (1 instance) improve readability of this sentence while maintaining the intended meaning? Original: Returning a key with an access token should be limited to only circumstances where both the client and AS can be verified to be honest, and further only when the tradeoff of not using a client instance's own keys is worth the additional risk. Perhaps: Returning a key with an access token should be limited to circumstances where both the client and AS can be verified to be honest and when the trade-off of not using a client instance's own keys is worth the additional risk. --> <t>Returning a key with an access token should be limited to only circumstances where both the client and AS can be verified to be honest, and further only when the trade-off of not using a client instance's own keys is worth the additional risk.</t> </section> </section> <sectionanchor="privacy"><name>Privacyanchor="privacy"> <name>Privacy Considerations</name> <t>The privacy considerations in this section are modeled after the list of privacy threats in<xref target="RFC6973"/>,"Privacy Considerations for InternetProtocols",Protocols" <xref target="RFC6973"/> and either explain how these threats are mitigated or advise how the threats relate to GNAP.</t> <sectionanchor="surveillance"><name>Surveillance</name>anchor="surveillance"> <name>Surveillance</name> <t>Surveillance is the observation or monitoring of an individual's communications or activities. Surveillance can be conducted by observers or eavesdroppers at any point along the communications path.</t> <t>GNAP assumes the TLS protection used throughout the spec is intact. Without the protection of TLS, there are many points throughout the use of GNAP thatwouldcould lead to possible surveillance. Even with the proper use of TLS, surveillance could occur by several parties outside of the TLS-protected channels, as discussed in thesectionssubsections below.</t> <sectionanchor="surveillance-by-the-client"><name>Surveillanceanchor="surveillance-by-the-client"> <name>Surveillance by the Client</name> <t>The purpose of GNAP is to authorize clients to be able to access information on behalf of a user. So while it is expected that the client may be aware of the user's identity as well as data being fetched for that user, in somecasescases, the extent of the client may be beyond what the user is aware of. For example, a client may be implemented as multiple distinct pieces of software, such as a logging service or a mobileappapplication that reports usage data to an external backend service. Each of these pieces could gain information about the user without the user being aware of this action.</t> <t>When the client software uses a hosted asset for its components, such as its logo image, the fetch of these assets can reveal user actions to the host. If the AS presents the logo URI to the resource owner in a browser page, the browser will fetch the logo URL from the authorization screen. This fetch will tell the host of the logo image that someone is accessing an instance of the client software and requesting access for it. This is particularly problematic when the host of the asset is not the client software itself, such as when a content delivery network is used.</t> </section> <sectionanchor="surveillance-by-the-authorization-server"><name>Surveillanceanchor="surveillance-by-the-authorization-server"> <name>Surveillance by the Authorization Server</name> <t>The role of the authorization server is to manage the authorization of client instances to protect access to the user's data. In this role, the authorization server is by definition aware of each authorization of a client instance by a user. When the authorization server shares user information with the client instance, it needs to make sure that it has the permission from that user to do so.</t> <t>Additionally, as part of the authorization grant process, the authorization server may be aware of which resource servers the client intends to use an access token at. However, it is possible to design a system using GNAP in which this knowledge is not made available to the authorization server, such as by avoiding the use of the<spanx style="verb">locations</spanx><tt>locations</tt> object in the authorization request.</t> <t>If the authorization server's implementation of access tokens is such that it requires a resource servercall backcallback to the authorization server to validate them, then the authorization server will be aware of which resource servers are actively in use and by which users andwhichclients. To avoid this possibility, the authorization server would need to structure access tokens in such a way that they can be validated by the resource server without notifying the authorization server that the token is being validated.</t> </section> </section> <sectionanchor="stored-data"><name>Storedanchor="stored-data"> <name>Stored Data</name> <!-- [rfced] We updated the text starting with "that any party..." for clarity. Please let us know any concerns. Original: Naturally it is possible that any party is storing information for longer than technically necessary of the protocol mechanics (such as audit logs, etc). Updated: Naturally, it is possible for any party to store information related to protocol mechanics (such as audit logs, etc.) for longer than is technically necessary. --> <t>Several parties in the GNAP process are expected to persist data at least temporarily, if not semi-permanently, for the normal functioning of the system. If compromised, this could lead to exposure of sensitive information. This section documents the potentially sensitive information each party in GNAP is expected to store for normal operation.NaturallyNaturally, it is possiblethatfor any partyis storingto store informationfor longer than technically necessary of therelated to protocol mechanics (such as audit logs,etc).</t>etc.) for longer than is technically necessary. </t> <t>The authorization server is expected to store subject identifiers for users indefinitely, in order to be able to include them in the responses to clients. The authorization server is also expected to store client key identifiers associated with display information about theclientclient, such as its name and logo.</t> <t>The client is expected to store its client instance key indefinitely, in order to authenticate to the authorization server for the normal functioning of the GNAP flows. Additionally, the client will be temporarily storing artifacts issued by the authorization server during a flow, and these artifacts ought to be discarded by the client when the transaction is complete.</t> <t>The resource server is not required to store any state for its normal operation, as far as its part in implementing GNAP. Depending on the implementation of access tokens, the resource server may need to cache public keys from the authorization server in order to validate access tokens.</t> </section> <sectionanchor="intrusion"><name>Intrusion</name>anchor="intrusion"> <name>Intrusion</name> <t>Intrusion refers to the ability of various parties to send unsolicited messages or cause denial of service for unrelated parties.</t> <t>If the resource owner is different from the end user, there is an opportunity for the end user to cause unsolicited messages to be sent to the resource owner if the system prompts the resource owner for consent when an end user attempts to access their data.</t> <t>The format and contents of subject identifiers are intentionally not defined by GNAP. If the authorization server uses values for subject identifiers that are also identifiers for communicationchannels, (e.g.channels (e.g., an email address or phone number), this opens up the possibility for a client to learn this information when it was not otherwise authorized to access this kind of data about the user.</t> </section> <sectionanchor="correlation"><name>Correlation</name>anchor="correlation"> <name>Correlation</name> <t>The threat of correlation is the combination of various pieces of information related to an individual in a way that defies their expectations of what others know about them.</t> <sectionanchor="privacy-correlation-client"><name>Correlationanchor="privacy-correlation-client"> <name>Correlation by Clients</name> <t>The biggest risk of correlation in GNAP is when an authorization server returnsstablestable, consistent user identifiers to multiple different applications. In this case, applications created by different parties would be able to correlate these user identifiers out of band in order to know which users they have in common.</t> <t>The most common example of this in practice is tracking for advertising purposes, such that a client shares their list of user IDs with an ad platform that is then able to retarget ads to applications created by other parties. In contrast, a positive example of correlation is a corporate acquisition where two previously unrelated clients now do need to be able to identify the same user between the two clients, such as when software systems are intentionally connected by the end user.</t> <t>Another means of correlation comes from the use of<xref target="rs-request-without-token">RS-first discovery</xref>.RS-first discovery (<xref target="rs-request-without-token"> </xref>). A client instanceknowingthat knows nothing other than an RS's URL could make an unauthenticated call to the RS and learn which AS protects the resources there. If the client instance knows something about the AS, such as it being a single-user AS or belonging to a specific organization, the client instance could, through association, learn things about the resource without ever gaining access to the resource itself.</t> </section> <sectionanchor="correlation-by-resource-servers"><name>Correlationanchor="correlation-by-resource-servers"> <name>Correlation by Resource Servers</name> <t>Unrelated resource servers also have an opportunity to correlate users if the authorization server includes stable user identifiers in access tokens or in access token introspection responses.</t> <t>In somecasescases, a resource server may not actually need to be able to identifyusers,users (such as a resource server providing access to a company cafeteriamenumenu, which only needs to validate whether the user is a current employee), so authorization servers should be thoughtful of when user identifiers are actually necessary to communicate to resource servers for the functioning of the system.</t> <t>However, note that the lack of inclusion of a user identifier in an access token may be a risk if there is a concern that two users may voluntarily share access tokens between them in order to access protected resources. For example, if a website wants to limit access to only people over 18, and such does not need to know any user identifiers, an access token may be issued by an AS contains only the claim "over 18". If the user is aware that this access token doesn't reference them individually, they may be willing to share the access token with a user who is under 18 in order to let them get access to the website. (Note that the binding of an access token to a non-extractable client instance key also prevents the access token from being voluntarily shared.)</t> </section> <sectionanchor="correlation-by-authorization-servers"><name>Correlationanchor="correlation-by-authorization-servers"> <name>Correlation by Authorization Servers</name> <t>Clients are expected to be identified by their client instance key. If a particular client instance key is used at more than one authorization server, this could open up the possibility for multiple unrelated authorization servers to correlate client instances. This is especially a problem in the common case where a client instance is used by a single individual, as it would allow the authorization servers to correlate that individual between them. If this is a concern of a client, the client should use distinct keys with each authorization server.</t> </section> </section> <sectionanchor="disclosure-in-shared-references"><name>Disclosureanchor="disclosure-in-shared-references"> <name>Disclosure in Shared References</name> <t>Throughout many parts of GNAP, the parties pass shared references between each other, sometimes in place of the valuesthemselves. For examplethemselves (for example, the<spanx style="verb">interact_ref</spanx><tt>interact_ref</tt> value used throughout theflow.flow). These references are intended to be random strings and should not contain any private or sensitive data thatwouldcould potentially leak information between parties.</t> </section> </section> </middle> <back> <displayreference target="RFC9110" to="HTTP"/> <displayreference target="I-D.ietf-gnap-resource-servers" to="GNAP-RS"/> <displayreference target="I-D.ietf-oauth-security-topics" to="OAUTH-SEC-TOPICS"/> <references> <name>References</name> <referencestitle='Normative References'anchor="sec-normative-references"><referencegroup anchor="BCP195" target="https://www.rfc-editor.org/info/bcp195"> <reference anchor="RFC8996" target="https://www.rfc-editor.org/info/rfc8996"> <front> <title>Deprecating TLS 1.0 and TLS 1.1</title> <author fullname="K. Moriarty" initials="K." surname="Moriarty"/> <author fullname="S. Farrell" initials="S." surname="Farrell"/> <date month="March" year="2021"/> <abstract> <t>This document formally deprecates Transport Layer Security (TLS) versions 1.0 (RFC 2246) and 1.1 (RFC 4346). Accordingly, those documents have been moved to Historic status. These versions lack support for current and recommended cryptographic algorithms and mechanisms, and various government and industry profiles of applications using TLS now mandate avoiding these old TLS versions. TLS version 1.2 became the recommended version for IETF protocols in 2008 (subsequently being obsoleted by TLS version 1.3 in 2018), providing sufficient time to transition away from older versions. Removing support for older versions from implementations reduces the attack surface, reduces opportunity for misconfiguration, and streamlines library and product maintenance.</t> <t>This document also deprecates Datagram TLS (DTLS) version 1.0 (RFC 4347) but not DTLS version 1.2, and there is no DTLS version 1.1.</t> <t>This document updates many RFCs that normatively refer to TLS version 1.0 or TLS version 1.1, as described herein. This document also updates the best practices for TLS usage in RFC 7525; hence, it is part of BCP 195.</t> </abstract> </front> <seriesInfo name="BCP" value="195"/> <seriesInfo name="RFC" value="8996"/> <seriesInfo name="DOI" value="10.17487/RFC8996"/> </reference> <reference anchor="RFC9325" target="https://www.rfc-editor.org/info/rfc9325"> <front> <title>Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)</title> <author fullname="Y. Sheffer" initials="Y." surname="Sheffer"/> <author fullname="P. Saint-Andre" initials="P." surname="Saint-Andre"/> <author fullname="T. Fossati" initials="T." surname="Fossati"/> <date month="November" year="2022"/> <abstract> <t>Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) are used to protect data exchanged over a wide range of application protocols and can also form the basis for secure transport protocols. Over the years, the industry has witnessed several serious attacks on TLS and DTLS, including attacks on the most commonly used cipher suites and their modes of operation. This document provides the latest recommendations for ensuring the security of deployed services that use TLS and DTLS. These recommendations are applicable to the majority of use cases.</t> <t>RFC 7525, an earlier version of the TLS recommendations, was published when the industry was transitioning to TLS 1.2. Years later, this transition is largely complete, and TLS 1.3 is widely available. This document updates the guidance given the new environment and obsoletes RFC 7525. In addition, this document updates RFCs 5288 and 6066 in view of recent attacks.</t> </abstract> </front> <seriesInfo name="BCP" value="195"/> <seriesInfo name="RFC" value="9325"/> <seriesInfo name="DOI" value="10.17487/RFC9325"/> </reference> </referencegroup> <reference anchor="RFC2397"> <front> <title>The "data" URL scheme</title> <author fullname="L. Masinter" initials="L." surname="Masinter"/> <date month="August" year="1998"/> <abstract> <t>A new URL scheme, "data", is defined. It allows inclusion of small data items as "immediate" data, as if it had been included externally. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="2397"/> <seriesInfo name="DOI" value="10.17487/RFC2397"/> </reference> <reference anchor="RFC3339"> <front> <title>Date and Time on the Internet: Timestamps</title> <author fullname="G. Klyne" initials="G." surname="Klyne"/> <author fullname="C. Newman" initials="C." surname="Newman"/> <date month="July" year="2002"/> <abstract> <t>This document defines a date and time format for use in Internet protocols that is a profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.</t> </abstract> </front> <seriesInfo name="RFC" value="3339"/> <seriesInfo name="DOI" value="10.17487/RFC3339"/> </reference> <reference anchor="RFC3986"> <front> <title>Uniform Resource Identifier (URI): Generic Syntax</title> <author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee"/> <author fullname="R. Fielding" initials="R." surname="Fielding"/> <author fullname="L. Masinter" initials="L." surname="Masinter"/> <date month="January" year="2005"/> <abstract> <t>A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI<name>Normative References</name> <!-- [rfced] Questions about referencesthat might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementationtoparse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="STD" value="66"/> <seriesInfo name="RFC" value="3986"/> <seriesInfo name="DOI" value="10.17487/RFC3986"/> </reference> <reference anchor="RFC4648"> <front> <title>The Base16, Base32, and Base64 Data Encodings</title> <author fullname="S. Josefsson" initials="S." surname="Josefsson"/> <date month="October" year="2006"/> <abstract> <t>This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds in encoded data, use of padding in encoded data, use of non-alphabet characters in encoded data, use of different encoding alphabets, and canonical encodings. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="4648"/> <seriesInfo name="DOI" value="10.17487/RFC4648"/> </reference> <reference anchor="RFC5646"> <front> <title>Tags for Identifying Languages</title> <author fullname="A. Phillips" initials="A." role="editor" surname="Phillips"/> <author fullname="M. Davis" initials="M." role="editor" surname="Davis"/> <date month="September" year="2009"/> <abstract> <t>This document describesIANA registries a) Should thestructure, content, construction, and semantics of language tagsnaming conventions foruse in cases where it is desirable to indicatethelanguage used in an information object. It also describes how to register values for use in languagecitation tagsand the creation of user-defined extensions for private interchange. This document specifies an Internet Best Current Practicesfor theInternet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="47"/> <seriesInfo name="RFC" value="5646"/> <seriesInfo name="DOI" value="10.17487/RFC5646"/> </reference> <reference anchor="RFC7468"> <front> <title>Textual Encodings of PKIX, PKCS, and CMS Structures</title> <author fullname="S. Josefsson" initials="S." surname="Josefsson"/> <author fullname="S. Leonard" initials="S." surname="Leonard"/> <date month="April" year="2015"/> <abstract> <t>This document describes and discusses the textual encodings of the Public-Key Infrastructure X.509 (PKIX), Public-Key Cryptography Standards (PKCS), and Cryptographic Message Syntax (CMS). The textual encodings are well-known, are implemented by several applications and libraries, and are widely deployed. This document articulates the de facto rules by which existing implementations operate and defines them so that future implementations can interoperate.</t> </abstract> </front> <seriesInfo name="RFC" value="7468"/> <seriesInfo name="DOI" value="10.17487/RFC7468"/> </reference> <reference anchor="RFC7515"> <front> <title>JSON Web Signature (JWS)</title> <author fullname="M. Jones" initials="M." surname="Jones"/> <author fullname="J. Bradley" initials="J." surname="Bradley"/> <author fullname="N. Sakimura" initials="N." surname="Sakimura"/> <date month="May" year="2015"/> <abstract> <t>JSON Web Signature (JWS) represents content secured with digital signatures or Message Authentication Codes (MACs) using JSON-based data structures. Cryptographic algorithms and identifiers for use with this specification are described in the separate JSON Web Algorithms (JWA) specification and an IANA registry defined by that specification. Related encryption capabilities are described in the separate JSON Web Encryption (JWE) specification.</t> </abstract> </front> <seriesInfo name="RFC" value="7515"/> <seriesInfo name="DOI" value="10.17487/RFC7515"/> </reference> <reference anchor="RFC7517"> <front> <title>JSON Web Key (JWK)</title> <author fullname="M. Jones" initials="M." surname="Jones"/> <date month="May" year="2015"/> <abstract> <t>A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key. This specification also defines a JWK Set JSON data structure that represents a set of JWKs. Cryptographic algorithms and identifiersreference entries foruse with this specification are described in the separate JSON Web Algorithms (JWA) specification andIANA registriesestablished by that specification.</t> </abstract> </front> <seriesInfo name="RFC" value="7517"/> <seriesInfo name="DOI" value="10.17487/RFC7517"/> </reference> <reference anchor="RFC6749"> <front> <title>The OAuth 2.0 Authorization Framework</title> <author fullname="D. Hardt" initials="D." role="editor" surname="Hardt"/> <date month="October" year="2012"/> <abstract> <t>The OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its own behalf. This specification replaces and obsoletes the OAuth 1.0 protocol described in RFC 5849. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="6749"/> <seriesInfo name="DOI" value="10.17487/RFC6749"/> </reference> <reference anchor="RFC6750"> <front> <title>The OAuth 2.0 Authorization Framework: Bearer Token Usage</title> <author fullname="M. Jones" initials="M." surname="Jones"/> <author fullname="D. Hardt" initials="D." surname="Hardt"/> <date month="October" year="2012"/> <abstract> <t>This specification describes how to use bearer tokens in HTTP requests to access OAuth 2.0 protected resources. Any party in possession of a bearer token (a "bearer") can use it to get access to the associated resources (without demonstrating possession of a cryptographic key). To prevent misuse, bearer tokens need to be protected from disclosure in storage and in transport. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="6750"/> <seriesInfo name="DOI" value="10.17487/RFC6750"/> </reference> <reference anchor="RFC8174"> <front> <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title> <author fullname="B. Leiba" initials="B." surname="Leiba"/> <date month="May" year="2017"/> <abstract> <t>RFC 2119 specifies common key words that maybeused in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words havesimilar (e.g., should both start with "[IANA.")? Also, thedefined special meanings.</t> </abstract> </front> <seriesInfo name="BCP" value="14"/> <seriesInfo name="RFC" value="8174"/> <seriesInfo name="DOI" value="10.17487/RFC8174"/> </reference> <reference anchor="RFC8259"> <front> <title>The JavaScript Object Notation (JSON) Data Interchange Format</title> <author fullname="T. Bray" initials="T." role="editor" surname="Bray"/> <date month="December" year="2017"/> <abstract> <t>JavaScript Object Notation (JSON)first isa lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data.</t> <t>This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance.</t> </abstract> </front> <seriesInfo name="STD" value="90"/> <seriesInfo name="RFC" value="8259"/> <seriesInfo name="DOI" value="10.17487/RFC8259"/> </reference> <reference anchor="RFC8705"> <front> <title>OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens</title> <author fullname="B. Campbell" initials="B." surname="Campbell"/> <author fullname="J. Bradley" initials="J." surname="Bradley"/> <author fullname="N. Sakimura" initials="N." surname="Sakimura"/> <author fullname="T. Lodderstedt" initials="T." surname="Lodderstedt"/> <date month="February" year="2020"/> <abstract> <t>This document describes OAuth client authentication and certificate-bound access and refresh tokens using mutual Transport Layer Security (TLS) authentication with X.509 certificates. OAuth clients are provided a mechanism for authentication toin theauthorization server using mutual TLS, based on either self-signed certificates or public key infrastructure (PKI). OAuth authorization servers are provided a mechanism for binding access tokens to a client's mutual-TLS certificate,Normative References section, andOAuth protected resources are provided a method for ensuring that such an access token presented to it was issued to the client presentingthetoken.</t> </abstract> </front> <seriesInfo name="RFC" value="8705"/> <seriesInfo name="DOI" value="10.17487/RFC8705"/> </reference> <reference anchor="HTTP"> <front> <title>HTTP Semantics</title> <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/> <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/> <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/> <date month="June" year="2022"/> <abstract> <t>The Hypertext Transfer Protocol (HTTP)second isa stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects ofin theprotocolInformative References section. Please confirm thatare shared by all versions. Inthisdefinition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes.</t> <t>This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.</t> </abstract> </front> <seriesInfo name="STD" value="97"/> <seriesInfo name="RFC" value="9110"/> <seriesInfo name="DOI" value="10.17487/RFC9110"/> </reference> <reference anchor="RFC9111"> <front> <title>HTTP Caching</title> <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/> <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/> <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/> <date month="June" year="2022"/> <abstract> <t>The Hypertext Transfer Protocol (HTTP)isa stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.</t> <t>This document obsoletes RFC 7234.</t> </abstract> </front> <seriesInfo name="STD" value="98"/> <seriesInfo name="RFC" value="9111"/> <seriesInfo name="DOI" value="10.17487/RFC9111"/> </reference> <reference anchor="RFC9421"> <front> <title>HTTP Message Signatures</title> <author fullname="A. Backman" initials="A." role="editor" surname="Backman"/> <author fullname="J. Richer" initials="J." role="editor" surname="Richer"/> <author fullname="M. Sporny" initials="M." surname="Sporny"/> <date month="February" year="2024"/> <abstract> <t>Thiscorrect. Current: [HASH-ALG] IANA, "Named Information Hash Algorithm Registry", <https://www.iana.org/assignments/named-information/>. [IANA.MediaTypes] IANA, "Media Types", <https://www.iana.org/assignments/media-types>. b) The documentdescribes a mechanismincludes reference entries forcreating, encoding, and verifying digital signatures or message authentication codes over components of an HTTP message. This mechanism supports use cases wherethefull HTTP message mayregistries above but notbe known to the signer and where the message may be transformed (e.g., by intermediaries) before reaching the verifier. This document also describes a means for requesting that a signature be applied to a subsequent HTTP message in an ongoing HTTP exchange.</t> </abstract> </front> <seriesInfo name="RFC" value="9421"/> <seriesInfo name="DOI" value="10.17487/RFC9421"/> </reference> <reference anchor="RFC9530"> <front> <title>Digest Fields</title> <author fullname="R. Polli" initials="R." surname="Polli"/> <author fullname="L. Pardue" initials="L." surname="Pardue"/> <date month="February" year="2024"/> <abstract> <t>This document defines HTTP fields that support integrity digests. The Content-Digest field can be usedfor theintegrity of HTTP message content. The Repr-Digest field can be used for the integrity of HTTP representations. Want-Content-Digestregistries listed below. Please review andWant-Repr-Digest canlet us know if any updates would beused to indicate a sender's interest and preferences for receiving the respective Integrity fields.</t> <t>This document obsoletes RFC 3230 and the Digest and Want-Digest HTTP fields.</t> </abstract> </front> <seriesInfo name="RFC" value="9530"/> <seriesInfo name="DOI" value="10.17487/RFC9530"/> </reference> <reference anchor="RFC9493"> <front> <title>Subject Identifiers for Security Event Tokens</title> <author fullname="A. Backman" initials="A." role="editor" surname="Backman"/> <author fullname="M. Scurtescu" initials="M." surname="Scurtescu"/> <author fullname="P. Jain" initials="P." surname="Jain"/> <date month="December" year="2023"/> <abstract> <t>Security events communicated within Security Event Tokens may support a variety of identifiers to identify subjects related to the event. This specification formalizes the notion of Subject Identifiers as structured information that describes a subject and named formats that define the syntax and semantics for encoding Subject Identifiers as JSON objects. It also establishes ahelpful. In Section 10.1: "HTTP Authentication Schemes" registryfor defining(https://www.iana.org/assignments/http-authschemes) In Section 10.3-10.18: "Grant Negotiation andallocating names for such formats as well as the JSON Web Token (JWT) "sub_id" Claim.</t> </abstract> </front> <seriesInfo name="RFC" value="9493"/> <seriesInfo name="DOI" value="10.17487/RFC9493"/> </reference>Authorization Protocol (GNAP)" registry (https://www.iana.org/assignments/gnap) --> <referencegroup anchor="BCP195" target="https://www.rfc-editor.org/info/bcp195"> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8996.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9325.xml"/> </referencegroup> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2397.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3339.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4648.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5646.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7468.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7515.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7517.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6749.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6750.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8259.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8705.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9110.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9111.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9421.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9530.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9493.xml"/> <reference anchor="HASH-ALG"target="https://www.iana.org/assignments/named-information/named-information.xhtml#hash-alg">target="https://www.iana.org/assignments/named-information/"> <front> <title>Named Information Hash Algorithm Registry</title><author ><author> <organization>IANA</organization> </author><date year="n.d."/></front> </reference> <!-- [rfced] FYI - We updated the title and date of this reference to match current information available at the provided URL. Please let us know any concerns. Original: [OIDC] Sakimura, N., Bradley, J., Jones, M., de Medeiros, B., and C. Mortimore, "OpenID Connect Core 1.0 incorporating errata set 1", November 2014, <https://openid.net/specs/openid-connect-core-1_0.html>. Updated: [OIDC] Sakimura, N., Bradley, J., Jones, M., de Medeiros, B., and C. Mortimore, "OpenID Connect Core 1.0 incorporating errata set 2", December 2023, <https://openid.net/specs/openid-connect-core-1_0.html>. --> <reference anchor="OIDC" target="https://openid.net/specs/openid-connect-core-1_0.html"> <front> <title>OpenID Connect Core 1.0 incorporating errata set1</title>2</title> <author initials="N." surname="Sakimura"><organization></organization><organization/> </author> <author initials="J." surname="Bradley"><organization></organization><organization/> </author> <author initials="M." surname="Jones"><organization></organization><organization/> </author> <author initials="B." surname="de Medeiros"><organization></organization><organization/> </author> <author initials="C." surname="Mortimore"><organization></organization><organization/> </author> <dateyear="2014" month="November"/>year="2023" month="December"/> </front> </reference> <reference anchor="SAML2" target="https://docs.oasis-open.org/security/saml/v2.0/saml-core-2.0-os.pdf"> <front> <title>Assertions and Protocol for the OASIS Security Assertion Markup Language (SAML) V2.0</title> <authorinitials="S."initials="S., Ed." surname="Cantor"><organization></organization><organization/> </author> <authorinitials="J."initials="J., Ed." surname="Kemp"><organization></organization><organization/> </author> <authorinitials="R."initials="R., Ed." surname="Philpott"><organization></organization><organization/> </author> <author initials="E."surname="Maler"> <organization></organization>surname="Maler, Ed."> <organization/> </author> <date year="2005" month="March"/> </front> <refcontent>OASIS Standard</refcontent> </reference><reference anchor="RFC2119"> <front> <title>Key words for use in RFCs to Indicate Requirement Levels</title> <author fullname="S. Bradner" initials="S." surname="Bradner"/> <date month="March" year="1997"/> <abstract> <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="14"/> <seriesInfo name="RFC" value="2119"/> <seriesInfo name="DOI" value="10.17487/RFC2119"/> </reference><xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> </references> <referencestitle='Informative References'anchor="sec-informative-references"><reference anchor="RFC2046"> <front> <title>Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</title> <author fullname="N. Freed" initials="N." surname="Freed"/> <author fullname="N. Borenstein" initials="N." surname="Borenstein"/> <date month="November" year="1996"/> <abstract> <t>This second document defines the general structure of the MIME media typing system and defines an initial set of media types. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="2046"/> <seriesInfo name="DOI" value="10.17487/RFC2046"/> </reference> <reference anchor="RFC4107"> <front> <title>Guidelines for Cryptographic Key Management</title> <author fullname="S. Bellovin" initials="S." surname="Bellovin"/> <author fullname="R. Housley" initials="R." surname="Housley"/> <date month="June" year="2005"/> <abstract> <t>The question often arises of whether a given security system requires some form of automated key management, or whether manual keying is sufficient. This memo provides guidelines for making such decisions. When symmetric cryptographic mechanisms are used in a protocol, the presumption is that automated key management is generally but not always needed. If manual keying is proposed, the burden of proving that automated key management is not required falls to the proposer. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="107"/> <seriesInfo name="RFC" value="4107"/> <seriesInfo name="DOI" value="10.17487/RFC4107"/> </reference> <reference anchor="RFC6202"> <front> <title>Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP</title> <author fullname="S. Loreto" initials="S." surname="Loreto"/> <author fullname="P. Saint-Andre" initials="P." surname="Saint-Andre"/> <author fullname="S. Salsano" initials="S." surname="Salsano"/> <author fullname="G. Wilkins" initials="G." surname="Wilkins"/> <date month="April" year="2011"/> <abstract> <t>On today's Internet, the Hypertext Transfer Protocol (HTTP) is often used (some would say abused) to enable asynchronous, "server- initiated" communication from a server to a client as well as communication from a client to a server. This document describes known issues and best practices related to such "bidirectional HTTP" applications, focusing on the two most common mechanisms: HTTP long polling and HTTP streaming. This document is not an Internet Standards Track specification; it is published for informational purposes.</t> </abstract> </front> <seriesInfo name="RFC" value="6202"/> <seriesInfo name="DOI" value="10.17487/RFC6202"/> </reference> <reference anchor="RFC6838"> <front> <title>Media Type Specifications and Registration Procedures</title> <author fullname="N. Freed" initials="N." surname="Freed"/> <author fullname="J. Klensin" initials="J." surname="Klensin"/> <author fullname="T. Hansen" initials="T." surname="Hansen"/> <date month="January" year="2013"/> <abstract> <t>This document defines procedures for the specification and registration of media types for use in HTTP, MIME, and other Internet protocols. This memo documents an Internet Best Current Practice.</t> </abstract> </front> <seriesInfo name="BCP" value="13"/> <seriesInfo name="RFC" value="6838"/> <seriesInfo name="DOI" value="10.17487/RFC6838"/> </reference> <reference anchor="RFC6973"> <front> <title>Privacy Considerations for Internet Protocols</title> <author fullname="A. Cooper" initials="A." surname="Cooper"/> <author fullname="H. Tschofenig" initials="H." surname="Tschofenig"/> <author fullname="B. Aboba" initials="B." surname="Aboba"/> <author fullname="J. Peterson" initials="J." surname="Peterson"/> <author fullname="J. Morris" initials="J." surname="Morris"/> <author fullname="M. Hansen" initials="M." surname="Hansen"/> <author fullname="R. Smith" initials="R." surname="Smith"/> <date month="July" year="2013"/> <abstract> <t>This document offers guidance for developing privacy considerations for inclusion in protocol specifications. It aims to make designers, implementers, and users of Internet protocols aware of privacy-related design choices. It suggests that whether any individual RFC warrants a specific privacy considerations section will depend on the document's content.</t> </abstract> </front> <seriesInfo name="RFC" value="6973"/> <seriesInfo name="DOI" value="10.17487/RFC6973"/> </reference> <reference anchor="RFC7518"> <front> <title>JSON Web Algorithms (JWA)</title> <author fullname="M. Jones" initials="M." surname="Jones"/> <date month="May" year="2015"/> <abstract> <t>This specification registers cryptographic algorithms and identifiers to be used with the JSON Web Signature (JWS), JSON Web Encryption (JWE), and JSON Web Key (JWK) specifications. It defines several IANA registries for these identifiers.</t> </abstract> </front> <seriesInfo name="RFC" value="7518"/> <seriesInfo name="DOI" value="10.17487/RFC7518"/> </reference> <reference anchor="RFC8264"> <front> <title>PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols</title> <author fullname="P. Saint-Andre" initials="P." surname="Saint-Andre"/> <author fullname="M. Blanchet" initials="M." surname="Blanchet"/> <date month="October" year="2017"/> <abstract> <t>Application protocols using Unicode code points in protocol strings need to properly handle such strings in order to enforce internationalization rules for strings placed in various protocol slots (such as addresses and identifiers) and to perform valid comparison operations (e.g., for purposes of authentication or authorization). This document defines a framework enabling application protocols to perform the preparation, enforcement, and comparison of internationalized strings ("PRECIS") in a way that depends on the properties of Unicode code points and thus is more agile with respect to versions of Unicode. As a result, this framework provides a more sustainable approach to the handling of internationalized strings than the previous framework, known<name>Informative References</name> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2046.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4107.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6202.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6838.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6973.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7518.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8264.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8707.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8792.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9396.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9440.xml"/> <!-- [I-D.ietf-gnap-resource-servers] IESG State: I-D Exists asStringprep (RFC 3454). This document obsoletes RFC 7564.</t> </abstract> </front> <seriesInfo name="RFC" value="8264"/> <seriesInfo name="DOI" value="10.17487/RFC8264"/> </reference> <reference anchor="RFC8707"> <front> <title>Resource Indicators for OAuth 2.0</title> <author fullname="B. Campbell" initials="B." surname="Campbell"/> <author fullname="J. Bradley" initials="J." surname="Bradley"/> <author fullname="H. Tschofenig" initials="H." surname="Tschofenig"/> <date month="February" year="2020"/> <abstract> <t>This document specifies an extension to the OAuth 2.0 Authorization Framework defining request parameters that enable a client to explicitly signal to an authorization server about the identityofthe protected resource(s) to which it is requesting access.</t> </abstract> </front> <seriesInfo name="RFC" value="8707"/> <seriesInfo name="DOI" value="10.17487/RFC8707"/> </reference> <reference anchor="RFC8792"> <front> <title>Handling03/18/24 LongLines in Content of Internet-Drafts and RFCs</title> <author fullname="K. Watsen" initials="K." surname="Watsen"/> <author fullname="E. Auerswald" initials="E." surname="Auerswald"/> <author fullname="A. Farrel" initials="A." surname="Farrel"/> <author fullname="Q. Wu" initials="Q." surname="Wu"/> <date month="June" year="2020"/> <abstract> <t>This document defines two strategies for handling long lines in width-bounded text content. One strategy, called the "single backslash" strategy, is based on the historical use of a single backslash ('\') character to indicate where line-folding has occurred, with the continuation occurring with the first character that is not a space character (' ') on the next line. The second strategy, called the "double backslash" strategy, extends the first strategy by adding a second backslash character to identify where the continuation begins and is thereby able to handle cases not supported by the first strategy. Both strategies use a self-describing header enabling automated reconstitution of the original content.</t> </abstract> </front> <seriesInfo name="RFC" value="8792"/> <seriesInfo name="DOI" value="10.17487/RFC8792"/> </reference> <reference anchor="RFC9396"> <front> <title>OAuth 2.0 Rich Authorization Requests</title> <author fullname="T. Lodderstedt" initials="T." surname="Lodderstedt"/> <author fullname="J. Richer" initials="J." surname="Richer"/> <author fullname="B. Campbell" initials="B." surname="Campbell"/> <date month="May" year="2023"/> <abstract> <t>This document specifies a new parameter that isWay used tocarry fine-grained authorization data in OAuth messages.</t> </abstract> </front> <seriesInfo name="RFC" value="9396"/> <seriesInfo name="DOI" value="10.17487/RFC9396"/> </reference> <reference anchor="RFC9440"> <front> <title>Client-Cert HTTP Header Field</title> <author fullname="B. Campbell" initials="B." surname="Campbell"/> <author fullname="M. Bishop" initials="M." surname="Bishop"/> <date month="July" year="2023"/> <abstract> <t>This document describes HTTP extension header fields that allow a TLS terminating reverse proxy (TTRP) to convey the client certificate information of a mutually authenticated TLS connection to the origin server in a common and predictable manner.</t> </abstract> </front> <seriesInfo name="RFC" value="9440"/> <seriesInfo name="DOI" value="10.17487/RFC9440"/> </reference>include editor role--> <referenceanchor="I-D.ietf-gnap-resource-servers">anchor="I-D.ietf-gnap-resource-servers" target="https://datatracker.ietf.org/doc/html/draft-ietf-gnap-resource-servers-08"> <front><title>Grant<title> Grant Negotiation and Authorization Protocol Resource ServerConnections</title>Connections </title> <author initials="J." surname="Richer" fullname="Justin Richer"initials="J." surname="Richer">role="editor"> <organization>Bespoke Engineering</organization> </author> <authorfullname="Fabien Imbault"initials="F."surname="Imbault">surname="Imbault" fullname="Fabien Imbault"> <organization>acert.io</organization> </author> <dateday="19" month="February" year="2024"/> <abstract> <t> GNAP defines a mechanism for delegating authorization to a piece of software, and conveying that delegation to the software. This extension defines methods for resource servers (RS) to connect with authorization servers (AS) in an interoperable fashion. </t> </abstract> </front> <seriesInfo name="Internet-Draft" value="draft-ietf-gnap-resource-servers-05"/> </reference> <reference anchor="I-D.ietf-oauth-security-topics"> <front> <title>OAuth 2.0 Security Best Current Practice</title> <author fullname="Torsten Lodderstedt" initials="T." surname="Lodderstedt"> <organization>SPRIND</organization> </author> <author fullname="John Bradley" initials="J." surname="Bradley"> <organization>Yubico</organization> </author> <author fullname="Andrey Labunets" initials="A." surname="Labunets"> <organization>Independent Researcher</organization> </author> <author fullname="Daniel Fett" initials="D." surname="Fett"> <organization>Authlete</organization> </author> <date day="8" month="February"month="August" day="9" year="2024"/><abstract> <t> This document describes best current security practice for OAuth 2.0. It updates and extends the threat model and security advice given in [RFC6749], [RFC6750], and [RFC6819] to incorporate practical experiences gathered since OAuth 2.0 was published and covers new threats relevant due to the broader application of OAuth 2.0. It further deprecates some modes of operation that are deemed less secure or even insecure. </t> </abstract></front> <seriesInfo name="Internet-Draft"value="draft-ietf-oauth-security-topics-25"/>value="draft-ietf-gnap-resource-servers-08"/> </reference><reference anchor="RFC9525"> <front> <title>Service Identity in TLS</title> <author fullname="P. Saint-Andre" initials="P." surname="Saint-Andre"/> <author fullname="R. Salz" initials="R." surname="Salz"/> <date month="November" year="2023"/> <abstract> <t>Many application technologies enable secure communication between two entities by means of Transport Layer Security (TLS) with Internet Public Key Infrastructure using X.509 (PKIX) certificates. This document specifies procedures<!-- [I-D.ietf-oauth-security-topics] IESG State: Waiting forrepresenting and verifying the identityAD Go-Ahead::Revised I-D Needed as ofapplication services in such interactions.</t> <t>This document obsoletes RFC 6125.</t> </abstract> </front> <seriesInfo name="RFC" value="9525"/> <seriesInfo name="DOI" value="10.17487/RFC9525"/> </reference>03/18/24 --> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-ietf-oauth-security-topics.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9525.xml"/> <reference anchor="promise-theory" target="http://markburgess.org/promises.html"> <front> <title>Promisetheory</title> <author initials="M." surname="Burgess"> <organization></organization> </author>Theory: Principles and Applications</title> <author initials="J." surname="Bergstra"><organization></organization><organization/> </author> <author initials="M." surname="Burgess"> <organization/> </author> <dateyear="2014" month="January"/>year="2019"/> </front> <refcontent>Second Edition, XtAxis Press</refcontent> </reference> <reference anchor="AXELAND2021"target="https://odr.chalmers.se/handle/20.500.12380/304105">target="https://hdl.handle.net/20.500.12380/304105"> <front> <title>Security Analysis of Attack Surfaces on the Grant Negotiation and Authorization Protocol</title> <author initials="Å." surname="Axeland"><organization></organization><organization/> </author> <author initials="O." surname="Oueidat"><organization></organization><organization/> </author> <date year="2021"/> </front> <refcontent>Master's thesis, Department of Computer Science and Engineering, Chalmers University of Technology and University of Gothenburg</refcontent> </reference> <reference anchor="HELMSCHMIDT2022" target="http://dx.doi.org/10.18419/opus-12203"> <front> <title>Security Analysis of the Grant Negotiation and Authorization Protocol</title> <author initials="F." surname="Helmschmidt"><organization></organization><organization/> </author> <date year="2022"/> </front> <seriesInfo name="DOI" value="10.18419/opus-12203"/> <refcontent>Master's thesis, Institute of Information Security, University of Stuggart</refcontent> </reference> <reference anchor="SP80063C"target="https://doi.org/10.6028/NIST.SP.800-63c">target="https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-63c.pdf"> <front> <title>Digital Identity Guidelines: Federation and Assertions</title> <author initials="P." surname="Grassi"><organization></organization> </author> <author initials="E." surname="Nadeau"> <organization></organization><organization/> </author> <author initials="J." surname="Richer"><organization></organization><organization/> </author> <author initials="S." surname="Squire"><organization></organization><organization/> </author> <author initials="J." surname="Fenton"><organization></organization><organization/> </author> <author initials="E." surname="Nadeau"> <organization/> </author> <author initials="N." surname="Lefkovitz"><organization></organization><organization/> </author> <author initials="J." surname="Danker"><organization></organization><organization/> </author> <author initials="Y." surname="Choong"><organization></organization><organization/> </author> <author initials="K." surname="Greene"><organization></organization><organization/> </author> <author initials="M." surname="Theofanos"><organization></organization><organization/> </author> <date year="2017" month="June"/> </front> <seriesInfo name="NIST SP" value="800-63C"/> <seriesInfo name="DOI" value="10.6028/NIST.SP.800-63c"/> </reference> <reference anchor="IANA.MediaTypes"target="https://www.iana.org/assignments/media-types/media-types.xhtml">target="https://www.iana.org/assignments/media-types"> <front> <title>Media Types</title> <author fullname="IANA"><organization></organization><organization/> </author><date year="n.d."/></front> </reference><reference anchor="RFC8126"> <front> <title>Guidelines for Writing an IANA Considerations Section in RFCs</title> <author fullname="M. Cotton" initials="M." surname="Cotton"/> <author fullname="B. Leiba" initials="B." surname="Leiba"/> <author fullname="T. Narten" initials="T." surname="Narten"/> <date month="June" year="2017"/> <abstract> <t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t> <t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t> <t>This is the third edition of this document; it obsoletes RFC 5226.</t> </abstract> </front> <seriesInfo name="BCP" value="26"/> <seriesInfo name="RFC" value="8126"/> <seriesInfo name="DOI" value="10.17487/RFC8126"/> </reference><xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/> </references> </references><?line 7538?><sectionanchor="history"><name>Document History</name> <ul empty="true"><li> <t>Note: To be removed by RFC editor before publication.</t> </li></ul> <t><list style="symbols"> <t>19 <list style="symbols"> <t>Updates from IESG reviews.</t> <t>Updated JOSE types to no longer use subtypes.</t> <t>Added media type registrations.</t> </list></t> <t>18 <list style="symbols"> <t>Updates from IESG reviews.</t> </list></t> <t>17 <list style="symbols"> <t>Updates from IESG reviews.</t> </list></t> <t>16 <list style="symbols"> <t>Updates from AD review.</t> <t>Added security considerations on token substitution attack.</t> </list></t> <t>15 <list style="symbols"> <t>Editorial updates from shepherd review.</t> <t>Clarify character set constraints of user codes.</t> </list></t> <t>14 <list style="symbols"> <t>Update token rotation to use URI + management token.</t> <t>Fix key rotationanchor="vs-oauth2"> <name>Comparison withHTTP Signatures based on security analysis.</t> </list></t> <t>-13 <list style="symbols"> <t>Editoral changes from chair review.</t> <t>Clarify that user codes are ungessable.</t> <t>Fix user code examples.</t> <t>Clarify expectations for extensions to interaction start and finish methods.</t> <t>Fix references.</t> <t>Add IANA designated expert instructions.</t> <t>Clarify new vs. updated access tokens, and call out no need for refresh tokens in OAuth 2 comparison section.</t> <t>Add instructions on assertion processing.</t> <t>Explicitly list user reference lifetime management.</t> </list></t> <t>-12 <list style="symbols"> <t>Make default hash algorithm SHA256 instead of SHA3-512.</t> <t>Remove <spanx style="verb">previous_key</spanx> from key rotation.</t> <t>Defined requirements for key rotation methods.</t> <t>Add specificity to context of subject identifier being the AS.</t> <t>Editorial updates and protocol clarification.</t> </list></t> <t>-11 <list style="symbols"> <t>Error as object or string, more complete set of error codes</t> <t>Added key rotation in token management.</t> <t>Restrict keys to a single format per message.</t> <t>Discussed security issues of multiple key formats.</t> <t>Make token character set more strict.</t> <t>Add note on long-polling in continuation requests.</t> <t>Removed "Models" section.</t> <t>Rewrote guidance and requirements for extensions.</t> <t>Require all URIs to be absolute throughout protocol.</t> <t>Make response from RS a "<bcp14>SHOULD</bcp14>" instead of a "<bcp14>MAY</bcp14>".</t> <t>Added a way for the client instance to ask for a specific user's information, separate from the end-user.</t> <t>Added security considerations for asynchronous authorization.</t> <t>Added security considerations for compromised RS.</t> <t>Added interoperability profiles.</t> <t>Added implementation status section.</t> </list></t> <t>-10 <list style="symbols"> <t>Added note on relating access rights sent as strings to rights sent as objects.</t> <t>Expand proofing methods to allow definition by object, with single string as optimization for common cases.</t> <t>Removed "split_token" functionality.</t> <t>Collapse "user_code" into a string instead of an object.</t> <t>References hash algorithm identifiers from the existing IANA registry</t> <t>Allow interaction responses to time out.</t> <t>Added explicit protocol state discussion.</t> <t>Added RO policy use case.</t> </list></t> <t>-09 <list style="symbols"> <t>Added security considerations on redirection status codes.</t> <t>Added security considerations on cuckoo token attack.</t> <t>Made token management URL required on token rotation.</t> <t>Added considerations on token rotation and self-contained tokens.</t> <t>Added security considerations for SSRF.</t> <t>Moved normative requirements about end user presence to security considerations.</t> <t>Clarified default wait times for continuation requests (including polling).</t> <t>Clarified URI vs. URL.</t> <t>Added "user_code_uri" mode, removed "uri" from "user_code" mode.</t> <t>Consistently formatted all parameter lists.</t> <t>Updated examples for HTTP Signatures.</t> </list></t> <t>-08 <list style="symbols"> <t>Update definition for "Client" to account for the case of no end user.</t> <t>Change definition for "Subject".</t> <t>Expanded security and privacy considerations for more situations.</t> <t>Added cross-links from security and privacy considerations.</t> <t>Editorial updates.</t> </list></t> <t>-07 <list style="symbols"> <t>Replace user handle by opaque identifier</t> <t>Added trust relationships</t> <t>Added privacy considerations section</t> <t>Added security considerations.</t> </list></t> <t>-06 <list style="symbols"> <t>Removed "capabilities" and "existing_grant" protocol fields.</t> <t>Removed separate "instance_id" field.</t> <t>Split "interaction_methods_supported" into "interaction_start_modes_supported" and "interaction_finish_methods_supported".</t> <t>Added AS endpoint to hash calculation to fix mix-up attack.</t> <t>Added "privileges" field to resource access request object.</t> <t>Moved client-facing RS response back from GNAP-RS document.</t> <t>Removed oauthpop key binding.</t> <t>Removed dpop key binding.</t> <t>Added example DID identifier.</t> <t>Changed token response booleans to flag structure to match request.</t> <t>Updated signature examples to use HTTP Message Signatures.</t> </list></t> <t>-05 <list style="symbols"> <t>Changed "interaction_methods" to "interaction_methods_supported".</t> <t>Changed "key_proofs" to "key_proofs_supported".</t> <t>Changed "assertions" to "assertions_supported".</t> <t>Updated discovery and field names for subject formats.</t> <t>Add an appendix to provide protocol rationale, compared to OAuth2.</t> <t>Updated subject information definition.</t> <t>Refactored the RS-centric components into a new document.</t> <t>Updated cryptographic proof of possession methods to match current reference syntax.</t> <t>Updated proofing language to use "signer" and "verifier" generically.</t> <t>Updated cryptographic proof of possession examples.</t> <t>Editorial cleanup and fixes.</t> <t>Diagram cleanup and fixes.</t> </list></t> <t>-04 <list style="symbols"> <t>Updated terminology.</t> <t>Refactored key presentation and binding.</t> <t>Refactored "interact" request to group start and end modes.</t> <t>Changed access token request and response syntax.</t> <t>Changed DPoP digest field to 'htd' to match proposed FAPI profile.</t> <t>Include the access token hash in the DPoP message.</t> <t>Removed closed issue links.</t> <t>Removed function to read state of grant request by client.</t> <t>Closed issues related to reading and updating access tokens.</t> </list></t> <t>-03 <list style="symbols"> <t>Changed "resource client" terminology to separate "client instance" and "client software".</t> <t>Removed OpenID Connect "claims" parameter.</t> <t>Dropped "short URI" redirect.</t> <t>Access token is mandatory for continuation.</t> <t>Removed closed issue links.</t> <t>Editorial fixes.</t> </list></t> <t>-02 <list style="symbols"> <t>Moved all "editor's note" items to GitHub Issues.</t> <t>Added JSON types to fields.</t> <t>Changed "GNAP Protocol" to "GNAP".</t> <t>Editorial fixes.</t> </list></t> <t>-01 <list style="symbols"> <t>"updated_at" subject info timestamp now in ISO 8601 string format.</t> <t>Editorial fixes.</t> <t>Added Aaron and Fabien as document authors.</t> </list></t> <t>-00 <list style="symbols"> <t>Initial working group draft.</t> </list></t> </list></t> </section> <section anchor="vs-oauth2"><name>Compared toOAuth 2.0</name> <t>GNAP's protocol design differs from OAuth 2.0's in several fundamental ways:</t><t><list style="numbers"><ol spacing="normal" type="1"><li> <t><strong>Consent and authorization flexibility:</strong><vspace blankLines='1'/></t> <t> OAuth 2.0 generally assumes the user has access to a web browser. The type of interaction available is fixed by the grant type, and the most common interactive grant types start in the browser. OAuth 2.0 assumes that the user using the client software is the same user that will interact with the AS to approve access.<vspace blankLines='1'/></t> <t> GNAP allows various patterns to manage authorizations and consents required to fulfill this requested delegation, including information sent by the client instance, information supplied by external parties, and information gathered through the interaction process. GNAP allows a client instance to list different ways that it can start and finish an interaction, and these can be mixed together as needed for different use cases. GNAP interactions can use a browser, but they don't have to. Methods can use inter-application messaging protocols, out-of-band data transfer, or anything else. GNAP allows extensions to define new ways to start and finish an interaction, as new methods and platforms are expected to become available over time. GNAP is designed to allow the end user and the resource owner to be two different people, but it still works in the optimized case of them being the same party.</t> </li> <li> <t><strong>Intent registration and inline negotiation:</strong><vspace blankLines='1'/></t> <t> OAuth 2.0 uses different "grant types" that start at different endpoints for different purposes. Many of these require discovery of several interrelated parameters.<vspace blankLines='1'/></t> <t> GNAP requests all start with the same type of request to the same endpoint at the AS. Next steps are negotiated between the client instance and AS based on software capabilities, policies surrounding requested access, and the overall context of the ongoing request. GNAP defines a continuation API that allows the client instance and AS to request and send additional information from each other over multiple steps. This continuation API uses the same access token protection that other GNAP-protected APIs use. GNAP allows discovery to optimize therequestsrequests, but it isn't required thanks to the negotiation capabilities.<vspace blankLines='1'/></t> <t> GNAP is able to handle thelife-cyclelife cycle of an authorizationrequest,request and therefore simplifies the mental model surrounding OAuth2. For instance, there's no need for refresh tokens when the API enables proper rotation of access tokens.</t> </li> <li> <t><strong>Client instances:</strong><vspace blankLines='1'/></t> <t> OAuth 2.0 requires all clients to be registered at the AS and to use a client_id known to the AS as part of the protocol. This client_id is generally assumed to be assigned by a trusted authority during a registration process, and OAuth places a lot of trust on the client_id as a result. Dynamic registration allows different classes of clients to get a client_id at runtime, even if they only ever use it for one request.<vspace blankLines='1'/></t> <t> GNAP allows the client instance to present an unknown key to the AS and use that key to protect the ongoing request. GNAP's client instance identifier mechanism allows for pre-registered clients and dynamically registered clients to exist as an optimized case without requiring the identifier as part of the protocol at all times.</t> </li> <li> <t><strong>Expanded delegation:</strong><vspace blankLines='1'/></t> <!-- [rfced] This sentence has two "including..." phrases next to each other that may hinder readability. How may we update? Original: This parameter has been coopted to mean a number of different things in different protocols, including flags for turning special behavior on and off, including the return of data apart from the access token. Perhaps: This parameter has been co-opted to mean a number of different things in different protocols, including flags for turning special behavior on and off (such as the return of data apart from the access token). Or: This parameter has been co-opted to mean a number of different things in different protocols, including flags for turning special behavior on and off and the return of data apart from the access token. --> <t> OAuth 2.0 defines the "scope" parameter for controlling access to APIs. This parameter has beencooptedco-opted to mean a number of different things in different protocols, including flags for turning special behavior on and off, including the return of data apart from the access token. The "resource" indicator (defined in <xref target="RFC8707"/>) and RAR extensions (as defined in <xref target="RFC9396"/>) expand on the "scope" concept in similar but different ways.<vspace blankLines='1'/></t> <t> GNAP defines a rich structure for requesting access (analogous to RAR), with string references as an optimization (analogous to scopes). GNAP defines methods for requestingdirectly-returneddirectly returned user information, separate from API access. This information includes identifiers for the current user and structured assertions. The core GNAP protocol makes no assumptions or demands on the format or contents of the access token, but the RS extension allows a negotiation of token formats between the AS and RS.</t> </li> <li> <t><strong>Cryptography-based security:</strong><vspace blankLines='1'/></t> <t> OAuth 2.0 uses shared bearer secrets, including the client_secret and access token, and advanced authentication and senderconstraintconstraints have been built on after the fact in inconsistent ways.<vspace blankLines='1'/></t> <t> In GNAP, all communication between the client instance and AS is bound to a key held by the client instance. GNAP uses the same cryptographic mechanisms for both authenticating the client (to the AS) and binding the access token (to the RS and the AS). GNAP allows extensions to define new cryptographic protection mechanisms, as new methods are expected to become available over time. GNAP does not haveathe notion of "public clients" because key information can always be sent and used dynamically.</t> </li> <li> <t><strong>Privacy and usable security:</strong><vspace blankLines='1'/></t> <t> OAuth 2.0's deployment model assumes a strong binding between the AS and the RS.<vspace blankLines='1'/></t> <t> GNAP is designed to be interoperable with decentralized identity standards and to provide a human-centric authorization layer. In addition to the core protocol, GNAP supports various patterns of communication between RSs andASsASes through extensions. GNAP tries to limit the odds of a consolidation to just a handful ofsuper-popularpopular AS services.</t></list></t></li> </ol> </section> <sectionanchor="examples"><name>Exampleanchor="examples"> <name>Example Protocol Flows</name> <t>The protocol defined in this specification provides a number of features that can be combined to solve many different kinds of authentication scenarios. This section seeks to show examples of how the protocolwouldcould be applied for different situations.</t> <t>Some longer fields, particularly cryptographic information, have been truncated for display purposes in these examples.</t> <sectionanchor="example-auth-code"><name>Redirect-Basedanchor="example-auth-code"> <name>Redirect-Based User Interaction</name> <t>In this scenario, the user is the RO and has access to a web browser, and the client instance can take front-channel callbacks on the same device as the user. This combination is analogous to the OAuth 2.0 Authorization Code grant type.</t> <t>The client instance initiates the request to the AS.HereHere, the client instance identifies itself using its public key.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /tx HTTP/1.1 Host: server.example.com Content-Type: application/json Signature-Input: sig1=... Signature: sig1=... Content-Digest: sha-256=... { "access_token": { "access": [ { "actions": [ "read", "write", "dolphin" ], "locations": [ "https://server.example.net/", "https://resource.local/other" ], "datatypes": [ "metadata", "images" ] } ], }, "client": { "key": { "proof": "httpsig", "jwk": { "kty": "RSA", "e": "AQAB", "kid": "xyz-1", "alg": "RS256", "n": "kOB5rR4Jv0GMeLaY6_It_r3ORwdf8ci_JtffXyaSx8..." } } }, "interact": { "start": ["redirect"], "finish": { "method": "redirect", "uri": "https://client.example.net/return/123455", "nonce": "LKLTI25DK82FX4T4QFZC" } } }]]></sourcecode></figure>]]></sourcecode> <t>The AS processes the request and determines that the RO needs to interact. The AS returns the following responsegivingthat gives the client instance the information it needs to connect. The AS has also indicated to the client instance that it can use the given instance identifier to identify itself in<xref target="request-instance">future requests</xref>.</t> <figure><sourcecodefuture requests (<xref target="request-instance"> </xref>).</t> <sourcecode type="http-message"><![CDATA[ HTTP/1.1 200 OK Content-Type: application/json Cache-Control: no-store { "interact": { "redirect": "https://server.example.com/interact/4CF492MLVMSW9MKM", "finish": "MBDOFXG4Y5CVJCX821LH" } "continue": { "access_token": { "value": "80UPRY5NM33OMUKMKSKU" }, "uri": "https://server.example.com/continue" }, "instance_id": "7C7C4AZ9KHRS6X63AJAO" }]]></sourcecode></figure>]]></sourcecode> <t>The client instance saves the response and redirects the user to the interaction start mode's "redirect" URI by sending the following HTTP message to the user's browser.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ HTTP 303 Found Location: https://server.example.com/interact/4CF492MLVMSW9MKM]]></sourcecode></figure>]]></sourcecode> <t>The user's browser fetches the AS's interaction URI. The user logs in, is identified as the RO for the resource being requested, and approves the request. Since the AS has a callback parameter that was sent in the initial request's interaction finish method, the AS generates the interaction reference, calculates the hash, and redirects the user back to the client instance with these additional values added as query parameters.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 HTTP 302 Found Location: https://client.example.net/return/123455\ ?hash=x-gguKWTj8rQf7d7i3w3UhzvuJ5bpOlKyAlVpLxBffY\ &interact_ref=4IFWWIKYBC2PQ6U56NL1]]></sourcecode></figure>]]></sourcecode> <t>The client instance receives this request from the user's browser. The client instance ensures that this is the same user that was sent out by validating session information and retrieves the stored pending request. The client instance uses the values in this to validate the hash parameter. The client instance then calls the continuation URI using the associated continuation access token and presents the interaction reference in the request content. The client instance signs the request as above.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /continue HTTP/1.1 Host: server.example.com Content-Type: application/json Authorization: GNAP 80UPRY5NM33OMUKMKSKU Signature-Input: sig1=... Signature: sig1=... Content-Digest: sha-256=... { "interact_ref": "4IFWWIKYBC2PQ6U56NL1" }]]></sourcecode></figure>]]></sourcecode> <t>The AS retrieves the pending request by looking up the pending grant request associated with the presented continuation access token. Seeing that the grant is approved, the AS issues an access token and returns this to the client instance.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 HTTP/1.1 200 OK Content-Type: application/json Cache-Control: no-store { "access_token": { "value": "OS9M2PMHKUR64TB8N6BW7OZB8CDFONP219RP1LT0", "manage": "https://server.example.com/token/PRY5NM33O\ M4TB8N6BW7OZB8CDFONP219RP1L", "access": [{ "actions": [ "read", "write", "dolphin" ], "locations": [ "https://server.example.net/", "https://resource.local/other" ], "datatypes": [ "metadata", "images" ] }] }, "continue": { "access_token": { "value": "80UPRY5NM33OMUKMKSKU" }, "uri": "https://server.example.com/continue" } }]]></sourcecode></figure>]]></sourcecode> </section> <sectionanchor="example-device"><name>Secondaryanchor="example-device"> <name>Secondary Device Interaction</name> <t>In this scenario, the user does not have access to a web browser on the device and must use a secondary device to interact with the AS. The client instance can display a user code or a printable QR code. The client instance is not able to accept callbacks from the AS and needs to poll for updates while waiting for the user to authorize the request.</t> <t>The client instance initiates the request to the AS.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /tx HTTP/1.1 Host: server.example.com Content-Type: application/json Signature-Input: sig1=... Signature: sig1=... Content-Digest: sha-256=... { "access_token": { "access": [ "dolphin-metadata", "some other thing" ], }, "client": "7C7C4AZ9KHRS6X63AJAO", "interact": { "start": ["redirect", "user_code"] } }]]></sourcecode></figure>]]></sourcecode> <t>The AS processes this and determines that the RO needs to interact. The AS supports both redirect URIs and user codes for interaction, so it includes both. Since there is no interaction finish mode, the AS does not include anonce,nonce but does include a "wait" parameter on the continuation section because it expects the client instance to poll for results.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ HTTP/1.1 200 OK Content-Type: application/json Cache-Control: no-store { "interact": { "redirect": "https://srv.ex/MXKHQ", "user_code": { "code": "A1BC3DFF" } }, "continue": { "access_token": { "value": "80UPRY5NM33OMUKMKSKU" }, "uri": "https://server.example.com/continue/VGJKPTKC50", "wait": 60 } }]]></sourcecode></figure>]]></sourcecode> <t>The client instance saves the response and displays the user code visually on its screen along with the static device URI. The client instance also displays the short interaction URI as a QR code to be scanned.</t> <t>If the user scans the code, they are taken to the interactionendpointendpoint, and the AS looks up the current pending request based on the incoming URI. If the user instead goes to the static page and enters the code manually, the AS looks up the current pending request based on the value of the user code. In both cases, the user logs in, is identified as the RO for the resource being requested, and approves the request. Once the request has been approved, the AS displays to the user a message to return to their device.</t> <t>Meanwhile, the client instanceperiodicallypolls the AS every 60 seconds at the continuation URI. The client instance signs the request using the same key and method that it did in the first request.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /continue/VGJKPTKC50 HTTP/1.1 Host: server.example.com Authorization: GNAP 80UPRY5NM33OMUKMKSKU Signature-Input: sig1=... Signature: sig1=... Content-Digest: sha-256=...]]></sourcecode></figure>]]></sourcecode> <t>The AS retrieves the pending request based on the pending grant request associated with the continuation access token and determines that it has not yet been authorized. The AS indicates to the client instance that no access token has yet been issued but it can continue to call after another60 second60-second timeout.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ HTTP/1.1 200 OK Content-Type: application/json Cache-Control: no-store { "continue": { "access_token": { "value": "G7YQT4KQQ5TZY9SLSS5E" }, "uri": "https://server.example.com/continue/ATWHO4Q1WV", "wait": 60 } }]]></sourcecode></figure>]]></sourcecode> <t>Note that the continuation URI and access token have been rotated since they were used by the client instance to make this call. The client instance polls the continuation URI after a60 second60-second timeout using this new information.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /continue/ATWHO4Q1WV HTTP/1.1 Host: server.example.com Authorization: GNAP G7YQT4KQQ5TZY9SLSS5E Signature-Input: sig1=... Signature: sig1=... Content-Digest: sha-256=...]]></sourcecode></figure>]]></sourcecode> <t>The AS retrieves the pending request based on the URI and access token, determines that it has been approved, and issues an access token for the client to use at the RS.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 HTTP/1.1 200 OK Content-Type: application/json Cache-Control: no-store { "access_token": { "value": "OS9M2PMHKUR64TB8N6BW7OZB8CDFONP219RP1LT0", "manage": "https://server.example.com/token/PRY5NM33O\ M4TB8N6BW7OZB8CDFONP219RP1L", "access": [ "dolphin-metadata", "some other thing" ] } }]]></sourcecode></figure>]]></sourcecode> </section> <sectionanchor="example-no-user"><name>Noanchor="example-no-user"> <name>No User Involvement</name> <t>In this scenario, the client instance is requesting access on its own behalf, with no user to interact with.</t> <t>The client instance creates a request to the AS, identifying itself with its public key and using MTLS to make the request.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /tx HTTP/1.1 Host: server.example.com Content-Type: application/json { "access_token": { "access": [ "backend service", "nightly-routine-3" ], }, "client": { "key": { "proof": "mtls", "cert#S256": "bwcK0esc3ACC3DB2Y5_lESsXE8o9ltc05O89jdN-dg2" } } }]]></sourcecode></figure>]]></sourcecode> <t>The AS processesthis andthis, determines that the client instance can ask for the requestedresourcesresources, and issues an access token.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ HTTP/1.1 200 OK Content-Type: application/json Cache-Control: no-store { "access_token": { "value": "OS9M2PMHKUR64TB8N6BW7OZB8CDFONP219RP1LT0", "manage": "https://server.example.com/token", "access": [ "backend service", "nightly-routine-3" ] } }]]></sourcecode></figure>]]></sourcecode> </section> <sectionanchor="example-async"><name>Asynchronousanchor="example-async"> <name>Asynchronous Authorization</name> <t>In this scenario, the client instance is requesting on behalf of a specificRO,RO but has no way to interact with the user. The AS can asynchronously reach out to the RO for approval in this scenario.</t> <t>The client instance starts the request at the AS by requesting a set of resources. The client instance also identifies a particular user.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /tx HTTP/1.1 Host: server.example.com Content-Type: application/json Signature-Input: sig1=... Signature: sig1=... Content-Digest: sha-256=... { "access_token": { "access": [ { "type": "photo-api", "actions": [ "read", "write", "dolphin" ], "locations": [ "https://server.example.net/", "https://resource.local/other" ], "datatypes": [ "metadata", "images" ] }, "read", "dolphin-metadata", { "type": "financial-transaction", "actions": [ "withdraw" ], "identifier": "account-14-32-32-3", "currency": "USD" }, "some other thing" ], }, "client": "7C7C4AZ9KHRS6X63AJAO", "user": { "sub_ids": [ { "format": "opaque", "id": "J2G8G8O4AZ" } ] } }]]></sourcecode></figure>]]></sourcecode> <t>The AS processes this and determines that the RO needs to interact. The AS determines that it can reach the identified user asynchronously and that the identified user does have the ability to approve this request. The AS indicates to the client instance that it can poll for continuation.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ HTTP/1.1 200 OK Content-Type: application/json Cache-Control: no-store { "continue": { "access_token": { "value": "80UPRY5NM33OMUKMKSKU" }, "uri": "https://server.example.com/continue", "wait": 60 } }]]></sourcecode></figure>]]></sourcecode> <!-- [rfced] Please review "in to for". Is the intended meaning "to", "into for", or something else? Original: In this example scenario, the AS has an application that it can push notifications in to for the specified account. --> <t>The AS reaches out to the RO and prompts them for consent. In this example scenario, the AS has an application that it can push notifications in to for the specified account.</t> <t>Meanwhile, the client instance periodically polls the AS every 60 seconds at the continuation URI.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /continue HTTP/1.1 Host: server.example.com Authorization: GNAP 80UPRY5NM33OMUKMKSKU Signature-Input: sig1=... Signature: sig1=...]]></sourcecode></figure>]]></sourcecode> <t>The AS retrieves the pending request based on the continuation access token and determines that it has not yet been authorized. The AS indicates to the client instance that no access token has yet been issued but it can continue to call after another60 second60-second timeout.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ HTTP/1.1 200 OK Content-Type: application/json Cache-Control: no-store { "continue": { "access_token": { "value": "BI9QNW6V9W3XFJK4R02D" }, "uri": "https://server.example.com/continue", "wait": 60 } }]]></sourcecode></figure>]]></sourcecode> <t>Note that the continuation access token value has been rotated since it was used by the client instance to make this call. The client instance polls the continuation URI after a60 second60-second timeout using the new token.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /continue HTTP/1.1 Host: server.example.com Authorization: GNAP BI9QNW6V9W3XFJK4R02D Signature-Input: sig1=... Signature: sig1=...]]></sourcecode></figure>]]></sourcecode> <t>The AS retrieves the pending request based on thehandle andhandle, determines that it has beenapprovedapproved, anditissues an access token.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 HTTP/1.1 200 OK Content-Type: application/json Cache-Control: no-store { "access_token": { "value": "OS9M2PMHKUR64TB8N6BW7OZB8CDFONP219RP1LT0", "manage": "https://server.example.com/token/PRY5NM33O\ M4TB8N6BW7OZB8CDFONP219RP1L", "access": [ "dolphin-metadata", "some other thing" ] } }]]></sourcecode></figure>]]></sourcecode> </section> <sectionanchor="example-oauth2"><name>Applyinganchor="example-oauth2"> <name>Applying OAuth 2.0 Scopes and Client IDs</name> <t>While GNAP is not designed to be directly compatible with OAuth 2.0 <xref target="RFC6749"/>, considerations have been made to enable the use of OAuth 2.0 concepts and constructs more smoothly within GNAP.</t> <t>In this scenario, the client developer has a<spanx style="verb">client_id</spanx><tt>client_id</tt> and set of<spanx style="verb">scope</spanx><tt>scope</tt> values from their OAuth 2.0 system and wants to apply them to the new protocol. Traditionally, the OAuth 2.0 client developer would put their<spanx style="verb">client_id</spanx><tt>client_id</tt> and<spanx style="verb">scope</spanx><tt>scope</tt> values as parameters into a redirect request to the authorization endpoint.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ NOTE: '\' line wrapping per RFC 8792 HTTP 302 Found Location: https://server.example.com/authorize\ ?client_id=7C7C4AZ9KHRS6X63AJAO\ &scope=read%20write%20dolphin\ &redirect_uri=https://client.example.net/return\ &response_type=code\ &state=123455]]></sourcecode></figure>]]></sourcecode> <t>Now the developer wants to make an analogous request to the AS using GNAP. To do so, the client instance makes an HTTP POST and places the OAuth 2.0 values in the appropriate places.</t><figure><sourcecode<sourcecode type="http-message"><![CDATA[ POST /tx HTTP/1.1 Host: server.example.com Content-Type: application/json Signature-Input: sig1=... Signature: sig1=... Content-Digest: sha-256=... { "access_token": { "access": [ "read", "write", "dolphin" ], "flags": [ "bearer" ] }, "client": "7C7C4AZ9KHRS6X63AJAO", "interact": { "start": ["redirect"], "finish": { "method": "redirect", "uri": "https://client.example.net/return?state=123455", "nonce": "LKLTI25DK82FX4T4QFZC" } } }]]></sourcecode></figure>]]></sourcecode> <t>The<spanx style="verb">client_id</spanx><tt>client_id</tt> can be used to identify the client instance's keys that it uses for authentication, the scopes represent resources that the client instance is requesting, and the<spanx style="verb">redirect_uri</spanx><tt>redirect_uri</tt> and<spanx style="verb">state</spanx><tt>state</tt> value are pre-combined into a<spanx style="verb">finish</spanx><tt>finish</tt> URI that can be unique per request. The client instance additionally creates a nonce to protect the callback, separate from the state parameter that it has added to its return URI.</t> <t>From here, the protocol continues as above.</t> </section> </section> <sectionanchor="interoperability-profiles"><name>Interoperabilityanchor="interoperability-profiles"> <name>Interoperability Profiles</name> <t>The GNAP specification has many different modes, options, and mechanisms, allowing it to solve a wide variety of problems in a wide variety of deployments. The wide applicability of GNAP makes it difficult, if not impossible, to define a set of mandatory-to-implement features, since one environment's required feature would be impossible to do in another environment. While this is a large problem in many systems, GNAP's back-and-forth negotiation process allows parties to declare at runtime everything that they support and then have the other party select from that the subset of items that they also support, leading to functional compatibility in many parts of the protocol even in an open world scenario.</t> <t>In addition, GNAP defines a set of interoperability profileswhichthat gather together core requirements to fix options into common configurations that are likely to be useful to large populations of similar applications.</t> <t>Conformant AS implementations of these profiles <bcp14>MUST</bcp14> implement at least the features as specified in the profile and <bcp14>MAY</bcp14> implement additional features or profiles. Conformant client implementations of these profiles <bcp14>MUST</bcp14> implement at least the features as specified, except where a subset of the features allows the protocol to function (such as using polling instead of a push finish method for the Secondary Device profile).</t> <sectionanchor="web-based-redirection"><name>Web-basedanchor="web-based-redirection"> <name>Web-Based Redirection</name> <t>Implementations conformant to theWeb-based Redirectionweb-based redirection profile of GNAP <bcp14>MUST</bcp14> implement all of the following features:</t><t><list style="symbols"> <t><em>Interaction<ul spacing="normal"> <li><em>Interaction Start Methods</em>:<spanx style="verb">redirect</spanx></t> <t><em>Interaction<tt>redirect</tt></li> <li><em>Interaction Finish Methods</em>:<spanx style="verb">redirect</spanx></t> <t><em>Interaction<tt>redirect</tt></li> <li><em>Interaction Hash Algorithms</em>:<spanx style="verb">sha-256</spanx></t> <t><em>Key<tt>sha-256</tt></li> <li><em>Key Proofing Methods</em>:<spanx style="verb">httpsig</spanx><tt>httpsig</tt> with no additionalparameters</t> <t><em>Keyparameters</li> <li><em>Key Formats</em>:<spanx style="verb">jwks</spanx><tt>jwks</tt> with signature algorithm included in the key's<spanx style="verb">alg</spanx> parameter</t> <t><em>JOSE<tt>alg</tt> parameter</li> <li><em>JOSE Signature Algorithm</em>:PS256</t> <t><em>SubjectPS256</li> <li><em>Subject Identifier Formats</em>:<spanx style="verb">opaque</spanx></t> <t><em>Assertion<tt>opaque</tt></li> <li><em>Assertion Formats</em>:<spanx style="verb">id_token</spanx></t> </list></t><tt>id_token</tt></li> </ul> </section> <sectionanchor="secondary-device"><name>Secondaryanchor="secondary-device"> <name>Secondary Device</name> <t>Implementations conformant to the Secondary Device profile of GNAP <bcp14>MUST</bcp14> implement all of the following features:</t><t><list style="symbols"> <t><em>Interaction<ul spacing="normal"> <li><em>Interaction Start Methods</em>:<spanx style="verb">user_code</spanx><tt>user_code</tt> and<spanx style="verb">user_code_uri</spanx></t> <t><em>Interaction<tt>user_code_uri</tt></li> <li><em>Interaction Finish Methods</em>:<spanx style="verb">push</spanx></t> <t><em>Interaction<tt>push</tt></li> <li><em>Interaction Hash Algorithms</em>:<spanx style="verb">sha-256</spanx></t> <t><em>Key<tt>sha-256</tt></li> <li><em>Key Proofing Methods</em>:<spanx style="verb">httpsig</spanx><tt>httpsig</tt> with no additionalparameters</t> <t><em>Keyparameters</li> <li><em>Key Formats</em>:<spanx style="verb">jwks</spanx><tt>jwks</tt> with signature algorithm included in the key's<spanx style="verb">alg</spanx> parameter</t> <t><em>JOSE<tt>alg</tt> parameter</li> <li><em>JOSE Signature Algorithm</em>:PS256</t> <t><em>SubjectPS256</li> <li><em>Subject Identifier Formats</em>:<spanx style="verb">opaque</spanx></t> <t><em>Assertion<tt>opaque</tt></li> <li><em>Assertion Formats</em>:<spanx style="verb">id_token</spanx></t> </list></t><tt>id_token</tt></li> </ul> </section> </section> <sectionanchor="extensions"><name>Guidanceanchor="extensions"> <name>Guidance for Extensions</name> <t>Extensions to this specification have a variety of places to alter the protocol, including many fields and objects that can have additional values in a registry<xref target="IANA">registry</xref>(<xref target="IANA"> </xref>) established by this specification. For interoperability and to preserve the security of the protocol, extensions should register new values with IANA by following the specified mechanism. While it may technically be possible to extend the protocol by adding elements to JSON objects that are not governed by an IANA registry, a recipient may ignore such values but is also allowed to reject them.</t> <t>Most object fields in GNAP are specified with types, and those types can allow different but related behavior. For example, the<spanx style="verb">access</spanx><tt>access</tt> array can include either strings or objects, as discussed in <xref target="resource-access-rights"/>. The use of<xref target="polymorphism">JSON polymorphism</xref>JSON polymorphism (<xref target="polymorphism"> </xref>) within GNAP allows extensions to define new fields by not only choosing a new name but also by using an existing name with a new type. However, the extension's definition of a new type for a field needs to fit the same kind of item being extended. For example, a hypothetical extension could define a string value for the<spanx style="verb">access_token</spanx><tt>access_token</tt> request field, with a URL to download a hosted access token request. Such an extension would be appropriate as the<spanx style="verb">access_token</spanx><tt>access_token</tt> field still defines the access tokens being requested. However, if an extension were to define a string value for the<spanx style="verb">access_token</spanx><tt>access_token</tt> request field, with the value instead being something unrelated to the access token request such as a value or key format, this would not be an appropriate means of extension. (Note that this specific extension example would create another form of SSRF attack surface as discussed in <xref target="security-ssrf"/>.)</t><t>For<t>As another example, both interaction<xref target="request-interact-start">interactionstartmodes</xref>modes (<xref target="request-interact-start"> </xref>) and<xref target="binding-keys">keykey proofingmethods</xref>methods (<xref target="binding-keys"> </xref>) can be defined as either strings or objects. An extension could take a method defined as a string, such as<spanx style="verb">app</spanx>,<tt>app</tt>, and define an object-based version with additional parameters. This extension should still define a method to launch an application on the end user's device, just like<spanx style="verb">app</spanx><tt>app</tt> does when specified as a string.</t> <t>Additionally, the ability to deal with different types for a field is not expected to be equal between an AS and client software, with the client software being assumed to be both more varied and more simplified than the AS. Furthermore, the nature of the negotiation process in GNAP allows the AS more chance of recovery from unknown situations and parameters. As such, any extensions that change the type of any field returned to a client instance should only do so when the client instance has indicated specific support for that extension through some kind of request parameter.</t> </section> <sectionanchor="polymorphism"><name>JSONanchor="polymorphism"> <name>JSON Structures and Polymorphism</name> <t>GNAP makes use of polymorphism within the <xref target="RFC8259">JSON</xref> structures used for the protocol. Each portion of this protocol is defined in terms of the JSON data type that its values can take, whether it's a string, object, array, boolean, or number. For some fields, different data types offer different descriptive capabilities and are used in different situations for the same field. Each data type provides a different syntax to express the same underlying semantic protocol element, which allows for optimization and simplification in many common cases.</t> <t>Even though JSON is often used to describe strongly typed structures, JSON on its own is naturally polymorphic. In JSON, the named members of an object have no type associated with them, and any data type can be used as the value for any member. In practice, each member has a semantic type that needs to make sense to the parties creating and consuming the object. Within this protocol, each object member is defined in terms of its semantic content, and this semantic content might have expressions in different concrete data types for different specific purposes. Since each object member has exactly one value in JSON, each data type for an object member field is naturally mutually exclusive with other data types within a single JSON object.</t> <t>For example, a resource request for a single access token is composed of an object of resource requestdescriptionsdescriptions, while a request for multiple access tokens is composed of an array whose member values are all objects. Both of these represent requests for access, but the difference in syntax allows the client instance and AS to differentiate between the two request types in the same request.</t> <t>Another form of polymorphism in JSON comes from the fact that the values within JSON arrays need not all be of the same JSON data type. However, within this protocol, each element within the array needs to be of the same kind of semantic element for the collection to make sense, even when the data types are different from each other.</t> <t>For example, each aspect of a resource request can be described using an object with multiple dimensional components, or the aspect can be requested using a string. In both cases, the resource request is being described in a way that the AS needs to interpret, but with different levels of specificity and complexity for the client instance to deal with. An API designer can provide a set of common access scopes as simple strings but still allow client software developers to specify custom access when needed for more complex APIs.</t> <t>Extensions to this specification can use different data types for defined fields, but each extension needs to not only declare what the data typemeans,means but also provide justification for the data type representing the same basic kind of thing it extends. For example, an extension declaring an "array" representation for a field would need to explain how the array represents something akin to the non-array element that it is replacing. See additional discussion in <xref target="extensions"/>.</t> </section></back><!--##markdown-source: H4sIAAAAAAAAA+y9237bSJI3eI+nwKouLE2RtCWf9XXPNyofqlzlU0uq6e7x 9GeBJCShTQIcgJSscXnu9gH2Yu/3WXbfZJ9k45gZCSQoyYfq6t5R/X5liQTy GBkZ8Y/TcDhMlsVylu+mN76vs3KZvsxPqmWRLYuqTLNymu6tlqdVXfwnf/K6 rpbVpJrdSKbVpMzm8N60zo6XwyJfHg9PymwxnFR1PlzIc8Pth8kkW0Kb9cVu 2iynSVIs6t10Wa+a5c6tWw9v7SRZnWe76UE+WdXF8iI5r+p3J3W1Wuym37/c e528yy/go+lu+qxc5nWZL4ePscckaZYwvrfZrCphFBd5kyyK3fQNdDtI4X9F Oc3L5SBtqnpZ58cN/HYxl1+WdTGBrybVfJHJL3N4GL4qyllR5oMUZjfPFoui PPlLkmS0BLtJmg7hgWY3/XGU7heT07yGj9KUl+FHmFBR2s+r+iQrZeF20+/y ZlG9y9Mn5Qn0kNfQND2Vz7Nitpvi+v3LX6mNUU1tjOB9egKWZTc9XS4Xze7N m+Nm8W5UVDfpm7rCjcunxbKqEz+8p6P02XycrWZLM76n2bjIy+CLcIDZJK+X 0LQd1TG9NCr4pX8JHgmGpd/cTJKyqufQ5Fm+S4999+j19sO7/Pv+00c7tx/e d3/cvn37of/j4YN77o879+48cH/cvXfHf3P/zj3/zf2723ftH77pe/fvPDR/ 3L3l/niwff+O/2Pnrn/swf1b0toPh4evd/Gjh9vbt/Rr+H3bPfvwzo754+7t W+abh7ellb2DH4Z7z7/nv9JUDtrGS9iQKZDzMa8UHKsfsuY03ZvBKSmWp/N0 Pz8pgEgvNvTFrD7Jl361z8/PR0VWZkgiN7OmKU5Kot+buNXTYeFb7n4yen+6 nM++OYUeh9nsRHrwJM4/Q/cbkQkcvr2Xe/TZq2ePH7Um9GqRl88ep4+qsswn S/i3ztPt0S0gRuAFi6qGfsuTNK/hlyxt8mW63TOvChoqpiM44zebRT5p5ANg KdQys5btt7dGOAVpYwrcZTd9WZ3l83Fepw8G6c6t7TtXmBYdlZej9CB7V8xX ddb/EBz37+psOssv+p95MUp/BEbU9D/x3Sid5umLfJoXdbXmuUej9AXwrGIO k6XvDvZePN/xc1Aq2msaOHOwow3xaeXMKex0ujzN01d7B88OHFtN3ePpi6x+ t1qkz7PyZJWd5OkmdrCV/uvO6NaG76W1NcAQm1GVNUUzxE0hymuk7ZtNNp/d PIP36TfeJvhrWDWjxfTYtclbBd1PTmGTbt11X7S3KVwVWZeDUfoILqiqXv8Y bNZP+Xyx/qH9Ufr6tJgtquVy/YNPYDOyGTD0xB0hZWzIzG4ZxnRn+5ZhPzu3 dvwfD257lnXv4f3blmU9MLzo3h3Li+6bPx761h7efnjPMJs7wnmeDR+P/CVc 5021qif5EDb9LK+b1jMVrvhQ92+4rBbFpDHsbEf4IFzj86LJh0BPeIG3ju0N JA6gjTkQ1HgFnzUN0YW81dAxvRHyitf8XcotBmf4x6xcZfXFtc4vHLvvuOf1 xzevT4Ch8hnf+9OT53svH8MObZtTZedEvGhajyan2WwOqzdq8puncMhm+c2d W6O7t26NtnduP7h18/Yt2PS7N3wjPEd/5spsdgFHJq2O073lMpu8Sw9W9TFc lvBRSaf0OkJX6yDhBNYcoTY9u/X4f/73Ubr3Pp9BR1d5/NUofbXKC+iTL7Un z18cPPrhxbPHhzCAnZ4VRI7xfjStCiKIbViwB3e2HwI/XzXD7Z2dW7evtmif v0I7n7JCIED9kM/mzeR0Xkx52gevH9y6de92++rbeFycFMtslj5DaROH//2q mOYoRGI7wOxrM2bHsfsudrNg927tPLj58tnB4ejg9Qj6Ht67PQmPy6rM8azc v+pZeT3CtQRpof8RYHcvs2merdaeJiPjRh8BTn3wH6tCrq++Vp7CglXl2qv5 eX78rjorlv+5tqHHWflu3XD+DBfHaVWVJ/2P/IRLk+flmhEDpzkEnnWclXJ5 o0Q0guu8yA4vFnnTZo4blwprc3x3uMSX7e8soG1cYVePV7MZC/dOOnOESQNL aWRJwqSJjRw8ef4UxgZMPi3hZyNJhsNhmo2ROU5Ap0KNC8SUY6TfNEvnObDA smjmJFUAXecnLMxlwfFbVmkG2lc+yfHQNtXx8hyUugERPchuZ/kFvoOHGe4l UCRYYsngLAAvXMpJz5auA24Sn9e2cPGLJjEPTLISBczZCoSqbAIctaFhkHyJ 7Pb1M+ilSc/z2Qz/bVbjv6JwaiThZAG7AYL4FCh1spxddPrkxQEWAIw/Sb5B BbSupqsJvZzggFLVc9NsNqvOcckiy4CNTmagSGH3qLVO8MMKFuM/Vnnjpp1P k86y6j2eyj1OCxeZCxGnb8ivSCKrbluhtRvn6QpnP76IjY/WktvQl7lvXNek wtfhbjyG+bq2q/Myr3nPY+OIDFr2MF2u6quMZ56B+owrhOQ84Ram+aRokKOO eD8MgcBfQF3FDNjzktuF3sIFluVYNSvYvgu4khOZVtWdGa9wDrODYdYpCMGi 11iSkRktczpN56DM0dfRXnGF/WSAIoCWzuDuwBPTEHSBF7S+msvxYYrJmu74 kCJzbIRWHKZ7fgp8ml4zq3KaLUB8b3B13pXwIjd1gncsd0gcQKhZVYnSXL5y K9Mb2ltS0YSKeY79zuGEF4sZjAVPONLNhBYKdnpaIMABVIDIRTOSQ4S6XnGs W3pcTWCFnYC0qETJkY7NXHSuuM2yES2yGSXPSh7GZDXLajyKnf6U29G20baO YezzHNZ9ykuQxahRtmLgFicfJEj7wEty0BEMT7IU36LIPuIYxRYmm04L/IVo VUdtx7n2HCfIquAA5lN7opeWjtb1PWsq3D3YGtwb/A33/MLfEOuGkABJHxcn KzggxbLJ4YBNL+DigsZhKiOi23melbLaPaeUFzdkZLS6um1LWEuQOXSUU2It OB6E+UraaiCtOR2tDx/W60sfP8p5Impk2rPsvqCd1RNrSAd39wKY2fIcxAkm 2OL4OK+h16R7HvIMTiieBeab0GpZLbFlXv2LtJjDQcIhK60us2JG48FXR8kf QRCDaS9gJIuaiJBAU+CVF8wvgRwJ3JxmAhWMq9WSBwyE1Go/kfYH6RgegsE3 kQZqIirgIbidxPxUcpcTioQBGwuNLWbVBTaewuac4nYBqeDLY+RTeTOpiwXq 07pR4WBG7Su2qWZnSPFZ6bpqQPpBfgx8F8kSeNkrVAzSndEt2GKBAT9+HCQt iOrDB4Sx4AtadmzpGMhxRu1qfw3LJKfZGXI7ZJWrRZLV1YregG9gYZqLZpnP QVuozvMzvP1o8WUbYa75+yUslLBNN7TE7DXuRDkFYuVlcbIIEe2yQFZE14h7 ecR9NHn+ju5VpcHjVTlh7oBbQWICrpdZHRq0Xx+4qnAAedbAxBM4eJMZnEHo GvhMjao8rNJZw1DBzseP0EFNm6g0uOTbhveGtZxsJqet5gn5Qcu1AqPyAzgv QDSbFe9y6DN/DzcD0gG8C7STzxJkBbTVnowaJ1E2hSpWDW/QmE4bEDzRl+ey JP4Iks97DfdWUzAvrqs5d4xf+nHxptIBx1GDMlMBleXvMyRPuOuO5WSIFHVM FAFD//BBnnFrBiT8zTfpYV7Pi7KaVScXzFPe5XA5VzVw7Y0XPx8cbgz43/Tl K/p9/8kffn62/+Qx/n7ww97z5+6XRJ44+OHVz88f+9/8m49evXjx5OVjfhk+ TYOPko0Xe3/e4FXcePX68Nmrl3vPN/j4ofAk7FHP+Fg4G5xVkuVQ/sZDO2be +t2j1//3/7V9B+b9vyEWtr0NJ03+QIwd/jgH6YZ7q5Cw+E9YvIsEpZCsxlZg t2ElF6hE4/7CxXOKZw35GizfP73BlfnLbvq78WSxfeef5QOccPChrlnwIa1Z 95POy7yIkY8i3bjVDD5vrXQ43r0/B3/rupsPf/c/ETBIh9sP/uc/J8L23GYA ucOBK5FdlENnXHH0SCwLLxbg5nw68GO4C9GGAddq02QnOazsjwevXqLlC9QX YNzwwc/7z+D/IMTUzG2qko8YUKcctIrOe848GfgBXDYlsjmQyUCNHc9EtXEj JbENmhWZEh6ui0kKBDQfpE2BokABtDUDBbhhpsbEgoYfIJbORQMjgLlO4Kzh fQrNpE6gJq65ZI5GfxP6clzkNd18Y7y24H4kSW55Cjz75DQ9y+qiWjU3dVws cWxafvXz/vNmq3XeiYFmOP4TbKwG3ofsYpxN3jUzNNsc/fsRyyFTkuNT2srz WngOsrFZBb+cZbNVzhQOggLfTojrApcgzQKbgRGj4iDCDrDjKTbRLBQwpFZh qDNWz+GUIgfH3dcLkXoZtUloxew/p71IN+arJSg86eHzgw0cDouSJI/KqG7d 1VHBYaxhqeFblGGBT9FLRcO6GipleVb6qxjYSHkC3T+FWY/r/AyuooHpGLGP DMlvA2dToOZ/XrrWOmyIpOxjFvPGQIxwOzLY5tqB/WMthzapuQD6QdtuOqkv FssKdJTF6cUWLSZQNXTxYu9R8ErPG0ACBYgDWT2T4QPRj3n4GzykRsECoian GeUFHZmsO9IUVsSNgUQkPCJwkEvzzBjuaV73/4ANQnqeysp12nPjcHL6zCMY IOItVkQTKExHJwl/YVtIX6LKksQF19U+qmaiTIrACjtD9zc8SGSQTfiIwsWH AoEKuKrVUQtEnoa0SNWR9/iiVtErfw9TWMqpnyGDAY41TUT/wzb1fZEsndgB A07+67/+K82y5uwk+XZof75NzU/w1bfJL/a79Jf+P5JfApy5/eS+qiP4JHx0 wFpJrE331S/t3n/HY8Uh/nOrdx72t2ZGv2jbrRnxG//v//l/tLr9pfvNt9zi t/H34KVHrL/F3v0lfaZaXbxlHW18RPR3ko7ccyPzOf8y8rMaBSulv3/7e/wJ dpeW1O1FZHOfAKW5B9NXCJfQV/9l/qMHf25k+6JdR/6CVThyAz5Kwx//zfAo SZ7nwCumSULjd9dF4+CiglA11huz9HQ1z0p3oa/gkYQauuTF5XnFCGRjIciE p+hfzeAKxxsUhYb8P1YFXBs5biowKeAdw+p4OA6tQ3g1r0pFA7Q3Ou94ApMP uww8/37jKev527vMSJR3bHxMktBmIydic+9gazfZdRo9XukELjUGRgTd9qyA P3IBeT2k42EGmK8gDw6NE72SeBYyQ4Vk3iEChnMlbm3xmc1mBVdDHC/eYta8 d0A3VlmA6OSAGMfi3jIwBju9qGCDUBx6OxAoruBLOBuDZgY7SqLSOSnw/JJA Ssw6YVa1oEQ8LYTL+GjicoEgMNPtoDVDrQiuTYvXkoIDYh1OtSG+Okv3D0AG EfntgnosatKNeG3MQsfe3jtoeBEU42nk9vAL4BHSGsW9eoWi3GpZldUcpC9C WdM1KGtCRPeEha9dD72JspWl82oMA7TzB5kqPc/H7Y9QQhviaKbodiJYYQU6 er6cSDcvKzSkxTBBvdIKOi7+WOpjnuw2o+i+E0hpXVDSYYJBGWDL3XyOUGGV SoUwoy3rk0CDKFs1KKG+g/PcRMieRBbEoqvVbIqLRmq0NuutLf55gqFcvyRl Z+ZahzHDgjkGqwd3v3twBYxA4R0tBSmDtG3YcSBU7wQPB/biO0yTuNXAlYpp cGqB4JqVgPnsQwh/7B3Y0TF339x/xYOTYyzGWRokagh84MimhWhSMBB/gAqE fxqFI+H91YKkJEs7JNXgmlKTJE9xq4w4+LZVM5mjm8Ms3SxGIOupcmLMBvio bAHIog1Kdih4NcCAsGk8S8iPJq0WQElXVmT9+uDlegV8eAuG/USOJi4MSZGu ZV4YOcpNF/BuzRmebb2Pc6tY+UKVZJx7nUCWPmPmt/9qlLBwCWQCAiiuHBsd q1xgswb5WEooX5kb+CdFx6ECiQkumEEyXvH4QEtKM1AP54sl3Q68Cnw3CWsU oGY1Oy5mM9Y0srRcocMYwjme0s+zCwah/UcOPxulew2rcqzekuxO0qk03CQo m0J7pNiMQc81miyyvLOiqpuWxmVRtIFfiQRXgg1eDvXXk0HauCpQTqNnNr1c LWB9X6gFhhehM3/pl7YHr9IL1vd1UvRRgm81QIiCUDdsv9FlabETPwlmUKI9 DxLec2re3QxF2WZJWW0IhklKmUQm7zTOFNZj62FTx1JYSVGTbqlmSoYJ9g9G IMAyw8c9HSRIYTRdt4msacqk/MiHNApaCIeOOxrL502O2HTCFzfimrrFTY6I 5hIlBcYbkdWy3IHjRTsbERx9lHiwliePWBktTrB3fhdEQRONOysFsdHFh4Wm m4IxofdpM8lLREEI34HVEGMVLqiTPdy1315epAdc3wym2fmSzWRTWHIgyDyb o1GgKqfozgXdwDiqespTlpng1BLYzZNCKRt6b+0ODaNjT0ehg/YoKxNomwm3 Mx6chVknIClUMoG8BdsC1u52nODchDfT7FeGlsVaGVdb98RhwBQn6JI+hQ3Y U4iIWEKZw1YJJ2QORgAqyS9lNQP2jgo43JwFMNfwxHQnwxc54dwwr3JJUo2H 7JjJsbwLbxCVyH2qR+4G8hzsC3dPXSKMiMSQt8fTgm5E8M8ZtIM9OrZnBFbO DIUF82KBQJhI36HBVhidI2xqSRF90PotmNW+hLBnFm3onIlMOqkWhWdDLVko oSmBeGU3Fo8vbmVzGvAdhOXhZs1r0IoGqSoCWeL2bzJDgYOsyLnSKX8kxCCT 8HBhzBytxoMGSZENhGIUN+sIsznHkbfbpQui1WqCty4BYMBT+VZLg1stVN6M xdaYKeeDVG4v0lWScxUebfdl3B7Zs1988VUMRDWwTble9j38iqTGAyF3NAyd o6cojGG8KmZLbYmuDhwViBUrNKuaZaOLHdezLmCTcchGZBDNRZ/21N5eT8TS GmuKk6XwK0rsZRltLYE7Q0U5gblRKKkRs3eeHYyGo7TLfWX+anRCYEIH3vfp zKwt+5fepnl5VsCxFaz+KVvr0ImcL2G3sMSaYEhwDmek4arn4mSWFXO1EMvt 524D5hCJuGllM5kaDRqkL15vvLZQOVNQ1OuVonNny0Q33bIc06CbJVwNpzQR XWrDw4EMyKDoaJbPFJ5mD37IpEnXqk5y6tRePsSnzXO9YhnRTeOaxtNGW+Ol DDWnJ8FJa+xRYwSAXIT8geo5G4jCPhGrS/rhGzXAfEyQfag8qFgvX1uwaWdi jjEuaQ2aJc7YbC7sMtHW/K2RkXaGqo3OXOUa0iyUGkSDxquO9/QQ95SwCFax 1Z8PbnO07uesDTmPPN5Q3I+blaWZQLcgGcPoeyq6FjWah1n5IwSofUduGigj gJlkSqAPqu9cg8JGiScbVgqhCxgBORnjXDYR6t/aJe8OtNsuWTXrx5jISMEu PyRrmcNA3jUOMSD3KBwCq7UsMblvpyvvKIzrgy4W7/N6ghyQ2pVV9JiYrKd3 1Msiuvb/wCmV1arciuuqNMemUSfOiN73WhEhXB3qM7Xbh+paNSloRKK1is7d 0ZOBnTjPUrLtFWLYJJJz1BGsoG9cyL07RZbn5jQy1AKrGkRcAuZ4pYLlA8rA kxzCiaWTk9jN1DmWFQ1bWYToDDxmpBpaIx2UwhC4WH6oyOg39wxiBy/AFszn uAUU1ogxAVsMpairosi2VoPljVb8g/dqkBbH3sSOvytuQtR+DMRFW9qCURSq mYbbBLM8q4qp1xhytLROVFRpoWRqqEOW2KBocOENdhu6PxtOS4f13+ju3wai N7h7xErEgYoVUXboFQiHTyTbn+R7j63gwfFQItul+H5Gn92ZmML2ESk64PZo hxi8QPXLQCZi+ZRu0cN0ygoZ2/aQVKh9Zumo5hRyEyMBe+KVTUN/tFkl5lK+ +7zaJoOxwYCMqfHFgOyJuXX3YOS1d2vF+4uubX/65NIyTVzB6zdrnDVZ3PAi vrZ4Q5FfC+JvsOgzvu1OiwXeVoTKfWx5kuPK0BdpRaMjB8lmN90QvkDfNXoV e/cyIVoiaB9HYTQK8ddq+zVSC3ykiXIZIgOJvZ6Kuq+Y+obYytuj083LScJj 8zSyoMicVYp2V4K7YsllkSGDnI4OG2nJsgo3mhvjzf1XA/+Hnmv+9+bewQAI lx7Z8/8cjGT9ZatOcB8FasbGaQLiVXXsusSDzxaNfOrlX34Zkc55ht70GvZF 6npFEEUgWIhit8ig8c18dDJC8HFYc9Cq4O+rEheO25m2DM9eYCdEszU+dtog t1k4KjilkkVx8djoGzYrbG7sPLCMOVmBaK8Qu2ANW6P0CWIx3IolVJTo0I9C PHbFr05IjQLblP3UevVPR2qyYLsbDsU14U4eDnoMovFxoTiLE/fhHqDbk/kD jamRKTTZcb7EVdAJ8KEYdL1OqQUnzlN4fFZPmy2JQKiYWnhHFURzm7rJwRTk mIq4osrhSMN47WWTixCAFGdn67OzhXYXEC3eEQzu1gu1xqoWOU22ZVHBZXjh eApvoXClvQMZMnK5pqErBloDkrkBvGA1K/2UcQuK5h1+zWgLCYBCQbCpeKiy E5QykGbqPEMPJzQAAXtEScBsEl5ioOrnpUNP8PLI3zs4woFUqLuaQA5mWvw6 3hXEfdgRBB0dmHHApoEUxiYHuBBgX9LTghATuYdDljwQvJKahTt1RYowMJda VCmZBQ+YlrsMbmgCGJBo+JZSv1Rk/uLg5IhZhQtQNCdypSzQd6daBTZmoccB ivc5S6CCGaJt4XlVvVO/KBwL4ZxdbrmbJEPL9sT6Zh9hrtV4l8HQrKi2M4Rm a6MfD/xkaerBS6jzNiwIis41JqHRhTehTJwvXTwHNC66errZ5Hn64UOgVHz8 uCVuuKzpzggtZPMrOw2j9d6vrAnzILZbvuPAAD2q3uV487hFW948NH3Lslvm ArnJ51Q2YSj3Pg4tWGOmp1173RMyQQAgryhym1H6uE1KcKuestsqywyb47o6 bxD/Oni9N4gaYp9VhwI0Mn1uDXjRAzLq2orUnzDdJC3c+Jj6+WkTQzKM0w6I owp0mM+QDzYenuqyKr9TNKK2tyE6rGFkzYKGSQJvU/m7xkkTNGwKZ5iyDrlq FAnwsWrOHdy8RvoJqeSoz3LECl7cFBZMCG1bsyQFcVFV9exi6CZGMCRzCGT3 SM05GaJykJH+k7l3SAB7B7v+GGkfqwVy5EYMzt7weJyzJ5pQfY1JS+AcuNWH dR+ER6uNdYkI5wl372DoeFyhug4h/YzkKRBaNC44yb0tQDSe0jKfBSP1Ql0A cwuNAo+jCbgQ96Ah9GZXK3oXTSOuJZygCWmXVtbJZbvpXpmeYtaHpd4Al+wt 0beLT8F0L4zcwKJK8EyNhNOIUstO8wTKkTUQ20WyrbRtonim2Gym+Gbd1tPQ jti0vV8WGbojiFatjIGEa5aEzI13U8kgbSanOR1nQX7F1eAY+yTFkRJ9vAcp UHj/6cWiomVsFDNFRBt2hM3abdvOKP1zvrQ3qg86IKNuKEei1bdZ+gNcLazF m8Jo8NxgHA1jH7QADsNp2B0ZTs70QjSQQTrlRSHZVm22bQURR47iC5od3EFh LsUtKxMmsX1Xr3J34RZLVVpY4PR6S+AbYyHYVekCAadOAHRaP36A1u+uw0TT 5zGB54/vSUFmazaAjDGagWIR0UvZKF7ezIsYPEWdoUDBzpvoH6w4LSnZQ9ZV dnUv7ZOhVuEiOAMRkBQikaHkoLtz6IF0J4EYocQe14FxmEB5hcgicscwIjjJ 6VZ5LcJuizHAMWSsb7qaSDCmCJ6ZYwJkF66qIfIclJ5QdascEKG9NPLSqnRL QpyUQFT4qELV163hgVtDRz8oOuCuRvcbvgTtGA4Yzrml8zTiM5IdLykKuK7J S4WAAx9CRmdgCvL1SU5CiEHGRfNjZ2ARWtRh3p0+DfYzAWMULKgu5leIvNtL T2bVGCMaUKpaLK2GoKIs49cB1hs60MU0mCan6J8zYbB21qBdNuRSTg5Zudoa CElEXueJhduFSwSb+PBB2paBE44zE/Y3r6Y5WYrbSH/X54y9Csjw7uxNItgg fdB9hAIZepE1zjqJvdsULRpz5LIBPcVz9uEb3SwFZjA4Gg56RqY8jidFbxwB OulwRoK4JarehYYY50hvMI14Tg5kAhnHBqMId5IPGJs6Xs2caSFEXyUIuePt EEZeet9NBmhOc2dawploMEW2OuGYglPBxFrxxH6a7B3Q+PQEEglKoN/swjhL wDvsRzavzry9xBmmqRv293FTsB7w6WIGkhAi/21lfNe6taef9jMSH+pPe1ud nH+57vvil/6tOOD/giGXIEyt8p6GcJgvc0qH5vj2MHSF/2XNQG6umcFrUWfQ w/4o+vpNHsDTAnTA03AE3sE82vNN1/cm8ZCz/Cb6/G25JfjWesHH3+wdefet y1/ClUadcdZ5Gd87W/9ueha+9e3QhBd8G3menfD5pzXJ/mgK+QlDAjAgADrZ F/kJ9/01n3/cOhnGU3QSAtGHCAPf1w+mHFDwmf1/sbnDz7/j//5X5DXz87+6 G/zv7n+9P7+k+/kZZpAMMqBdvYFf3KrFCHrN+yYKJUbQ8hoHO/y8wOREsfXr OcC9Q/4l3eODNaUD3MfIuNuXVYt/2Eiadfyj98cF3VyVkV3288kcVX+OJJAk Gm6xs5se0K02LTK0LLJvfRBWYO35GpFx2L4NwzcKL/mxxbbEyCwP06L655Tw ji0JsQ4G3ih5C75LF+tZkZ/H+3NpRFiVZbzfZjJp1DdBmhPghWbAUlZDACxO q1/Uwrhiz2T+CQ1uGNoKC/ZGR0LWeZIH/rL5jVoM2B7MgL9dhAymed5duknN GgnJn3jVO/n57cL1/lZG75oTIcjNiZYRgR+UnwnHUcMOMshOpys6gP0GvlIa sVAKOZlx1PDUu2DSCAZG+SDbcxNDxlt0hsj7koLec2c27Xi3ByASrDa6TTUK 24l7BDGAbNYB4A87faIViFwmiqUZPQjRDE2kDsEQSLbOMemQdyuIuRq67s24 BnYgKvdVsqksb+iOKlC9dyC9IeD6ZiJcxI2I6EtQNv1yK83I0ZwdKsqLQE95 Y5dSX21sM/rAFk2jrEQ0j05HpfY2QugopnD5SkzIroIUtc4Ql9VvOqtmLE7j zlB2BufCvG4NRZia6iKyG/SbUMVF2kCXCnNAZeb0ADv6vInoIfZR+XpLKcI7 F/XRg0zVTVNUUFhf46PvTzY1XE1AWfRRZRlxN1IGa4YAEIc+k5xDeV1XteCr nYM9p6tQ1+lYBSBLbagU09DEqemfRAK2HE5bdIx5LOlj1PGEoJfqsgPbORLh eIlf4XTd5eJOR4fBlFULwZANoRaFfRINx/OH0WGege6+ZvP+SF6J7fuwaFzI ecjrNLdKeqJpa3LPmN4o9sRapYEfgLqCv7dcRiSvL/JMR+leeyx2IMz2KRal 6131VpiEuEOYlXvL4F3PKtxoCN9rA/vKcgQSNwmGlM9H+3KsJeBGx6xIMTro L05vu+EH6CJtz0zsgJJUK8aJKCCFDLrpm0U1mzEa7tgpvQmd6kdDfGZLV8Nd rNfnxezT2iXyGpOklx0iyqx5PRKj4nrF30/zybsuJqGGuKA/vpPKT19xkYG8 GBI037/mfp0s32YM0YzFLj19OTRfmn0gabAi/1m/4/4S7UhGzKPqfJizsd7K XiPyW1MzHUqAyG+9s1Z309x15Jgeh+sVvllkgOygLQN2vLJrzscnMA1nj6+A CiB6ZyhZlPgoMISFYxGtrSZu3Q1PLtRF5wxOKd0ZRdRVobWzev1Ym1nWXJQT +LtEoFphKWd18G4NAm194lZd/eK0VO1uThOGwV7bwWOa+469sYu5elTXLMmf VZMAFrYEiqjfMg8leu/U38nV2SEjuXnWX8p4BasSG7uDu7Qonp+v9NJT89eX voydmNW5jZ1A2XONBHlXv6ZcRpQT3j84X1JvGKMnRiuqAk0hws9ENNUB40dv gkbXsv7O6sC9Y5grkWrYGNsfLmGFmrhHJ0BKGYYlcHZcimIpWRpUToTk31LZ 2OGEqM+nQLN6XDQoh27Q5npXqL8A+0WnN6gCB+QQ2f9Q1BbWpQ91eLmIQKxG N6Jl2y7YZEKxL6oPtyRJtaSIo7/4rCGK5mwqSBHsWMOYAlkJgIph+PTx0H+8 FeY+6MolcFcygUbJwi7svJoWxxdbfBdO1ULdlhMH0LYfZnB1misGPa76efIx eSkqRyb35quy5FAe513TjImdh+3JFLWCrNLoOOTvnzUipfDx/P0CGVmgBl2q /iCndZgwsdo9Ek+M2d/YuXUmhV8HF3xOpi9SubtTq3rFpijDjY/08+CdN0q9 cXwndsVpcDEF07Veh6lvtoUDkwAm1ewyLoYmGD5FBItHk06huL6ejCY/l1Du 2IfCaltwHZ6SDZqEtNg5ES/iFoN0KhtyibKyKTVjUgRdKSpXjdJXBH50VNUO m2sfj8tUVcadBnrDB55x+JC3DMbH0IPSZszcJKkn9XTGjslw2o9XS+NNT883 Rd1LRXFEU2YgqOaAsIuZD81p379wJFntLpZ2hxkdxIBaiVugkE2a2wwHZ6IY fTbVLDAVS3QbhbcA6Zr8oHyLUoBjhrkcDPBM01zVHEm5BvGm0aCFPxdvKBHc G8y4cZw1pyqCoaQJC3AhyBjL6jaPYsD0OhlaKtDGQfzHtPvvnLZtx8d2/APn M/LhG+elIjZ8G89B48YMhznn4aWb05nyl+IXlkSSZ6taIyT3AnlfmHPbmuRr jPYuTR5qifTrOiK3NBKbxTVh2ifPxfqC9SClcgTDyEBAW8kOgammCS3qyWou wcWwPl5eQDd/yuzbyU7lGtYpOFZfYjRnQ7FiiUveKK05L2pHbpJIk/RoNuTX VcObe46VLmzGZxOQLKCnK3+gQyJqI8+ISlLnZIlJasVLYlgYrxSbRmy2gJ78 5MRViENiDgjyEVP35hhz0lBn5UpLCksWL8b9gwElNsExNRJP6vykD2C1yVmk 4utzscCE3hinys6Vdsc4Dtn2iycVz+rS50JcyiKbvANT67ONiYppN3OXU3ya 9iw+rhM6WKPPiISOYdU9txGtpUTfGw2Fzhxe7dPZSyQPp1ZOQE5BF8B2dL0d iux2SG4cpsGyb+LI6xgWcZTu2QzvLnOHzMb4S0tQL20ubo3JURPMqC+VBLLx zFFlAlyYXFER8cyXQg3q3et3CydOIlpZuSByeD5px+wiroWj0oC7b4CPvZLs Gc4vSRmb4WtDSbHxUTOvK5CmNk2fXUq9uT27kOjpQerDWNC9OPGuN84/bXHK ycI5lbRwDclrJl01qpz4QTTynEu4jd02Ln0RhwTOrfNti19JQJ6RgbSzRHzI OQ0FFUwpxXcuzD2iC0FnbhQ4Cdm8icZo3E6nqCmgbPbDSCLLjtUaf/OZtVza w287eQ+PvLOA+ty0c0D6H+98cYVnNve2og9sfrf1xTr6NrD5R54wf3Vyiko4 wi/p5nZnpJ3MnMGKa1LNmLtKJKlnLJeo+8UO61vjgkEPYM62NHwRntnc2SKP iTA/4y/tllsv/vK74ebtLddDN/dp74utXzADZPBF34s41Dtb7TSpV+kRhnp3 a9jd1usO9covhrloYdz3toK/25ler9bj5v2tdXMMe3zwJXq8ZI6bDz91O7Zv bf0tt2N7e+uzF2dze6d/O3BxtuF4XH9xrjlHNzW3mO3Jfhv7/FuXkLadjzbz ulokJSFFtnVS0bbSF6oQ5MtDcKLYz8tCe+0ctLd3ndyhMobe1+j8NKQr5fB0 fTBTxILntIWM5SCG2HwMB424HcchyAkLYJIe9EKF6FhHzuqEwtSA2hS4VDpi 6dlFGGAYvaSMErka9T8G+knMwxacgclird0MfRR+dgx747q1qRyxTIeEyTEE KyVn3pFm5WQz47uvHVHOLwptwDsyBqYa1OjceJH4SbEHE/qDMR5KM8RgU++y ZWZH46dSIhj93BRLifaNWztZsRgazYLIwHa3zGbvOGmIDIN6cKlYdbjiYMHL Q5I8iYZS9sh4U3EMq69YRM19+FA3QzXlCtjAGDr598Pq7cRXT/3XXLRXptFU xo2NW7i9pdmMQ9cuZ9816IduRkBaoh8ZwuQXNw/iAbP04KF6WOB6oTfRG+eZ Fbc3GSuCDPy7LYS0erC+gaN06OVN5Djvv+q6aXhPj+ALP+Iw9EgzfvncUawu cp4AeknDHQwi45iqSQrldRXMX7wA1VcOKatgqGz66Fq0Bpxidr/yJPcReS50 eKB+wYxECarJWg0eb2YE4R73VOwS/uVrA3SzO39BBiKepRfKmm+Emc0dPIuK mGstwpV90Z+WdbSdY4E3jZrqSUyZ2txglLEW6O5Oz5FTwL0xcKI9dg6Q94kn 6CZwBkS4EHjjyFes8DZJn1tKEmlh8YcZL3rgBYLwODt65OgEYr5y/h9CHD6y Fja2qKbIi8QO6Ohy0AXzQuP8grMvdLIuUg8ufFn9H1nv5vn6Wl9trBgW+O7W GsuU8LPQN2xAGcbVoYe6vw4/MecPTXcWxIgYL49lCQ1yojmakHrfuHyBzrf0 Ms9Dm2mPl+BeD425Ai6tMcLnQ/5IR6ngC4+OW73Pre4HqyrGFZcPyqSKarmt wdmniSOs5F1Y6EXrp63H5aDl7VL4y0gqAl81GK7xYYW9F+UVgglhBR70nd1M 8r/CsKPL6a2vduWZx8Ox1nVOqXxajyTjuaRbbJCS0MFXI2x5kA+32EHEP+kf O6/qd3GhRai+4mCzCI3wV+G8RAS75WQAsl6RW0DbwBU5CfGTRQNxDJbYvSZ1 ExRLs/0GaKE5LcgCZGQ90qE/CJFhXu0wbO+sOQ3Y6hVOBMXE4njv63hv94wX KBazR7nT4ZcU7bCt4VbqcxZbWeTxzruDAxRdPLthRZ5kRH9wR7WNqiqgKVGs Wu/q40etOOaBzJNVMeX8hxjqjEuEV6tEktqs4F7AFvnRGX1ayHTLKCjrm0Su da445qXSkHpoyjnXNFbIeSCJFRruJbGmR8WvjXTAULreS10LmSDY+yKUDcfk amzCjSyEraIb5+okxqbWbIT4e9WOTgULZhrnVAfFx99GMgUkLePhijK0nJ9W Ls0LpVgORCK9mrW5pHLQLpa+6iFDMsvg5c+yEU9U2SO1y8kUs3pcLGu0dFAt ONDgbZpxdS9z3nZh4o5BIGuQ9z8lBimnMzL+k/iShGlBnLxs2HU7HcghTVfG DC3j0MhyetzydcdE85qZG4i9CfxNnTVRNjXuEERMiiSspmioUB2msULdwLFH XS5bRlVqmdZOjadMN74sSKDwaCOS4FpkILeo5ulRtEZWFOAOf2LPkj1hZMHu S39+YWUstCVQRabLkO9uO+Ev8BsVbAqgxd9vbm/9/vcYDVcv0wNe9/T3639k gjEU7prjabej6PowlQjXVJLnRqDHde18qfEoaB/wr5es07d3+9cYz7e//z0o VrBfyl7pPNrBRbbrn7/UeDRY/RPb+R0M/u7WlxgPWl5esl3o1dfZ9+u0g/O6 98Xm9W+fvc7mI+UbZqwghLXp55H1MYye9w7f+KTxsLXzKDzuZHdx0cLu3HeP +yf2Hh7mh2zHSCmBdYe5mMP8+b1d5zX6v79AWnYRtP3oWNFhfLjmhxZs/+Bz x9K3fmQIokHsK3CwZjBffF0+7T6Omzvu7KaPbfR3HUqsRiRA68d2XHbBhFrj GSJJ5HYn92cgtwyc57ZByRwwmCQ78ZY72LQmsBch1CLU0Qa84cgh+wW7Jb7R qcYk0FhUlD5PIQmKG3ESd79uXpoSKTLWEqodVEbFNRkdPENjywrzC4G24nOz WQcbEkUpH5gMQNZZd0FcLxW5BEEHVvu2q0rYhsxaEqOxnwhINm0CNAw3mdrO 0jcoHmP+tFw0BZFXY1HGscWMOHlBazRx9XTnd6INupg10bCxSZmj1DSgaI4m WLyYwuLdQZcVDywWyhaP+sPOH/iSjy5ckYOhGAm014wdi8Rtg5J2Upl8QaLT 4aDIQZeUZkkLAFLQAPE/xsOx5yS5Ez8HQkY4g4CUxKEpPiSiZTT6tGiKP99e Q7VLxKTeeB3Lqi/4Ox8xizl7gmCnvkB9gjH4HQ21tHRWZdNuTkp3HKAntx/+ UYGqrXkzZY7nwOtJRZn2kailNIksOo4luTtyYwlStRrr2QB9ZA0e3rEP3KPq cPznwC+RS9oXDNXbX3oizqDB+yMPBnL+vCn6J0aNGcyUjVkjtlvIpFr7pLxL ET0m6o4y65xXzT74tMW4jDtboYJNTyCqwUm3xI7KvKVs7a0cAg+ShofNTVLO UrDNmmGDxyDRPa1T1TMy4CM8nmCI6OCANd1la10KOXuSdOaODUvPSEzR8+pJ tZ/z0yn0DdEH3nQW8n/l/b2QNvoQs38FTqa16fgRO8yZQ1KEvNRwkrxxhSVw KLQ6khUSfbCxndAS2OvG4KAOeRDLcc1zipRReFVParDJMCZK/lI18jJjh5w7 EWnTnaI192R0rcIMNZiHuMYiYS6kMEggjRgj20QVseb9iUdJsq8sglaa8aGx STzISfrBZeRyOTMnX2SypevxjR8ufuH+FscJ+EDetZfimhBGZcP0viOHCOfW AdDmMyOR7Xff8bBjCQFsGLWNVER7yUMXxtaNpnWZUl0MqBSUDgVPs6JKKstT Xy06DG6NR7Py+glruWrCkZ4sFSCS3+o5059h/tsWOR80qHCfOjC6s6OWQboZ Z09VjB6nDPoSJrssHbgtBUva4RKND86VlLFa0IkyVVA+TWliiNsG8tc0lxyW 35CSTp/0oe0rfeD6cLuUQ1So1eDaYe0qoKTlICGvtyFmCqanaEyyjQ5Qj+Ph FBeXSoVujNxfJln6rsQkOk6coWdN0KA8CN2TGC5DtDcnFpuKQdTJVSFqCUro mXYbwzdTHSQlR2AUwdsc60nRfCpt/XB4+NpFRPfB/aMkNjp0SXDVYM5NFNl5 VjDLNz5vlT/wlh9wy9Jbf+g0O11UEvYlJUuZOHz0tyxlwoNwbysr0yD8uKEF Xf/8FekTS+hbvubxNOFrKCrkdUxjJpcDmQ7QgKSCdNSyAaTnpNlW/0Dm5yXZ ipTRli5Xc/QIycJIQMLfhYmBkKdPgOK/DFQYh+J3fmNQ/O0tcgZ+XDSLWXbB U3+E3KjPcvLFoPgvAFmjHeFzTTmvMNwQWd5v0MTweaYBb2KgD7pu/BHMGv2j e89Fu50vZmLQ6ADkmlQP4HvJBLb5R2D/OCJ7Log8v6rJ7Lrzuv8lTSe/oXk9 +ALzeiQeLF/xfH2r4R0Rev5uDT13TEufNJ6YSXqITkfrzDQRPt8xLf3trTa3 f0NWmzvXsdp8thGsvS5f0mpzt2W1cTrNtcw2X9O4MhVpQMpF4dhilhD8Er/b 8iagL2yUcN1zGj0XIG71k6hBwQwNm/ob2RIY3IOr7W9gVIDuB75/ZzVaY1q4 BHza4eyWKy4y151dvyXBbJxRd8MttICl27yoNWHHGEq40pZBvovaaURWW6cO RfsGGhRImAyfuUN1NN2JzUNwVmSWNtTV/UbjSuGK97IMsPWp88HvtIBmv3x2 rM53PXomCIC0z7o6ocetrbrV0WXjSIjLhaEx7ZkpiSdkPstW5URjZ4ytRrN0 4To6G4pXfD/djqIRK21AJNgJNt6EyT1pCSzIReF2U6Y9LQKZOUdJk/LFe3re /9J2nAefY8cxTLlyeIcHUFu4p8/9RvDoizwrCTuJ7/0VYGbiBpSeQ7DmkO8F sUR9gS7tS8DHzCkfkwvLZDMyTIwcQMkcgZlSOWRM0+MgXCoYcKsNXBIk64t8 2YaEfS4roiHgje5MUqJuvoL6cA/4+Opsn+kOSU7yL1EFeHdGTS6sCtNix1MJ uqy1Jn+53FkchSD53ns3EXN75+gaHV5xdX6S1UTE6NBN2cb7LIDNKcWsIvam +Uxdehg8VfGrpM4po5BuGVLS+vvNHSJXfNRNmrg8vhyamqRGnOYiiQRcSOow SU1DKS878Yqc8skUSp9zodZj3i8PjbeQcY6JwSSNaxD9HnHNHKGKMzHKhCLJ F5U7lPn5+gVEen6I1+H2zj+icaRHZPks48idvxfjCN/izjKyZ5P3hmk7jHmE UvyuNY20gGrJWIQCicvWjwyzU4KLZMlETpiTIvRS6wWt3YVQY3ngnMui2UTE swt/0yWmMJaSsUlaZnKzk1wSVoLriWy90YTmga9jePgtouGKHn4uGs7/fEU0 vBf0+wpo+O8E8v6SDtytdr7V3C+/Nrp6px9dvX/1df7toZBfwuFeUcjp15vX Gk/wNSjkF0P9vGf45Zjjbwlj/Lv1DP9NY4z3QoyxbCX/D25OuWK5vHgrVPJX QSJVnGCX6VzC64OUENXUq8Qc6T1QXVl9jBTBdMIJ+4tx+p62mMLZeeKZvQkl 5MwLjLdQMhhUH12R+Y7wAZoMZZcmP48BSlDOi5KFYpWGrfrIcKpPDqACNK19 90H8eMsF8YLAv7wh2aTbUbWSucbW5FIdHKZh/d8o8HdiIh5LrgaPCWXDZDzq CSd5mK8P+XKEf0zHlhTGcZBLdwqzu/TixW0FJtaNNOsx3eviufe21FPb5JwU pNom6ohNMaZRI76h4i4iHCsX2e1in0nZDhDsED/+POxYnC4D/Pg2QscEIt/t uqdHIw/c8ZBKN3jOAm9so3aDADrweIgot/Mx1q8qfMXxtQdgcJ0zZR4OASPz LKuKA1PkmEq9By7AgfejTFJBQ1cWyqOf8Pvcg9T4yCejiXevgSb6Ii6fiSXe +8JY4s5vEEu8/w8EJcJCdGppOKCi8Her1hhRPEJrjeCdT5/j3HHe5CNXYy75 9VgkrDV8d4poJDzNif2a/wYg/5YAZI+P+VfBH9XJ/L+9s/8RvbMJS0T80Scp R1LAeru1pHyhDIxWswiKW8yKd1LzrZPK6cMHjbQx/SDOeSD20SHFoPQCnWVF 0sBaqBMTHfJNTpnkmj6mjGks0UqI+9SpeDpItPQDnwgtVFuKxGNysyO7rjFH 1DxvJeIEPjEpGsrM4XKt1MKZU5dWXq/vXpttqMbQED7BDzfQxK+CMXp08Wpg 4vUD3vsUcvahisAZ19a97VN9UASltr4Eirg+AmGf6pvnHe55PfDwpeZ8bSqJ Agz3W05MTXBuA+04AixQYighe4UJUkpJ9JvDGdYqupfcd62o1Kkkw6yOe7Na zrN3bQuIpm5qaTD5tKPDBJpi9Ip16Z/wwever333JLblpaTr3r5GPJU0wrML TYvlyl1imXOpeDGQ5HKOfwZJvfodnT7n0v67MRrqtai36T7L5xLi84QLrSmL O6RhB6nM6OlrhVZJEoWmk6dt6Yo8Z/6I85FSNSahdI+0pJxQWr1y+nNs8anj 9RZ5+4DWh5rCq5dhphwLaqyQlpLORnG9uZ5eUI3HGic8bNVugvdBCaQMi4rv Sf264KEbDc5rlXtHKBNWHSs++MkBNRGGfR3Tob0srnPJR65FbudaYHjn0ZgA 0Jfp5jOuxiv0vvaNYINir3fkCVf9IxQiPqn34LH1MsXBynXv5IpvL339M3uX fzfTQxSFX2eUaXzruq9/Yu+48nfXrvzX7B1Xno2/T0hND+W5z1z5S6nuM2ke l+4+n3fKICs3RJ8Y/IV7x6V7YHqf9nf/5c77Z3LaqGj8IBCNGV6qNHFrHdzI 9sr4QpKvFVffrBUCu1aUrAyw8r5swKuG/ab1Aub+OumSPQKpHvdZ9+pjZ+K/ L5kNXZ+Rsy2Ys6mA3iOw5B25yAxUTTwIuV9tuDEVJHiIM2WgROL1gf3L0WnF FAheZHw8biBVf6nYVoa5nXe2XOQEp6SObWU0WXVvQME1KEIVB04T7CFpetls 9Lv8YiAaYW4mxiIe2jEkfyzSASx+VswaD7PutffLveaxXs04Tzol2gkRzxc8 fordNxqKL+t23yW2IfHTp/pYfzCHKGDOcpf/pnX6xFKJCa8xUbqxt3VozFnB tYq6+hy391z0SKfhDcQaGCcwKimJWD464CNSrwMgUbkRphEQkNNjuHwmrOKB 6JXPDA79CjGHVpYIo8U0k7zM6qK6BF7z+aT5oCla0JOJGpMFgBqeTePNEg6i fJvqn5IhRWZ3TS1ZqrQ6r8ykC1q0asO2Jt7QocdihHUusf+c5Kdk/WjcLAlZ xLISUtbEWaOBxlHd/rsI+f9UZ652COdv1lnyN5Y6IH3qa7BcksP3t5XF987X DbH/Yvt+nXa+bHbir57F9x5l7WbHmcvy9/4KWXzv/6pZfB987Sy+X9Kb8OF6 jcbdzSy1zPKs6as7nWE4AduNA7j5mspP37UZ0YG+XDiykRnbOVzfuFJUOPG2 72QsQnlNSK4va9Wkb3Cx1xW16tY2yzQg1gpRJl72kyM1737pSMl7nxMpqWqb G8eavHzsnRd6y/WrOFdOx2fcmrxaxK6Xl2bYM7T64PNdJ5xN6Is6QGBbe+JO RGXawzRS3lyjXgFAcRuz6uSEKG8jbFdUBVnjiGHsuMDgX3KmA7W6ZhHUJR11 MeA9Xjko/sLMlnUx4c9i3MeJ3ySO85DmWLGI5H9OO3ne58Lp1njgNEVVDcVh JdZlqDWSMvOorkBLpZtszx/FloPDhB5aq8gEoVyhFZXE/OV5ZeO48gpzwyU/ wJ9xjSWbYbq7C/JhbqiejO0lKZoBeXRgxJaJOseknlgYNZyJteQk2sRAiguq MtwawMB7JmNR+shqJlw/LSvFTxMIhqMgaTMuYHPmA+VX6nqJhEpZBNAZdrGo 6uWqLJYXCdXWwatKXFTspkkxx7LXt0UscYlhxOIqp1uUnpMHGxoyLwaSmE2n ea5Mz6wt9XbCyyHOKMMJpxJs1+6RLaakhpMVaNRzaEE5hVtbVGa1AWrXG+SW lCcB/mCvs1I+YIeXSJH5UVteuPKPU/NY/vvEVoyYzvLf7zqSIZeAeaZFduHx K6gfnzGeeDvrZK7Id+12UKnaYfm9Xy2OqsHt8cD8nz2GX9aoxVdQP7qPfKl2 1DyGUvYovao6/fXGowYztNeMIraaLzKeXvXs2vPqUTu/4vqsa6c3s9snzSsS e/g3nFc0s1ucfth29ZQqGQQZ63pjD7/u+fIZ/pCi//bniyP9EL4dXTG2l0p7 IWOPPIvw79XHs8/e1J89L7yG4s9erx0Z/ae2I/iF++Ka947CH1Fdf/tWoOx7 ObTj1Ec+WB1BFKNdyNtXBE/U7F/XlJyInIh3w7RBRRPoo335ZwctK1vipFbU lTAqwekQGAbgMxsH49Nk8qgsyDMmoVBCApxpSKIQEFUvi/9YuZRVlBIBU+7X 3XI5baOVDpvbj6emRksLJ4h2g2E9CN2WeUmc5IbFCqdnGYW3KFKfzdCr0O+H FWWx6i4IiKhXs9AMa8CYv90Cpxj1+8L7NE1BOq8sDTNls5rn13AZahGgO61A yeI9y+egFmEsS01QkhdJy9V8zCUcKcRNu9PAgFOQqvOy0arCY1wrE8rB7nO+ p+pMskYsTnEZxvnyHHVrSWzRqmuuQZJF6HK9LjGzh5vcknYynnVXJJoog+sq jy+8Ga29nsGCrEnX3IQ1l50LYVB0eY3l/fqgm1gdrdVTbHqskd0IzpYobW/i anpvjOwR/Pa2mDZHKbQymw6cGdUSWbwnQdGMao4tdOJrwxBMb0JvzwxdT61G SKU7tXb9wGT9tufMhyX7rIJjfqwX+dJUZzoAskuqYdZZhhcrkDo6+SOlRrwM a201K2yAoCDiOhZpW1YuvLXHdUD1WduziUqUSsY85KlHI4HNNbn1YzC71qnH QTieEEsrFjm8cAIv6A76uxSkKIPjRVEdLjSylZWGojwohCObIU7JmWG0dMWU gg+bysFyzovEQX9Ky4y2xcOKpQLNEW/TEdCHy5xoNyIStBLgi4QJeodxLN5x 5b246/YiFtd6yg4T8+CSdg7yhLhYzkVoV+WrwPvy74gP8kuX1YD3hECu8joa eJjvSF/8hamhzSEbAVG41NM9CwTBbs4XwjXDTD6GdegytlI/ekZ9YI82p2RD Aj3PDNtx+Qq1FXqEeZaFLBsqrt3Gn0xxJsy25LMihVkHfPqh+yNzOZOy0USe 77AUimas3wWhuHhjvtXIxbfe0wXaRhYhDb+JMhnyV28l88SXbMmpy+IHhF1P GJjjOXF+AEp2ilmkpqnPyQQLXoSxxG59myV5nGixHHsiqM9w2P2CJx2nfr8W 3MYyP6mWZBkq8/dL6DlfUIV5TczAAZKxi7a/lE5reD0B1MHRv6SEj49oNAzL Xc6xq/ia8ZJ9ue8yrBjPKYVh50gOPS9gf1ewQ3oCaQydO7rgeDytpo0L4KjY FaCMFtvohe9t8Xr08wcWQxgssZFWcr3bW5f5DFXl8Uw929xdZZNX/Irhk9ZN SizKH/TGBy3ssBIhJQuPSif4mk4M7BnVc3n96uBQ76k3Px68egk0sf/00YOd uw+3XLrbRGiCqRHeX8AlsPQOREwXrW8JwHb1bljFQpck5aGNFC+h6y4cYyN1 sGqKPOmI2D4NCnesw+QucRJpxXcHK00kDRBz9sojlQxylJI1lEuGJ5T055hL n/imUEzIm0ldjPk6YDMQ4/tqORrncMfD3h2xmP2WrOFH6SYPL70JW19ndA3y J83WbgL6uTQrfA8tWLwiaKHOSa1ZV1yrFasySvef/OHnZ/tPHiPLCsz5recO 8jz98CEIOiPKOxLe4AYeGWXgBTDWgFqbkiKiw5jBcKxtUImNzZzkxaYGEnHZ VREBCaBnchFu156gPMJT5NHZrUFjY3kSmWo3pojrObngPj+zdiYZfP1dftG/ KORFibFwsB6o6lKGI9MgAwflRWC7ttX1jMXfPUsZ6NHtgKo5xfYp4ttMjIiZ pmdafrnbi8kt8Fpifz0r+cyd/hZ045AROj9zEAkU0DHiFNebHaR5QViHIxDJ wz020Z5WxbK92JQOaBWTzDyZ3pSj9NXrw2evXu49b8/QRd4daSfrzoOEmvYm DFqRrVLuCNQEVAbkuPNOSiu21vOects9GTFTsnxy6WP2621Yg2t5xqgkGZ6g 1kMyTMwUEi6GPtdOIDDPEdppnAKgZCu0IF6s0xykH7b6gzyVlw1diD6C7g2F C7LvlDpqvfbVJffzkwJo6gKuqmd7L/eGdPFYl4s91LSGJRM6rIPGOVIoc6hN UeorWP5dtov+tYHj9IEWe8Py7I3dlD8138Bnb9xn+PMh+IueXF4scnhuY3Fa Lathtig2Bt2H5HB12nMPIPoWeZG+OwcxIe/7clrNFqdFudH59i+RYcwq1tPW DOR0uVw0uzdvSuy0VqQr8+XNviHoK2reHmE3s5skJV5tXEDDGa7jmnEBYWT4 WN8gijlG2ka6Cz75GL6tqzd0rSfhe/L8Bp9AQyIbIg6HVFMC/SItvLhQ+6+W 5XqJ3/jON0D0wwd16ewyS19Ja8QbcKuEvcHtUR27VooT2/5fz98FD+P7S3x/ Y/9gL1jDDRrx3h/2vgs/fldM8Yv3F/853A6/yWYn3NDO3XvhN3iINt69+u5u vX/nx7Nb37/In4/gx6/qx8T+q6urrCacHom6SBAbWgl4w9DOBmtXrUkyoZxW NHT3WmvTW2vP6x1QOgspN7d3bt+5e7f9OkE82MDzn54fPtu5+/inBztP/3Tn 8M4fnv7bo/ZUdYoiibRmSFDoW76uifY3CmBH8PHGIN2oFhkwsGDOzq8qfGcq HExoNvlIhqEkORBPPls+Niblc/Hdpss5WSp7K75A0NRbyb6lOqh8o8nsTDc2 dWFOd7m9eKqWMYoUpDLHtrAAxua8OhORkQfAE5Het7AsB15lItvKlXMiWXGL +Rw2nir2dhpysIi0BDeJRWZf/Ayq0jhnBCprqRoO2AC5LPe6EepYCelY2gpd 6I/4qeEhsLX0SNIh4FRv4gV0NEr3SEykM4wj9EU8Xuz9OeHrk+T3GaxayZec 9oyskrIoUAqurAmGVZDcgEVIqCA1fmUmMUqfUuoOonXWHrPlkjGZH/940Dem zYZkA310+Nfz5uPHrVSydbX6wNgWtbNdoC8m38rY/HmNlp9ao4wINUvJsqtL TpKVICYyJQohiqjG0ImGBhs9WbSaJBGXzPVKCZnVapC36jCKyglfyWJVL7CO daX0JorV3utnce2biEjhfXgw1AwTUi3FMsZqplId+rcxpW2SzJi+4XiwTsCd najGjG2hiExVYEXdXFK0kCid3OKb+Wq2LBatFptOk/rY1tYgyVo6MM74uFJx 1uUy7UR5ZYiy4uBbuSpig2dow+k/aWTalwAdLe1b6BAF4IrcVI9b46aFb7za DnJ+W0+/yTrNGn39inqvSvHtIFJJ30mKmInE7apfTOIaHMmds5oyy0CyhbEb 9WtPTd0oi6QTLMHu6i9F9Yhjr5tBV7jzPimjoAbIIjkZhgj9gr4KRsIXVcv0 bcyv5ZQB+zGK6bwhWMVXSt7K2DwWyL7UejrUXiMHauqhghArDk4dGRdw/rRA zoAocaERg45Nv2OVJd6chkzNzMXiZ6gvK6k/SnyLq+bpIVTcxuNZdhKQoCW9 PU0rQ08pxM6JQfFocuaSJbwxXuElXrEf6FnBOQbHhsHLDrVzoXjd06jGfDFy XKeeHx0o77xR8bqWILrQMRaRjlwDutfRxjiHD+uNI0IJdI+hRbu9g8gIW7ZC ggC5LSFQGn27xWpeLJfRBqnsM2bekfXAOw83WhGG6JEuQwlnsxLsAl6+0cD9 0SxJJ0fpSQKItwLTdjAC5fg+athrxkS3OCSBA/UqRqmWZ/qCTdTEWIyjDM8J 35LFCe8zgqCVk2v6qA8f2mHXwFiE8TiAmpvjr4HxMKDhAAFNMGlhcQkLWPG1 afcKee5T3CGhLFqJl68OOQ2fHHG6jdHNJa3IXtcKrjDZCI5dU6k7l5hDqAn5 gs/FeVSUZLB5i28eSSpOpWRaEMcT6Ls2+sGH8FogR3ABPqX32/AG8wpqG0XS Z+1rNop1xK/E8O7xvh+ZwEHvfQoxf6+PsVLkIitqL+W0cJ2RAU/isEkMMmmp ZpdBJWthkj6IpBce2ZjmiH6FkEALfbgEEbkmGnINJKQ9jvUIyDr0I4p8eNTD IB49u3GezepVI0zgWjtyXFWxAY2zSyZ7xUV3q0jrd/OzFrBv8RbFBJM5tOdN 3/HCoKrSvMvr/hVOzHg2SOLAZaXTsT3cub2h+vgzd7bwChNNdLBG8sLnOLma ypD+yLrF8QlJU71h3R1o6kT6nAIB+4jfiF3zGF5IeOehLTd62bGUyLljoDla Bowm88tgnvCGHuCCK9qBjrHNcOJAV/jY1TVeKOu3rLajEjpZLFQ34jpRy1ol Nj/WS3Rcg5gp0eskbYVCtVsjSedt5XChELjYIUUfpEsMLdWY6TGMGEwZCeJL WUaYxERTAgxERmPTzxt7UcSUrj5dc2RuRAyOys1QRdbmyXeEctVYxI8GXSIw zCkQM9H8R+qZE5NEo0FcJZT+VTTobILJuCt6uOual59TAF9gxdJazY8JDXqg vikt2deOnOGqahkZGbeRxKWPDZU+ZPwbIoBsdsUOhaYuEQLI/6gxCB9xivMq 8XF9lqwH6REfyCMSFPmPnaN1tzszU4NatjicRZ3/22ry31YT/3wvzex8Hs2s E1ikyUu2Ky640Fcd4YWm9XlUsVaQ6Wv/Cru7bmfXCDb0/VrhhsYUkoDfYmuD QY0Fx+dFD7VB/CVhoWcPUzKJrNNSLVgntVcsMuFegKUHtfEQixEmSAdLLuHi TQtL6uDMsUxVH9ou7VdFmnvdZxxMjxkciqUKEKn3yZE7p2WPEAxZRYS9Pyfk /9vBaD3WGdqbegEnI7o4HxvjnSsfSSu03R6c8cU2Sd4wGvKHD/tPHz288/A2 SnD4ksXZuv0ocUjDBNW2rV9XmYHxmNLXdeij9LWW3RIqsZVRjtSsdqT1Al4t 8vLZY7TslEQVj0Wnh9v71bPHj9AgQpdqk81nO/JWerD34nm6YzqHp/GzHbzi 070QRukMUVAbA7Q5VME9+lQebYMKrrGhNBbBN02ihs5yu0CNDjR+BTJpukFc hnDU/NOuF9ItUhaIwYT8RUgyIDS+egyxpciC7MjkhPgJWmFVAtCpFQfHSZ8k bga4Ioh4Bz+8+vn5Y1zJ1Vw8/8mPtT8shtfauGZJdXsXJcFNupNVkPNoza0F NlSCBznlOC41puXgWjs+h0/gHWfQXYtpMTO0pKaIOZFajA2qz85TfrdNezJ7 67HjBczQFh6xgqcRMzjfO3ELeOpN4PACHT+8iETtPvTeZYFrmI1oWgrcit9y PCBSqVvFpOvgLwk03vREaXSy+gwSrWZCtZjRGhdkSVEgOI4/t4OckBJlUI2f 1RTd1QtUD1ArUxVk788YDEYqiJ9110M7dsGqxzhaAS1vOOieQRJVDLftwdFJ QObMhegDp6dNrkJrYX9vvI81p+WNpcuQmLXjCtFUXeazpqdnvo6MC7YFGKyf KIgAmoVCOZf48mguBiMDiE9kklAapEb8LTBDZ+hJ4Wxj60zGuhiwG/nsmH0d NfUo7pB7K9g7YmXq28qSQrsIYUnbgSFgmvE+cFXAtkWRJbtDB4gZFzSvIWY6 RYbqvfUrSjuT8GR9JTryJ5mqHdC5kagXBxD/WxTuMJJHPDEaG1STtOpeupnH naK5d6x5nmvpOJ1nEMkVyJMaZERsrhXwtSbX0x7lbEGi4TQ/g9j6C/JGXXBQ LE2VeEqsKxTOHkU2t+EmYGZSiqAxPgJo57tIXa08Fg9ZClJ3De/KyXTGqAKR ate+1ek30X6jc2zRGBmAGg7GYCk1kXG6bYpJpEBRPW7EyLUXqzHwSyLKKi5i M0oXpEz1UVB0gbZIGdoScejjR9obs4JkJeET0PeqexiPgbPUk3M5UCZcYy1j fBDWLpvTdnkWX3A9/s4cK3PVujxkv6mLxjmgR+OPxWWmcbZHgQcra1Onq361 MJHzVjI4EtfG0Pd5zxGeaBmEGnohIrwc3QzZYAlXkIYP+XBNiYozF+iglaHA TcLnK7bO25uewqV1IHAraLS8Nj/Xg7Lfh7LXi3KdH+U6T8q4L2X253tvny3f 1rdf7Z9Pjx9Mirc/Lo+P/3SRHbx/EHGz9M6rTJuEneTjIYNUQ/RulE5/JW9W 55l4DeGzfff2CJzcjeN05CI+Zp8y31cGgnvD9gq4b2Dzj4uZCGPLeoW2AHV4 gw/HlfAtfx5Iu/Mn3QwdL+zhNIfvaoJnB5dKdM6F0qVMy9/n9aSgIkkrc7kX 4jkJDS4lyHbpakzNme2fohcnht5S0coGs0FXsxVe0jUcKO6qPfB2vukMmH1d 5Byye55d0JhO89lCeRVV2YM5Nc54YdJoqMgGDfUHWpKvkOSPw+Tb8Fa9qAil zsuzoq5KPOINZ1tzZiofwzXLz1DAw955uyjzH2VoA+LRvJWc8Z1cF5zAHfjb ZcW8M7ls+ldsUUsHiqigVf8kLtoNhJaSUaUWl8ai3hSorMgCR3ofc2qWTH15 BG+gvH8roEFlhhnSDdwyRNyy2+JBUoJ8dRaNjHRJFpkiMJqRkiZoKUNPIobh w+pzOhGM020CsRTeazRgUJ16JG4HZLIp5SJ39qLTrJ5OKrQvsowiWfNI5KEi E5th6jxegmW1gAP23oXPe9qE34q5DxfbeFpV32X14b+6lPd3NrY0mj9GY1Tc tVryYvni6LLNF7l4jAXubL1nI8fHMnOIkVImQLVTGWGWjusqm+a11VmmF8A5 YclWVOsMfXQpdp6XG3TKjBO7GjjwLCtmtFhA3jlHNLaWDfqU5LZegOJTO0Ed ktyu8i3nKsPJWIkbCBE6HoLcTmOWZQV57mqUK8TeKCFYEd8ZlQT7jVfkoO16 DJQRCqsO+j3PxZomPJMdkAzfFrVNsuF0uMqc00g6jci4LgXfkXp32Kd+ca1P PLe56wothJ6Ro2godHBEksORvzCSmGKCL7QNlj+FDtbkyZX03n749Gt9Wv2+ 2ncfCqbU5FDa25K4QGirwILOynW0u66pvaXhOUib0C8jhndUkqq0MbYhvB/4 YCVLVArFvuuBMNLiiaRdUgjyW21nVEawix2xmwRmolK1pp0Ik5cyz9TSsd71 3s8LE4uoiRiTUvR4PZiZZ6c5O7JziTqRbpFPTE4r9A+nPBCVy6tN/m8lJ7yA 90fpo2o+r6RCDbpjOrR5N0mGiFH6AEGruDMAiN+YKvSO1DO+CYcI8hY1o0MU PDiDNp8DI22lar1hIRrvHEZ4DDIStB7svX7GN5OFZ4fp47y8aA8Ql7zGOAvS RJFPiHP8NVjFmiOJfoFc5TNtLuZAvbVshiM/xT9Ij4wppgz7SK4XuZzYCTnR E2qCkKkaCAHawDhmF3yvwqshVyiEQ3WdHoNRwjkLeJH7EnXHQyp72XohDg5R lpFc3Eh5poHiv9lRTSkWwL3Cm+SaVbyz3UYcLIjsjXgDyRXp5RXKHm0ylIRH RvNCC5NMVL6Qkpkip/msaVygShIpLJg0XSRPtpRBjZzbb1tuSpyXKN+7cmXy u4iiTGBbOvhZK5i1FflA3I811URzkxnRAQjc6Qq8la3FsT6vS5SmF+hFNaUd oBxneN9IKR1JeewKUltbkU6GWLGTHHXsqgdofjxiE+FIOv4ymN6vnprAcrFq iGcu3MXtTGU3mvbsuI1R0rq8W6cEXshYfPq8e3yvN0h/ki2IeJDwstk7IRpn Vd47gKHL9PAI2iQRSNekewCDTjhvBUzyjO42llfoGi3eD1cLdqt/10TwUjfs yWryrqo+foSbYEYZ8ogUvZaZWB0MxcmmWWkKwFYCpb0DMSgyYViT9eWANZz1 fXfWP3zTOeq9JmzNzej2yAD+cRjLQbdJq0SXvU4uZXSEGksCxtDQl6kpzDMv dxVAeytn6dcjrf7LyMli80BwCkm8QXxctqGbWd2dw8SnTleIX1wZ7eUmKsAQ 9nkKOy8SsXRVjZGZidYtmdCPs+Y04CsZ4eJwMVim5qQLt/SjKN4lvw3v3tke ZuMNBl1spQZf9DeMWozvdSjI5aUQqQxCwyeoagIuor1/QUa1siVWi46KypFe 49IacpmTUnMO9Q62HdFZ53+lnH2JTvMaEoocstekZOMRExiMuEz7qMV9RRSf XH/QetDUqgueJsr1w/LnQTGQgpxC9ERlMcNR4oC/tBuW2E61w40wyJUHJsSE +aTNxurx3WCIZ4ggseWEqikcIcYYYuaKMVL8Wgj7e5Bl/8mjVy9ePHn5mNF3 6Cls5Oer5kPRJk1aU9BHx+kiO8llNTDBkQnRdNgaFr4McPNZdVK9DYZipkOe dhxx55YqNrPLu0RGhl0pO6EillMvE48vtPxBig5iu9QaOUTs3H54Hy4jayTD A08j45jpi0UezMnzljZCfDV0+ArIsPrNy+Lh0zRsGtbNRXnyPzAp5r07gyf5 +floNPr9RgRF1gMSQZMDr5n2adUhXw1V1mOsgrGXk1ac665xnkRd40aYU+zQ u6bhYBnscXQKM1Jtl3UzFItVJUow32hGlR5N6mXvCxJXZb08gaXWOXLg0HsI uMorupIyOEwdqhBgG3Yk3conTEx4pYuaK2KKhb2VO6gN7UTyqckIrJQa8K1+ sVANXiwA+ONYlImBqlsiGm/xaYUq8RDfcREGtrbLpZ4AqILZFJue1YcAksuC 2QmXbV+LDmJ1klCcG6qq4ep5Gb+rzEYSRlRZDWFMKBPQ8TEqYczEw3ShcdOr YsmGjtwknEqX9GVdtrk2NYYUS7k6TjxT/IItCupF66Rmg2TABNWlrF3iJSis 2Up/gGcr6aVv3gaFRRyU04jdYZwz+OL2K4gfwY/krkkIO/dZqxzgYLO6ZnJi ZGzDsvLpqA49Fbmc4LKzFF2rhISHdVlXQDQXZiNU80HRkvIXnBkAbj3sRgPk 6A6UUvl2QlqBiZuswdA1lxxScbCr+TsNQZ5YVsllFMbJZLmK7bHHU5skX5zm cyxcxS2LswnZb3yW7LwuclvdrqHaZ0RasiVErpShl/wy2puPOiPq6G6paDEM pKdGpQWaFREhp71ISH90I+zyTKVuPtzDBaUG9Rhlw+Bl2/hPnc9ZlpoWIIeu oHE0LQxnxRmpEtqB0yDm1RiNJGHbVJoJq36JUoZBn4SvGF2HI/F1xRuJbkmE y1BudkfeGGjOCvYJ8oNOValAe8GsqsGtQydcfXxQbceyeYXcifMM43acaSSS QzKJbEknvQnlRUbYjyxCmcLCTXbhnDGIDaCiX1DmaAtqdMiCk0+zcmEuFcec JHwoQ8qdtXGWCBGJVa/iAGgnJs8uvNc8RueWnIk0outTQaUPgXtgv5rhj2kb XzAlFngTTWaUxHrPUsZTdVzscWfrVTskLzIbE/HVDezTaB/xxlDETTs+mCrx Jm1XqM1uWr8AHv0C3s22prwvjXCJx7tVFvwaxoZgR2D9bYy7duPiColBm6dw Xd2TnKqDnYBcLgLnO+78yvBj0vXESQn5J6jH/+num+A98cxpeiLnjTtla9pe n6B9DzyA2ZVXtAseMSoD4v+rqcLIi+XHne8ffP/g1Z29f0PHko9t3+CelryT MH9Dk8cv8ou/ivvMR3Ib1vRZPUEJaEpvjPxWeMdi9TuU5Os2u0Egslc1lRpF dRi9H8ntQbiG4SqJJj1nfbEn2wxB5ixZZGHOTYRJr+5jrLrM2Oe0tlUbjc1d yiECWfBlI49r2o8rJ4ufsEnMvC55tyUMg5OBuvgBLGFA0T1tckyzkwxnoeaw fOqcXUmgDNvJVtMi18ouRdOs8rrb4jxbsE+OlHpgdYjv5rA5EnHO4VYWQQK3 37fDvryj9IfqPD9DFlHaPOlzyd2qThhY6MVHwcry8JpweMYse48O2MElh7mo DgwFuFo6ywt1DKnTzWfT11tyEfKkhNw8fXDoRTclCUhcPhEY2epp0axPRBg2 bsEM+prNbrxsAW5cEL0mPZtAixVsmTrD9OddUhuefQvpNGgYKwDMQayo0U2e l09cichthUBRjG4HUQDWihPs+B3FyIspJ01CD6JkXFVLFHEW8B56fgcVhYwH jTmVcjsbBchdvw7o5GKmoh20WMDegQcAA5UHacVXWvJeIDAN1MZQ6XCpaDNT GipplYYKrUAMnga4qoNRRZZ5yxmBGUTtQ1E9nEvHtCfXsscSiWIKtgR6OoUO WHyK3MsGPy81L1VQe6dFuJ2qOl0lRKFvyso3gcYGvvYtuouxPEmSdfOuWPRB PoMU7UhJEZfL5Jw2QT66QJelhMAuVEONP61MPX6VJE1PC16xZ48Kg4iOQ5oc Ez8T1TTxOR/t2q+pBR01RJFw2mN9aollQaCOdYZ28VHtVNJRbdU4dCeqWHgb 2xUTofmaNXREEmc89A7763B8I4p2q+BItm8JBelYYo24m1kjl3HvZ77acuzm r5JOOrbuRnVksI0//Xy48+Lpi+0/fffspx9/Onj884M/vBCj0atSK8N4xzaq GM1GLBIV6cTx7Px4i8YmcffeIZij8IiHeNQbyxdPA2LEyldLNqTKwNTDUtha nC64NIXpiUWVxJXYikoprK/OiuPcYRkkr3jVqclbc28HZRnfQThY1IVrz/Nn zYsXvdjKFOFrB2EMurNM+Lru3Qwt/FyBSJQv3OUe0BhaOGfahLiOJhiRvKxA AjmvajSmAwX93Gq9JR9H8v61Ssy1toJ4ugvetuXDWZ/vObKoYibipahbESik FnQ6Xs1mUkIsdPLo1A8TEeIq5sdwmZ3rZGJ8JmP3Y6+RMX0WS27f0vBdYnY4 ncfL3N/WVFlAA0avHJhoBZpEMAdvFsZqK/ksP7Hqe9Q7j9zlvUeZw0PoxDDi mUQrNrxAGZhytoWM0qdRi4h5DrGUCuJZk+g1G5aZDL0LHPI6rVH3ii6RGwAc W7QgzkhTk2wC3ruPQRLmQCpzaMJpWSqujQJrM8tW5eRUxDXrj5gyH/MZ6zrX ARe6ZO/uFpDCpWB42jfC4uaVVCipymlWX4DcclYgefYcJaKb86xYmuh9Gr8Q g5X7whpr8YqYrGUQcDsWtW2WOzDIjzIoZObBw0Qr2nlHmR6/XWeLpq3x1QOO qzDbtBoCbAE5qXuQeDI78kUfGI7iTtsfd+3iQjp1rngpJl11hkAeI7uHhqyJ vXOXrIhqsQa72gQoneeYQcP7+LfRBzZpE8UuzBXkjCiYVQau/a6/lAMndIgt XQJFTlwtx/tkyeKb7jA/Jys5kdUdVie3Hp6yGoklGP2ghQ3ZHFWpDekbISYm ovgb8YYnOi1RjZvNiMBLkqDblreOKG2jnPXLLXaVc4tvQ0oSCsANIGqyObHL manzCvfMMZ4ns40EN+JhvSzL8DNJ69q0qSV0keISUMFm2bTBm90aHkN6h5xt XaVCG9x3tY615gh1PdVEr9FjzZ3kxqOwJ3DPjZDf4CESiYcjfK0KUr+TTCHp 0U5Dxt51mbpkJNg7jeMz03DqGqmcJYznjd4SsWKe+t1WWOCXiBxkq3GxrDE/ Pt4ralVzu7K+ZVcm1HWhHDehIJZzIxm1Kur2F09zeAnWCAQiu5ghpXBHzCbU OEY12tRPVTz4nNjQrcJKhnwunyf1ciUlA8YvsvrdBpusYtMpKLGmmESskMT6 IhKfUUDiKsUjXJTkV6G/RB08MpGGMXgrRjD4JX63ZSS4QEBKmCrfBGS5lqjZ osvjCMjHkQSFeTSnAREZE2tICyzWiE2trsZoANbZBayai5JmWrk3EdGdzehO TJL2iImr3EezHUpRw4iwiFo83rQJq+c5JkrkyDbjhSxjisB1P+8/Z8X+D/u0 D9cn4gFb0N7i2xt/+bqUQzKAHM+L+Hroag38mqsNFhrgGsetNejUHu1nXVzh GMGqEK/0SAMbTIQlTtvSatoipsQQUzPJy6wuqkbKsGeUqgTpwQXojn05Vsz/ M/YpvNCpVWzUYxt1qGZwrEasQyQ/NDgvZaNFuMhE4B0DvBUd54ur7rOqE+5f aEIx61QpLj1lhKKvSlVXY4g4qL8FM4zjbe4qUvEYE0QVHHkaqgCiSrCaxQQp 9T9xs3QnQ4oJoHRfiTrpyDwipKKpgDpwfjF96cfNy0fJmjjK/nKopLVRclTn HmFUiCDDCyoIwYERB7cDOswvUM5/jIbcgkHeLtQg8uO6THeG39HDvd6P3loe aSkpnCRKkj+mrdEiRtYiz6XaScFYlYRdoKYmQjaG2yWUNyxS3p3eYZRWct4U BrNGp9ZR8qznNYr0D7UTzXQrMBQlUmeRXmvc2MwopAlhgwkpV+ziXGrU+UBy ukS1y9wRmKihR9jEERZWkF84Z0p8ykGykr7pqTHfuBZQ5g6pReQFb6Nqa5pk GZqsicsZf2i2RbwZMGJS8hSS8MerNUTXYzpt/C7/TeOiZjr1JXhUTeue69lw Kj/h7szQVfyZobgeeddDRyFCFBHL1d0iVM4iWoaO5uNHHFu2WHzasBhaauFK Wn/B10SXfDZ0n11ldNAYD8wLF580PJ+iCzlziAJj6uKai79jBx3byzFXiHF2 VGbq5AIfGbGKq61hk0v533zo+PTA5QW4bAowZJyFcW9vM6ForLg91p6zd53a bW13anhIDUuYCyZAVVon8t4LtM7I3eAo+YrXg2CkgroFh4m6kMklxmzioq96 RNbOpeFr8h7p8I5Chh2/NoiFMqgLrRADT3ovX5K92HlVYjbQ+rYim1xgUUpa fi8oOYroqdCkqRdGRbt11IPEgMdOT++c71Qh3oULUgKyQxGH7C0c4pGXQF10 M7FDeME+4iQdcBnvKhDOzyh/WlOBGOecf/xE2Y0UTYHsO29Dj/ySJcGZImNz yXGO84U4shF+SfCa5K4ixyDOZIiuZpUkzcCnTwuXtapVwxAP1Ro5NwoABLJl EULojH6a+rjeVyDigJU40DCwdzZWt7Wtu6BBI/NFroY41MrZsJrImImYIiZU e+Rt623/AVBSStC3OJOiuBCQK0JvEK9RpYOXkyA5Y7oE8ZukrUa5DCbTJfbi r62hc8Lo4TR4K/UyGQrqpkYZHmtHU7RvyKTnBF2TwVBtx6Pk03hLVAT2egY3 aUaNqRpwiiITymEUQ7ZlO0nMkH2l04GSyK9yMGg/4ofCbBjJVFpGcjN2WkhU 2Yr7DstJST7tpFDLSq+PHWx2gLc5G2Uf4VpECNUJI1e+Eh1CBGvpasPZDKfo OaGCBAsjaNkgF3UjgaAB9HICTkICdsLSVa9IQk6YCqSsnwyF/FclbpkuFIoY VRUdWQMGOywTl9MgtmmonJVoQc4wsgtXiA8Na7hGJhN5KpGryxqAmyq4q1bN im4q8/5Uj8w4c3Vv0N9W0ZdpNVnNfcBN7WL3EaaSa5PTOh2zb0by935FBmwg Bip+zVvSQdFBlZokdACKCPtrz31nvMmVzr1p/dLDj8TTc1tZcf5X4wOUbqyl d4SPhaclKt1ejVtobOXncgx83KtGzyXBhcubxXvfOl7P/1GOF+mnv/oRK0OL uJghrnzsSEH9miePOxCXUjPQp2wr0ERokUMnZuQrnjc2FLC2pEWnrdeiN4Qk DiuAO4IdVxhsJXi4CBCV6yKbIYQ1z+djcok7NsmezcFS+z2hnMkRr2uIcNDG eCcaWnhriyHtVfK1WPy74yuKVGuzHHfyLFgsJfdXvu1HkFGXjop8izh+6HjZ LQvP+b5EC7Zl1W1qBE58IPjtwrj0adANtY9+h5Umo6+0Hipl5ezPydqffYHa hO8GYWiPgJmSqxgNPdnJnFx8kIWUuUtS1SVGtizBS/QyRQK1nRqWhZPtSL9K Rb8Kzha+7YvSaf5GTm4ki+TIQdj/rCjf6T5IDOQJZ0nDUfDZ9nm44KXGXXVi P2t0GzR1gPV05fVXN/nI3G807bh46xMYELCiqj48yb/ZyTbS8f6As5oLNUhl DFZ/PSJO/NTARJTlF61cR4rOIOmTraqVZISXdu/g0bNnGjfHAXXttOSS0Dub YViXjajbgOGdbqTQTH3hYfXUZlKx68C2szkautGzzgXswxUId9G0mmvP5ckK 2ZmQOhIxJavC4BNsQalbQ4F7HeOtncQXznMlwN3RtEwCp/Q2xpbCbOhkfMdn g3XxkUZmDdUt0S0Fvda5PfDTjx9jsYkEkiL4SblJpkGSnh+wrb3ZCYbknc4t WvrD3sEPw73n32+5AtMZpZRm/g7NZ6vZUrNPNSDynGbDnbv3jlpVtK9ouhB/ QZe+QlfQUcWAw51ZD3HehZEkJ2tuzHVYMF8sLodoy2ZyDeTceyR5Vx+9VDuA S89NYFMjBH6iUeS849zEVgAyVX/SyCP3jxUMvuygcZg4YJRZup4RZNb6ZPGP rmAt/5KlxMVivo+y+1uRMBkvQMORDDMHOy8dKrEUc+pgsnP3EY2bBkFgM2Vf MJuBHWiUIIGOJXtTJ+N8eZ6LVV2dMkPoyN//wcjY3YIgCOpb1XuDWyJ7bvkv ng7CyOYul+Epu9wQEV5tiryTA2LeEX6TsGH1gBwlV1pOdfTvJAYpWytjQ5Gk +kihJY2CKjUi/gjaoufEChq+MZ9XTar3BUEukQL34QXTXQlXa4WOlWVMqmpE oNP4RMkZQ4YlwE5EDXBgs+xd73p7u1jIHB7pZh8amvpOLDQR1aTLpDCLpXTl 2L1LTB4Yri7jXgmL2hzYm3VZFkUIqPXIu7zTPLjn5Psnh5doZzqBvjzaN5o2 3S9zFQuxJ1DLx3kiIrl4KmElCvZR97KcGeomldmc4TsbW+gfkZBUG2D5odmg mWDqlVSTgSJu7ITQpHP7XKKw/2ZdQ/evx3j6pbs1/CjYbl9kHH7hjN2t2lbB EGz0H25oIhs6YC4sOqlBZunacQmFJH2CD5rkpKgJRRFwaDtnErPpldkFrify FQiA8lZ6HUFmIUeAdP+EYq41EElD/1vVyJxT/9/OdtbmRI9ZyHIMaR3zIWFj PeNh3edypkPCRdLPdNBnTgOuojyH5KtkPdPBwfxdM52uyPtZTOdv5H75azCc YKs/g+FIoC2anKIXoDAhbc6H4DLhYF4HShVVXqSg0mG6bHWvteCMz5zGzjks K6zhSsjRzDcL0PxgVswpkitzCjrECgJJmYMZ44aaVZpifWmOAqH+QCFjEa5A oS7ipSdBN5Kj0EOPsmEcBuWTEzSrkxOsbBzJCmAUhniOaCq8wyGYbdf662jM mF4a44RDJ1A/D9RgV8VbjoDrLRYcQpjmsHJgGhoppIXYdNixLlLJzGfxwfII jD151ZAVSJMAb2qjkiLKIg/ho2yWXwPJR99ITh6T2C/08ktoWYIk8oHOQxQS upYlcUSBiWkdkECNbUlKiG/cAqeP84acRG1rz2VpI8QpU75CLjOzafwSHYxZ Vp6sENE3YZH9QbY28Xg7Xxnut4kTtTRFvrguqbQjMBmG0FksL9jde3fuEaNb dxXQSoY3ge+cDEl5Ofz5AKNAjuvho72Nv4Rc+9mxK0TVzulC7MSHSiqJW3Pe gACNZBFUSKQjiKVG0mKZz0Pzn8coTNooGAPGZGryUrbuaXfkUa1vBSVrJTW/ gGwaxZp8k35PKuu+c6ByWMZHintxTiSxPO6+/Imxj1EcqSt4ZVyvE0mnRRKL mAalILUr7+VCgvn8ebjRHcxxDkeVSkSKhtsXenmJNyq/bEVQXOU5l4Jjzszo sNwkkSqjQenv4BG8S6UstYSy9qJMlQTltqADTbknuJKOl0j8iC0vWk7d1/uM p97TvLdBvVYyDZEQHuZZXbtqauPKJCB3/yAVc8k4P81mLl3y/qtwbbJWsdjC OWhOOzOlJ3iaeoDX7rBlu4pGUd4vmZ4yClMlAgfsopC4cMgsm+ThmFvhKCrO dMarz/GQJSVDOOJHMyqR55Olc35azrpE0YAcMR6cczuWWPHzdWto6y8f6Q5e Uk01SpyxeqpSTpmUSz4u7KS/olxy/nD4+7c1uk4xBxwlReh4Wq60vKuOlGN6 2OmhFU6Hu70kXBdB4hM8u+eYtbdlksp8IyVf2p2RSZhQtJy7pD0y9w4osXBi iCnB+tDFHjiQtzjrax/l0b7t6ewPdRiU2usaEYecliyoFxVkK9Ew0j6/2K1B kqVvnPh/KabNBtusU+a5W+9cuVZQr/7lq8Mnu+mNf7+BRlPcKlADSfwEIoSL PH1w/+FOksiN3bnD6VOHFBlNjdVQp6mBjnNTX75559HTOw93Xjz/d1MS9l9f HPzx4YufXvzppx/+YLU4py5uvPju8aunf/r+zp/vPvrXHx/96cHO9vMfNsJK sDK/cHSWO3dL3rosmQ9u/fx6/893X764ffvVi59/evHTwU8/m4F87FdKI1Nd vv+MYOcOAQGhAzuq0zeWa9uNpQ+GfK9s6VXvqwq7gHogkm5OKtuQfLulJ4dS DlTHSSzdnCUiIY/epfbL/Org4Yud1y9++Onn/Xt3Dr978PLed3+8/+rfvnvw 6PHTVy9f72w/3H+9/fzwVkADs+yE5UFeCI1tZ+yAptnd2CtsEg7zptv0TvXi dXQTTsqPfshzGuGkXr7YCN752FPAWBY9XLBu0lhdjHjqWPk2lkBW+kzb0nP5 aeQoF3mEkpoYKQ2SpsCkKVmZU9BpX/ZCSlWZz1HLy6ZTaKZRxjalbJU15utF AdTfkZuPnz3eGkiquCVboFzNNU1v+8zk4QqsXiZ7cYeQf6UtGfS1Q+sQNsMf 7XJA/L8YOr5Ke1MYRNDaqp7J57vS1C4haPfWEMyhcVh0oFgj9q4wqlPYh2gV KodK6I91g3/ETwwPMR7yyCCQN3E7jgZBaTFyFvURqiKdOajSl6rKRycjoafF 8qLVZVkFvWq1kzDkXlBUmqUGL7kpPMICl0NspK5mvnWsCqCl+IS+tre3P35U hswQNNcHRnhy2CxBmdng1GiCQNLQ3CX+oXt3fwzyttlYClEUAsVFxSR9Wxet jRH06IuEB3jFrlNEKRHvsJ6UUXE0K+ppdyj+ddlyTYFt9XCVyMSoDhh40Z1h XB90a715BqZUmQRdmtw5l9YnoqYiQH3oBEBP8X7D8SITAcrCBA4YST0itWlZ MWcwlo+2uu6KmNMMVhHFqpO8dsuYzauVnDlKwcgG8xNZBc6eEM9NS1OgTGns /OH9RwNE2Y44cM6TpD0M2Or5d3Nz1Z14XcISjDNOO5ehcZoSPtAoxdkJw6bn hanqom3oJpFkibWY+Q6wTeiyBQW1ogq7aOfiDhYoyKFvgQUpBjRfdpN1Aqjk CjctbHi6CUtzy7G4sPQW8lBJhOq9l7Gh0IPZin/sToAQt52Atg4qrw8HoVPU QZBcvbuwtHMn4buTSqkHyt2ZEcQvBdAG4nyJPr0ovx15OGQZH59xNxXLA+HO R9zPkXq/ULu2JK5ODmgEpQBd6t4+pFLGEUuOLh3e2oMdFDXr22VcsizmN9M6 BhFHBFjxITflEZfWeW/LKF9e2/lEZccNxLyFXAReu3crFCGSsACfBVW6d1fh 8Nq34hT1lv13B5oQU6rZ6yXE5jSPySCo1LHWGTObRR1dRpHu3rRZMR6xIINY soYimuDMxc+by8NSO0NKN3EyUiGVn0QKi15+fO1ioAcVKTLzSCJV0MmIeD3a 1hiSds8swezx04cMXH5oaaeB3ILAkJRrwsS1F7zxZFP2JrgWEBpdPw7wicst IZPvFoB0ZCMu/FqQLAmmvSZhc8h2U8a0HJMLhh/xAmg1o3kl+xwBkCeTM31r XXwSSW8YsIAwnJQrsBrqMTx9/m7lI6j1euQMckpCFYz9oW7HNXEmHka8LYV0 CEQXcm0NUVMTLQqjm3xGaIZUsuJaEObBNfJuyEETU7onvLl9ttSyX+xNArE3 OaImupKvabk9IWhfwid8bnTnk70+F7p5VjaTWqKqVD644Ig6uvfgCGMvEJ7L 2RQR6MoHkvZ3e3u0g+NENQhIPswlR1m/nJyG6hM+Rn2yaiRZRaneljh6a8Ut X1GOHT9JOPagr+Z26ArBs2yczy5ZUX0oRlWSWMvnO/I13LGrN7wNXi5XOy59 vjXAm0v4Zzg2dpDSZLHhmUXbNYYH6LjOM288cAa2CHU7mVOxfKmZHXuW07yB rruuE5PBVYWhQBjmBgO3EPHf504MxLj3+pk3qtmReMGqBUgGoRbdN9C4K3vT X4aLm6SLiVtgobOHcwundcNQIYv9gsO5UBrk41U5sfEsvpqlqwDnXXAOnMAb cceVlSay1qlGqmbRV5fl0d2TeS3s0Gqs8CJr2SlA3dqSQRg/Qi/RhUQ5zfVy 4BZR2CHHfaYccS4SF+3jmSucsq57V1In2GWkiUbfdOo6G69wUSn78HnA9Hvi 2jpMgcvaNG+LMqIflyuMQCQ/GdGFZQk88CDjVK/jou6J5Xcqhabh7xDhImuk IgZnBAgzz4b6icabncGfDqjBpoDs4KzsU6YglAA4IHdRFxXlFULqp1FKIow2 VZGq5K3SLU5J5Sp1QB2hlRjctDgmFwnvcNajOwYxbyPXfFe3dfZEUplEx2Vn o/DIYt1Z/rYvJNc1zmkCpRGbdduktc/bwXiprXckrcj2SbX3ZjVmlXbpBW3v LdOyyLRlK0FtXG16cT9zl46ram28+wZmJ8hBr1EDOrvWGSiNyRYPmdXF2SGn aCarptF1NDV0RP4XLrtkPczBI6nWzDVRBmG+r+AqG/OcvAuSD0/r7KOpUXiZ N0hNAeluP0mn8VUwOxQuAEPcA25PLQL0VCpFQXzJKXh0vEL/BUxPmGPFz6pu YsIYD6VVY6kzmK70EeAMl0mMZnd3u0CpXqVUeeH4E2/iqyGc9ilkcQYF79zY WmgRWIYPYzVcA/O6ol9Rhz3KatrE9CHQZLF3u6rdIXB9N16HafdK+FqQX2f5 /8Fgv00UVpdYbreh8jDEB6ulFFf5/wkouP4tGhaGbgTlRoXAib9So059+S2D jI5UHQfUjeJlDSJyO47M5GHXCDPjtKRisZcErqg3Q3Mm+gL0FFIEA+kjJCMu lOhoOCj6Xh0HzuFOdaCRK41wl048GXRlr0ifCiUQUbFU6hEOC7hEKa3lJ89N 86prCI9Rb7vRPNizusTbqx1Z2cZ0VaOcwov61Kwnm5TQrRZfBLFR7zNqknVI ObtmpdymhCsUTWxA97PkmScWnJrC0hEpP4RZK6qypaHFS4J0xhj4+oaGlU9R wabfQimKuhLNk3zhZ5REKASsfGPzako805rR6LMLUNhhhqiVi5uccBUcObt/ HlORy0DIGXWWSbY6yMPDrZlVytD3vVhwMi82/XWkCa4lhAXItP7Y/8femza3 jaRrot/xK3jVEbfsa1GWqL1OdMxQ+76Q2j0dEkSCFCRuJkhRlMP//ea75QIk KKnKNdN9pj6c0y4RSOT65rs+D0+Ou1gwdnewNMSatZTGsgjlClO9bVJE7I63 zB1TrBjDhrQebXUIaQaurTI1MCekRcWpau/hZmP5YMt97Vhok/8arjO0zJzM PdS/JibuGcWacvYcj+EWZf6ls/XoGsTGLRZO9/A7h5lj15mDjECD9sqmrSHo lr4n/bao5SGiXz4HLqslHX0c1kyuoNK98PTbPqaB12bTloZfRmrhq+96q3WC 5PTUIrvZBsijowymmNBs0iceRXTQZcEeMovOmwzNaXxZ7SHKB5jtYVYlkhKy pqi+ohnuMV1J0kPQpkFNkyH8GmHyIDU5ujNCuCIuDtTJ0m539q5lr0cnFOUs azB5KQUUku3BmXQhjDc/CxDQRkmOA/DtsFNg63vE1tUySq43i9BiKEaQeU2I R/xgRt/QBHnBJ4jpMDmOVnKxlVHXesFhuBfz7eN5qv745x9OP/RlF/6pzML3 xmffzih0cwipWUhN0w+kmgbEeaywfOgOusWwF2fzHVH7cNrQPwI0eOoF/PtI qTeR74d6t9VTioibAfmv1Ceh7mXCR3NmGKo+fZ+Ux2XvzWBZzVcUQ5P7UQ+V RFDzk9OPdjQI4RHfRxF7Okk17w2k0xTqmSnqVgN6x8qy++C5Zw3R0S5cX03q sOnT6RRo/eKjk5e169urkOYNggnmpx3B9dRKTUteVPDbGyHBdMhGsqRNNZao MUK5p30yEr1xA8KayJVjm4cS45kc/zYB3ncGOHNiRzkRTiWQWxH4mk3RWzs/ yJla68I7gpyY3xdw4RzOjgHyIy0ByyuRvKcmXpDA8ke+K4jOxCZ8S+DSsGHO PhqJZmHHpslTiINDvbFrqW34YBLUgK2yk6txcIGId7Lzon56KT9UGaIOoMxG XwdEdGFvAGQpCQdj5xilDf+jdEeXbrfTojFQeSL1kJhezB0d+LDB48Gfv0fp qFqXIE4viAXqsX3F/alc///IdP7M/Y454lqoSSL19ORJLHkn8Xxr++C4tLVR 3tpevti+uTnZm9+92Tw8Ks1tXpwvz23trJcrJwt7c1klgzoh4jSdzb1pHLK8 mcxhwivDKp8VvhyxF1xnqrjwfGC7StP89p5jdPagS2OVGig1bnBInJwgdv5a Mt8WjtNcWDZmdG1lYHWId6wWJlwBT63XjdXEtlagIzBONit42mQS0JxxfByB faIzsXVuRp/xuI9/jIjTzIyBJNXMO244/52QP7FvXHJh4DMc9AU3XYgQqrhB ssdvZkipLJQ9OrPtfpu/G4hV4ZW3+stiR0ntrxvFyFdZ3pBS/gPmEUvFlOT6 by6m+sN4kBgB8S+jiFpUWOoURBmRgQXunApBZPb6wss+bJXtQmDPvdhNBOmT San5TGeDLkCA/QAwbAxuSmiJP8BJBKmbL4iloD0l52wCb20nm0aJ5hp2qvlb 1o+SpDjtux1mJPqRrdWcrPQZhwwWfjK155hS7KgBB3zR9Sh5OCWhhNTRE43v xkNUjq4jNVsG3wBe7kQwZWF/nFUj/U4F48JgKZ0B/5TrwxSSk36poac4aRAU UdSRAh+Bdob+3Cbi1jjBOAEUfRn28noMqy4Tw1psF4tpuuDjmykAUKGeFQdF UbAKfZIfY0HWIDVdnIV5Z+erpRipHMK1mUyOtAOc56ODQ6+SBnCQQHAekoGX lidA1henkwfExEYIjDZpi7+T+P4v7Z/Qldh8HnYHDYkB8gIYPHhP7xxKkF/Y R4daIU0lYMecczsrMNSTOi3MBH+g42/C3tsM6nbFv4hpDxq0nczCkgKtEixc 56g0QuHlO35TwKhS+p6FoI0tZPrsFOViXL6ZQvYH19vCNH1vzhn/onPPaIzi Z8fMwoE8l2YOcjLSSEh3C8CIEfUJTDqcBP6+m50kkWLUopNmSZo4Mehl3pOE Kj1TbnDKpTX9NuwBpK4nGCc+Zoi4fXMHnHuzCfKMDWihRubEbbysS3RN6Jym eldg0WAuIaLA+XdMYWvDhpd15h0m8TlBrQyXhVmsVKQrl80QGWor+rVJ2FM2 JsXZRNU+RWGNXTP1Kmma4biOsyGKSErDIM9Q3reCid/CwJFQJPFdOlMg+DsX e1fGL4EctdD9CFMFhcnWpO2l4J4C6Y8SJFGaGRe7gxZMl10+GJ0kPgAJdwQO oFmcY4lxYDlJqV/pff2uegq3pOlD5RSiMDCEV1pn8Cmg76GxTAH5UPHwt/4E 7cRHZ65hTGxXJS88o1TjimjU+7TDwMPxkqnR0Igj4ggkAQpE5XI5WSbkgDPm 5JM2KedznMSDbN1vwHtOXvEmp0leEkIpGkjEDhDrPAPqtkkzFfZzAgS0IAm6 /VSyAZq3PrQ0H8qKPOVYmAKv4kCq2OEFGKcWhDmJ7oYAHvEnCWSIRaRcwa1x oB2+2n2SpQ0q5CZ7Yk0TZNrq6cWpMNsKwG3EiAg7wGuunta59/GAJtSISGVR ylBCNKGwW/AcAkvCwstCBc6DWsThDQuFg2QcWOBwDxbUAA4ysDdFPEgVSsh8 oEdWXdLmBrYlokaQBThWcu86/acJsRIzaDPykcSIrE7Voai97FhHGXLadJnm AouBOxnYlQ5p3kV926eJF888SwsKQJI5bTIhXsuW6u9zSh/hvIWtAWeK4Z6k gzcKHe7JHLES4L5hgeT2KJ5IbusOdjr4CLltwZDb4u4ZKw20bbCiLTo0i80W zYBpSluPDYWtM+rA3vCaxLaKEXjA6dPJe47uPJEqFe6VSTae91KZyFiac5/4 Kb1zLhP1CN4jUub5kXskjYUYeO4RoANNXyGFCVdIkPM12Ek0MA+ERP5VErzz Kin8iaskF30Txm5dJeo/nVuEhvM/Bi//1PeJc4m4x42eBteRy+dqU1paB90S LsEfEC78NUPLBQYn1KeqIwNf6pL6qk7XAOZtWm+hiTLCLOKbUsHNSHqjOGii 2MpKO3XHAppRuzcQ/xRkhTPzhXoIc8/taUaccvA0x3xNwWcoHR5Tixielxvl QKkeaBRkvDkfFSQWk6z2bCD/kY9LNtdn8jFBEnyre3woRcji0FLUJ1Hkc5+D v0Y9DQsWuain6hx2OEqXwJIu2gtOI6k5BhQ0F4DohLHBQkB+3Si6L/TCJvhX nBpc8AGg85gL9ViS4V7ELGNMEWjh+uh634To/9hejcIkhlCz+pq2gOXGDD6J 9CFHkNICByx6yMWRfDZyzQeZjqyDUBMQ4h4wEq4NkN/9wqcEXS0+1kSgQUZp YI8JUleRGgxABITuK0i6mIX/BlmYVCJjzgBC5aC7GGRoD/1LZ/qHjuWhIapP 1BPvI/20VfhCi9hSo1K3isxXEj0Dm2fQVoai2sozeZVXhPsJX7jH8l2TUBtB jCMwiwa9akWd5uDhDUFv9qMS9+W5tfX5ja0tR5Z7RZctuvGytPa15oFz1CnV IahUCzix0gze0nTiAdMUKOOecG8hL0p+GQ6CcFiP71tMq1oQWlXbe2jLIs1C aCuumBMBkh5QmQUoVW5x4VdyrXOEfRWlXFtDCFUXWEDmqEyrT3f7WkBUjmeM VaUPrZkT4gnt1MmigPxXFiyEnar+pqHUEI0K8PLE3vB4KTM4/rBH8FaDE20T 6RbCwPDO7mYWC6rgmKc6CMpZSlPtTq5HUAdJX7Qkje28eY5DBN4Dlya4BoRs PvbQD+TZgqKNOsT1ts1gcm5lU+BkQsXFu9hQU5PTCeicuq6T9Cw5pY8ijVlF N580lAAsBeC/1bbWdcEZStwJN5P6/TNO/h8bFzqEJ49KbTE+mILQnLU/fG5C C1udBqVdEpMdQTCYQCt4vWG/100iPUdQ5Y6yQwpipLsmKEKzEXxUL0kzXU9W Tmyu60kxkv9+egpuyYCT7kgVsPPYM+S9CGWSjcCVJ2kxWoOAKymtzegQEmHE /QqNBj7zbq0GHn6nZgOP/hXaDUbfPpsCwbeVHHjyr1V0cKn+jLIDDfxZhQc7 4VV64JeJ9M1nKQExyRfJpfRqnOLufmAyZ49FT4OOOsSL1xVkHUtjqmduktyw 3IRpEW7g9CcFP92+Jek4wU5DyrEZqRM3OzZdSstHmApO3lkX7sOjm6Ry3lJC lJWSlVFEJ2DNiUPiKykUKUzt92uupLT+ra7a6qp35jApKj19Hg1CR/AGtk4a ZNVfPFG6ANSeCiYrS6mMgXxQE0J4jpshVs2cAKza7wErAtWh6Q8E9AENM9VW 90b4hBUQf4dEckIivypeQcWv/ybBij+tRNqhe+af9qmMnBvy8XCrsEsrJXlg B/9N2AdiA0P1Waz1zfGcMznE+7THtKb/DiIhnSbkFD6SBYKZP0HuFkeZMEQL QAiXNWCwTv1xAKpymYTfRTSYwxzBt4jG5snLM8rmlPikuOijg7CWd7BlkLT1 U9zmTr7SG6SR1gSYI0rSK7Eb48CGrzeiEARaNofpJB7yGscDhoFmb7uFj+fu TZ2k2XFXMuNRnjQcTG4QogGN4G8FP35kCAZ+MrG4ecYh9okd0Eh9GKhwyg+D bVe1qi0MNXrTvlkWRMwghSeFKocwCJgEJKvIymTFI3E5KmOaqohzYsGkiTtc uWB8H8TGkAxJSSZvCfPJuu6dvgVMAsktWkUhe0gNEja4mngjrAlnCsYCojFw UrKs/GMlbhyw/M8zaVzfdwIcoR3JrAoe0DvhGjKoTlnGCS3BUDk9dpDt7glM zmF6sHVYCKpYtBbZxjERVt1mfaxRfbOHtgzUb0GHpHwGU5NSQUX9JGFcOKSU MAaiV8vvtvkSmkCYale/DVMpxmfKuFO7u91j9g2ck/n5+dWfPwvId0/PThcM kAgZRFo4yqxg6QsCzAM0XwtKDvmjOVEwIrtje1ztDe06NpnXQO81MBqfSCBu FzZMI2ZYNoe9UJxXQpyl1IXyCYPM4yaIRYEjzZ4RvKxncyEH0moDLYANIl+W idfLa9tWZrsTXxVg4VDPsyaqXkIGfaKvnVjpqOqPlGreipOB3Aj6NQbI05hu VnZiummXBJOvHoba0I9u8aPpRMTMBz2cBDkAt6YfDkYSckawp0M9EAPFS2gr 3fo9L1DRW2XShp3CwzdD5V2dwrGysHY3gHejg5fNBlXw/m4rFy4djIcIJo8C hslfrs7PSodbh3NXa7v7e/vVjfOVU6zS+UmV6FPmEPvbjOtcEDSdqsmOxo8z MzPclGg0VY+Y1LaN8VSJNxd9dnDZCKOcXCmUKwpZOVX7XvBISlK/J4ERG/ca XkrcAmaaBFhSR+shP/TCuP8ZUzJaXHiX8Pd1Ow5VEEGdPECtGHnrPkOXAjvy YoxGT9jfQhx8cDYJ3l9U+SdyzxJBgV/DfSMfQOQbhxaoXpGXJ++KczjTA3ah J+JQFO1fEw1+hi4gW/c0GMHZBTO2rgM3R6k/7tR2+0HozC3rJtJYYlxl2hqz 3RM6qVinH3NNksmz1qaCxmVUf0z3wu1DnLqX+gGqRTExumSmzCgiytTFgi5y Y5x1C81oQPeDnV/sq2U1FC/2jSMI1vbNBePXhpyVK87vKHMLGCjlotK2qLdZ FFOmrg252MOA7V1ADaMTlZ+zlkoVjzpaeeQpT28964rV6yGLjEWeiAVIRZ6S mIU2HXqP/kz7Rnu1uaPtbDeoQ9VsPTIui0qmH4HBnnuMdN2pKeyrHIsPSMt1 nHNbKKeUeCn7qkfgnWM7EJU7lBT22Qv08M0VaPH/6l54jiihaJHosdTJTj3w jS6dKV7Y6Y7AC4/eIu988MaShqWjgWA7m+irZUNM8B1qEh73i1nbCFnBXmzj mfGeGWsq8L6byImqo5IfpyBuBaF+CZr98aN6sjI7uzS/DriYTlkqiBDgN4ca UF4cI/Ks2VeteKjWcBNBE2hqEDudXkNp1ph1yj7DufO1ntN4aLkSnV06Uyhn b66w9UT5XAFUcKoe/JYYPVq/jTlx99FgFJE2D/HbUVcuNAT64n+jwso+OfAY IUpMILs7pTyBcFcbaNiOhfqVmTQIlUIZml0Qv60CijtxDKQuV/ShO0iIjbg5 7LMlD1ZtfwgStdmPEOECmGwHzAUHd1u/2xyaFQVXdKsbC+R2N0A6YeQiCNVs 9ZvRwLJgaPeTUuQupNrnmw6drAfsEo4xadK2jJcDaDE/uJU/Pq+GJqXNgbjj A5Ep//kwY4femRMqTFLQlUZEMG5lCqwy1833QJFJIGwjO5Kih2BaMjAduFlS 1rKFg83u1qxd8uMfWdMnbRBMNnwE+s9ZUDDRRNG+Y8M+xzgofPrx43h3Q0kX YIDoFPYuMejUA98fa1Khhc/E3B3g7AjbrRI1XqiWDw8KJaunqlH4WwlbRcYL TWnJOE/qyl1aGPZbYjMJn2EPNiB+wXGghYUNSgCCgGCRCt3XaZV2ZZUMPabt W0tzQgfBIQLPh+A+7nod2sZnLC6mXojCObQYdtBwCVDMaY8hqUEMdmr9HSYW icDp72w4IrJswJIyq8h31QZrx6+G+NpopbC1wY4xWOUm4icy71t2UKKROU52 +vVzIK8ZF6OG1iIuVJdRQb78eVrmiPGqGZIQ1slyayjB2AYXICX4gwpcV1d6 C+RKATz5Stx4im+RKkB0S348cNdMgxzWMKlYQ2wnkVuqH3P+DU03ROaDqKHO CzaCZH+86Q2RyG4DE8b64jdnUBdUDSV3gfVjuXtNSMQo83WzcfMsyjTOipue psG7LCemlfmP13K6RbwniKfBp+U46U9xEnj6DZ1KMa9jxkIcDYlwgoGqHEc6 epiDFEYCfVyjcgbWSTY5INk5sfW7fuQUarOolgI3MDAoJS+nJBrzOKAEE3I3 PEO1YWDd9JMgt0rOdd8Bvwfe2rCN+kDxSNYwqprk5nyOwhZBy+R2AAz9ib4H DaMa9zUjbexAYhg0f84Z4ZwQ62OpYg44gpkJM4aJukn4r8qgSGdJOdXzDEZk MRJQtMn4GMjt6e4KO1fLt3ZwrjnCFqY2JJLnQZsZRDZXuIk3MUVt8E5oQu+p xjq4ZgGN1lCD/+eB+2jKeT2R4PFaXl9eXyjfrO7vVKpLV0vz5b2yYOj8Uvpx nWpCPjV1r272+yBaRdxYt2UEv7xJzGvdjohnbpIG6incqmmKur0LbaVwh1+/ 86tzhTYcyWaULkGQC9kmZAmNnoIxUctyNQ+SUOeXcrIEjcc7myNYgP3PbHCY Z4e9p1uGXPYsHvHvafoEOYTeknpan3Us808r0NhaEfMpsz5ri00p29mHobqi i5D0g44lPrseAiYaiPY42nEpc2s713CKzM1FKoxha4DB4yf1oYCba5DQrKRX w87yIkh+Rji45Q0p2Pxmh0J2QMyqeYH42CAMI1hQ06IyJDqkQi2aRwRGEvPf DXd3O2yBXIOUbasfNBvZbkCAqR3WmRxHq3sD4YWCU9SPat1mB4jhBSMeNURb pk8Lcjy9r1Q6yGcPUSZK+gHmScWtVMcs1WHqjjvns3K0EhZ2Cv6gOKV4YKko eJoZPD8NNCId9aIbgTjHhH+CrHB7CliruouIIu4a0pyFjw87LwrCvH45BTxv bQm3gadorF++VT/dapwk3ZSdN0Ted4Nn7+H7IFBqd2dYnBZmfzhMFxo7iqe6 zkYxuQNY0OpEXWwdkxPVpRRDX6XRynGB/mTLanyc/515w96m/CrnZQ47hqSe kQjxux3kMLqF75tm0N9pvN4p+hWedyI/Mg52MAVkatUFXLNqE0SNqA+ZX0vv JacTzt72JcsiUA3yTTlTGWGVCqYNYHuDbve2EdpSJA9chLEPsaegZEPclUeL nOP6zrrXLLiFDvgJQenV31LSeHzLpYzJFJvSSGlpCCD64K0ycznogqVkIHho SZj5nRri+1FiC/qClIvGMs+QueNxSGBCIWhvcEyokga2JnmCEpshysaLMffd ZICYd99mgePeZOQS727mcJpeZHEgsJjUrnzXh2nfJdT5UR43iLobMXnRJBUN 0k6q37MKHjbqzxG2T6qVJmzdvvBU7vFN5QuXoQ63E1IYwbFO1dXbJQsSQ1vW 2GnEYcIrxo6rZwm76J+18sSJsaitO4qF1r0oJmYCk+gFAJSASKsZ06l510cD 89LI/QbiRmdKqk7DNa2kJt6QJCeEmUXr5uLl0OFDv1dACWLELIVVBXN1wpo5 KyTzvEtBRJwa8jziFUdnUlJoaVfEeRTfhU8ZSuwcqjjaaZ+d9bRZw+7kkTwV mYwSwxtN+rSTSWRhf0lrhnALPVJ5gWVCBMohAJku9LoD9M/DArY4sXwAmIdd qdTmWHxT6dns+ZYYlJd/xQMYVNhgYwTaK9uJW7id1+E51esfblLXTyszMj0u cOkSBtK3FG2ElaZs3VYN9Fy1omZoIHvBxgncQrYweZL4AxeQ2JicMdhCXTfT Lzb4XmqTFsmvQioF1b9rv9y0NqFd7GJZFK25ciu+EFRukzp1z9cacofY8QHx FNpN+9lwLLY4jAVbS+J6/u1jpN3qfJL0wbBsUqRWdZabAos12gvkO9KKPzjW hq1GjKTiTj4lL6qGQLBi2Q+UbAGxftou+Kr0wdCF+bOv6t3asI0mkg5joixg wFnaHATDEvTgEu9bGbWUSCJYpmpK8UKFtnkYfLASPUYMLIlZQ1qT8b8QhoLX RzbtLKKaiQeUy+LBTevyvDbkj3I+MQQIBrP+fdgpiEgGhVPlDuZQqEtnqP4M oa5QdgweQlANe90WuGX1DYXqLvq1g7pSRXFQFIRRvzN7D/WX9SwGe/XsigLv imnzLliqRPZG/Q74rDu7EhxGLj84SwN7EeJUprkfRsib3RuIUzfPsQ2xP2tR UUIgnmFKLzayXxfI6qNtUFx9Z5si0uQMGxhDPIOwa4P3PqAyoemU3/ehlBDR GMGw4u+VHT7dHHnKwDWPO9D1z+pSDyPIfbCAviYTqiqhY6olN9QgNpP0igx0 THgwzgktTbP9o4ODCNDc7fsSILSLNE+yp7+VXXP4r3ctgz1bb5NbuYbdR1ZN 8msMj3GcOCbjWykW+aE6lPqIhwgLjaH2lP8Z9KA2h8kgsA7PJKJfJuKgEkFh vhpagmCyY9Q/jX5eKkp+1zGohhDjia6k76ZA1AxLLWx3nz0miezvTLzcilIR aSDoO23gUwgxO0OfBtJAKOBH8XkGxswwt3jUiplJfmNbcWAT0xHQUt7gxNuQ olHs1w7RiGsP03CAWOmIsj5gmG0MIUu6MXjU1MEdfybShYkzJjp7YCaMEpuM sU3FLljgRIWV3SRsObdPWhUxx9yGdKocOxd0wxi9H5Dr1m2UPqdyc5iYcKgL rmJiYNR4BOp7tQfAYeo0deFSWvXXwAryZFS0nPIMIY9XCE6pTqHxNSYuHQ0/ 6JdBdtehr+qY19QQyMAokGvKlBsUpVqJYXohgdMk1Kt9Uuw2ivewpLq79gew AM2+9VSD0UtUG0p74fBFTTWoFPpSNvLrvd9Rc9NngLx63IzBjzOC6RyQYAwz 1gzrKry7uNwEP6pOK+qBaru3ogYI4FZ8j2FUdZQbreglJgJ5dlWilRaMwNB/ DvtxRBeGsUfqUa/VHWvF0cSYSU2iOq5uq9vEOpfdjpbrjlSCo8oHQXqud79a EOgD3sv0378lpOeNYWpIZXP3sggc5ucL2BvGIlHXHuEV3VVdhKqQDAK++q5O ISNDVKf9oCYsPq+RsAC6XwnyVGWzd/Q+rlRR3PSR6dKuMWE5OV3gVBESOyTp YovUUUSsbhtFuNolDIAA+RPgOgsH3T6mrlI+pUVQYt0rrMzCuHEmQH/hEjLD Fq/dlwS9ktpt7BNgkwQdidhVNPDBH0MOGvGgBTZMUGK5bthotuMJz6AMJwme c/btGnZOUweNthan2vW7LU3hw6m7ZPZY47d7IOYcybS4j5YFz7CaXJPinc53 z1cu3eRvKhe3TH4tj99WyYOwQ4uH2QG0M+QvcURZQlrSiIRhH0UKKd9XL4s/ fDaq7U7EgOhgwQ4TxFQw50KDl2olGS98dynsEieaT9E9pzO/wAU6TDjUKsml SgFsscc81gfQLst2mT0Cz11q6Qc2HjNKADKRPfxKjpMiNXcBo576KyJNTkt2 1rWilFiakgF2t62JDJ4S+5kGPjaoxItpr75h15jy8sYdJhEZdIOUZarVSHcO cLptVuMoOyfCMgAy5DmMWwTjBY14iHT5lJDLOeEfBEoWXC3o9X0fHC2EFpA/ wKf++A1qNIxB/GBeJvDN2NE0D6a5+PMCViktnxtDLEA0tVWwKMjhu9+4Bjlb Yp9aGS5Un2YmhBCFaxFvmUDddi0sS0S/kFWjSueep90ypZCcnK0p/5Q5zpk3 sfj778Ti5yOZ8cqRr99rXvghtmB5+lEv0qZRxnvksCsUvtEnqVTSt3wO1UKa aMFLsMB7cVKqPyj5WZx9Wo1wQPUhXfKPUUon7xcd8KLMsxmnMIVyTR3mAmOm gtqgzl4RN8fQ1qFRrLGYIGVJqoACjjImBF0/zj24JoJvmxha3U/YEjTGwHll N5nxTo+3I4VJHXEK/4lQUkSUFtFp7xYpn2QkK5sqrD+rTYB5pJ1oAETyViDS toADo9ta6dd8RDEl0rOgumaG1MW4YV8i+vYJMnlOsZXNbSpI9C0kJjWW0tSj NoVCZjLhzGyar0b/NRaapTdBgEnHxg2ahs7LZyys0A4Dw8gccen4EQ1Urvke BmSmU+UPWMSslMZAgl3GbQb/IuJOTGm2/NpmPtVjZAsiHQZjLmBdh+SSYmIY heMZv6aDeqWYVVFbI8FAhFNZfwJ2iBE9E8vORf6wtQtnfWmETm/AAR+l1lhp Hs2YrGWhPaQfRHcNzPpzK9hmDZ4RoGLXy0b9hdPe1BmeJPW6tdqw7xpTelHH gThZbUeT+JJYHllZRFhZpDcndjkttnRCXK4WvGutJYEbPhh0JzYYxORmE08U SLO0Qb0LuG4CVBR3nrut5zw/A/ugcs3eVPWTzBR+hzBkUq5ruNHJ28qoEphz xJ3lK4y8f3wHGRE9Vqek3+10hwnDj7maWRLwPNp1+/Bzg3P8ZeoIWOmTsRcB awgo/RjzGGO90gQXyFkQ1vJigCbuA2lFgpvNlhHa0oQIZbfG6ZLoYArv+3GN zYyxVjhCxFnAMFwmj4I1d/v0oLjnPlgIB472n9LYMyo47vXpwPWa2wWSPCJ7 HMh8ruucIKBqa02wGXXlQ1TnXHLwVYAXR8pyZdGlVcfdC3sZi1inIYemH98D xh/OFtOkWtGtorgRuEHbm5ACxXdiiupFyVGWI6feHlFwxakMlMgsUGCjIxQs +C7hvuMn8CVOe6D+YAqHEvEQFU+s5im8pOPyjKFIOJDYL8jAazQQ8AFi1pKi kXJkwxLpgnMynDkVYKI/3g6Pa0UEs5vwooaT3AulhiDUNNtFJykFJgn3ozIJ AP3NLDbKuR7pIZb5g966Ojr3oU4RhuVEAT2DEceyf+FEr8P0iKSrczLtEums y9e1smBDx5ZjPGpD/vIgJdDgyCK/cUCOJHUvgndbCFxQatOuAL0ZrxoCxmTp 1VEXCDP9FnoP4yRW5msH9zE+q+Qgc5+Ghfuw8yRHKpAPgPGjfm4QnJ2av07S wPJ6Nh79OUdSJoqGeeEI2j80HngQThBRFWkbMoCasUjJfVeoxf3asE17KEk1 jtS9qdvbdk8EqTzBtLXBxkvWDc+1V06XWEHGCuihVsbc99IXBG0Scq+lN4mU VcK+HHTbhALDnk/NKuYh74RQI9Ziiw8G/avRwIF0inSNFskHUlSoAa020zZL Oy/N77zPZAkdxw8KUq1KUNUj1ReJK+438EE3pXwLQ3+ZrZLRRHFZEblJXzkw 2RYOqC50cX3FlKAE1RbSCzcwBdtYPLIy4kQH8dL9kO9iYnwqvfQSEwwNZ7a4 GhGuIJOSQTvWxeIDJ5mT+W5keN1KYxJP9W8IT0HQHXUrCcJOX/Hs1+kP4AX+ 4x+FqnhXbE/BpXgoNwE3OsH6yYzHSbKo0uBquXlvWbA511DlZBQvPAWrV1JR 5Mdqz3pWZyBNQ/vXUinsrn9L8xSTjz/4sJPPru/1+qeYNJhhYgZRLwWUl0qs SDTxKbkPJSXEH/cOnD2RM9Fo8E8sFOZSYq6eCjKIT8xQiWVzbzYfvVFmTnAM LBBx2QRJ3z9Wc04pxpA7YQJTO5OLUGloG/El/84geGgyqTtqVYtWWV3YJvWz ERgD20DfYSBcErCZcnnSomjT1FOCEYQtyJ1VN3zUHOZ6aQXlPf0RHcRSUh4E Y2MIzv4UAOQbHRe115AiOF3PejUMur3/8xGRG4j4ssWHZrRyyOq4Y3bhs8PX aLPGiR2Edm5KNFn+J4hYUalvoLHE8QTXwt6A9AZUneDmkrAvhapc9U6M0SyA KkKYCp9lJAD8XpYyK/vRCVrJqz4mTMfZm6IryGPI/By0U/QOZqsZmarOnZLc ojmlvyUdVPcTWK1M+eZ3GdLFbjmZ0o0Rb1xB88aJro+esdoTujpbcedp2nKH PXA1iLTDxHTi0IBNiVqukBPId6lgVFkxbixL6kkNcZSxztE/WFcHHMUYxF7D PvFu73ZQF7CijYBHrst+Is1VS93b3jyzLmjHTYgeDWX6o7IIPjcb04vHbJ+9 bOaH5XTAjxHMUBNdjnyVQ9kbXnRCXMI8f59A4Wk+sKeIbpDPFqA2GxppP6cL aTRdQFoX78XNSBlp3O2UxzmDwY2+YqiHSc1wwUALG6IocaJo/XnasV0ZRzrj VjCITBrmi5JXbUQm2ZASodSI2rq2UXQSB2MujTeLEoTlhsXqAg2ZmlkrxMhI xAzoBchQ2KEM8QXdoMLCIZUJlslvV6uzXA9QoLpUAAhnyx789BKiuYVy3RDm uhTkmLhGGQa++LPg5Rox5EwAm2O8iAbswbgPBzrc6HLCYOI6Qv9IgY92cjJl nIshwSwAf479U0+n5fRgDp+OxYoZo1+rYLiXvULXrE29LvgAlJKpLTrkJ5Bd pzkzwCAlODjROi25rMUpnW4NPM+A7iDdyV8YGnR1xpDXzaX1S3JdauoFQ6WA 8i7WXbEknkMiaxGLGGwGeBKw56OAV5/71H9GW7NG6XTa6uNxFT5N4W/wztRn kPUBI9dZvtKitvugtwgtZ2pVW92wbjym1szRLPgvc3i0isVyFrNO9lK3SP/e vNRREdLsOcwqY1/rhpfMe68bJp38e90SvYm5POlbad6sTj2g7mXpbSNm9wq5 n8gab4ssvU89MLkBIwe5n4+F8BMYI5nsxYY5idrdPhPkMFwWu6DILAiIzSnp Mi0UJw/Tp/BatUp0Bxyw0Ritmu8l3a0AUb1Tnrgso5dkx7tDMtQfrPvo8rvA qCOxPtty/eBrBaIMUbs8CrFaaNjDhwhYYiAlr10EOMMdE/UD+rt23Fuhz7jT Gw5EHbKvC5pGNUtsLMBj3DzeDJgYK2Xvhp6GM/0icCMbUAxqOumFFLCxkNiw m4SqNBL/DjWuNlWvi8GdQE1qf8yjsi2XZ4LtzCwOQa6bmlO72JHGFoWDgClQ YGBQkRASI5cwFmUtFv0JfEcMdJyRqXDuviYrw8oEmib4JWsGtYoky4nvpBmf YPFFBbMwl02EGTOyIspZd9maEJaO6JoKgjBqsweJ0qbnCpSoPAIe8qbS3iSr RxpyAHXgpmR2KXVRxhJFRKIp7aRr38fNIZBquPFtdOM2W+PeQ0KBNh1sP1fS qFtnrjvkDTG9xyl8jiEpzfTJqMxKIhWJNBS3lF1jiBwpNtSdGRI63kfWyB9C AwpJ3XZx+mwQOKzLY/clMne8Rta88z4BvC3Elqtsra+UlhZ+/mQYCx/ToDiy couNWSMKOWvXVp67dqK3UTeCtHk4I9jUlng2flar5lvAFETp9PVHXbCx01Or nFbK2bhUrpyQKzmBqx/dy+QrhbSSNLUWXRfO2f6TCg6q45TP+LeS87aS829t ZDHMSiN1AfxJi8s09H+13eWnfPHdtn+BeUZmmB0Gdl/Krjkey49ENrTmreYY NVdWDkV1zQxTQ0RQEqAXOD6dFmKKWtBTHCY2gwzsJC/NlIb14fNBrlBDu+pf GuhWkLfhCO/bLbVCHb7bpfM97BgwIVJy2fJgT++kL7PQnvRtJ0FWvqm9yEia rSxPxKu17llx8mtmRZYmdcSD0YqVnWZj3RjqBuHLDDIdCMqLqTDS+AwYrMWs NdT2JBid57LdEGbhdxh5RJr6C+08Q6E7gaf1D5p7Kbh1L3PyxyxAxz/xt933 t933t933b2H3OabHh2wNv3HBAcOXVAgK8pEJqcYYKOYJNiRb8ROp/5ONgyDN u+vjxGSRBREJH9mxIf8OGRmL+HRBcJRm7UkDMyoa5YWtJrp4XU7yeJCWof/1 i92+f5F99Lcf+G8T6W8T6W8TaaKJZNht/zaP/jaPClaiQdmqSsiaR6rJSSBr KeuI0y5cuW0bSMG3KfWL3yxSP3wuZMwhXUcFb2PMN3FydoX9B9NPTP2+qTKo R1GvAJknSLs9TAbqSoMMD75AqHgyYggx4A+4x/RQ03+6IT1FsiZKHXAv6864 bWUKZa1hXyIErKhPKnJnHFgFFVQGzXvmQymgJ0DGbC/zOmWHwT9/eOpZfwoM on0gvgknsXeRuBDWCOUgfaHg2jF9mfcm4dphNETMQnLJNhkWNdNvcdprwFer 8JBqes1mMRXZ6Gun4tJpZSiAoUiQfRDKwFIF1V1GOUXuWkPTxGSmMDHZGwgV bF09LcNiyQFf7w/NfadMRgHp9KOjp8ZKOfOwgVlFySOu93JVQxkyC2mrVlrz uWfJmnX1LbyJxMZn1iphWV4m09aARTsuCLwhAvNjZiPYbUgECFPaWwicwhdO oIsHzlJS2jSts3UwkRPMK7bzMNiTSHE8mF8B3AaoejpmFkCc//ghVFylmXl4 HphmV1eWYBre+rbovQbhCdBY1aiUYIEKAa5JAOMm0GwTgvXBCYqTRijcF04l sZXniG8hSRFPZj+iC4uKgNLrGLbAeoGlhGDZAw9CA6T49hM0qt5HhvREyzhv b6fTGytFgw6fJBTSCRTrDuVu4JR2iTASfOVyq+VMm3NCGW5UCjPAKRWQJHiO SLPBGXB0cmfqRUP1TMpMgXLkO0Hu50Vdn0Bm7tJnmFRAfxfggknQAkUxCDAh bwEhID6BjQAAhf9HXY1twjaQJfrMnTmy9MgHjRfuYJTp5bCU8gEsY9QJa47K PBM4IDOTAWjt6C9De1nWMPSVwbtU82TJk8XugNKTYYWmkB/9zo8VGAa+OXUp 0MGwsa6tzCwQTo5JrndqnrAUkltzsVBoTWA9MKhKRbT2PepuL8zohwLjPuAl Q/WXMpqfwN4rWqBJIHzSJUfdTrML/crUd0hNouDSS1P+F3QOeA0GRqWqfYs5 QfcH9U1RPlIlKWx1rrHlX0kVx6+zHefRRcXEE4V0mIj79k6Mvrt84WDXM9hE Mnn248+fKCgsVOWUEvTzp7alSBPJZUHJFDgotUkS960cYoeXTE40HilOsTUF 2Z9iNDPjvnhQPk+SXVi6afLqzQ2B/HkCe6sfuafKdv6aT2Ra8krwzzyOrzd7 EdxB415gf+uq8jMBeS6ZDGeKPHOruuv9ih4GvmoYq7SS7VSOpZoPjFmAoGup JZJCGStP1SXCDbzQL9Pki6Wk7m6PrACBCtfJ1uyHgjploh3RnitYKZO7akwj 7WoT4RIQ0yT541N0ivKdIiE+IYp/DrMi5LGjjEEfISNESU4iXO4joukxHQ8d v0Jgy37N1WMgARNiWwqUCN78vfDb//oNbDnVal/ZDqQ69kF5K6wsr5aC4GEw 6CW/f/3K3DVCXNqJBl9JFf86V5pfWFz8X2ox/wdsm3++FJvN4f7l2eNK/7Sx XF+O50fz5w+vz8O9xfvecWt/XG5d9A5e1hqNa3jp/7X31D8XdrcuL3f3r9fW SyenS+eLS0cHcwQvn+uMBhcce+gFEsNMCOtjuCROXnUAs+tiwenWjHvWkCLZ sa2J0MWklYR9rmrCoxy4Rzl6GSDMzTv0JwoUTHDFW9qoasTR9JwT/x6VkidI 3sOWEn+9HgE0hwXfTe8qW6nv5utV6jSY+8cvGmkwGrYDcEzdXmtXmXTf33ut giBicdqBZfH3WCSSb1/AGySJce9UeCr05etevIDBkXPxwk//TS9djV/FB+zk uGoCILlXXM3SX/iixbeZ46xgcfuFhb3q8ZHFU2bZr64+CYFYTVjGt6ZDAvbX X5/6c7/8GtW0HTDBha+wo74uLi7Ml+Zw5r7OzcwFO91k8HshK9WDdZrO4tm4 F/1ue9++YpNIBTIFAwQekN5jfafWH8SzpZ2D9dH2+fz3h/Ob+dHN1WBl97F/ cbs22Jzvno+Ph/tHT0jlMmVPAbTgE/iaUsSQqhCqRJuSAAhAlohta8TRGwuI DUayLFx9ehb1BCrQ+uTxbn12/WkcfxNIGgR9Uju0Wq1saWCQEYPpaTx72KYo 7yx68sDSAJKk30Cf0J+8UKwdHvwSkc8Af0CE5hf2UgArxK13HjKpOzaAP1mC hvgRf37+yMVCyP/BRy+Wwl9wsbDI5/vVB5aB43EFO84rCSk6JBY5XgoK/l0C rwBY/yiflVpKidtqv1tYVlT+KtalDmCOecikPwQE7URo78wSFApJOZnIDGEr 29UG2pvsaPCelSDDAsBAYErovhjY5rjzGEl2GR2r1AGyVWh9b9HeZUcdQUCY 2nvLyRCErVE4TiyQnDjBNTM5896dnj1RI3Nk0Rg/61p618CsNc72tJ5fZWZ2 NYKX7CO178gTnIj/EDyH4nO9R5UdAhwds+fMteWyBZu/owc/GDJ3IzNtdqIR avafZl9my5/tnP+uyWlQ7bTVFfj/0TDQQcnjKExgQJEeOEgQ2omTCHi6RItz yIIyQRDuRrn6W0K+Uu4JmmTf0seP9SIPEH9ew+7tY5DdLHgK2z+YGaGjifkB TflL5ObRsQKq7fbEKzgXAVFZ32BWQqligPvZoYAoV7HaTZhuxlB6ULRBsKod TXgBWyEhHD71OkI+IRISbxK9O+gIvZPvF3UsDNFE9SCzmTMKGFTUdIf9QkRI L2KJXuwdHC+VF9bLZ5XZ/cpxcLi2cbx1tb1wvbh+sbd+tVKaO9gJtKJgGYZi nFI2jFZjlFL6dfBizEY6iwM4xNBHTv68Hw8MFxqz0naUna27i67YvsZ5G7jh NSUXm10lmB7ageP6R1FwS1vElv4GGFGfk6doPGmbvX1eZpiRkmvlAxhSIez3 w7HZ0rgqQhkHmwfnAUcKWYcoMs4rB8Vq2IgKa2okSwtUR29tsh8//p/K1vrC 0sKKRB5Mfb5kYSYpBYQARgzCanZu3OAPIjxbekIH4SMplTPFlRh8A1TewlEI eAC7lj96B14sy7rYBIo75epOsXywbXJYfH3heKTEFGJvMOe3xM3n0fsAehki uKk60VPJQ1gsLS5Npaka8dvyIw2VLTs+LsSjpf5uVA6TjmogDtTrxfsYkizK JdOH9OmNJVeZljv1YZ5vJ3s1c4z5kH7ArUMnb8uCas+Mfr64OFf6M8NXr8vw 5z80fPvLHxn/+9xlvfH508Vetd37Xt07DDeuk6fF7ZXL9efm9epcqxg2z0+i uVGzU6zVFvvng6Ol1ebJbqlYvU2Km8koqq/EawvgFDvZuw0Xd5pLG0fx8vft 5v6oesqE5EDcB3ou3fTbeM2Is+FHBr77p4BzUeBbY81JYiyl3RnVXsCqBWA6 l+QGET4GWSBZB9PQDhV9Mula3xwcMvvaxr98xrSfbx7OHPtR/vnz54LFzQMB /t8SQhRkh6+dRQzh0QCBeK072gDgDFL0Ng4fEAG+uZlmGvw/a8SQ9kvQyRh8 oyu4EQmHRJhmTUP1G+Df1cXd0SqIw5SQwvB2wHY+k5tbo8kitp4FC2YShTnJ xqPLa/7WTtTsAi6YHEHLfQmoTnBfEeKvGqMzDIcIkhOGMLyYSs6zuOLw/FFB g90FZChDcCeCVIvqBnVwskHCOUC8BkHcBvg56KNcgg7KJsv6CUFOvEmtmZ8O TMDUo95O84Z57pKvIouzpI5Ys0+4SGdQOkLea1h+MeP0/Aucv1ozvkkzTtfy yW7KlJQKVI2zLlwNYYYVFaDceEGySrQmWS1wYQuHEuzJ8S2C4N1qIiwYmuqm Pe2h5KszlCkEyyNyoDBRDAHZajkhwQ8Lt9LAY9cI5RdPrzM5dgu3nOxgI2Vh 99OzyZxFJgU7LGhfk79p9s/n/YxxYWxBcutAtwHtz3AGvWkeBJ69VvgEaJWD hKD3wUCFncZs6589RQVBbq0DsXVSNner5Z8cTLvNd1HRSQoyrzlTkXXcqEEW 6RGS/2zaS3NqJSD7KI/RDmZx4iwAMRE4tlO7xtOR+xjlfhFoBiVtSVyCjk8A /eTqSNHdoO6wYd9hunHW2jYZoLPAzTlximCbOkCdpEJhof7EF11u4CFlSXGA Ub8humsyA5qEEpEJwY5+qFGxWE2GvH2qgoqy36d1AnqtW4RSBElnZIGDMZXd tB/Da2z69xxvWAwi2D61kFOwKUwM5HtqtciFJk+hAoMxhEOOIVRlRRNmvQbL ssgRBnajizj8ul/dPz8+PN8/NN50h1/5d2IcW5k9P6lcLx4dzs/j0/Aau92z 9qp2ux9gVc7vhdlA96m4Cxrw7zCQuX/OzMyYX6y/aWNXdqwVFh2AZM2rWrFY ISnsrItCUk7FQGe3CI7bdEE8TmoE90LvK0c1JTlQq3tj4zskBG7ajfZqcSlc hpmwHfZIIfU7jtNojtqZzVV9zr0x0Zv9V23bhEhDvMmmmKetbZ9v3lDR5KQ1 QZJn54c979PmmPzJo5EOL03Y5znhpXcfpI+dDvnqRtyMsGNkBuNvFNH6UFxK bYC8xQ8NnPPkjfAQ1in1S+Owhdkzw6JMMl+8SWT5yzJ4+dp/ae7ubl4crl0U 107Pj5efXu6T3l+zTNF47+F+uxYfx3vD+9JiazcexfWd1mj3sRtft7eedjsf lWm/ftWYdCSx6n8dfnSQfzS5RtglTxx4ddx8crvkazqyruQIU7r3KIwHd5ZH EMp++FBq3tt0OuoErdzPJKVv61roy16HbitlhIpwoEOiFmnq1iCJAO480WV8 dYzfdbp6AJF6v05Y1vzEG1kWmEhvU+ga7qYA2oSSKkDrHxQWC/z1XNRfqxgK LiqiBKdaLGyKeueV9vCnu0G3e9tQn3pDxJ9ZNpETHshkGTi2PL+A9XvlazGZ LDd8QEkHadVT3vz5M5P+Td4MgksX/6eEu6S04g2mZQ9ieID6W2PYR93yLZPI nU7JnQsheBB8m5IdOTV5v5JCDVxklhWqpyzV8kQDAizFadYnYvm7qZHGfqVu OL7lLZeGstBjyPrN00CsjUa6Ql7X39j8pCh3UihanvToXR/pFfYi6bo1hn9O e9lKWQTGL1LQ9N1CbuDxr2DKVJjOvpnW+0ZKDqHgwjkp/OnQY4LT8cnfdUDi DdOIMAANQn9gkkATqDblgKkIcmVrfak0W6LQBRU3wzhCcBcyX5MSezSpOlzL ZTacfun4GNGVZ3dhoLqAF3VguabAzWaWHN1+doYisBsMW42YhbSpPMYAntsZ B8U5yKumcKIM2s5H9w+TiuVkVdwPWYrmchVoBA2HrkCTjqDgBZ7ylsevCinu iHARZPyrqsMZ9nXvBFgU2rjrqDjP8oSXmURyXcDbnfy8HxMUY7sWE+cKvlSf kHF9R7G3O11DkGTzv3Re/c9pVNwCPQCthOeVgfkLexzpiKdUJ/mgJYK+vFR6 GWJ6p80Mn0Iw87den8k38+eDxhk+Sm+uVf5uCGK/VqMpwtqpSmdnrcgzR5F9 LjDIzxszN5DZN7njgirJe/ISDugzvqLwzPUUqLfa8UDIBv2Na1GUQ5DqY0KR DB5996LeBoVWt1IcPumWsxRMc/OTB9WTKaWkkwtXctuIGcySOzWB6nUSzevE KFpKPwwgEWNcpNSg+tsxsm6f39BEV++NmOkAPiteph8B6Tjv1ujcfY9RVLdx Aa5Be8TShVMOjIn80G9PvW8DTZx5bSJJl1x3a7/gmcnprFKf4dV9YyiC1GG/ oRmgQaYjFCyhikCKxstDOHRBU9K5BHEjfbAMlwhMTy00iY8U6gU6qCg1YFCk eRcVur0QHA4yAUL251zCzFzR7T4RgBGIot+trOP3Rcp/YNryFHXlFrui5DP9 FX9B0Qoi+7i6elg6OdzZP68sLZytrRwtrV0uH9+sraxvbB0fnZTmVisncwdn s5hgzC8rUaGuMadB/DtAyKkmJyUOQU++6ovJanRyf7P9Nh0sUrdnoN9Hh1PO Oz8D918/6YNTvATunKg/3sb1RP3xm/PpKdqn8FVaQafbU3Edftkrba9srxwv lG9MD34W/kVflStQ81t5IM18zFOwXd9p4qhtDRsSzIJ0HNLcCeQO+aCT1Smv fcPJLamftrJnykP112S308aW3YoXDMwlghLS93iqjdB0VmzifjF7xVKBtFpk rZK1s9/ewboj1lugoqvX5mfd1eZJ7oGJgHHZNGWs4zTOrpobPEbh30cFPn/D aJ3SyHQr3C0G0jRIi4ewlxTcYLsdvXOtvBT1Oabau0bCBoWOT7gKxbYQPp2Q KffZthUQxWECVIv2EBi3hTYOtJfPPxFYqE+ZHszjFGi0CYC707YU72wr0GbN AiLpIW3w27GGTJ1NJjyTvJ1HP+3QbEtEIe0L+CX2xF9kMNCu/8/R5egC/j+g xpHLWh/4QItpEdEIpqJ1bH0AyEdMT7uYiQ71urhO+oRB4MuiSg3Qo0r+rUb+ JWrkAwOujCNuwpI+XA5gE14zqS1epZBsAdFm7UbL+g9ZWaCkBq+aINUNQzi7 COHzHkWAdv20hMwcn7GGWUD11/BAgqU7beFP5eKpEN+6OqUvA7/31lJ/f/wH qwO/3J7wHoE3rIk31/pvYyPb7/9IYyMFksCXQh4sgr400jlNNimyXd+XctWS UcFAPcLobALBb7h+LQZdbqEeedTQtC9qxitqfVSAMDpUBRkFkZKH2R9u64KS o20dVT2IkS2NpTBd9LPs+cqxbjLOtoyHFJ2PfIJ9erCxFDhWmWsQwIvGJnD1 4IbLPjPs1alujk24zFVuOe7yAsgBoSuRwzWPHzweFByOVeJ05dmE6zqVuw2G xqG2U9Qu3HzhuidPaj7bJ35EC5fHnjGWswWeGODBG1TNEIGjoejFq9+Q4kad gG88vzZC+8l6vCAaaAY5b4J9IdX85bP1nbfNDCz71EGQMVfhw5QbJzgOe6aw hT8FQrfU+c04CIzpyfZgP9ICA8qaOhAUbNqlfTph3axaObWDski+Tu56Gick ay5AQMtVI2dS0SUdiSOscl/7qVr0N8oVgmx0jhPQixFcDpKz6jLzctdhK6PR BmoNWyus4dFZM5VOiQ6NIHX1QCe/wLtuVj9f6bgXeRny+CKVHmxHJ+7sC+8O P3HH2/ZONko21iLVcZw9HAjeBf2V38did/hUYnIUk0gahRKNPpLrdsapItt0 ej+D8yAsrdpSzcgRURw8x+pGSmMWcnqD4+bF2vfgwIbJE992AeaA2LBxluJN 0XqneCEFTcKXh9owzRCFRorRC232nHwbpx+UiyJon97+mIxNPLYG0tHdgYFW yXFbR/W8W5f2ss7f8XSg0AeZ6cToZ/zGHiRcSd4HIDRPMvetAdViwl6CZcUk Kfi9BVhPSqgqE4LqeZy+pNCcs31x4c9z7SQrKqdzJhAai4ncAnyA/igTST0h 65nShhJdz2pxYbwTB3c6AJcPRj1N+ZjAItPuYHUCYgBzM4WyhxiEe26u27ut bveObGHVhPRcG5cMRkBFpngSw04qoeeufDZ3NxOU/PFyKMzvs3Rl52UmYVgE D/aFZM1a2L9TPzXxap0pmHBwRhd0d5IMgJqSSl8ZmSvY1UGkhWj3hL5cl2Zl Nr87Yd5OZmbKk/2kJqt0R09m7GLzDUyOTH2InTC0q1nM65vUaQsXBHcVhgRo 6pXgn/evkOgO5AegeXJuQ5iY5IkwK2Brcnf+4JpkZ+5dy0TVwLxUonZaq4It Wjs4f/7n73ip0r/ajDywD1JrPhMs0AROmvXopRf3LcVYCsGiCCA1sp9EYUaa RTz4VeuDvf03Wx9s+13rs/AH1gd3JBWVIaxByg0CWA1qDKAQwkSo05OCK/cB fWNpmAXk7FoahU1sQbQX94PC+4lCWlkNXAGKlVC61J/GRB6LNibuAUeEAHCn dROdHmcrATSDmZ2EWzGPeAt6BtuF3u9HDbVdcSC0gY1bSeq2JL2KZU6625Af yAumTV4lAWmBuXnYXNg6K/OG/pRa49wdKOGC82NVezpSjtqAW9BdJPfGhynS aCwdpP5IneP3acCivIkPPV/dlSfBx5DSbIHyiwN0dU13lpMMjNBVPXTKg2bR J1SqtA6JDnrNJWSYOOgzvAUSW31mGE2dZ5uBAVYjFz8FebQFst/rCvdORMo1 DgGqx6G63dHRAUY8bg2sroFUZbfq+M2lgKG+vQzw1M+flNtJsBEoQRL1Z/Qv BVCcaJnc4X2XqbFkOvWUcIij9hAB8CwtGOoK2G4k/HlWY4jAh7AJ8GHa50Da kX7OkrumtRxoHxuA2MNFkBbHebPpyz67o6fu0ghBHiszzT+AmmYyBMQPBoN3 7Etyv1hV5lnAIssBreuQAy1u1CtQ9+mVyam2prFM34DPBqQ/e8Fn3zs7va51 ot2Nr7Oa3493pr566PEsWLWcxP5ntkWR/UTOjQIWM14A07iruFSbbxsJpdAx d/P1XWcMhmU04FTqC7T1A5IGz+qPb3VKkI1cbQQ02W4Ns7brJtYnWqjxTBAq pVYHrJoUQ0306SPB4c+Umv+B6HDhv0d02Ha0w7Ti7KdiOyLQPh6vlTKPdKgy WyHB/hnEuRc7U+021LfEo5uwgqGTUifUMg5e/ny28y9OYp4YuaJfIEjjxo7A qTs1XZga9eNBZGIw/3LiPjLfqcAPuLuhxSlBkZ36lxXuYviqTLiLsZR+L5jX picGxN7ClE6/Tuh0qoGD/YOz3dLixv5Kaetq4WzhdOtmfSontEUfgbdWV5av d7YrZ4tLyyuru8cH+zqqwfX2PlcE6TqhAXJgmWTRMuxicLjQYO+yXRVkZ1Bl s94k9CyPBKFfTJLWXBPPTcavrnTh339xANqXavMXBqCn3x2fpehrkcK0txij tdv9Y6dB9gHaE5kst8l4M5L8iFQyQ1/Kvjr1QJKEJUDomPIbSaqLELpiVR3i IcTiqy47jIwE3HnZGmzuUr6d8XXBVsxEixA40DLhUEumSZFr3bL10BEkv6qv 6A9LONJOd8Cwz3+HUpE/LmUz2wn+P7T704Fl0FYSrL62izjmcWcsz0bcT/Ic xZh1ERgnOxjvnbGtM4kEY8e+Du/hPEcJ59PExAHsxo2DlPNeifFhTb4MFMz1 wUNKZTfaGfE24HvGhSLKIutdLDsnBNgxiu8PZXBKANwYYjCRfQfWHl7/71Ef A06RkghyhJ7iPO+9tgHakFjUIjSjaGyK9+kTxsl/Vx/2wZZWy9kKm786LYi3 vz4N/zZSeXbzYn99uVi62R/dHN4uHS0vzb5bKucJ41z8wHdogNBw0XbDgPsG ZW+go8xq8/aATzzWkQnhEHMxliYnKNlQ9PmJr/+tlMq/dcl/Q13SZ9D8rQh+ UORQhOzPqnsTIpIeHW/EEiml3cWmnEbuS0dfM5EWgo2ELr301BXMzqwRMAEB tIaGLzEXo1+MYrzA2mFwi9v3r/jsMA800bQMpJtiPJWedXIOEA/en3ng5APM FAylnqdzvyUB4YFj1ong4yN9m3bqa/0pJcDtmJR26us2RqEyu1hFGiYmsUga iV7IxWhhxsurTMPRqfME24XB0zyB6m/mxrnX9d/4GU27OuTZNAODWfPeJn8r 2/+pLo0lJGDJvYbk+pHryHsNadUItjrYdCZXRZ3/lPb+zmwexBWMM8kxfHlR +kfaLe8mrqLgsFCsDHVEjlRwek2bP0R+exYSGMTNpiihXAVgzm6tq+UuRYZ0 rMfK0dTxCev4tzLOZDUDzW63zoFJSqfRNg6ZA8bU0VMeqM5TqqZJDyKsGLRB wGCYKex0R4BBazvP5bM6V8fU8nPCnQYI6UeZUDTZ/PWuybAY2/2EALPknbpe dkxQrRhI2lzY6HoE6Bk/g7xssFFM8PldJqy0U1NTuZSQ+8YZBjpZ0U7QDaxk q7zkAyRpK2xsHmyebf4RFAt+899fXr5ZfaHt23o2Xx33vM0TiLNWml0ofDrq FnhAnzWeKTvleasSa5G2d51943Lep6KU9ZiwQFUDZOWb0D2sPYOWpsP2Bmuo y/nFE74YHMvBzY3GpJEaMHfbRixtU6o8lUxRp1KQDilYisnT/Acxl/5ROMOZ ODQz8eMfOOSimRxNHu/4frPQMehnoNdMeDrIC47TVwg8k/Bo/KHvGi6k8Gui pgtfcDNqoENakFNiiYG7JmxOWFtD1xC41rLh6TkmdZBfAGkHSS/0GtpDcRKk I6lpX8pfVM4DnhvUPqbuI9WxvqMp/AfX+oj2gIIgczJTgNVomBrOktR+Y17u giGAAugrFzram7KTHw2X7AkH7xkxsj0ReWxbfbJrk7NMHpKQkkj6SQbVmT7s R3T29CGY+LnUh6goEXKOkYSV721qgWAmqR2rXiHTPKBvB2+OcxrJf9KAvODR Zy2gOzAgeOyrINl0gelQP/5Bx9qF5M5VCFD/SyP0dYSH2/4r5yj6UStJlxqF mJslgiUjeSSRhzO3xF9ssrdmAj28dKdqFrsI7G5ShDLJfgDPj1oLboXAq09N pxLBxGuMoOXdXkTEagzNpS1OejUIkdmBsiY6rPTVJyWkgUVJTAFa3qZ6M0mD MkSbucdS7StN+JNG9QuEsjOzFnwBu2UlD8pAA6n+Xox3Dy67caWngNMnOFdd wfoHwQXyhOovtHxzeYwFSMXGg24NxBKyYxOehKzUwjBBQmjUMRstAvip00cD 2zElBW4sRFcFeHJwfcIATQOu4PuWjlL/JmaOjVVNhsznQFTDULhAsK+ZI+p3 r9WQL0TZoZRW4yvTMzuLa2ZSBSRGZGuKSmNIT75bTE6d/66wXgyYRMGw0khQ TH9FQDER1DaTeybSNeAoIn8YbkpmO6p1+0hEzGwDb/dfq/YGPJarnDIsFnhX SUbx5Lvq7e/iXcVX066d56u+JGtg0rp5hLZY4NG5fFwGpta53gXRM6sUeKp1 SAtO2T/GQ4kWBEYDUxnYYYccxFgeAyXrAWjGnKMGRyyuQZYy8yCEzCQP2XFO IbRun6QlslFgPMwqx5fj7SlgFkuF7cBZ8YoAGGuR0iBhYtMEyrU0XZ9eaHuU AUv+VK0e6YXvM0Jov9HcMyyysyq2/aZvWb5PZRntt51gs2E84iad4yd543Zu nIM83HG7kt7Tshmtz7PFBDbUveWPDvTpQCD3JD/hVqIKesYnRhII15G8Zlyu kDXYfAsnZEtu0ZyzmHdCHshSw9cMATOmXNkDe0IR4YRrZGX5Al4+UXkJ5JUH O/MX4jlsnSyVV3aWdq7nlw935ubX95eXDtZulq7nzssb20sXm+cnm5uVxZ3S fzyeg9V/VrVvY/jI/NLs7NtxMU9XBuMe9qT30B10i2EvTo2Gm0MZlGlPP0A+ e/9v5MfP+bHebfWUkJzK/PovTzdaLGMndCRn1cBDn9cFeUXSSGfgM62v6EV6 X7/U7RPCPE7oVzsahPBYXifittqLiedz7kZI7TQJlfAsFvVX8kKfBu0VbHsC aepCERYAIVDhkG2XecSvbY5M9JvJsZ/MGX7e69o06eQrZPiOCSxUknfutR5B x7bLBjDWLu5AYPteIwoodVceKbm6H2m67ApLQsdi9trKQB/1Hgc6sE2xmspa HAn+J/roBCsv8DtOMGsPnoImhVzMODa6DZNzBr+2ISAdhy1tyTlOx7Tt4Aer yBqZYZoewQOtKPkKd6obd78Hv+MtJ53mjdUvOOjE1AAoLmkVQ73DKg3oFUZF g2IO3OG9MOG7l5U9yIRkYvDhfSuu4aMzhcrm6fluZXOD8IqJuBs6ZF1S0M87 nE2D/g1Gv2FHlItTRpO+BkmL6apLMkK6nxir1ESNtddnUuEIFiCgYholieXh sRWk1rhINGT2TpA6Ao5nBfBbEreVShp2IqcoPms8VsUZ25IEAkODplUdZ4eh olDT7JeelWX5wbNltCvTsvuEHHFuMjDPOfIIwnwwhbCxAspLhNI2XFJlIj6H fXDQUGUm1euZc0KUAri2MeqSqZJIeNDmRzJOgCTTwBDKd2B2Y6TMNg+mwUtc f0nw4wfePHGzSPKFWUGAc5sdL0pGywX2b+MWAd5adIN8mvqfQqs89T8HgJMw KILqRJlI4Bypo3NkCl/hC8txJE19nubWSr+itcKUnvup/1Ib45/w33POC/qB ItIN24999vl5pqlz7811UK25+iluFa1Mxk1b/XwcPWV1z6fBGLOequW0UolK Wvm0vJb+4YmQuF7Gr8VSRhNtNak5IINO5yTAL0/Ha4v9ysLe8+z2YXQQXi/d 7g5u+/PHlVG9sVKLb/cGjcbVOKy+rLxcq5HmpyqEcQud6aY+Mu3c0/dTFA8k /C8HnuWpI1dEyLr3Y2jCTmxnUbu0eaaFOUVXCU9QSDCIapP+5ET1yqoZAshC txfqFGROuZcEJF/pO8JhQXUasNQrZoYPCxSB4lv5EzllCJ8Rnvn88WFRNort vMkfn4cMh2rg7arJ9Er8ZhYJQq6E+WkPGhJKoClBcVEjb0HSEygo4H2iK037 HT3lqfI41i0TdbBOofTz/BVA19ATcqs+f5sMe0AMHNWd6cmL31rpE5nAiVID Mfz5zpCJUQFNtkiGOYy8R3DTSvknqCVBKKW9uqzbn0ov/sWxVUQC38VpjXX5 rPg6BA4znRFosh80B4RNc4rOwGEHnwfsumkvGbZJ8vE7CilLiAYk44EyB/Fx mpSDlEcvWyLVaimdrq8UoyjJ0Z9cldWfWZLuJLlsLaLozMdzYhmmcv4dsQzJ Vfm3imbYpiGc6jcd3Syo/BtqWhICMH80I98+T/TfutI+bgTimBXCbeHE0tkv FsRo3asnwUMmQ0bCM0haLh0xZcmZKOegICiNCNFlCzvvVpf4RsGuEW+1zH2W xawH9VOmPwvcw1mr5O3BW0aDanESS0E42NFlQaqwnmQ+VA/djnj7jKvanAh/ xJkBw3GBHGy4jkHiAMta6K3Ic0yYxCg0MHdIrUnwj0IVvd4GKzExV9M6zciu nN4f/0AXeSQmTPITIT1hx/tdAvQ4FcXZpGNqMYGfS/W2UoW7w2aB7zjuZOfg a00lJDOdZSFbYuo7n8KnEFJ/p+iwgI73WUc5fIHyQD9Y0JBOQVAsIGpg+nnJ umB3vn6VSKaInUi4pyl1SENuQGhojCAFqJ5ZOU/YIiKq2skbalosSnbRAmid MqD9M7rDpk9uZzvdjDdDOgwIvxbANIhRU7BPXccuc/ff7joDE2P+NkYCJ/R3 0gSTiuWZYVsle/8Ua6Ck1DyT+MJfaV2diJJgX2KTeH6EWxzkDaXHvDfqIqPu sJ6dHj3IAbN+mJKVUCKcLjEYduhE1T0Dxy56Fqjbo6iuf/jQf0yJwIQL9Yci lT8CrC7Y+WNy4khWbHawiQiDIueDSIYBqW3gw9tC/1CixIflLQL0YdV+2LJK CLg+MyaRorEVrUirDRaiXWjBveW3uh8XLDK3fdvTRm46eRYEJPxBOLQzXrOE ++ejDCWkEcqmYwgqgi/pR5l7OTSU3np5jZeCXHtp14XvblcvBzbrq4XaJAYP RQGt5C1N/ShPfEoGKESgXoKgKsQDCOtCXkqUhnkp7BqTHRVi2hyOZiaeH4ZY ZTgiFxcJJC8KFRq6VNY76J2wWRGwK9T8q+SegRd//LgnVzG4eyE+q/2HiCvr 6kp6yTUxu+V6dMJlln7VQchFLRugkESbLOwLnfbgT+sYsvidimbPJ46LFEL8 LUiQVaeNf3dMdMg6dv1qptPqzu+2oyD9WsjP1/rjnrrO+mHvgXWcujoBz7bV adqaURqAskRMvj+PyLIv04fPctymRp2M22oH9+Manv+7x9GT2nKpjZaa+xgH oPO2+pFZBOPNvozu8Swjm+jy4twytA8boVzYu9zXoQeEOaGAaqupvlxuNdW9 NnhoEyXd3VOszM1P0NDuxmfLKUAbFl9ip7WQRNuxcKgWiab42ZfFmmrqamZx drWwDn1vkAW1/qD68NluoXyNbd5Hds7mM4MXFagFPWrHrtdFHdZqYVvHJ2e7 x0flA5jjmvq4Ptc4ySebh2CnxJSZ7e6hmtVV7g62CPe+bTtxkp1cHlRHAv9Q u1YZvj3I0YOYMC3IwtIKpxVgY9AByUUDotVuF4u8wZ9sLiN1ziE33D+gf4Bj zB3VWar3g4dh+17ZdB1kTKwNWxQq56iD+t63Y7DMiodnB9V/ffqH6ubK8uzi Z9iwwCS+tKC06AN8WF0VXZAlbhFcnOiQRwpgXYsuPKIT1qZsDhX7ZPC4kkCT FG1s6RteePZlWYmasRr9WHV9t3xUtsWIEGS/QdOADmtE40ENJG1Aqg+Punb9 HjVO21ua4KQfXWdHVXRGScO+2/74gvHHq56LH52F9efAuue4SGmamI/kTmNH 0h2/eefuXueegwlOCwgbh8Xx+uZ5fDPeXr+n1+vltT28c07xq9+7+yc8u9qf iyO2j4FaRzhutHofHz40hdAGu7ubOxvr6+VRtVke7a6Vm+r/zspHa82n7w9P 8fbqaHatfJpslbFLQlYn2Oq8TZzdRVahlU4epwKfcumKVMSIrCOC0BOtA1Hk feXokXbtSOqBnCRdoGb1a4iI+ghogH/CL9qKr8f2T1WxBg7oID0u5RwmbqrF uLd++bfEucJBCbKmh4KmflVEE4Ojyj9hIKn0Kat45a2aFH9PAn3a81jYqLDa GXY67E+WBof4QcZVNA4Y2wRaY1dmwT5rFSgRdV4pzIiOJJsIJnpnta4K0zA2 SQsBbSZNhAuaK2h/kFuhumXXa2ZchFQTwDsV/EtMQ4Tfkum29xvZGgbhjEwB kb3C64nXmZ1vRXIET+pUtXiycLV3elu53luvnFXP52aW5o/mN6fosOG86PaN FdIOOx1SM2BwyUMI5qHWwzi6DkwvOEq3rNPidwF1231rkmp3xtvezG6WjguA MDvqN1BGQYdRGihMLnzH08mChRA58/Zo+ZQYc1xmOnvD8G1pAtGRtEsmS2x9 iJoyB5qLClItvhe8HYKT7TbYD9PubNHuSFE+sEdMILw7EZwiJe1aYyzyJwb3 e0YnTgZQNetkNOLNDY5+SHgSGzm9ISF/lDU5Z9ASvZFwBxQlU61MDCwnDYT1 rXX7jOEMuUygRSFiBiMqm2hFgmWADDqkDg7ky3KdfapP4l9BqMDWMxxNsObR XUejosIO6BrJf4KDuUcpA2zzlMKh3tFCHGVs8gACwDX0wEDCWELDZBSQNMU5 AROE41nsdGFjnBFoUNBBiqk4AoKQcR+UcpQgsCnRM3KeA6GUvr1HtFg8oVIu uMxILPb0H5iuRg4jNMouEgCVkgwKx+5zHuZrCuVzO4lazxChwes7debF7WRu 8JBvbe18pqRpPMfojMLf0cAU5Gg5JukbHgzo1lh3Rokl9+O2sRUWlH4P+dzK TOgTZ6GS/yPYgXj90fl07FplnU1sMp2KpI1hT0YwnQdXh9cTmhKdIY4Kb8hv fSmAgq8rDViLT7zmOADKIc0T4zixA5pwKWYKdjSwjVU4b+C8UgMw9+dEegNO fA5Ch2KQykfIRy8Vg3wQfI1gkg2sLcQe0i5NyvHB/cmESVY8A0KYRnzrBKS4 AYeHDnsmJchP7cEuJzRUbHBmWKjnaKxFLKW8Wba5JDzdkVOZUMNg8r5l9Bit Sqk7fFgDnTSDFcsalRW6v8NaVp2dL3ak46lwPq07hB2F4d7DFpnO6FWBnC3L hwnPYJabuFY8N1euXw/OaEA8ixkIrk8YtU7IVwXqFVT1WHv514xWu2UB1ID8 sNm6ajvfMDsrhZxZSU9IYCYklbSSb25K1UjGtXr2zk6gmTxVdlOjNOknuUuM exTemIIzPJUq8ktqSoRDDqUuvrXDPlkPvesoDSTaCa/o45eex1TSXfpY03s0 shzjn/FAZBYclppMIPh9RQfbm2eFr8lg2Gikg/I6QfwXMhjn572lUuUgi+2/ WJX759zS3MrKysLC8jxksMX1f06ptnvFfhJO/Rdizfxz6qh8vLm3NVfarJSm /msQNumRqUz8//et0y+bj5ffa/Mrw4OttfF+uDj+Ulu4HF9fj9bPts8f4vrl fqO/eDC3/hCubMUnmyPoysbL9nLnUs3u2kH169rSxUHj6Wav2zy5r7XG1WT1 cGM3Ke/ujXY6r63a3uPo6rJSajWe26XX+avlzae9nTY0ctNbqLbH+8fV+YXW sBzvV+ZeRo350tH1Vre1075pfK3e79zsDS+fT4fVhfP5+fUva/fJ1evKYaO1 tTO38TCARna+rs9tLsalhYVm9b5+sH7y8lpeq309nT3auagedOe+h93h9e5z 5+VqbeX4bH5/uT26fEwOHua21xeft84e7qGR+avT+aX5/lJj9vikEi58v9x5 GN5Xvta/7n1tHR0/3q/VH7+vlveWVrvfj/a+lEtXZ19u1vsXYbK5tzl7vPa8 AY2Ew9NuPB493K+sHa4tfznZ3D1KTp4Wv66cP4dHL/ejf/7zdyfVwhVkLL+S rADzCKBMiJIAL3NEwp2zSTUizA4JA+Tf01lslscQna5Ly4uz6GXPHKfUzl+j 3rwXisGUyd6BL7K4Cd5R9d21bl2pqHJ1MmUMJCKcDqO+84uwIStxZPVUq2La pwCiCI+lBy3nBFzfwBbvZFmHqCez0DP4OY6Ig7zAMSl/b3ItmJC16kqlqpfJ qn5MAtvatziSNW3xGJUx/S1yoEq4nLsWkE7t83TyHWOUkkz4zpNpD/axk2BJ GiFbFqp1jjGjXUReB2NAmUp8k1ekWgp4o3VAheiSJtAdcZXoOK+uQBfz0mG5 o0buoL5A/5NLDLDd1Ect5c74lsmRbkX0dtWsPcd1wPuT4cpxAOIB7FKCLhD6 s+3nsMoDQjDpgEIu0f4EfYtfMG1KVwA3qPOFFCiKa7xxvNe62+60gzUv1ooX ZpWz1UwGPSkA7KoxGei8fyicNtUetJIpNyxyOEQYxLODquMWflaGkTYxuU14 mxt6HCX1VENlDLLWwJreu6xmeiaNyENF1YRpLN3WwGqpF45b3bAuDYSDVAOW hZXaEm6ohA+MCZWcyNOH/LQvZoJNFrk9UFZPnFMjZaNmN0mqkKigWCbEjrts LYIJVIizgLwe5iSikyCwjw1GPM2ujF7AcRIPMExba4FrTPthPLjy4sm3QhYG Js+Tzs7BiKhWT8Jib35loZg8hOp/7GfcVP4iv8KZ9KkIxJlv1OijpUnEoxlC Ctp99BA+x2rG0DSmpFW2wTGyy8cDhNp0YJkweueFEr61ppN3gZUgAXkR2lWr USK5qJpGRCxLOkhI3+LhseWoXmjEzWFfyn9pFaOWWjVlGJneWWBKD5AM0OF0 gAkrpVdFB3EoXUQuB70ZTZVyRtBYlTdgnwMXyTOkVUFCAtEcpah87Cz3MRgu TbL9SC+3kuXdSh8Te2HPARoM7OjhazHLHDSjjh53KIR+ow1JsVJ4CrQESjys UaKysYd4/0haYsRcN3p8+BDLRrSLKJ/E1CrZANB61dUJi1oNTkNBSWjuVc5w E2XJBSJCFKVuWxn16Hr0vgJTY0MUAUY2XPE6+3Og5AMy71AIHamfk0E8GGoK vFE4fms1Amd69zO7hU4bcajT7og6w3aE5BUP5PBJCJnB8OH2MWTdiGENZjh8 F6bvYjGMHfeMrxoSd3BEeZmiZ0nMSBvdb8GlZEgDbQMa97s6fXzmjWBwyely Xf6+M5ZK3pILQI4e+bKtLdAOn2TjAvqLjv2Qc1Tc5YOHyPiBE5czoFLVEAN2 8l2AgB+WTr9b3JiJo0GjSCYj27RFyjjH3KGzbqER1sBDTQkQWIbGkfkh41QH gvGmRoV8iW6yQVMJLHCOQuhL728sv4r6zDYhB2ZKfnYx1nfZ19zF3aThBNkh bQS1THS9Wxu2tQ9Lfyr2hkj1fjC9CGKdAPsJZJEDKpN8Zs0df5I5M79idoEV 2pNdr+0PQNxs6gCyzmRO0puHNxYvrRRGpCSB9rK/aXj4ya2ZsxI45Qb9bkvv bwxrwt5hcc6XUHHYY1YGg/IjI09tloDDXFoa0Gp8S707iYfKsOR4vUFsSn3L xrzVjGCLduj8swHSwYme6GEMTEwc0SRBhLZa/nEHnyxqNv4j1rOfpXPodT66 eiMDBfnzM9lTcTtWClmLXWUQgLOK5FJlV1AdSjVz07K+UmhhOwQSb6r8b1J1 vCvV1mnMRs2AodkB4eaRy/SuQhlTe8fVTeOGK+gEuMInR9ZUWfrNz8xD/yip bgWGTRA/qnN+padSpezKT2aLI7mNahUS8chA/fz7H0UU4Ywa7TTjLJUeptlU F4rX96ez1WY/adfKyy8brzf7w4ujl71ovrd+PaqXo6WoUR0vPNQ3mlurxeeH 9cXmY1h5MnWm8dzocrhZqR5eLpw9Lyy0FneO+gfFtfvH28763kv/dqd8HEbJ RnzSKZ10xqPRZqM5f/S8unjUKZpGorj18P2qEl4WB3v7m4ePGzvD20Z7by2K 2jtHN7sLc6XmWueqvv26cdEtlerP192X+tL2oYwlk1809R0Bri/qtbPb4bi4 vjG7vX9xsN3b3K5Ulp8W9o6Xzp4GtZXDzZ2n9aWj3a2r+OHpdum5vHu8/rq+ sWQ6dnDYfT6MO8fXSt2sdOr73e2zo/pe47K1sbVRrZWTlfXFTmk8Vz1bPz2p vMTttevi/Wh+tRjefDeN7F0dvhwfjE8eX4cXzfjseH1t9/lgY6m4Umw/bz1e 3TzdRlFjYzYcLLVPF79fzJ/PPd4MVlZkLLh8Wzuth/rZ1mz39awVb7wcrjUa Z0vh3sX+zX77/n5r7/jiSN1aq7X51tX+2vzwZf6ofH+7UaqvmW4sx53e6uZF ab572d9IeluD5/XnjdX6Tf+qWdk/3Ok2njZ73dtq9XntptEc7BSPz57ur2/P vg9OtkwjWwcn++XR7N7VYm3rpNNZOC29bC50ivXTZTVB6/utxdXnm4Odtf5O 9aG/Ovv6/XWrN1vevzpfbDyaRu7nmuurByejZKtc2qov71+1d+fq/dPTzYvv q5Vid24FWl7bPj06PXo8vr14qu2dxWvtzd2Ls1vTyP5e5aTeu9grt++bnevL sHFw+1BuRPe39f2V3srieNjfvNha6azvL3aP5zdP+t/XlncPFs6/h5sd08hi tTU/nH1ceVns9osv/X65e/RabNaPn5ePjxo310tHW92wON9Y+b46WivvnA9P ZVHSyWtT3xFIp9vsHW0+bew3S6XK42pt4+K2eLK3dhNeHT4tLW31FheXK2dz g7CxO/y+V9nZHDaqx9dKXHWtubk82Ztt7rw8zzUv9kbzzXbx9fr5ojg6Ozxq 9kuji2StGr1W9x5Pqo8vlzeD9lnpdWnlcm5j+LxvGnm6Gc8tPr8u79VXFh/a G61+vF27Olrvbm2eJ9sHl0+9nZ3Vyuhk97U5PN+5bJ8NVsaz3avxrt5yKB3q z+v727ul7eXKwcP85fixu3e70V96uJk/eLgaRWvz17Xr+e/1jdW1zsvN8ly7 fxAfnjYXatYaba51Rt/XN8+ObheT6qBTqlVqpb2rzvPByfz2ymB5d2tfKUK3 8e1Z9Sys7S0Pz2YXDqvh7OL89bxppNIY3T8fPFaOTiqz5/vlzfmbl8rxeXc3 vDgant8uFU8PGyvFUtw6fy5t7x73149WlpsnatfIYDypg1N1FBDx4U178yDc b56t3l7eHlbOiueNjcvB2UG09bi7XblcCbeii/bN02plWcmuwUr/6HV8VNw9 NX07XJj93loZruwtPddK2+3T7Ub36aB1crp0dVBdv15auX15OrvqP3TP5xrF aKMzeHo4WT5YugpHVWu1jjvPi1ulneXReO10eXHnvL1z1lwp75fWbp8rrcPx 1v7j1f1F63W/sfD0/H39obq9+bqw+6i3IqZAPlwf7xWvjvd3q/XDw+pD53Z7 4XK1XZptn81eXA5O15L22trTbqnWrgwWyvHKWuO6vpNsvZYHphvX+8ePvbXK XKW339trX+y/7G4fjWebSzfzYb10dZ08rOx3R63xxXhl9+lm5ehwVO3XznfX bravr0wjjzu90ePrc2P7+WrndnF/r9WpzN8OK+e9hZuF88en0v16uB81Nzpz cxelZyU65h6+hyfnnYfKzYt1Hcw+VjbP6vXXZHO+PZyr7q/Uz9Yrx4+j89bc Qvv8qLsSn/XP2gud2e8bYf11Ze3ppFscPi+src9aB2nYqc7uz9+Xb+fPmxe9 5de11ulWd6tzcHZcGl72btvDg83L7dbScnPt++rh8fx9f/+qsf0Qzz8dm0Ze x6PX0cnZ8HuxdnG6Md48Wg4PZqsv6/fzO7WF3br6/GFz5fvO+fj4vncSDzZO tUNiP+uOTTTQOHtUXV4Bk1WQofDVFRGcM5mD0fOTM+YM4bjWsVHf098dMSKa qTOx0iZHXfpoCkbFA3sTDgb9+F7Z4OBUK7oQeA4qCmuyAoGQyVdlbwBr9hqi VieAb4OJhSnuyhhC65HTicK2UiKpANKoVvb7mEchifjiy2CEPmhZHBDakW/i UtzbGR5ZBsGFMVlyBqHfnth/yqAzjiXXJvdBwBgEa2wZ7XkYgAsrwylQeZHk H+k08p/MFGSSQjJRFf6J+mS8lURf0yGPL7laQXNlnZ58tAEVQvVt9+SMlets R12sWmKuGSI3L7o0U/vPjkMYmxxCBlB2IkESnASPB3TaZCvpAEJaxe+z+9sp hrrL+nb1x4x/VdvD8AEXUUW4UlOA484eRQevVCGx7SMOA7szZxZyDmcOqSc3 1zeUVSEF/KZTGrroZH5lAYCVno1/oLpTLi7OlaDkmjL99Fu6nNvxAHvg6//3 OtJVZ1OO9PftKNtJrk+cO09yptNFXoEjvj6Jr8rIHojOmGbQM2mMOHatf57O 8akH2Q7csUv9bsJsZ5zh7I/RubgCGKMdr31OlDW4ERkh4YFwUqbl6kJpTtBO 2ZWY49ylRhwkUpg/fXgxsCf5IPr4GJgpXceD3dOgbfCSlTqiX8S6IfH5gHPc drSZt/UGsd3bKPENNyLhhPPyZIaII7KJxVyZhMNKwTjpTqakgI0t7iYirC7O QyJCQbrrlF9L18E57vSWl5biGhKaKVg1oiYBO1N2RRwITr2a6+vHR9MUA27L acQ5e57t6cX5TsUX7LWxyq0nu8uzyxO8Z3ncbCO9OmUf8LsR0RbSk+Ntd+tV Ax8yvBockYOYQZv9VL7W5RiCP8u+dns97dHcDUJ18ZpDZiU6aCWNr2nw+txZ GL8SuKGFhP8aF+xaD24GNaikYKCjeX0n9ooTtuyepToWIrZIAsEcqj7iBTcv AGUXt5PX67R3GB8XWgFqG3mGAJk6RtjAQq0F+IQCLMRwywhzQojk0UsPY5JK e1Lab/8JXNghpTeqV2tPheQpGjmj1/A91vgxGe0uO2ZiysDWhp3mELYA5F7z lOKul4Wf9ozXw4FGxIE6uZM/oCG4CbNFfWRMAVUaak+1qkSrXFlSiq9aBgXe pJzSCBnzykXHgauMfaOYiudJsUmJfgz4IhEavQXvOFqtbjF7B+PRs+Em1d1q 3ZD1CH21op6qDv2WcJGyU7OvvsDnSbIC+CnfNrVz29No0Pp5Gx5G9yeQWihR GVgD1jqmozl0rR8kXUnoXDLuam8p6nTmGkNFMUm9ayUY/WEP8sdpDd/E6P13 YjZsdLtfhacyl8zwYu/geKm8sF6+Pli72jmrzO5Xjt/k1JUO/gqwRK8X3/z8 cSxFVqRPqqBG+/ASP+xSAreJuJX+sDMJG7n6E24kcB5BI3/QgWTcRpgr+1HX UdphBI28w2nkbiTzv1NKt+ipu8jdPZD2hxXGY8GT2qDHCkfwSz6DsbXj5Zu8 aV3CYEucgDWYb8hqLQmEh7ZVCpod0QiiiHNeUcqRKAoEV/T376WrtfZrZWO9 slmrljqX3a9LB9ej6/Fjv3U0d19pPH/Z2T+4j7bL203JK9aWvYhAI84R71Ss PDdNiRIi0yohNPg+iagtlt8RHDpwjJHfCxNw9OHkBmnLgCFm/9g06MZaUac5 AIG4urJi/spg9xm+x6n/aZBh8eID+f0xSNr0lwvuRz97cvcxpf+j+ftmQ7bU PtMQSxbuNlh9zi5g2+GPl0QQ0jB8/89Ta8rPBzhNtD552LofWHyYS9gAH62y +D+5lJlSjFppODoLl7pP8/HOTRJW9ltz6tbebzXrizV1y74O7sftpZWr5tVK s3rc3J9dw0jFl9eDvbnV7vZjtbyz8bj3clVqXp2U4spS62H1/uDwrHHyer91 0VnYfPiyeN6qRSdfZm8W25vV5efZytyXaCeCRo6/r7Vmr1vX+2H1dG7u+my5 86U2OumsV+vPX5e+LJXai6+jq83NxqCzFpXnNte7/cbZ8GQQDr+O+2fXm1QA sVr+uve9UnpYvXgtb84tP1Vb1WqysXNdXuo+JFvfa5W98PmqtFofntxsNK6b Tzfh8tJw+WGvND++eOme94bQSGnvy/LFuRKLR1+XS0fzw/mvr6X6+srz6dX9 6/rJ2XF80B/OlVr3S8+dtZvuxv35dlKpfH3dOQmHLw+Pq2dfsJG5le7il0Fz dH01mlvuDh72qi+7u8c3qydPu83XhSaUYvytyv2tyv2tyv1fp8q95TsxOhO6 0hJOhObyk6y3SkO3Oj5jTePreCOdLwfGHwl+EO15SleHurfjnS6UyA5FvJCB O46wCd7FAccB2a3zFI2dvOM+ItoRqIk1TnDFiUfHw3EwTdh5ut4AktNa4X3U 8nUPtASMtbZaxpFg8SUMO4O4BQn8SgTWAWV1ADpOMviMGHmwQL8RFVtvQJzU NUCKiIm1BqsdukrXIB9VO4oYJsbJTc5iKv5Do8VIhHhywakJEzJrAztpdUW+ QOZMaMTxU0jBlEP8jHwxGlMiyJJqTBfQzwwYmhxj1W5OCYpaMelWy86kt2fD WwJ0ZnlRyHvSka/gXjLfkuj1/R//HDUZ+ELppmLHbkfH1fMiEbYH0ordqF2R 0g4FNVK7ncyZwQRmN6Gc55U/rvS4FNzjHd1euCvuiMjP8UuZgb2BRA74yr1u TGBp9say2AwDX1jeG6ywFtLZLyY+JwMT3zJBO7t1Y1BTA7Cp6PmbUm8U8dL/ kyaFi4L+B0HQF+ZXV2bmF4pzpWKYPG+EM6HXoFB6wD9/37r/Wl587oSjh+Fw b/HlqVR53O7f37/0l2rPcefme33hy97J9cri8CvcbHtH47NWu9JePx6MLx5u 5o5fv9aq1YVBch11lhqvvfVR/DpeOj99OVo7/afP+OB5+qj9kSr9ztobi2Jr DCD8C/VnUa1W7EEyF1oifiNDevP789HC7v51stcqVQ62oi+D6832Qn3ncKGy sHbW/f6yuFHaauwsNKPFy+On5gsm4tV3S6eV/uPaSn+cPHerm9vP5UZ8sXd8 mWzXTjbmWudL86vl9sjWq3+BVvgfyoZiBUVQdurAMh5Uc6jMETTcSPVszktA zhtUElDisNwwDRFG0v8Wn417ZD3emw+fNdhew68fPWupQ5IvCzKsQFp4FX6/ rm/sPW50StXvK1uVlVK0uFs7PrhstxtLo92DbjJSennt9Qvmxh5+iVZeHrc2 epfV0nU7Prze+H5e78el83gvuXlZmj+be10uJ6v7raWds+0n6qKfbsh8P1cs OF4IEQ3vEAu2GyIrGmyx8Cs8Xm/RL8lAs7xL0k/zTHY0K7MyEjrMjlzja9Z2 hzl3FR47dZYiXTHC19PfN9ZfcWP9gjvLubWmsVUlFH9FXz66Mf/Q1vRuzl90 937k9nVn7veLy/PNl6vT2WZ0GZ2d7z+sNzbOli/3xmdfvhzvVC/uGyflueHT 5Wx3ud1OBvX7593X1fh4uEOf3ahsvVbW2rOHpydbF4e9g42tq9P65vxzXKoe zN88vtauSt8PRq/lwbiytvqlklyUamG5vDJbXrzZPuxy35vnyf7J08LW1sbR 8n7l/Gb2+Wz1sLs6rr2sbnz/urq6dHZ8OSi3vy++zl6fX2+ORp0vZ0tfjmqX K/2tQTuhRpK5m8bV9uxmt9y4WHqOSou9Ly8Ls9dz/eeNnaTxFD6dVdYW9lYe Ly82xvfVaH518Li7f7rWnR/GtY2LETUyGEWjtcOjuL4bfllairfme5ePK6PV SvV+ttapbTaf7592muXq9/Amumq/vGwvNA9XenM7O6vPX4+/n55RI8fNZnux eXbZXj9NFrovm+3LpHF2/BI1hp3Gw/zVl9O/daAcR4vOkULoA8vuZ55oC6Hf znhqMF+FxdAJJrsFSPHjHwg58dF0XXjpLpX7OCmjEFExPCqeBqUFFwQCZJDT ysbJYE4V+NViKLFSk3imPpjq4CA0g6+p3R52eMyCt2UCMIHwBGHQEjtZBEx5 FxUMjeEQu9qHfJgEV+YFKUg0FPvqwsIsIKNBDAohcPOjUKkUPd8F/KviS90k ysSX5haXlgNrsBRe/P1wd3d96XF9vVzfFyDq7fLV42h54eXksDy7vV79vl3d vZ/fON1cWx+dlw83rl+ONsrjtebRxVr58BAa2Z9d3Ls8n1s8bfdeK9u9xdOn w8XzjfPXo9nTUvWishTOr20eby7Onrd7veOr1kNt8/9n702320ayNdH/eAou 51qddhUpa/CQzr6n+8oabMnWYFGDpcxaFkiCJCwSYAKgKDrLP/vJ7ovd2FPE DgCUJaerOuuk1+rTlRaBQAw79ry/ffrs3afz1c7p1uz1sLuPauXHrdn+5s5s 7+P6zcHmyfKZ+fveR/j31rL928f11b3jd7O9wfnm6bt3m5sbxUH7dLQfnexi RV13+eg389+bB6frK3ufelv7V6OTaFzMjjaHB73t3d/C49HT8/cvt6OrvdX9 8cqRWfvLnY8OdBtDNwi8vbW9vn6wsf7up3V4ZmPwxvz31jp4yv+uPOWPazzl MEZtLc09POU4RqmKRnvKH7On/PEtnnIYo+Qtv6+nHANIJW/541pP+ePFnnKM qVlv+d/vWCmzswn8XOgPxtA0uP7E0Om7l8n59pvl6Pz1/O/D0/7q5tOfpvnH tRej4dunn5LO499evFp7+upl7/H7/Ky/gQ762evp24P2Rftk/Or5SueiyA66 N8uTYhS96ExWr96MnrwetY+P+51iMn31NE3a4Vo+O9ofFm+Kk/nT/dcvYIyz x9tvT+M3Z/30sL12NUu3Jhsr7397c/5s9Dy6To83ivbfr47fHbWzjejJdWd/ km2sXxzdfHr2aSXZijYGGNnb37ta+2l+fHR981M8vJicHkxP/r4z/HvvoDiN Hkc3T3fWD89vRu/y66I/zE8ufus+35lvdOfPV89eJ0evRycwRj9ZM2S03H66 +nz57+ejfG3n+tlwLX25frjyIn6x/OzkY3xyvP96bbB8s3f299Mn07c3g3n3 qngy23yyN5pfwxgfk/Dd84u1/OjZVv5+L+2ud96/3lnfHc7e9IqTx/23g97s 7dPr4sawqu8xwn99jBDlqi5ucL0C7smiMbjmsemvYNEwiMemv4ZFI0SiYtNf xaKRVsu9Ee7LomGQL5Q7fplFo7RbVOh4VxaNrLk+oHl3Fg2DMJv+ehaNjKQU 0Lw3i4ZBKjR4XxaNrNWw6T/EopG3vn7xx1g0JtBM/yCLhkFO/p0s2oZ5/+0B ZWZ0+RTziP3vcY8b5N+xERvmoQfNxgPqzvDgH7cYShDKCjMOAi6wJVz+OVkV wdiZQtq4YJ38lohvoy052wF+K00SBuzg0De+nxRxpqKVBQJxUPsAFaLzMaCw UXbUvTL2jGt2FGOQa+7ww0tBccwWByjnHiB1owWh1h10oeVVDTiY24/6DWsy clJgWzMU2ZQNS+o9rTbX4v6DXZiCPEVoxYLAWKDxSePwzQ6D06s+BsaINJPq SnEkTzCjT7WMBYextxa2eiWAQtfCDfES0b1f+mtrAvVxWQI/Iz5aOtaYk0FN bw3b/6bS/29hpBs6VwUBkQKh58EZSN9dr9BnZjHgwcUGlEG2ptpBarzacDQZ KLLyy6ebjd7cXE3um2ArtO0yamDZkTqoMAwgoswhhL1m9XVYUguCIr0azPrc XQlKfaXIq22jG/SiySidYyR2AqpZjKR6WxM+/6zYQ7GpcS5//8FDtLyvrwKA NO/jq0DgzRpfhYtE2XZWLkL+0Ez0ke1999QQncVHV9Cjx35trtdFCWGB2JtQ KX7xItbWUxB0R2E8RkxTaptX6sWGYW3bIkSV08UO4rXcE8pVl1JJedDwamb8 9Br8armj5RLXS1emUyrF0ZX0Nupu+z+qXj/MjL36IaiD31mwilCVFsW5HdJ8 IhzJYDTDOkTfJa9oB6qwokv4mi7YLuaT6vIQT5gOsMn7RC5twT5GwvIrv4fF uDoQZ764ylXBprMIYUg0uEyAr2rlAGqHHq719sbOjoVCdeIDQbs4KUaBOnKT CsPNJpMoQygsGqEzp8YMCYHT6imba7tgylAmq6rU3VwZv7PU4TOBzgnpaFpE 1PJFwWFCz74QMV57jd8Qu1rlqcAfjfjsZ+EA+Yz9qVRUL+WDD8FMHEQZQ+je q2QQui3Q25D2lEJqFdVqnezvvG9sTdLu0Pvq/WtO9bW/Q7Gp2ZXq7kNNhVCw 3yPg2F5ZdYmDhnQgN++8xEaL02xkeyw2Hkpz5wlF1B9RNtDrdUgsl9LyhnyQ CMa+LNNwqJIlDLZSaa8rFPQ8nl4xsup4hA+hz9PQ2OHJsdSiB1RwijDGrlKv beG5iXMuWiw0AZLFCkyrWa9brgzZmReRLUu3pcY7PvI4IW6OzZG6DhvD8Dqq LCiQBb3aOm5yV8o2gnlvbr3dOt7yCu19xGfDmFUZCoHOJo1oPCnmFs253tNu ddiewi5H3ZlRMQItxTgrSuRxC2aBU36t/N739LwjyfP79YJNIXHUgPbWATAt QKUr2SQL6mjkacONMe/ZkJf8yTB1O67Hx8VZQ5zCPOOCtVp3KMEAfC+o/E/z sKnDxh/+vSn4i2ON31Pw/5op+HGuqigroUMScLXFkYev4tPpwcVJd3+lOCpO 2s+Km9XOk+7LwezF+HDw/tXazuHLtdn5827RvU+h3B1ClH+GQrm1QIuwnxvR fHfYedWND+Ld9smnnZX9eCffGe/PL862ly/O3sUHH7dW944HTw423y3vfzox vw2XOxRUerYzenl4svIufruxm4XwbLybdMbbs7fvdz+dt804ydHT7oZ5btyb nr83t208ml68Mv83L37rYbnb/tVOPIt773cnOx/TOHx9tNx9vffs7fzFp4v3 u6sX73emF++Hw877l/lF++nHzury9cXq02F3Y/fFEh0jdgC6y1Eu9U9+a7VP W+sr8fb+6t5s4+jswzwdnRbHq3iFji/WV4dPz6P3J2n8dHv13Wp8nG4sH3ef 9LLz7YP26533z366SnrPfjo6WX8+f/3bxulh6+LdVu9Z+HZt9fWzF1gA9+LT dC+ePTv4kD85fvnm5dr15sH1LBueF5uvn/Xfrw4Pny9336UHrSfPD2ad3w5b cf8qu95ZG54O9t6/OO5/xLhB9GZ/lgzT/WS2dt2ZPm/vv4l+293qdGYX/clW O3wVTdpPV2/2X4429/fOX7579/5m78XBb292w/f9/qe321voQG29j5ZPkj4s 8GUWfloLD7PD+crGs/DJ9Pj57G0vXDsMjw9Oi8E8v/kUx2vp7tlk+mn57PDp 1dH046dNRCadvf+wdfDpbPlj/nGjffW2dfg+fNOeXAy2Pu5/fLO5N3gRZ+2b k512sbKxcvzst7X2p6NBf/rue8Truzz+Lo//WvLY2vvWEc9VYHnVbBLXUMy9 xoyNk0fSMEMQsLTVulTCiaxpfeWq04LbYhXawl6EoBUsrrbz0L98d4PYNR8h KmAsWvdVtH2bDfEloC04EjQs9O6HSe5agZa6lWADFr9xlfPksS0rRTdxJsVI 3g4tNWAM/ar5FPUDg9YIhJ+PPgDp0KJB3gILjljXUGhcAQWS80XPhYOFwGaf 3H0Ct99sbCfQeHQOTE6Fe5wP3/USsX1aQ9t4ptROWEFRsreGYO5nKSC0GlOa PJ/gQsIzVMCCoFJmPdQaCSgLPALTQhIKS54V8cc/lk5RquAC/VcIHBm6MfF7 5kCM4khIpMayt6euOlCYI5pDlCYDjxEtrhUOsOEzehUh/RFWkTM2JXaah+Iq go8dCkYW1ITweeB+Tidmj6RAUG0TdhylaM2c27XAQAG8r86UQ3A9idLIYTL1 /0gK+ZfDRTqscVvto37uvgWP4qLPgvsUPHrojGEnvZYKm1C70fA18n7zzlBB ne8fkXCSOLydE3KRYw4a8jD4XYna6Chhu+iFJt+tWnBcVRSkoVxhNewM86Yh h+ymosFRa3g3B6e81mm//+B1S/uK4NQ9Y1NfCE3BlP5IFMoR/QLXHMWclr7H nP5TYk7/1pDTw6+IOS09+qMBpu/Bo79s8OjfGD1CV32OgIvxp6hXgn9Xt4R7 gyu5wgAAGnQBkZ3N2aoBEeZMh2I0K19aGM3BkXJPHS/1wtWdyEXPt/1vL8t1 AJclpF4GoCjA8VCnDcpKCiB8MG/C3Ps6fxDbFPanWTHEBUjBigsA/sniZ6Qc hrnS1S+1UnAZaMBlr6F7pQPrvcNjt8vgP3t47CujY4xgHzqyPqSjaH6Pm/0H +um+u+m+u+kcEf2nJhr/RwfDaqv6lp88D4KvCoD5wa9fg68If5VDX78G9wh+ bST5m52N9cHOxu7wfHV/1F3b7/devch+DS7OnpiJvHy+EcOv/H/j7Y/nq6ef unMzmW15U/9+dN15/TINz54UnbPTX4Pl87OjYe/VVqxHef8uxf/tt2fy7Ukn ORp1zeg9WOZrPfKvwXrcXTsadhPYmJednWR3ZBZvtnV/eWe0nPvzu5h0xqNP YXmUXwP7xMqo92p4fQFPbOyaUY4m3fEpfNcfiea10h1fma+uY0Tx14C39WPn lZEBybvpxfjF9dvVfXPsN/H52X5mDqJmT55ed8b7I3M4g53Rxa/Bm+Otn1bf HR9tvjsd7b0bDXdOt3dm7ZXdw51B6t56vfyG/1fmFZ+v3kwuzp4u73z8NUgH 0cw+HXdf7153Vs9ppknvkzePcTGK2uVdNc/9GiS9DGalRnK/ro6ucMZMct1k f1i3ul8DM/4yjr9hyH55K367Xh3tgn5/eXKyvVEzyq8BUFZ+MedR+PLUnMeU 5jS8OF5Oi7OtF2/bp/tXxycrx6GRCE/7R5+O3h+cLc/3Xq2c7G1fvO9tb290 V1c23o2L3b3xfnGSvFt+d3b15N344uJia/jpKJm87G2P3h6vTmbvRjs3J2ZP Xr7tbk2K06viSfukdxAdv0z2R+mn87N387NtQ1mbw7edtV4enV48PdgaZWcf hwfH73vH3fH+aftkNzxaGZ3/GoRXw1lvdfKsN7543TMn/P7T6dv2+GZ68tHc rtPd0+7mUbi/ffpb+Gk3fre6/fbirLfV+bh1c/pxdzXaOlneOxv+Gtycn748 7YyH7bNkONp7NWkfnR5dXbyefDo63i96x9vH7U/Dq9Ot/baZ/drp2exm/9XK 6fH4pyfh6dH89NXycsfQycubo1fbV9HH4Ua48vL67fvT1f2t3c29V7srnZGR pp/243enP306PeuddTd7z96Nb46Oxi9eda5uTo4/7a6crr3sd34N3p/uHZ32 Xnc2z9culndvDk5WDvdWd+ftleH4aHU42VstDqNktBYlvXenr09v3p7tn52c HD09Onmydn4ym52sDTd/Dc4/7u+cfzravXi9vXV+spIcvN7eOX0/OjxPXr4L 3x9tnbR3FF28fGFPX24C04m5r2sv8/P3VzXc6emwc3aCt+D4/dXgndyXLfvO 4Hj8a7BdGHr0qSs5nYdEo2nv9dGs+ymFe52HZ6fT3sbTcWf1p2t3O1++eGuY UoWHfeqd7f6GXKlyp3bHnbXd4vz90Sf47Wy+OwE+a/jJ2mls7oOZ+YvZ+fvt lYv2bo/mZdafLL9Z2pvtp6d77yZPh6c3O8vjjfzF29HBSW+7uNp8H66vfIiO fw2uD97/9nzz4FVWbL55/fy3J9eHqzcnv631X69+PFq/+C1JO+nyWe/wcC3a W9t//fTdyceznybhsw/vJrPeztnVm+dZ69dg+uHp6mS6tTw6fDl5vvvkZHX2 ZPRisNMZ/BRfJfn4bPw+On+6/WwWvzr+aVL0p1vnrwbjUbq+23vxdifav95c M3fn7dnqcLX3aeUwWY02k878evBy+WQQRssv04uXT/rPXvTfnH386eLF7Pp4 5+PVytuL3f2Vw+7b5x8+Hf/0NjMy9oVhSofzT8fP371Ir696K3nryWy49fw4 S16dfNruPh0Pzk6SD4P8YJIfPh3v7Iw+pltb163t3w7OVo/m++fT0cHFaPnd r8FPW0my+fr0w/Xhp+z16CTMOq8GT877/UExu3o37L15vtraPbg5f/fFmCM4 ibRz2rnH/v0xx79gAO97/O7PFL/7xrE7HfW5LXann/vq2N29wErvHqhrLA7U fas4XeMOcTrY5cZRlKfTrBs11snFexQPhgVgxGb8gzS9yvAHY4gh/hc0mI97 SJ0Z7GZeZNMu0iTQF/vhLNlTmMtMQAbNg6Exo2hGR22KB9B36G9c8pan/WIW ZhFXrriPQHskeBR8/3gdSzVyjV9s0/qSx/4fD3/gn6iN1yP8No5jnvzFawKG kQ3zPbN1+Bowujzi95YQCO1Hf1aBWTltNe17mISjdJBOrbl6AGBqjdWlZbPR Ztv85mRHNLEAXFpq2EobubUXz9Cdib67NC3s/fc2iAvkwiwL50RV0YhrW4Ww zO8B/g7Xnysk6ZyRmHgv4OaGmRcPEOIP/FDFjiFoQxYQbKsMY7uJ0mKYFI/A Zx5wU6XQtgU1NBTaYBa5KAXQlYdjT+Q0Yf4H8SZZX8A9s5BL4fJpr/jVmnU0 yuduPckBXWuaF28GAkazT9hCSge9eAzROJZ/NOBSYwue5VVZN3Lo4rHAHaJL 6NM7ibKC27bZ5mC0SAkRrB/uNCzIt52qDcVJwMNRgY0/uNIZpV8QmSSpLSYN 0F8KEwk7JCw6UTGLzGd6cR8ZYcHzZSaP0p6jotGCsKj5rtx6FwjJveO1/Qb3 1s/ZM8Q9jYlVU+0yayBIieDzqYh+WRsP4XVTLYevacLcHzF33XfxjLJ05CJj S4GeICtGXOQuEMQQs7iBsAwUJrF6JHoYrpLhr0Vpu0oAZRzmkMtFMB9qUL/C di2oO2Co4mF109EoRqlfPRwPNbCBbIQ+QtK3CPLpBJS0fMn7FAS8oWA9mePo NjeslCzWxxEDGpHhwGgj4hzKE3dQPh1tbRzs7W3tbxriZmImXRSvBYFSj1qT aTYBr5ghaaRgQw8QVrYRZdpuCLhep3HPLTq3q7b3Dm8FzsnJGbOpIUR5ByM6 QqMoxCOpDXe10xgfh2XjNLB4HyNcpAzDGfG9jKMcopOu5WyXtxjJFKk5wisG +GWy9Uywln/6ssEwFoaAz4zmpA6R1kLXPRfJ539VwnGs2CMnhk0kmssjmQbP AHYjQe7hrm2jM8V4PdefW3lu3h8DS84inh+eGOjILnoPp0SjyclKngJNYolz PswlhSECtiqYS6t7bPmclQcwLAUe7WE2VSvVAA/WUFwRQ9Awk4ssTfYuQ6zS zw0vIrlmvkk3MPe4ErNoslbq9AekBdCyGsxuUVChMlEal9iNZ9yEleHC/Irz iuDHdGxUI3upHmTmBB6gGvJgZhTq6IEID7OeUUpnfuuK5CHhOZW54hRlvvBK LoyJzsFsSdzFRubmEuaSODRn/Q3frn4Dpgd0jvt52/SusBcCsw9zocN4FDIs Q93W2w03uhWQAy4F51DZ+vtsuwh4HCkLZ40H8diYAw94VrD7NpwIczBkNkzZ KIR5wHJdRpUv7NZtWzL7gNg6ZBNYS9OKQrvKWvqZmBdxJW48op1xBKOOcGNS 6t4bNjphcoVZDVPzSjIdd+zj5tKYjYjpBVjBJDMK2iga3H5ifEWyxii6jkZ4 dvZFvp4sc8ETIflrtLIFh4JTrT2Y3hgCrgg4YlgvfpFPC3MI+OBmLiuHd9Cw Z+5fTIIRkisgnSuBiA4L/S9E+pWmR7SeRYpc+csPM+SQeDWb0EPWMK1HQLyo BprLBY4Bx77tjaVkDO83JZEfCrEZJgx0mD/iI2OppRXSwCVUGhoqgH8bi+IS 6bMVTuJL0rQcc9e5i+Uguoq9cS+5B3Ygr4k7ccdq8B3ZVSmoS3yr9EfaKhWb V6PbXaqOvyANIomKx+UvyKOW9mDY0WPUF+u/axlW9bv29pc+QsdTSTEI/iF+ QNAs4GxIBcwjo1EY8YQkhAq1sawKd34o/IC6xC4NfPWV2hzTfzKHVFLb01+b QZ1Co8wZd0mBtiJlimjrKGBbChWRlpG7vWm3KEnrivUQkjMiDfJw3lS/OUsS fQMKARdGc/LZqHNgcZCZTPkmBT2iRB49ZN+2gD5K7gT8jDL5ZJLreT4dl7F4 KakaEgQNZ4ec0Wat/4BAlEIYQaCfimAmyEoivhDl6RIuxCVrE16noksinUvw NtLho/8I6TowM5hFZlFoC13SXbGj8AuXQpOX1pzADEYeg/ijUV+R4IOSXkGa IJ1fU+VkkytV2+2Yi2w3SPGr0ojMlQNJ5eNX0D5OrG3lTsketmxK7VPuvNER 7X1/mMZdfOWWQfULX/gAEmpQOevQtupWDaIiyO4qImv5S+6ZdWFdim8BJWZa hCN77cj3Ic1Vy76LwJruFQ8Gf4wU6C8JL3Td2hOtlwxBSTIA1bqTrpE15BIZ A5q1NTqMYhgQaL1LBeU1dmy2Pwo6I0ojtWfqUjr3/L9YMn1LcXNfEbJAVDS/ zfL+FUL220rORTLyuE4kiQMKronloUyIHuuES81Mc4bC1sdg02zoEvfoElUv xVNxVPyOYqiJ5hyBcFRjFhuFDJwkRjqYwQWXpuYjMF7pG6WZA7fRTB9SUFFu ooYQT0IrtH1zGq1P8oooFhw4/wJLZeUZrnFOOAkT8PPWDGHFAr4aF3k06t/K cQLhOPkwnTHXIm8D4uDznGDPzYAt+xEx9PMADHbky542rDgWTESb8sIBYe8C n3L8wI0VB02fzxMBOC3B3wChPiWDeTvc7C8HUSoj8vsclSURfKdZoU/WMxvv PZHgsjvNIAY1v7QwP/83lPv/dmq8Gk4ddWXA3xujsPi50VpbXVp79qTZGCUD gORfW1pdfi6svfLsU+/Zn+jZO4sFa7W3sDqXDutuIsJwq14WzuqX6egQvsIO g9bKE7M2/H8ehDUTHTx50t584DP0HQ44qRIZLNu6Fn26Eq+R0hFffUBG16Fu n1YRUuoCsEfnrrNsnC1vioMYngKe0qYUP9tKwx9+kIgazEMCnXnj5dz8g+O6 dYFO+e1zIPic6COJKMkBooRs6pTCnG7OMiRFDWvCqI+agb8R0KSU4gqu/YWK kkjEIA0oVuCsLPk4D1dyziw1dmFTRvFVVNp5/aWAvIUSMl78ICn9snXiQZSo vvJzyerIj1YJ/0Kk8E6VGAG5ZIxiaRaKxqW4z7w5gg+zvPJbuCRzuZo6AvM3 RKgVtFwz5AOnxFjwRPMflKC80IeZ9ORIjX1GWT5cuISbRgIKwzrYOIbMTTFC 8kmIeK2w7WkPYYOhisFoBpxqgUEJo5wY+gsnkDZCRJLD4gEhdqnxOp1FqM8w CHCQx8U0dP5uuw7wUCQ9G5TIIbQC38CIWF6kqXXNl2LyP4L6cR2NYCp4nmgV QiEhgSIHWqUBSy7lUNmcnhxOx2HSgpNAa1qIqf364OTtJrnezTlOwFpysTB5 ThKVCMMZIrJ5PEKwzP40l/iPnZ6zWM3fR/E4trdGvorePBzCkFpoNK7BlFCB 7c4vMQH0p0mXsIshPopFZeMYIhFxYqF2YTgb6Df7dJl3U1BtXM0pxvGfPX/y AjrQzEgFEGuMI4bKj0KGf6GYINO94zj+GQkdgg8Ed7vJDIqvbsC7SGQnkWw4 GqJUl6WAM2dqCbn/LV/OVgrhxtXPnzXCae1nXKi5cJWU1nC1e4xx6izmqAx9 rW4bPT/numzbJW0NW+Ve12fUUom7tdAeBq2M5kb/tmzFKDrjnLkTTngBU6re +NhzhzhzIPT8tKiW1or3y4bEMYOSMugYroujkb1kdN4yBxPVt8zFLr+7hP/1 LuGmli7031UJ85+n9En5zmLBqHWfO+Tn2AJjuKm6aFxdVAyfBBVlg4o40wzT NdJGP+xCoook0GqrVCAXkl6NygIXU7KbiA0FEPaRqHvTWsdOgIUS7ceQVmQ4 /phrhiQjgR2uhl+YaR4kygWJujHorKC8WlFYnpbcb/Sr41osj7QMGAQrG8pO mtjm31ACNW8521I0Opvm5HIAKCxJQsX8JTTaetCJhuF1nGauyTziApQCepVM ApIivag7CrNSuTuv7OfblDHHaoSg1kWPhfQGs3TMiqgr95q3xANSLUH9BkzO KYrMzCwDW8xANNOwIeYadxgFi8aRkX5JnI/JrsmiEUWMa5TsvDGdaL+NUKbE 82Hvo8SM0qU0CTIUrKKJycbxiFQmcGiBSYPC3ebceN4jTA7djHNsozEH8H/5 b2MWvZzz55vUDRYiuOP4k02mtQlpCNvR6o9AXQnsCGbKoGwOQOfwcU/KUjVN jEoG4+GVACMIH8PQjesxDzFYMoseWi3q5GhHUjshhewqmkN3Q+dZq4Ug2YLZ Ub+MaJQbxZtyFqUlCfQroXYPmCvBnm1D/lnuwg7G2Em76cjsn9XBeXIwGqYX oQqKOejwP5LM5mmWAhZWCVbMQm5Okk4K3HMcAyZkc0zNp7gf5Ti8oovuVSCs nwdgzFokBq7Yt8Y8D0ObLH+0m40BBEOUEeVJseP0R2otQcQSJxZQzE8041oB SS9Hg8jmrOMfdRFlcFlGFL0UXZXZFx21TrYu8Qh0tkETtEtczQdezQdZTTVn sZTnghd3HVJR6rdjyX+pHlX/Len7ay9+evaZvEC8AXl3GI0jl1rVeEjUKsOQ NvPgEaRRQMK0e5LuNdAAEMxoTuwI3NbNr4FdkTwzmCt8HEdzZR7w57rrWcKo iRQN2HgPjKQxXaQm30z8A1bifxgbGxcKfzE1EdFeahNT1jEc7BIzfyTjlcdq 4FgCbqOy6HObHY2vu4oVpnPeOJbU/IqE7n6pfiGnRjAqj1yeaeEDjyqoH0aP gW+oohr8hAjtX5CF7qgPtfFDe7AtjSPqxjM339tZ319vqQnR91q4fY9oo+kq r78tbzRhGnzg3fnDe03DfevN5hId1hLl47/UfPiWM6An6g6h7gBwPvWHsE2f 2mO0pNvOgb7Z4u2oOQojfT5gGdLXbb19B8QYbaHrKyQKxF1PQXYfx9GPGxMa h/VLsvCxX6C+xW06dD4nDn/XfXYj4T5DXc+hLGHRDsNXcEK3bGw+7XyIex8Y ROCPbS4lSXLmjZ94B4Pfd3/5URxVSLlm9Cop80MLtxZHrOEjbR58xw2+TVO3 W9sA1KyOmfQQXUakF1Mz5BdrUFJS3l+A3cmIg3yzLbZjfu3O1lCu3Vk3+Lfb WKLZdTtyeVeFYO23+XIs4gRS7+XtZSdNjVGZWD2E/22MlWxqLAhdORcWjV9s rzBVp4PpG+RfQ3XX8wnCPsA7NhCBj8Mle0QZZ8JiXD0CTh5D950cbRE5G+YP kK1op9kPjcL8QPzK/mzppUggn9APaD/ImZpKZ7RFV3IEHpIjSAvWfSkqzqUE ORoLTt9cPzc2SjJHI8Sqv2KUUKEqVczJj4HRaBPAR4wLpD4C2ZtIKUyoNqmS 4zqI4d2SeiTmAzXUizJdb8St23Wbu8DycspCYFUeC0FpR3J2v5S6yilSdfqX qNVofSQ8WIDmT17A/0+b4zL0aAhzWlUlj7RtF7ivzhj6MKIbHFrigYegzbWP i+gdPA/mSjN1w0a5WQXqyMgstgWeMGU/ngg7SImz16ExSoo5FRyFOVUmrdtW gxJ5L9WhqQvuFc+00axRFvA2vV699C276Y846NimVomC5AhOpbZnS2cQZSSm xPkldB0/WxC2ao4aGHhm6kdtm5JSwSJMMzYsIJ+NPPlVsEIzAMdYOthZ0xhY MaZFMsn1CV7OEALuijW+O07dV64z6znHEmJbCW7p/OzsrLWuGi1KHSyxEMr3 w+8YQhqNomQQkYcPnY0uZlXvHRiDWwEtYusdwA+TEWUzOczmmxXahVhr3q8L oDUftSmf74g4iOtUiXlGcAlLJqYwdx8MzgjODwCgKdwcaptY6lR8F/hXosD2 UuMkXxjNwZak4EdlzqBT+XxSAEmDLqQsyurmgF8zSzVUnhSLvsbuDQqVZw2H smezecpOAirAwSgMagKJREltrox4tUIvd+n33xfH4FkpEZ0yn/bNkeJE8fQK QIPKJemZMhxr1gL5vtDccjwpGPexXNvDAVt0xqhjLweaKTRDc6rZvFDXG+M7 so3ljTqumaXEPoFhg48K/dgoLexhUnRHQl0KXjlmZ5LWBVTfv+rHCFEeOty6 yJ36jvMuQ4K5xs9VdGQ2TuUVx5QjJqFFKQy0shsOus1tVJ8trS6twDDWL8J7 Qh1uxSQ8Qiq3ZWIqdC1P2L1QxFX2cNryaO3gJCGLfEZ6uGpkXN0oNfj9953W 5pKRLv0WoeQJuZLzi8AlCYsAMUBstr9lE1I87kT1UfvrccnKXPXnBrbyhltN jOe/JAwW5hIte1zcwEP/k/brv7bPznbenL989+zk6bP9tyv4k5y+fTuzbzvH dYUpwbLBAaTz/S3UMrHBGmxOfhLj3yIsbImuR4c5g1GKu7LEkJwkWUAOPMI0 AV1lIPiu3sNkyEiGt8ajvNS6oucrrr1ThoNYlux4iE0ZJ6cd6nDaR3o/YNIv RJ5rk7rdLV3EkS9LBHEpcDY9TbKwR7Iwe8iVGLRjKOW5AqhLB2JlkKkRD6ZW J+b72jEbtFRzLQiIr7gpw/A58g6YLH5uVInXBoO/1LDKNhJu7SSTKcD8xYOV /1paWnK/qL/JYJuIpmx+GIYAFoO/fT22aekcKhH0O0KfWpDQB29eH7WfvX+2 tr77fOP5xpP1ixfrBx56fVXwq1TW+tsGd30Wzi0XJm2E4zN89owtTElGMcdP uEE1mhOiD8uDqiQS1OA4z6dRTzJX6tIJGzMvf0XpBk6rU9VFKE4txSswEvO9 NjfCbvgNyZuNCIUG638EU8x0P0nh9KG2Es3IX0DimZsSw9eO2sY+sM211S+t LH/UEPzYUuKglIUhg5iZp12iV6lXOR5YkwJttMaukVkYEbULYHQU0mgwFIs5 UNV9Z9e/kdVXYhxBhtRAuiWAQjOCvuDEiyCg57WIl+PL08q9B4LIWR03JMKJ gPIXUECPKfcJMR3yFKtMw275FPTOZ8ZKN5YN2BgybGwr/4kBkjEup9ss9zzn b7TQuURgBy2aL/c9b2yyPlBS1XvKgsOfWjomqixN0SMgtM5P2DRN1dygNDxZ sTR5xZkCVmdgP0jPWqzT8FFifJEORzL8aGZYSo+AB+oDUIBo6IYCHAVW+hNv phFUdkNtmiPGmPGWcx2Aztpa8oOgomgxqplZA4WPUXuIKVc0HmNFVo9g0dDb gwIzuikEXsVmMPBGI6S5Ox3JLlFbbaiktNuGULNpAo0ElhrrvesQOQIo3ZjB aHMawEYhqPabYqqOFhM57J/N9jGCAp0zqMwqXlq3dcgczL4vBduExQ4lV03B FKLouj46rnMxfKMesAAiwhAs92PkgVsvhv48tcRZD03uiMBAKxyIJnWFvaHi NjG7PEpzyBmGAVVgfGppnHZauAvkEax3YVqjqDfgBKDffyj/6TOnRZjZQQIK cXbMWybTPLkiDcmwPADSlkN2GlNssYes+RBDRsV1HM3yZoDGCXxJGDuhsyXG WjF2APzpZ6Pm//7//R/zxfUbwxeS3uff19U/jKYarIeZIfBDcyO7V7H5Zy8c Nw7GYdY4mEZAr+ZPSS+L48ZmZOhmEMK/k7BjLEZoet29MlevGWzGZvqvw6xn Ht80FzWLGxfhwMzccDX+y9w8bbYzvW4G22HHHHRjZ9yBFB3z71FqSNqowtFo nHeH4xiG2c4gdSxvHKZTiNma776K0mwQNbZHkfk3ZMC+Ds0XY/gw/i/8wbzb 2DPKcZhOe81g18xv3jifwhR3zQlPhuYbUYL/nIJuiYhVMNSbsBiOgCXswVSy Yt4M3kZxv7GbmmPKjR7VDPbg4HbTBGBT8L9Pw2wUmQf3zb1rh1fx2LCXZnAc XoXD+CptvAmNhR7CntKfsrRxDPIqnpunznHX28MI/I9LdXSCsqNKLMhcZmmG SRADo3hM5GIVkTm5tF+zlEZpwxvquBpqWUg//sYYiYRdP9LM2AyYV28T3qwK /R45I7z7/vwC5Xuah5S6QSj9RNXoPlyE7kf2glxk4qy33RuPasnTYdeBV8Uw EXJvoGU0TGeQc409U7AClqJV4AIHd53TRDDKMs8hZdbZVF3IO5EkmJpdwr+4 PYXvU/WHsF6Q16H58Jj32E6OIWos6hNsIG4kbqnaSlBCMM8GLI1AHwhmIjMW Wu2GKW2P9k4Rr7UxkXiAjpGFv4nm1FJDOBM8xqnnEseOwDEu52mDVkwBuFM0 676zThHNzQxlNilHGjanvh1Trod/4uz+DB1Dxd/jMcCRRT6PQ1+0Rw722Kg5 SIXWGmcRb8UwHiO1YO9jOhTI3ZxMORkFUCpxpk3roSYVja+h2efA9hAxtxHr Wcwj1KwkJkkBPnVIAtLa3+/oaQffOPwY67R3WHfPyig4wJs45ww6VFFjNrrd /Vp5pn8TA+YVyqx9lmexlDN6IYFDOatQ4pET6cZo+KUeFU1aMnpGtlSh5AKh IyZ3GAQqOC/NHAC5QQCTB8SaMZhD0F1TRv/7afXpi8+fNZSIjrmrAnjXc4gx YZo2H1SKUDh6R3Exwgm0sLaYGA91XZSkq4jEz991rllJO21y7v4DGx/mlN4H ZJFgPe+0Yz/A+W9mDg/KEeXH/puuOl9VAMtYHjRczUIsIuawBiKPc8gqaxFm o2oOIDMv9P2jDtMoTspIXk2qVsNZuMCLigkK0gDogkZuIz5aYzA1+gSoZFju Jqqv5/AF4p0mPanJEO1YjBj0la373LpN+WZHynzjsha/ctgapJ6hV1G5OH2N tih48HoOUGlmJo1jbCpq9sZemYcwnUe3z2f+wKFDRspXvPLT0lP4OAzx+fPP QfC3BeNAh4qfG5fAby7NQ7bI72czmLlbXuQbmvL1zd//R3vr7fbnz7hle4an hg3wDdVuEU/njpszxsGIMPHiri4/eWa+GhNg6QP3MUPdmSRo/P47MLkl/BF/ wzdwaKM8Yj9Xi0wpeKDPflr7ifznqavFc6Y495lCRFAyt7j1LHkOKGGAExJ7 quOlyy3CLcdtSXCHtXX6N8g7Kdxv5R5EPTwIxp9WMbJG8jg0Px1MKsaI/LQl 7ch8Z8DPDaiHz+bw5Xqnzc/mB6Af8b+Uj/pvlOelcS7LA9AMDqeSK+Ndj5+9 sdaVJU27Tpn7mLQgJPAz7rx5eltSL1UKUP3HlT9B+Yp/DhqNvxmtfQBWNHL1 h/kjegV+2AZ4BMsLvJ/2AN25SPOh0S5HzBWhutA+ZNZrdt+Q8v9oRGPDzyyA NHZDM4YTdUOzvcP0rBo7W8fbRF1nrG+/An3bcNsb0Bj/X4idLBmThDcfKw6n 2JylAXCRB/tIJqr8CwGf8Xdow8hXPs3u9aUNdPhjTnFm7mXEb8NKQZfMxTvv rvH/bjT2029wkUoA8N/kJn2/SN8v0n/Ti8Thaslp+/cJKK9H8vcL9v2C/dUv 2DcXXPqGfb9g3y/Yf9oFM2YhfoEcRIwnA94zscPJO9WigKBktbDJaGvbHE44 DuYlgzVxK8lVJh6uML+KtNMKXDzmIBinARt4WJOxiIuRefjBrdN8AKAGnj9K Ne/mgcB9QuFHtCyry2qJAwgwH7apBU2Yg0N9bMvLxuai9t0lUB459yRhTiPv wfbCkhQAvKvtOSIsu/Ajzqm5ZmAr/2/wh62suuyxzYg66Jg3tm7AG9F4uLn1 yMdITT1o/XDkH3vOJjx7escT9PC5DvOLtkYelQ7Rm1u3fVVF/R27+zHXVdWY lC8JDRCfNVctHSCZ6l318Uisj7wzd484fnqXqZU3g/yjWIUO7J3kRBmtHg7U my0GCWGz/PnlKfgGwQuMuaxT8k/3p+jcos4xjNlyp7neYRvFk0dRUzuQlLq7 OhWYrM3SY694ZWyHPuWyP3KEH1iQD/sDglAp2j0WkqrjG46KguD3nxvXCAT0 Xw+WH3wO0LdFSbUlUHDMRZEJwj0AIcM5v1hhS5AnUmXMbwhivn/fhGE9pFoe B5MlSMTudzoB2l7MgXVlOdBOAN4MO1glLegO1OKBagwomgyZOVSCp4qKAfNw YqP46otLuHiGVfcrdLNoFF3DzrOTLqcOWBAW7NiEph6BO3qtE7jVlGWOG+Li rj0ey/+C4J9wIP+Evf7nwi38Z/BPnf/1T3Iy/9MmP3INDiXslVST8rtlX3pl FPGNV8fhuqfq5/mH6huUXFB9QdJkFjxPTnv1vGQnVN8wJ59Vx4e/Lni2Mjb8 VeeJl9+SAs3qV+SXxe98MOO6L8Kpx8k0aoV987Ou/KyMYNUF7qZ1jHr39igc WIqi0+rDn76kJni5bvjGN9UVqnP8Wi1Brek/QEe4VaR8vT6gN+H+2gC8p4TV bBiRZl2QqUXRTRt6wGOB7ynQh6YVXxyA5Ads7gE8ws3/7iKZatfzB+TSOkug kxxfOMPMP7t0FQiEVKausdeWGoelSnFDE5TdygouQKwc8aIfUBRafmo27A/f pdyXpFzt/RUZp87tVlHXiczxZP+s7P9ieQfnhbU/qq/eQmnYm8JOR//0hr3L m5Yn2wJpVWoqlhJX9/F+sGC8gzlH5SqqEsuWeKuPqBu4IB3wm/L1L6/za/l8 aV/+ury+vBH34/d/HhPry1Jg4Uq/Wyh/Dt698E7e2UbxQTT+Wc7BuYvBUMGJ +KpRaCL5bbbOoned4l2Bafh9ATrDXbg61I6p/EcZIvey4tepfPRfydIrq/pa Dl7Zhb8uD69uxf219oWOJjN07Fpn0gds2pw9TAvrSM2MqVsKHPhdOPMt878n by4jsnxnul9iurdcI2G7t3Fcw23Jq/P771W2VGWL4Xi0eqdHLRfcIF60I9Uh vnpLnMp5Z+7ACBEwUOu0DjDiX8n36tfxtcyvtO6/Lusrb8R/X/V14Uq/q69/ Dk668E7eWX29iubOx+ug6ap8FB60Tl148BbvcXdk7rdRRqt+50U+8F6cG8qa V93N/MPdmfUmvXA707bD3pV5m/9DnzliZhti4fc5a/3/NmP31/ytGDyv8Tuj L2/IX4fhV1b8nfH/ORl/5a7eWQAADVb59CK2+89pFt/j6VE6SD/c6xXL1xdB +v5+K5LvFxm60FlNBThhqmvAXO2nsBJAChkhIPQNefqC9X4tM1+wP39dZr5o Q/5Tmfkd9gqBINWmMxZl0nhAatYD6XyOvScwhLgI4aBAPABBTI+LOffSIvTQ uzp8GGXc7Ds1AYGOUXw/sZKVu0d4F9QfEYHn6u5qk0bw0pTwusK/DAMnrCea NXbRqk95dbfLdW6zQagoxqgyIPjNv2LJwpNyLHMfT8zImDVra14JQMK9kUPA 2UcLbwLEKqcPG93zK2bBSW6AsYE3Vmuv5k2zZMOgQT6SNJ9XE7M0WoU6gRKs a2E7PhNcj4DvTSaXtLgm7TMy68QBpdIEUCQ/dDIa0PkcPT6yLfAu4Yw/QPot j2//TdBp8KXaD1ldQwQ6Egu8eBc96YvMpKInATNfrCfVQPHTTOqVJk9Zagpd PiAh+wBrgfmGNxeDx5WQ95EBf9e6btW6vihUjdYFB/1lrUtuRV3WF5+KPFIT L5pMbnnP/FqfBYbX4pYX4Rl45Ja363W5ygjmqbspdqU2ATXb7HcH+GPqHRw1 t3bqi04H//lnUPn8nfgWWp+/c98Vv5o9uZ/uB1PwpXFJi6kqMYSvVlZgWFcB mPRII3HVUq5FXo4SkPj/Xg2mZsn26i1QYnBqToWpKCz3E66LDqwqX/GJu0lY b0Xfpd59pN4ipiKC704yr0ZyADI34P/cIvUm03x466vwwN3Ezut4wfKGcXJr agO3/MPH+IbUgM0nomS79FL4L9VuUVOjBfAFaQTi5l8mY3DZ30K04Pq/SxS3 FfcXJJoCiJysLBGy82xZ113y1pobGEq6FqILAJ6Du86AgmL6DBGSM42IEcTj ScT4mFjMqVgLvA9ojaXWyPdk46Vd+gNe5O+8+s68unRL78Kip/EH7Pgb5XWc FgZczGCleJIJcnGRJz1w1ypPevpfUuZZmekfrfPkhOq/LGMs7cPXVHXymXwv 6/yDZZ2376NLt6NrhlWYubpjdZYIMEH6KF0JV9cJQIKTCXR15qa0/HVGSrhP JWeZdL4HHP8cgmURi7tznFHqAHWKhxoMflpQxFmt/7xTyYt+tzYn2htlcQFo XSkkv7q4FrKmapTfWZi/LfeslDfDrzH4d2topMcoqslzjLIszWq+h3+/m1kE 6oEVi7UqxR2Et++HI8unZA5VWyaoEAQimuaWLAk0A0IKIOHRcxF3pyNkNW7m 5Ob/F5lN/rZ8C/vpu6ZQuxtaX+BObihdbfMYNWVsrywt0/mh0I/eOy8UwZZ+ jdjEzvFm/E48mKbTfIRlDGmXUNut5V7/VZm3VRPuazV9U2n4Xb7d2XBaLOXu 7N76ooCAGM6dHnSRm/s9jqGaO71CPr27PWtuDzRR+BAnd3r+C9WjfNsWlY/e UdYU0uHzz1s+6i30j9eP/tWlR2Un/lOTeO5TQfrdMvpzSo7F1/KeNaQLSje/ ZDe4usqve386gV5BvQ9hUWN2fLFidAvMC7MnKjUTLY4WZhJ8MZKCz+ZOAzNM Gg5emsX+6/m1mv/X8mW33r8uR1Z7cH+vH77slO+yk48zwlCQczcrphpnWZLm VinHqCegr6hPlYQRf6bOjQY714X2zbRtZmOcH626PGnRTpEam7hYmuaPanZs XMR3khl1h1GRFkj4KC5kg23v2Z7LMMOhvsuAL8mAOhZguD/u8e21rNRp/APH Wr7suLFvMGrY3V9QFs493gJYm3s8LoC1d3jFa25v9to1uL/PLpDr8K7fROvI 6EbxnT7Ch3L3F6YJdBFK7rnVRZp+6Id3Onx4FDoQfuB23Pk9PH1vojnAtaZ9 uGSljDuo55vAb19MtHOpSgua1MKdnVJAGpgzdPo0CkouvbjChvnWN5Xgdev6 WlFe2Ye/rkSvbsV/qpF1N2E/ERLihus2T141xsUWmQD9jc7GXoNhukXs2XZk HPdCYiAqjwlPHMHoel87JaWPSLJIlJjrmWHwbmhOlY4bCUgqDcx5Cpq4OVII HMAm96ejfjwaUVDU13XuomHcQhy3ZebdpmmYIcsL/m6pflst5RbuBskh+Lcv G6vYITweOGOR/yCg9VWpJW/Y4NQX3xgXo9x9AP5VfQaaTrhnpLUFIOXXPuse FYz+2kc9cVkCQXLl8YvlI//O/YgnAHzfRdpmYvrGgu8PAhqpFf21Jd1XgBgR y2JwohJ+kW2QB7vmoxkxK4B3zYv401057peRiogc7sRrv4MV3Z1p1sEU0Vbf yik/zq6+AKrRjbIv4W7AIz+0V58+u/05B+Hmdd1sR5lRWQAggtt7+7GWMPe6 sC9y1rnu4PZH5G/Jt66IudPkvx69zS32r8vtvF34763SM3VIE9IqEftz0/5E qHQeCx1if15K+V/gkO4g6Iv5rOsiLNyLvxpxn90y98GlYc4AMcgCmn+WKwPW 23eDtKs72e9hoj+HHKnnPncOEWH+nbgJP0RJb5LGummAY+MLE9jAz4aU9gEr s5S/rQZu9I7jUe7AB7YnvnpI8AWiZfL1Q/g4rF89TAWL9Q+tyfo33SDcNfrW d6GVN6S8wfGzKDT/OwVair2/G/r5X439tIjMJU2pM/LYDIlWvREo3Obc/NDH xvJojYRs5P/tbwtEbowpeY2jaV787W8N/4Mw8GZoWGSjfTXvRNlgKfh/0Jr7 +fHjgWFX085SNx0/7uX062PoZva/qJExdZL2RzPLLuO/4neXGns7xw0zWWjC 7ua622boKzMvDAdx/7HG+mgUEyeume44NsfVuAgHcW86ipOlRt2MYxqpFfJI OHOB2fmY374GN/nd8Dpsd7N4wkt4q5ZwFPbjq9ibOoqKzFhx06RH57J4cvTs 4wxHwfn0phwVqtvU0mTWJ2DzNlaXlr1tbSNag4ekZl48fH1Ye/LrYWb+49CI ze5VXD/VEB6ZXHnbNxl+gQZmUUf3xJP9BLrYeLujttdMrEliEYpbIduO7pVZ UycLs/lSY2OjtMCT/a1jJHJWJ2X/8Yf6NeBPj/NpEhUtaIXWyvHNO+354dxc J3OML9ub3jyOM0PWnVHale+/MrrpZmy+auy/2lkU8sZjIwnyx+a/Oo9BiX5s dOqeEVf41x627MofwzSXxr0vT9G/a6/ShZRxakxTqJVf2tuyWwYVx9GbaK4m fC2PjaPHX/x6U5/sUXsJnp8YWW2E0tz7+PvzC/noSwhvXEWNrWRgrJEIGG/d Ld+dgmreODJmiNFdaje0kxu6THGnbuafWh/N7fhfjfXeNVz3HjlvF/IomXmT py7X6wvUeBvRtw/XFzCO2hP5wXVp3PALvn//wTZoDIKdxEL4iKqVUDj8Oqq4 hgtt76ldheA66saFucwDdDN30yl4vjkfm74Poxs1XUEGLapJj8v0QBZWL5qM 0jlNx+yIxW5uHL9t495x03jz+jHoxXGhFtsCryA2RhFgGvwO9ZYGWwxka2Oa 4D0yEze3eZZmVzC1RHS7YXjtmW/4CnzcmCLptDDSQmynlxuHKy+efv4ckJFQ UBWM7RZqyzIFIweWZ0P+SMjjMIkn05EzKZCrd6OJkLC0D70C5RtNcVY3c+vX p/Y1MFq17rhwrWyqj9dF6oo0MJ88ajtIAfsO1FNjVU/lpXxq7PyQ3FxQcN3q hHnUu6283vXfHM1LUxOwjbDRydKZIG1Qjgck/acJbG3TfpSBhyTTlr4deChQ AJdQe6JGDQKbEm6AMS1gTRNHYPKBsIZKGlgRKdsrE334AP88TPPiwSNDtFvX CBqCxv9dtl6ynfCaGRYOySBoTWMHRjBjOegTjgC0yJbq8qQDTWv4mduoCTeA 38z9THez6FkEuF+5Jt9mYOyuazAOCTBMRip/Cg8D34hKANc5h7wk1cXMgUGY XAnHaB4YrmAYZkg8kO5TpgJpaBwLT4H3+iGsQI4rSc1mEisxTwYTbLvq93m1 z9bkBrOnBcjC3F5wrlEzX905LHdbn0QDahTsMVKco5ASOFoNhVtHgREUKB/M /i8FZ0PsF0v+V5q1Pe1c1xWEjeo8zDjmlPhUqkci6Fl5YayLJMBXSDYBHi1y NPXKLJ2OoKS8gQlTEKSEagqyksPCfD6C0XL2ifBCiKPRaTrKPmoHfCtHkZG1 Mfi0ZUfrKN+sC645zmSp4fOGL003kOma7e7LXtJ+413X2D3l75LYbmI2Qgze hIFRpRBZrBa9V3xT5olACuEPd+q+kKf9YhZm8gX3b3RP2J1GpjaLc9gBTBKR nXUsPwBDjr0aSkbZrRZ8CPrSwY+545rgnlCcrxMJRUqVChAg3UBpiManFpO7 IhCeiqSLjt0fc8WD3eOK1/LfQHLUAloYsjZag9l8s1yAtUCRj+8EJG3ok1ba 1KXqNc4UUSiOjaVioH0A/8B94mNioAP4WmApqIvHMAtjdlw3MHvIMlDzbSrb YaCnhHAGUXZUF/Jj7hf8UHILKS5tc6FhT44qIoCtq7aQh1Jkcnrpsy9FwjrF Rh0yegqNbQtnrKUcQOU5KUdShS+keSIgecK+q4rzE/Ua+DJw6ZwSdrA0soWY QeQXx3+bDRsoTj2Kr8iMbAbwDMyFv2E2dhAhWwOXMEb3udbSLQ+ct9AXlkQ/ 7XsMBVPHKXBBww0L6+Rviop3FeWyME64aI3AR6zJBOZCmQXoCefaMenLngfk ehQ11/JgLGIm2iBQIxxkGI1svkSZvzzMXav0SNoJ5Z8/g26wqfESyTvoie5b dbm6jw1D3DIL0WhWGdQnW3Wz+aRIB1k4GVIceqmx4wKQ5oQ8XgTfE3kZ91mC g8yJsfYtoAAAOrPRIW8h4IUxg/+atG26ME1Rc8BNq3eX078x/MHtGcEDW6kM FQe13XdcgvCEsihemJRGm0O1pUVjmI56fPSYjCZzRCaBJAuLUKM5XbALcQ46 NMPBVDWqMmxxnADGAV47xyeVdJc1i9I4Bo3H6kGjef2RY2ACcAuq2XTMC43e neUOpBPd9HlQ2Mont/19infZ24ckru6f2WrJbEIAsNLjMVXpBjpUwQSEsSA8 IlCsPP0Fm/TAHSbEAZ24GRgqI42nNAxhzLqkIL62NNaCiwimJk7Su2jNgCKU XDG2iE4s2FrdbSJeIVPDAJa3MQFuudx02vQOWEweEiu8X5kzxLEM5yjkZQrm taYTSSTBWGZguFQKj/h9smGvM/TwWlJmBlGOGBodOIeX3Mt2fBwROoTW1bfa RTO7DDOMuA0ZGBYbo8K/xikSYBc/kDpXh1w1NmtRiOElhJtmFBuM0/Y9Bsns yTGfst6keZVVEEkhzAGJD83KSnIqxqNB925Ek2EEqXMjyYZAsrG9xx2LMbOQ fZe9Qe3nVoUaEJXQGEFuV5pGwLbOOO7lBV1j70Sbrj/6CMD0IqOswNc9swTN h6pNE+Chmc9PzUbOoXFsxfz2xxHNohf1QyOXmWjrqMASwCzMXWg5UGjAPkww abK440Qs+sOijbodZY7VQJ8ETAOOmznN0MWybdN5j7vEuSNU0lTsjWPzCURa nk9RfUJUXCdbAmIlcYaGmREvaKgZ45LtQerNajcedX3Gwpbta7I2SjFvmCE+ HJCDicCzgXYzY6ek/X6OceFpnot7yeqC9C0CpcgpGcCoUmKO5A1ZFPBe8jWG c9Ct8arTOUCvtGQ0l3AuQjOamTL2I2Oe4r56gg2qrsIeX0JnE0ETv4jcEIOy cbLU2AKpAaoap3W434Cpg1XmbilxGnjq9fHxoSN2+hvJXPQYtMyfzUWK82HE OGYwluEtyAWyaBRywF+4g1qIPT6IcWYJKqJowYO+KOqiMHVDUtPxhK4zXvS8 ACvbSgG4CNPBmOicFMEpmAeFBCpsNnxq7o+hzTGggOIOStdDUHLcGaCOo+e6 k7DMnaUZonvbsPJEujeL/caeIH0xyjSPW36F9pVoWGQeW43anEYMjDAqnRuM r6gBBJI7gyZ2vdYCUwBxKTDSeCipIPRPpD7kwOSWkAzOR9bfiuaXOUW82bQB uIIfXb/IpUYb6aZBEQaJDFG438weIvy9xnUcOmRSH+b6aHvjxdPVp58/S3oG +qozRAEW8HOQkbLOyrkt0C6g/gKFDGhwx+ANnyJbUrZJpcwRWKeoVDLdutRs kdSQyu1TGqv4UNvZ13qJaEHmJWADnG0OhtEUpUetTX2MeyETgT0BgzbpWdty Sowp0KEENC8TqXSzJByg3bsHv+6RFYahzQG67JSROyZ3PeiFv+DTpYRv1u3+ 8fAHePKRy7/XkDK1lhJLBlKGA/GEQd4c0U0kTBO+iuzS0BbegopbFDbc7Aby J7YpUd2l4EMz8GiRSQSvDs1Kf9PlXlkBKiOqpSkDnEkh0D6mYpYuNV6nM0Pr mVxdNq2Vh6qBOKR5BLk75su4RDJSYCEomjI2+QN2uai7rr/nzkWZy3LZ7YYU eTTqN/neGpJl8yPsFk5cy8OeruA8Krhp5s0kGgE5EosHN0yInSXm/hHwrXc6 R904cFAoUTwfFHJHcgvAeWVTVpiZrRDCC3vDkd2CI1kJU6vs33LUrHwAd7bp aJz/7QxEq61vwwekS0LsR41AI2r84qlR5kLwfz2y6r0VUIjAzNnIbnJBPR2W b4Fo0rhAZ2jzWmVKHODiU288JDUCVCZunwAHQUmP4DRhh0BP5ZaBC2R7msFr Y2ukgOgGB1U3UveoRSI05MCCOaIcb8vNvPHw+Pjo0HAFKHzLUO3SwUPDp4z5 1ZiZQ7saWfeJubJTzqrY4WAnB2p5GJoKjGwlUu720l0R6xY0pzoLM0bq9knU xgETeIK9qOgnxMDo3KjxY4kVMBIrESL9FJQAWr3Bk7QB6pc5MjDsrOJLVJfF gxg+4c8ZnZTKs23EB07xBsifCMdQOXoDrF/NbgZ5QuLko0Q5FxF+wpPgfTE3 07ofgJKHRqEk0c5oSqIPgGxeWVkB2WwsW1lzz6jIeWG00HHA++Uv1f+0C+Pg NuLE2e5F7yj5obwacSOKQOlYME7TcrpF3BE+Ic+4ycrhoheeZhBoD7yaH22s TChPx1703GjaZoIW4cAyCYjm9WwbFPPdwEUJeWvIu9zaMCuTXe9DsrS3409W VyDdGQwvNYK1XaN+HxZ9jd1fBkmakZMFNZqHJHtiiWiADgXKNPxoSO2yCAeX 7pwDZA2PUO+yw2PkJy/S1NWcqS3kvLOQ4oMQc4G1ujvuWbJ1kPflvGMzgntb LnxuHcI9yKONzQTBVHEOYRwK1ROskkPzzzfQQDtpyXBooIn6s+k+dyifKylA 7sUgIE1RgouS/opVfDVIABgy7MpeYrir5A5phHDwyE3RdX5ItUdQJbST9LPQ FaU8PHyz80hnzsIgRq0FVlNIeFJ8bKWp5KTYg74Jyop4YmpcX2TQGZmQpgX5 WMjXLTczpMTDYs6uAI53lyPENiGXF1qnO8KLoPtGLArL/haWgTnSlL79avPo s55Sp+zcdQTSpstkdk/bMGjU7ZUkBt+SaFFhp8hkPRnlooAbbzdKPRPYTZOc Tm/j1QQoTQdhNZdgxpynocYStxmbG+Te4STS6/TK8HKM+IIbD81wkvFEJpQ9 X1S4spuexHLJPY9Kqru+upAgMBeuOuh6m7gm7LWGgmQqHU8LNG9aykqKKOoE DNiQU2Gm0UULqGPYdwDcAUiqIFMdLmrTmH5w6fAhcGsC7jXZijHMG3Lt0BsV TiaYpgYLzNPRtJCKBOL7ORGezcjAqaoVga6KN5MN+zAhvPWY2RqSjhffE+Ya 4vIhOopJb5DEYFSwFqWL+EeJcQf9B8oKkOQnSzfgh4CLT46OjqceuhsQVujf 6k9hzgqc1Z+RigJ9Gzz5OS1Qik8KxDkBna5C9G4Ovk9fQukisjg93nu/S9YH sjIbQ1BRi5pIOriwSrH7zjygnAcvDAHuoVFRcb02G1jFhFvbwp4YRqxBoyCR Msa8dMFAa/t+DoBmMNpTEl9mm/Y46SxcYBaTmFEpceaUyl2AgdPvcUmhFjzo WwiCjTIjR7u/HGCLMykchNdsahjYNuQAsxrZAillqxqDGZNYnU9cn4K25SX0 DPExmzGEQQLYPHRDeQk26+1AZTDZn8iHbPsdeq5i74irS3CrN1w/xxqShIIm mF6ONprZ/GmBwQ6J23Wj2/wTFFbHHnZZfA3rL5V/blaVlzKJouvMKTnivIGv oo8dWQSyHWIWiVSaYcpsQJ5t5DHGRoUIJHhT2eWO2qaNh9CXXZYVASwb1cUw XpWlnTcetg/X80ecyITPUBM9fv8hDxCM0w54ZPW7j0rVgeLDca5yVEJ61ci5 H2MQMQMuA1kXDNbyquzMJkxInrCBbHcVeSHG7CElKEoQS4Fu4SSEmSStXkSa qT9LVdrdZOc43g/ro4P4lszdRVMCRQDNxepHKXqJJptqH8O+ckmB8UJZeZM0 yz5Z3PqIEb/dWKnk6BAHsRCsh5oFkoEc/yqbx4YbDTPWz3fR0sVU1Qbv1sRc Dql/NoIj60n+iGGQuaQA+z5WOZMfc4q+Jqi6If8RIY99R430jsiTynFv8oag BAwnoe1GVT86Zd6WTYttzMgnWwaY1IQMoSb5yXtY9tktJCgZqntY8a1ab53N cmGac4yXNe+B0agmqNYMooLj7tSwhatCcfM4fpbH4xgVYj9Xhppu2kLEIO7z EGAc5BTruEbScFPGm+WbTOS4p0yAmAKnoDdkOn8j6Bnx25Noslc1BBSfiCMn j+xwkmvGjJ37m/rfojPCr7GaTZkZ3WGa5vRuLyXlQ8dluuYs+9MRkScYTebe 44bm1cPBBdtd5gQB2uNmQIYtzKKT0b7SYiwHJy2Z2S86T8lQloAOLcuWmcpa ypFXOhmbwwfKeZZC5qKQiaMP1MCIo1LJZVUc2KgaRBhFyqkKGhwM8V0gSiWf oMuZM1nb43JfLhXU4qLDwHqWJSUDKiHJULE/eRqSugWx61aUW00AD8rSCo2g 7oc9Kq93adhJr0kCkwILfoORxNt8emRfGhI5RLfs0JLLqbMwnJbp9a+Fic/S qvlL7b1IDlhmLwmFvO1s2MDfJ3HUrT9A3pZK6oDL08GFgfFhBhd2Rkk+ljjx r6Ab26zTlBMHKUhq503iz2Y5ocpMVwwv1By4PQkIK0TT8cQKJMmADDADkqSJ zEzSQPURSLCCqFSeRO/lCMLMZJZRWotY1z3MsYA3gtAeoW9IY1qmdZNBYCjH 5GkH2WjvfknPTSg+0U0z3hpfsjR1Irzn/rf3wU8CbWB5hlzjBeFCkCyxu//1 V70soPBuSt6ATb1psgN6gaAKXHjTldVz+K825cgsE9WEIabRQ+g/Z/zMWYgy xu4kkiK7QeEzY1bMrXedSWoILWCSBessCxZf8cqHWAYRGYWw8DSLcExZB8bK jkbXQMU6Q5biWvCqk7XpRMl+/7LhV9D7F1DyKO0ZvxJSej1FEnPHgJ1k30Hd X2w3sJhCUAkhA44UfVoGShvZLzcfe77TZIScchgRTAVCEhTxYFiMKI96kLm8 G5WVRwoOag4IoTCas5ehtxTQ1LTfrDI5dvMoEYQuosncm3CV36ESkqIxF2OS LIL76aSwOKk58TqDtRbdQxmqoQSIQQWKMiADs9/gtYACHJcDY3NuFCKAipZD EUaZ2YphpDO3c0rpkP1AzWIQFlR8lOSS5yDeemge3OX+qyD9qilZ/WqjvDxQ AWrEJmAmwloQ2pjA8pq6hsRJTEily6j6CEwczi5QmutO30tE00I21PzpOrJ4 LUh5FbHDxlg/C6e96YimK4lmga1dK3XhKFkNRGPo5ghBiqTTXKxBSTpQ2Wti J5IDScVsjB5crgET7SrqphxtoUIS8qZqImPvYSAdRGgfyRXAnrOSN8fbvwpL x0IIztCnq2LnK1tndmcK0gUMnur+9bnyzEioozY6GL488QVH6mUV3naYRRZ3 r3RFToUsMXRHyUKyLV5KqD5ZSirh2JXKTKQg101Mshmiv4ZS0XOLAcYOpgJA YJFyRlQ3YuW/ubVir1zLYPOO+GIHvIKS05HDgL5PUjsNh3A3eM+H6McR3p7I FUzNSWyI6wfTst0FNfwkTQBZwbpazKHHpauL0TCsXBAWkNlIp7A80hHhVrdc wY6lcauz2fiFEIX0WsYYPB06VlmQYkbFVQAGVkyBVmxOeYoxre6US+aYoTri 4yQMG5+UyjuLBi0za4IUi6/I6Q1FbkNQJGlofwwg08MdSRAu6zrV9+RuDrHg iotq5uMxYLp0cdrruf1njQfUC7nZJ41c2QP+KWqaVxUhrjSJeJH7JMVs0JZ1 xaLCwvXd6IcMc29a9l+BGn3e1GIbnS+cZEX+/Rls0XUIJfBzqmORQKSR6VIw TcdNnbhRVIHdi7bBdRiP8PQHUzPQCHPOQB8rF33ocITthihJck9Wlp9DWJjS JmuXYUaRWAcqphi47kRJ1KdUe4heAl9FR+CYDIg58yayIZ0PpZeFMwhpkJWP OykJksgJ/JC/VjLSrEdaSy+l94Qrw3dLmVk6BwkqL6XOgrKVjF0n3ySdzX7K nSno3AFWQ1KGRTkhL7b1uLidSw1jxcx17jF5YCA46A2KxACCbYqORrIb99Y3 /iepszaNP7AZJcR4Oc+jUOUnzudifeZBcMIprvabmhx1/QPGcWuMFvGi20Cu TelocFkpzE5nIXE+KhA42FicF1RrEXGM4CGC0lhxZc4V4Ani4hEkHdpz9vi3 jYu4olkqBNIXkWIW6rs0R0qHToM8YuefwuV0gshTYDx6KteLcO3CLZ5doyWF WQ8VfcA3GZI/Q+ogJOrV8guqgJ58zK+2tzLJMGHT0DUHAAyLgnGJiSAxlhVB NMqrhgOd0Jzkb1Pz/HRsLgkofVa5opCZUUnNZyoJ7TiBhyyAYy7LjujoxKeP LB040TywgEdsw1HW7Cid9jgSXWJLzF/Mms+GUi0ESkGcSC6V1tqaHCgjUhuD N7wjCREcQySMDqSloExLJToSR571cG9QlpgXY3HqC8nw3OEzY3DFesDNxS7K hcVo+toEjFJlN+oPOoxP5Q+jNL0KyE2myzF05MgeKAZk9bXzSy3wmtRzhGaA rNT6AmXNpFIaEkvF3HMqsNwZgY4Qz2eYSxs+t9TAPzatPrJNo1gmOQWiygok +dCZzvT3H/NgEs5HadhDlQ9dSlGCywOOvG4lfu4qIWbO/+Wp8FfC+KaSgxf4 YcO5jbNZtu0oyL6kvAxV9uRrBnzUyKICYaOucsOxqLpiHN4XJRU9CnfFFXRh SbDIJ80+G14T2PjbHL2kklcAu4D3EPQBX9CCIy/Evouh5J5AeQBqTAXxEmYb 6DqFCJJjHqA1QA5AYF1LI7NHB6UFcz03ElJeYn/um1Jbh4nTzAegrEpXFIuD FY7aZvlzcrhKbaBU8JxjSqGvAoCk4vIj4u56eklpho8W3xp7YxXRx+CP9pNt J2Ex9Nwaydzp/E07SdpjY/n03O7ahFysmkuHcSeGS1AWIV7yx6IcL8qCQVKM 6+sg6KYC43I5vzqfGJwGIM5A2BJApEUfQAqSsKQTvZg/4YvE8vGThxYC/pjB ZyVPI+9CADR3HmItEBdoQpibWE5SCsqpgWC1Z8aGw9IZsoMrZ8zcX6oEzNV5 mVohrgG3vKgzrFeUaom0G9bRm7ErlCyvcQrOBEqNNxcsGQDjCgopVnMPQsIT BujN5ziOLWlKt1orLNeB66J2QSDDTmegCnYAF3aDgiuPWOMxuTi0Dw9/kPo1 cudJCjncGc9hpkx/3AK/dk2WYQi+Jk4i3Aucw17mLivNyOLIqSC+q14JF8d6 yVzUAMxnG7YTAZCBcxZY4kFiYXnQ0O5iZ2LmKoVkq4hx5xlQKPEMgfSM7k73 VIxqT0AGkoNgc6Fs2mEoKheNIm5Ua8WjaPCQdodm3lDSkqUTrshOe8gxAr0J g6lKOze3YTJ1UZ/6L6HjeDQC29W5IWJfqwkwlHHTNSdMbuN8bLaADioiHz6b H6UiWjg1shmTue++lD5Zvlymt7JInKwSzw39nAZLPgjiQBjEdochWJuQy/Hu x6vUOZqJVCpWz50k61JQzaIT9aWuprUXGQmaWXAE8rN4Ra1mqEFKs0WWHYjI IaWE240oSpJ8GnxbsQnEIc1pcjwlJZkZv4EuXEDMSn/GUzHS2rca6i3ZMI8k 9b3kXDzryAYC9b5IF4hpjx0ispO1dMfSx/C0IaZ3BVSimGZXCHQB/kkLU4JO WiNQAJPG285a1Rp0TNDX4WAkmdtPhvQGUFEm2QZXvm42KUdYLXH3YgGGhXog PHKofsoafcOsKW2P5+EV2FAKCHtBOVNiNPdw61yON4gWM0VeVyBecbpH9al/ pH9UneI18QQjWMZ4EC3clMAXAFZt5gTHl1RpvVC6+NXRRtDS8/6gOrG9My/b GNUKGm1iNL2MMiUKvHoTzAvEQ+VaBJsfGCpyCL3CcUYzsCdPxwOfR6I0jCKw 6UtUNkwP25pubzBUI4ljoRWWY4GQoLjZD+KeY+QShHugvD+lXZEgg5mCpnUa iPXKxCoZGB8QfUcFKAKJDZbMT7IkKlX0cTJkM4DchpRvhKFlcSI6u24c58zP KHLf4RpVCWKALgHWIQZRWVKKUwEZDVabYNmlWZw/GZQ3nagLbk24QYAkZzYe xMkI/eeYBokoQUBtviPQ84wicH2PK3uQnZHuNoz7VMGAXCZQUbD1wx1QLXYk prkIhk7clILT0JuKwm1UQZD0kYLKg4T1iLNocfcDf8H6imgEg5hCVflQbvMo HsdMr1jyrIos3CEF1hVsLs4sirn/AfIH8KERmjrNzJ4CyJdI6vGqlTpa1AaA u4dpCSj+MHYfJ2qneFWSjzUt4AtN5ReWviwObo+fNUwuBf4kdWts+iBpj2w5 oLYqS7daonsgYzl8WSr6I/ILquSfYDI8J1KBvmHd+bwClw3qD9hsDIC5juZ0 POKuQJNEXV70lfBN4M9iNr52Ndmh1QmgQo4HatHLAmtRVW8Pce435jBe4mEs Zt7ws+Pdb+oJvSlMDFtK5NPBgI4F0/Rtgn/DFgNITho7AQNV0FCTlWs9sKwJ maMj7oAxBvIyWc9+qXAWAgQBYSYoNtuEzhWCYBP6HDMXftqTvDW2SVzR1ZUg MJTSa0vZHDYFnhFb2RQFO14cZvrLZNwClAWUlkWlsq5AvqxdDw8hrWpMKDf1 FjNlPE1Bdc39+gYXZ0NrccHJ2pgg8nhVDkTVyOS7dvh+giEhPivQyDieUlbJ XGF9peZe1DQsQZGUOcxXJpvFq3S3AzdJx4pHXGJZpw4SVgDiVuo6Kt+8VH5F VleFIkpWDGsdks3pKSiSzKddsKp4oAT5zMqn9UeWN6sEhefV9Es81wJKVmCk yq5gEiG5VyRle4n4iu4SZzYctV3ZY3loNLVZo4yyqKShOlQB2kthAoJ3eisk k6g25XoQwWH1boPQDxUjBDaulEWdOQHByv462ddndXaBBGe02Vt3V8FBlHEt ZenoP+KOMmTYBSogBuZIjOqIyBCfBiiWSA7AENOYyVY73KG0eylBh1xvwBfJ m4EDT6GBnZneUQjhXlUNbawmNJXnpA09mo49GR+Wk1MeVe5ReU/ktHx5Geg7 Sj2DPEc5NReaJrMwca21LbKSy8Og/IN2ShFoX9WgzkGetZYZCRqKuzavqVOA FoXxyCUnimsYPQ6gOhtN/U1t9Rdbar4VhvNwdjfQU8AaE09FsVM1lBCPy0Ny ++VwsI362HLwA2TbBDZLFFI2IRECpSEeGtV8Jka9QzQ4Mk2oliqB+YKVZLSq WFLB9G5YKzCPqGjsGvoBVPavvjLOyiSgU69sHiEUBJOmbVW/AE0K9Ik2Lhme 7BK5wCUu9FLth0MuKOFki52GrjBQ45SyG5TJVGM5QHRVcsvyqFEqwkZ9TnnF ADywH2IisdGxtpSCt2VUKczi3DBnSSE15CbllBilf3Xdk4Cbj3Us0Qh5GeXM I5JrU6cVQA1sY5CGI4vPb9N7CIhaxQasdxuVRnThkErK6WEJBtDsXEs5Zg56 2eanplk55xopUwF+Sjq/vwy4H0uNl3MVlFMpNhq6192KJvMT73NQ9CKP68C8 ldaowJdST/3CQpeBCgQm77kHAl3fx6/7dZKVWUklNl9y2oI405tbSV1L0tK6 BTGrLx0O4EN4vpgkxnvsnwfKKkK6Mt8L1Pds1bT42NJROmDfp8Ux8yvQbJmZ zIE8VebeIw+i1m1LAWGA6besXO+FYI1DiimBzWstLEsH0yphYlY7VPBAF7p0 NDL/1USfRkSgxbyjetHgCtRE6wQN0HMJ8twmueNGWihJiYF0ERECIlKVRTlg BzPewCu4Z8i6EJIWzZQTjvEIgH8wTUZp98p5eetnXipuYTp2eYV6dFuKGAiC jSBdI0a2wC3YkEu5QwQ0pGlwDZcMKiEMG7gzworxIKDyBNDvqmXgshR0YNlz 9wiqjv9AbIhOVxza/AHKwmDXkC23SLoj8NzYOw0sS/iGfdVVhFumU/4sQPtI 6gfUvGcppyrMYofTIrgG7BxXjmIwFmW7AteegRM8Qk5usROSxasCbrdd5HAT 6AIIt7q2HTF1NAiodR10C6PaPF6UkKmRMxkoPFKSow6KE3go6Col0ea0R0Y7 AOHHx0OcjFIYaesxA4/3vx/mQ06tSsiVZO+kpPTRdRSUEfk6l4BAhhLOS2K/ 7LNCuxH5snIBWyQNzjgn3xkOG0nSSqfsi96Lb+APJ5PaugUf2iW+mU4+U+Z2 HbivbbMAnUVQkNiCCU4vh3+HSYRIt7KlspMBc05tVxqDD9MYxlCmFcMyGXSl eiERxz/px4Np5vDcSAcuHOS2ZpKMhe8S/wQGW3+NQyp+RRlhdblJ/JhbQCj0 2pB+v9729HFw+EGpGYR6oqJW5KVcQ2Y9y31Oy1ic4g4xvcX4zuFoFmLVSyOk y9tnlwrMjeRYOLqy8hxZMUYFuP5cdRnosQUXWL86CD7saQAHB9rUurJ4YYlw HiM/n8e+o0uvLLuottcBLRaxELrSUgjzedWDLXji82cLq3sbNIHLIwNI+Jgg YgEtuoiLKdXzqYyQoI7t+wBq8G0LNV9+1O4FeneTmtWJUQRFyvKw88HUPI+7 wS1Dq7TqKq7Z5GtUg1ENBPsyHLhfrnkkIhRQj/X3W2/X9zdXlwFMixvToiUT cOEwcUu8q+Kns0EMDqr1embsXBQv3XO5o9ucwiSI3KTfpyBH6x0oE8JSw/UR qZXPPsatF6vEseRusQnCaACk8HObUyjsEleBRSJpHVoBfgL64o5S77UZQg+D pAIDQJCwVELQbRif0p6TgicOZNDV+xvBBU+KysqqTgipgrcBLFC/LdU3qEae QOghUeF0ArmLoTLFlpEHHHlNUqmkLMButECPTsshLV/FBRthrUHlYpIoospa mcOIqS7CcZ1piLRPx0ydsXGHYvYhWBUelQO01uHqU6KDIQ+hzlqFS0iNbxrm YGGBEffugDrYUm218uDLPIweFo9tQpCrsY7TjKLhqvUMBjIUo4QxwGluTm2W lEaoa12jZsu42Bq/Obboz+ZnowehLYpegVFQL2SVVcYdkmqw2dWd1EQK1AJH CN31QCcOZouuLtW9CrXSvpVwOKRTsW6RQKqBXzGvu6a5Ymvxt8uR8BaWS+MT wKRHGSFWq7xDvQ4TNhGldYvqM109DEKvlWZAwDyOdrwDiseGKmKKwzqLQj4Z sCYcZ7ZTjGf3rI8wwkW4hhaGQTq5C4wy8OCI/H4lzAtHFdQ8ZAytsljKqXXZ shr/jjBKvzXFG/lVPNF19kEpmkxuFR6kJIHQ1V8Ow8Lhgnqb115NhpuCc6M6 MA4bE/oFyNfO3MKoe2AD3HOi2uu8fNGLWloE1hg4zmEpv0RZrmEKBUJrmhwA ACAo6YuaHQBjVORk7SvNwHGiJJhtR0msu5b4djfOjAS26a84+0rOKzkYUAI5 MLO4wN5HubXI2PjWookhR3TDDsA5gS10Hj9S9236B24rqANcaiy5eBArnoQA UaW/UNQgVRgLx6XFOVbp2ojRdTFL7RdUHSxSEbw3iZRiVBVH5zZInEB2srYK UxxhmaIoJfYVzr2WHjVARlhVOBIgQlF1sGgOSiwjF8BzH65py1RF2TA6T2Dh GN10IjUO2qgKPEbgctHejCupe3wHSJ2SIQNL6G5cKPbx0jodtCNm4DTxCRVA sxmDUmzOniXsmlbncs9JRttdUDtcr4Ib+rTb6cgoqPaD0uWLdWUI1XGdfuP1 VmLRFPikgJNVkcMa29lLg4qskqCWaB3qcR7c3iVRjRXqqm01HEUvEpsJ1ZNy u8B1kpXqXAtyI2yoFHrVFOsdS1PFgd1fA+sFXASIqDViv8MM8WrlMOPGlygt mv7XjaHSB55hOE0xYhGhQkXokQk5I0uLOPTAoVnNuJlU8YOytCSRGBGdqT7N KjvALSbLCy3zXAaepEiJXUnVeUaiuReLFPG/BcUI7KX6MgmXCc4RGho+5fjK YRlrTlk6+u/Q3A8ccTUU7mMwMsSzwiEkLoCAoxiLlLKPsqy3wbsA+qlLL44M AUSjRMiWU+zko35fDYcxh3NRAIIOEEXaJTG2UVAzEx+JmLRVb5MWcBTbL6MX 5xJMxUqMSEC1Ua1VqIC1uE9N2xnPcY2Kk0tEdYXEAkaYovlN0SKxdQkeMljN ypH/4I1oNpwow7OgEkgrXwLEHFFeqh9Le2S0YXD0WiEq9YVYcq3Wh5VmXvov O7CGXJKHPRmo/JLcnwyGUZ/lw4XvtVFoEaCqqxGmavh1O0sY8PABGIccnMnd OqhtaMk44iBObGNSCw5Y0M9CSyqYLgYXxSgvKalYddtpbSRSvEpaLpisOfnt AC8iNDLXXrcSnD5rqigv/ERJa9jWhxpVSRFo9AXvCqTqJdZzrnd0AQQ37I6l O+Bt7DmfFmmSjtmTzJIJVSw8Pbq5/H2n8KNWUvK6ote5prVrWBI03uWh1HNL tBmmZ3AzE0SttJklDU7HxtRbLHdgU6vnbH6ZZ+x+Bg8IGshUlcP4RJQMkbK7 DH3NteaL2XEHTecy9ilPCw6guvt4bUuwrDmqrl9CRWXg08e9KL8q0on/WJzo 7iAKUc5QwDiXtEVfuJAdDuM3WTcWOBeMZFkYUDO2qs2ANEjsrOFfCI0yaFma MbXo4LzkXVdbFtQBWyvM7m2EOK7AvTLioIbHW4TPGeeB6mXjzE60pIdh5uKI VFgOwSt1M2x0GFgbTJNqLl0TcUohdP5hieXqnZAp0mjqWQKyQUgvvEjmn5aN J9YqhpwSuRWuBra8UFUFSzqmw/pqgm9wGE7QALT5urZAQ3gTpn23KOMT0sgF 56BcR0k6PVMuMay5BmZPkHdcu4BroBIqYHssqrvkcZSWwumyngxQG4IMTpI/ zQtwhwWw9ZqKhtMS88nvIORlYwLnfZKMWkGmAmWB+Q1DMti0SOe8ZBw2+UoM jVkqUJBksYOrrgc6wHVEkd5bQGapksHJAiFkVi9c1ypncnoLDfJuhohs1OOH 856rLsGwKJlJHM4laBYls7TYsbCEoT0lLMA1hA9v+Di9sBrGbkUfqOpqXYEV tB8JCt0TzyFgqK1X4E2qAZIK6REmRiVfjCAivRlmkZ/w2E0nDoJEDBxKb+J8 xsYlzf3SK+n24aUD1alLyn1c0gZGZJC5TJG3aVUmE4DCxi9li2Eb+rJYXW/+ j4c/7Kzvr0tYRHbyUb25sWOtvpKtEesfKBRdhfLz6+fzSONtwwVqgf4P2Z+s U3nNcVxuYEXlMvZGbrSf4OTobRMtax/8rexC06ZrNYDr8sgkjXiaTVJmoghs BneeEPsoyOAuLj5f/rzZySPL7EQHLkt5qwlQqZzk4dAtZqnMQR5UCMqiOfAB krBPA/e0QYT4Uc64eE582hPS46hWKn5vi15EqawZSgBKxMLPkIGKwUQNOMIm jkZ+wnl4nNlfJggbaQDUj0di+GGNgf4QJWf5xnvZ8UawIr25oRFOBFMQ5xTw S1ySU+irJjTTpp8R6RRx7w6gdePEvmHOVdkDMqfGoa6SDh3iuIsQqt1ExsRk T5hvWvZUsxW4roNaeztJZIWqCKWSoHHM+Drm/o0eDKvtDbhADrDZaraxi/Ck FL1VoTZLRGVjk9o8BP5wQ+k44kiMnRM1DELzq9brFB1lb40pBuGcmvDvEJ9o gbHGKAGX8N8fzEOXsjj5CnWyUsmKv//ODLrFj7g0hwXeMm6vZFRLmA6KLwrN Y3xJ9RjsRxDe6TE+On2/DuDY2TGQbsXmGIyNUgHdFZzhlxESLy3Y0cpDs7np xKXHNgBr7GcYgvv8qf2gDbBudxsEQytC136Qaus1F/G7V/li4rPz8auvIQh4 ad7NWjVH+r4ihKJy8RXUXYqCmiyDpT0eZY/A1xouegNU5NATBZPFPujD7qLz H6CvFjcQkDauTQSgbPRH0Y2EVnQ/BLqgikm1GFG3/noRajAnZMKHLVKIdQrn 2sAkDRCEZM0EaveNao3srjHN9GM0TDzJOgsBu55FMmbKdW1N31g1JOR0M/ue J12hGJPgB7IG8FlBN3Ia6SIX31LDR7fHFdCJ4A2SucCN4LhZt4ungkRlzMyr Rgk81k0dli2ZLpg7f4QQM5nX2Q7VcnTHoeek8KGhKVUdd4Dn6CS8OKAsCKfN 8sfbYpiD4U/SVNQs4Ed2boM7VXLyrCOawj/s36IwYxFNyoU9RIa1mRm4FXpz nKaVs5HBGDsZfh87Q6TCtUZxcgW59IETTvQLG4MU9kCSRiekhDPwYJA0kpQc T2gAWjMZCEJaIftM/tjwqus07rGBi/523y9vLk3svD58XSx3w2dZO4Y7hQVf XE3EeNUA9kzWdbCoHU4lri/f5waLUQvJUPMeuWiwct3MRWQaYGFLdkcZ650S HtiTbVG10wmX4HCGhQU3a7TbR9uuEihc3O49z7O+NBGEtskZVhSRMbLjA8jB d15mhnX4oNkd+lMrVm8D3Cmi2lb7uGvTxKjt8jreojL6hJoObphk9tqKLAzk zIOIkny9lh4yrqXlbhZPCoApCHvs7kcP2CDCLuiVlcIpUTeKFCtWedoyLHqD KMJhJETuYFbJtwt3yizBdRanCnAaA1nKJfOUS2YqwLgZV9/Ye1AOiJpnXtEF eR9tIYHeUJ6d0uExA5TC9UD7iFcAJ+PlGyBUL9Mdjcsp1rWJkexHbqL51YOW x9m8oVhYqMomsaIimCYIoUKl5TQZrq9o8Ichpm2LFmKojyesOz55iWuKkewh 3FAmqkomhYVUZ9Vj4Ft9Bb1WF2PrXU6TAbaCQFtcGuPKRKbMN/kcHLnoBk9O cDMICgEijOaljHs39fqIccAQLOQl08fhUM9sggKpFDp5t1EFhIeKQu7IU1da oQv+iGK4Qk1nHcJd5Ntcm4y2xNh9xKFxFHSQ0NHXvwN+qR/zanEFcTaLbWkP tBkAVh1fPL5noCtUQiVkmCBbxmvpkCAIW7cOoovyIkQFGMe93shBkgA0g6T6 kJ1nywxUGhyLKGW8awBH2BPuFK8vB5MXZakopC0+XHTQQq2+5yRiw0fyt4G2 9zSD1LYPP9Qy/xRsNP2e4HHcdu9zylUjW6g+PYDlFLHQwD92SM8BDxihECfo RtbHVW63Wk3wgItEtgUw7sAFMZp1L3jNwTBLpaz3UcVWoffC1QwEdVHiEodQ ByF2g119Q1UgwidUdZRl1mTdl6Qfui+MaBlINYoWeoFCv+k4ZE3lxEQk+/pS QF0KXU3ORkUyIGgQQGJT1ZvcBwNbiBMYZa3Hx6Mo7rkSmUMyNh1Q8dj3OQTx gjAMHRmWAhuB1RLJJEDzPDg21NUf9LLAsIxCHg9U9+JFiHxNhbGaoH5lRSIC 26upLqFT1MjuZlDdRvFnw/+o+62SWZSaYV0nBYPC6tzZcplmQcC8DQbmLdV0 S8WyzfRTBGlrsayMxXQOdLeDUxvuRn86gmrpYEGitYqJyLZ4ERHr3BQGhnUT gCpF/FN6EuK3Au1848NlO0ZqM25RRzRSPfC/IzWfthnemJobKdCPlw/Dw+X4 QKsLD3ApMneFcu2+UE/eaW0uxVHRb6XgfGnZkYp0EndzaB8fihooU8ebIzhU qOqtLT8P6IsN+CIFm3jBrsgJ90zDEzN35NxWL6eYcCxwcBkpiLlIH/N0qGBO 4xjQ03oaa8trjQdQU3IA0vOBAl1iMUA2B4kJ/8XnZFP41bvygaQXZj2zd/Bv 2CFLbjZMZpTupLCNaTKGE2fkQ0rIdYCdehXgP5h2jFrs0vF82+rwoH2sK740 pTIrkJSBhfO1AILlzZoahbcTD6aY2mA4udlpCH1n0SxzvTdwVJhGQxee8WG9 2jp2yyH/XwRqfmLrlvBNWZSNcqnkdHuztzn+y4ExN9dcAfgG/hpWm+oA/HgM XDkkTFgMtn7Wa6A4h54/u8+nGA2ARsUd8ZOLq40ph+3vEgFxb2NyIDauge1k gmkwIwB2gZX65VKWf1mvmADZ/OPhD1Kz2pKHWvTEI8bBLlyTdzHXA33fqOEc HcPRQana3KvCxjkj35ToJ3JuJk3l+S6oHOehbQRcoY5HrhzX4gt53zLbjJ4m c6WBxxoGDc2k5tb+Cxx523nX6032QbRVNp1KVn9CjA9+8GMeOJppYKcF0Dys bQpPeDNeYBM01hfH5QIr/YRxph3gfeAI9UcuYxOYBbvsD4izOSkQQvmTvUKS Wi5KSamynMswui5NrOIi7CP+SswRHz2eNsFv8Rdq+GaFHe6zxTLXCoRrWb8X MneYnXleyR/YQmrO6CgitetMxN6DsiqY90RgjARrUqX0QVmG88npPUid1sJ6 p8LsUSqoikmopYGIGlGwVRGu+AS5Vh4WlaReN2JuPeJbrORAJBxxdTRRafPr XVtHzCtUJoG5gl4ruJbwk89AVnWP15kv1zEn/HQEgttl/qDPzyjO4D+1NgwE JMDzUVM8Z1VghIXJrXXmN8ZRlZeYl8hFKq42w+intmixqWD9c2meUAZBmdV1 qI9t+YgYJFhWQAWtPggY8qsq3CBOP80clD4jDyJMHmZOhI0qbBV1e7F4BDX7 n3MKlltGAn6AHDB8BB3RoQswW6mA6AY+GKlSWq/jaKZQCGQqKiGB7xhWiWVz KkJv+gBgGDO/gaB2Ji3HidXFdhI7NRDMSBFU7HZ72/igVPagJoSdjVLMwsNi P3CzO5ivkjEs/NcBJGPDoADDDE1odEyhpUGZ8Gvwc8qQRV0h+FqrVFAcG5sa /l5dScDA0tD4UrhrIxmkjzawsL6EzeFyULgXM/eOo5K5+k1FF5OCQIzBJQvB AjRkwGMAGN6WmtHiLlWvSNNB6nzA9KAg1nV6QprUbQtZ2142nat15a4u5gBU ZN2mWYBeYVttV9sIO0nX8QOJpVbwGhqVPaHoYSt1NL69mXF9d2iWq+DSQ2QK mpNsT4BZlpMwzpzzC/uFVqMxjNSGPJfHRq9KUu8BCaaT8iSo0M9VGzB+u7Tg 9poilSs6b/Fbylo02S2GUoM0+cx1pHbMzoFlL67HceYGdcAWrHfWeKXIbebt MV1MrxkDbjgoAF4bEtofKC0mP4NrDkMcPbD+6OaC66T4vGNzgca+JlWYMKL9 beQvu4tjey8tUjcDzshDxRaS8aRC3mcZzvfHSi2pgQgFSi4u2AnXt9dD9HfB Jknuk4XU9F63TBV4usKRxS0suDlXbT+0upo2dKuiYHWU5yO2CdyVeLZ+zMvd 1EowlGLCcN099/gAduZ1fIptIhMJ5EXaPhyl/22vk7ZuX1pp6BvWptFI5iTG 24vpZBHsKX7NQsw6+CqFyIEt0AQsy/W6jKXBpSTjWNAJbAkLfgHoB4YYCP7V XWRzeQfHCldnLlXrFabMvQoJ1DIQvzOVq1HiFdkQxE1ANlMPNtlFgcSCk67+ ijEuiKHrlcbc1Q1XJydCwtHo4njZ0pquzIyEPUIz13Y2DBhsptq0hjdUqlTq /YtOBzhKOZZySPkGJTUg458/c/qQFcL4A2cLWbTRTkRIg5gvJvcVF2fLAGDC 8knEJMnITK30/0W4pGqDVFgeqx8SzudMCT/rG7Ykdf1NpPB9JOieeL0ZEIKz k0GOKQCCtJOnUEvfIPePi/KGdnMHkH4HGfxxamvV6BSsUVL3YQeoxuAQ0ixS ZFafQSiUg/n/b+9bm+M4riy/16/ogGKXhN0NkeBDJGM4G+BLpPgUQFmSOQ6i 0F0NlNjownZ1A4Q19G/fvOc+8mZWNQjJku2YtWJiTAD1yMq8efM+z6E+FDaL k5fGu4gZQ7uFcq70ICJ4VsqZrp1QGkIeNw3NXx8leQ+oXIfpKPZjkBnD5k3J RIADLZBNEbGaBeErLPmgmTeAikfrZATN5AEjDyZPdfxrpsUSWhJQfBxV/EBH F2O39BzpakRmzbSxP5ByvWSfLtFUwSDgx65EKOz7E09gCdh5GYn7jnkcBb9e QQNjx9YYQPnSW4zBsKmLbRUfwdTY1n0VhnhQzuhzXL/rom4/CBWJ1BmHTTib KLFfQg62NXhVLhbNGXEX0ZrUkZ88os2D6HFF8RhpiyFsi6ZeppYy+UOt9oQO qdNAu3ok8MzVdXqv6z+icuxmkcx2JR3IkaCMKF84vHAULF1mA4BVP85t4WVU GYsKznokvlaDr3d/XpWGOIPLIG0rYRiiLl0qtLBXZQzuDr3CGSyg5HVxr/UW Hb3EyCbVMcdIDUxIJUUei3oC4e5iw4DzalkVKOy5CBCfl4XOw/EWPIBRrBZP ipIk5POEI74vsYVo5d4QC1SQB3c8nPCvwsnwKCarerBm+pPFK6l6DmfZpM2Z 2OHU0pG6QFd9AdzdZSRCsdNiSOIr0XDZErEyRy527hBWhhk7MMS+mm4JBBDj kzisZNzAceHnBf+vJlEz2NleXLPCx7/7kpYHCpAYJiE82brC1XvQqJ5/dN0a wgtzo0DPUbr35KiMwRczkhUYZRzeYyVt7FlayKsPtagLiCJZ1hxFTDID5Fcn ASOpujvlEwLaTgiOhoVGgI/qn0p0eLBuODlSzkYuplNA7rwu0HnJiHXNS0Pl Hlf16XqYOWWItkjs+hwHPQ5rQk36/Ut4ptBqgrEDTV9wlQJJcz1f8ZwSJ/oZ inTOSk5eqce1HvoQUHNzRQaSkocdV7E0jkWoCQOicOosV1qxJ+ATfdsThUi+ IjZdhQzydjHo7cBxroB8Xi47aTSejgdyMGF/C3Aa+D/FALdko0i5H3FhEmYM XhiYnXdcWpUhxttNOtSsMZj2+zEiOZwSmDtIPYTJjaTGalYRomKa88NVmC+E HfEeyHqGFQxbIo/SEFnZYim6ZFAhx1NyRkhB+briwVmyhrFtJXKh2oiMiOSZ Wg4XRDO4gIYCGrmkCQLxlLqv6zaeTmkLOMjSPlR8hGvcTF9d8Iscj5aeXBJE 6Kn6tvwC38uApcDeQW0A18rE/ifbYJFqiGwaqIPwbK4Mukj9JrTJTnMY/1bX HE46O8OyFNX8tA5e4jEqUVwyL2hQQslHvTUficOLlYpU/BzQeosxS1o+qTbn o3hPVOTL2NJFSqPvhBZ8b3cui35tPxnB9tpZspFJfN3lf8Pr9k9W7dF+v/oT ZdsWqLtpGyCcYbuyFZXsPlyjqMYU+8d5Tvm7PV/KGXuSvFmr6j2mZWfnSTkp DmzmdkpJPVw3lFTrFEkVmSDTaCPIugq7NdCmwh0knHt64o3RO37AQAx1mxKV GKxYLIWVwI+eiWvQAPVzlsEhTdbR0jU+oseMcnT21spmecrJCflEQPf1gbnM 88ofFi7mXdji81h4vEQvcjCgmq+OJV5IbtgWmlKTDIU+tl2PxhOLlAjUxpd/ 09VRNIv1ciyVOeuNrtwYN8GRCh/uBbYjo/P0GGXyrpxVwMsq2uNTcTsr2wJH FG7PiSoHORFU5tP7zdlTTxxODitMknSQBmLBnAew4lZqX2xZoOKnjcVmfa2Z LlSRfKN+27lkGpXJoEOe0KlUfrtmTTgcuoyllVKWqhV2PIl1p3FADUkL4+T9 CIJlYfX7V1XN6Xbqx/XYpCYbdspcPaquLQ8UZzDqeytrT0D0AHEfiR44Ez5V T8SuYsiSvaiLBlaZYX46ApEOVROtEldTM8GQSJq3hTwaY8J3J5JODQrFY3qw ZWbSRw+SR5d9D5avLpedZyO9qV5Bbu4PBVbM60u8px0k8OTh70fB9WuX3azH fFKgabx1F+2+7tqtdQfldOrusL1xlQNj5G5DcQmeyO7rzQHxCQlTd4qfHnVY tx8eHu7MQfdZJaz/SXLAHVj2C7+b91BSn5R/jdRI5XUdHeu4Ndmzndz/XjsY szcVGMsUtbKwBYO/+Ncq0xvICK1xJUZuqvJvvYpBwaEg8C7TphFyc5PRjSWV v374LKc2HUofyP5ruiRX2uKSc+IqEeTjKm0lk2xgLSWYttyW3ih65hK1ZOwF OBt9zbspv2BvhTc5Zn4c9XaoAJwBQHNLX7x2FaC2V4JcqV3PZDZtlVlXyUHz EwFCxeENe99Qx9K5WCuQfG0Rpe/t+pmwU4WBfuPM+TehDPOoV68tUQcjxaMG 952TJKwTARDI8oME6tA8TxYFHpWqdM+vxBdqgVJrIT6ZCmktlCNwfa83RcXY 4YP74yHe+9JtFrn1vdlaV3IsZ2ZMfh5kvEYdgBqx2+MO6JqDrkP3M3bDGrOw 6Qhx0TrOmpR4oGOoNRrF6xcNrxXk9cXVyKsSPPxyNec0BVhmmvkkPk9H2xIH KDMtk1ffGPKX667jevPw583eqJvxeno3SGn4ohvBbTddOzZiuIXnHRC7fTXp arII8KZSxxFmoiGNtidcwQs8SLW8i7hdkqEQ4XIbTTFXLBqfaFFd9cglI7ME XVyG27zOwl8bd0+myCrX1aiCCe5n9TMdSLRvHKhRTwAibfdiE18jf/yoM+Y8 tIe8S7sO8R5UWzMARqfYunjZhV9zTXr9mWSu7CAfmvsBOButmGixoozMD4A7 WegX4N/iquhcfrf7goQygS4ZROgSFwnruOhkrqW1BOLe5s12XHMZ7vThj6fU zulBkXRyQIVSxLZILUuQjt9IxRhBGhVWcBQJIXmBKHSruFBFL8d1BNO10oQI P5ULRmwktbcX3Xa04FzXwcdAXFyQg7V8VELoWScVCpbD5B5IyJL7e4ukGcSz x0Su7HFURWl0iDldOqQ6BbfwE+4M0fgIthTB3HPceVmdcOnIBBuGS7tP+/0c bvkKZk/8rLz3LvvOQdpfyiZOpBZmeIIt67W07/XU2p5IhdH0DPdrElaHymwA QHmyPPLwTN2jLvZAC5U0h39PVlzOED8q4yE0GWh984VjH+yoVqt84OSNCKj1 h8X6ElcbXyQZiKT4iGNeSYmrRYR7B8q0sJG1OKWgyZ0XYXnVUzeCrQpaX5Gc Cqz0j9F5IdUrnCXgOc0aCEejlPXTM+gUHjFFOLm7+bO4A7nzX+xknT+uOkQL C/x4K0Mg/ALNYjvTndmsJAISC7rWvxbbfdmcnHAAqZX2cDybRPdvf/vboCzb 08NisDUK/20N5D/8FH/+40j++2P+c/HfzMjz3/yH/96RwerPCjNnPw9ItMI/ Cveb+D/xZ8Wl6/z9czeu/XndjX+8f/X65v3//OU3dh40urq9OfrPXzHU/xhd vbGpk3vRjf9x/+rNzfvxwl871F8wOfev3tq8n/33a77x0kP9j/xtV2+HAVxi ci77RvqmnYu+6dJDzX4OAvDgVwvAw14B6EzG/auPflcBoMl53Jmc31UAglB/ ddE3/S7f+OR3EoCvf50AdN442Cf9uq+/2Gd9qz9foJCDTi9+vhds6eWsur/x hMgZq8H16/cScxbHKh8sG8F6HRHZAAw4Atts7/XinTAGDkXuraBOzXfEk2gc evSrA6wsg3aGsfngjrE8O8XY23iYuYzS6S8RKvEot8Kog+JOH28R3IsTXLh3 e7P/M4GK0uaArQppRZc8fHUdT7ixqbYSp8UmZpT33FrimzTBrMf1UB659+o6 W91lWs0hnVIP3/Ibb3bGTHVDbWoU+fSIa6EMt9/KpitmydLrbtuHaWFEmxgZ ajHiw+yXwewYPNu9Dk+LvtX+AGl79vS6GXLaGHg1zOTgj/Tx4f/TrX8M7wyO Jt2dDFTiRy0uwq2c8687tNjJEu/wdzj5+UUS8uDvkJBtPOHhbykh2xdLCL/x Uf+YU1HRCP0aMXncnbZ1kvLV5uBBhCnxdzAMDEuP7O0OT56uLz58Us1q0N8u LU3dES3r+8l0QSIteBpFw5AuF4nj9zlCIAilL1QxYbNYHhUNJWqtoYXFIuzJ Aj/pTtUyqLBD+Y6+CJZy2PlEfKrvXIwifDTe8/XmBXUBaDDvCw3RN/qZxmvI IWiRN08+v8P6GryRq/S5tD+3/f6ULG5Zz3info6LtZ9eNY4t9/p5LrhUGAk2 dhWbHCGi39Ny1dVPq5ynix4tpbndJ2iRBs9JvUwT8FrZEzYaJCB8GR4XVDOF adWpddxN3nc7O2pQIeVhCdhpD4/mR+BpNCp2J4n8NLwq6TVFITBvfi+zlESl CnHWIjFEIcAD0ZvshOg4HHAxKBS6L7jswzijL5Q4iVYAk98iV1qQBQ90pq05 XH0kifMMmFCqfL3ZQvP+0Cu/LvqvZOG1GAnqPq9HOs3Ur4NL8r2MR2gomK+O D6oFF7lImauiEhZKD2X1Q1zb42A6pMN76AIxQ+0Y8o1GHu1MH7/1/2mh8zNl 8F7T6msdYICI8uJAMXAUWSbVsosK9cKRi76tumvJEejpCtwmTC71Hc9kIc2W 5bw/sJi8y+pKet9BMRiapAW1X1anXMfJdPUxaZUEe7MxUg8pvWGixZEuc6vl kZo4Ci+TJSu0NKVB0cqsIbAvL+kAzMODWwsCQyCtsd0CmxmSAeJnRadTL1FU pZXWOIQ9S5k3vafHlgSOIjwWQOVd3x8Xs1vVTVRYfvcdlYsJ3S0wU9q8Q9+r kzIcOJRGzJ3/6LAskfM6zB2Fuvv3ndS/jo+aphUqra5aBYy3UhBxKgZbheE9 IKbu/LIK1TWWhAFlhDmq5tpjqDmTSL6o+0gzS1HtacS5NxHaeHdu3CxQ6+Eo LahYVSYxgSMTfLwIJJmCpULRYcArDxtbmoIp7CkONEwhOUCoE0tP+6BMHN3X QVWAFVLOzgQPLoI8nGv/rk2ZGN1QazkBbYSHIyZXj9gBvcvIjhoTphUM1iAD nXPlTLmUP2awXLDHJ9VH2DpgKmIBFz+lWXRlnc/PR9W8ZmbdPWl7u/qo2du0 mf0aZ93ac9P9/tNaYlZxm5rpND9JIzOeqF3sJD6DVCsmNgtjr0b8KfLFjMdY +yaSJrlOGz5xptC7dZQpSmd8IfqsirYS4DH7fGvLsrf0tEwog1neEzZPCMOL 3ry0NE+C7NwZGgrOQMfu2VE10/4VIk0ViCzG3CJXUbFmCj5Non1gHZqAzE6J NmjgVIs5QrV9rGhKaWuzyZCG74i6MtinidiPoKyF1loYJO1S2Od7VWE4DAgS gERChJyeN6DG4Vnsfm25lcjyr2+5cpi2RlZ7iLw2yV5eQWygLmaPNs3g/66C z0Ad3ecuSiDV86RwMRY64hWrX5LRXTzdZ9031ofzRrOcMks8ZM4mUqNhr1nS +qFBr3B7YZG/gJkhJaQTtoUjDvHvU4skTjGaglxDsUGhMWECjqXYLAHyedsA xNvKR3QXvNcOU9mCaB0eVzNFcetHTGVkNogiDdQ92vNjEckrD4TBXCegpEFr o2gOUBYUTsocF0PYn+Gl9MXWXMIa8fHHo+DDGSQUa+Q/YZn2Tqi1xENH4q+j ym75FHGUT0TpYY6AL6HtbN4S8TigDteXlymeM+IJFGrwWzGOGP/uVgIRdlQV reEHM35q3IJWSoIWH8P+CUrvJHihCzQKpLlS4Y+ZUcDC+TaJRuQAhoJyyCzG 4RWx0ZMPVArnokSY5xCzJcegvME9qqUFIBQxLpjweAUpKo8YqHJ0sywPO0Ik +fn6Q3VGrRAHrlkrTecX8llwynKk5dbcexDl9GjW4SCxRH21D6pB3anPyzSm EsW5kiIkTccFz/5J08z4CVUir4IXSqAjkPGj+oCNnAz4o4cpo0jHoaw9QdeN DpqPkgXmtn7qnSo12NZh/Wanv6QaP9rxQcUsgobeiyxV2vWWvM8AcMRSjuhg 8ksFMhArMqLbahGLsCnbq/W8d4SWiYHFewDDZ0R8KS86hsd3TCz0xhZcdJq1 PfzatFn02didsBg0k9Ih2rthPhR9h2HddhoxXRcrTjbHhD5dzce6ouSo18HX K3p7c8nfsLZFUhbHNfZN0ARhqqaI1dK2yLCItL8lberR4FkG5rEUQt5ZPa34 wFzWVh5K6E022sFqCftla2D8f9RzUDjS+7CTDpsFt1/KCAdXxcyWILaDGvK2 eLUcb23K2BzGlm4tbU0UwcDOIXQ31VLmZ9pJfzhrDsKYxQyHQsK58SQnaEka 3RL6lk/SLrymfwnS7w8JxsrHUmRcGT3A4YXwalJRutKmlW3GH0OVLEH5j8Up eZtC8oMLIjhO2L5GSMKBmTWdPfsw8vc9XO9FV7MU76MVSA4rMVVtENlRxby5 WgUknz1MftK3BuHS4lkJBRcCgCg1NPPzJdo5hMiolKprBgFVi+W0XqzQGhPU AVu/Sc9xOy6PW65DBRkzjjnCsIChe8RyuwSOvO9UkmCC6qwk4IB1l0or7dqC BjhXQiyC1tHcJw4icjGlW5EOuK7vxVVwZ9IvHKPpvp+i6FtIO9MGB7Mm2J21 gPsaaV2steccjn0km3bHW9QRep7XCbe8JBriVX9Q8UfVg4tUy67Jq9bYHgdd iH40kqwisnxhwFLKySi26crUm2OKDFgRrzD64pjTvtxx7mrbHOANFN01ip2w OYk6lpt2HE3wIJibq0poIbT+HaVgMHN5CY2akWdnoYGs1HwQ3lqtxGeGRASP JVaNyAwtGKHw8ZOxM4joOnwAuYxdvLpu76c29hgDi2tW7XuqNLMAqsHhhCkA GeFHg2HFqjz5AIsIA9IRFJWDqymMyRBGE0B8vqIuquxoU/l1qP+nhA9zjNEe MrnoMTZDsBA/gLNq6andJAJVMjt53FvuSdzFO6ulJm/ShAXiYcoF3I0uuP2M IC2qR0ATlq7T4kqbRsO5fraHkMcPIXlDpxHFPxsTr0S3TF0bZVfGk3TeRfgq NvpTzlE6fhHZPjBIkUxDmPjl9aS2sNDxjjWgi1uqOMoWbTSQN+MrEHPDB1gM ikfhd2gtjyRMJ6iaaj4WYmOvwRzzEF5hHk6Mt0byYkyEjlZystmzSvxlT4OE cVeCVj5lUTX4PFmAZ6qO4uib1cEy9rP0leCGj01ghNbpWKG6zs9S0eNKbJQz OgSN8Z2hNCP6Gw8x/rYeaobEzEgMl9RooQO/yGrLBQ0vSQwszjlAN2pOlsA5 Aq/7QoIcTRvprOygOCoXfMhx38gzBWaPaUmOndkJEAHP8pBDzEz6WgBlDh8W 1WTl97BsHIkqagm2lT2x1fgmzvaO4TGnkNP6W6JPVvK7+Nsk3KXGI0cxT6vz iPzsOZNRMOwhcERrdAs/wuZ+pzE+D6Yvj93Eh66l3Y4R0mA84kl5n4g+J/Yj Rzi1tIcGdhG3OfOXuzRBeHrMrQjaw8IzWC7M+2KckXIhQVENySQXInniZpiE k72lj84/0o2uxRjn82X5ka0Hg9gQ1QTghQQogtKXc588gtK2kYr7gYllq0V7 5W07DE7BPoODfOY+0m1feyHhtK0ElyPJEjJhadudKhYWmlgCU6DFyQmV5D10 oKTTmj2I/axv9l6/onYwGlaDJR8CE4oOPukwdlsqhTKXN1UpeyWf+ocLt3fj Ahapuw7Z2dt5+WKwna2rg2AwuVEwGhGSwQ/hvkkTZBGgKm8VsbBAKCOx3mRW PW+FIOnRM/DARTs0BUO/NKYRaSMQR1VU3iTXmVJKoCusOXHrphL1EIzeEmzw nFZETYoQjrWFlQrZEspXkfofcpKMs/YO7ty9tGciySJVMSgUrpRTUEzcwvm/ OAsQqZQiuJaaBHm8wqGwAiVPjG4v9upDUN6zSqAuDLwu7sMsn6NfzUeURoYP Kt0THLyxEIh2InHKvPpIVgztmtcn1fzZI8qDzcOHUG3VI4078CjICseRJ7l1 CPz31cHgLbKDV7/5/u2m7CoDQ9OOWVz7mvX0nvR87YRrHs+xEegzrn7zeu/x pt8YpNqDZWdVMNSNxu/arUAP7dN0q/GHhgitn037uv3LWMCkgZ5lrNMld2GY H4quYqRyJbtUnJJUWMQQ6XjRQM/SIe3JCK+0AtMtNVNJqi4tCljwhyH7Pqvm mnhlvgAO2EqfczhxRPF4fF+x4hfVgSH28tD946S5vQvaS/l/HIguLCV4UKmH wsUG2grUN2sFKtIcOKgfAOMn7IaxphFt+bWlrbhojA1wvtP8eZsF79fEqZEZ o1/KK9csrlF7x0tJeRT1snXQXBGidmnTwAhIQSGgxy3G6Zm7XRIkC3QjQwU4 ZHK+MuvVsnpA7OBYUtljtchSSVw0aav202ztvVKTurunTkZWcS40DeI5pg1q 1rzFnGlSjdNbRJvoSFJA4dunKLAH8LWBJqfbLgaH/LiuWG3WDGLtAqd9y4i3 FilCVZfvLvlwnBqSod3VBLe6e8m+M6GT2dWq/XBXumj61XE/kvGuhIQLzf0k eN2cS1HTOeKjZWKylmfP7VWSCSMM2NFttMTE05L4rcKKppqYzHM9adKISM9j o2yZbi/Opazm/kt3uYTUl49iemMDem9h2EHllIR7YdGZKItUR3xB0sfM11EY 687Lty/28KAwsmbKvcUpGNV60kIyT0bciFiM6eTH4cxW2SUne6CT3SGfLhxA xPFy1o4UsguAr11S975BfqiqE4NJH/TBpIs0cyG84a0RLLyOj8SQGaVIuvU4 ZLs5XLK7J8gD8hI9RbC5j6rZScwFGosiuHzehUk4rj+OVieKIRScoPjF9cfV yeYWQ+hZq6w+PPwzeP1GkQDeAu0SJ9NKul4j/rOCxAnUFENbi7bhCZGiwHVF ksCciCQkRsn4jpaM6k9UJvWc5Yklv44Ikti1ky7cEeZwU3qdE2LKeCygduE0 /IX5MAkv5OnjFy/3Hj59+ezR2+1r29ufPnUqlB3CiLADOmhhxSYMMhvpffYI Bn5G6nuHtfhbXl8PSKiX8Lhb5cMV9jr2d9k5Uq/DHwj4EEFwDMNbVL6rW6PL kfVYid37MPTEl4czmvC044agXIL6pvJL8UyGheOlDDbyyUhLaEcM+QVeShfi 2N3rlkXa/CR5v0LRJYwzjL0ONe95PjSLlKUMtbpzF1GGBJA3WhQEQSjxnth+ TW6MvI+LYDx/QAJyf1DNq2ntamQjeiZbl4WTlfCdbLILF0h3YzFAgPc/PAyr 88SQJmhTGUs/n8N3gyooxvFSfYOyE3IKBoCGlki1UkYipkfBSi2kmsYu0hnh YE9/hJKMJ0tKqdJm41VY2Rg6pbzFcW6Gc4yItD/zmNHhtUulZ8qXMS+M/kBC NVHBJjvEIqCL6jT8YpL5ngLLzgmYeeRUKLRQKfhzSEuSXUGVRwogTo8TZzGd Oo70JzmoYefgLZz1qBVXcRDzyUlTz9nqxkpyVlVqk2YJcFXvCQrw8SLKfM9g +cQXwPRF2DPNainVYCcmKuJytjo27s04aGyIgnohODya4s/Hyn6igbu3mv53 UuC7eyQMHYSU1wy/JGz+VPUBrauMj4WFY8tNll4vm5mPr2Go+YZCv8x8xHPG DAa+qJ7V7SKaTKXyTUjthmQaiozsAh9Az67OuuORygwmZOOXmp/PEEYZnC5y v1Ys7WF4cYC4+Iud0pJXgfFNtoseqlZPg8FrUQ2q1tdrmiIvuBlyIYanGIlL FMVPo4/lUn7/wczeJO251WOEWYoIGRnZFFFHQD8Ei5n8qGXsJnEchNAu8tLC 8V1xTOe8ksIwKmRRBFJBg/Ul2wT3FFudzC9lfwMxFoyskLoeJjdccMnwUJGT 87jROqOr92wIlsYrpiqgeD6vMj33rXnXXEbtIJKdydHDcrAmUsMloqXV+jOv zSDnbFI3Vh5MMz/XFHrQ9AtgehSOIX4dYLLPkzi6s3zHCAwoK39Ym2dHwRcs uNZtQqTkyq0KI60FcwSMDUXS9Nku4dwW0p41ymY+CSpbrYkJkO8PVr3duFxv hSf7sMHA354/W5OkRfjUmRtKdPrXQi1ze45MnapCS2PW2lxAHZAJ1Lk+x7My SvyFve6okZSJJ2OrVD0eMfWxAiBU0GxrF/Pfr0Av44wdh1aIT0UnIJAp+rqY 6dxK8K9ZmmI+kRmetUYDD2I/P8GFQvX6u8Ns3wQXQ4ehjgbnoN7x2hz7Kxko K/5Ky8ASQJ2Dqoh0JjoZrqfAPt8myJ3Y3tdO6JkXjG+9FMtushq7GZYpyIBd LfJjb5TtbfclUqqMafww9Qv4+V1xHUZiM1ce6Q4Y5moV1gCzxMYIqc44qo0W GPrBx76MV96qM1eLYDx2SATCSNsVKHlkV5BMJ6cu2glX86CwawxOtFdrZ02i lbICAcxEvzbEjrGue9JdfvyRwbBFHchbcZDIDjsuF0K9Hb66SO5qNT0N20br gvg1qiNnwki2RnGEt7RV1f/8yEKHM6uacw4oLpfrQBpMwycxsGPr7FohfRYN VEildcYzZMyNidx0Q5xhMVcLsrKOYaY3+hLR+RzV5QBL0fflDMrOLzdaBbEy lLOqHZeLCarxu0rR9ckVVrDCIZtJPTE2FTOReR1la1jrYWu0fhpEL1y/kVpX ej6pLiMTWwoRgjGzUqv6I1loB6sw5HlG0pq2ms65nA1WAShZVa41QkG++QiG xq7Ictg4QfufD67u7e0+2UyiE+1iyhEJYU1LUbmS8mmBqEYNjEyy1VCWgiRL M839NPTbabUcH2FqCrpJjow5GVqzyE2dl11DoH2mRoLmemQsmpmatdyZjrqN qS/37OHM/AxWm2Am6GqSlRjmCN0fEa+tKIWHnRMm8pZFFVnbsueQBcGfS5D2 8xiREvUfi+fDEhUJja2ByEgrTAm4yfCW/aPl8uTel1+icZYKTr8sJ8f1fD8m ZrGRmK09tk0qyh5tFDtwGuVERQ8QntyGR1+/u711/fadrWtb129+uW+x+9Lq CQ+qoxoxz6AUqrPwty3u+ZcqqW6WBTzOqbmUndvcLY2hk+iyW9xqUKRwPWsA 0pRsnBYLHjURztTvDT1mPTl6W9LXc7gEz0YjGxo2VnPQvVGoU/xfqci1Z/sM mn9RPVUPWsr9RIUDCRXuJrD/7LFR3y6qY+rpBU4uCx1caJ7pVvqjYwMijtVY nIKiPq0PmClZjQX1Fp40liHc35F7o1XDjYNWTQAXKIgfLB73txHdRwWWm8M1 zKmk/xDs01UxqlmJECZoqpFsCuE5O0bgUgVddFAvF0RzHuZTG3QQWSpIniSr bnmmdJfLccTqx+PBjlwmUki5oS8SeOPmsCnqY+lQP2qA/k+d2WSZpNChC6bv HZ+PYFgvcICrvaJlzOEgouSPVjFrkjHDI3Bs2Iito0Ke4r109vi9tePSYKpf Ve/h62umopcSpittV9963RfLfzxZULcLAD388ka2MVrhxpDbuUssOdUp2hqL RriOjFkFKITbLHQVcTjwt6R04TGO5Er5vKUiapZWRqO9kkTA0zrQpVeEmF20 R8RT4Ur9izAAvO+k2bMDYYfeKva4Vd++9xeEgtnPdEUyHGuulQCTIqH64JTc GLEpZm83i6Rdie9DyaO81Jb11dD8Oi195ZybwvmSDGt3PMtE8S7CixpMvs83 Jb0g5hVx73FK/TWTThaGs4XNSMdAIYUQC8dTaQxFYQ6pGENMjJwLW3uV6hnz 1lsL/9wXDi8KqynucsZrQlEcCumnZdRvVpS9VccKKiXtoynodS8Aq7oWVvAO yeeesgU5oMwM3+V+4B7dZdFH4yMHDuLX86R4GiE+BSUI5kPr4DjEFNCQTjmZ LFATtxUTE5EMzpnQbeVICeFYMpWnibtsn9Oaukmmg6PVcYqvrF11XEjBpvKU mqHFLtK8BdNCjiNssyszppyMYyVlc4LZZXxFhNhwExxYtbYJaOTJd4LQ5DiI C7KTkdoI7zmjCUiJWZ0hnqSQyLjAHm61DToCjhNRFvc8q27CulHDLi0nG+8v 1WUncuonCEgmyUR16cFOzQFLSihSwSb0WlRoqpo4gUj7wFQGFTMnuOeabrND lrVMcMCOC86EoeaUszTNmdCCs4ZmIY2xBhkUFZrwVPPaSCUknVzzK0sO4qJS segUXdszYinlwnGLmCnHkNe8lGJ6BTFaYi6DA2EjYoUvjzyr4nQMCx2XGqEt q3XkxriKqEfhKlI5GS2+7fZKLFsr6CnGvcxJVjgJ07rSJEFD3L/HJ0x1JS6M HSw2XHEZDVGA6BHp0AxrWykNjfuZv88xs1F/PN0b83IX1cMFbVMtlq7VhkvU CDRl3lkdHRvNjWxLRNmtZ+pUuFbYAJPbpMFNwvwOf8xAzR2DJ3uc9G4MRIzq INpqKrmQgVJUFJIOUIMr16SbUq2R1pZkdXhWrRxjGdpIFgZvHbr8ZWj9ayPB 1tih9rdaXWpJmE2X2as7hNvh6VmuNNk/y5T5CsSzshwKSWMD5s+KWQ2hQ8M7 GNZhEs8Qe4NWuNkGdUhVtobd4Gp5gQbielpVPeHcRZUcraqct5VVQOBQLA7O 0zFlpT2Dn3+O6u/TJxT6cW8TT2M3zREkh1EhOoVyjBm6FLOQpKBIlKKmczgX KBs2cqqXJiplO6o9gks99+WqkU6gcGFwq4XOtac5SlTloyUy58Hgsn+DhZuo dIizppJUotxdII6jUwuCL4pPL8gY24GxE7F+cD4xZr/eIqyQ593qKwyN0IBw CsQ/5yTFCaViB4gxVlLocNJMmSbmpTdHg7ydObLjqGSCR3boe3psJFvFJ+xO ez4fBwtxTh/t0PyyFplwUThXGTWAXsK6ffd1lKCgNVMGodI9GaAqzvwPhh3Q AqZwfBhqJYa7uJ6VXzM16DpiNiZCe2PRjY4PSp9H3G8X277EJXV7viA6wZLi pAcrgRPrPpb3J1e5gNWXmnv4bOWTTVencZS0AAegSi7zP8QUs/LC8Hg5jklf PKHgMRQeRMuTtmizBELH3BffbTHSndUlliPEN4NqWXOV5zkaKc8RnAh4FP6k PhA2LN/eVCQ4CAlMmT1w2SQdeNlI3PdGsBFfvFaUPJ8exCBbWnN41vqWHBXi Y74UqtLgO1YL8LKym9HTUXVgxjN3gMRJj2xXXZ6kaTmmoiOKyavC1tjxux4Y giyWhJ7aTatCsjazGB7wb+VS48M65WmxgmvHXecOV8OpUHEyKhTHpdkiKDq3 xdVeVl3X4ZpVdDiL2DnC/dxLBRRjl1iCbMNm3GBlpA9uBQUkXw9vqGBNiofh QPMbD5lwhfcyw8rZejFYUi+smavD/oToVpDVw7DEvPgP8957FPwlQYaDc326 aROENk/K5RF/UXjqMQX2bHWzKXFTwEGQrjbgieAcFT1qxX1QDmxSahrGtKvD DD0TS8spU7ewdlqofSnxaR+gu6pB6mqxaf0NKiYF/hrMQ8oJ04Oi36ezkOEb cv1bP3WUPQtl+Ytw/EWu88JRZjkyqUEcHUFRMR6AEo1LU3Z22xYhS9EEDsO5 diXlfUvPMupH9966NkhJmpp7VqSX0HEeU+TKb5kUaj+MkdZTkibtB/MjlDqv tM7JCDvpx2XbpNBtZXdpkkCUcDi2fW8qV7ThI8iUGgQttmSfLnynUGxqD8dr UhFM6CS/YjRWrtk2R4UjQXNJ8XtvJhnWNPwPgTZIes95McXu68gBC2Yf/oL0 fkc4q7By1m8PJNG6DdssOHwT8874K1RqaEtTHLhDgeXlgqyypPeo+hhMtlra JPQbHPgBvcB9awpgToABMUqrrJxvO4BWZJZK7CQGQP16F+lciJWISAYDIuiK meLH6rm2JokSRMBRitdEKKwih/eo5uHIqbg4vZpOERl0BpDx2KddpOGtEIcg AhS51uRG4ftRLYgxIc50yHkSOS9XE1Tfn0hlb2yXc8iMwUfT7F6hzxGb7Tgc RwcGsTrssGuTj7lYMrN0d2ORghQCurTlJAHqtL+MFohBOaGh15c1Uh1Z4g+u l1S1AETUwpNG9Wpk7jSjrcT2KSvOOfOJ44iLOlrSnSpBVw+q84a7sZVtlI80 XyCyKTV5FkhIYvRWBm9lYI5Lz4XLYxbC0jLlQdvMTqv0FJERhgcw4zjXeoTN rCUywUzGo+PRoQ0ILeBoK8WoQP2VSQRXOpNdX7caxyfgKnLaRtpghHoY2hdk GlkISEtQjTUSJTdSDnN8UrLNlBRvhOs+UBQE8fhO65XmCHb3xNnaG73RPBuX Lj4nNzvxtCiU2SachezLw3p1nWGcg+EmHuVZrXVT+CH2+wBXqM5DjXz0FvaE w+LBbLgM1jSDFkDgiGrzQlqxSPT2RxQzE/NhP9ywLwE/X2wdyx8RyTAABK4t 4+ADBTXecsaGZUO8wyIpnlfsMQH7RDhaAog9ACIsA4TpS/jXfErFiGMroZee 2vaIBU5TQHAdixqMg+Kz+VCPO2alCbfPHfOxFE0HI2QqtUp0X5ZtsyKcmIqX U6kDrTiwZqtUQvGIgg1hirm3eizw8IaMdcov7KdhsW6u9Hjj1fD9XVa2LdUg u3uf6Ubl2qpwaWvdkNYbWHKjHsqe0zcXEmrVUmZtyCCgPUKctSfMMzuiiUb/ emb2LfQpOf5JyO7IhwZiS+CaXSeV9VwrrqaloFqmLClp+ZgLP699MHFxrEML z9qh3ZSJIO1JJ4ahfQoIlmoDsyEk8OxF3eMCpvUuhatUihrEM5+iZ4KAUC+K VDiazEsvvhEwiqUtX6WZXsmZ6Y4HRJms5BRiAiVxEEwW7X+hIHEedjW1zRdq Rxt1VO4atjEPuU9Jurijw3SEBZfCUrEhbI0V6n7PJwogfFCJBWvGGHfL8qk4 ZVOKn2wruVyUk4pgm5upeDO1Yzf13d4iem0B5vqF8uDERkFqzaATbvCGyz8I xsG1CoYDTupCpNlPfso6CgfWd6UUsEBKnFS0GSNVvWZy9SECCMcrsvvk4e27 X92gTryNNYMhXYRA5zxoojeKsLTBUyUdnaRLSSSOOPACncxvwZissYQUBwwN vdKuY+gJrfOQUsRVMHmCrkftYuF/0vhbc0BmkSklZ9kpLe+kDrsouJ1whR32 U8tKLJiOgETZSl6mRwR5tysN0/K7kOyjPuLTquXGhQWzbQSvi3uy+JCH3KUv pAjGlgaFHS42tUA7Q9PzCKgHRmeNAJaHMTMctf7N3Ro+OjxMU56YehtXmz8z MUcjyYB6nqbKWjcxUkrkAVvIG5RH4d1tMo/sY6Hg/+A8FodKeUiW8g/3OxZp qQZpO63ZEiuUsPtBNUOx+BeZwOhxJMwbvI+4tMo+m83A6HfyVtbctPEssAry 8SO0cB+Vs2lkog8S1AgsQe3gMHySTDSFOFeu8sbQx+oIpwUgH3w60ZlwKQtX T01i+zeHGLXJlMPxiCt9RMVwWokk7xXXxmIUGs/W8eTlLdntFs5n+CdLq1i0 7qSuxpzOiTD9seJq1hyioVwrQRFUPjYqdj3AuIxmhYwpJoDNEOu/pTKZCshW C6bZeRxraKm1jcfA4gcXsj8svWJI1uVR8gue7LQyimPGBnvaH/ujD1QI1yCs 3M7OrWbCROSDjARp3BwGy++YiVsoQcoVh/oZeEgrZU6nFQETI8abcqbTG30R fwKSgjc46MmcxmgeqUqkTJGuStBqrUpQH/Yi2ulZTEXqDWFR8G0MC6ncCiiz FamM3y7GoNTk1NoXVSvRlbZNTXvnPQv3ym7lmY/phrWFt3a++7Hx6kmRUd9L tepZF1M6jKUrX9n/zq08Spk01uupnWQmuQqftVYw0uzjs/nmmEDt2Lp6ropZ zRh39/GHpKpa6ZfCnos+B41geOH7D3zVS9w6iDl0RtPNIiEcwFrU9lfvq9qj csEY52lmw06kLuNDQmiW1dxwGzGdDJQI53Z8ke1SCRAVTjVH/XAVt93hcptY Qm3W+z35WcABlSzokxVLEwp1BDnJm4uWvj4kDVEg5U8ByxhzYiOWD8O5vB1L Tu58sCNRsIJdgDLKbgNCz0fFXUHLetrUBhckdgLCGzNp+G33BX/PQol9IesY ROh745VOt2wWd2qZu0iaSWhepHS4hX+VhtiQ+EEd5gUfOciwI45dvKL3emsG /8xSQ6Vp73ItsEFzWKB8B1MUo6ARP4vRgpg4ZpsXkFddor/rR5WUpzkUjXTy Ep4FtWfO1UyObat56su+XUq9Gl9Y1T+tapZYNIJPY3tHkASlWQwvfETcZwnD ieAb0iMSjhOaV9+KTYY7eUawLiyCSRmmZlEuatrhNTt6bXVcj0hBlHOEvYYW 65PKeM25i98B85QZIelUdjEkCWekeVV0jKwWVVptm1B0vfVengaWRXG5Erh+ AjHoYCt9VrvXTwXT/E0BxZyW+m8NXlEJBpNFZcrkSL0efnSLx+QVAPRQ6R3m Zo5qfDQXbrE52WhtubA4olUoCCXY2BXFcUYj2AwtGBQUvmfdedT9PEsDZ93+ vJ0oronjC1jCHq7XOQICJY7trjKm8VfOTthWvGBoCBR1xyfqHfEiN8Q8Divd IGvsWTVTnIk5R49F0BZkb8msxdbu7jhgrmbHM5cCrpuhvrqV3o///LaBdFKR U9tDB6PDMjbduFdN9iIabkRhXDse6Scs8UZLiJC+taeQw7wUMXAdoQlEt48Q RULIyGcik54rRTlXrRPJVgCtHOgcVvch35YwPqblQtcYdkjtoEb1UN8aPKqU rlKSxp85KIe9CpzMFCOxooaP4EofzIL1HLth1luHTlTsxEzeKSr92Zzi41R2 Vtg/OZZp1qkDKqKaPcoVqc6n6UPxwLwFCDoJtdTcImLDDQgTYxdUBxQ6YK7I p/K0aG50aV9dla9+d8L+sagEk6VB4eFqTgOOOCwTMyt5RL3jdcXxa/y2pHaZ 89dt34XCQtGaoPoaC6moUEhmwZ2uF2z+s9hqfaqwDuLgQeNjV50aSUpSDqU1 WmHTsEheYMixE61g0+jk776GT56FIFjm+jxFeI9BpKvV1uEWvv442LDar4Ie PIr9CrfXphzRYasFu2d1ImesmVJpFVyYNsrSi5eU+CMCIHtWSmPNUltELdo0 SWadTG4hbWGLJIlRyA55SLDFzNzEi8PRU3h48U/WqdIcH9Rz2+a2YSw+4wes G4DjLDFuyhECM/toMSuVEj48NJw65ZASvpT9h/gRx+L4ug8geXgo8TaLd4/c ZwgHtoTAD2oQjzKjTf690awxUPY+4VJYhXaJE9211rM/6WWs8ZEt3fC+7DR6 x2NUyPq/Ce4CZD7erZqqhwR9oeFvHD+d0UiRwYEQcZg6xSR7rwBWOSqT6rmk wGUb+6S4xPZi11/E2YDshH9rswiF6wlas/WdqUPnStleEM+cJUNzDviSZ4/a mM6ZUIfxUiq3SuU+mNtchDXinGcpSPFrpjVh4cVaIJ9VMv95GCYbwu5Tsx1S utK4chzO4LZ2PSPLM0bCr7mALR4QGiKmmZ80fY092j/CCpqsLwkqxuI8ero8 KAshWYBJK1G6OlXK0aMZYrW1VETD88JQZNlHh9Wv3GEtzvi73b0Rp499o8B6 2EzrRHDm4ZzLUejlsDSWR2rvA2fxSougoadspBR6yjji6aIFEpV1K8v3juVI 0mOu5SN3LfoRjY378HhsUa/u7PlYrAZ9paeNi7LDSwHmSB6MsVwZimCzOAxO yl/FIut7Ob6Y/iQdpREBdhgPDur9iaOy41t9ZlTcUAg7AahJr+VoZL+O3dWL OKTYFsV3Jszd4ANgYwGXn9oviZYSl+miiCR7SqZqOxqtnmchBiZzT0JZNeWn ucqiiWUvLSMYuIRHN4IDc5UKqcYZdXPfNpXa3+hpdh7Hqfh0/ktBPKUgyLRC TUvYdfOViCtSxxZ3NLNXWY+SvIvBZ0lBYLUJQMW+iW1dCpzEIzgnVAyAs5dh fxYdi8xNgvrbWE01k0TtZpJg7I5rYxtFX6MvAvvMb8xCoAinZT44QWBLVlyj ocJbN3XmNKm9cbUQPnRSoCyFdMtpM1sFf4YdwaOyE75yqvc49Vz5sphzdEWE SRKspg84qw6YuqqUHCGKEJxMcC1p1eDAIcG5fsext3XAx9lEmp93lm24bmIS ZgGAHQrHNTN4QgNR3eSGvH3D1GKa5JOlskyLvEW7a2PBicyYGoPiiJ/reMgT 147qI+liTx8pjQCcZztqkAdBMcr1O8lKzJQGDUd/ouVk2rcGV18lYqaFdZzp z0v4SmCmVB/JmBFzryeo4Znr2u7oHd1NR8YmW5tFr8LtS+QErau2bh6HpGXV pdcjvV70jZZxjTx5bG+cpjUU+GPubSdVPl8XqncBSfJ51rk8ZgxHS6hfPyUH RacU0NJxjiOt1HRcRJ2BlcqN9oIZ1dORqb0W1oYe5XQoZ/qZoIFoP9AlhizN W+b+eN0hu0mRu1QjuYxW2hXCqhphB02OI16CTdGTGuMBia/3KFhjMw4Mh3nZ g8iFw1wru8iqt3KOY43DtrGNC6soHgexUonU+uIw/TbGnyJdO2RLCeS45BUA DEgBGdgrp4kI1sZppiM5qaM9IO/DW5RKvq+ehQJuCs/tq9W6LKtCg8tMTZz2 kHlFl7o0LeP7yYVcVmlVONcOxOqWrGP8Q+ID63zEIFBRjEYj5IKoWuuRRN4H T2uK1BGjzRH/Kzip/zkg9XSPsjBoiDtGVwUZYE8eDqoJ1SVpjyPHzhSrdTS4 frcYhP9Gg++APSk2+rPHe19T2r+uzsJQ/AWTAZHvSNvssnH4nKBFWB3gL3rP zmSC0NIkWChAq2WUkAhLHwZw5/MDoMu+utxlt/su23kkF6Xjsk6GrLbNard7 ChP5LbfkOY8xtxTVW/n3tUfVSZDoSfbWh0FvktU3DruBOnBJWCBHNCO1BLdw XIHMnl91M/kgrcNWLFXJxFKRxR8d3qfUHMutT+qPUM92F5QAML0ig1RkbHKA Y+XsvK15IKPrN5KPJiD6oN4P9ZvDD/VizQfHjDY+jLnG6FagSfth2kW6t9v8 WUngB7QaCVKTb7IUzlaqqvTQYK1/YdQATjYGz3Ze7Ui+GjKPxho+ApRhLB8X YWmeBr20Oumi6AplFNxMzkWyIcaIz9Mw+67IffCaTvHBtsDz1C0vCe/YOMSE 7azxVICRnUyvf/zxBGFeUjwUHcEsR0tLScmdAMmSb8sDXpLjPKmmJUFIgsi9 nB0GwV8eHQ/2nu5s37o9cAhU4Tc3Rreub+vrd6GQBvsa1HjP7QUkNV4s9fJH ErRN2MdoqhIZztaSpkS9Y3MaubmvN2IsphU741trt7PQIgpaE5baa8/R9et6 62LRICciBQV0EuDcGLIppAkZbHmqTsH12A6JTkq+sZ6bDR4XRueUHq+nOgcH PPgD5Zg1pm8Ta4WMORBNk2LORLAMt/yCUJroLnwaD8QvBHyyMH46GUYnDRvq 9TyBWrYWyFRKJoONl1RG3G7kQr9bnZGvNDhcBX8WJFLzHhmJ2iDeh0scfJf4 4m0wq2F1mXlgsAb+u63nBQJL4aHBxt7T19+9eLThhT789uXOjxvpCcPR63XE MrRq7QcJ61toR8sxPUdpS/zeyMq5tM+IA2+XOdHwCt8mlzaqXvoZKY1Teh80 L9KEYruHK6f1LDcGshwgJRtXbVxrbKpryR0qTezoxEjIgnphW85Ula2ZaRRR SP/CW7J12lC2tWd9cqAcrpoMtddg6BSwJt5jQt5Jzz4JmtN6ZCUHJB5EV7Tb oIeX77GTNlJmDjtOwm4pT4K0bdDqvicFscEtIaW+1QvdXIYX32QGbaamk1yV SdHHmisXceCJcXaus4/JSEHgXMEBToywa9LlreSoiVqT08mRcya9fvc1E0ef W3s7y8C1u5cSSgwqQqGJNIn5dMkHMCGk1bCxlacKYFJ1VDACypY6N2MxP8b4 vetMS9PxzJGbcFloZvqyu5IQ32zEELQ5q47TKlWQHOq1FCwX67IiWvP81Mqh KIFaAWcldVXDW5M8b1e1D65Gyj45Bja7TyTjlSynMK3pN8ct8D6MbQP9JUNz bzbwO4iy3yt0UdxMmmWb6ZkG02yGcq3ymGKnsIg6To5an/i2zFIWAU39Fq80 6J4NjrlsSKgvYRxGdAGdPC5/IiOGSd152B7bLxupCvNiwRqtt1VnqhB11vOf yRZD8oTV+aD+y+efutZkktn5yhQSO/IQuPBxkxkqbpnxyymlZEBMgKiBrfao PkmNpDUfKofIZfaNjPJ2rqCtbT344Bv4/A3Vke9RV7sRFRv6Yzs63o7qDT3n 39eTDb5Yr92jY4AuMNX6Xg6h94Z9JVo/uQgOzXuS8ORCDNNfx+5OzzPTdd/Z i2xOy4YPDAOAY+dyGlykhKov26GGstLKJyYBfT2oFYQ8OapYUwm28ZRh5Xf3 ormFKliIIwWVRqDQFN7pbMobsmZOmhPGteXQbH7NZM3f9dTiQNKjZ4+cTKab UuH74wCbZsa0S2GeZuWhK2FFvfcSJbZSQpyqlwitZ4pGPHnompeC19fRObey EfWJEFTOZ2Qr/7KNMDPvYRDJ7fHni+6KrNd8V/y55y79dkv1imdOQkOFgmnR TeaBkFdBkfYTVJR99E2qth95a5eUMxFkW0gj3Ontzgr0IPNErevMqXLM1b6c Gx4RKE9wd1xXjVpnFADIJVTf1uFwb9C9RZHuiiv/nRHKkqOJueimB/t9WX7M H21m7CwsygpdGCxJG6B1WYh6kJbT8CNa77kM9pcPM4/KRPVPmCFzUhNY1I/x kkd1GZ543HcBZPpmNgjGBWxmzeF5zzIwXyuajKL91Nnzdrntgw2PYHwYPL4T Fx6qgMzhbEaV8CQj4yGLTAmki6L3PXrTvAmCjqohU4tXjpaTK3GBqX8RcP1P dt48U2dJH/Qslvt2GAOPNFmBt2Q+vuo7it+Tt4XOfhzt+RVGpACNHfwJNtTD eqc0RuG0ZiUdLbf4aG2enehTFOgE1kCH10aW/EauSOzEGKvVFIWArVM9VDMf WqQ7a5HayL81Zayn68v6OCgtswJNWJkPLGweoo0j03TDHAzTRUmhAKWB5+Fb KSafG8KXX5S4j/zWsPAboyQFs3WDo/lAxl+SZ4hCHepcrpdPVweDZ1iU9HD7 Zu/1qxiwT60WWwEUsWmHNWtz+tXGxQPU6NeGRD3fl2HtvGplD2EZlAaqloLg Ptt7Pbhz+9p19WYFwHndaxJ7pVzIhn8SjDRy1iLUjUQ0dGDXbB8xMxI1wjHl F+38yaKcAlMTIEHJQTHY3ro2+PmL03YEq2JbkDSvtPGckT4mLq4Ti9nuvcId K9IUEvbYpESwY0aRoPZeUVzfGvzhDw+lKhYYtSnMFpHpcADl3h/+UOAz4sAi vo5v4hbbuk1KRM6qA22l5J6AyBYYHXpHM9xixq2wi3UA3RPxm3wdnz3l1F/b ilIVBWXvj18Qx+1bgCPcRafZMSJTS/EyEmpUhq9D8BiKUrZHsGKK18Vz6OFQ Y/k202oPYgdjshitVh5zS6uvlp+uZlN0l6JFkTUlnONgC0vMLrq+CZIxfV1a w+/6Bf2FK6o+5AWx1mPJDg6VuNGuDi89ShgEUG7vVlqSAlvJRPRCaiJDECtH SWwH2rlGTVedrEoGke96GYzc8yNm7ZALkEpGIpP8R4IHKWEzbQp0CLeRxV6E irGtJg0VjQhK81YwnNmK0qvxiJEH8uPjEgEJhZMA3O2omY5Q48pZW+qmmNJL AFp0zvV71ayt0glMc09cbQ5DkGetucRktbhezT843FKk2levMQa8ru1axikH qp9WIXs6vy4aqe3lrFSfY+JU2uRqhlFNJPi7S5J2UHXp5pbIJ8onrbfy2OVV sGfRoRX24DapvWfcoeyTwCLJM564w2bJNYo9ug/l+XF0G07rbLCAymR76TXO okzWIjHfS8rfW9e77HHnpKBdg7U5Fs51a7DpkGgYi3zRYc3jSYkRVQs7a9T+ Zs54qVWiW4NXlMEKuuWEpUGniPSCK+rNtzHDzbiUrqpTH98YcuSVijTa4GwQ lA7j0qk2YwUa9X+DaZj5xBp+zUh9EYMRM8GbQWpVYmiQbN2IlNtPxSSjh0UZ TW502Dggm6TVj87gWErC+8IyWpg+BeDKB7NS3Iouq6RDN1laewFHI2LZXngG 6oFSxRDlh2rzZKfIxhMJOQClddiyXPamZ0swyD5Y/ZnbEcnSeZFzuE0SX0Mh ZD2tRuPzMdefd7oSEhzJpSHxAdis1jaLgVguwPVJZER8ahTheLys8ByYpmvT 29avRlNfgXizVSQXC4nnfWHha2/AaspKunqURGytJjlNIFUcQY3tL/586WaX 69/XEyG4WRoiftZvn8Gfx/sIrD8z0az2txW9jLIxZRmTVSE0TW0ITLSjdfHT QPkzhd2Q4Ex4QAiWNl4R0FC0mjhsgq3Bo/N5eRxc+lTzqqiqUgxeETn6EbQB U4eqSP9gxxpTRXKvcy4EraSTCoRbRDMx96C9uSW2JiuqJAUo1ee1cHBqsmyM vlcu9U+KKbFWJV3pNpe6egDp+22PPZp9L7ERn9ITnlLhx+lcguZqsqRK6cdL DkstsGdx1QPTjWaNwA2EOANeVZjPm7QtLBkQrc+enaH6mB63AbhQ5/6a57qQ ZH30JEi/KaKjXW5E9uMmfBnLOPV9UBgMvWzoJYskC9xpUM/9CRzNr2gpUxhV 6r8FkU1qNQF5dFpDoDD9zXTqb2TNqjD83MWGCYz9oQk/NDlEFnXYGAgIf3j8 VQfrDoiyO19d++rTJ4bN3t3Z9SbfVfI/s8vv3rh7my6vOMks21InHGWbJ/CP FN0OVmxibft9Ek/RBZX2xwjzVCjoUuSZq1Sy1RyScxNWJAx3U/PWS8GcjfWO Xi5ZIaR3Y8jtZnacq6GavV/x7EcGNpjDpORFDHQAGKJy3sJoPRx5hyUUhkRG zZ61WZnEKihphAeLpGIxSIM/eOPnDevnE8nLBuOwokBOq0smZTSyL7T1NJek iLC7uxdFI/pX/gCn27m0W1hAvAUnSg3os7dw2MVY7LkwXmoua51xLFW2goQY rg6L0ea7RBQ5/5UDECkWLKwsIdroQbcnM6xauKpF9r6gDQ5W9YyJ3AwBkCKx aA/3bPdOyo0QlA1L3z97CQOXIDpSrNEjCrb2+9ciyanBl4a87RBgaQOKo5+D NEhx1Q6kTR+G7gZt9ULpLZN7LulKdoLyapPGwXbdyF/qOFqDCDdgAS2FRXZD uu3lYNswPr2co2kM0kI4vto/Lsd0cliGdb9N8q2Ij3wNBrVevq+0jntH7FGN JKEuhmAPdfp7thVPfmY1p8T3vn5pJix7kwrpnnKGk9sA8sAtVS7EXV96vFQw BlqSKLW5Z+U5xcKezc2LUYsm4bod8gCNz7ETrUJrZd9G2d1rZWMY4KKvhxO4 xYUgFnAHEaylyaSN5K0N+sVkdD+RbVnCsZBmrzCuajE6aU7QBQLedmb7RTz1 sSRSNZI8eALh/vkLTRwZqqgFU+387NKL6sS23q4olJpnYDycB9pwzovJCOY5 D1QN5T7NGTvasFg0w3oMKdRNW1XshxEydkzTEiskx1SMBMk1VUvILo01+LKL Yo/2oVTMcyh+mOLDpds9OUBN0RbhwJtz6yq/inFZjL2XIzStL6Kmto5dSWSM HuA4+Q4N0i5GaKs0ojkaUT3NJzQ88srIRA2Tpi7srNcQu54IdGHBOuP5yNtU CZiHyiwTGtaB0pHacQxqQqUEiWFv8+oj3AAAMJwdQ5eaIinSDqmHVGkeA0kZ RE1EZK4Rc9Hu3yRyA96eSvrPctJ7M19a6ZMdKMV861BMwmv/9re/DYjBfCTp vOLN6723gy+XH1EQ8OX1revF06Zd3tM+HVmorfDhxKBDp+robfiCe75p/cuf 2mZeWBHB6Nn8ZEWPqA+v39/a2op/cb/Thz1C8vIe2RSj7Vu38bfiZ+jPDV5k KWO8N+Dfur+E372z39F/Pyc/yZVcN5BfahdQMnFj2P+3s3BKVOv+OGlmYevM Nzp//Uv3hg1Dgls/ECWWz2Z+Xi2/XDcEvUUdjC0QoX+J+NHlxkUeDIc2144r nPUlXbZuEIC3bHtel/zmk/0kw/jE/yMpVbe8VBOSrjYKBMKv+HvrQzeSjZ/O PiQX8xOW9ISN3b2dbNAbFf1+59udB/kfPtQT+tPH87+Orud/K2eH/LggoPnf SDA3Prx+cGuxe/Ob02tfv6xelD/efv9s+X5x4/Xu2WR6Z1y//2Y5nf5wXu59 vBPEO86UzsmnZEKskiCZA8R4aZE2NE284dZzg6P+3ZlgQ43GaLdlH0DVjfei KEkK3ksfu1pfXt++cfPWrc73k6dJD3jx/MXbZ9u3Hj2/s/3kh5tvb3775M8P 80/9VHwiDUQ9Z2+PBMcVcadM5SHuocSNLocXDgDtNy90mtj/2tkz5BN2qpQ+ xAooDuvTzKx2gPJBg3qv0MFpKjGivgWHDzB5hE9vIgq66IWpl1yW8ELTIKp5 b1jId+uLCq/nxbvpCl64BnMJtUIgK4yrtU+rqzIfbF+7Nnj9/HOq+yHBXY0e clzmXjDKR0DpMkXcI5JRnu5FKVyjwsLh8aU+4subD5/cvLv98sWfXu59f/fl 85cmUFGGN14+ePT6yQ9f3/zx1sM/ffPwhzvb11883SiiHG1IdL3qOxV6zgv8 FZ2a9PQ71757s/vjrVcvb9x4/fK75y+f7z3/zkmq21XZ3uj5LBtItoVjRWa4 /6uHXz28ufPnu8+f7u7d/uH2jZ1vdl5vpFshF56WsNc1gcYCzOVAQiwfbSOR vm4/GnkvwZ+JC4UCaCCUR/cxbhQUBCqB79ID5apxtU7QBjeu3Rg8Ife4eCHH 3L3BrxEFPyHSnaIgzYwK3ool5JnYGhDE8/7EhBB+YpgOEDq5rvPSbMjIGCyp SU4lWj4KRmQh2f1EMW0N9mpRGKYLzIR0YUuuHShbo/7mLDmXiMizsm9IOgeH 8oZC6WvaTp7dEWxoKa1cRZVb/Ak90uIhX7uUM5xAbBMeB26JLkruMyJSNco2 JVnJjlS8ev328b3Blf+6MkC+9Sw4GSdIhYcRUKvwna/ubhcqO9trZedzZ9F/ hd32f+hz738cHR6unn//9qc7i2+nX02+qm+c3fju6K+nq29uHZy8nj0/35n9 6eTFxwfT6Y900//2Pdz3bz578v33z57/+ODh9ptvb3936/arF9cv2pvCudwm RRkJ5pCTXAhm52xgKjQ72bjbvq/+RGWIgvgH54WArDC4PFdKJiCZUBHkeavg tlyeKPiIhclx33dZwEq64NVVXqYowBCwIla09T6LXF/sDIVpc9lQUkOOdyaC fyZXpYjP6A+IkO9F71bQnaZLIgHV/hFSTKYtEqsDjSun1Xo3SbX93+8sJe7h PY6Y9J1Lv4NX5WWfTqc+8d/oGGqpWCnepqvdnDUNKt8UXEOuSGs8O4xbCNEo 5dja9Q96t6oS1il+LLngwu2oKlPKRYsOZjhvDbEQIw15Hrv9u7TZb2hyrfd9 zY55vXf35fabl0+ff7d7++bbB3de3X7w/Vev//zgzsNHT16/erN9/e7um+sv 3l7z7hKXn33GqMFLvzRZ/K/Ejnq5/lX+RdFDz8ywixzydc74Wke83wnPHN3P ON+/0PH+BU53Po6Lne2LHO1eJzs62J/+krrU/6LWcVQqQDc3ZuJHHG7rDxFy LO7i+GCWVeivTh2EXUd3aHCPavFXDFJAsX0bjfzdYTwk5Nm9JgH5eBodLR24 BDquTxZEaUTB/m938ev+Z9RKjBkZeU6WLkDp6Xlp8OaiUscj2PQUTIAZeqhx UhEuvbeQUtDGmolfE5H8nx5QVP0yintzsMEkcUvGuAszHHfHutBWvwf4S+M9 Q99/+pdLBFTq9jKRFBPzLX2GpYSQl9T3M6hBqQWejLDC7OuuzrRtCio207w6 PcF5TQsR817XB123IuC2o+VJBbDOxpVW48I85daVMhwPQdR9lYkWKTl7otB8 i6YVwyg5c7m+OqghYiDUH1B1U6+n8/sHWpJQi9O2i9Owl758+cPzp9/6czdK SEfFy283dq4/eHjj0ZMnnejcv+rx8eWfvv7m+Zu3zx/eSmwZrPq9we1rfVvh kgEVUdrOQ4bePq2Zxr1ANLAV0ifPbcvOVUnsSnJgWBSiU0MwC5sieRE3/WQh DK6kkyNCcsXtmNJUkwjVjiHSb9Wvkj1zjlQ8Jbgs2eseX8SKXysLgMFu8N9a 69Ix7LWyl50uYVzHpyaoiwIVcdhUZlnL7Jyg3QHNbxQuKHTYlDeNcIu/bECF bHAGX3P0cny8UuobqgtV/s5OoNDQgENDxa8PDanPkXiPW4PXGhnSoVrxWsdH icLQFDa40kfflOYVU0lg9ZCxIAcvq3KO870fjZd42ZuJlAuSAtOQGQomz8Nm EUuHCB2LPtf8Am85+Trz4AvELIA0SSYVAlgW/J7UxmbIAMzR3viMj+02/SVM iX+CP/2L/GO3jX6Ba3xhQKTIz3Wh+qJT87xaiugZEr9lMDRxYdLXm7iYN51+ 0PhUxWhdaYKjsMgIpUyoxIors0rB6jaxQy0QwFx+97P07zrGvv7qx2/f3nz+ 7be33v75x7t7L/b2bj3+u4+xnbffP31989vr3//pMsdYigTbiaDlFXWuPA4F 7uj+F5V0HvygMDOKJrrG3gFquaD9z2b9esBUStEdEK94d61NVdRcPOZpnz6v BuKk/Uo10LeU/wpqoG8Rh+s2dXaOoJmJ+6It0FVY0adfYG060OLRfwe4fvMA 19/lMWab/osvBq8arZg6pfoyVCLGcEiYR7IW1sZDeqIK3fJtsWqbs3nBFL9S vT1vLEqQxD7WRAeYqoL7P7LIwNCy2VKGRAltvCP8u4glSeJP0kUviSM6qqHq 86bCbxFk+PWhgYyel9Z5TnhwVJwetF7YSaMbnw8NXKLq5XhJVOTxD+NqsfwC tSjhjwdn4+fXqnZ8Y+dhcOoebP946/3s8V77w+M7zd3Zcnzt1us7d3+avBpN Drd1MJepxbggdNAX+xJ4QW8QVw5pvldfSWj/9zcE/uma5jJq4xdKU1dt7HjY xbT60NVb0kW/Unc0KR+4FtAWu685KMO2J9Mo9cVOtYwSskY2oweKRHMT+ipX pkXEH+NTj1makkGv0UqInGX1RNaHd3CeqENBSS0cJ8I6D37gaiwTgPrVmtKI /1GB0J7KSspkkPSfHDXLZlSe1H15i3+XX144rn9c+WWWiuJp77NWLrvs03oe 9kZdzkaOEvJXiQBpiMmiPLvclMWaORqFQB6Ort8c3djG//UNgYNJYxSFfrf3 aOPCqfmNw/ukHrLQ/urgfT3BhOT+JztG9EgGLsyrLbme7Jvtr+98fed1eKNz SbHgv08+oMcnoUOfFTZCjTGWxqGsRLMXHHSUN+XXIpbPwBpHkfzSwavQuNPC lSyI0e/PuoFqID/xWf/VIxC/Sx7282EH82NL1Nulx7HAGSsP57Fn3jSuwEJB DlPjQuvl5n4e02VatUdMn21kePW8IBAccWnF5GDECNr2/5B46G9RDfQ7hSd/ dezh34HFf9a2fvDs7revvr/9p7vf3/jhyTfPb+5e2370D9jWFwQTk9XgjIpF nNJIInO9/tPDiNyuutZ7/E02Z98y/aM2p6CrXLATk2ggO9fLNfHAf8f7/qXj fey6h7k8N7gb9NnvARQBSytoNMQwGx15Aw38HrU+2mrMXNRJu7EiJjBW7bLW puPCwRASoMTtr27e/fRpmGNdx6zCMWPUC5qOuvTkPccnCe5EBLQDYkIrsODH TZiTMBJ6vfAZb30mFjEJW2YG1B4utt83fJh9QQmA/74PEIl9Y9WWUql64aZU eMTpLmM3JCk+Z1NG+ihItTjYnUWphfCaqHYfmw9R6LdWMCTCu/PBZqMsHdKJ oftatY2ohkKsr7TFW/P5v2Pxfc82sjMfhff2cff73B+U2eN775Ov+b+2r8Gb D/8rGwYX6NcS7v79z5b9yy1cvvGeHNH7lO/nV9FBdZ/7AnRvvRJQOrdCuvDK 0Bs7eDsh7ILPG+Zzf9sQE3K7JlDGUB/hcZhVHECkvQVBKZUaX1xfsRI/WVDe VwCX/seHkiz2IOGdnlBO0tlIUD3wlTcYcGRjkFW7/rZVdv/Yrsr/4+X2t+mt JIPDax4BLmCKwoy6OxPkK63QPLGtUaAjBDHYBMuANwHj9oR9oyhanq6aDc1O 30sSUY7N+vteD6iupIlRfsWw7gVhZBn6gmjLfV6hfViOHqZhNa+J9wFwby50 0BlQbHQCJILmszDzOdiXluJGhKHCanIZ0zrrABNrjVunaOoB7orCHnYsn9Dt VBUpVJZGACbGa+t7Ur7gAmnPfPRGmI940RnOI8G1oNdn+BTAHx8CkKlRwrgE 4UUbAmucPYxxUYYzm8riwvlcLYFVKXymzHLd+WsEUZGIOi4QbcSDL4TFU5Rn zehUFFNfgosYxZ/HzNEK797AajRqHwGxR8tmZHxPhtsxFLeFoOGq+Wm9aOb0 9ysOYVcujcga8Y14YYPPE1/TPWNL7K5IlDorF4eVZ3nFtAvD/VBx4Uh8RmHU o7CpKN/qUJskUFcITI/SmuKziRCucoB4HLxgsFjda+datqu7ah6jajx+QKQW bTUD7wFLrjiEREDJcypA3/ZQpD7kySB0nwgZcmSVMsuS11W/3bhaE9FmJL85 Y4IReXKzCDPvUjoOtmaYY5PpGNcxgAkxOYMURyBgwN54gqJCGEdkE7A2UUKt Zj6tD1dq/zKG6IKALj9Us3MxqoNiJJgaQrfhdQdMjUB8TQvFXHPHL53r4ThF gDfsQgqXJARlOlNtFb/m5Xfh2LfLaP3D/LfCLqvgNGUb42KFWBXyBEjCy50f /TNiY6c9AfiDQqE2cGNUXZmOs/gNxjkcVB/R3aDUx1H+6NSI90T0RhMgJ3qR z55NtcgA6NjyEFVMumstU93pQJEv2mQYm++rAwFE243UX0FAs3UbxxkT27H3 RlsU1Xv5rM1mulliU7bOxD1Cm/+Db5DZQ4+34FD/4V48QvfzK5/wt1/m0qdE +rCjVG64Vkw+XPq8wpHDNCDueQLLsW9FJE7KooejT3jCqHR0409nH9p9JbxT phpHJccV/lZBGmyToEP3wwX78bn0WFAFmwEbvyC84w0VStA1Qm01eBYxF9xI ON2Cr9wxglP393rCFu5+b+vSZYRinbD9XvJgjQBiTyUcZ5cQEto3/xaQXyUg g6+VOpRs58cRcI/iN/rDp6J4nEDx9cCSCUieN7vEpSTMdYU+jIBuEYGRTuCC cb8YxpSpKaONzI/O2/zZmlN+xsE7/ddfrn5BzI2bA+LYOJgFUdEQcN0WyZgV qzk7oQ3AroLPykaHUqZlNsLQYxQyEXqhyLdMf8xjhViAUPLg3O2RNFNkpu3W gE22mqjkw8jD7+eSFzoIzoWz+vD2SXrqEJjyZMLg/EJyGK4E40kytcBOD5br IQEfKgrzvEhoL4eY4nF9guOVBhMEEwEyOs3k45ACEagZHINKffOTuCPHlPxq jO1MQN4GElfDQOIscBEOFRqo09W0lTBpMJ4i+EjNSQhvLxSAXhFxeWXFhWWH ZZ9d/KBhFovwGePSEFUHVQ3TS8lSCVCX54kwJIuJMQQDz1Y9xxE/b8S8qp8+ GaoHicg7zHY448+Pm8VJELzjIJX+x83CBRY/C3cp8xXWh9YLmNLjo6ZpuS6I riCyMKwDFuHgXAJC5TzSmeISTC7fAnC3wdOwWqcERkdzZAO40jrirwK2id4i 1LzCUaZ5+KnAJnJ/RQ0wYtjn0pXCckoJuGRhyuLo/IQsfnLXZw4sdgwnJzpR DNXLDramWPd9OGc/glvQyIaFfCnxksI7OpvPmpLYh4M45VzkDjMFRtrcjcQD GVr4q+R+mmwEPCdMC+GhpRPg9rxNxy1BPU1eXZxVTJv3d0xDLGnjm8TcLHgQ FPtnz2w1d5xV+ZjtmWrCltrNtHDM2EM+FTBfBcnpQSUZdJu2Y1ADEtO3fuPW 4KpP97lTxS2BJul5KTjyUainSy8Hwfre7hPhYyRY/mnJoIjZ7lU9PmrbxTRs 2s2ieNLEFK0JJlqyfNPbu37QohTliq8Y4c+Avy3eMTdbyqoc7hFc1hGFsDY1 EKS4n2HYa1XS1mDHiwjvE4BFluoyuMeoyAxt6fbDeuwPpbaGxUr5ksUPCKLI gk+Jl17jRwAm4wLxwZdIfhwOHM/gBR3l9RTSqac0LNA5ZG0OGWGVnFgeLtfd gCbBlVXErwuny84kz3246pxJRVRTAK+N8Os4T7wuk5RUChE8CGtbzgpFkw1f IB3tGSeT22g5WxNvtZT4AOKFRBPspQnKjo4TtgmmvZD4flCbqwVJBF3D3yfm odgjPdGZQXq6FFJLgreQnTEWzhXh5ECQRZkFIjwr19G4pd9pIUskQufJiRV2 cDFmql56lZK60GU8wQaDjnBopxSWZQiHG9IXkReDLy3sUooURkg7UxgaU2LF WC6dgCryL5KdejypVnOEd8Eexsm9p+jp/P1v3MkdDGN/kAsXmkQG5fj3F2gG kT4EZkHY/QShv33r7mZEaW855q3efszqPaa6NfqsWtDSQTqgpl6dgO1T/t2i WPgOJm4KK1FIkLdVm00xZoc0zdA1NUUbo8JQineYS0MldgX5E8MO81FOM1oo aG/cXvZiGs+08tC/QWmOF/UJWNI8fws3GC0k+u95EQonjlZfRYYGEwjzHNkb PUCyAxwGJyWbzGTZ835gCCsCb+ekdkt490uBFOcYIJvQQwnXOR6MhCaAdL1u 3bHi9XNsUWN1YPEKjtQppBriiDWqaYqCoFrWgyeIOqqB4U2BvHPiX4zCMhRr 3lpjoLxIIWjtmIjfeItilHSxKo1j+Bm0fq2Q4IhNDicruLuYwp4Gz2PpJw6+ Wpxqn68pHSAXK9bw8fwq1Nud4PQk9Y5aTP5Lwalym3c8lWuv1LRE+rOtqAte bBONN8MSEHJNKs4JGladKqFVHnyvm8/tGhmAfDePo28nFTBh2zg4wehSt6Tu /mlwTN4Az6XImdYGOkqZZk48A5XfJBk6tqq0SMnFsBRu4IUMnCYwmC0om6Ds gdp5supVujd4XbJvxzYqEhE6Xi3R8E7Bz1nwJU7FdWAzyQ1ctFtJ+YvDWeXd zC22raKxH1vVzUjF+Su3JiYnA1gzGayX0wKKO3uMqZRmrogyZfIOo71KTfG6 LbKXsHN4BpdTZkcrIBDNmUU77AGd4Y4kLaYWGf8UMDdKF6aMGLrGDAAnSulS tF8mHbQtC4/nTwx1VhGARakjPrjrTNvJLObklBKBoUl3RSlMVWGpFxfMkOsL TBiTFzIk0Ix4afQQwgjSk8j5O2d9m7OAxIra9YcnL42phewleqjbjtQn6JEa nj1T4jKvVISwyYwNJ9vlonKbMuNTy6Ubfylp5y45mN+RUrPyWb1rL2Hcjthh KqpBYRyz9SJZK2bWxgGM6eBXyUNjI5s8VE3jPnwJHZlWqoMyBFZqHBunSin4 dBQ7ktKy+yDwS5bs1LYuZlTDguNFFZmG1eg7iMx1eZ73/vqqTLPX4ewQKY7U iS0K1F4bs4TkYeSElb0tuX7K4dRc2y1OVORsxIYrckPdSm+Y4gBDD8d38EXC wsvDISaOqZOtaf4qpoW6RKhUUZZ7zSWcBHISqV1FIS7eFmbR2lJYREhTr2e6 YFHrw+8exviQzGBBflYclq5IvM+UWkJfGdxEaoiVDcfxg1qsbWJRTpW+j6Xw EEXoN7ChN+JL4ijUJWOHnz61YMNtVga5FK4JUQh2e+vCGeWH2rBl5s18xJeq StCSEVR4UJQaG2WvSoLMEjgQS+7nn100/NNW8f8AgZjqmRCsBgA=[rfced] Acknowledgements section a) Both authors (Justin Richer and Fabien Imbault) are listed multiple times in the Acknowledgements section. This seems odd, especially in the first paragraph. Please review. b) Only Justin is listed as editor, but the Acknowledgements section mentions "the editors" (plural) several times. Should "the editors" be updated to "the authors"? --> <section anchor="Acknowledgements" numbered="false"> <name>Acknowledgements</name> <t>The editors would like to thank the following individuals for their reviews, implementations, and contributions: <contact fullname="Åke Axeland" asciiFullname="Ake Axeland"/>, <contact fullname="Aaron Parecki"/>, <contact fullname="Adam Omar Oueidat"/>, <contact fullname="Andrii Deinega"/>, <contact fullname="Annabelle Backman"/>, <contact fullname="Dick Hardt"/>, <contact fullname="Dmitri Zagidulin"/>, <contact fullname="Dmitry Barinov"/>, <contact fullname="Fabien Imbault"/>, <contact fullname="Florian Helmschmidt"/>, <contact fullname="Francis Pouatcha"/>, <contact fullname="George Fletcher"/>, <contact fullname="Haardik Haardik"/>, <contact fullname="Hamid Massaoud"/>, <contact fullname="Jacky Yuan"/>, <contact fullname="Joseph Heenan"/>, <contact fullname="Justin Richer"/>, <contact fullname="Kathleen Moriarty"/>, <contact fullname="Leif Johansson"/>, <contact fullname="Mike Jones"/>, <contact fullname="Mike Varley"/>, <contact fullname="Nat Sakimura"/>, <contact fullname="Takahiko Kawasaki"/>, <contact fullname="Takahiro Tsuchiya"/>, and <contact fullname="Yaron Sheffer"/>.</t> <t>The editors would also like to thank the GNAP Working Group design team (<contact fullname="Kathleen Moriarty"/>, <contact fullname="Fabien Imbault"/>, <contact fullname="Dick Hardt"/>, <contact fullname="Mike Jones"/>, and <contact fullname="Justin Richer"/>), who incorporated elements from the XAuth and XYZ proposals to create the first draft version of this document.</t> <t>In addition, the editors would like to thank <contact fullname="Aaron Parecki"/> and <contact fullname="Mike Jones"/> for insights into how to integrate identity and authentication systems into the core protocol. The editors also thank <contact fullname="Justin Richer"/> and <contact fullname="Dick Hardt"/> for the use cases, diagrams, and insights provided in the XYZ and XAuth proposals that have been incorporated here. The editors would like to especially thank <contact fullname="Mike Varley"/> and the team at SecureKey for feedback and development of early versions of the XYZ protocol that fed into this standards work.</t> <t>Finally, the editors want to acknowledge the immense contributions of <contact fullname="Aaron Parecki"/> to the content of this document. We thank him for his insight, input, and hard work, without which GNAP would not have grown to what it is.</t> </section> <!-- [rfced] Use of "GNAP protocol" and "GNAP core" a) May we update "the GNAP protocol" and "The core GNAP protocol" to simply "GNAP" in these sentences? If expanded, "GNAP protocol" would read as "Grant Negotiation and Authorization Protocol protocol". Original: * AS/RS: the AS promises to issue valid access tokens to legitimate client requests (i.e. after carrying out appropriate due diligence, as defined in the GNAP protocol). ... The core GNAP protocol makes no assumptions or demands on the format or contents of the access token, but the RS extension allows a negotiation of token formats between the AS and RS. Perhaps: * AS/RS: the AS promises to issue valid access tokens to legitimate client requests (i.e. after carrying out appropriate due diligence, as defined in GNAP). ... GNAP makes no assumptions or demands on the format or contents of the access token, but the RS extension allows a negotiation of token formats between the AS and RS. b) Please review the use of "the GNAP core" in these sentences. Is the intended meaning "GNAP"? Original: Consequently, no interaction methods defined in the GNAP core require the end user to enter their credentials, but it is technologically possible for an extension to be defined to carry such values. ... Managing this binding is outside the scope of GNAP core, but it can be managed either as a configuration element for the client instance or dynamically through discovering the AS from the RS (Section 9.1). Perhaps: Consequently, no interaction methods defined in GNAP require the end user to enter their credentials, but it is technologically possible for an extension to be defined to carry such values. ... Managing this binding is outside the scope of GNAP, but it can be managed either as a configuration element for the client instance or dynamically through discovering the AS from the RS (Section 9.1). c) Please review instances of "The core specification" and "the core protocol" in these sentences, and let us know if any updates are needed. For example, in the first sentence, should "The core specification" be updated to "This specification" or "GNAP"? Original: The core specification makes access tokens opaque to the client and defines the request/response scheme in detail, therefore avoiding extra trust hypotheses from this critical piece of software. This is particularly important in the core protocol for security artifacts such as nonces and for personal information such as subject information. The details of such attestations are outside the scope of the core protocol, but the client portion of a grant request provides a natural extension point to such information through the Client Instance Fields registry (Section 11.7). In GNAP, the most vulnerable place in the core protocol is the push-based post-interaction finish method (Section 4.2.2), as the client instance is less trusted than the AS and can use this method to make the AS call an arbitrary URI. In addition to the core protocol, GNAP supports various patterns of communication between RSs and ASs through extensions. --> <!-- [rfced] Terminology a) We note inconsistencies in the terms listed below. We chose the form on the right. Please let us know any objections. unicode vs. Unicode Detached-JWS HTTP Header field vs. Detached-JWS header HTTP Method vs. HTTP method b) We note inconsistencies in the terms below throughout the text. Should these be uniform? If so, please let us know which form is preferred. polling continue request vs. polled continuation request continue request vs. continuation request push-style callback vs. push callback Attached JWS vs. attached JWS Detached JWS vs. detached JWS OpenID Connect ID Token vs. OpenID Connect's ID token back-end vs. backend Note: Both forms have been used in past RFCs. Which form do you prefer to use in this document? Note that "backend" appears in code in Appendix B.3 and "front-end" (with hyphen) is used in the document. key proofing method vs. key proof method proofing method vs. proof method proofing mechanism vs. proof mechanism c) Please review capitalization, hyphenation, and quotation marks for the following when used in general text, and let us know how to update for consistency. SHA-256 sha-256 "sha-256" SHA-512 SHA256 d) We see the following forms in the document. Should the lowercase form be used in general text per the usage in RFC 9421? HTTP Message Signature vs. HTTP message signature e) This document consistently uses the lowercase "subject identifier" in general text (except for one instance in Section 3). However, RFC 9493 uses the capitalized "Subject Identifier". Which form would you like to use in this document? f) We see the following forms in the document. "datatypes" is defined in Section 8 and appears mostly in code, while "data type" and "data types" appear in general text. Please review and confirm that the usage is correct and consistent. datatypes data types g) We see "Referer" (one "r") used for the header field and "referrer" (two "r"s) used for the parameter and in general text. Are any updated needed for consistency, or is this acceptable? h) We see inconsistencies with the capitalization of the following. Both forms have been used in published RFCs, but the lowercase form is a bit more common. Please let us know how to update for consistency. Base64url vs. base64url Base64 vs. base64 Also, please review "base64 URL encoding" here. Is this correct, or is "base64url" intended? Original: The certificate thumbprint calculated as per OAuth-MTLS [RFC8705] in base64 URL encoding. i) This document uses "SAML 2". Most RFCs that include this term use the form "SAML 2.0". Would you like to update accordingly or leave as is? j) We note that the names of the states are capitalized in Section 1.5 (figure and list) but are lowercased elsewhere. Is this intentional or are updates needed? Approved vs. approved Finalized vs. finalized Pending vs. pending Processing vs. processing --> <!-- [rfced] Abbreviations a) FYI - We have added expansions for the following abbreviations per Section 3.6 of RFC 7322 ("RFC Style Guide"). Please review each expansion in the document carefully to ensure correctness. Security Assertion Markup Language (SAML) Internet of Things (IoT) Privacy-Enhanced Mail (PEM) Elliptic Curve Digital Signature Algorithm (ECDSA) b) How should "RAR" be expanded? Although the title of RFC 9396 includes "Rich Authorization Requests", we do not see the abbreviation "RAR" used in that document. We do see RAR expanded as "Re-Auth-Request (RAR)" in RFCs 6733, 7155, 8506, and 9390. Original: The "resource" indicator (defined in [RFC8707]) and RAR extensions (as defined in [RFC9396]) expand on the "scope" concept in similar but different ways. c) We do not see "OAuth-MTLS" in RFC 8705 or any other published RFC. May we update this sentence to use "Mutual TLS for OAuth" (or something similar) instead of "OAuth-MTLS"? Original: cert#S256 (string): The certificate thumbprint calculated as per OAuth-MTLS [RFC8705] in base64 URL encoding. Perhaps: cert#S256 (string): The certificate thumbprint calculated as per Mutual TLS for OAuth [RFC8705] in base64 URL encoding. d) How should MAC be expanded in this document? The following expansions have been used for MAC in published RFCs: Media Access Control (MAC) Medium Access Control (MAC) Message Authentication Code (MAC) Mandatory Access Control (MAC) e) We see that the following terms and their acronyms are used throughout the document. After the definitions and introduction of the acronyms in Section 1.2, would you like to use the acronyms in the remainder of the document? resource owner (RO) resource server (RS) authorization server (AS) mutual TLS (MTLS) --> <!-- [rfced] Please review the "Inclusive Language" portion of the online Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language> and let us know if any changes are needed. For example, please consider whether the following should be updated: whitespace In addition, please consider whether "traditionally" should be updated for clarity. While the NIST website <https://www.nist.gov/nist-research-library/nist-technical-series-publications-author-instructions#table1> indicates that this term is potentially biased, it is also ambiguous. "Tradition" is a subjective term, as it is not the same for everyone. --> <!-- [rfced] Figures a) In general, for the figures in this document, it seems that parentheses are used for numbers/letters in the ascii-art but not in the SVG. However, in Figure 3, the SVG includes parentheses with the following numbers/letters but not for others. Should the parentheses for these be removed in the SVG? Please review. (A) (B) (1) (7) (12) b) Lists follow Figures 3-11 with numbers/letters relating the parts of the figure. The lists after Figures 3 and 11 use <ul> with hardcoded numbers, perhaps because they include letters in addition to numbers. The lists after Figures 4-10 use <ol>. Would you like to use a consistent format? If you choose to update Figures 3 and 11 to use <ul>, perhaps a nested list would work. For example, for Figure 3, perhaps 1-3 could be nested under A and 4-13 nested under B (or something similar). Please review and let us know. c) The SVG figures in this document (Figures 1-11) have width or height specified, which will make the artwork not scale. Please consider whether scaling should be enabled. Scaling will allow the figure[s] to be resized when viewed on a mobile device; however, there may be aesthetic trade-offs (e.g., a given image may appear too large on a desktop screen or different figures may scale differently based on their relative sizes). Please review the HTML and PDF outputs, noting that we will need you to update the edited copy of the XML and specify the viewBox item where appropriate. --> <!-- [rfced] Formatting a) Please review each artwork element in the xml file. We believe that the 11 artwork elements that are not also tagged as figure should be tagged as sourcecode. If you agree, please let us know how to set the type attribute. If the current list of preferred values for "type" (https://www.rfc-editor.org/rpc/wiki/doku.php?id=sourcecode-types) does not contain an applicable type, then feel free to let us know. Also, it is acceptable to leave the "type" attribute not set. Some examples (currently tagged as artwork): Original: "interact": { "redirect": "https://interact.example.com/4CF492MLVMSW9MKMXKHQ" } ... NOTE: '\' line wrapping per RFC 8792 pyUkVJSmpqSJMaDYsk5G8WCvgY91l-agUPe1wgn-cc5rUtN69gPI2-S_s-Eswed8iB4\ PJ_a5Hg6DNi7qGgKwSQ b) The file below lists terms enclosed in <tt> in this document. https://www.rfc-editor.org/authors/draft-ietf-gnap-core-protocol-19-TT.txt Please review to ensure the use of <tt> is correct and consistent. Let us know if any updates are needed. Some examples of inconsistencies: user field "user" field <tt>user</tt> field finish "finish" <tt>finish</tt> continue response "continue" response <tt>continue</tt> response "bearer" flag <tt>bearer</tt> flag "Authorization" request header field <tt>Authorization Request Header Field</tt> Note: <tt> yields fixed-width font in the html/pdf outputs but no formatting in the txt output. c) The file below lists terms enclosed in <em> in this document. https://www.rfc-editor.org/authors/draft-ietf-gnap-core-protocol-19-EM.txt We see that <em> is used for states (i.e., approved, finalized, pending, and processing) and for the features in Appendix D.1. Two questions: - Is <em> needed in Appendix D.1? Please especially review the txt output, as <em> yield underscores that might look odd in the bulleted list. - For "continuation access token" and "grant endpoint URI", is the intent to use <em> with the first occurrence only? Or should <em> be removed for these terms? Note: <em> yields italics in the html and pdf outputs and yields underscores in the txt output. d) Please review whether any of the notes in this document should be in the <aside> element. It is defined as "a container for content that is semantically less important or tangential to the content that surrounds it" (https://authors.ietf.org/en/rfcxml-vocabulary#aside). e) FYI - We removed a number of links with text per the "Document Links" section of https://www.rfc-editor.org/styleguide/part2/#links. Section pointers and citation tags are still linked. --> </back> </rfc>