IETF Logo Mail Archive

[dbound] DBOUND - updated use cases?

Ian Williams <iwillamz@amazon.com> Wed, 28 September 2022 19:23 UTC

Return-Path: <prvs=26302f2b8=iwillamz@amazon.com>
X-Original-To: dbound@ietfa.amsl.com
Delivered-To: dbound@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4F07C15AE3F for <dbound@ietfa.amsl.com>; Wed, 28 Sep 2022 12:23:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.181
X-Spam-Level:
X-Spam-Status: No, score=-10.181 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.571, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazon.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nM27qyhZZ8Fx for <dbound@ietfa.amsl.com>; Wed, 28 Sep 2022 12:23:29 -0700 (PDT)
Received: from smtp-fw-33001.amazon.com (smtp-fw-33001.amazon.com [207.171.190.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6608C15AE3C for <dbound@ietf.org>; Wed, 28 Sep 2022 12:23:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1664393010; x=1695929010; h=message-id:date:mime-version:from:subject:to: content-transfer-encoding; bh=eWz9wmr2TiU//VofFKKm9SnUL+rmradDSmNoBO+Yxeg=; b=IPnExeq38QFRzhlopIjzkdHAXcSSqY2/9Vppx42Ibx1CLsGI8yXcOTWM ZAbqAH4HOoX91q9Ry/MqlVG+dFnZuwuBum4hRhiP/DYZLjTzWYuPGQY96 xA9tu5EeZ1Ijs9lXSrm9ARaYGvkNAv+8L3SeaBknmo2SfQ/fx5CxeU/6m g=;
X-IronPort-AV: E=Sophos;i="5.93,352,1654560000"; d="scan'208";a="229318389"
Received: from iad12-co-svc-p1-lb1-vlan3.amazon.com (HELO email-inbound-relay-iad-1d-10222bbc.us-east-1.amazon.com) ([10.43.8.6]) by smtp-border-fw-33001.sea14.amazon.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Sep 2022 19:23:29 +0000
Received: from EX13MTAUEA001.ant.amazon.com (iad12-ws-svc-p26-lb9-vlan3.iad.amazon.com [10.40.163.38]) by email-inbound-relay-iad-1d-10222bbc.us-east-1.amazon.com (Postfix) with ESMTPS id 2CE251A001D for <dbound@ietf.org>; Wed, 28 Sep 2022 19:23:27 +0000 (UTC)
Received: from EX19D036UEA001.ant.amazon.com (10.252.134.145) by EX13MTAUEA001.ant.amazon.com (10.43.61.243) with Microsoft SMTP Server (TLS) id 15.0.1497.38; Wed, 28 Sep 2022 19:23:25 +0000
Received: from EX13MTAUEA001.ant.amazon.com (10.43.61.82) by EX19D036UEA001.ant.amazon.com (10.252.134.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.2.1118.12; Wed, 28 Sep 2022 19:23:24 +0000
Received: from [192.168.2.32] (10.106.179.45) by mail-relay.amazon.com (10.43.61.243) with Microsoft SMTP Server (TLS) id 15.0.1497.38 via Frontend Transport; Wed, 28 Sep 2022 19:23:24 +0000
Message-ID: <bd3a32cb-dd41-b195-e46d-419611000ceb@amazon.com>
Date: Wed, 28 Sep 2022 12:23:23 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.0
From: Ian Williams <iwillamz@amazon.com>
To: dbound@ietf.org
Content-Language: en-US
Organization: AWS Security
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dbound/nrWC3sAQ9u8EKsEcZn2nsZ8FQds>
Subject: [dbound] DBOUND - updated use cases?
X-BeenThere: dbound@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DNS tree bounds <dbound.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dbound>, <mailto:dbound-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dbound/>
List-Post: <mailto:dbound@ietf.org>
List-Help: <mailto:dbound-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dbound>, <mailto:dbound-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2022 19:23:30 -0000

Fellow DBOUND/adjacent folk,

During some of the side discussions at 114, it was mentioned that the 
previous
use-cases for DBOUND might not align with the more-recent needs. This was
theorized to be part of the reason the WG concluded without consensus - 
there
just wasn't a way to handle all use-cases.

Some folks recommended starting up a use-case discussion on the mailing 
list,
to see if today's potential use-cases of DBOUND align with the previous 
draft
problem statements.

Therefore, opening it up to the list to start from the beginning. What would
some of the use-cases of DBOUND be? We can probably agree that there are 
many
use-cases, but listing them all out might be an apropos first-step towards
creation of a solid problem statement.

Intent of this thread is to discuss these use-cases against the previous
charter, and potentially to organize a BoF at 115 among parties 
interested in
discussing a problem statement.

(in an effort to foster active participation here, it might be best to 
get the
use-cases from the browser and/or DMARC folks summarized by others on 
the list)

Regards,

Ian Williams
Sr. Security Engineer
AWS Security

v2.23.0 | Report a Bug | By Email