RE: AW: [Enum] Carrier ENUM mini-BoF Agenda

["Stastny Richard" <Richard.Stastny at oefeg.at>]

Peter Williams wrote:
> > > a: within User ENUM there exist privacy issues.
> > >     set-up properly these issues do not exist in "Carrier ENUM",
> > >     because either the information is not accessible or not usable
> > >     by end-users.
> > >     Note: all privacy issues with ENUM should thereore be discussed
> > >     in the first half of the meeting, not in the mini-BoF on "Carrier
> >ENUM"
> >
> >   Good point.
> 
> 
> This is not appropriate, in my view. The reasoning is very flawed. There
> is
> a relationship between holder of the E.164 and the ENUM provider. While
> end-users may be unable to gain access to the marketing information
> derived
> from the providers analyis of the transactions for a given ENUM name,
> listing beneath e164.arpa (or elsewhere), the provider may seek to sell
> this
> information about the holder to value-added resellers, folk sellling
> additional telematic services, etc etc. This is quite typical in the US,
> and
> is what the US privacy policy apparatus is designed to codify, and
> disclose
> (even if it provides little in the way of enfocement) - so subscribers are
> at least notified of the possible arrangements that may impact their wider
> use of telematics.
> 
[Richard>] With setting it up properly I meant that the privacy data 
is secured from end-user access by established means. Period.
There are now already a bunch of privacy data out in databases, more
or less protected. The more or less is none of our business.

That companies may resell this data may happen, but in Europe
this is not allowed without subscriber consent by the data protective
laws. If this is different in US, go change the law, but I do
not think IETF is the right place to do this.

If somebody within a company is breaking the law, there is no
means by a protocol or architecture to prevent this. So there is
no reason to discuss or bemoan this in the ENUM WG or the mini-BOF
on carrier ENUM, it is a complete waste of time.

Richard

_______________________________________________
enum mailing list
enum at ietf.org
https://www1.ietf.org/mailman/listinfo/enum