Re: [stir] WGLC: draft-ietf-stir-identity-header-errors-handling-03.txt

Robert Sparks <rjsparks@nostrum.com> Thu, 25 August 2022 14:22 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1D53C1524AF; Thu, 25 Aug 2022 07:22:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.688
X-Spam-Level:
X-Spam-Status: No, score=-1.688 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id heM5nxgE1izp; Thu, 25 Aug 2022 07:22:49 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08DAEC14CE3F; Thu, 25 Aug 2022 07:22:49 -0700 (PDT)
Received: from [192.168.1.102] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.17.1) with ESMTPSA id 27PEL6WD023864 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 25 Aug 2022 09:21:07 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1661437267; bh=C87xunmSRpmP5DAZdpypByP9uidGdJURo6z98Z4NCp8=; h=Date:To:Cc:References:From:Subject:In-Reply-To; b=jQ0ryetHks9rztKfpchrkw1XyxBSKdDM5DLGDjlY4AgIi0k6nNHCJtExAQms/gKJA z9I1ZPSlZuhAElKBeCMKlz0Z1hodNlnlWG2IfwnpJU7Z6gU1SKfL/JT2djOn2VRJ2/ Oc4Zh+A5ren4CGfMhIg8DZD5CxjaejY5aS9i8arc=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.102]
Message-ID: <480cb290-d2a6-8652-5d91-452e3a182b20@nostrum.com>
Date: Thu, 25 Aug 2022 09:21:01 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.12.0
Content-Language: en-US
To: Christer Holmberg <christer.holmberg@ericsson.com>, Ben Campbell <ben@nostrum.com>, IETF STIR Mail List <stir@ietf.org>
Cc: Chris Wendt <chris-ietf@chriswendt.net>, STIR Chairs <stir-chairs@ietf.org>
References: <166092541721.15611.12331275110612885444@ietfa.amsl.com> <73813D32-314D-4086-BEB9-F37D2887DB90@nostrum.com> <HE1PR07MB44416763F30C0ED896226CCD93729@HE1PR07MB4441.eurprd07.prod.outlook.com>
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <HE1PR07MB44416763F30C0ED896226CCD93729@HE1PR07MB4441.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/cvr0O8joDWUWNH_B5NC_9c8sda4>
Subject: Re: [stir] WGLC: draft-ietf-stir-identity-header-errors-handling-03.txt
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2022 14:22:52 -0000

(Assuming you meant Reason+STIR below, and wearing no hats):

It isn't clear to me that there's a need to say anything more here than 
what RFC3326 says. Perhaps the text can be clear that this uses the 
rules for where the header can occur as RFC3326. I don't think we want 
something _different_, and I don't want to try to restate those rules in 
this document.

RjS


On 8/25/22 9:05 AM, Christer Holmberg wrote:
> Hi,
>
> When the STIR protocol is used, in which SIP response codes can the Reason header(s) be included?
>
> I can only find the following statement: "in the next provisional or final responses sent to the authentication service.".
>
> That is not every explicit. If we want to allow Reason+SIP with *any* SIP response code it would be good to say so.
>
> Regards,
>
> Christer
>
> -----Original Message-----
> From: stir <stir-bounces@ietf.org> On Behalf Of Ben Campbell
> Sent: maanantai 22. elokuuta 2022 2.50
> To: IETF STIR Mail List <stir@ietf.org>
> Cc: Chris Wendt <chris-ietf@chriswendt.net>; STIR Chairs <stir-chairs@ietf.org>
> Subject: [stir] WGLC: draft-ietf-stir-identity-header-errors-handling-03.txt
>
> Hi,
>
> This starts a STIR working group last call for draft-ietf-stir-identity-header-errors-handling-03. Please send feedback tot he authors and the STIR list by September 7. Note that we added a couple of days to the WGLC period due to the US Labor Day holiday.	
>
> As always,any constructive feedback, including feedback to the effect of “I’ve read this and it is ready to go” is helpful.
>
> Thanks!
>
> Ben (For the STIR chairs)
>
>
>> On Aug 19, 2022, at 11:10 AM, internet-drafts@ietf.org 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-03.txt
>>   Pages           : 7
>>   Date            : 2022-08-19
>>
>> 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 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://datatracker.ietf.org/doc/draft-ietf-stir-identity-header-errors-handling/
>>
>> There is also an htmlized version available at:
>> https://datatracker.ietf.org/doc/html/draft-ietf-stir-identity-header-errors-handling-03
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-stir-identity-header-errors-handling-03
>>
>>
>> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
>>
>>
>> _______________________________________________
>> stir mailing list
>> stir@ietf.org
>> https://www.ietf.org/mailman/listinfo/stir
> _______________________________________________
> stir mailing list
> stir@ietf.org
> https://www.ietf.org/mailman/listinfo/stir