Subject: [Insipid] 3.X Identifier Porting to Other Protocols – RSVP: evaluation

From: James Polk <[email-masked]>
Date: Mon, 27 Aug 2012 18:24:06 -0500

INSIPID

Here is the set of use-cases and requirements 
discussed in Vancouver. We are to come to 
consensus on each of these (or not), and if we 
agree the use-case or requirement should be in 
the document, we need to determine acceptable 
wording for each. The Subject: line will contain 
the specific topic (which use-case or 
requirement) for this thread. PLEASE do not cross 
contaminate the threads. Any new topic SHOULD 
have its own Subject line. The chairs will 
monitor and call for consensus on each use-case 
and requirement (and wording of each).

Please make constructive suggestions regarding each you care about.

The Section numbers will be reordered once 
consensus has been reached on all items we're 
covering, so don't worry about that part.

3.X Identifier Porting to Other Protocols – RSVP:

There may be a desire to associate SIP session 
signaling with corresponding media flows.  To 
facilitate this association, it should be 
possible to insert the Session-ID into a 
media-related message, such as an RSVP PATH 
message.  This association would allow, as an 
example, for network monitoring equipment to 
associate troubled network flows with the end-to-end SIP session signaling.

Derived Requirements: REQ9b

WG consensus in room was to deprecate this 
use-case, and the requirement REQ9b.