Re: [stir] Proposal for update of erratum #6519 - ppt syntax

[Christer Holmberg <[e-mail]>]

Ok

Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Marc Petit-Huguenin <[e-mail]>
Sent: Thursday, April 22, 2021 7:11:34 PM
To: Christer Holmberg <[e-mail]>; Roman Shpount <[e-mail]>; Russ Housley <[e-mail]>
Cc: IETF STIR Mail List <[e-mail]>
Subject: Re: [stir] Proposal for update of erratum #6519 - ppt syntax

This was shorthand for 1) I disagree to everything you said, but I have nothing to add to what I already said and 2) I want to signal to whoever is deciding consensus that I disagree.

On 4/22/21 7:37 AM, Christer Holmberg wrote:
> No what?
>
> ________________________________
> From: Marc Petit-Huguenin <[e-mail]>
> Sent: Thursday, April 22, 2021 12:34 AM
> To: Christer Holmberg <[e-mail]>; Roman Shpount <[e-mail]>; Russ Housley <[e-mail]>
> Cc: IETF STIR Mail List <[e-mail]>
> Subject: Re: [stir] Proposal for update of erratum #6519 - ppt syntax
>
> No.
>
> On 4/21/21 12:40 PM, Christer Holmberg wrote:
>>>> I have not been able to follow the discussion in detail, but is there a reason why we simply can's say:
>>>>
>>>> ident-type = "ppt" EQUAL token / quoted-string
>>>>
>>>> ...and then add text saying that the only token characters are allowed?
>>>
>>> I believe that exceptions to ABNF should be kept to the minimal necessary.
>>
>> My suggestion is a subset of generic-param, which is the generic syntax for the parameters.
>>
>>> Few implementers read the ABNF, few implementers read normative text.  That means that only the intersection of these two sets will do the right thing.
>>>
>>> That's also why we should not deviate from the norm:  We should have used COMMA in Identity, ident-info-uri should have been a field right after signed->identity-digest (similar to name-addr).
>>
>> Perhaps, but that is not what the issue is about.
>>
>> Regards,
>>
>> Christer
>>
>>
>>>
>>>
>>>
>>> ________________________________
>>> From: Roman Shpount <[e-mail]>
>>> Sent: Tuesday, April 20, 2021 5:20 PM
>>> To: Russ Housley <[e-mail]>
>>> Cc: Marc Petit-Huguenin <[e-mail]>; Christer Holmberg <[e-mail]>; IETF STIR Mail List <[e-mail]>
>>> Subject: Re: [stir] Proposal for update of erratum #6519
>>>
>>> Hi Russ,
>>>
>>> The complete grammar would be:
>>>
>>>          Identity = "Identity" HCOLON signed-identity-digest SEMI
>>>              ident-info *( SEMI ident-info-params )
>>>          signed-identity-digest = 1*(base64url-char / ".")
>>>          ident-info = "info" EQUAL ident-info-uri
>>>          ident-info-uri = LAQUOT absoluteURI RAQUOT
>>>          ident-info-params = ident-info-alg / ident-type /
>>>              ident-info-extension
>>>          ident-info-alg = "alg" EQUAL token
>>>          ident-type =  "ppt" EQUAL ( token / ( LDQUOT token RDQUOT ) )
>>>          ident-info-extension = generic-param
>>>
>>> base64url-char = ALPHA / DIGIT / "-" / "_"
>>>
>>> In this grammar, SEMI is defined as SEMI = SWS  ";"  SWS. This should take care of the SWS after the token.
>>> _____________
>>> Roman Shpount
>>>
>>>
>>> On Tue, Apr 20, 2021 at 9:22 AM Russ Housley <[e-mail]<mailto:[e-mail]>> wrote:
>>>
>>>
>>> On Apr 19, 2021, at 9:57 PM, Roman Shpount <[e-mail]<mailto:[e-mail]>> wrote:
>>>
>>> ident-type = "ppt" EQUAL ( token / ( LDQUOT token RDQUOT ) )
>>>
>>> Since RDQUOT allows whitespace after the double quote, do we need to allow whitespace after token when there are no quotes?
>>>
>>>        ident-type = "ppt" EQUAL ( ( token SWS ) / ( LDQUOT token RDQUOT ) )
>>>
>>> Russ
>>>
>>
>>
>> --
>> Marc Petit-Huguenin
>> Email: [e-mail]
>> Blog: https://protect2.fireeye.com/v1/url?k=f5436fb7-aad856b2-f5432f2c-86959e472243-d9535674738af26e&q=1&e=7a194cb8-6230-48c3-b23f-d2e231acea1c&u=https%3A%2F%2Fmarc.petit-huguenin.org%2F
>> Profile: https://www.linkedin.com/in/petithug
>>
>
>
> --
> Marc Petit-Huguenin
> Email: [e-mail]
> Blog: https://protect2.fireeye.com/v1/url?k=3c808f74-631bb671-3c80cfef-86d2114eab2f-c675e5fca897c209&q=1&e=ff81ea56-63b5-4201-94e2-6d0158073ba1&u=https%3A%2F%2Fmarc.petit-huguenin.org%2F
> Profile: https://www.linkedin.com/in/petithug
>


--
Marc Petit-Huguenin
Email: [e-mail]
Blog: https://protect2.fireeye.com/v1/url?k=94d2e976-cb49d194-94d2a9ed-86073b36ea28-1c860d9bb52fa7a0&q=1&e=8f0f87d9-0c36-4141-920a-25094faef6dc&u=https%3A%2F%2Fmarc.petit-huguenin.org%2F
Profile: https://www.linkedin.com/in/petithug