[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Sip] refer-06 question
Assuming that you mean RFC3265, there are several contradictory answers.
I would like to suggest that refer-06 should be clearer on the subject.
It should describe what a minimal implementation is.
Patrick
Quoting hisham.khartabil@nokia.com:
> I guess it all depends on how you define "immediate" to mean. If its a
> matter of seconds, then I think its ok to send the one NOTIFY only.
>
> I quote RFC3165
>
> "Until the first NOTIFY message arrives, the subscriber
> should consider the state of the subscribed resource to be in a
> neutral state. Documents which define new event packages MUST
> define
> this "neutral state" in such a way that makes sense for their
> application (see section 4.4.7.)."
>
> Regards,
> Hisham
>
> > -----Original Message-----
> > From: ext Vijay S Kamath [mailto:vijay.kamath@wipro.com]
> > Sent: Friday, July 26, 2002 3:25 PM
> > To: patrick.mourot@online.fr
> > Cc: sip@ietf.org
> > Subject: RE: [Sip] refer-06 question
> >
> >
> > Patrick,
> >
> > You cannot delay the notification until the referenced
> > request completes.
> > Quoting Sec 2.4.4: "The creation of a subscription as defined
> > by [1] always results in an
> > immediate NOTIFY. "
> >
> > So I suggest you follow your second suggestion.
> >
> > Vijay
> >
> > -----Original Message-----
> > From: patrick.mourot@online.fr [mailto:patrick.mourot@online.fr]
> > Sent: Friday, July 26, 2002 5:24 PM
> > To: Vijay Kamath
> > Cc: sip@ietf.org
> > Subject: RE: [Sip] refer-06 question
> >
> >
> > vsk,
> >
> > Thanks for the answer.
> > I understand both cases; but this does not light my way.
> > Let me put it in other words.
> >
> > can i delay the notification until the referenced request
> > completes? leading to send only 1 notification???? (assuming
> > timers are OK).
> >
> > Or am i oblige to send a 1rst notification, wait for
> > completion of the
> > referenced request and send a final notification ?
> >
> > What is mandatory?
> >
> > Patrick
> >
> >
> > Quoting Vijay S Kamath <vijay.kamath@wipro.com>:
> >
> > > It can be either 1 or more, but at least 1.
> > > Qouting Section 2.4.7: "Each NOTIFY must contain a
> > Subscription-State
> > > header field as defined
> > > in [2]. The final NOTIFY sent in response to a REFER
> > MUST indicate
> > > the subscription has been "terminated" with a reason of
> > > "noresource"."
> > >
> > > The final NOTIFY can also be the first NOTIFY.
> > >
> > > Regards... Vijay
> > >
> > > -----Original Message-----
> > > From: patrick.mourot@online.fr [mailto:patrick.mourot@online.fr]
> > > Sent: Friday, July 26, 2002 2:48 PM
> > > To: sip@ietf.org
> > > Subject: [Sip] refer-06 question
> > >
> > >
> > > Sir,
> > >
> > >
> > > In 2.4.5 § of refer-06 draft It is stated that a "A minimal, but
> > > complete, implementation can respond with a single NOTIFY
> > containing
> > > either ...the
> > > body:
> > > SIP/2.0 200 OK if the reference was successful".
> > >
> > > It seems to be in contradiction with § 3.10 saying that
> > > "Alternatively, the subscription might only result in two NOTIFY
> > > requests, the immediate NOTIFY and
> > > the NOTIFY carrying the final result of the reference".
> > >
> > > Do we need 1 or 2 NOTIFY in a minimal implementation?
> > >
> > > Best Regards,
> > >
> > > Patrick
> > >
> > > _______________________________________________
> > > Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
> > > This list is for NEW development of the core SIP Protocol
> > > Use sip-implementors@cs.columbia.edu for questions on
> > current sip Use
> > > sipping@ietf.org for new developments on the application of sip
> > >
> >
> > _______________________________________________
> > Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> >
>
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip