Re: [Errata-design] Fwd: WebEx meeting scheduled: Errata System Design Team

"Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org> Mon, 02 February 2015 19:01 UTC

Message-ID: <54CFC9AC.2090707@rfc-editor.org>
Date: Mon, 02 Feb 2015 11:02:04 -0800
From: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: errata-design@rfc-editor.org
References: <672179354.14682.1422380737490.JavaMail.nobody@jva2tc116.webex.com> <54C7CEFE.1050508@rfc-editor.org>
In-Reply-To: <54C7CEFE.1050508@rfc-editor.org>
Content-Type: multipart/alternative; boundary="------------050509070608020103070405"
Subject: Re: [Errata-design] Fwd: WebEx meeting scheduled: Errata System Design Team
Precedence: list

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Reminder: talk to you in an hour!

Agenda:

Any more discussion that folks want to close out from the last call?

Next topic: existing proposals
    a. Replace the concept of errata with a system that would
        allow anyone to comment on an RFC, with the RFC Editor
        or stream controllers to mark some concepts as important.
        The 'errata system' would be a system of comments, not
        a system of discretely managed items. Comments that
        stream controllers (or their delegates) mark as important
        could then be shown through an “errata” link. Alternatively,
        there could be a general 'mod up/down' [1] system that
        anyone with a datatracker account could use to indicate the
        importance of the entry. The RFC Editor could handle
        unambiguous typos.
   b. [A]n IETF-operated web site that is preferable to the
       competition (e.g., tools) and that presents errata of this sort as
       highlighted in a different color on the presented RFC, rather than
       as comments that are in a separate visual stream from the
       presented RFC. I would like errata to be done similarly, if they
       are verified by someone who can check whether a new
       consensus is required to affirm the erratum.


> -------- Forwarded Message --------
>
> *Errata System Design Team* Monday, February 2, 2015 12:00 pm  |
> Pacific Standard Time (San Francisco, GMT-08:00)  |  1 hr
>
> *Join WebEx meeting*
> <https://ietf.webex.com/ietf/j.php?MTID=mf2ad3313ccc51b5d88d3be6be50d2bc6>
>
>
> Meeting number:     641 589 473
> Meeting password:     blahblah
>
> *Join by phone* *1-877-668-4493* Call-in toll free number
> (US/Canada) *1-650-479-3208* Call-in toll number (US/Canada) Access
> code: 641 589 473 Toll-free calling restrictions
> <http://www.webex.com/pdf/tollfree_restrictions.pdf>
>
> Add this meeting
> <https://ietf.webex.com/ietf/j.php?MTID=m778f6f23d61cdc4c9bf92841a7ba4096>
> to your calendar.
>
> Can't join the meeting? Contact support.
> <https://ietf.webex.com/ietf/mc>
>
>
>
> IMPORTANT NOTICE: Please note that this WebEx service allows audio
> and other information sent during the session to be recorded, which
> may be discoverable in a legal matter. You should inform all meeting
> attendees prior to recording if you intend to record the meeting.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJUz8msAAoJEER/xjINbZoGBWAH/1e6KdyEwBI+Qn1jvyoKFvIs
4qXGueoVkBnEmiCc7fghmyqnr8sqXgVCLevfPzobLR2HFqPV9/KUGJY4Rvl2QBHZ
bct8WuNew1JU59fm4e6+piLe0ya3YwZaQOCj/4oDepSvyPdItWtjsHu6WEGkjy5o
5JourUX9ietWpIHGRKucV2mbeJ1Udr2zDXD2NFgBzXbZnpatvFnBIIh/3IyxS9B1
JDE87nGvWo6oPfn8WkZznpxVht5sycihOMJJsxmFVCndAy4MDheeJNqlb+wKXVMd
DImqT7eEEEUnOXOPke49pvJ+7cMDEf3FX8Ac5nUJ+2yP3vkfP6CTQ32JQN3z9IU=
=E4+X
-----END PGP SIGNATURE-----

[Errata-design] Fwd: WebEx meeting scheduled: Err… Heather Flanagan (RFC Series Editor)
Re: [Errata-design] Fwd: WebEx meeting scheduled:… Heather Flanagan (RFC Series Editor)