IETF Logo Mail Archive

Re: build personal contacts outside of meetings [was IETF 100, Singapore -- proposed path forward and request for input]

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 25 May 2016 20:14 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 B31E712DC53 for <ietf@ietfa.amsl.com>; Wed, 25 May 2016 13:14:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.327
X-Spam-Level:
X-Spam-Status: No, score=-3.327 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham 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 VFHiWsVKMy8U for <ietf@ietfa.amsl.com>; Wed, 25 May 2016 13:14:46 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CBA212D7E8 for <ietf@ietf.org>; Wed, 25 May 2016 13:14:41 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 5F2D6203B2; Wed, 25 May 2016 16:21:03 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id DA091638BF; Wed, 25 May 2016 16:14:40 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "HANSEN, TONY L" <tony@att.com>
Subject: Re: build personal contacts outside of meetings [was IETF 100, Singapore -- proposed path forward and request for input]
In-Reply-To: <AD3E2E49-51C4-4DC6-9AD7-2F9E101D40AB@att.com>
References: <20160517181436.24852.58610.idtracker@ietfa.amsl.com> <3945cc1f-3e99-0fcb-e983-ed2e46fa871c@nostrum.com> <CA+9kkMAWFQDrT6WqTGz=6LcDiBkg+iuLEuSzeSqfZA4-J-tvZg@mail.gmail.com> <CABcZeBMGpKFiA78iQDFa5xaM0r0q_3LfLO_JKxaWJ9CBUTeaLg@mail.gmail.com> <C5B9F952-FEFC-4B73-9AC6-E050F59A74CB@consulintel.es> <CA+9kkMCQBdZOebSo9WwEd14+Bgh64Tpd+8BfF+uzbDRSV-gFxw@mail.gmail.com> <88c09ff2-51d0-d419-1253-ddd8e6049397@cisco.com> <CA+9kkMBi3pR+N3E21j=gNAKNNndX8NvpnwEJcNAYpJGpx6A6mw@mail.gmail.com> <093f7f6f-4d4a-334e-e476-a0b562bd9fd7@cisco.com> <5741EEE6.2040302@gmail.com> <c4aeef86-5c0b-1858-3340-1d1cf4dffcc3@cisco.com> <5741F491.7080908@gmail.com> <be769a9d-92d4-8f6a-12e7-8f68c74acf70@dcrocker.net> <309932C5-9ABB-4873-9EAC-0AECF1F3C4B8@nohats.ca> <0c9401d1b53a$8f12f550$ad38dff0$@huitema.net> <484467c4-8490-ac2b-a89f-9f1bf2a0e14f@gmail.com> <CAG4d1rcbk58x9OUOnHTRd7uGwGY6SEEJZmiAZkVwftOLjzjz=g@mail.gmail.com> <AD3E2E49-51C4-4DC6-9AD7-2F9E101D40AB@att.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Wed, 25 May 2016 16:14:40 -0400
Message-ID: <1755.1464207280@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/FGzlhkjfhIFprj1PKtYYvKTLAQw>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 25 May 2016 20:14:49 -0000

HANSEN, TONY L <tony@att.com> wrote:
    > It’s very useful having the pictures on the WG info pages. However,
    > it’s not a well-known resource for other purposes.

Maybe we could have some "random URL" fields available to people in the
/person/XXX.json part of the API.... that people could edit in:
                 https://datatracker.ietf.org/accounts/

and would get linked to in all places where people's name show up rather than
having the mailto: directly there.

That way people could point to linked pages, personal sites, or other places
where they can provide whatever identifying information they are confortable with.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.28.0 | Report a Bug | By Email | System Status