Re: [Extra] Francesca Palombini's No Objection on draft-ietf-extra-sieve-mailboxid-07: (with COMMENT)

[Ken Murchison <[e-mail]>]

On 3/16/21 8:50 AM, Bron Gondwana wrote:
> Murray pointed out that I STILL had it wrong.  Uploaded again with a 
> much better version :)
>
> MAILBOXID-OPT = ":mailboxid" objectid
>
> FCC-OPTS =/ MAILBOXID-OPT
>
> objectid is defined in RFC8474 as:
>
>        objectid = 1*255(ALPHA / DIGIT / "_" / "-")
>                ; characters in object identifiers are case
>                ; significant
>
> Of course now that I've posted this, I do wonder if I actually need to 
> make it:
>
> MAILBOXID-OPT = ":mailboxid" SPACE DQUOTE objectid DQUOTE
>
> *sigh*.
>
> I mean, RFC8580 already doesn't seem to be very specific about the 
> whitespace between tokens - but I expect we probably do want the 
> mailboxid to be a string rather than an objectid for parser 
> simplicity.  I welcome input on that!  (I'm pretty sure the parser we 
> have in Cyrus right now needs it to be a string for example)


I don't think adding SPACE is necessary, and no other extension does this.

We definitely want :mailboxid to take a string as argument, since 
RFC5228 doesn't specify anything other than numbers, strings, and 
stringlists.

You can probably do something like what the imap4flags and special-use 
extensions do and simply define:

MAILBOXID-OPT = ":mailboxid" <mailboxid: string>

and state in the text that the mailboxid string is limited to the 
characters allowed in objectid.  Of course, even if you don't state 
this, and the string contains invalid objectid chars, the script will 
still parse as valid, but just not match any mailbox.



> On Tue, Mar 16, 2021, at 15:29, Bron Gondwana wrote:
>> On Fri, Mar 12, 2021, at 23:19, Bron Gondwana wrote:
>>>
>>>
>>> On Fri, Mar 12, 2021, at 23:04, Murray S. Kucherawy wrote:
>>>> On Fri, Mar 12, 2021 at 3:41 AM Francesca Palombini via Datatracker 
>>>> <[e-mail] <mailto:[e-mail]>> wrote:
>>>>
>>>>     I would only like to bring up again Magnus unanswered comment
>>>>     about formal
>>>>     syntax, and hope that the working group can address that before
>>>>     the document
>>>>     moves forward. Thread starting here:
>>>>     https://mailarchive.ietf.org/arch/msg/extra/zuH2VTx-NoXQXFzQ1PeJJkts0Bo/
>>>>     <https://mailarchive.ietf.org/arch/msg/extra/zuH2VTx-NoXQXFzQ1PeJJkts0Bo/>
>>>>
>>>>
>>>> As it happens, EXTRA is meeting at IETF 110 in a couple of hours, 
>>>> and I think the plan is to discuss this there.
>>>>
>>>
>>> Sure is!  I'm putting together slides right now, because there's 
>>> nothing like the last minute.
>>
>> Conclusion from the meeting was:
>>
>> 1) let's just put in the ABNF for FCC-OPTS since that has consistent 
>> syntax that it makes sense to complete.  For everything else, less 
>> than 1/4 of existing sieve extensions have ABNF, so it's not really 
>> sensible to try to extend that - it's all been done with prose.
>>
>> 2) we need to make the :fcc behaviour match the fileinto behaviour 
>> for the relationship between specialuse and mailboxid tests.
>>
>> I made both those changes and uploaded -08 right now.
>>
>> Cheers,
>>
>> Bron.
>>
>> --
>>   Bron Gondwana, CEO, Fastmail Pty Ltd
>>   [e-mail]
>>
>>
>> _______________________________________________
>> Extra mailing list
>> [e-mail] <mailto:Extra%40ietf.org>
>> https://www.ietf.org/mailman/listinfo/extra 
>> <https://www.ietf.org/mailman/listinfo/extra>
>>
>
> --
>   Bron Gondwana, CEO, Fastmail Pty Ltd
>   [e-mail]
>
>
>
> _______________________________________________
> Extra mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/extra

-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC