From c78c3f362bec6b183298155a1a1e30d382ef0b14 Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre <stpeter@jabber.org>
Date: Mon, 20 Oct 2008 19:16:10 +0000
Subject: [PATCH] clarified content disposition in session-initiate

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2411 4b5297f7-1745-476d-ba37-a9c6900126ab
---
 xep-0166.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xep-0166.xml b/xep-0166.xml
index dcf76b1a..12942951 100644
--- a/xep-0166.xml
+++ b/xep-0166.xml
@@ -946,7 +946,7 @@ PENDING  o----------------------+   |
       <p>The <strong>session-info</strong> action is used to send session-level information, such as (for Jingle RTP sessions) a ringing message.</p>
     </section3>
     <section3 topic='session-initiate' anchor='def-action-session-initiate'>
-      <p>The <strong>session-initiate</strong> action is used to request negotiation of a new Jingle session.</p>
+      <p>The <strong>session-initiate</strong> action is used to request negotiation of a new Jingle session. When sending a session-initiate, the value of the &CONTENT; element's 'disposition' attribute MUST be "session" (to be precise, if there are multiple &CONTENT; elements then at least one MUST have a disposition of "session"); if this rule is violated, the responder MUST return a &badrequest; error to the initiator.</p>
     </section3>
     <section3 topic='session-terminate' anchor='def-action-session-terminate'>
       <p>The <strong>session-terminate</strong> action is used to end an existing session.</p>