Re: [apps-discuss] Using the .well-known registry for SRV (and other purposes)

Barry Leiba <barryleiba@computer.org> Fri, 18 January 2013 19:11 UTC

Return-Path: <barryleiba.mailing.lists@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 1EF7321F8775 for <apps-discuss@ietfa.amsl.com>; Fri, 18 Jan 2013 11:11:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.105
X-Spam-Level:
X-Spam-Status: No, score=-103.105 tagged_above=-999 required=5 tests=[AWL=-0.128, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iJx92JQ45OfA for <apps-discuss@ietfa.amsl.com>; Fri, 18 Jan 2013 11:11:10 -0800 (PST)
Received: from mail-vc0-f178.google.com (mail-vc0-f178.google.com [209.85.220.178]) by ietfa.amsl.com (Postfix) with ESMTP id A62B121F866D for <apps-discuss@ietf.org>; Fri, 18 Jan 2013 11:11:09 -0800 (PST)
Received: by mail-vc0-f178.google.com with SMTP id m8so3204531vcd.37 for <apps-discuss@ietf.org>; Fri, 18 Jan 2013 11:11:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=xpkhpXEuF+cveQnlmjk0uZmqt/Yv2aRU21NnQiufETo=; b=0anE1Jd+mwryShz7vr+2RhLee23tQSu5UDo31MPmQdyKP5dCK5dbx1fXbhSNR0rK/A kwY1tJ8xU2IAS7cs6rMEEJyEBUD7ZOi+Un3P154sHQx6TzZjquw64+MlkQWUEKShvIVM a3tvx43/OaTe7I0SRN9roI1nXxbWI75j9ndk2IJLXPW6FPGfXArGVBVPyxxG2T39W6h1 b1KGnDyZVp1FDE3pt9swu7b4DCMHY/odfQHRHXSQRzk/fod2KBIugfzfKfGZtMh9KwuH hMz4xfc5wbl4yd7lZxvQWlsKXmQELlFRWjqHU445gdMIL3qy71gb86Cbr5i9UfdMMxUb rrwQ==
MIME-Version: 1.0
X-Received: by 10.52.88.33 with SMTP id bd1mr9409125vdb.70.1358536265727; Fri, 18 Jan 2013 11:11:05 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Fri, 18 Jan 2013 11:11:05 -0800 (PST)
In-Reply-To: <CAMm+LwgyMq5FrA9k7cN8r7W6+etF8QZUndqGupYgnuE3YGXpiw@mail.gmail.com>
References: <CAMm+LwhCPzBMUtVpgsX6D+GA5im2JjTJioY4+2e+u-iML9JOfg@mail.gmail.com> <2644CBB3-5D5E-4247-A79F-430B7358EAA4@frobbit.se> <718EC148-9317-4419-8CDF-AB45CFA4C5D9@frobbit.se> <CAMm+LwjRkCv8qRW6P6vVU930h0OLWcSPSdCKO-A4SR3dutMTDg@mail.gmail.com> <48B79BFC380C7720A8DDE536@cyrus.local> <CAMm+LwgyMq5FrA9k7cN8r7W6+etF8QZUndqGupYgnuE3YGXpiw@mail.gmail.com>
Date: Fri, 18 Jan 2013 14:11:05 -0500
X-Google-Sender-Auth: G3J2diP2qYC4-eVkcUzcqUrtPCg
Message-ID: <CAC4RtVBLeyTZkmL+znwHxEAEWS9EJAqMT4VS3fHkkZfvBfPXkQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: General discussion of application-layer protocols <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Using the .well-known registry for SRV (and other purposes)
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: Fri, 18 Jan 2013 19:11:17 -0000

>> Please see draft-daboo-srv-caldav (in RFC ed queue for 800+ days now).
>
> 800+ days in the queue strongly suggests that is what you should do.
>
> It sounds like the draft is blocked because
>
> 1) People insisted on more flexibility
> 2) The mechanism proposed to achieve the additional flexibility was not
> acceptable
> 3) The issue was not raised with sufficient force in the places that a
> decision might be made
>
> On issues like this where the only thing that really matters is that the
> IETF just pick one way to do something, it is a process failure if we end up
> with delays of 90 days let alone three years.

To be clear: the draft has been stuck in the RFC Editor queue because
of a normative-reference mess in what the IESG has come to think of as
"that cursed Cluster 83."  See
http://www.rfc-editor.org/cluster_info.php?cid=C83

Cyrus's document has a normative reference to
draft-cheshire-dnsext-dns-sd, and that document has a normative
reference to draft-cheshire-dnsext-multicastdns.  Both of those
documents have been stuck for a long time.

I agree that this is a process failure.

Barry