[Docs] [txt|pdf|xml|html] [Tracker] [Email] [Nits]

Versions: 00

stir                                                            C. Wendt
Internet-Draft                                                   Comcast
Intended status: Standards Track                               M. Barnes
Expires: January 4, 2018                     MLB@Realtime Communications
                                                           July 03, 2017


                   PASSporT SHAKEN Extension (SHAKEN)
                  draft-wendt-stir-passport-shaken-00

Abstract

   This document extends PASSporT, a token object that conveys
   cryptographically-signed information about the participants involved
   in personal communications, to include information defined as part of
   the SHAKEN [ATIS-1000074] specification for indicating an attestation
   level and originating ID.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 4, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of




Wendt & Barnes           Expires January 4, 2018                [Page 1]


Internet-Draft                    idreg                        July 2017


   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  PASSporT 'attest' Claim . . . . . . . . . . . . . . . . . . .   2
   4.  PASSporT 'origid' Claim . . . . . . . . . . . . . . . . . . .   3
   5.  Example . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   6.  Using 'shaken' in SIP . . . . . . . . . . . . . . . . . . . .   3
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
     7.1.  JSON Web Token claims . . . . . . . . . . . . . . . . . .   3
     7.2.  PASSporT Types  . . . . . . . . . . . . . . . . . . . . .   4
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   4
     10.2.  Informative References . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The SHAKEN specification defines a framework for using STIR protocols
   including PASSporT and the STIR certificate framework for
   implementing the cryptographic validation of an authorized originator
   of telephone calls using SIP.  Because the current telephone network
   contains both VoIP and TDM/SS7 originated traffic, there is many
   scenarios that need to be accounted for where PASSporT signatures may
   represent either direct or indirect call origination scenarios.  The
   SHAKEN [ATIS-1000074] specification defines levels of attribution of
   the origination of the call as well as an origination identifier that
   can help create a unique association with the origination of calls
   from various parts of the VoIP or TDM telephone network.  This
   document specifies these indicators as a specified PASSporT
   extension.

2.  Terminology

   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 [RFC2119].

3.  PASSporT 'attest' Claim

   This indicator allows for both identifying the service provider that
   is vouching for the call as well as a clearly indicating what
   information the service provider is attesting to.  The 'attest' claim



Wendt & Barnes           Expires January 4, 2018                [Page 2]


Internet-Draft                    idreg                        July 2017


   can be one of the following three values, 'A', 'B', or 'C' as defined
   in [ATIS-1000074].

4.  PASSporT 'origid' Claim

   The purpose of the unique origination identifier is to assign an
   opaque identifier corresponding to the service provider-initiated
   calls themselves, customers, classes of devices, or other groupings
   that a service provider might want to use for determining things like
   reputation or trace back identification of customers or gateways.
   The value of 'origid' claim is a UUID as defined in [RFC4122].

5.  Example

   Protected Header
   {
      "alg":"ES256",
      "typ":"passport",
      "ppt":"shaken",
      "x5u":"https://cert.example.org/passport.crt"
   }
   Payload
   {
      "attest":"A"
      "dest":{"uri":"sip:alice@example.com"}
      "iat":"1443208345",
      "orig":{"tn":"12155551212"},
      "origid":"123e4567-e89b-12d3-a456-426655440000"
   }

6.  Using 'shaken' in SIP

   The use of the 'shaken' PASSporT type and the claims 'attest' and
   'origid' are formally defined in [ATIS-1000074] for usage in SIP
   [RFC3261] aligned with the use of the identity header defined in
   [I-D.ietf-stir-rfc4474bis].  The carriage of the 'attest' and
   'origid' values are in the full PASSporT token included in the
   identity header as specified in [ATIS-1000074].

7.  IANA Considerations

7.1.  JSON Web Token claims

   This specification requests that the IANA add two new claims to the
   JSON Web Token Claims registry as defined in [RFC7519].

   Claim Name: "attest"




Wendt & Barnes           Expires January 4, 2018                [Page 3]


Internet-Draft                    idreg                        July 2017


   Claim Description: Attestation level as defined in SHAKEN framework

   Change Controller: IESG

   Specification Document(s): [RFCThis]

   Claim Name: "origid"

   Claim Description: Originating Identifier as defined in SHAKEN
   framework

   Change Controller: IESG

   Specification Document(s): [RFCThis]

7.2.  PASSporT Types

   This specification requests that the IANA add a new entry to the
   PASSporT Types registry for the type "shaken" which is specified in
   [RFCThis].

8.  Security Considerations

   TBD

9.  Acknowledgements

   TBD

10.  References

10.1.  Normative References

   [ATIS-1000074]
              ATIS/SIP Forum NNI Task Group, "Signature-based Handling
              of Asserted information using toKENs (SHAKEN)", January
              2017.

   [I-D.ietf-stir-certificates]
              Peterson, J. and S. Turner, "Secure Telephone Identity
              Credentials: Certificates", draft-ietf-stir-
              certificates-14 (work in progress), May 2017.

   [I-D.ietf-stir-passport]
              Wendt, C. and J. Peterson, "Personal Assertion Token
              (PASSporT)", draft-ietf-stir-passport-11 (work in
              progress), February 2017.




Wendt & Barnes           Expires January 4, 2018                [Page 4]


Internet-Draft                    idreg                        July 2017


   [I-D.ietf-stir-rfc4474bis]
              Peterson, J., Jennings, C., Rescorla, E., and C. Wendt,
              "Authenticated Identity Management in the Session
              Initiation Protocol (SIP)", draft-ietf-stir-rfc4474bis-16
              (work in progress), February 2017.

   [RFC4122]  Leach, P., Mealling, M., and R. Salz, "A Universally
              Unique IDentifier (UUID) URN Namespace", RFC 4122,
              DOI 10.17487/RFC4122, July 2005,
              <http://www.rfc-editor.org/info/rfc4122>.

   [RFC7519]  Jones, M., Bradley, J., and N. Sakimura, "JSON Web Token
              (JWT)", RFC 7519, DOI 10.17487/RFC7519, May 2015,
              <http://www.rfc-editor.org/info/rfc7519>.

10.2.  Informative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <http://www.rfc-editor.org/info/rfc2119>.

   [RFC3261]  Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
              A., Peterson, J., Sparks, R., Handley, M., and E.
              Schooler, "SIP: Session Initiation Protocol", RFC 3261,
              DOI 10.17487/RFC3261, June 2002,
              <http://www.rfc-editor.org/info/rfc3261>.

Authors' Addresses

   Chris Wendt
   Comcast
   One Comcast Center
   Philadelphia, PA  19103
   USA

   Email: chris-ietf@chriswendt.net


   Mary Barnes
   MLB@Realtime Communications

   Email: mary.ietf.barnes@gmail.com








Wendt & Barnes           Expires January 4, 2018                [Page 5]


Html markup produced by rfcmarkup 1.123, available from https://tools.ietf.org/tools/rfcmarkup/