Re: [MMUSIC] Lawful intercept - don't (Re: IETF#89: First version of CLUE Data Channel slide set.)

"Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com> Mon, 03 March 2014 13:27 UTC

From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: Harald Alvestrand <harald@alvestrand.no>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Lawful intercept - don't (Re: IETF#89: First version of CLUE Data Channel slide set.)
Thread-Index: AQHPNuPtojrwWNrIz0u/GKnujYzdjw==
Date: Mon, 03 Mar 2014 13:24:38 +0000
Message-ID: <E1FE4C082A89A246A11D7F32A95A17826E004D0E@US70UWXCHMBA02.zam.alcatel-lucent.com>
References: <7594FB04B1934943A5C02806D1A2204B1D1C0E03@ESESSMB209.ericsson.se> <CAHBDyN75R1Wr5BODSQ9RNmNP9G7QZdOjZ9Lw+Vz3DCEUUYh4-Q@mail.gmail.com> <CAHBDyN5aDiJHy0fZ3=A8bLyCGAEhSojxu0_kAdLvOTykykE36Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1C2DF7@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003463@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C3A97@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003836@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C4C1F@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003961@US70UWXCHMBA02.zam.alcatel-lucent.com> <53139A10.1040502@alum.mit.edu> <E1FE4C082A89A246A11D7F32A95A17826E003DC8@US70UWXCHMBA02.zam.alcatel-lucent.com> <5314404D.5070500@alvestrand.no>
In-Reply-To: <5314404D.5070500@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/7_Mf31B7D5CgGJVQLPAboTUz7Xw
Subject: Re: [MMUSIC] Lawful intercept - don't (Re: IETF#89: First version of CLUE Data Channel slide set.)
Precedence: list

> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Harald Alvestrand
> Sent: Monday, March 03, 2014 2:42 AM

> On 03/03/2014 12:00 AM, Makaraju, Maridi Raju (Raju) wrote:
> >>> > > */1./*Lawful intercept (LI): A CLUE channel may have to be reported
> to
> >>> > > LI agents per regulatory requirements. For various reasons such
> >>> > > reporting may have to be interworked with non-data channel SCTP/dTLS
> >>> > > transport (e.g. TCP).
> >> >
> >> > By explicit policy we don't consider lawful intercept in IETF.
> >> > The same issue exists for the RTP.
> > [Raju] I understand LI is a very sensitive subject and by no means I am
> making any statements about it. My comment was providing one use case to
> which a service provider may be legally obligated to oblige.
> >
> > There are other cases that may require interworking at gateways.
> >
> 
> When stating the use case, just say that one of the participants in a
> CLUE channel (including the gateway) may choose to share the content (or
> the existence of the channel - I can't tell which you mean by "report"
> here) with a third party.

[Raju] Both (existence/control, content) are possible with various levels of "reporting".

> 
> There are lots of reasons why someone may choose to do that, including,
> for instance, the requirement for recording financial advice given over
> the phone in many countries, and calling out legal intercept is just
> going to generate lots of heat but little light.

[Raju] Thanks for providing a non-controversial use case! :-)

Thanks
Raju

Re: [MMUSIC] IETF#89: First version of CLUE Data … Makaraju, Maridi Raju (Raju)
Re: [MMUSIC] IETF#89: First version of CLUE Data … Paul Kyzivat
Re: [MMUSIC] IETF#89: First version of CLUE Data … Makaraju, Maridi Raju (Raju)
Re: [MMUSIC] IETF#89: First version of CLUE Data … Paul Kyzivat
Re: [MMUSIC] IETF#89: First version of CLUE Data … Christian Groves
[MMUSIC] Lawful intercept - don't (Re: IETF#89: F… Harald Alvestrand
Re: [MMUSIC] IETF#89: First version of CLUE Data … Makaraju, Maridi Raju (Raju)
Re: [MMUSIC] Lawful intercept - don't (Re: IETF#8… Makaraju, Maridi Raju (Raju)