Re: [dmarc-ietf] signing keys for arc-seal/arc-message-signature
Seth Blank <seth@valimail.com> Wed, 24 May 2017 18:35 UTC
Return-Path: <seth@valimail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E50C1201F2 for <dmarc@ietfa.amsl.com>; Wed, 24 May 2017 11:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.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 HnCzjeDZ2nGA for <dmarc@ietfa.amsl.com>; Wed, 24 May 2017 11:35:34 -0700 (PDT)
Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::231]) (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 9BC69124281 for <dmarc@ietf.org>; Wed, 24 May 2017 11:35:34 -0700 (PDT)
Received: by mail-qt0-x231.google.com with SMTP id f55so162842580qta.3 for <dmarc@ietf.org>; Wed, 24 May 2017 11:35:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SxbcEdzn7krB5RcmRGmoA7dYJOM8yg6BIO5Pgrb9N0U=; b=RyYksnDsaVoSHVySCgl18r0fJ0YVBUqlpyzX5JyPO6529UMmGKX4TfK/D3AyVepr9n ExEdfserJl96xaNwV4WLZRFPpL2gSTwal0TC9S5bSRrTqknfxKL3QE5APoDEfMEjpiqv LFbQFzw+seNZG3bvUUeVhXHMJfeSxe2SC83hoCV/rY5GCbkkQ5eG7Il6pYFbSjPk+6ZV gq1Pv/3RR0wvl7UYEotLBfWI/xAGouypIhuk3yodL5WeOOjUu4I7XK/OZ+lZhb232Ap+ Ng84qn7TPOzGOSLtwaHObl12RFNu659YpRCnStQDZvYpxmUZPvI3f1S8cvjbbWRvKiXG 5OKA==
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=SxbcEdzn7krB5RcmRGmoA7dYJOM8yg6BIO5Pgrb9N0U=; b=oaIQhWgLtHweDTJc/ZgW0QaBvZ7H3CDvbq4HAO8DaFZXRDv1/XCaj+/GbpVi2/HcHe dvKM5hqH4lUZnQmiclJjcnezMZtUW+vzMqBPOGexdTFaF8nMEYJPS1gyOj3fIQRG6FAg L6Ifg1ebO4EL+KLCNArCg+RHFfncrjDfJfmOoTz4jd/1B3ej05ZUaB6F47b8Q4UkTAzm zFwNUaX1sXUbUwugc4YyAr5tdC6yfB4p2tqryw+owfha+fHP8xh/62BBemUtgeJ59IhH tuz77VOvwJJlItyXuGB+I8qZgJLTOxiTpuDoD4flPU2BiVC6dkl7cmxuWsh+AOc1oHvs RC7A==
X-Gm-Message-State: AODbwcB/XBbalYar3Lo+YfQysROXpvgLIB5XTl3nSapWhunEBrdYeHZE ev+rX7w3eoB1IRRx7kt3qRBJJ6yhRhiJ
X-Received: by 10.200.43.203 with SMTP id n11mr34542825qtn.241.1495650933829; Wed, 24 May 2017 11:35:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.42.242 with HTTP; Wed, 24 May 2017 11:35:13 -0700 (PDT)
In-Reply-To: <CANtLugM9WH+gOZZherOcUdDEzcGXFuG=7iO8CiDFNbZTaSUh_Q@mail.gmail.com>
References: <CABa8R6vC+NUadZvgD9DKsc+N+SPhTaOd00vjn1EnPHdWDzuDWw@mail.gmail.com> <CANtLugM9WH+gOZZherOcUdDEzcGXFuG=7iO8CiDFNbZTaSUh_Q@mail.gmail.com>
From: Seth Blank <seth@valimail.com>
Date: Wed, 24 May 2017 11:35:13 -0700
Message-ID: <CAOZAAfNZw99=tFFDUDKnf6xapeSXj2GfkcCsHEoU9e2YraJ1Eg@mail.gmail.com>
To: "dmarc@ietf.org" <dmarc@ietf.org>
Cc: Brandon Long <blong@google.com>, Kurt Andersen <kboth@drkurt.com>, Murray superuser Kucherawy <superuser@gmail.com>
Content-Type: multipart/alternative; boundary="001a1135a4469e827a0550495e78"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/NJxgEbqMIRoakMS10L1hcaRPJEo>
Subject: Re: [dmarc-ietf] signing keys for arc-seal/arc-message-signature
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 May 2017 18:35:37 -0000
Does the group have any further thoughts here? I'm happy to suggest language for Gene's suggestion if there are no further comments. On Tue, May 9, 2017 at 4:02 PM, Gene Shuman <gene@valimail.com> wrote: > I definitely can't imagine any sensible case in which the d= tags should > be different. I do think the tag should still be specified in both the AS > & AMS though. While not strictly necessary technically, it does make the > language in the spec & implementation details a bit cleaner. So I would > suggest simply adding a line/section in the chain validation section of the > draft or somewhere else that says cv=fail(or invalid?) if the d= tags > aren't identical. I think this is an entirely reasonable restriction. > > =Gene > > On Thu, May 4, 2017 at 3:44 PM, Brandon Long <blong@google.com> wrote: > >> When thinking about how to extract information from an arc chain, I was >> wondering at the "owner" of a section of the chain. >> >> Theoretically, that's the ADMD. A single hop, however, has three >> separate domain ownerships, the srv_id from the AAR, and the d= field from >> the AS and AMS. >> >> Our current implementation uses google.com for the d= field, and we have >> three different srv_id's for different pools that serve different >> purposes. That said, the srv_id has no "validation" except for by the key >> signature, so d= seems like a stronger "owner". >> >> Except, the AMS and AS can have separate selectors and domains. I'm not >> sure if that's useful or desirable. I'm tempted to only consider a chain >> valid if the domains are the same, and I guess not care if the selectors >> are. >> >> Should we require them to be the same? If we do, should they only be >> specified once? >> >> For changing algorithms, I guess s would be different, along with a, >> though I would think you would need a separate set of headers for the hop >> for each a in transition... >> >> So: >> Should we require d= to be the same? Should we specify it only once? If >> not, why not? >> >> Brandon >> >> _______________________________________________ >> dmarc mailing list >> dmarc@ietf.org >> https://www.ietf.org/mailman/listinfo/dmarc >> >> > > _______________________________________________ > dmarc mailing list > dmarc@ietf.org > https://www.ietf.org/mailman/listinfo/dmarc > > -- [image: logo for sig file.png] Bringing Trust to Email Seth Blank | Head of Product for Open Source and Protocols seth@valimail.com +1-415-894-2724 <415-894-2724>
- [dmarc-ietf] signing keys for arc-seal/arc-messag… Brandon Long
- Re: [dmarc-ietf] signing keys for arc-seal/arc-me… Gene Shuman
- Re: [dmarc-ietf] signing keys for arc-seal/arc-me… Seth Blank
- Re: [dmarc-ietf] signing keys for arc-seal/arc-me… Murray S. Kucherawy