Subject: [siprec] Scope of metadata model draft and its relationship to protocol draft

From: "Elwell, John" <[email-masked]>
Date: Thu, 20 Jan 2011 09:17:35 +0100

Ram,

The title and introduction of the metadata model draft suggest it is limited to specification of the model. In addition to that, we will need to specify how the model is encoded for transport, and how it is transported. It looks like transport will be covered by the protocol draft, but this still leaves encoding. I would imagine we might want an XML schema, for example. Would this eventually be part of the metadata model draft? I understand there are still issues as to which metadata is already covered by existing SIP/SDP elements and which needs to be conveyed explicitly as metadata, so it might be too early to develop the schema yet, but it would be good to have a plan on how the documentation will link together.

On the assumption that transport is to be covered in the protocol draft, there are a few normative statements in the metadata model draft that might be out of place. For example:

- "The Session Recording Client (SRC) MAY
   initiate the Recording Session."
- "The metadata MUST be conveyed from SRC to SRS."
- "The metadata MAY be conveyed in Recording Session Dialog."
- "It is RECOMMENDED that a SRC authenticate SRS using the normal SIP
   authentication mechanisms"
- and in fact the whole of 6.1 possibly doesn't belong in this document.

John (as individual)