Re: [straw] What is an "end"?

"Ram Mohan R (rmohanr)" <rmohanr@cisco.com> Wed, 02 December 2015 16:23 UTC

Return-Path: <rmohanr@cisco.com>
X-Original-To: straw@ietfa.amsl.com
Delivered-To: straw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6BA31B2A84 for <straw@ietfa.amsl.com>; Wed, 2 Dec 2015 08:23:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.911
X-Spam-Level:
X-Spam-Status: No, score=-13.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_64=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 7DtJouD7XPeZ for <straw@ietfa.amsl.com>; Wed, 2 Dec 2015 08:23:30 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDBA01B2A51 for <straw@ietf.org>; Wed, 2 Dec 2015 08:23:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2364; q=dns/txt; s=iport; t=1449073409; x=1450283009; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=Hn4I9UendGuiQoDLnuDbUGwHBQZllMV0H1hELvDfVBw=; b=lXaSK9laR1nesBISmP0RE0NVBnv/TYT343TOUEikopWjcfnZtgIuDdJR hU2Fu3AEtw8nJzAsLak87PTFqqEWEAlm3GV71zK7RCg74k0C1hUiqZXNv 8+zEvN8e8V+WFNs3QHrxaT+OgEOgRGcvqP7cojvPs/ec9XQKJWj8rgxmC w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AcAgDJGV9W/40NJK1VCQ6DLFNvBr4FAQ2BbhcKhW0CgUw4FAEBAQEBAQGBCoQ0AQEBBAEBAWsXBAIBCA4DAwECAS4nCx0IAgQBEogvDcAJAQEBAQEBAQEBAQEBAQEBAQEBARYEhlWEfIQxEReEYAWNXoh+AY06nGkBHwEBQoNGPnKEaIEHAQEB
X-IronPort-AV: E=Sophos;i="5.20,373,1444694400"; d="scan'208";a="51986742"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 02 Dec 2015 16:23:29 +0000
Received: from XCH-RTP-018.cisco.com (xch-rtp-018.cisco.com [64.101.220.158]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id tB2GNSDW030647 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 2 Dec 2015 16:23:29 GMT
Received: from xch-rtp-017.cisco.com (64.101.220.157) by XCH-RTP-018.cisco.com (64.101.220.158) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 2 Dec 2015 11:23:27 -0500
Received: from xch-rtp-017.cisco.com ([64.101.220.157]) by XCH-RTP-017.cisco.com ([64.101.220.157]) with mapi id 15.00.1104.000; Wed, 2 Dec 2015 11:23:28 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "straw@ietf.org" <straw@ietf.org>
Thread-Topic: [straw] What is an "end"?
Thread-Index: AQHRLR3G8SKnsCDjrki4kF41uwtRVQ==
Date: Wed, 02 Dec 2015 16:23:28 +0000
Message-ID: <D2851887.4B386%rmohanr@cisco.com>
References: <20151201045818.23491.19134.idtracker@ietfa.amsl.com> <E63559A7-6A37-496C-AAD9-426AB697FD65@nostrum.com> <565F0940.5010506@alum.mit.edu>
In-Reply-To: <565F0940.5010506@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.8.151023
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.78.101]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <59D31B1CA2E6444FB3C87AD1EE819CD7@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/straw/7uI1QcLH6y3Zgc0kMrBOUEdGX4A>
Subject: Re: [straw] What is an "end"?
X-BeenThere: straw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Sip Traversal Required for Applications to Work \(STRAW\) working group discussion list" <straw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/straw>, <mailto:straw-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/straw/>
List-Post: <mailto:straw@ietf.org>
List-Help: <mailto:straw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/straw>, <mailto:straw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Dec 2015 16:23:32 -0000

Hi Paul,

-----Original Message-----
From: straw <straw-bounces@ietf.org> on behalf of Paul Kyzivat
<pkyzivat@alum.mit.edu>
Date: Wednesday, 2 December 2015 at 8:37 PM
To: "straw@ietf.org" <straw@ietf.org>
Subject: [straw] What is an "end"?

>On 12/1/15 1:40 PM, Ben Campbell wrote:
>
>> - Define what we mean by e2e. I _think_ we are talking about end-user
>> devices, and that we don't want to leave room for semantic games along
>> the line of calling a b2bua an "end". (This would change the arguments
>> around certain requirements, e.g."don't terminate srtp".)
>
>I think this is important! And I think it goes beyond this draft or
>perhaps even this WG.
>
>ISTM that the definition of "end" is a matter of control. I may have a
>server somewhere (maybe in a cloud), as well as one or more local
>devices. As long as I control it and am aware of its behavior it can be
>considered an *end* representing me, and carry my identity in the
>signaling.
>
>And this can be true even if it is not an "end" in the overall topology
>of a call. For instance, I could have a B2BUA (application server)
>between my phone and the "other" party in a call. It might record the
>call (on my behalf) or otherwise process the media. It could serve as
>the hub for a decomposed endpoint.
>
>OTOH, a "traditional" SBC is typically *not* entirely under my control.
>It may well have policies that I disagree with, but can't avoid. I would
>like to ensure that it can't access the content of my media.

Agree with all the above. I don¹t see a way by which one endpoint can know
if the peer is a endpoint/B2BUA or SBC.
If both peers are using rfc4474 it can verify the identity of the peer but
it will still not tell whether that is the final destination
for the call or if the call goes beyond that device(like in the case of
B2BUA/SBC).

I don¹t see a way to solve this with existing mechanisms.

Ram

>
>This gets tricky when my SP provides application services to me in a
>shared server. It may give me some configuration options to influence
>the behavior of that server. But it may also have other policies of its
>own that it doesn't allow me to control.
>
>	Thanks,
>	Paul
>
>_______________________________________________
>straw mailing list
>straw@ietf.org
>https://www.ietf.org/mailman/listinfo/straw