[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] Thoughts on SIP Identity issues
- To: Dean Willis <dean.willis at softarmor.com>
- To: Dean Willis <dean.willis at softarmor.com>
- Subject: Re: [Sip] Thoughts on SIP Identity issues
- From: Cullen Jennings <fluffy at cisco.com>
- From: Cullen Jennings <fluffy at cisco.com>
- Date: Wed, 6 Aug 2008 06:56:21 -0700
- Date: Wed, 6 Aug 2008 06:56:21 -0700
- Authentication-results: sj-dkim-4; header.From=fluffy at cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
- Authentication-results: sj-dkim-4; header.From=fluffy at cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
- Cc: "Uzelac, Adam" <Adam.Uzelac at globalcrossing.com>, SIP IETF <sip at ietf.org>, Paul Kyzivat <pkyzivat at cisco.com>, "Elwell, John" <john.elwell at siemens.com>, Dan Wing <dwing at cisco.com>
- Cc: "Uzelac, Adam" <Adam.Uzelac at globalcrossing.com>, SIP IETF <sip at ietf.org>, Paul Kyzivat <pkyzivat at cisco.com>, "Elwell, John" <john.elwell at siemens.com>, Dan Wing <dwing at cisco.com>
- Delivered-to: ietfarch-sip-web-archive at core3.amsl.com
- Delivered-to: sip at core3.amsl.com
- Delivered-to: ietfarch-sip-archive at core3.amsl.com
- Delivered-to: sip at core3.amsl.com
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=408; t=1218031078; x=1218895078; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy at cisco.com; z=From:=20Cullen=20Jennings=20<fluffy at cisco.com> |Subject:=20Re=3A=20[Sip]=20Thoughts=20on=20SIP=20Identity= 20issues |Sender:=20; bh=BHKi9UALqbV0goKBYgy9rEe0W6BL/kLx3CQZJuY53SM=; b=GX69UMUrZ8h9knBVaq4LlLR3Kx7BjgQZ2NpFcoomQZx/iT+SdJqQCKL6WJ TfhP775wZN91jGxicAhVnUcsugzZvkv/nFX6YrRLL80pXtYVlcgJwN3G6P+4 UV4hcWAjvD;
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=408; t=1218031078; x=1218895078; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy at cisco.com; z=From:=20Cullen=20Jennings=20<fluffy at cisco.com> |Subject:=20Re=3A=20[Sip]=20Thoughts=20on=20SIP=20Identity= 20issues |Sender:=20; bh=BHKi9UALqbV0goKBYgy9rEe0W6BL/kLx3CQZJuY53SM=; b=GX69UMUrZ8h9knBVaq4LlLR3Kx7BjgQZ2NpFcoomQZx/iT+SdJqQCKL6WJ TfhP775wZN91jGxicAhVnUcsugzZvkv/nFX6YrRLL80pXtYVlcgJwN3G6P+4 UV4hcWAjvD;
- In-reply-to: <4898802A.2000709@softarmor.com>
- In-reply-to: <4898802A.2000709@softarmor.com>
- List-help: <mailto:sip-request@ietf.org?subject=help>
- List-help: <mailto:sip-request@ietf.org?subject=help>
- List-id: Session Initiation Protocol <sip.ietf.org>
- List-id: Session Initiation Protocol <sip.ietf.org>
- List-post: <mailto:sip@ietf.org>
- List-post: <mailto:sip@ietf.org>
- List-subscribe: <https:From sip-bounces@ietf.org Wed Aug 6 06:57:40 200>
- List-subscribe: <https://www.ie//www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
- References: <0D5F89FAC29E2C41B98A6A762007F5D0F266CD@GBNTHT12009MSX.gb002.siemens.net> <02829328-7B0E-41AB-B325-01246363D09C@cisco.com> <4DAE5E60BA49D8419D7C8832503F5FFC072817AF26@EVS10.ams.gblxint.com> <0D5F89FAC29E2C41B98A6A762007F5D0F26CCB@GBNTHT12009MSX.gb002.siemens.net> <48919248.7060600@cisco.com> <0ae201c8f310$d183a0f0$3675150a@cisco.com> <E6C2E8958BA59A4FB960963D475F7AC30F04C561DB@mail.acmepacket.com> <20080731205152.03E7E514892@kilo.rtfm.com> <E6C2E8958BA59A4FB960963D475F7AC30F04C5632F@mail.acmepacket.com> <20080801010212.654B5515743@kilo.rtfm.com> <0a2101c8f3b1$b75dd500$6a94150a@cisco.com> <20080801134611.1B8C9516C54@kilo.rtfm.com> <489336E4.6050204@cisco.com> <0D5F89FAC29E2C41B98A6A762007F5D0F565E2@GBNTHT12009MSX.gb002.siemens.net> <4898802A.2000709@softarmor.com>
- References: <0D5F89FAC29E2C41B98A6A762007F5D0F266CD@GBNTHT12009MSX.gb002.siemens.net> <02829328-7B0E-41AB-B325-01246363D09C@cisco.com> <4DAE5E60BA49D8419D7C8832503F5FFC072817AF26@EVS10.ams.gblxint.com> <0D5F89FAC29E2C41B98A6A762007F5D0F26CCB@GBNTHT12009MSX.gb002.siemens.net> <48919248.7060600@cisco.com> <0ae201c8f310$d183a0f0$3675150a@cisco.com> <E6C2E8958BA59A4FB960963D475F7AC30F04C561DB@mail.acmepacket.com> <20080731205152.03E7E514892@kilo.rtfm.com> <E6C2E8958BA59A4FB960963D475F7AC30F04C5632F@mail.acmepacket.com> <20080801010212.654B5515743@kilo.rtfm.com> <0a2101c8f3b1$b75dd500$6a94150a@cisco.com> <20080801134611.1B8C9516C54@kilo.rtfm.com> <489336E4.6050204@cisco.com> <0D5F89FAC29E2C41B98A6A762007F5D0F565E2@GBNTHT12009MSX.gb002.siemens.net> <4898802A.2000709@softarmor.com>
- Sender: sip-bounces at ietf.org
On Aug 5, 2008, at 9:30 , Dean Willis wrote:
The "right" way to do what we seem to want here probably involves
adding
a routing protocol layer to RTP. That, however, makes for a very
different architecture from what we have now.
Our NAT traversal story for SIP more or less has formed a routing
system for RTP so this might not be that far off.
Cullen <with my individual hat on>
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip
tf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org
On Aug 5, 2008, at 9:30 , Dean Willis wrote:
The "right" way to do what we seem to want here probably involves
adding
a routing protocol layer to RTP. That, however, makes for a very
different architecture from what we have now.
Our NAT traversal story for SIP more or less has formed a routing
system for RTP so this might not be that far off.
Cullen <with my individual hat on>
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip