RE: [Sip] INFO: A recap, sense of consensus and a proposal for direction.

"Eric Burger" <eburger@bea.com> Sun, 04 November 2007 17:21 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 1IojAH-0005Sc-9n; Sun, 04 Nov 2007 12:21:37 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IojAF-0005RN-TE for sip-confirm+ok@megatron.ietf.org; Sun, 04 Nov 2007 12:21:35 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IojAF-0005RC-IR for sip@ietf.org; Sun, 04 Nov 2007 12:21:35 -0500
Received: from repmmg02.bea.com ([66.248.192.39]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IojAF-0006YR-3n for sip@ietf.org; Sun, 04 Nov 2007 12:21:35 -0500
Received: from repmmr02.bea.com (repmmr02.bea.com [10.160.30.72]) by repmmg02.bea.com (Switch-3.3.0/Switch-3.2.7) with ESMTP id lA4HLR15010511; Sun, 4 Nov 2007 09:21:27 -0800
Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr02.bea.com (Switch-3.3.0/Switch-3.2.7) with ESMTP id lA4HLPhS009746; Sun, 4 Nov 2007 09:21:26 -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: 7bit
Subject: RE: [Sip] INFO: A recap, sense of consensus and a proposal for direction.
Date: Sun, 04 Nov 2007 09:21:20 -0800
Message-ID: <A5E9CBACB726CB4BAA3DAFF0925C188F0215F2C1@repbex01.amer.bea.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DFEE085B@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] INFO: A recap, sense of consensus and a proposal for direction.
Thread-Index: AcgbIY00oS2TP5mKSYi+xw3th4CDlAAHhxNhAPHWPgA=
References: <8983EC086A9D954BA74D9763E853CF3E04183D84@xmb-rtp-215.amer.cisco.com> <63DAB754-7CAF-48DA-9E47-96905FE45E81@nostrum.com> <9EE99659-BC47-4F29-8C95-652A95D2EF7B@softarmor.com> <EFC02CB0-F640-49D1-8C51-349A909DC9D0@nostrum.com> <20C2BE8C-BBBF-474F-967D-81438FF4EDF0@softarmor.com> <472505F8.5090401@nostrum.com> <8FF0EFA1-77DA-4D68-9B34-2AB904C9ED42@softarmor.com> <47255D1A.30206@nostrum.com> <E6C2E8958BA59A4FB960963D475F7AC3022B33C132@mail.acmepacket.com><472756C2.1010205@nostrum.com> <47277440.3050707@cisco.com> <CA9998CD4A020D418654FCDEF4E707DFEE085B@esealmw113.eemea.ericsson.se>
From: Eric Burger <eburger@bea.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
x-BEA-PMX-Instructions: AV
x-BEA-MM: Internal-To-External
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: sip List <sip@ietf.org>
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

Wasn't this why we were going to publish the perils of INFO? 

-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
Sent: Tuesday, October 30, 2007 6:02 PM
[snip]
I also know that other SDOs are looking into using INFO for certain
things, so I think it would be really good to define a proper mechanism
before they also start to use INFO as it's used today (with all the
problems people have listed).
[snip]

Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.


_______________________________________________
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