Re: Accurate history [Re: "professional" in an IETF context]

Phillip Hallam-Baker <phill@hallambaker.com> Fri, 05 November 2021 02:19 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC73E3A073D for <ietf@ietfa.amsl.com>; Thu, 4 Nov 2021 19:19:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=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 KaQrKeKiOdnT for <ietf@ietfa.amsl.com>; Thu, 4 Nov 2021 19:19:20 -0700 (PDT)
Received: from mail-yb1-f170.google.com (mail-yb1-f170.google.com [209.85.219.170]) (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 161AE3A0691 for <ietf@ietf.org>; Thu, 4 Nov 2021 19:19:20 -0700 (PDT)
Received: by mail-yb1-f170.google.com with SMTP id v7so19292026ybq.0 for <ietf@ietf.org>; Thu, 04 Nov 2021 19:19:20 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hT+GcQtANHsycg4muFrRGUwRRXCmICeT5A0xs4gqeFM=; b=FR3a+ClJWXhklR80+WpIdmdoRRv3Hh2lT8aOfrDsoWZKbDhGHJh1lAD7nvLchPtHz2 VdeiBcOADSWH8B2jO9T9uydWWmoZCUtSXpgrqmprWvHDQButRhsulCtnFljwfLnATxHO nDgYzv7/YqHJunXbZsbZHNQvwT2BQePptLY9jAqkuYSsYcwvWrtox2xcKPDOyu5p3IxQ T/IMxItNvnXsH01Sef4bJZf1MAwfHUDMKsyGN9+XvYpA4kzYKJWJfy1KW48p9EOu5Tu5 cv+zq066rlwTElmgvO8vUxWKEEl/arDUiALvSx8ecmZCmG6V75ygWZwLw5935SkHPyFf 6p6Q==
X-Gm-Message-State: AOAM532bxcwE5cNMB2WOgN7Rkj4o6e0V1SyMAjyxPRxEmL7U5vYygcMM YX2xU1nt5BAUD9whFb8y/msc6c5wqQk9p2hXVPp1GB2zDX4=
X-Google-Smtp-Source: ABdhPJz/Ssq7fdhCwVDu7pNpo4rBe0TtZ2uR7oguCRaRUDm4WMryVYc+6NueFFsSHZOAolLujaPQWOQlB3CP0qem61M=
X-Received: by 2002:a05:6902:124f:: with SMTP id t15mr65525708ybu.47.1636078759112; Thu, 04 Nov 2021 19:19:19 -0700 (PDT)
MIME-Version: 1.0
References: <8F4B97EA-665F-4A59-B99D-791B4AB9F2F7@yahoo.co.uk> <746C1453-FFB0-46E5-ABF2-8630DC23B959@network-heretics.com> <c3e9fe1b-8e48-a364-9e25-4084dac70889@meetinghouse.net> <3a6bf8ad-5492-0942-a451-6317e8a93705@network-heretics.com> <3e685576-a230-a7c4-f371-d66a55aa820d@necom830.hpcl.titech.ac.jp> <7a087707-499f-e3bf-8701-1a58930a8a22@meetinghouse.net> <4ec32d7a-a17b-635b-91bc-4152313d6800@necom830.hpcl.titech.ac.jp> <885e62bf-7d6a-4501-a48a-e7c2cbf20382@joelhalpern.com> <e59adb61-a55c-7f5f-a60a-40bf186c139d@necom830.hpcl.titech.ac.jp> <CAC8QAceMSrfkqGTYcMNr3JargO3gxJqTaEyf02LGHd-KVeUDHw@mail.gmail.com> <6286da3e-2beb-9556-089a-2e1951573b1e@gmail.com> <59c80b60-438f-b10f-ad61-ba839f6e4f95@necom830.hpcl.titech.ac.jp> <e834916e85ea47ef94fce07c23928d2b@huawei.com> <37b299c8-e821-07e5-6240-68fb9d1ca137@gmail.com> <23b450fb11eb4a51bb4ee837b5c52657@huawei.com> <a805b50d-3ccd-dd2a-4931-6c6dc9a8ede3@necom830.hpcl.titech.ac.jp> <CABFReBoMue+WU3YEzs4Qz4RCB=3=Q2p_tCdy=wiY0Ld9XcHCfw@mail.gmail.com>
In-Reply-To: <CABFReBoMue+WU3YEzs4Qz4RCB=3=Q2p_tCdy=wiY0Ld9XcHCfw@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 04 Nov 2021 22:19:08 -0400
Message-ID: <CAMm+LwhdxAG3QPz1nEz6m5xgk9B5WH_+pb8k06mLSjJSyFcfVw@mail.gmail.com>
Subject: Re: Accurate history [Re: "professional" in an IETF context]
To: gjshep@gmail.com
Cc: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>, IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000042f21805d00145e9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N-7vF7HmyhqaXeql3fl9IPFqhn4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Nov 2021 02:19:23 -0000

On Thu, Nov 4, 2021 at 11:27 AM Greg Shepherd <gjshep@gmail.com> wrote:

> Existence of running code for some specification means
>> not that the specification is good but that we can
>> operate and evaluate the specification to judge whether
>> it is good or not.
>>
>>                                                 Masataka Ohta
>>
>
> This, surprisingly, can't be said enough. I've repeatedly heard the
> argument that someone's running code is verification that the idea is
> sound, and therefore the solution should be adopted. And I can rarely tell
> if they are simply lacking any sense of architecture or if they are just
> trolling the group to push their work. Either way, it's exhausting.
>

The fact someone can get code to run does suggest that they have a solution
to at least a part of the problem. It rarely means they have a complete
solution.

But I have on multiple occasions received the following objections to a
proposal.

1) We don't believe your specification without code.

2) You are only here to peddle the code you have already written, you
should have talked to people earlier.

And it's the same damn people both times.

Men should really take more notice when women complain about mansplaining
because the people who do that to women do the exact same thing to other
men.