[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: we all refer to LISTEXT as LISTEXT

To: Arnt Gulbrandsen <arnt@xxxxxxxx>
Subject: Re: we all refer to LISTEXT as LISTEXT
From: Alexey Melnikov <alexey.melnikov@xxxxxxxxx>
Date: Wed, 22 Nov 2006 12:40:45 +0000
Cc: ietf-imapext@xxxxxxx
In-reply-to: <hqw6HDpVsNAF4+OpaZWhtQ.md5@xxxxxxxxxxxxxxxxxxx>
List-archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-id: <ietf-imapext.imc.org>
List-unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>
References: <200611211403.12916.martin.konold@xxxxxxxxxxx> <BnLUz+OOPWg2Iuae01CAug.md5@xxxxxxxxxxxxxxxxxxx> <hqw6HDpVsNAF4+OpaZWhtQ.md5@xxxxxxxxxxxxxxxxxxx>
Sender: owner-ietf-imapext@xxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915


Arnt Gulbrandsen wrote:

So maybe the final RFC should name the capability LISTEXT, too. Werefer to all the other extensions by their capability name, and wedon't seem to like the name LIST-EXTENDED...

Communigate also advertises LISTEXT, while supporting a version which isnot compatible with the one implemented by Cyrus.


So I don't think we can use LISTEXT as a capability for the approved draft.

Follow-Ups:
- Re: we all refer to LISTEXT as LISTEXT
  - From: Martin Konold

References:
- we all refer to LISTEXT as LISTEXT
  - From: Arnt Gulbrandsen

Prev by Date: Re: Review of sort
Next by Date: IDnits
Previous by thread: Re: we all refer to LISTEXT as LISTEXT
Next by thread: Re: we all refer to LISTEXT as LISTEXT
Index(es):
- Date
- Thread