IETF Logo Mail Archive

Re: [rfc-i] Proposed Program Description for RFC Editor evolution program

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 15 January 2020 18:40 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A2B71208D4 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 15 Jan 2020 10:40:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.5
X-Spam-Level:
X-Spam-Status: No, score=-4.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (body has been altered)" header.d=gmail.com
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 j5ThFSKA0IPH for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 15 Jan 2020 10:40:50 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E72D2120906 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Wed, 15 Jan 2020 10:40:50 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5C1E0F4071B; Wed, 15 Jan 2020 10:40:47 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 867D6F4071B for <rfc-interest@rfc-editor.org>; Wed, 15 Jan 2020 10:40:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id unAm_Ir-x0Wl for <rfc-interest@rfc-editor.org>; Wed, 15 Jan 2020 10:40:41 -0800 (PST)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) by rfc-editor.org (Postfix) with ESMTPS id B8FADF40714 for <rfc-interest@rfc-editor.org>; Wed, 15 Jan 2020 10:40:41 -0800 (PST)
Received: by mail-pg1-x533.google.com with SMTP id q127so8601887pga.4 for <rfc-interest@rfc-editor.org>; Wed, 15 Jan 2020 10:40:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=gA6nSOcjO9WGMwQTQxjlpfkjqUd0ay67L325mKG/IQ8=; b=m5QqKlbspsBWxQ/QAgQxOAOgvUPpGuBEwm3XmjwJrkmiN/zgvl24paqRCFLFDh39HK JDzfPJKHGJKDfwAiKilZT3HH+bUy3rB4s4eTwAxGM2q66EwrEqaEbOZrbs2DuWKGhwBk 7UEwTs05N+31TEqLRT4F7FA3pNhswtVoQeOxxyRcxPgO9ot8zSOa0y99zrBoRrWs2Nhj 29Z3ow/U0UE/f3NSQID19wbclZYdDrv44fSfXYkukmkQDh98BI8sqWlVEpQb/CxNEMG8 oqAYPTQSB5FUWPkHas4bhEaiPDtSzcB5AzT0EVZLMbXNz8+pRffKaJQUwGSdTOCYQ2nS PMlw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=gA6nSOcjO9WGMwQTQxjlpfkjqUd0ay67L325mKG/IQ8=; b=OmGqov4NS60uab59UU4UWdtfV0S5TLHHCDPV2ZZrDm3wh7Wv7Fekt17IRXpYr4k3a9 C08EO7El0pI89Rz8g4HUvaHtNrkeK2abGIXvk/kh/SHuevNKTiTSqP3CoT9E3Lp9P4bc ehDqRJhid0ELYh80/i1md5fG9dbIT3/G5/1InZLKPBfs+vIRFMn5hqZnOs3PkwtDMeZq PmQgcfP90yuvReNjmYgvgCvpF4opVzg+bi9SmqC1otJbMmQOmW7135JzxWaBtmwtssir KLhWmHG1ogZ1PJJZx7BsrI2H1xszwLIqSSxu+AzzCCsb0Al7pPKjSi8y83VueD4PMF67 oGBw==
X-Gm-Message-State: APjAAAXQUeXZn5ND0n3gxAhsN94xyS3O8crb38i6+U33ButImLG8Zh0d QVisGB8SkcwnP2/wOKcjM6Y=
X-Google-Smtp-Source: APXvYqyQnj9eIM7pUi2oycZnFFQME6BJ+Dx991c0gCWhxwpTSwiI/qwFVg9k9CpcaXD7DmvllEcuZA==
X-Received: by 2002:a62:158c:: with SMTP id 134mr32306170pfv.81.1579113643907; Wed, 15 Jan 2020 10:40:43 -0800 (PST)
Received: from [172.17.0.82] ([111.69.8.186]) by smtp.gmail.com with ESMTPSA id m3sm22367936pfh.116.2020.01.15.10.40.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Jan 2020 10:40:43 -0800 (PST)
To: Phillip Hallam-Baker <phill@hallambaker.com>, Ted Hardie <ted.ietf@gmail.com>
References: <CA+9kkMBFgdFdT3CLYWDvK5QN7xQOnMo+SQLG0_yueqhthcd+bg@mail.gmail.com> <CAMm+LwjprpUb-_hM5Q7+a0bjWSVD6bTm3Dyf3MKs392gzws6MQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <a0353404-6d96-0491-8049-935f0c88da62@gmail.com>
Date: Thu, 16 Jan 2020 07:40:39 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAMm+LwjprpUb-_hM5Q7+a0bjWSVD6bTm3Dyf3MKs392gzws6MQ@mail.gmail.com>
Content-Language: en-US
Subject: Re: [rfc-i] Proposed Program Description for RFC Editor evolution program
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: RFC Interest <rfc-interest@rfc-editor.org>, Internet Architecture Board <iab@iab.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

> Yes, I know a clique decided that they only wanted black and white images.

What clique was that again?

Oh yes, I remember, it was the people who bothered to express an opinion on the open mailing list where the format was debated at great length, including the reasons for excluding greyscale and colour.

I have some code for a heuristic to convert greyscale and colour to pure b&w if you want it, although I was hoping it would be added as an option to the normal tool. That said, SVG is a horrible mess when you dig into it and the tools that create it are inconsistent. This topic does need more work but b&w seems to be the least of our problems.

Regards
   Brian

On 15-Jan-20 07:20, Phillip Hallam-Baker wrote:
> I have some concerns about the way the process is working with respect to the new format.
> 
> We can in theory include SVG images. Only we can't because the spec as it is written is for a subset of SVG that no existing tool supports. So we do not have SVG images, we have a private spec.
> 
> Yes, I know a clique decided that they only wanted black and white images. But I think that decision should have been made by the IETF as a whole and in full knowledge of the consequence that it would only be possible to include images that were created by hand or with IETF-specific tools.
> 
> I want a process in which it is clear that the IETF is the community that defines policy of that type.
> 
> 
> And of course then we run into all the problems caused by all the silliness that comes from the RFC series not belonging to the IETF only it does only it doesn't because we continue to pretend that we are multiple organizations and one organization.
> 
> 
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
> 
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email