Re: [VCARDDAV] [Technical Errata Reported] RFC6350 (3100)

"Javier Godoy" <rjgodoy@fich.unl.edu.ar> Wed, 08 February 2012 13:43 UTC

Return-Path: <rjgodoy@fich.unl.edu.ar>
X-Original-To: vcarddav@ietfa.amsl.com
Delivered-To: vcarddav@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 701AF21F8504 for <vcarddav@ietfa.amsl.com>; Wed, 8 Feb 2012 05:43:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.087
X-Spam-Level:
X-Spam-Status: No, score=-1.087 tagged_above=-999 required=5 tests=[AWL=-1.689, BAYES_50=0.001, J_CHICKENPOX_45=0.6, STOX_REPLY_TYPE=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 LC4GOd8UIn-5 for <vcarddav@ietfa.amsl.com>; Wed, 8 Feb 2012 05:43:08 -0800 (PST)
Received: from fich.unl.edu.ar (fich.unl.edu.ar [190.122.240.170]) by ietfa.amsl.com (Postfix) with ESMTP id 7738321F845E for <vcarddav@ietf.org>; Wed, 8 Feb 2012 05:43:07 -0800 (PST)
Received: from localhost ([127.0.0.1]) by fich.unl.edu.ar (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits)); Wed, 8 Feb 2012 10:42:44 -0300
Message-ID: <D46E998BA10B4901AA37693410EBAF9E@Javier2>
From: Javier Godoy <rjgodoy@fich.unl.edu.ar>
To: Cyrus Daboo <cyrus@daboo.name>, Simon Perreault <simon.perreault@viagenie.ca>, vcarddav@ietf.org
References: <20120130182941.6F376B1E002@rfc-editor.org><4F26E44D.6060807@viagenie.ca> <14E42CB21F0E477CA6DA0AC8E1E1A40D@Javier2><4F2C0224.5080701@viagenie.ca> <23AAF311845C458FB4606A66F77369DC@Javier2><4F2FD688.4020602@viagenie.ca> <4F301E46.2060903@PetesGuide.com><4F302205.3090108@viagenie.ca> <1252BF8A8F10701EB5AA31F8@caldav.corp.apple.com>
Date: Wed, 08 Feb 2012 10:43:07 -0300
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
Subject: Re: [VCARDDAV] [Technical Errata Reported] RFC6350 (3100)
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF vcarddav wg mailing list <vcarddav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vcarddav>
List-Post: <mailto:vcarddav@ietf.org>
List-Help: <mailto:vcarddav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2012 13:43:09 -0000

On February 6, 2012 2:21 PM -0500 Cyrus Daboo wrote.

> --On February 6, 2012 1:55:01 PM -0500 Simon Perreault
> <simon.perreault@viagenie.ca> wrote:
>
>> There is no
>> way we can change the ABNF so that the example becomes correct. The
>> example is just wrong. We must fix it with one of these:
>>
>> TYPE=foo,bar
>> TYPE=foo,TYPE=bar

TYPE=foo;TYPE=bar


>> TYPE="foo","bar"

I'm not sure about this one.

On <http://www.ietf.org/mail-archive/web/vcarddav/current/msg02476.html> Simon
said that "all parameters can be implicitly quoted", but the published text of
RFC 6350 suggests that some parameters cannot be quoted, because the ABNF only
allows gratuitous quotes in TZ, ALTID, LABEL, SORT-AS and any-param (which are
defined in terms of param-value):

  param-value = *SAFE-CHAR / DQUOTE *QSAFE-CHAR DQUOTE

  tz-parameter  = "TZ=" (param-value / DQUOTE URI DQUOTE)
  altid-param   = "ALTID=" param-value
  label-param   = "LABEL=" param-value
  sort-as-param = "SORT-AS=" sort-as-value
  any-param  = (iana-token / x-name) "=" param-value *("," param-value)


Thus ALTID="1" would be valid, while TYPE="foo" would not, because type-param
is defined as

  type-param = "TYPE=" type-value *("," type-value)
  type-value = "work" / "home" / type-param-tel
             / type-param-related / iana-token / x-name

If quoted values such as TYPE="foo" were valid, they should be explicitly
allowed (at least as a general comment in section 5, applying to all parameter
types).


> And perhaps we should have an example of 'TYPE="foo,bar"' and explain that
> that represents a single parameter value of "foo,bar" just to re-iterate the
> point.

+1, though "foo,bar" is not a valid type-value.

Perhaps this clarification fits best for the SORT-AS param.

For instance, the value of the SORT-AS parameter in
    N;SORT-AS="Mann,James":de Mann;Henry,James;;
is a single param-value "Mann,James" that applies to the surname, and no
sort-string is specified for the given name.

On the other hand, the value of the SORT-AS parameter in
   N;SORT-AS="Mann","James":de Mann;Henry,James;;
is a list of two param-values: the first one "Mann" applies to the surname,
and the second one "James" applies to the given name.

In this case, both examples are valid according to the ABNF, but have
different meanings.

BTW, the sort results in section 5.9 do not change, because both "Henry" and
"James" sorts between "Christine" and "Osamu".


Best Regards

Javier