Re: [ietf-privacy] Logging Recommendations for Internet-Facing Servers

S Moonesamy <sm+ietf@elandsys.com> Mon, 16 June 2014 00:35 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf-privacy@ietfa.amsl.com
Delivered-To: ietf-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16C8E1B298C for <ietf-privacy@ietfa.amsl.com>; Sun, 15 Jun 2014 17:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.849
X-Spam-Level:
X-Spam-Status: No, score=-0.849 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.651, T_DKIM_INVALID=0.01] autolearn=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 tJKP7GNoXfSe for <ietf-privacy@ietfa.amsl.com>; Sun, 15 Jun 2014 17:35:36 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 49E391B298A for <ietf-privacy@ietf.org>; Sun, 15 Jun 2014 17:35:36 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.133.158]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s5G0ZDH3014363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 15 Jun 2014 17:35:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1402878926; x=1402965326; bh=dk2KKZCn6HeqGSfkScox1u2+UbB9EX5n0b0CbcwHhlc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hQK6PGCVyDnTynEKsarcEomkArJnwB8AQo6OQYGQdcxQ+6W17D4GXj+niplHzcEwP rQSjA1lO+NVtdS3K6Z38trYJEYSIUPLQvhVUMOQ4IOkO+I2v4cf/fA3K8mpqdIYxBC /lMXeOD+zjHcW4qF+hGt3xTj4RER0QV59oCRLrt4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1402878926; x=1402965326; i=@elandsys.com; bh=dk2KKZCn6HeqGSfkScox1u2+UbB9EX5n0b0CbcwHhlc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=YeeA5Anc83GMAvmmrg51q/JRUnyMsalhLeip8xA/trsT04CHEZH8mTCsplK9KerDC dDyTnNZ4mIVc5TQKlba6VDKs142RorR2bzucptG5pnOfhQMa0yKpeylBWMMt26PutJ h8wpIN427yPHpTL8qir/329VxVmzAgW33Zs2w25A=
Message-Id: <6.2.5.6.2.20140615110808.0bb44ef8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 15 Jun 2014 11:38:20 -0700
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Linus Nordberg <linus@nordberg.se>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <539D96ED.2060901@cs.tcd.ie>
References: <6.2.5.6.2.20140605221300.0d300d58@elandnews.com> <87d2eaz7x2.fsf@nordberg.se> <539D96ED.2060901@cs.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-privacy/FQXfA0Yx-yQe1p8x0SH7ddSxD1o
Cc: ietf-privacy@ietf.org
Subject: Re: [ietf-privacy] Logging Recommendations for Internet-Facing Servers
X-BeenThere: ietf-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Internet Privacy Discussion List <ietf-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-privacy/>
List-Post: <mailto:ietf-privacy@ietf.org>
List-Help: <mailto:ietf-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jun 2014 00:35:37 -0000

Hi Stephen,
At 05:51 15-06-2014, Stephen Farrell wrote:
>Q: How will that happen?
>A: Someone will need to write an I-D:-)
>
>If someone does such an I-D that is reasonable and improves
>privacy, I'll be happy to help that progress.

Ok.

>Not sure if the BCP's RFC would need replacing or if updating
>the BCP with a 2nd RFC would be right myself, so talking to
>the original authors and/or the intarea list would seem wise.
>They might also have other stuff they'd like to revise, who
>knows. (The draft leading to this BCP [1] was an intarea [2]
>draft.)

In theory a (future) RFC can be added to BCP 162.  In practice people 
won't read it or miss it.  A first step might be to talk to the 
authors to see what they would like to do.  The INTAREA working group 
[1] lacks the expertise to review privacy-related drafts.  People 
with an actual interest in privacy will have to participate in the 
working group and review the proposed update to BCP 162.

Regards,
S. Moonesamy

1. https://datatracker.ietf.org/wg/intarea/