Re: [stir] For the sake of implementers, please verify errata in a timely manner

[Chris Wendt <[e-mail]>]

I think that’s slightly different question, historically i think maybe we included as convention just to potentially have something readable directly to indicate the type of PASSporT contained in Base64, but this is as you say optional, and implementations can’t necessarily rely on this, etc. etc.

So yes, we could leave it off, but like i said other examples we keep it on, and i believe as people tend to code to examples, most identity headers i recall seeing also contain “ppt” :)

> On Apr 12, 2021, at 4:19 PM, Alec Fenichel <[e-mail]> wrote:
> 
> Chris,
>  
> Shouldn’t the example be changed to just not include ppt at all? It is an optional parameter that is only needed for compact form PASSporTs.
>  
> Sincerely,
>  
> Alec Fenichel
> Senior Software Architect
> [e-mail] <mailto:[e-mail]>
> [phone]
> TransNexus
>  
> From: stir <[e-mail]> on behalf of Chris Wendt <[e-mail]>
> Date: Monday, April 12, 2021 at 16:07
> To: Roman Shpount <[e-mail]>
> Cc: [e-mail] Mail List <[e-mail]>, Marc Petit-Huguenin <[e-mail]>, Christer Holmberg <[e-mail]>
> Subject: Re: [stir] For the sake of implementers, please verify errata in a timely manner
> 
> Ok, great, and before someone calls me out, the example in rcd-11 is not quoted :) but i’ve fixed that in local version, will fix on next version.
>  
> So, agreed RFC8224 is only thing that needs fixing, and I think Jon sent out note that he also agrees with errata fix for this.  
> 
> 
> On Apr 12, 2021, at 3:53 PM, Roman Shpount <[e-mail] <mailto:[e-mail]>> wrote:
>  
> Chris,
>  
> As far as I am aware all RFCs and ATS examples have ppt quoted in examples. At the same time, in https://tools.ietf.org/html/rfc8224#section-4 <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc8224%23section-4&data=04%7C01%7Calec.fenichel%40transnexus.com%7Cc3ce1516bc694b129cd408d8fdeea848%7C8e2972a2d21d49acb00518e8ceaadee3%7C1%7C0%7C637538548777280771%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=AXf2UPzKbyDcaOctfF0gRP1iMtFicDoLVSopwTsoB8w%3D&reserved=0>
> ident-type = "ppt" EQUAL token
>  
> This grammar does not allow for a quoted value. Considering that examples are informational, I would argue RFC 8224 should take precedence.
> _____________
> Roman Shpount
>  
>  
> On Mon, Apr 12, 2021 at 3:45 PM Chris Wendt <[e-mail] <mailto:[e-mail]>> wrote:
> Hi Roman,
>  
> I tried looking at the drafts/RFCs i was aware of and all of them had quoted ppt in examples.  Probably missed some, can you point to a published document that includes ppt as not quoted in examples?
>  
> Thanks.
>  
> -Chris
> 
> 
> On Apr 9, 2021, at 1:19 PM, Roman Shpount <[e-mail] <mailto:[e-mail]>> wrote:
>  
> Chirster,
>  
> For the record, RFC 8224 was published in February 2018. IETF 101 was in March 2018. The decision was about misreading an already published RFC and using ppt value in quotes in examples in other RFC. There is nothing in RFC 8224 that says that ppt= value should be quoted.
>  
> This makes me think errata should be filed against other documents to fix examples.
>  
> Best Regards,
> _____________
> Roman Shpount
>  
>  
> On Fri, Apr 9, 2021 at 9:42 AM Christer Holmberg <[e-mail] <mailto:[e-mail]>> wrote:
> Hi,
>  
> Since the errata implements a decision that the WG has made, I don’t think it is appropriate to reject it just because one does not agree with the decision.
>  
> The WG can of course make a new decision.
>  
> Regards,
>  
> Christer
>  
> From: stir <[e-mail] <mailto:[e-mail]>> On Behalf Of Roman Shpount
> Sent: perjantai 9. huhtikuuta 2021 8.31
> To: Marc Petit-Huguenin <[e-mail] <mailto:[e-mail]>>
> Cc: [e-mail] <mailto:[e-mail]> Mail List <[e-mail] <mailto:[e-mail]>>
> Subject: Re: [stir] For the sake of implementers, please verify errata in a timely manner
>  
> On Thu, Apr 8, 2021 at 8:50 AM Marc Petit-Huguenin <[e-mail] <mailto:[e-mail]>> wrote:
> 5. https://www.rfc-editor.org/errata/eid6499 <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fprotect2.fireeye.com%2Fv1%2Furl%3Fk%3Def89db14-b012e23f-ef899b8f-866038973a15-fdf914a9f542a726%26q%3D1%26e%3D8813711f-31d5-4b19-9e71-65401444b97d%26u%3Dhttps%253A%252F%252Fwww.rfc-editor.org%252Ferrata%252Feid6499&data=04%7C01%7Calec.fenichel%40transnexus.com%7Cc3ce1516bc694b129cd408d8fdeea848%7C8e2972a2d21d49acb00518e8ceaadee3%7C1%7C0%7C637538548777290767%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2F%2BciniHt1piDh3WKBFBbNEgibPlAeGH%2Fmnbzn%2FJ3Yus%3D&reserved=0>
> 
> I disagree with that -- wrong examples, especially from another SDO, should not change normative text.   In itself adding quotes around a token is puzzling.  An additional unintended consequence is that quoted strings are case-sensitive, whereas tokens are case insensitive, so that may create an additional interop issue.
> 
> For these reason my implementation decision is to ignore that errata until it is verified.
>  
> I actually agree with you that the ppt value token should not be quoted. The reason I posted this as an errata was that there was a decision was made during IETF 101 that quotes around ppt values are mandatory (https://mailarchive.ietf.org/arch/msg/stir/tI1dJUYPFiEvYIHBCmsBiVvQ0GE/ <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fstir%2FtI1dJUYPFiEvYIHBCmsBiVvQ0GE%2F&data=04%7C01%7Calec.fenichel%40transnexus.com%7Cc3ce1516bc694b129cd408d8fdeea848%7C8e2972a2d21d49acb00518e8ceaadee3%7C1%7C0%7C637538548777290767%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=FdqigXUAGjauXDnLj5d79L17I84kpDGcTpcnlc6JApQ%3D&reserved=0>). I am also dealing with implementations that quote the value, and I need to be absolutely sure this is incorrect when dealing with them.
> _____________
> Roman Shpount 
> _______________________________________________
> stir mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/stir <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fstir&data=04%7C01%7Calec.fenichel%40transnexus.com%7Cc3ce1516bc694b129cd408d8fdeea848%7C8e2972a2d21d49acb00518e8ceaadee3%7C1%7C0%7C637538548777300758%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=XVdAGpoQaHssZXsEr4pa7H75sDaa6RuKpzDSx6zwTFc%3D&reserved=0>