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

[Christer Holmberg <[e-mail]>]

>And running code...
>
>That was a genuine question -- the language we use drive the way we think.  Handcoding a parser as a state machine vs using a LL(1) parser vs an LR parser introduce different difficulties when
>writing them, and I was wondering if your insistence was because of that.

I have many years of parser implementation experience. Having said that, this specific issue is not related to something I am currently implementing, but more in general.

But, if I am the only one having that issue, I am fine to drop it in order to make progress. I guess you'd agree that SIP is not the first choice if looking for clean and proper syntax :)

Regards,

Christer


On 4/23/21 9:49 AM, Christer Holmberg wrote:
> I didn't know the rules in IETF were "we believe in rough consensus - or in whoever has the most SIP implementations".
> 
> (FWIW, I do have some SIP implementation experience myself.)
> 
> However, I have not objected to your proposal. My issue is whether we really need to define a new syntax for a string value, that doesn't exist anywhere else.
> 
> Regards,
> 
> Christer
> 
> -----Original Message-----
> From: Marc Petit-Huguenin <[e-mail]>
> Sent: perjantai 23. huhtikuuta 2021 19.42
> To: Christer Holmberg <[e-mail]>; Roman Shpount <[e-mail]>
> Cc: Russ Housley <[e-mail]>; IETF STIR Mail List <[e-mail]>
> Subject: Re: [stir] Proposal for update of erratum #6519 - ppt syntax
> 
> I have to ask:  What, in your implementation of STIR, made you so confident that what you propose is better than what Roman (I assume also a SIP implementer) and I (a 5 times SIP implementer and one time STIR implementer) propose?
> 
> On 4/23/21 9:34 AM, Marc Petit-Huguenin wrote:
>> On 4/23/21 9:27 AM, Christer Holmberg wrote:
>>> Hi,
>>>
>>> With quoted string we wouldn't need such text.
>>
>> You would need an even longer text that explains that a quoted-string that contains characters that are not in the definition of token -- excepted for the initial quote and the last quote -- is invalid.  You would also need to explain that, contrary to the rule for a quoted-string, the string is case-insensitive.  And you still have to explain that the string needs to be normalized before copy in the JSON document.
>>
>> So many words.
>>
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>> -----Original Message-----
>>> From: Marc Petit-Huguenin <[e-mail]>
>>> Sent: torstai 22. huhtikuuta 2021 21.07
>>> To: Christer Holmberg <[e-mail]>; Roman Shpount <[e-mail]>
>>> Cc: Russ Housley <[e-mail]>; IETF STIR Mail List <[e-mail]>
>>> Subject: Re: [stir] Proposal for update of erratum #6519 - ppt syntax
>>>
>>> On 4/22/21 11:02 AM, Christer Holmberg wrote:
>>>> Hi,
>>>>
>>>> Another thing. Since we are now using DQUOTE, won't those become part of the ppt value? I guess we don't want that.
>>>
>>> The text I proposed is taking care of that:
>>>
>>> ...a quoted value whose unquoted part is equivalent to the token in the "ppt" parameter, normalized to contain only lowercase characters...
>>>
>>>
>>>>
>>>> Regards,
>>>>
>>>> Christer
>>>>
>>>> ________________________________

-- 
Marc Petit-Huguenin
Email: [e-mail]
Blog: https://protect2.fireeye.com/v1/url?k=2e44e216-71dfdb55-2e44a28d-861fcb972bfc-5f2c34c4704afcbf&q=1&e=c10aea91-1104-429c-a6ce-27af6838c68c&u=https%3A%2F%2Fmarc.petit-huguenin.org%2F
Profile: https://www.linkedin.com/in/petithug