Return-Path: <sperreault@jive.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 5C5601A87BB
 for <vcarddav@ietfa.amsl.com>; Mon,  2 Mar 2015 06:41:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001,
 RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 CJPVbkRIrm_e for <vcarddav@ietfa.amsl.com>;
 Mon,  2 Mar 2015 06:41:18 -0800 (PST)
Received: from mail-la0-f43.google.com (mail-la0-f43.google.com
 [209.85.215.43])
 (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 C82D91A87A7
 for <vcarddav@ietf.org>; Mon,  2 Mar 2015 06:41:14 -0800 (PST)
Received: by lams18 with SMTP id s18so30662040lam.11
 for <vcarddav@ietf.org>; Mon, 02 Mar 2015 06:41:13 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:date
 :message-id:subject:from:to:cc:content-type;
 bh=UkoeyLQVSjZdbegNeqKC6LOtyY29qTu4eR/RBK/fvJI=;
 b=GZDo71Ki/MxA0wH/8gL8HAj0nXAq8aVNMKCch1yZaltIyMAY2n7NPmfcUEwblrMPR3
 2FgMDPLEfDBMiOkKWdMLit58hGtnjEy6N//MPQkRIyM6h8jfp1+4QcxKgTdPEzWJjk5M
 9Yms63z6+qvBnHyP7FRhmvUUXhGd99zVRgU1LKToENwuxrfqm0yE2Qjg1RP4JyPWBcj/
 V6ARfX5l5JqOp53Q4w6uJSXf7hAm3T1NCabAROqHT3WhxoCtj/IsVXrHIriZj4nBGoIY
 TC5mBmM/F+rSS71N6shPdcVrjxMWgEySCyVsknBH5w3FfrrN9qPmTYx/9oPXdk5Wmmqp
 Q4BQ==
X-Gm-Message-State: ALoCoQlO0e+kx1Xai40HUU+Fc1sXz03QbeU7YD49jN/KrlTQdgkRBCfQ+teO2PJvnKiXTMOPJgwI
MIME-Version: 1.0
X-Received: by 10.152.207.72 with SMTP id lu8mr19705815lac.90.1425307273216;
 Mon, 02 Mar 2015 06:41:13 -0800 (PST)
Received: by 10.25.205.144 with HTTP; Mon, 2 Mar 2015 06:41:13 -0800 (PST)
In-Reply-To: <CALaySJL0+x5uA2Z9CnW3FjysZntCgK_24eCVHUThme7WJkjzYA@mail.gmail.com>
References: <20150127140643.86577180489@rfc-editor.org>
 <CALaySJL0+x5uA2Z9CnW3FjysZntCgK_24eCVHUThme7WJkjzYA@mail.gmail.com>
Date: Mon, 2 Mar 2015 09:41:13 -0500
Message-ID: <CANO7kWDQL79YjZSjHaKtovvx=tZmYAE6TnOY1RcbH3CyhScO2w@mail.gmail.com>
From: Simon Perreault <sperreault@jive.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=001a11346650b75d3205104f35eb
Archived-At: <http://mailarchive.ietf.org/arch/msg/vcarddav/4bS3iUd1EC2rDrDdJoc59JOy2to>
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: Mon, 02 Mar 2015 14:41:20 -0000

--001a11346650b75d3205104f35eb
Content-Type: text/plain; charset=UTF-8

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.

I am thoroughly confused about errata statuses, so I won't make a
recommandation. ;)

Simon

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
> >
>

--001a11346650b75d3205104f35eb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Although the original text would not cause interoperabilit=
y issues, the corrected text is more accurate and better represents the WG&=
#39;s consensus at the time the RFC was published.<div><br></div><div>I am =
thoroughly confused about errata statuses, so I won&#39;t make a recommanda=
tion. ;)</div><div><br></div><div>Simon</div></div><div class=3D"gmail_extr=
a"><br><div class=3D"gmail_quote">On Sun, Mar 1, 2015 at 6:28 AM, Barry Lei=
ba <span dir=3D"ltr">&lt;<a href=3D"mailto:barryleiba@computer.org" target=
=3D"_blank">barryleiba@computer.org</a>&gt;</span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">Simon, can you please comment on this errata report?<br>
<br>
Thanks,<br>
Barry<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Tue, Jan 27, 2015 at 3:06 PM, RFC Errata System<br>
&lt;<a href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org<=
/a>&gt; wrote:<br>
&gt; The following errata report has been submitted for RFC6350,<br>
&gt; &quot;vCard Format Specification&quot;.<br>
&gt;<br>
&gt; --------------------------------------<br>
&gt; You may review the report below and at:<br>
&gt; <a href=3D"http://www.rfc-editor.org/errata_search.php?rfc=3D6350&amp;=
eid=3D4245" target=3D"_blank">http://www.rfc-editor.org/errata_search.php?r=
fc=3D6350&amp;eid=3D4245</a><br>
&gt;<br>
&gt; --------------------------------------<br>
&gt; Type: Technical<br>
&gt; Reported by: Ivan Enderlin &lt;<a href=3D"mailto:ivan.enderlin@fruux.c=
om">ivan.enderlin@fruux.com</a>&gt;<br>
&gt;<br>
&gt; Section: 6.7.7<br>
&gt;<br>
&gt; Original Text<br>
&gt; -------------<br>
&gt;=C2=A0 =C2=A0 Value type:=C2=A0 A semicolon-separated pair of values.=
=C2=A0 The first field<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0is a small integer corresponding to the seco=
nd field of a PID<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0parameter instance.=C2=A0 The second field i=
s a URI.=C2=A0 The &quot;uuid&quot; URN<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0namespace defined in [RFC4122] is particular=
ly well suited to this<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0task, but other URI schemes MAY be used.<br>
&gt;<br>
&gt; Corrected Text<br>
&gt; --------------<br>
&gt;=C2=A0 =C2=A0 Value type:=C2=A0 A single structured text value consisti=
ng of components<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0separated by the SEMICOLON character (U+003B=
). The first<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0component is a small integer corresponding t=
o the second<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0component of a PID parameter instance.=C2=A0=
 The second component is a<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0URI. The &quot;uuid&quot; URN namespace defi=
ned in [RFC4122] is particularly<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0well suited to this task, but other URI sche=
mes MAY be used.<br>
&gt;<br>
&gt;<br>
&gt; Notes<br>
&gt; -----<br>
&gt; A &quot;semicolon-separated pair of values&quot; is a structured text =
value. Moreover, the RFC6351 considers the CLIENTPIDMAP property with a str=
uctured text value (see the Relax NG Schema definition of property-clientpi=
dmap).<br>
&gt;<br>
&gt; Instructions:<br>
&gt; -------------<br>
&gt; This erratum is currently posted as &quot;Reported&quot;. If necessary=
, please<br>
&gt; use &quot;Reply All&quot; to discuss whether it should be verified or<=
br>
&gt; rejected. When a decision is reached, the verifying party (IESG)<br>
&gt; can log in to change the status and edit the report, if necessary.<br>
&gt;<br>
&gt; --------------------------------------<br>
&gt; RFC6350 (draft-ietf-vcarddav-vcardrev-22)<br>
&gt; --------------------------------------<br>
&gt; Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: vCard Fo=
rmat Specification<br>
&gt; Publication Date=C2=A0 =C2=A0 : August 2011<br>
&gt; Author(s)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: S. Perreault<br>
&gt; Category=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : PROPOSED STANDARD<=
br>
&gt; Source=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : vCard and Car=
dDAV<br>
&gt; Area=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Applicat=
ions<br>
&gt; Stream=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : IETF<br>
&gt; Verifying Party=C2=A0 =C2=A0 =C2=A0: IESG<br>
&gt;<br>
</div></div></blockquote></div><br></div>

--001a11346650b75d3205104f35eb--

