Subject: [rfc-dist] RFC 8588 on Personal Assertion Token (PaSSporT) Extension for Signature-based Handling of Asserted information using toKENs (SHAKEN)

From: [email-masked]
Date: Tue, 14 May 2019 18:35:02 -0700 (PDT)

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

        RFC 8588

        Title:      Personal Assertion Token (PaSSporT) Extension 
                    for Signature-based Handling of Asserted information 
                    using toKENs (SHAKEN) 
        Author:     C. Wendt, 
                    M. Barnes
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2019
        Mailbox:    [email-masked], 
                    [email-masked]
        Pages:      9
        Characters: 17254
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-stir-passport-shaken-08.txt

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

        DOI:        10.17487/RFC8588

This document extends the Personal Assertion Token (PASSporT), which
is a token object that conveys cryptographically signed information
about the participants involved in communications.  The extension is
defined based on the "Signature-based Handling of Asserted                                    
information using toKENs (SHAKEN)" specification by the ATIS/SIP
Forum IP-NNI Task Group.  It provides both (1) a specific set of
levels of confidence in the correctness of the originating identity
of a call originated in a SIP-based telephone network as well as (2)
an identifier that allows the Service Provider (SP) to uniquely
identify the origin of the call within its network.

This document is a product of the Secure Telephone Identity Revisited 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 [email-masked].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC

_______________________________________________
rfc-dist mailing list
[email-masked]
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org