[apps-discuss] The acct: scheme definition -- draft-saintandre-acct-uri

Barry Leiba <barryleiba@computer.org> Sun, 01 July 2012 13:30 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 968AD21F8A7C for <apps-discuss@ietfa.amsl.com>; Sun, 1 Jul 2012 06:30:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.152
X-Spam-Level:
X-Spam-Status: No, score=-102.152 tagged_above=-999 required=5 tests=[AWL=-0.825, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_TOWRITE=1.05, USER_IN_WHITELIST=-100]
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 dvO+6Kzvob0G for <apps-discuss@ietfa.amsl.com>; Sun, 1 Jul 2012 06:30:00 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id B4BB721F8A66 for <apps-discuss@ietf.org>; Sun, 1 Jul 2012 06:29:59 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so7064617lbb.31 for <apps-discuss@ietf.org>; Sun, 01 Jul 2012 06:30:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=Jml+2kEhEHHAB6Opjfol9+FBWtwLosQjsU8ZSRAPoNA=; b=kxKU+imRp8r/jxsdQ+Rv3QnYuPjbyhgqVsAR1us+MHZxCKDGUxq1NBpgjif7uJ+P2q N/55Y3bSOjCBOPxhHfkhunrBH2RJbwH6hgD82TAiyJwGptxMky/7ulvmTm4lMawYjTLS B11SXliimR1kZ2yBgj0i/BZNRo5+dIf81+KtDLBov4Sp37tsuhdOwXbWBjcdNVez/caF kfY/6G9GPlbHKRHF71Eq/F9oDOJJcB4b/lXReRO/8qnoSE4HB8Hjh61OVQSV9UJArDhG DfTTfBDfQhwN2KLI8WWimhdV7zvFoJx1pfObUaRMKAs15B9mPc11J2p9n6oxN1RdUFT6 UkXw==
MIME-Version: 1.0
Received: by 10.152.111.200 with SMTP id ik8mr9175912lab.15.1341149401008; Sun, 01 Jul 2012 06:30:01 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.17.133 with HTTP; Sun, 1 Jul 2012 06:30:00 -0700 (PDT)
Date: Sun, 01 Jul 2012 09:30:00 -0400
X-Google-Sender-Auth: 963QUVYPXXw_prFPZKBuiQuYvYM
Message-ID: <CAC4RtVDrGj+RcKp5q+_W_qFbk7QomWBpZqPn2s+gDcdt-Be+5g@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Graham Klyne <GK@ninebynine.org>, apps-discuss@ietf.org, "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: [apps-discuss] The acct: scheme definition -- draft-saintandre-acct-uri
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, 01 Jul 2012 13:30:00 -0000

>> Graham, I think you're right about the fact that these matters are
>> underspecified. I hereby offer to propose some text, and will do that in
>> the next few days.
>
> I went beyond proposing text and decided to write a standalone I-D:
>
> http://datatracker.ietf.org/doc/draft-saintandre-acct-uri/
>
> Graham, I think that text answers the questions you posed, hopefully in
> an accurate way.

I have a couple/few comments.

Very tiny minor: I might like to see informative references for mailto
[RFC6068] and http (probably [RFC2616], so this isn't waiting on the
httpbis set).

Slightly less tiny: The Security Considerations are correct, as far as
this goes, about the existence of an acct: URI.  Only, this spec
provides no way to expose or test the existence of an acct: URI, so it
does not expose the security issue you're noting.  I'm not sure what
the right change is to this document's Security Considerations for
that, but I really don't see how the creation of this scheme, without
another document's definition of how it can actually be used, poses
any security issue at all.

Significantly less tiny, indeed; issues about the grammar:

   domainpart   =  domainlabel 1*( "." domainlabel)
   domainlabel  =  alphanum / alphanum *( alphanum / "-" ) alphanum

First, to avoid ambiguity, please either

   domainlabel  =  alphanum / (alphanum *( alphanum / "-" ) alphanum)

...or, better,

   domainlabel  =  alphanum  [ *( alphanum / "-" ) alphanum ]

Second, and more important, it concerns me that we have so many
varying definitions of the same entity, a domain name.  Yours is a
variant of what's in RFC 5321 (SMTP) -- a variant, not a reference nor
a copy, though "domainlabel" here specifies exactly the same thing as
"sub-domain" in 5321:

   Domain       = sub-domain *("." sub-domain)
   sub-domain   = Let-dig [Ldh-str]
   Let-dig      = ALPHA / DIGIT
   Ldh-str      = *( ALPHA / DIGIT / "-" ) Let-dig

We have this, from RFC 3986 (URIs):

   host        = IP-literal / IPv4address / reg-name
   reg-name    = *( unreserved / pct-encoded / sub-delims )

We have this, from RFC 6068 (mailto):

   domain       = dot-atom-text / "[" *dtext-no-obs "]"

And those are just in the documents you're citing.  Others surely
exist in other places.  I don't like adding one more to the set of
different definitions.  I suggest instead that you either use this:

   domainpart   =  sub-domain 1*( "." sub-domain)
                ; sub-domain is defined in SMTP [RFC5321]

...if you really want to keep the change that a domain has to have at
least two parts, or this:

   domainpart   =  Domain
                ; Domain is defined in SMTP [RFC5321]

...if you're willing to accept that a domain can have just one part.

Barry