Binary Application Record Encoding (BARE)
draft-devault-bare-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Drew DeVault | ||
| Last updated | 2021-05-24 (latest revision 2020-11-20) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-devault-bare-01.txt
https://www.ietf.org/archive/id/draft-devault-bare-01.txt
Abstract
The Binary Application Record Encoding (BARE) is a data format used to represent application records for storage or transmission between programs. BARE messages are concise and have a well-defined schema, and implementations may be simple and broadly compatible. A schema language is also provided to express message schemas out-of-band. Comments Comments are solicited and should be addressed to the mailing list at ~sircmpwn/public-inbox@lists.sr.ht and/or the author(s).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)