IETF Logo Mail Archive

Re: [Marnew] endpoint consent

"Songhaibin (A)" <haibin.song@huawei.com> Fri, 25 September 2015 06:14 UTC

Return-Path: <haibin.song@huawei.com>
X-Original-To: marnew@ietfa.amsl.com
Delivered-To: marnew@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2FC51B368C for <marnew@ietfa.amsl.com>; Thu, 24 Sep 2015 23:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 79lHzc_nSks5 for <marnew@ietfa.amsl.com>; Thu, 24 Sep 2015 23:14:02 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F35C1B3689 for <marnew@iab.org>; Thu, 24 Sep 2015 23:14:02 -0700 (PDT)
Received: from 172.24.1.48 (EHLO nkgeml403-hub.china.huawei.com) ([172.24.1.48]) by szxrg03-dlp.huawei.com (MOS 4.4.3-GA FastPath queued) with ESMTP id BNY68960; Fri, 25 Sep 2015 14:13:41 +0800 (CST)
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.75]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0235.001; Fri, 25 Sep 2015 14:13:36 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Aaron Falk <aaron.falk@gmail.com>, Salvatore Loreto <salvatore.loreto@ericsson.com>
Thread-Topic: [Marnew] endpoint consent
Thread-Index: AQHQ9iuobCVj11FbpUOVK8xuXEFXU55KmM0AgABecACAAA86AIAAAwkAgAG8gfA=
Date: Fri, 25 Sep 2015 06:13:36 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F6539A78D@nkgeml501-mbs.china.huawei.com>
References: <1991284A-864D-45C0-A016-A64C8FA5F029@gmail.com> <09EC7D4E-0245-4019-9D20-F95CF2362845@piuha.net> <2B9B48179856DC4FA00C93C79EB7E64A0E991DDD@ESESSMB109.ericsson.se> <CAD62q9X0o3hUp_48OQCohkxh-+g-0YN+HJNCtZJX2huwa96ujw@mail.gmail.com> <5603E174.8040009@cs.tcd.ie>
In-Reply-To: <5603E174.8040009@cs.tcd.ie>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.75]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.5604E616.0108, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.75, so=2013-05-26 15:14:31, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 82159db264fd3f3c90887fb5a427616f
Archived-At: <http://mailarchive.ietf.org/arch/msg/marnew/X5bFTkgTbMAULebll4maefPafY4>
Cc: "marnew@iab.org" <marnew@iab.org>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [Marnew] endpoint consent
X-BeenThere: marnew@iab.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Managing Radio Networks in an Encrypted World <marnew.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/marnew>, <mailto:marnew-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/marnew/>
List-Post: <mailto:marnew@iab.org>
List-Help: <mailto:marnew-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/marnew>, <mailto:marnew-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2015 06:14:05 -0000

Agree. It depends on the use case.

Best Regards!
-Haibin


> -----Original Message-----
> From: Marnew [mailto:marnew-bounces@iab.org] On Behalf Of Stephen Farrell
> Sent: Thursday, September 24, 2015 7:42 PM
> To: Aaron Falk; Salvatore Loreto
> Cc: Jari Arkko; marnew@iab.org
> Subject: Re: [Marnew] endpoint consent
> 
> 
> Hi Aaron,
> 
> On 24/09/15 12:30, Aaron Falk wrote:
> >  Meaning, only one endpoint
> > needs to be aware of the third actor but he needs to know what he is
> > giving up in security through that trust.
> 
> I don't think that is correct tbh, or maybe I'm confused about what you mean.
> 
> In the scenario where a user accesses their bank account from work in the
> presence of a TLS MITM operated for the employer, I think both endpoints have
> valid reasons to need to know about the MITM.
> 
> Cheers,
> S.
> 
> _______________________________________________
> Marnew mailing list
> Marnew@iab.org
> https://www.iab.org/mailman/listinfo/marnew

v2.8.7 | Report a Bug | By Email