IETF Logo Mail Archive

Re: [Ecrit] AD review: draft-ietf-ecrit-additional-data-29

Alissa Cooper <alissa@cooperw.in> Sun, 19 July 2015 10:20 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: ecrit@ietfa.amsl.com
Delivered-To: ecrit@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3B391A8AC0 for <ecrit@ietfa.amsl.com>; Sun, 19 Jul 2015 03:20:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7] 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 ZO32R0THmmDV for <ecrit@ietfa.amsl.com>; Sun, 19 Jul 2015 03:20:31 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46F5F1A8ABD for <ecrit@ietf.org>; Sun, 19 Jul 2015 03:20:31 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 9B585202D4 for <ecrit@ietf.org>; Sun, 19 Jul 2015 06:20:30 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Sun, 19 Jul 2015 06:20:30 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=CSIp5gOY3nyjNMJzDhN52G8yJMg=; b=jqZYb1 Wj0RNzEsRK0OqnDRBX3YVX2vXJ1OuaHX3o61yiKFyWcnuQ94QeOzEjMosubPPQng 65WSyTAICE6OpOrLRZmmgSTaRkanzqgYoVsmTD9KAxU3D1DyhWFPKTmCsgHrIfr2 uS+BzwYwg0GpfqtA2mdBsSebeN/myqV8nk4Wk=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=CSIp5gOY3nyjNMJ zDhN52G8yJMg=; b=hZ8O4bfN1Guvjodnb+b39o2yPXJ+XdiH6rNGg3RGFdm/Vb4 O9cTD20jXVPSwc0ktvqlLn47iSf66DJMAPKZEmF0zEhAR0Hj35ZAVNVuHYQCVTMA AHV/muqEw01KGWby8uwTqGL7ue7QZDk8yxFljC+sE4JDA+aaGSZHHUKQl9bI=
X-Sasl-enc: OLcLbmZh/6KyzQxwH7jinGq/PiO7tIwIBEBoFnIhSzP0 1437301229
Received: from [10.24.134.123] (unknown [128.107.241.162]) by mail.messagingengine.com (Postfix) with ESMTPA id D4124C00017; Sun, 19 Jul 2015 06:20:27 -0400 (EDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <5903491F-5756-4D9A-BD7A-A81C75EF6730@neustar.biz>
Date: Sun, 19 Jul 2015 12:20:24 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C86AAFF5-CB9F-49B9-AF7E-43555A769209@cooperw.in>
References: <99E88B8D-C7E1-4C33-A5FC-45E105D28580@cooperw.in> <p06240600d194f63d737f@[99.111.97.136]> <AA8402BC-217E-4072-94A6-4C9B3BB2A08B@cooperw.in> <p0624060ad1c4cfdd4c23@[99.111.97.136]> <FFE14662-87AD-4970-8E3D-201203305B8D@cooperw.in> <5903491F-5756-4D9A-BD7A-A81C75EF6730@neustar.biz>
To: "Rosen, Brian" <Brian.Rosen@neustar.biz>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ecrit/2WhKxrql5FUWibBNc28mAJ3icdI>
Cc: "ecrit@ietf.org" <ecrit@ietf.org>, Randall Gellens <rg+ietf@qti.qualcomm.com>
Subject: Re: [Ecrit] AD review: draft-ietf-ecrit-additional-data-29
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ecrit/>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Jul 2015 10:20:32 -0000

On Jul 17, 2015, at 5:59 PM, Rosen, Brian <Brian.Rosen@neustar.biz> wrote:

>>> 
>>> The thing about the subscriber privacy indicator is that it's up to 
>>> local regulation what elements it covers and what it means.  I don't 
>>> think we can dictate that.
>> 
>> Well, does it have to be in the owner/subscriber block? I thought that implied that it was only relevant to the owner/subscriber data, but if it could be interpreted more broadly then I’m not sure it makes sense to put it in that block.
>> 
> There are jurisdictions that, for example, would consider the telephone number to be private, and that is not in the owner/subscriber block.  But all of the data in that block is affected by the privacy indicator in all the jurisdictions I’m aware of.  So, I do think it’s in the right place.
> 
> Randy’s point was that what it means changes from one jurisdiction to another, so what fields it affects could vary, and which blocks they are a part of will vary.  I don’t think we want to make the mechanism more complex. 

Ok. If you could add a sentence to the description to make it clear that the application of the indicator may extend to any of the additional data shared, I think that would help.

Thanks,
Alissa

> 
> Brian
> 
>

v2.23.0 | Report a Bug | By Email