Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Protocol for spelling of 'Authorisation' #44

Closed
wants to merge 2 commits into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions protocols/BE70.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# BE70: Backend extension specification

| name | BE70 |
|----------------------------|--------------------|
| version | 0.1.1(preview) |
| status | proposal |
| authors | Tom Harley (trh) |
| serving component(s) | all |
| consuming component(s) | all |
| basic spec | no |
| can be required by servers | no |
| can be required by clients | yes |

The key words "**MUST**", "**MUST NOT**", "**REQUIRED**", "**SHALL**", "**SHALL NOT**", "**SHOULD**", "**SHOULD NOT**", "**RECOMMENDED**", "**MAY**", and "**OPTIONAL**" in this document are to be interpreted as described in [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt).

## Changelog
### Version 0.1

- First draft

## Dependency
This protocol relies on [Protocol BE01](BE01.md), in particular [the section on using tokens](BE01.md#using-tokens).

## Authorisation Token
A device requiring authorisation **MUST** accept an `Authorization` token (if present) as if it were an `Authorisation` token.

Devices presenting authorisation **MAY** include both an `Authorisation` token and an `Authorization` token, however in this case both tokens **MUST** have identical contents.