RE: [Sip] SIPit 20 survey summary

"Brian Rosen" <br@brianrosen.net> Fri, 27 April 2007 18:48 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HhVUY-0005ub-Lk; Fri, 27 Apr 2007 14:48:26 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HhVUX-0005uQ-PJ for sip-confirm+ok@megatron.ietf.org; Fri, 27 Apr 2007 14:48:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HhVUX-0005uI-Fu for sip@ietf.org; Fri, 27 Apr 2007 14:48:25 -0400
Received: from ebru.winwebhosting.com ([74.52.236.50]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhVUW-0003US-8i for sip@ietf.org; Fri, 27 Apr 2007 14:48:25 -0400
Received: from neustargw.va.neustar.com ([209.173.53.233] helo=BROSENLT40xp) by ebru.winwebhosting.com with esmtpa (Exim 4.63) (envelope-from <br@brianrosen.net>) id 1HhVU1-0001Zk-6w; Fri, 27 Apr 2007 13:47:53 -0500
From: Brian Rosen <br@brianrosen.net>
To: 'Robert Sparks' <rjsparks@estacado.net>, 'IETF SIP List' <sip@ietf.org>, sip-implementors@cs.columbia.edu, discussion@sipforum.org
Subject: RE: [Sip] SIPit 20 survey summary
Date: Fri, 27 Apr 2007 14:48:15 -0400
Message-ID: <075001c788fc$9f6a2be0$640fa8c0@cis.neustar.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <687F5314-7A9B-443E-85A0-0DA3FD7D7030@estacado.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AceIGJCaZDa+E6LPR56qjSCK6qd7hgA4ubcA
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ebru.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Source:
X-Source-Args:
X-Source-Dir:
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc:
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

I'd like to point out one thing about this:

> This is how they answered for multipart/mime:
>     2% I break if someone sends me multipart/mime
>    24% I pretend multipart/mime doesn't exist if someone sends it to me
>    24% I ignore multipart/mime but will proxy it or hand it to my
> application if it shows up
>    10% I try to do something useful with multipart/mime I receive,
> but I never send it
>     4% I ignore multipart/mime that I receive, but I try to do
> something useful with multipart/mime I send
>    24% I try to do something useful with multipart/mime I send and
> receive
>    12% Other

Moving forward, SIP UAs and proxies will be required to support
location-conveyance (currently draft-ietf-sip-location-conveyance-07) in
order to support location for emergency calls (citizen to authority, like
1-1-2 or
9-1-1).  -conveyance requires multipart support.  

The consequences of not supporting emergency call location will be serious.
I believe it is likely that there will eventually be regulatory requirements
to support emergency calls in some jurisdictions.  Upgrades to several
components of today's infrastructure will be needed before this all works,
but stack vendors and UA developers should put multipart (and
location-conveyance) on their development plans for next year at the latest.

Brian




_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip