Thanks.
Between in RFC 2327 says,
o Extension Mechanism: Tool writers can define experimental bandwidth
modifiers by prefixing their modifier with "X-".
And, somwhere i saw the following (forgot the source),
b=X-D:<delay in miliseconds> is needed for exchanging the delay
requirements.
So, it means, we can send Delay too. Is that the Delay during RTP ?
On Thu, Feb 25, 2010 at 12:36 PM, Kamalakanta Palei (kpalei) <
[email protected]> wrote:
>
> Please see the response in line.
>
> Kamal
> Cisco, Bangalore
> India
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of
> Premalatha Kuppan
> Sent: Thursday, February 25, 2010 12:25 PM
> To: [email protected]
> Subject: Re: [Sip-implementors] QoS paramters
>
> My question is in addition to Bandwidth, whether other QOS parameters
> like Jitter, Delay, throught, etc can be carried ?
> [Kamal] No , and not required.
>
> Jitter, delay will come into picture, during RTP. But is there an option
> to mention these QOS parameters during session establishment itself.
> [Kamal] No.
>
>
> On Thu, Feb 25, 2010 at 12:20 PM, Kamalakanta Palei (kpalei) <
> [email protected]> wrote:
>
> >
> > Not very clear about the question you are asking.
> >
> > Here the precondition needs to be met means , it need to be ensured
> > that there is bandwidth for media flow. If bandwidth is there, it will
>
> > be reserved for this call and then the destination endpoint alerts
> > user (phone rings).
> >
> > In addition to qos there are other preconditions like
> > security-precondition , but its not the topic of interest.
> >
> > Thanks
> > Kamal
> > Cisco, Bangalore
> > India
> >
> > -----Original Message-----
> > From: [email protected]
> > [mailto:[email protected]] On Behalf Of
> > Premalatha Kuppan
> > Sent: Thursday, February 25, 2010 11:39 AM
> > To: [email protected]
> > Subject: Re: [Sip-implementors] QoS paramters
> >
> > Continuation of my prev thread:
> >
> > The RFC 3312, says about Current, desired status , strength tag etc..
> > but this to ensure that session should be established only when the
> > pre-conditions are met by both end.
> >
> > But what all the Pre-conditions, still its not clear to me.
> >
> > I appreciate your help.
> >
> > On Thu, Feb 25, 2010 at 11:35 AM, Premalatha Kuppan <
> > [email protected]> wrote:
> >
> > > As you said, Jitter and Delay are related to RTP.
> > >
> > > But QOS is for Media (audio/Video) right ? During session
> > > establishment, there is an option to send the BW in SDP, likewise is
>
> > > there any other parameters to carry other QOS parameters (like
> > > jitter,
> >
> > > delay, throughput etc...).
> > >
> > > Because, the draft says,
> > >
> > > a=curr:qos e2e send
> > > a=des:qos optional e2e send
> > > a=des:qos mandatory e2e recv
> > >
> > >
> > >
> > > Also RFC 3312 says, Precondition defined for QOS and there would be
> > > a local status table and transaction status table. But i couldn't
> > > understand what exactly value or QOS related parameters would be
> > > there
> > in those tables.
> > > SInce its at UA, each UA can have different QOS capabilities (!?).
> > >
> > > Correct me if iam wrong.
> > >
> > >
> > >
> > > On Thu, Feb 25, 2010 at 10:14 AM, Avasarala Ranjit-A20990 <
> > > [email protected]> wrote:
> > >
> > >>
> > >> The jitter and delay are related to RTP. So a SDP that is part of
> > >> SIP
> >
> > >> INVITE cannot send them.
> > >>
> > >>
> > >> Regards
> > >> Ranjit
> > >>
> > >> -----Original Message-----
> > >> From: [email protected]
> > >> [mailto:[email protected]] On Behalf
> > >> Of Kamalakanta Palei (kpalei)
> > >> Sent: Thursday, February 25, 2010 7:45 AM
> > >> To: Premalatha Kuppan; [email protected]
> > >> Subject: Re: [Sip-implementors] QoS paramters
> > >>
> > >>
> > >> I have not seen jitter and delay parameters in SDP.
> > >>
> > >> Thanks
> > >> Kamal
> > >> Cisco, Bangalore
> > >> India
> > >>
> > >> -----Original Message-----
> > >> From: [email protected]
> > >> [mailto:[email protected]] On Behalf
> > >> Of Premalatha Kuppan
> > >> Sent: Wednesday, February 24, 2010 11:19 PM
> > >> To: [email protected]
> > >> Subject: Re: [Sip-implementors] QoS paramters
> > >>
> > >> Thanks.
> > >>
> > >> Between, regarding precondition on QOS, i read the RFC 3312. But
> > >> still not clear whether the UA sends other QOS parameters like
> > >> jitter, Delay other than BW.
> > >>
> > >> If someone brief it, it would be good.
> > >>
> > >> On Wed, Feb 24, 2010 at 7:24 PM, Kamalakanta Palei (kpalei) <
> > >> [email protected]> wrote:
> > >>
> > >> > Hi Prem
> > >> > You can explore more on below SDP. That will give better
> > >> > understanding
> > >>
> > >> > on precondition QoS.
> > >> >
> > >> > m=video 3400 RTP/AVP 98 99
> > >> > b=AS:75
> > >> > a=curr:qos local none
> > >> > a=curr:qos remote none
> > >> > a=des:qos mandatory local sendrecv a=des:qos none remote sendrecv
> > >> >
> > >> > Thanks
> > >> > Kamal
> > >> > Cisco, Bangalore
> > >> > India
> > >> >
> > >> > -----Original Message-----
> > >> > From: [email protected]
> > >> > [mailto:[email protected]] On Behalf
>
> > >> > Of Bharat S
> > >> > Sent: Wednesday, February 24, 2010 10:25 AM
> > >> > To: Premalatha Kuppan; [email protected]
> > >> > Subject: Re: [Sip-implementors] QoS paramters
> > >> >
> > >> > RFC 3312 explains the SDP Preconditions mechanism that allows UE
> > >> > to
> >
> > >> > delay completion of a SIP session establishment until one or both
>
> > >> > sides have successfully completed their resource reservation.
> > >> >
> > >> > IETF has defined the precondition-type "qos".
> > >> >
> > >> > -Bharat
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > ________________________________
> > >> > From: Premalatha Kuppan <[email protected]>
> > >> > To: [email protected]
> > >> > Sent: Tue, February 23, 2010 3:30:38 PM
> > >> > Subject: [Sip-implementors] QoS paramters
> > >> >
> > >> > Hi,
> > >> >
> > >> > Please tell me what are all the QOS related paramters carried in
>
> > >> > SIP/SDP (both in answer and offer).
> > >> >
> > >> > Thanks,
> > >> > Prem
> > >> > _______________________________________________
> > >> > Sip-implementors mailing list
> > >> > [email protected]
> > >> > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > _______________________________________________
> > >> > Sip-implementors mailing list
> > >> > [email protected]
> > >> > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> > >> >
> > >> _______________________________________________
> > >> Sip-implementors mailing list
> > >> [email protected]
> > >> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> > >>
> > >> _______________________________________________
> > >> Sip-implementors mailing list
> > >> [email protected]
> > >> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> > >>
> > >
> > >
> > _______________________________________________
> > Sip-implementors mailing list
> > [email protected]
> > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> >
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
