Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p4FAla65071505 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 15 May 2011 03:47:36 -0700 (MST) (envelope-from owner-ietf-pop3ext@mail.imc.org) Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id p4FAla37071504; Sun, 15 May 2011 03:47:36 -0700 (MST) (envelope-from owner-ietf-pop3ext@mail.imc.org) X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-ietf-pop3ext@mail.imc.org using -f Received: from mail-bw0-f43.google.com (mail-bw0-f43.google.com [209.85.214.43]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p4FAlXNI071499 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for ; Sun, 15 May 2011 03:47:35 -0700 (MST) (envelope-from evnikita2@gmail.com) Received: by bwz14 with SMTP id 14so4913172bwz.16 for ; Sun, 15 May 2011 03:47:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:content-type; bh=sMNWUUYdYy4mzfMjwZtSZS+eQeXjNBk5B+0jbCPBdI8=; b=L9GSzpFUpbdlFmNf71mYsU0iC+LGqhFBOYAtleRxgjF5mfn6r8y+aAQAsjUg2tzSjZ fuDz30JtQsAuBsAbBhbZiX3p7wTnd5Cy00JJHr7n4Q+dSL4wRsJIQlarBLRhd9CEgUCB dbLirD3ZBnUAI1ji4Aihjstj/kfzRjuHFPCuw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :content-type; b=okx2i1SWM8cV3RHPcFAwZAccXCiBkMsi9r7YLqiouACEB1hMJfa+Zlv+GGWezXT97e Ud2WuyQTVyABvktvE3V6DAwJaJ18HxAzh+1Ps65uMcGAKzzuR4xtspUEOMRzxgdN7d6f JASydzoruZjecwhrrAoi6iHCPzGSSeIpCrYxA= Received: by 10.205.82.199 with SMTP id ad7mr2999984bkc.152.1305456452973; Sun, 15 May 2011 03:47:32 -0700 (PDT) Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id q25sm2358171bkk.22.2011.05.15.03.47.31 (version=SSLv3 cipher=OTHER); Sun, 15 May 2011 03:47:32 -0700 (PDT) Message-ID: <4DCFAF6F.9020808@gmail.com> Date: Sun, 15 May 2011 13:48:15 +0300 From: Mykyta Yevstifeyev User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: ietf-pop3ext@imc.org, tls@ietf.org CC: draft-melnikov-pop3-over-tls@tools.ietf.org Subject: Soliciting Comments on draft-melnikov-pop3-over-tls-00 Content-Type: multipart/alternative; boundary="------------030300080601070901050205" Sender: owner-ietf-pop3ext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. --------------030300080601070901050205 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hello all, Alexey Melnikov an I have undertaken an attempt to document the POP3 over TLS binding (aka POP3S). The corresponding I-D is draft-melnikov-pop3-over-tls-00 can be found here: http://tools.ietf.org/html/draft-melnikov-pop3-over-tls-00 The draft replaces old draft-yevstifeyev-pops-uri-scheme (http://tools.ietf.org/html/draft-yevstifeyev-pops-uri-scheme-03) you should be aware of. The new document contains more detailed description of different issues concerning POP3S; however the main issue is TRANSACTION vs. AUTHORIZATION state after TLS handshake and the way of signaling it. I'd like to ask you to provide your comments on this draft, not limited to aforementioned issue only. Please, while responding, keep all recipient addresses in the message. Mykyta Yevstifeyev P.S. The most appropriate list for discussing this draft is certainly ietf-pop3ext, but I think it will be useful to direct the message to tls list in order to allow TLS experts review and comment it. Mykyta --------------030300080601070901050205 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Hello all,

Alexey Melnikov an I have undertaken an attempt to document the POP3 over TLS binding (aka POP3S).  The corresponding I-D is draft-melnikov-pop3-over-tls-00 can be found here:

http://tools.ietf.org/html/draft-melnikov-pop3-over-tls-00

The draft replaces old draft-yevstifeyev-pops-uri-scheme (http://tools.ietf.org/html/draft-yevstifeyev-pops-uri-scheme-03) you should be aware of.  The new document contains more detailed description of different issues concerning POP3S; however the main issue is TRANSACTION vs. AUTHORIZATION state after TLS handshake and the way of signaling it.

I'd like to ask you to provide your comments on this draft, not limited to aforementioned issue only.  Please, while responding, keep all recipient addresses in the message.

Mykyta Yevstifeyev

P.S.  The most appropriate list for discussing this draft is certainly ietf-pop3ext, but I think it will be useful to direct the message to tls list in order to allow TLS experts review and comment it.  Mykyta
--------------030300080601070901050205--