Re: Old directions in social media.

Eliot Lear <lear@cisco.com> Fri, 08 January 2021 13:05 UTC

Return-Path: <lear@cisco.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 0305D3A0DF3 for <ietf@ietfa.amsl.com>; Fri, 8 Jan 2021 05:05:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.973
X-Spam-Level:
X-Spam-Status: No, score=-9.973 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 C2OkVMR5bl5I for <ietf@ietfa.amsl.com>; Fri, 8 Jan 2021 05:04:59 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2BC43A0E85 for <ietf@ietf.org>; Fri, 8 Jan 2021 05:04:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2861; q=dns/txt; s=iport; t=1610111098; x=1611320698; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=VskzvrR8SgFTH7YKPUy6NkxoYuiUhz5/5TCIWrzX/MQ=; b=DIWjiRymIMMIrjFvkjaRcplIo4ngnTJDCQtxsinaHyexC5waELVyvJr5 SylYAj6S38hfJwJG5c1M1jS5ok5bS5ZxpOLW/nzl6K3Ukd9s9SMrtEgW6 J8zvKBSIx6fdc0daXo+BlYKUrIKYv72TkTwMZFL2A4+p7+2183ozl6Xtx Q=;
X-Files: signature.asc : 488
X-IPAS-Result: A0CoBABXV/hfjBbLJq1iHgEBCxIMhAUGgXwBIBIuhD+JBIgRJQOaUoFoBAcBAQEKAwEBLwQBAYRKAoFxJjgTAgMBAQEDAgMBAQEBBQEBAQIBBgQUAQEBAYZGhXMBAQEDASNLAgkFCwsYKgICVwYTgyaCZyCtOHaBMoVYhGgQgTiBU4peekGCACaBEgwQglY+hAkBEgGDOTSCLASBVYEfKQcEgVYCgQuQBYw9nCqDAIMngTeQcoYPAx+DKTqJdIU0j1Owf2KDbwIEBgUCFoFtIWlwMxoIGxU7KgGCPj4SGQ2OO4ELAQKNIkADMDcCBgEJAQEDCYxNAQE
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.79,331,1602547200"; d="asc'?scan'208";a="32501611"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 08 Jan 2021 13:04:54 +0000
Received: from [10.61.167.187] ([10.61.167.187]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 108D4rh5015552 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 8 Jan 2021 13:04:54 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <82633D31-0168-4D51-9250-2C2697FF6AE7@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_0D4D39AF-34C0-4D49-A4BF-0AF0E27C424A"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Subject: Re: Old directions in social media.
Date: Fri, 08 Jan 2021 14:04:52 +0100
In-Reply-To: <AM0PR08MB3716E884A0BF30D161E26750FAAE0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Cc: Michael Thomas <mike@mtcc.com>, The IETF List <ietf@ietf.org>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
References: <CAMm+Lwg1-pxKU8vMinFDUbVca52VgFzTOOSJMnJjaUJvF6PLew@mail.gmail.com> <062d01d6e387$39c46270$ad4d2750$@acm.org> <CAJU8_nWD3MwLs5aVNMi_3LqZysrfjv0N7N3ujV-zhqxiFh3tsA@mail.gmail.com> <788651ca-0c84-7a54-9c48-b962faed635f@network-heretics.com> <CAJU8_nXSE-E2AVrJnqe5ZifR+qGhXscNCFXQRDj_GU1r=hNOyw@mail.gmail.com> <70416f47-7c31-8571-02ce-f95ff386d54f@network-heretics.com> <X/TtgTtl02AMyns8@mit.edu> <AM0PR08MB371623409DE8AB03CC667234FAD00@AM0PR08MB3716.eurprd08.prod.outlook.com> <866b1357-ec50-7765-4277-fd4fba8d793e@network-heretics.com> <AM0PR08MB37166B8E57C293917737D9D6FAD00@AM0PR08MB3716.eurprd08.prod.outlook.com> <d8454121-f6fb-3cbb-3149-656e20efce96@joelhalpern.com> <AM0PR08MB3716C960817BCCFEE4F9F911FAAF0@AM0PR08MB3716.eurprd08.prod.outlook.com> <edf8225b-d005-4f99-b96f-41bc49633da3@joelhalpern.com> <AM0PR08MB37169778B08F3F83413194B0FAAF0@AM0PR08MB3716.eurprd08.prod.outlook.com> <01RU3E1RGXW4004QVR@mauve.mrochek.com> <e3b4e262-9d4d-2c5c-5588-67d37d8cedc4@mtcc.com> <AM0PR08MB3716E884A0BF30D161E26750FAAE0@AM0PR08MB3716.eurprd08.prod.outlook.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
X-Outbound-SMTP-Client: 10.61.167.187, [10.61.167.187]
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eRkADW8vyaA3PS_Ibqyy0Ztc21w>
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, 08 Jan 2021 13:05:08 -0000

Hi Hannes, Mike, Ned, and others,

I do think there is a transparency risk that is related to DISCUSSes and appeals that has to be considered.  However, RFC 8875 does discuss how to address that, though perhaps with a focus on DISCUSSes and appeals, in Section 3.2.

I have a bit of sympathy with Joel on not wanting to bifurcate conversations.  It’s not a matter of gray hair to me, but simply a matter of wanting to participate in formative discussions.  If they’re not happening on email, then one needs to know where they are happening, and be able to get in the game.  I don’t think there’s a perfect solve for that, but it seems to me that the concern is somewhat obviated if WGs virtually meet often.  There is, of course, a convenience tradeoff there...

Eliot

> On 8 Jan 2021, at 13:28, Hannes Tschofenig <Hannes.Tschofenig@arm.com> wrote:
> 
> On 1/7/21 9:27 AM, ned+ietf@mauve.mrochek.com wrote:
>> Speaking as 30 year IETF participant, including four years as an apps
>> AD and many stints as a WG chair, this is not now and has never been
>> my experience. I could not even begin count the number of times I've
>> had to review mailing list discussions as part of reviewing a draft.
> 
> If the document you are supposed to be reviewing does not give enough context so that you have to review the mailing list discussions then there is clearly something wrong with the document.
> That should have been your review comment.
> 
> Ciao
> Hannes
> 
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.