Re: [Geopriv] WG status update

todd <tglassey@earthlink.net> Mon, 13 October 2014 12:47 UTC

Return-Path: <tglassey@earthlink.net>
X-Original-To: geopriv@ietfa.amsl.com
Delivered-To: geopriv@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADE8A1A8A1A for <geopriv@ietfa.amsl.com>; Mon, 13 Oct 2014 05:47:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.786
X-Spam-Level:
X-Spam-Status: No, score=-2.786 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 avzfDC-4rIeU for <geopriv@ietfa.amsl.com>; Mon, 13 Oct 2014 05:47:05 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfa.amsl.com (Postfix) with ESMTP id 50A2D1A8A3F for <geopriv@ietf.org>; Mon, 13 Oct 2014 05:47:04 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=j1rZ64CinP7HmasiyNW1GZaOr0qZueSkTd/5rGlraAVBZ1HI8f6VSmgIwgsulssI; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.134.155] (helo=[192.168.0.109]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1Xdf1j-0005N0-FV for geopriv@ietf.org; Mon, 13 Oct 2014 08:47:03 -0400
Message-ID: <543BC9D0.1000203@earthlink.net>
Date: Mon, 13 Oct 2014 05:47:12 -0700
From: todd <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: geopriv@ietf.org
References: <EDBB62E9-6974-43A3-A682-D8F47C58531E@nominet.org.uk>
In-Reply-To: <EDBB62E9-6974-43A3-A682-D8F47C58531E@nominet.org.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7914a0e18889080418981e0352af62106b350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.134.155
Archived-At: http://mailarchive.ietf.org/arch/msg/geopriv/3Q75bZjHqTPF4p1AKW8Lk8Gy9cM
Subject: Re: [Geopriv] WG status update
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/geopriv/>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Oct 2014 12:47:06 -0000

Hey Ray are the IESG telechats and the IESG sessions recorded? I.e. is 
there any evidence of their operations created and how is this content 
stored? I ask this because of - well, you know.

Todd Glassey
On 10/13/2014 2:44 AM, Ray Bellis wrote:
> Just a quick update:
>
> draft-ietf-geopriv-uncertainty has now completed IETF LC and is now in IESG evaluation, on the agenda for this Thursday's IESG telechat.
>
> Just in case anything significant comes up during IESG review my expectation is that we shall keep the WG active until this doc leaves the IESG bound for the RFC Editors.  At that point I believe the intent is that the group will be closed, but with the mailing list kept active.
>
> Ray
>
> _______________________________________________
> Geopriv mailing list
> Geopriv@ietf.org
> https://www.ietf.org/mailman/listinfo/geopriv
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4765 / Virus Database: 4040/8378 - Release Date: 10/12/14
>
>

-- 
Thanks,
Todd S. Glassey
[Personal Email]
---------------------------
This email may contain confidential material protected as trade secrets 
and the like and as such is by default considered private and 
confidential in form. Without the word "PUBLIC:" as the opening tag in 
the Subject Line this email is to be considered confidential and may not 
be reproduced or excerpted in any form or disclosed to any unauthorized 
parties in any form; If this mail was forwarded or incorrectly sent to 
you please destroy it immediately.