Re: [apps-discuss] draft-saintandre-xdash-considered-harmful-01

Joe Hildebrand <joe.hildebrand@webex.com> Mon, 25 October 2010 19:20 UTC

Return-Path: <Joe.Hildebrand@webex.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF5DE3A688A for <apps-discuss@core3.amsl.com>; Mon, 25 Oct 2010 12:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.387
X-Spam-Level:
X-Spam-Status: No, score=-104.387 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vW227yUDO8T4 for <apps-discuss@core3.amsl.com>; Mon, 25 Oct 2010 12:20:43 -0700 (PDT)
Received: from gw2.webex.com (gw2.webex.com [64.68.122.209]) by core3.amsl.com (Postfix) with SMTP id A6D493A69B7 for <apps-discuss@ietf.org>; Mon, 25 Oct 2010 12:18:17 -0700 (PDT)
Received: from SRV-EXSC03.webex.local ([192.168.252.197]) by gw2.webex.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 25 Oct 2010 12:20:02 -0700
Received: from 66.114.169.7 ([66.114.169.7]) by SRV-EXSC03.webex.local ([192.168.252.200]) via Exchange Front-End Server mailus.webex.com ([66.114.175.11]) with Microsoft Exchange Server HTTP-DAV ; Mon, 25 Oct 2010 19:20:02 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Mon, 25 Oct 2010 13:20:01 -0600
From: Joe Hildebrand <joe.hildebrand@webex.com>
To: John C Klensin <john-ietf@jck.com>, Eric Burger <eburger@standardstrack.com>, Discuss Apps IETF <apps-discuss@ietf.org>
Message-ID: <C8EB3481.388FE%joe.hildebrand@webex.com>
Thread-Topic: [apps-discuss] draft-saintandre-xdash-considered-harmful-01
Thread-Index: Act0eZ6LmpJrVoHcmU6NQUGuPUg0ug==
In-Reply-To: <A583522BE810D0F2978AC4AC@PST.JCK.COM>
IM-ID: xmpp:jhildebr@cisco.com
Presence-ID: xmpp:jhildebr@cisco.com
Jabber-ID: jhildebr@cisco.com
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 25 Oct 2010 19:20:02.0538 (UTC) FILETIME=[9F7634A0:01CB7479]
Subject: Re: [apps-discuss] draft-saintandre-xdash-considered-harmful-01
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 25 Oct 2010 19:20:44 -0000

On 10/25/10 11:08 AM, "John C Klensin" <john-ietf@jck.com> wrote:

> Ignoring the obvious small issues with syntax, using
> vnd.URI.field-name or vnd.FQDN.field-name would have the
> advantage over vnd.Registered-Vendor-Name.field-name of not
> requiring an IANA registry... and the disadvantage of being
> somewhat less stable.  Of course, we could punt that tradeoff by
> having both Registered-Vendor-Name and something URI or
> DNS-based with different first-facet prefixes and letting the
> vendor choose between long-term stability and the convenience of
> avoiding dealing with IANA at all.

For syntax, base64 generates sequences that are valid according to the
field-name production of 5322.  Clark notation is a nice fit for the
URI/field tuple.  As such, this should work:

"B64-" + base64({uri}field-name) + ": " + value

The person/group that owns the URI owns the change control over that
uri/field tuple, and is responsible for forward- and backward-compatibility,
or changing the uri or field for incompatible changes.

The B64- prefix is intended to ensure that we don't overlap an existing
header by mistake, and to give a hint to third parties that if they
base64-decode the field name, they should get something interesting.

-- 
Joe Hildebrand