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

Hi,

Responses inline.

On 4/19/21 9:48 AM, Christer Holmberg wrote:
> Hi,
> 
> A few comments:
> 
> Q1: Instead of talking about "being tolerant", we say that an implementation MUST accept values with or without quotes.

That would place "with" or "without" quote on equal status, which they do not have.

> 
> ---
> 
> Q2: Regarding the following statement:
> 
> "Note also that the new syntax does not allow for spaces immediately before or immediately after the token when quoted."
> 
> That is wrong. The syntax DOES allow it.

No, it does not.  Let's expand it:

ident-type = "ppt" EQUAL (token / ( SWS DQUOTE token DQUOTE SWS ))

The SWS are possible outside the quotes, but not inside.

> 
> And, why does it bother if there are spaces?

Because now you need to explain that the spaces needs to be removed, before comparing the values.

> 
> Regards,
> 
> Christer
> 
> 
> ________________________________
> From: stir <stir-bounces@ietf.org> on behalf of Marc Petit-Huguenin <marc@petit-huguenin.org>
> Sent: Sunday, April 18, 2021 6:55 PM
> To: stir@ietf.org Mail List <stir@ietf.org>
> Subject: [stir] Proposal for update of erratum #6519
> 
> As discussed during the interim meeting, here's my proposal for the new text of erratum #6519.  Note that "Original Text" and "Corrected Text" refer to the names of the erratum fields, not to the current content:
> 
> - Original Text:
> 
> Section 4 says:
> 
>     ident-type = "ppt" EQUAL token
> 
> 
> - Corrected Text:
> 
> It should say:
> 
>     ident-type = "ppt" EQUAL (token / LDQUOTE token RDQUOTE)
> 
> Furthermore in the second paragraph of section 4, the following sentence should be inserted after 'defines the optional "ppt" parameter (PASSporT Type).':
> 
>     Implementations SHOULD use quotes around the token when sending and be tolerant to the absence of quotes when receiving.
> 
> Similarly in the fourth bullet of the first list in section 4.1, the sentence '...a value equivalent to the quoted value of the "ppt" parameter...' is replaced by:
> 
>     ...a quoted value whose unquoted part is equivalent to the token in the "ppt" parameter...
> 
> Finally in the first paragraph of section 9, the sentence '...The "ppt" parameter value MUST consist of a token...' is replaced by:
> 
>     ...The "ppt" parameter value MUST consist of a token (between quotes)...
> 
> 
> - Notes:
> 
> Based on discussions in the STIR WG, implementations should use the quoted form when sending, but should accept both forms when receiving.  Regardless of the presence of the quotes, the content is treated as a token, i.e. is case-insensitive as explained in RFC 3261 section 7.3.1.  Note also that the new syntax does not allow for spaces immediately before or immediately after the token when quoted.
> 
> --
> Marc Petit-Huguenin
> Email: marc@petit-huguenin.org
> Blog: https://protect2.fireeye.com/v1/url?k=f3adc327-ac36fa25-f3ad83bc-869a14f4b08c-93577bad37148e54&q=1&e=6560ca76-961e-422e-be46-b21dbd7d45d2&u=https%3A%2F%2Fmarc.petit-huguenin.org%2F
> Profile: https://www.linkedin.com/in/petithug
> 
> _______________________________________________
> stir mailing list
> stir@ietf.org
> https://www.ietf.org/mailman/listinfo/stir
> 

-- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug