IETF Logo Mail Archive

[Uta] draft-ietf-uta-smtp-tlsrpt-20.txt: suggested changes to Section 6.2 (Report Type)

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 02 May 2018 18:57 UTC

Return-Path: <alexey.melnikov@isode.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 5A65012DA12 for <uta@ietfa.amsl.com>; Wed, 2 May 2018 11:57:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.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 s2xL6YI8Xftj for <uta@ietfa.amsl.com>; Wed, 2 May 2018 11:57:13 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 3605912E8D3 for <uta@ietf.org>; Wed, 2 May 2018 11:56:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1525287415; d=isode.com; s=june2016; i=@isode.com; bh=lFEhu1loiWdVpbb/nmk8LllyoFYvkDHxhTjYAko4rQY=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=TGj16H8PFbDB/cJFvAfHcQgc45/WxNsykKR7VK1vKFZ8oEmE3x6nGasqxlGDxCAPQ3QUee hU1gekS6Cjrua+lGGbk8owF8nUeDoBEWA4u7oI5FvdRIAVCH6hzX1DAE3ZzZQ4w9p53fGM bw+qgDFIQdJhjC8Y1HV5J5iNC3EBn1A=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <WuoJ9wBMbh5b@waldorf.isode.com>; Wed, 2 May 2018 19:56:55 +0100
To: uta@ietf.org
References: <152528006604.11163.2648195212177840063@ietfa.amsl.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <3eca2a52-7899-165f-c407-2178d10473e5@isode.com>
Date: Wed, 02 May 2018 19:56:45 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
In-Reply-To: <152528006604.11163.2648195212177840063@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/rx0nq-APKBvQffiABJM8BksvhIU>
Subject: [Uta] draft-ietf-uta-smtp-tlsrpt-20.txt: suggested changes to Section 6.2 (Report Type)
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.22
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, 02 May 2018 18:57:15 -0000

I would like to suggest the following replacement for the Section 6.2 
(Report Type):

OLD:
    This document registers a new parameter "report-type="tlsrpt"" under
    "multipart/report" top-level media type for use with [RFC6522].

    The media type suitable for use as a report-type is defined in the
    following section.

NEW:

    This document creates a new registry for "report-type" parameter to
    Content-Type header field for "multipart/report" top-level media 
type defined in [RFC6522].
    This registry should contain "report-type" parameter value, list of 
corresponding Media Types for

    document defining it and an optional comment. Registration procedure
    for this should be "Specification Required".

    The registry is to be populated with the following entries:

      "tlsrpt", application/tlsrpt+gzip and application/tlsrpt+json, 
[RFCXXXX]

      "disposition-notification", message/disposition-notification, RFC 8098

      "disposition-notification", 
message/global-disposition-notification, RFC 6533

      "delivery-status", message/delivery-status, RFC 1894

      "delivery-status", message/global-delivery-status, RFC 6533

    Media types suitable for use with a report-type="tlsrpt" are defined 
in Sections 6.4 and 6.5.

Does this look reasonable to people?

Thank you,
Alexey

v2.23.0 | Report a Bug | By Email