[apps-discuss] Comments on draft-levine-orgboundary

"Murray S. Kucherawy" <superuser@gmail.com> Sun, 21 July 2013 08:37 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C092821E804E for <apps-discuss@ietfa.amsl.com>; Sun, 21 Jul 2013 01:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level:
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nMhCHUEcbqZk for <apps-discuss@ietfa.amsl.com>; Sun, 21 Jul 2013 01:37:35 -0700 (PDT)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 638DB21F9E47 for <apps-discuss@ietf.org>; Sun, 21 Jul 2013 01:37:35 -0700 (PDT)
Received: by mail-we0-f177.google.com with SMTP id m19so5044639wev.36 for <apps-discuss@ietf.org>; Sun, 21 Jul 2013 01:37:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=bAyOH3s5/9Cpw5RfM/rlR3nZzhUQsQ+M/+ICK6HRCFU=; b=SYx2KfNFyHnldn2v+sqS8UOFJ2x0hC2JNEmn+ARCy6eq8EU14hnw9/OW3zpdMR1CdQ py/Z9QLfUMDkgfuINjtNGXD+d7p8aQfw5AHQj4BdxlRmMgnnz8pIj4cz10HqetCEYl+f Ve0qXRxsN2mCmMYGXaV2fcSXU3cOhHJdjm78ov1jv/6XIG6yOEyUu+wwgUHULcQFAfit qF7d4O2qQN7OzxERN4IGOxe3QuRagY+0tB3LoH6TK6k0Lr/8aeobpPo7hlsZiVwnasSn PR12X1bZ+LNF6apr2MEj5aY88uFNmH+lmpx3kh2UHQYDQ9VRk6axDemJjXMvYY7A5Olz eg/w==
MIME-Version: 1.0
X-Received: by 10.180.102.37 with SMTP id fl5mr26520142wib.52.1374395854278; Sun, 21 Jul 2013 01:37:34 -0700 (PDT)
Received: by 10.180.90.16 with HTTP; Sun, 21 Jul 2013 01:37:34 -0700 (PDT)
Date: Sun, 21 Jul 2013 01:37:34 -0700
Message-ID: <CAL0qLwZD6uV-XZkwQBX2MEmDmnBy2opt9pgGFrAgUxnr+LJk7g@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: draft-levine-orgboundary@tools.ietf.org, IETF Apps Discuss <apps-discuss@ietf.org>
Content-Type: multipart/alternative; boundary="f46d044517f7acd70804e20178a1"
Subject: [apps-discuss] Comments on draft-levine-orgboundary
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Jul 2013 08:37:36 -0000

Hi there,

Similar to draft-sullivan-domain-policy-authority, I'm interested in this
stuff from the email authentication angle.

I've offered off-list to develop this with John in terms of the text.  Here
I'm just talking about the mechanism itself.

The mechanism provided here is fairly straightforward, but there's one
limitation in particular.  You use this as an example:

A query to _ob.ca might yield a response that indicates boundaries at the
federal, provincial, and municipal levels, such as "ob=1 ca on.ca
toronto.on.ca".  The issue I can see is that in fact there are domains in
.ca, domains in .on.ca (and the other twelve), and domains in the
municipal-level domains which as I recall number in the thousands in
Canada.  It would be impossible to enumerate them all in a reply to _ob.ca,
certainly without switching to TCP or having some kind of indirection.
Might it be better to have a reply syntax that can indicate "stuff can be
registered here and up to n levels below"?

For example, maybe this would work:

ob=1 ca on.ca+1 bc.ca+1 ...

This allows domains in ca, on.ca, bc.ca, and the rest of the province
domains, and one level down from each of those (and would fit in a UDP
reply), while maybe this:

ob=1 ca on.ca/1 bc.ca/1 ...

...allows domains in ca, and then one below on.ca and bc.ca and the
province domains but not directly in them.

It also doesn't handle all of the use cases as Andrew's document does.  The
one in particular that's of interest is the "two related domains" use case
that's popped up lately in the DNS groups.  It would be great to tackle
that as well, but that may be wishful thinking here.

-MSK