Re: [stir] New Version Notification for draft-ietf-stir-identity-header-errors-handling-01.txt

[Chris Wendt <[e-mail]>]

> On May 2, 2022, at 11:24 AM, Gorman, Pierce <[e-mail]> wrote:
> 
> Few things. First there is a redundant "enable enable" in the abstract paragraph. 

Thanks

> 
> Second, are we currently using compact form for STIR/SHAKEN? I can never remember. I'm thinking we use non-compact form. I worry about introducing more than one way to format things because it invariably introduces parsing errors. I know that's not considered a reason for not developing and occasionally requiring multiple formats in a protocol, but it is a reason to not like it.

We usually use full form, but i think this is sufficiently separate from other things that it should be fine.  It’s really a matter of taking the signature part of the JWT, which is pretty simple text parsing. (after the last period essentially)

> 
> Finally, and probably more importantly, I imagine fault and performance processing regularly uses orig/dest and perhaps especially so if the errors are being captured and analyzed by an autodialer system.

So, i think we are just using signature as identifier, not to necessarily carry information, that is the proposal.

> 
> Pierce
> 
> -----Original Message-----
> From: stir <[e-mail] <mailto:[e-mail]>> On Behalf Of Chris Wendt
> Sent: Monday, May 2, 2022 9:15 AM
> To: IETF STIR Mail List <[e-mail] <mailto:[e-mail]>>
> Subject: Re: [stir] New Version Notification for draft-ietf-stir-identity-header-errors-handling-01.txt
> 
> [External]
> 
> 
> Hi All,
> 
> Based on some of the recent comments in the meeting and on the list, I'm thinking that perhaps it might be best to only use compact form (i.e. just signature) as key for identifying the PASSporT associated with the right error. I thought maybe there was some value to send back the orig/dest or origID parts of PASSporT as well as keys, but maybe i'm thinking that's not as valuable versus keeping the security properties simple.
> Would anyone have any heartburn if I made that change? I suspect not, but thought i would send a note to confirm.
> 
> Thanks!
> 
> -Chris
> 
>> On Apr 19, 2022, at 7:59 PM, [e-mail] wrote:
>> 
>> 
>> A new version of I-D, 
>> draft-ietf-stir-identity-header-errors-handling-01.txt
>> has been successfully submitted by Chris Wendt and posted to the IETF 
>> repository.
>> 
>> Name: draft-ietf-stir-identity-header-errors-handling
>> Revision: 01
>> Title: Identity Header Error Handling
>> Document date: 2022-04-19
>> Group: stir
>> Pages: 7
>> URL: https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-ietf-stir-identity-header-errors-handling-01.txt&amp;data=05%7C01%7Cpierce.gorman%40t-mobile.com%7Cb80319c8faf9448d32d708da2c462c60%7Cbe0f980bdd994b19bd7bbc71a09b026c%7C0%7C0%7C637870977169154119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=PB1PafUgk2YgaiVt3blLwOZNmRqKBTJi8kj7EKBNOb8%3D&amp;reserved=0 <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-ietf-stir-identity-header-errors-handling-01.txt&amp;data=05%7C01%7Cpierce.gorman%40t-mobile.com%7Cb80319c8faf9448d32d708da2c462c60%7Cbe0f980bdd994b19bd7bbc71a09b026c%7C0%7C0%7C637870977169154119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=PB1PafUgk2YgaiVt3blLwOZNmRqKBTJi8kj7EKBNOb8%3D&amp;reserved=0>
>> Status: https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-stir-identity-header-errors-handling%2F&amp;data=05%7C01%7Cpierce.gorman%40t-mobile.com%7Cb80319c8faf9448d32d708da2c462c60%7Cbe0f980bdd994b19bd7bbc71a09b026c%7C0%7C0%7C637870977169154119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=nWPrQqhZibaite8HbMABi5T62ZS6zkWUNDz%2BqKQEDdI%3D&amp;reserved=0 <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-stir-identity-header-errors-handling%2F&amp;data=05%7C01%7Cpierce.gorman%40t-mobile.com%7Cb80319c8faf9448d32d708da2c462c60%7Cbe0f980bdd994b19bd7bbc71a09b026c%7C0%7C0%7C637870977169154119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=nWPrQqhZibaite8HbMABi5T62ZS6zkWUNDz%2BqKQEDdI%3D&amp;reserved=0>
>> Htmlized: https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-stir-identity-header-errors-handling&amp;data=05%7C01%7Cpierce.gorman%40t-mobile.com%7Cb80319c8faf9448d32d708da2c462c60%7Cbe0f980bdd994b19bd7bbc71a09b026c%7C0%7C0%7C637870977169154119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=FuwVQdfoWJRkq9%2BreVYojR50NG78PZbABQ6cfF40NlQ%3D&amp;reserved=0 <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-stir-identity-header-errors-handling&amp;data=05%7C01%7Cpierce.gorman%40t-mobile.com%7Cb80319c8faf9448d32d708da2c462c60%7Cbe0f980bdd994b19bd7bbc71a09b026c%7C0%7C0%7C637870977169154119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=FuwVQdfoWJRkq9%2BreVYojR50NG78PZbABQ6cfF40NlQ%3D&amp;reserved=0>
>> Diff: https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl2%3Ddraft-ietf-stir-identity-header-errors-handling-01&amp;data=05%7C01%7Cpierce.gorman%40t-mobile.com%7Cb80319c8faf9448d32d708da2c462c60%7Cbe0f980bdd994b19bd7bbc71a09b026c%7C0%7C0%7C637870977169154119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=73LVIjO5YDoEJgNHeb5QoRVyVGU9U7G6uoQ3As6xa3k%3D&amp;reserved=0 <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl2%3Ddraft-ietf-stir-identity-header-errors-handling-01&amp;data=05%7C01%7Cpierce.gorman%40t-mobile.com%7Cb80319c8faf9448d32d708da2c462c60%7Cbe0f980bdd994b19bd7bbc71a09b026c%7C0%7C0%7C637870977169154119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=73LVIjO5YDoEJgNHeb5QoRVyVGU9U7G6uoQ3As6xa3k%3D&amp;reserved=0>
>> 
>> 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 Secretariat
>> 
>> 
> 
> _______________________________________________
> stir mailing list
> [e-mail] <mailto:[e-mail]>
> https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fstir&amp;data=05%7C01%7Cpierce.gorman%40t-mobile.com%7Cb80319c8faf9448d32d708da2c462c60%7Cbe0f980bdd994b19bd7bbc71a09b026c%7C0%7C0%7C637870977169154119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=70Qx1Cqb4wmnEwwozA1agPcIcKxNlGIwsR0I7WWihQo%3D&amp;reserved=0 <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fstir&amp;data=05%7C01%7Cpierce.gorman%40t-mobile.com%7Cb80319c8faf9448d32d708da2c462c60%7Cbe0f980bdd994b19bd7bbc71a09b026c%7C0%7C0%7C637870977169154119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=70Qx1Cqb4wmnEwwozA1agPcIcKxNlGIwsR0I7WWihQo%3D&amp;reserved=0>