Identity Header Error Handling
draft-wendt-stir-identity-header-errors-handling-00

Document Type Active Internet-Draft (individual)
Author Chris Wendt 
Last updated 2020-11-16
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           C. Wendt
Internet-Draft                                                   Comcast
Intended status: Standards Track                       November 16, 2020
Expires: May 20, 2021

                     Identity Header Error Handling
          draft-wendt-stir-identity-header-errors-handling-00

Abstract

   This document extends STIR and the Authenticated Identity Management
   in the Session Initiation Protocol (SIP) related to error handling
   for STIR verification services and how they feedback errors to STIR
   authentication services.

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 https://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 May 20, 2021.

Copyright Notice

   Copyright (c) 2020 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
   (https://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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Wendt                     Expires May 20, 2021                  [Page 1]
Internet-Draft               Identity Errors               November 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Use of provisional error responses to signal errors without
       terminating the call  . . . . . . . . . . . . . . . . . . . .   3
   4.  Handling of errors when there is multiple identity headers  .   3
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   [RFC8224] in Section 6.2.2 discusses future specifications for
   enhancement of how errors are communicated and the handling of
   multiple identity headers.  This specification provides some
   additional mechanisms for solutions to address these problems.

   In some deployments of STIR and specifically using SIP [RFC3261] as
   defined by [RFC8224], one issue with the current error handling,
   specifically with the use of the defined 4xx error responses, is that
   when an error occurs with the verification of the identity header or
   the PASSporT contained in the identity header and a 4xx response is
   returned, the call is then terminated.  It may be the case that the
   policy for handling errors might be that calls should continue even
   if there is a verification error, in the case of, for example
   inadvertent errors, however the authentication service should still
   be notified of the error so that corrective action can be taken.
   This specification will discuss the use of reason header in
   subsequent provisional (1xx) responses in order to accomplish this.

   For the handling of multiple identity headers and the potential
   situation that some of the identity headers in a call may pass
   verification but others may have errors, this document provides a
   mechanism to add an identifier so that the authentication service can
   identify which identity header is being referred to in the case of an
   error.

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Wendt                     Expires May 20, 2021                  [Page 2]
Internet-Draft               Identity Errors               November 2020

3.  Use of provisional error responses to signal errors without
Show full document text