Skip to main content

SIMPLE Made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence Using the Session Initiation Protocol (SIP)
draft-ietf-simple-simple-09

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>,
    simple mailing list <simple@ietf.org>,
    simple chair <simple-chairs@tools.ietf.org>
Subject: Document Action: 'SIMPLE made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence using the Session Initiation Protocol (SIP)' to Informational RFC (draft-ietf-simple-simple-09.txt)

The IESG has approved the following document:
- 'SIMPLE made Simple: An Overview of the IETF Specifications for Instant
   Messaging and Presence using the Session Initiation Protocol (SIP)'
  (draft-ietf-simple-simple-09.txt) as Informational RFC

This document is the product of the SIP for Instant Messaging and
Presence Leveraging Extensions Working Group.

The IESG contact persons are Robert Sparks and Gonzalo Camarillo.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-simple-simple/


Ballot Text

Technical Summary

The IETF has produced many specifications related to Presence and Instant Messaging with the Session Initiation Protocol (SIP). Collectively, these specifications are known as SIMPLE - SIP for Instant Messaging and Presence Leveraging Extensions.  This document serves as a guide to the SIMPLE suite of specifications.  It breaks them up into categories and explains what each is for and how they relate to each other.

Working Group Summary

This document servers as a roadmap to the SIMPLE specifications. It introduces no technical content beyond the summaries of those specifications. While some of the referenced specifications had some degree of controversy, this draft was not controversial in itself.

Document Quality.

This document is a roadmap to other specifications, and therefore has no directly implementable content. The document has undergone normal working group review. There have been no specialized expert reviews, and the shepherd does not believe such reviews are needed, other than those normal for all documents (e.g. Gen-ART).

Personnel

The document shepherd for this document is Ben Campbell.

The responsible Area Director is Robert Sparks. 

RFC Editor Note