Re: [Uta] Last call: <draft-ietf-uta-smtp-require-tls-03> "SMTP Require TLS Option"
"Valery Smyslov" <smyslov.ietf@gmail.com> Wed, 15 August 2018 14:55 UTC
Return-Path: <smyslov.ietf@gmail.com>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E897C129C6A for <uta@ietfa.amsl.com>; Wed, 15 Aug 2018 07:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level:
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=1.5, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c8yhxKR2XCm8 for <uta@ietfa.amsl.com>; Wed, 15 Aug 2018 07:55:27 -0700 (PDT)
Received: from mail-lf1-x143.google.com (mail-lf1-x143.google.com [IPv6:2a00:1450:4864:20::143]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC488127598 for <uta@ietf.org>; Wed, 15 Aug 2018 07:55:26 -0700 (PDT)
Received: by mail-lf1-x143.google.com with SMTP id 95-v6so1073338lfy.9 for <uta@ietf.org>; Wed, 15 Aug 2018 07:55:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version :content-transfer-encoding:thread-index:content-language; bh=VLZ5As8Fb//onK4EJwhZFR+dvpxWev9uruijxgcoj08=; b=eC/6V5Tu/4RjnwjjKGOJ0qWNDxwGApvfoFECCHeZaPdI+QDTindhZGA7zrMVKFNU9I E4giHRqGUD0f9arn3bmgFe0U+RpEoJdYSMZCkhE0yafrNopA9awdLo+nOXYblWrpYntj VIYosVF4e2qSdJBfOfhrssKErCeWuD6hjP33GQW0ScQnE4+6ZomnNHtEGGpYCrFiBjhd pq9hmnrIObE440R/tFrLxet7HF9Jt5oDDSNDMqZCQe7cRK7ancv2Fd/PScCu9ZVCTj3N YicOiDkQRHaxAY7XTvqxDUe6tdDclDEfWdpLM3dMwk9so1kdMyVafZQPGTFFXrgZgZzO VEFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-transfer-encoding:thread-index:content-language; bh=VLZ5As8Fb//onK4EJwhZFR+dvpxWev9uruijxgcoj08=; b=KwejMVwaPPjy7lmFEH9tp76RZ8N/jlkGKYjGmVJSjR95d7mlBkEsYcVMLB6LgVtnr/ gLZOQE+4+OHBeY5trAz0Z4apCxfpvH/xVnAZiXBOgwpnKn/kerPX9UH989evajo5MsOK wRogbdAQPfCdYBUezzk5ONSp5YSW5Y1qJEygqKRffe5KJ6k/IeZJR8NIO0LvKnLaW9Yn 7U7/FEFI/PLxIAAQTX1r+kRwrQvmmBSUZa14zVHuvwKxnUR68HlH4IhkV7rerndtgeg7 u/+DbfmbrK7lbzCVvKGLWSf2zdYIqubqMn+Q8RwhjyStUQAqtqlaLicobzefHq4Erq9B Abxg==
X-Gm-Message-State: AOUpUlEXU8R46w3rLqZ7hOOhZKN8ZLkmCDjmjeQbK3uK4v+Alr9Y2U4+ kGVwYp7Bdsr07j0uE1+hZVk=
X-Google-Smtp-Source: AA+uWPz/bN7KN6cOkAkR2Rk3bLx3sghu1phc+d5Gr1Xx9N5OGyv/0sjvMCWqq1GBBmrOn+8V9+ZdAw==
X-Received: by 2002:a19:5911:: with SMTP id n17-v6mr17824542lfb.102.1534344925286; Wed, 15 Aug 2018 07:55:25 -0700 (PDT)
Received: from buildpc ([82.138.51.4]) by smtp.gmail.com with ESMTPSA id t15-v6sm4020376ljh.21.2018.08.15.07.55.24 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 15 Aug 2018 07:55:24 -0700 (PDT)
From: Valery Smyslov <smyslov.ietf@gmail.com>
To: uta@ietf.org
Date: Wed, 15 Aug 2018 17:55:15 +0300
Message-ID: <002801d434a7$fab29f60$f017de20$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdQ0dLqVhI0XrshOTRStZU4M4PKwjQ==
Content-Language: ru
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/ZyC8AYD7EAaqLXnvtPn97880_Y4>
Subject: Re: [Uta] Last call: <draft-ietf-uta-smtp-require-tls-03> "SMTP Require TLS Option"
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2018 14:55:29 -0000
Hi, here is my review of the document. The draft is well written, however I found few places where it could be improved. 1. Section 2: In the following para: In order to specify REQUIRETLS treatment for a given message, the REQUIRETLS option is specified on the MAIL FROM command when that message is transmitted. This option MUST only be specified in the context of an SMTP session meeting the security requirements that have been specified: The last sentence uses uppercase MUST, while in fact using MUST NOT is more appropriate giving the meaning of the sentence. I.e. "This option MUST NOT be specified unless all the following requirements are met in the context of SMTP session:" And in the following list I believe using uppercase words is unnecessary, since they described not a protocol (REQUIRETLS) behavior, but the requirements for REQUIRETLS to be used. I suggest changing those MUSTs to lowercase. o The session itself MUST employ TLS transmission. o The certificate presented by the SMTP server MUST either verify successfully in a trust chain leading to a certificate trusted by the SMTP client or it MUST verify succesfully using DANE as specified in RFC 7672 [RFC7672]. For trust chains, the choice of trusted (root) certificates is at the discretion of the SMTP client. o Following the negotiation of STARTTLS, the SMTP server MUST advertise in the subsequent EHLO response that it supports REQUIRETLS. 2. I also have a question regarding the last bullet above - why advertising REQUIRETLS is linked with negotiation of STARTTLS? It is my understanding that TLS session may be established without negotiation STARTTLS (as recommended by RFC8314), so why the last bullet doesn't say just: "The SMTP server must advertise in the EHLO response that it supports REQUIRETLS"? Am I missing something here? The same question is applicable to the first para in Section 4.3, where STARTTLS and REQUIRETLS are also logically linked. (and note a typo in a second bullet above: s/succesfully/successfully) 3. Section 8.1. REQUIRETLS is generally effective against passive attackers who are merely trying to eavesdrop on an SMTP exchange between an SMTP client and server. This assumes, of course, the cryptographic integrity of the TLS connection being used. I assume that it is encryption (and not an integrity) that protects messages confidentiality against passive eavesdroppers, doesn't it? Regards, Valery. > Hi, > > this message starts extended 4-week Workgroup Last Call for > <draft-ietf-uta-smtp-require-tls-03> "SMTP Require TLS Option". > The WGLC will end on August 15th. Please, review the document > (especially if you promised to do it earlier). > > Regards, > Leif & Valery.
- [Uta] Last call: <draft-ietf-uta-smtp-require-tls… Valery Smyslov
- Re: [Uta] Last call: <draft-ietf-uta-smtp-require… Valery Smyslov
- Re: [Uta] Last call: <draft-ietf-uta-smtp-require… Jim Fenton
- Re: [Uta] Last call: <draft-ietf-uta-smtp-require… Jeremy Harris
- Re: [Uta] Last call: <draft-ietf-uta-smtp-require… Valery Smyslov
- Re: [Uta] Last call: <draft-ietf-uta-smtp-require… Valery Smyslov
- Re: [Uta] Last call: <draft-ietf-uta-smtp-require… Viktor Dukhovni
- Re: [Uta] Last call: <draft-ietf-uta-smtp-require… Jim Fenton