[Sipping] Approval of draft-ietf-sipping-app-interaction-framework-05.txt
Allison Mankin <mankin@psg.com> Thu, 13 October 2005 18:41 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQ81Q-0000e3-Hu; Thu, 13 Oct 2005 14:41:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQ81O-0000dv-RV; Thu, 13 Oct 2005 14:41:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04601; Thu, 13 Oct 2005 14:41:38 -0400 (EDT)
Message-Id: <200510131841.OAA04601@ietf.org>
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQ8Bv-0003hb-4B; Thu, 13 Oct 2005 14:52:38 -0400
Received: from localhost ([127.0.0.1] helo=psg.com) by psg.com with esmtp (Exim 4.52 (FreeBSD)) id 1EQ81B-000P5b-V4; Thu, 13 Oct 2005 18:41:29 +0000
To: sipping@ietf.org
Date: Thu, 13 Oct 2005 11:41:29 -0700
From: Allison Mankin <mankin@psg.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: iesg@ietf.org, rohan@ekabal.com, gonzalo.camarillo@ericsson.com, dean.willis@softarmor.com
Subject: [Sipping] Approval of draft-ietf-sipping-app-interaction-framework-05.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mankin@psg.com
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
Hi, all, The IESG approved draft-ietf-sipping-app-interaction-framework-05.txt today. As is laid out in RFC 2026 (in 6.1.2), the IESG occasionally changes the intended status of a document during its review. In this case, we saw a document that looked strongly like an interoperable protocol specification and not so much like any of the RFC 2026 definitions of a BCP. The change from BCP to Proposed Standard does not need any process, so the approval was changed to be for Proposed Standard. This will also be mentioned in text in the approval announcement. Thanks, and congratulations for the excellent document, which has been awaited for a long while! Allison _______________________________________________ Sipping mailing list https://www1.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
- [Sipping] Approval of draft-ietf-sipping-app-inte… Allison Mankin
- Re: [Sipping] Approval of draft-ietf-sipping-app-… Jonathan Rosenberg