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

[Chris Wendt <[e-mail]>]

Hi Christer,

I think that is a fair comment, i can do a quick spin of the document to include a similar statement:

“Any SIP Response message, with the exception of a 100 (Trying), MAY contain a Reason header field with a STIR related cause code defined in RFC8224 or future specifications.”

I’ll wait a day or two for any comments and then i’ll spin a new document.

-Chris

> On Aug 25, 2022, at 10:40 AM, Christer Holmberg <[e-mail]> wrote:
> 
> Hi,
>  
> Yes, I meant Reasonse+STIR. It also seems I forgot the background information for my question in my previous e-mail. Sorry for that.
>  
> RFC 3326 says:
>  
>    "Initially, the Reason header field defined here appears to be most
>    useful for BYE and CANCEL requests, but it can appear in any request
>    within a dialog, in any CANCEL request and in any response whose
>    status code explicitly allows the presence of this header field."
>  
> So, my reading it needs to be explicitly indicated for which SIP response status codes Reason can be included.
>  
> For example, RFC 6432, which defines the Reason Q.850 protocol says:
>  
> "This document allows SIP responses to carry Reason header fields as
>    follows:
>  
>       Any SIP Response message, with the exception of a 100 (Trying),
>       MAY contain a Reason header field with a Q.850 [Q.850] cause code."
>  
> Regards,
>  
> Christer
>  
>  
>  
>  
> -----Original Message-----
> From: stir <[e-mail]> On Behalf Of Robert Sparks
> Sent: torstai 25. elokuuta 2022 17.21
> To: Christer Holmberg <[e-mail]>; Ben Campbell <[e-mail]>; IETF STIR Mail List <[e-mail]>
> Cc: Chris Wendt <[e-mail]>; STIR Chairs <[e-mail]>
> Subject: Re: [stir] WGLC: draft-ietf-stir-identity-header-errors-handling-03.txt
>  
> (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 <[e-mail] <mailto:[e-mail]>> On Behalf Of Ben Campbell
> > Sent: maanantai 22. elokuuta 2022 2.50
> > To: IETF STIR Mail List <[e-mail] <mailto:[e-mail]>>
> > Cc: Chris Wendt <[e-mail] <mailto:[e-mail]>>; STIR Chairs <[e-mail] <mailto:[e-mail]>>
> > 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, [e-mail] <mailto:[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-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/ <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 <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 <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
> >> [e-mail] <mailto:[e-mail]>
> >> https://www.ietf.org/mailman/listinfo/stir <https://www.ietf.org/mailman/listinfo/stir>
> > _______________________________________________
> > stir mailing list
> > [e-mail] <mailto:[e-mail]>
> > https://www.ietf.org/mailman/listinfo/stir <https://www.ietf.org/mailman/listinfo/stir>
>  
> _______________________________________________
> stir mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/stir <https://www.ietf.org/mailman/listinfo/stir>