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

Barry Leiba <barryleiba@computer.org> Tue, 03 March 2015 00:21 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: vcarddav@ietfa.amsl.com
Delivered-To: vcarddav@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CA2F1A8AE9 for <vcarddav@ietfa.amsl.com>; Mon, 2 Mar 2015 16:21:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zGynH9f-J2_D for <vcarddav@ietfa.amsl.com>; Mon, 2 Mar 2015 16:21:16 -0800 (PST)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 539F91A8AE1 for <vcarddav@ietf.org>; Mon, 2 Mar 2015 16:21:16 -0800 (PST)
Received: by lams18 with SMTP id s18so34039287lam.13 for <vcarddav@ietf.org>; Mon, 02 Mar 2015 16:21:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=QZeLgme3W8Nz5MhmMgl7kFWTkLEVXwJNdexJVzYV6fs=; b=XW4HeRw/8JRM1AwzKiawhY9DKfBpo8I8G5jt/pH1biN5AlHWGg4qMwEwxtO5bQYr6A +H0gotrH+Akm99tdCbG9aYqc/yMzB5E8dFc9sIMOkecz7g5ZcPboejiQvgRiBQFVvglG +4OUrdUY2Ye+iCZRrrmLAgvya7nzjrLOVEpG53AF/OQtoOwMJ9T56mP5tlhTVRJ2Sj63 UMHBFh1patGAdeNeUZGA8ggrZ8pRDAFQg0w6WU5IJNXSrfFGCHO/B+nsBXVJjyywaKtw cUGOvkloGxLcs+T74zFb65OUgJyh2AAkzRENQv2i3ZHYYow03Mu4DLapiFr+6NlFnpfW cTMQ==
MIME-Version: 1.0
X-Received: by 10.112.148.38 with SMTP id tp6mr26525008lbb.82.1425342074804; Mon, 02 Mar 2015 16:21:14 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.152.127.165 with HTTP; Mon, 2 Mar 2015 16:21:14 -0800 (PST)
In-Reply-To: <CANO7kWDQL79YjZSjHaKtovvx=tZmYAE6TnOY1RcbH3CyhScO2w@mail.gmail.com>
References: <20150127140643.86577180489@rfc-editor.org> <CALaySJL0+x5uA2Z9CnW3FjysZntCgK_24eCVHUThme7WJkjzYA@mail.gmail.com> <CANO7kWDQL79YjZSjHaKtovvx=tZmYAE6TnOY1RcbH3CyhScO2w@mail.gmail.com>
Date: Tue, 03 Mar 2015 01:21:14 +0100
X-Google-Sender-Auth: ebGJajbu9o-7ocuQlWLIyKZ9Alk
Message-ID: <CALaySJJ5weDafSrsZmROxgTB+FNWbJiDpRKiiCi1KbFGndfsjQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Simon Perreault <sperreault@jive.com>
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: <http://mailarchive.ietf.org/arch/msg/vcarddav/BrrycQv9TXSPvbQEhDf3Y-F6G08>
Cc: ivan.enderlin@fruux.com, CardDAV <vcarddav@ietf.org>
Subject: Re: [VCARDDAV] [Technical Errata Reported] RFC6350 (4245)
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 03 Mar 2015 00:21:18 -0000

> Although the original text would not cause interoperability issues, the
> corrected text is more accurate and better represents the WG's consensus at
> the time the RFC was published.

That (particularly the "would not cause interoperability issues" part)
says "held for document update" to me.

> I am thoroughly confused about errata statuses, so I won't make a
> recommandation. ;)

:-)
See <http://www.ietf.org/iesg/statement/errata-processing.html>, and
see if you're even a little less confused.

Thanks for the quick response.

Barry

> On Sun, Mar 1, 2015 at 6:28 AM, Barry Leiba <barryleiba@computer.org> wrote:
>>
>> Simon, can you please comment on this errata report?
>>
>> Thanks,
>> Barry
>>
>> On Tue, Jan 27, 2015 at 3:06 PM, RFC Errata System
>> <rfc-editor@rfc-editor.org> wrote:
>> > The following errata report has been submitted for RFC6350,
>> > "vCard Format Specification".
>> >
>> > --------------------------------------
>> > You may review the report below and at:
>> > http://www.rfc-editor.org/errata_search.php?rfc=6350&eid=4245
>> >
>> > --------------------------------------
>> > Type: Technical
>> > Reported by: Ivan Enderlin <ivan.enderlin@fruux.com>
>> >
>> > Section: 6.7.7
>> >
>> > Original Text
>> > -------------
>> >    Value type:  A semicolon-separated pair of values.  The first field
>> >       is a small integer corresponding to the second field of a PID
>> >       parameter instance.  The second field is a URI.  The "uuid" URN
>> >       namespace defined in [RFC4122] is particularly well suited to this
>> >       task, but other URI schemes MAY be used.
>> >
>> > Corrected Text
>> > --------------
>> >    Value type:  A single structured text value consisting of components
>> >       separated by the SEMICOLON character (U+003B). The first
>> >       component is a small integer corresponding to the second
>> >       component of a PID parameter instance.  The second component is a
>> >       URI. The "uuid" URN namespace defined in [RFC4122] is particularly
>> >       well suited to this task, but other URI schemes MAY be used.
>> >
>> >
>> > Notes
>> > -----
>> > A "semicolon-separated pair of values" is a structured text value.
>> > Moreover, the RFC6351 considers the CLIENTPIDMAP property with a structured
>> > text value (see the Relax NG Schema definition of property-clientpidmap).
>> >
>> > Instructions:
>> > -------------
>> > This erratum is currently posted as "Reported". If necessary, please
>> > use "Reply All" to discuss whether it should be verified or
>> > rejected. When a decision is reached, the verifying party (IESG)
>> > can log in to change the status and edit the report, if necessary.
>> >
>> > --------------------------------------
>> > RFC6350 (draft-ietf-vcarddav-vcardrev-22)
>> > --------------------------------------
>> > Title               : vCard Format Specification
>> > Publication Date    : August 2011
>> > Author(s)           : S. Perreault
>> > Category            : PROPOSED STANDARD
>> > Source              : vCard and CardDAV
>> > Area                : Applications
>> > Stream              : IETF
>> > Verifying Party     : IESG
>> >
>
>