Caller ID legal issues (was: caller ID and implementer's guid e)

[John Talbot]

Paul to answer your questions

> -----Original Message-----
> From: Paul Long [SMTP:Plong at SMITHMICRO.COM]
> Sent: 13 May 1999 10:41
> To:   ITU-SG16 at MAILBAG.INTEL.COM
> Subject:      Caller ID legal issues (was: caller ID and implementer's
> guide)
>
> (I am straying from the original topic, so I changed the Subject.)
>
> This is not a standards-related issue,
        [Talbot, John [MAIFP:EP12:EXCH]]  The requirements themselves are
defined by government bodies, but allowing the protocol to support these
services is definitly a standards related issue since compiance to them is
faced by nearly every vendor.

> so we can end this thread if someone
> objects, but I was wondering about the legal ramifications of caller ID.
> Are
> there laws in some countries that require the following, or is it just
> considered good etiquette and/or a market-driven feature?
>
> Caller ID to be transmitted if provided by the caller
        [Talbot, John [MAIFP:EP12:EXCH]]  Yes that was the malicious call
identity service where if I harass someone using my phone the police can
trace who I am. Satisfying these services is traditionaly enshrined in
operator licenses.
> Caller ID not to be displayed to the called party if so requested by the
> caller ("presentation restricted")
        [Talbot, John [MAIFP:EP12:EXCH]]  Again, yes this comes under data
protection legislation which is enshrined in the voice telephony guidelines
and therefor governs most operators in Europe. I believe though that
compliance to this is not so strictly defined in the laws in North America,
if I dial a 1800 number, even if I restrict my number that restriction is
not honoured.


> Paul Long
> Smith Micro Software, Inc.
>
>         -----Original Message-----
>         From:   Chris Purvis [SMTP:Chris.Purvis at MADGE.COM]
>         Sent:   Thursday, May 13, 1999 8:28 AM
>         To:     ITU-SG16 at MAILBAG.INTEL.COM
>         Subject:        Re: caller ID and implementer's guide
>
>         Pete,
>
>         Just a note about the security matter you mention.
>         Some PC based H.323 endpoints allow one, with just a little
> knowledge,
> to
>         persuade them to output debugging which includes all elements of
> decoded
>         RAS/Q.931-H.225.0/H.245 messages.  This is clearly "undesirable"
> when
>         security of information contained in such messages is required!
> It
> also
>         might be quite hard for some people to switch off.
>         I don't have a solution to this: I just raise it as an issue.
>
>         Regards,
>         Chris
>         --
>         Dr Chris Purvis - Senior Development Engineer, WAVE CC Software
>         Madge Networks Ltd, Wexham Springs, Framewood Road, Wexham, Berks.
> ENGLAND
>         Phone: +44 1753 661 359  email: cpurvis at madge.com
>