IETF Logo Mail Archive

Re: [Int-area] Kathleen Moriarty's Yes on draft-ietf-intarea-hostname-practice-04: (with COMMENT)

Christian Huitema <huitema@huitema.net> Thu, 02 February 2017 23:47 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 494A11299BB for <int-area@ietfa.amsl.com>; Thu, 2 Feb 2017 15:47:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.757
X-Spam-Level:
X-Spam-Status: No, score=-3.757 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.156, SPF_PASS=-0.001] autolearn=unavailable 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 gZ5OksDAoGho for <int-area@ietfa.amsl.com>; Thu, 2 Feb 2017 15:47:34 -0800 (PST)
Received: from mx36-42.antispamcloud.com (mx36-42.antispamcloud.com [209.126.121.30]) (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 8C6C8129972 for <int-area@ietf.org>; Thu, 2 Feb 2017 15:47:34 -0800 (PST)
Received: from xsmtp31.mail2web.com ([168.144.250.234] helo=xsmtp11.mail2web.com) by mx36.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.86) (envelope-from <huitema@huitema.net>) id 1cZR6D-0002Ku-66 for int-area@ietf.org; Fri, 03 Feb 2017 00:47:34 +0100
Received: from [10.5.2.12] (helo=xmail02.myhosting.com) by xsmtp11.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1cZR68-0003Pc-HR for int-area@ietf.org; Thu, 02 Feb 2017 18:47:32 -0500
Received: (qmail 3212 invoked from network); 2 Feb 2017 23:47:28 -0000
Received: from unknown (HELO [192.168.200.66]) (Authenticated-user:_huitema@huitema.net@[72.235.151.78]) (envelope-sender <huitema@huitema.net>) by xmail02.myhosting.com (qmail-ldap-1.03) with ESMTPA for <int-area@ietf.org>; 2 Feb 2017 23:47:27 -0000
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
References: <148597995644.19147.5662596058741679761.idtracker@ietfa.amsl.com> <98a7c881-0e44-59ae-f820-41f0a57d5d0f@huitema.net> <CAHbuEH4oq7iq1xWnYPAhvzxGYUS4fPNVvJP1QO2pij95i+N4cw@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <e2fa2d68-e1f5-8f29-74a8-ff0ea9e6e298@huitema.net>
Date: Thu, 02 Feb 2017 13:47:25 -1000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CAHbuEH4oq7iq1xWnYPAhvzxGYUS4fPNVvJP1QO2pij95i+N4cw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: 168.144.250.234
X-SpamExperts-Domain: xsmtpout.mail2web.com
X-SpamExperts-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-SpamExperts-Outgoing-Class: ham
X-SpamExperts-Outgoing-Evidence: Combined (0.04)
X-Recommended-Action: accept
X-Filter-ID: s0sct1PQhAABKnZB5plbIVbU93hg6Kq00BjAzYBqWlVTHAar8Je/lORhy3PZJU8LERWeKKG4PAQY Nyavp7c49FXKwZbSflcvTu2SSy6NnOlTugiLDom8V25hond3K4RsO76XSTAwtV4mg4i2ouCDa4AU hvIWAV5xUW/+gAh4vXo6lgC+OSEHpaYTubtN5qh4RcOb18WfxGyg6Om6u4YYm7S63TAnH7NYUZmI wYUJpMw5hjoyEb9Oq0NWpyO3vrfYzS02aeiYw+GANPqwVsDMNz3dKxLhoxcmaInYbR5vlqGudzLe k2TYFBStSOMccbr5Uz0sPgnpAk2KA2vJwMd1uWhCmLzOxTAcQmFWVARhgNqBNFD3an3wiMp49rVr ybSBcKaDTe3QRRhTm1Fh3Md1txQRCdMNhge1Unb77YyuZq5Mp47GVCdF9wr8ftn2mWYkRBdQ80wr wyng3wNtDYr6IWSdEOMftBjsWb6BDQzjSsEw7+KMtoemwN8keIAcPKMBBQ67muZNm3G2c8/Pjjqy k0k0bdVHmDm5y9NcoZdM30MpNkbYYJ8YZ7d5zi74j6F/pxvnk7PJGygctl3LC86in/6DwZpjxPTx I2S/vwoydU2Z0wfN9VTx9JdR4F4pphrEJ0EukYkH0+QwgTkvGReJqS3AA1zi4L4OJ0M18xnuBW/6 592ULW4vfh/b1HrXegYtA33RcJFkKtzectVa+m3FGVTjivxAvo3c7emvOBtm7Pu6elFFgxvixKHD +ndZqoQq0JFb5sY5yvsuaKnQYvhP+274nM+117vLjWiTA8zC3e5qTjAEzQR26Rr0dPOgWImr8RLl b7eodTN0qqevpgO22x1MHpWWGb467MW5FZ9pSB8=
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/3VVgdIakf0U22sJtSszpeh8Y7eQ>
Cc: draft-ietf-intarea-hostname-practice@ietf.org, int-area@ietf.org, The IESG <iesg@ietf.org>, intarea-chairs@ietf.org
Subject: Re: [Int-area] Kathleen Moriarty's Yes on draft-ietf-intarea-hostname-practice-04: (with COMMENT)
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 23:47:36 -0000


On 2/2/2017 8:45 AM, Kathleen Moriarty wrote:
> On Thu, Feb 2, 2017 at 12:08 PM, Christian Huitema <huitema@huitema.net> wrote:
> ...
>> OK. This is the classic tension between privacy and management, and we
>> can certainly add a statement in the privacy section. Kathleen, do you
>> prefer something specific to incident response, or should we write
>> something more generic?
> Thanks, Christian.  Something more generic and maybe in the security
> section as it's used in a security function to track attackers.
How about saying something like "In managed environments, the hostname
is often used as part of incident response
or other security related functions. Mitigations for the hostname
related privacy
issues will need to consider the effect on these functions" ?

-- Christian Huitema

v2.23.0 | Report a Bug | By Email