IETF Logo Mail Archive

[Sipping] draft-johnston-sipping-cc-uui-03.txt

"Alexeitsev, D" <D.Alexeitsev@telekom.de> Thu, 15 May 2008 15:52 UTC

Return-Path: <sipping-bounces@ietf.org>
X-Original-To: sipping-archive@optimus.ietf.org
Delivered-To: ietfarch-sipping-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 13AC83A6833; Thu, 15 May 2008 08:52:21 -0700 (PDT)
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B7FC73A6833 for <sipping@core3.amsl.com>; Thu, 15 May 2008 08:51:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.248
X-Spam-Level:
X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ke8zXo4ZJG8w for <sipping@core3.amsl.com>; Thu, 15 May 2008 08:51:02 -0700 (PDT)
Received: from tcmail12.telekom.de (tcmail12.telekom.de [217.5.214.82]) by core3.amsl.com (Postfix) with ESMTP id 31AB23A67F9 for <sipping@ietf.org>; Thu, 15 May 2008 08:51:01 -0700 (PDT)
Received: from S4DE9JSAANM.ost.t-com.de (S4DE9JSAANM.ost.t-com.de [10.125.177.122]) by tcmail11.telekom.de with ESMTP for sipping@ietf.org; Thu, 15 May 2008 17:50:14 +0200
Received: from S4DE9JSAAMW.ost.t-com.de ([10.125.177.114]) by S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); Thu, 15 May 2008 17:50:14 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 15 May 2008 17:50:14 +0200
Message-Id: <F452BB3496398949B9D6634F9B6B155704127D64@S4DE9JSAAMW.ost.t-com.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: draft-johnston-sipping-cc-uui-03.txt
Thread-Index: Aci2o1ywuK63u7inT0mgKIED07xGiw==
From: "Alexeitsev, D" <D.Alexeitsev@telekom.de>
To: sipping@ietf.org
X-OriginalArrivalTime: 15 May 2008 15:50:14.0668 (UTC) FILETIME=[5D9EECC0:01C8B6A3]
Subject: [Sipping] draft-johnston-sipping-cc-uui-03.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1575591702=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

Hi,

The UUI draft was recently added to the 3GPP dependency list. In order
to boost the progress of the work I'd like to start the discussion on
the still open issues and understand what is needed to be done to push
the draft to the RFC status

Last mail thread about the draft
http://www.ietf.org/mail-archive/web/sipping/current/msg15115.html was
finished with no conclusion on the encoding details.

To have this clarified - is the encoding clarification made in the
http://www.ietf.org/mail-archive/web/sipping/current/msg15091.html
acceptable? If not, what are the counter proposals?

Greetings,
Denis Alexietsev




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

v2.23.0 | Report a Bug | By Email