IETF Logo Mail Archive

Re: [secdir] Secdir last call review of draft-ietf-uta-smtp-tlsrpt-17

Phillip Hallam-Baker <hallam@gmail.com> Thu, 22 March 2018 16:09 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1519D1200FC; Thu, 22 Mar 2018 09:09:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 BC4NMa4R9jlR; Thu, 22 Mar 2018 09:09:28 -0700 (PDT)
Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (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 CAB901242F5; Thu, 22 Mar 2018 09:09:28 -0700 (PDT)
Received: by mail-oi0-x234.google.com with SMTP id 23-v6so7807289oir.11; Thu, 22 Mar 2018 09:09:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QyoRXof/CxpvAE6mDcG4pE1XQTllc6sOr1JJZOIq5aU=; b=qdJrBG2u2aYQ6TFOio6CNfFUFNMGOP5HHQRLFKeuX6JErNUIi1qHcfH3diDumeR5xA 2f9WpsI0ZKgoqK+Gns6MnRdaoTDYeVd+2FajWc2Z+dktP5828wihFrM4E5M97Xj0YCTs ns+7KFgw+6FB+kkXTL0TIa7M7lbY8bc0xAbFSWLQfhtCRVDQhtbHBFNoPXBA8Vk/Yudb D9prwxXajpvRmMWiHW1bvWrfrxImwTz0D3SgkRpJJmPjFzTnBUiRLCEsJKL/iQYF46zt bssSWyVznQ8Nl6kH/lLOL0q6hl9nKeGzC1PMznpKEuvF6zfOk/JBsDa0UCoT5/0ORqJa M6uw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=QyoRXof/CxpvAE6mDcG4pE1XQTllc6sOr1JJZOIq5aU=; b=Z9yEFwOuoN6qMzJdKh1lAbKC5ccZEZSswrOtFMw8nf5OcAoi6S+zwq1cfRgvlBTfqQ uvgO+W/Y4dISQlSzmGxPSSvoJUXrEnmlSNtRFAkBMDPf5I+jbJM1P+ZEOJ3zsweUiZkp /FBRbVpHM3kMVzvJQQY9xyfYO5ZUSNv+gewWxE37v2fZZZWS33r4RcI3uGnU2CGwPVfW oEDoe7k7gLKG9VLKCcS8TceVShPJ3i1ayExnfzf8rfDggwJzyjdlei2rOfLC5tsGWeG4 +tnyLVa4L+H2b532+09kPmccX/IdYxcN5XWqjkh3hirnbYGaN0xuDlXI0GiTMMrI3YlN aerQ==
X-Gm-Message-State: AElRT7HEmR6lXSbEFhGFcy0pldYhMl4BDwTJqsUV311Omz2rtLwy5u0B M379gjMh+dp81s7eaBeZhzHv54Fgwu45m7iQ88E=
X-Google-Smtp-Source: AG47ELuzPc0lru4WLJo6ohN7GQH5rALM7vCVlXPs1CLuGraKnJDrn8r/3voQevHbCqYM2yGlkoy7jBNyO8vuQAtFMoM=
X-Received: by 10.202.206.13 with SMTP id e13mr15280063oig.34.1521734967804; Thu, 22 Mar 2018 09:09:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a9d:233c:0:0:0:0:0 with HTTP; Thu, 22 Mar 2018 09:09:27 -0700 (PDT)
In-Reply-To: <5AB3C901.5010009@isode.com>
References: <152053794569.13938.10396254284390037265@ietfa.amsl.com> <5AB3C901.5010009@isode.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
Date: Thu, 22 Mar 2018 16:09:27 +0000
Message-ID: <CAMm+LwjzaHRO8PDNwSUEEETcEZfNiKbTc4-jo91Rj03Cg2Qy4g@mail.gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: secdir@ietf.org, uta@ietf.org, draft-ietf-uta-smtp-tlsrpt.all@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113d225a32cb65056802882f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/ccxA4IFwKJWAc4wnyI9HlR-NR0g>
Subject: Re: [secdir] Secdir last call review of draft-ietf-uta-smtp-tlsrpt-17
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 16:09:31 -0000

I concur, I had come to essentially the same conclusion after discussions
with IANA. The registry we were looking for was the one Dave had proposed
that has not yet been created.

I can sync with Dave.

It might well be that what we want is a sub registry of the form
_smtp._rpt. That way the reporting info for any protocol can be discovered
with no need to obtain a per service registration.

On Thu, Mar 22, 2018 at 3:17 PM, Alexey Melnikov <alexey.melnikov@isode.com>
wrote:

> Hi Phillip,
> To followup on the IANA issue from your SecDir review:
>
> On 08/03/2018 19:39, Phillip Hallam-Baker wrote:
> >
> > Specific issues
> >
> > The DNS prefix _smtp-tlsrpt is defined. This is not mentioned in the IANA
> > considerations. It is a code point being defined in a protocol that is
> outside
> > the scope of UTA and therefore MUST have an IANA assignment and is a DNS
> code
> > point which is shared space and therefore MUST have an assignment.
> >
> > If no IANA registry exists, one should be created.
>
> After looking at this in more details, I think a new registration in the
> registry being created by draft-ietf-dnsop-attrleaf is exactly what you
> are asking for. I think registering _smtp-tlsrpt there should be
> straightforward. However I don't think this document should be delayed
> until after draft-ietf-dnsop-attrleaf is done. So if
> draft-ietf-dnsop-attrleaf is taking time, the proposed registration can
> be moved to draft-ietf-dnsop-attrleaf itself.
>
> > In general, the approach should be consistent with the following:
> >
> > [RFC6763] S. Cheshire and M. Krochmal "DNS-Based Service Discovery" RFC
> 6763
> > DOI 10.17487/RFC6763 February 2013
> >
> > It might well be appropriate to create a separate IANA prefix registry
> > 'report'. That is probably easier since this prefix does not fit well
> with the
> > existing ones.
> >
> > _smtp-tlsrpt._report
>
> I think this is covered by draft-ietf-dnsop-attrleaf.
>
> Best Regards,
> Alexey
>
>


-- 
Website: http://hallambaker.com/

v2.23.0 | Report a Bug | By Email