[lemonade] WGLC compress-02: multiple COMPRESS algorithms

[Tony Hansen <tony at att.com>]

I think the following covers all that is needed to handle the
possibility of future algorithms being needed, while making it suitably
difficult to actually add one.

*IF* in the future, another algorithm were added, and a server supported
both algorithms, how would the additional algorithms be announced? I
think we should choose a method comparable to that used in other
mechanisms that allow multiple values, that is, a comma separated list.

There is no ABNF specified for the COMPRESS capability, so we need to
add this to the ABNF section.

	capability =/ "COMPRESS=" algorithm-list
	algorithm-list = algorithm *["," algorithm]

Just in case, some future algorithms may require arguments to be passed.
I suggest adding the following to the compress ABNF:

        compress    = "COMPRESS" SP algorithm *[SP argument]
	argument    = 1*TEXT

For the IANA considerations section, I think the following would be
appropriate:

7. IANA Considerations

    The IANA is requested to add COMPRESS=DEFLATE to the list of IMAP
    extensions.

    The IANA is requested to maintain one new registry: IMAP Compression
    Algorithms. The registry's purpose is to register compression
    algorithms that may be used with this extension.  New IMAP
    algorithms MUST be defined in a standards track or IESG approved
    experimental RFC.  New IMAP compression algorithms MUST include the
    following information as part of their definition:

	algorithm identifier
	optional arguments
	standard commands affected
	specification reference
	discussion

That's it.

	Tony Hansen
	tony at att.com

_______________________________________________
lemonade mailing list
lemonade at ietf.org
https://www1.ietf.org/mailman/listinfo/lemonade