Skip to content

Commit

Permalink
Add a Relying Party conformance class. (#604)
Browse files Browse the repository at this point in the history
* Add a Relying Party conformance class.

Fixes #88.

* Link "Relying Party".
  • Loading branch information
jyasskin authored and equalsJeffH committed Oct 12, 2017
1 parent 394c9c0 commit 527aaf6
Showing 1 changed file with 23 additions and 10 deletions.
33 changes: 23 additions & 10 deletions index.bs
Original file line number Diff line number Diff line change
Expand Up @@ -197,19 +197,32 @@ A variety of additional use cases and configurations are also possible, includin

# Conformance # {#conformance}

This specification defines criteria for a [=Conforming User Agent=]: A User Agent MUST behave as described in this
specification in order to be considered conformant. [=Conforming User Agents=] MAY implement algorithms given in this
specification in any way desired, so long as the end result is indistinguishable from the result that would be obtained by the
specification's algorithms. A conforming User Agent MUST also be a conforming implementation of the IDL fragments of this
specification, as described in the “Web IDL” specification. [[!WebIDL-1]]
This specification defines three conformance classes. Each of these classes is specified so that conforming members of the class
are secure against non-conforming or hostile members of the other classes.

This specification also defines a model of a conformant [=authenticator=] (see [[#authenticator-model]]). This is a set of
functional and security requirements for an authenticator to be usable by a [=Conforming User Agent=]. As described in
[[#use-cases]], an authenticator may be implemented in the operating system underlying the User Agent, or in external hardware,
or a combination of both.
## User Agents ## {#conforming-user-agents}

A User Agent MUST behave as described by [[#api]] in order to be considered conformant. [=Conforming User Agents=] MAY implement
algorithms given in this specification in any way desired, so long as the end result is indistinguishable from the result that
would be obtained by the specification's algorithms.

## Dependencies ## {#dependencies}
A conforming User Agent MUST also be a conforming implementation of the IDL fragments of this specification, as described in the
“Web IDL” specification. [[!WebIDL-1]]

## Authenticators ## {#conforming-authenticators}

An [=authenticator=] MUST provide the operations defined by [[#authenticator-model]], and those operations MUST behave as
described there. This is a set of functional and security requirements for an authenticator to be usable by a [=Conforming User
Agent=].

As described in [[#use-cases]], an authenticator may be implemented in the operating system underlying the User Agent, or in
external hardware, or a combination of both.

## [RPS] ## {#conforming-relying-parties}

A [=[RP]=] MUST behave as described in [[#rp-operations]] to get the security benefits offered by this specification.

# Dependencies # {#dependencies}

This specification relies on several other underlying specifications, listed
below and in [[#index-defined-elsewhere]].
Expand Down

0 comments on commit 527aaf6

Please sign in to comment.