Re: [siprec] draft-ram-siprec-callflows-01

["Parthasarathi R" <[e-mail]>]

Hi Ofir,

 

Thanks for the review. Please read inline.

 

Thanks

Partha

 

From: Ofir Roth [mailto:[e-mail]] 
Sent: Saturday, October 20, 2012 12:36 AM
To: Parthasarathi R; [e-mail]
Subject: RE: [siprec] draft-ram-siprec-callflows-01

 

Hi,

 

According to the metadata scheme: 

 

<xs:complexType name="participant">

       <xs:sequence>

           <xs:element name="nameID" type="nameID"

             maxOccurs="1"/>

        <xs:any namespace='##other'

                   minOccurs='0'

                   maxOccurs='unbounded'

                   processContents='lax'/>

       </xs:sequence>

       <xs:attribute name="participant_id" type="xs:base64Binary"

            use="required"/>

       <xs:attribute name="session_id" type="xs:base64Binary"

            use="required"/>

   </xs:complexType>

There is no associate/disassociate time as part of the participant
definition while it appears in the call flow example of section 4.5.

<Partha> This is callflow document issue and the actual XML element is
participantsessionassoc. This is updated in -02 callflow draft </Partha>

 

And session is defined as follow:

 

<xs:complexType name="session">

       <xs:sequence>

         <xs:element name="reason" type="xs:string"

                minOccurs="0"/>

         <xs:element name="group-ref" type="xs:base64Binary"

                minOccurs="0" maxOccurs="1"/>

           <xs:any namespace='##other'

                   minOccurs='0'

                   maxOccurs='unbounded'

                   processContents='lax'/>

       </xs:sequence>

       <xs:attribute name="session_id" type="xs:base64Binary"

            use="required"/>

   </xs:complexType>

 

According to the session definition, session does not contain start/stop
time while it appears in call flow document. 

<Partha> This issue is related to XML schema in Metadata draft and has to be
fixed in the next revision as 

There was consensus to add start/stop time as part of the session element
</Partha>

 

I am interested which is the up to date version that should be used (call
flow or metadata scheme).

 

Thanks,
Ofir.

 

From: Parthasarathi R [mailto:[e-mail]] 
Sent: Wednesday, October 17, 2012 5:28 PM
To: Ofir Roth; [e-mail]
Subject: RE: [siprec] draft-ram-siprec-callflows-01

 

Hi Ofir,

 

Thanks for your review. Please read inline.

 

Thanks

Partha

 

From: [e-mail] [mailto:[e-mail]] On Behalf Of
Ofir Roth
Sent: Wednesday, October 17, 2012 4:46 PM
To: [e-mail]
Subject: [siprec] draft-ram-siprec-callflows-01

 

Hello,

 

I am reviewing the examples provided in draft-ram-siprec-callflows-01 and
noticed that it is not aligned according to draft-ietf-siprec-metadata-07. 

 

For example: 

 

1.       Session element does not contain start/stop time

<Partha> I guess that you wish to see the example with start/stop time. We
will add in the

 next revision. 

  

BTW,start/stop time are optional elements in session.  So, the callflow is 

inline with metadata -07 draft. 

 

</Partha>

 

2.       Participant does not include disassociate-time (as in section 4.5)

<Partha> Sec 4.5 is call disconnect example and so, disassociate-time
exists. Please let me know the exact location where disassociate-time is
missing. </Partha>

 

If those are known issues, I will appreciate if someone can let me know. 

 

Thanks,
Ofir.