[Ace] RFC 8392 on CBOR Web Token (CWT)

rfc-editor@rfc-editor.org Tue, 08 May 2018 22:58 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB00412D7EC; Tue, 8 May 2018 15:58:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Herh_gjyJmnn; Tue, 8 May 2018 15:58:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF875124234; Tue, 8 May 2018 15:58:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9203DB81C2E; Tue, 8 May 2018 15:58:16 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ace@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20180508225816.9203DB81C2E@rfc-editor.org>
Date: Tue, 8 May 2018 15:58:16 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/PbpwtK_tE7ewlCL_Su7xxf9hytk>
Subject: [Ace] =?utf-8?q?RFC_8392_on_CBOR_Web_Token_=28CWT=29?=
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2018 22:58:31 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8392

        Title:      CBOR Web Token (CWT) 
        Author:     M. Jones,
                    E. Wahlstroem,
                    S. Erdtman,
                    H. Tschofenig
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2018
        Mailbox:    mbj@microsoft.com, 
                    erik@wahlstromstekniska.se, 
                    erdtman@spotify.com,
                    Hannes.Tschofenig@arm.com
        Pages:      25
        Characters: 46316
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ace-cbor-web-token-15.txt

        URL:        https://www.rfc-editor.org/info/rfc8392

        DOI:        10.17487/RFC8392

CBOR Web Token (CWT) is a compact means of representing claims to be
transferred between two parties.  The claims in a CWT are encoded in
the Concise Binary Object Representation (CBOR), and CBOR Object
Signing and Encryption (COSE) is used for added application-layer
security protection.  A claim is a piece of information asserted
about a subject and is represented as a name/value pair consisting of
a claim name and a claim value.  CWT is derived from JSON Web Token
(JWT) but uses CBOR rather than JSON.

This document is a product of the Authentication and Authorization for Constrained Environments Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC