Re: a brief pondering
Narelle Clark <narellec@gmail.com> Mon, 23 March 2020 22:37 UTC
Return-Path: <narellec@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 EFBBF3A0E80 for <ietf@ietfa.amsl.com>; Mon, 23 Mar 2020 15:37:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level:
X-Spam-Status: No, score=-2.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) 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 o2o-DOIV6vLp for <ietf@ietfa.amsl.com>; Mon, 23 Mar 2020 15:37:02 -0700 (PDT)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 8671B3A0D72 for <IETF@ietf.org>; Mon, 23 Mar 2020 15:36:57 -0700 (PDT)
Received: by mail-vs1-xe29.google.com with SMTP id d18so2019952vso.7 for <IETF@ietf.org>; Mon, 23 Mar 2020 15:36:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2hAgLaPZRbv/66jSWzuP/kd7pk7E6czxVuKeYT/BEbs=; b=DYRUoC85Qrvg23sj07DqMA7nYWKJqq7DADqGBj+s0/SnhweOWJWYvfrbkyvXEj4Kx1 oV7knrcTikFx7eUEk2+emAEzQ/NTtfBohcuIId0TeBH5VECXBvUEIZTsiD50NzWzjdkl sAtQrGkPJZaUEmWoe4Cxlt9Tq7sseAyd0IPHJ6NVpidTc5TXnEHW+UIvMm5Wwzl5LS+3 7f5bsLyX16xajudtx7VnwQRe0fwiV+DpEVu7TxBT+Ijdl13jaae8O1wOSHILpqUdIOGM EGL+1x4YH46LvwfIol8mfjmX1r3QldY/D5mKFS+UtbvFI3HGTZ62AXTxDdUV+FHHuJGg 7oSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2hAgLaPZRbv/66jSWzuP/kd7pk7E6czxVuKeYT/BEbs=; b=H9WVsm2weGLQoMJehg2J3BpAvCqejp84Jd73KI3o+RL0sa57se+CVxBVM4R68HDust w49llCiUEjt7adH+/t4Llpq0ET0IKS6Mh04uhbaK3N9b93WxvvtAQQ8xGdKI6IQJZdN/ ogn9ee18DlUNBNSQcsGEmPJ0nJyklh2+ZcOLBqHQ1BpEp9nkk29pPfRpOMTQ+CIRqIFe w6+5fgG5sTpf657O93MByYe/43Y3m7ONcZyinx9x65m940luPiBywC4zoI1xnoDFHBXk MyTq7QwkY4RLH+2H83n+dfKu2s9DFAG+EUTWKiHcHzVGd7MCItiIrrDbMC4pQOVPsTuk AQsA==
X-Gm-Message-State: ANhLgQ0CSrFCcXB+ZqZf2WMSC9ChUT8u1bbt2Q7m+cCUOTzJ7q91RpdD y0dh1z5dAdyHMhspphN7uZckQ+6uoIj5Z/F1zZE=
X-Google-Smtp-Source: ADFU+vuHLrZ0ISvJbqM/39emmADzCOee/xFt/XBkroj7T+U7HROa2B3Lns7TaHXkg/FD0IgNfTJuEVWfRv5qh1mR0M0=
X-Received: by 2002:a05:6102:31b7:: with SMTP id d23mr7424737vsh.25.1585003016259; Mon, 23 Mar 2020 15:36:56 -0700 (PDT)
MIME-Version: 1.0
References: <fd6b7ee2-cdbe-14a1-0087-ce61282b22f6@lear.ch> <29D0DCA7-1D72-428F-A6DD-05511D90C039@cable.comcast.com> <CACRMD1F3+xFU-y9W1WyrVudZGWj1zL8hYGjUWbSHxnvEsOD-Uw@mail.gmail.com> <23760.1584997700@localhost> <CAMm+LwgM605mmTUVORDNXK4Scwnh7p+A2CcovayLBg84kmqMsg@mail.gmail.com>
In-Reply-To: <CAMm+LwgM605mmTUVORDNXK4Scwnh7p+A2CcovayLBg84kmqMsg@mail.gmail.com>
From: Narelle Clark <narellec@gmail.com>
Date: Tue, 24 Mar 2020 09:36:44 +1100
Message-ID: <CACRMD1FrexZNAtEFgc4LemcOj-zW5Bc3_cPAbVKJPimY+U4P-w@mail.gmail.com>
Subject: Re: a brief pondering
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: Michael Richardson <mcr@sandelman.ca>, "Livingood, Jason" <jason_livingood@comcast.com>, ietf <IETF@ietf.org>, Eliot Lear <lear@lear.ch>
Content-Type: multipart/alternative; boundary="000000000000c08ad305a18d45c4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/D5UMrTDzCO2j7x6abJCSXNINzhs>
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: Mon, 23 Mar 2020 22:37:32 -0000
All very nice things but right now most of us are making sure a) we have enough bandwidth and b) troubleshoot customer remote access issues. Narelle On Tue, 24 Mar. 2020, 8:50 am Phillip Hallam-Baker, <phill@hallambaker.com> wrote: > At the meta level, now would be a really good time for IETF to announce > what we would like ISPs to deliver as the base connection for fast, > reliable work at home: > > * IPv6 with a block of at least 256 addresses available to the customer. > * Support port forwarding. > * etc. > > Applications really should be connecting peer-to-peer for two party > communications. A reflector becomes pretty much inevitable for n>2 of > course. > > > On the usability side, something that is really pissing me off is having > to search through multiple menus to find out what the call sign for a user > is on various apps. By call sign, I mean 'that which I type in to connect > to someone not in the contacts directory'. > > Don't expect me to 'remember' because I am having to fix this for someone > else. Alternatively, it may be six months since I last used the app. And > no, it is not obviously their email address (many people have six or more) > or their phone number (again, they can have multiple). > > There is a school of 'usability' where the user is insulated from the > information they actually need to perform their task lest it confuse them. > The dirty secret of usability engineering is that most of the focus is on > hyper-optimizing the experience for the first fifteen minutes of use. That > is the average length of a demo before a sale. > > A related problem is working out where to enter the call sign. > > > On Mon, Mar 23, 2020 at 5:11 PM Michael Richardson <mcr@sandelman.ca> > wrote: > >> >> Narelle Clark <narellec@gmail.com> wrote: >> >> Which leads me to a question: what can this community (and >> similar/adjacent ones) do >> >> productively together to help? What new things are happening on >> the network from >> >> which we can learn and quickly adapt/improve? >> >> > We can keep the internet running. That's what I'm being told to do!! >> > And we're onto it. >> >> And there is more: people are now noticing when jitter and bufferbloat >> actually matter, and ability to send A/V directly from end to end point >> really does matter. >> >> I just wish that more of the tools/platforms were: >> 1) supporting IPv6 >> 2) providing better diagnostics as to what path a particular speaker was >> using. >> 3) am I having a problem transmitting, or are they having a problem >> receiving? >> >> I think that we will see a direct relationship between using IPv6, and >> seamless/trouble-free communications. >> >> -- >> ] Never tell me the odds! | ipv6 mesh >> networks [ >> ] Michael Richardson, Sandelman Software Works | IoT >> architect [ >> ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on >> rails [ >> >> >>
- Re: a brief pondering Livingood, Jason
- a brief pondering Eliot Lear
- Re: a brief pondering Narelle Clark
- Re: a brief pondering Carsten Bormann
- Re: a brief pondering Michael Tuexen
- Re: a brief pondering Nick Hilliard
- Re: a brief pondering Carsten Bormann
- Re: a brief pondering Spencer Dawkins at IETF
- Re: a brief pondering Michael Tuexen
- Re: a brief pondering Adam Roach
- Re: a brief pondering Adam Roach
- WebRTC (Re: a brief pondering) Harald Alvestrand
- Re: a brief pondering Michael Richardson
- Re: a brief pondering Phillip Hallam-Baker
- Re: a brief pondering Narelle Clark
- Re: a brief pondering Toerless Eckert
- Re: a brief pondering Nick Hilliard
- Off-topic: making WebRTC work in practice (Re: a … Carsten Bormann
- Re: Off-topic: making WebRTC work in practice (Re… Spencer Dawkins at IETF
- Re: Off-topic: making WebRTC work in practice (Re… Carsten Bormann
- Re: Off-topic: making WebRTC work in practice (Re… Philipp Hancke
- Re: Off-topic: making WebRTC work in practice (Re… Cullen Jennings
- Re: Off-topic: making WebRTC work in practice (Re… Harald Alvestrand
- Re: Off-topic: making WebRTC work in practice (Re… Benjamin Kaduk
- Re: Off-topic: making WebRTC work in practice (Re… Bob Hinden
- Re: Off-topic: making WebRTC work in practice (Re… Harald Alvestrand
- RE: Off-topic: making WebRTC work in practice (Re… Larry Masinter
- Re: Off-topic: making WebRTC work in practice (Re… Keith Moore
- Re: Off-topic: making WebRTC work in practice (Re… Phillip Hallam-Baker
- Re: Off-topic: making WebRTC work in practice (Re… Michael Richardson
- Re: Off-topic: making WebRTC work in practice (Re… Eric Rescorla
- Re: Off-topic: making WebRTC work in practice (Re… Christer Holmberg
- Re: Off-topic: making WebRTC work in practice (Re… Peter Saint-Andre
- Re: Off-topic: making WebRTC work in practice (Re… Nico Williams
- Re: Off-topic: making WebRTC work in practice (Re… Cullen Jennings
- Re: Off-topic: making WebRTC work in practice (Re… Mary B
- Re: Off-topic: making WebRTC work in practice (Re… Harald Alvestrand
- Re: Off-topic: making WebRTC work in practice (Re… Christer Holmberg
- Re: Off-topic: making WebRTC work in practice (Re… Harald Alvestrand
- Re: Off-topic: making WebRTC work in practice (Re… Christer Holmberg
- Re: Off-topic: making WebRTC work in practice (Re… Simon Pietro Romano
- Re: Off-topic: making WebRTC work in practice (Re… Toerless Eckert
- Implementation requirement (Re: Off-topic: making… Harald Alvestrand
- COVID-19 contacts tracker (Re: a brief pondering) Benoit Claise
- Re: COVID-19 contacts tracker (Re: a brief ponder… Carsten Bormann
- Re: COVID-19 contacts tracker (Re: a brief ponder… Keith Moore
- Re: COVID-19 contacts tracker (Re: a brief ponder… John Wroclawski
- Re: COVID-19 contacts tracker (Re: a brief ponder… Bob Hinden
- Re: COVID-19 contacts tracker (Re: a brief ponder… Dirk-Willem van Gulik
- Re: COVID-19 contacts tracker (Re: a brief ponder… Keith Moore
- Re: COVID-19 contacts tracker (Re: a brief ponder… Joel M. Halpern
- Re: COVID-19 contacts tracker (Re: a brief ponder… Eric Vyncke (evyncke)
- Re: COVID-19 contacts tracker (Re: a brief ponder… John Wroclawski
- Re: COVID-19 contacts tracker (Re: a brief ponder… Keith Moore
- Re: COVID-19 contacts tracker (Re: a brief ponder… John Wroclawski
- Re: COVID-19 contacts tracker (Re: a brief ponder… Rob Sayre
- Re: COVID-19 contacts tracker (Re: a brief ponder… Fred Baker
- Re: COVID-19 contacts tracker (Re: a brief ponder… Rich Kulawiec
- Re: COVID-19 contacts tracker (Re: a brief ponder… Keith Moore
- Re: COVID-19 contacts tracker (Re: a brief ponder… Vittorio Bertola
- Re: COVID-19 contacts tracker (Re: a brief ponder… Stephane Bortzmeyer
- Re: COVID-19 contacts tracker (Re: a brief ponder… John Wroclawski
- Re: COVID-19 contacts tracker (Re: a brief ponder… Christian Huitema
- Re: COVID-19 contacts tracker (Re: a brief ponder… Jeff Tantsura
- Re: COVID-19 contacts tracker (Re: a brief ponder… Robert Raszuk
- Re: COVID-19 contacts tracker (Re: a brief ponder… Rob Sayre
- Re: COVID-19 contacts tracker (Re: a brief ponder… Phillip Hallam-Baker
- Re: COVID-19 contacts tracker (Re: a brief ponder… Harish Pillay
- RE: COVID-19 contacts tracker (Re: a brief ponder… Andrew Campling
- Re: COVID-19 contacts tracker (Re: a brief ponder… Christian
- Re: COVID-19 contacts tracker (Re: a brief ponder… Rich Kulawiec
- Re: COVID-19 contacts tracker (Re: a brief ponder… Stephane Bortzmeyer
- Re: COVID-19 contacts tracker (Re: a brief ponder… Christian
- Re: WebRTC (Re: a brief pondering) Cullen Jennings