Re: [stir] I-D Action: draft-ietf-stir-identity-header-errors-handling-05.txt

[Christer Holmberg <[e-mail]>]

Hi,

Not sure if I commented on this earlier, but the title of Section 4 is:

"4.  Use of provisional error responses to signal errors without terminating 
the call"

In SIP there is no such thing as "provisional error response". I think it 
should say "provisional response to signal errors..."

Regards,

Christer

-----Original Message-----
From: stir <[e-mail]> On Behalf Of Chris Wendt
Sent: Monday, 3 October 2022 15.03
To: [e-mail]
Subject: Re: [stir] I-D Action: 
draft-ietf-stir-identity-header-errors-handling-05.txt

Hi All,

I did a minor update for an inconsistency that was found during some review 
for 3GPP.  This is the change, in Section 3 i added the following 
clarification to make it consistent with Section 4:

any _provisional_ SIP Response message _or final response message_, with the 
exception of a 100 (Trying), MAY contain one or more Reason header fields with 
a STIR related cause code defined in [RFC8224] or future specifications.

Let me know if there is any concerns.

Thanks.

-Chris

> On Oct 3, 2022, at 7:59 AM, [e-mail] wrote:
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the Secure Telephone Identity Revisited WG of 
> the IETF.
>
>        Title           : Identity Header Errors Handling
>        Author          : Chris Wendt
>  Filename        : draft-ietf-stir-identity-header-errors-handling-05.txt
>  Pages           : 7
>  Date            : 2022-10-03
>
> Abstract:
>   This document extends STIR and the Authenticated Identity Management
>   in the Session Initiation Protocol (SIP) error handling procedures to
>   include the mapping of verification failure reasons to STIR defined
>   4xx codes so the failure reason of an Identity header field can be
>   conveyed to the upstream authentication service when local policy
>   dictates that the call should continue in the presence of a
>   verification failure.  This document also defines procedures that
>   enable a failure reason to be mapped to a specific Identity header
>   for scenarios that use multiple Identity header fields where some may
>   have errors and others may not and the handling of those situations
>   is defined.
>
>
> The IETF datatracker status page for this draft is:
> https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-2650c0cc9a2d6576&q=1&e=e590a4b7-5afa-4319-8405-16064dcdeea5&u=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-stir-identity-header-errors-handling%2F
>
> There is also an htmlized version available at:
> https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-14f78f7bd980af74&q=1&e=e590a4b7-5afa-4319-8405-16064dcdeea5&u=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-stir-identity-header-errors-handling-05
>
> A diff from the previous version is available at:
> https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-d25c94871cacb631&q=1&e=e590a4b7-5afa-4319-8405-16064dcdeea5&u=https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl2%3Ddraft-ietf-stir-identity-header-errors-handling-05
>
>
> Internet-Drafts are also available by rsync at 
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> stir mailing list
> [e-mail]
> https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-c86045d26e773717&q=1&e=e590a4b7-5afa-4319-8405-16064dcdeea5&u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fstir

_______________________________________________
stir mailing list
[e-mail]
https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-c86045d26e773717&q=1&e=e590a4b7-5afa-4319-8405-16064dcdeea5&u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fstir