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

* Nit: In the abstract: s/enable enable/enable/.
* Would it make sense to say that a STIR Reason header SHOULD be sent when
verification fails and the call is not rejected (also, hopefully, with a
recognizable error indication)? Section 4 has a "SHOULD NOT" for sending a
SIP 4xx response but I'm not sure if that sentence amounts to a SHOULD for
sending a STIR Reason.

Otherwise, looks good to me.

Thanks,
Anders

On Sun, Aug 21, 2022 at 4:50 PM Ben Campbell <ben@nostrum.com> wrote:

> 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
>