Re: IETF 100, Singapore -- proposed path forward and request for input

Dave Crocker <dhc@dcrocker.net> Wed, 25 May 2016 13:51 UTC

Return-Path: <dhc@dcrocker.net>
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 8FCD412B01C for <ietf@ietfa.amsl.com>; Wed, 25 May 2016 06:51:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.086
X-Spam-Level:
X-Spam-Status: No, score=-0.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RDNS_NONE=0.793] 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 TkHe4r0XKM6A for <ietf@ietfa.amsl.com>; Wed, 25 May 2016 06:51:02 -0700 (PDT)
Received: from simon.songbird.com (unknown [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5F7112DCD3 for <ietf@ietf.org>; Wed, 25 May 2016 06:47:35 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id u4PDlf8v014107 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Wed, 25 May 2016 06:47:41 -0700
Subject: Re: IETF 100, Singapore -- proposed path forward and request for input
References: <20160524210344.64781.qmail@ary.lan> <bd1f61ef-3be2-1a16-804c-68548df0b789@gmail.com> <alpine.OSX.2.01.1605242300120.194@rabdullah.local>
Cc: ietf@ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <0c5fe5a8-a973-5117-63e5-44fae6c8b349@dcrocker.net>
Date: Wed, 25 May 2016 06:46:51 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.01.1605242300120.194@rabdullah.local>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/tmcWkOp0Ie4MfrgrRCQCkuCB5kE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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 13:51:03 -0000

On 5/24/2016 11:17 PM, Ole Jacobsen wrote:
> With respect to any medical situation,
> it might be prudent to carry paperwork which documents the
> relationship.


A possible expedient is for the documentation to be in the form of a 
basic Medical Power of Attorney:

 
www.americanbar.org/content/dam/aba/uncategorized/2011/2011_aging_hcdec_univhcpaform.authcheckdam.pdf

 
http://www.nolo.com/legal-encyclopedia/living-will-power-of-attorney-29595.html


and an Advanced Medical Directive:

 
http://www.webmd.com/palliative-care/advance-directives-medical-power-attorney

    http://www.caringinfo.org/i4a/pages/index.cfm?pageid=3289

rather than documents that have a broader scope about the relationship.


I've no idea what the handling of the treatment such documents will get 
in a different country, but they would at least establish a history of 
claimed authority.

d/


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net