RE: [EME] EME charter

"Henry Sinnreich" <hsinnrei@adobe.com> Mon, 13 November 2006 20:55 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GjiqH-0006Y6-R3; Mon, 13 Nov 2006 15:55:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GjiqG-0006Y1-WB for eme@irtf.org; Mon, 13 Nov 2006 15:55:45 -0500
Received: from exprod6og54.obsmtp.com ([64.18.1.189]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GjiqE-0007IR-Nm for eme@irtf.org; Mon, 13 Nov 2006 15:55:44 -0500
Received: from source ([192.150.11.134]) by exprod6ob54.postini.com ([64.18.5.12]) with SMTP; Mon, 13 Nov 2006 12:55:41 PST
Received: from inner-relay-3.eur.adobe.com (inner-relay-3.adobe.com [192.150.20.198] (may be forged)) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id kADKqvvV001378; Mon, 13 Nov 2006 12:52:58 -0800 (PST)
Received: from fe2.corp.adobe.com (fe2.corp.adobe.com [10.8.192.72]) by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id kADKtYeA001220; Mon, 13 Nov 2006 12:55:35 -0800 (PST)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe2.corp.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 13 Nov 2006 12:55:34 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [EME] EME charter
Date: Mon, 13 Nov 2006 12:53:58 -0800
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D2214130E@namail5.corp.adobe.com>
In-Reply-To: <C17E007E.17EC9%mshore@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [EME] EME charter
Thread-Index: AccHPKfr5n6MhHMvEduQBwAKleNSdAAKHeTA
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Melinda Shore" <mshore@cisco.com>, "Fergie" <fergdawg@netzero.net>
X-OriginalArrivalTime: 13 Nov 2006 20:55:34.0321 (UTC) FILETIME=[10336210:01C70766]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: eme@irtf.org
X-BeenThere: eme@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: end-middle-end research group <eme.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/eme>, <mailto:eme-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/eme>
List-Post: <mailto:eme@irtf.org>
List-Help: <mailto:eme-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/eme>, <mailto:eme-request@irtf.org?subject=subscribe>
Errors-To: eme-bounces@irtf.org

Melinda Shore wrote:

>For example,
>relays are, unfortunately, increasingly common in VoIP networks
>and while they're effectively transparent to the application
>peers they are being addressed directly.

VoIP back to back user agents (B2BUA) are anything but transparent and
they will break SIP routing and security completely. B2BUA will most
likely also break SIP endpoint applications that they don't understand.

It took quite a number of years to develop ICE for NAT traversal, so now
how many hears will it take to traverse B2BUA?

The is the worst form of job security :-)

Thanks, Henry

-----Original Message-----
From: Melinda Shore [mailto:mshore@cisco.com] 
Sent: Monday, November 13, 2006 9:59 AM
To: Fergie
Cc: eme@irtf.org
Subject: Re: [EME] EME charter

On 11/13/06 1:10 AM, "Fergie" <fergdawg@netzero.net> wrote:
> Having said that, I would tend to think that endpoints can defined
> as the source (originator) & destination addresses in any IP
> packet.

One layer's endpoint is another layer's middlebox.  For example,
relays are, unfortunately, increasingly common in VoIP networks
and while they're effectively transparent to the application
peers they are being addressed directly.

Melinda
 

_______________________________________________
EME mailing list
EME@irtf.org
https://www1.ietf.org/mailman/listinfo/eme

_______________________________________________
EME mailing list
EME@irtf.org
https://www1.ietf.org/mailman/listinfo/eme