Re: [dispatch] SIP Action Referral

Hi Paul,

Thanks for reviewing the document and providing us with your feedback.
See my comments inline...

Regards,
 Rifaat

> -----Original Message-----
> From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On Behalf
> Of Paul Kyzivat
> Sent: Saturday, January 15, 2011 10:59 PM
> To: dispatch@ietf.org
> Subject: Re: [dispatch] SIP Action Referral
> 
> 
> 
> On 1/14/2011 1:41 PM, Shekh-Yusef, Rifaat (Rifaat) wrote:
> > Hi,
> >
> > We have submitted the following SIP Action Referral draft to the IETF and we
> would like to discuss it during the upcoming DISPATCH meeting in IETF80.
> > https://datatracker.ietf.org/doc/draft-yusef-dispatch-action-ref/
> > A charter proposal will follow by the end of next week.
> >
> > We would appreciate any comments or feedback on this draft.
> 
> This seems pretty interesting.
> 
> Some of it seems relatively reasonable and straightforward.
> 
> I am a little concerned that the space of actions that might be
> controlled in this way is largely unbounded - the beginning of an
> enumeration of telephony features. But maybe not.

[Rifaat] For that reason we are stating that for any new action to be added there is a need for an IETF review.

> 
> A couple of pieces seem to be addons/afterthoughts that aren't well
> integrated:
> 
> 3.2.  Loosely Coupled UAs
> 3.3.2.  Answer an A/V call on two separate devices
> 
> I note that the function used in 3.3.2 is not mentioned in the
> enumeration of actions included in section 4.2.
> 
[Rifaat] Good catch. Thanks.

> This feature seems to raise more questions than it answers.
> Specifically, a one time delivery of audio answer SDP from the phone to
> the PC hardly seems like enough to make this work. What would happen on
> subsequent reinvite-o/a interactions between bob and alice? How long
> should the phone keep the audio active, in the absence of a real
> signaling session to control it? I suppose that the PC can send
> additional REFERs to the phone, but then there will be no dialog to
> refer to.
> 
> Maybe this could be developed, but there is a lot more to say to make
> this work. But ISTM when this is worked out there will have to be a sip
> dialog with the phone, perhaps from the PC.

[Rifaat] One way to address your concern here is to keep the dialog created by the REFER request open.
But Yes, I agree that there is more work to be done on this use case.

> 
> 	Thanks,
> 	Paul
> 
> 
> > Thanks,
> >   Rifaat
> >
> >
> > -----Original Message-----
> > From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> > Sent: Friday, January 14, 2011 8:15 AM
> > To: Shekh-Yusef, Rifaat (Rifaat)
> > Cc: fluffy@cisco.com; alan.b.johnston@gmail.com; francois.audet@skype.net
> > Subject: New Version Notification for draft-yusef-dispatch-action-ref-00
> >
> >
> > A new version of I-D, draft-yusef-dispatch-action-ref-00.txt has been
> successfully submitted by Rifaat Shekh-Yusef and posted to the IETF
> repository.
> >
> > Filename:	 draft-yusef-dispatch-action-ref
> > Revision:	 00
> > Title:		 Action Referral in the Session Initiation Protocol (SIP)
> > Creation_date:	 2011-01-14
> > WG ID:		 Independent Submission
> > Number_of_pages: 24
> >
> > Abstract:
> > This specification defines action referral that allows an application
> > to make a high level request to a User Agent to perform an action,
> > and let the the User Agent execute the action as it sees fit. Action
> > referral uses the SIP REFER method with a Refer-To header field
> > containing a URN, which indicates the requested action.
> >
> > This specification also defines the option tag 'action-ref' to allow
> > the UA to indicate its support for action referral.
> >
> >
> >
> > The IETF Secretariat.
> >
> >
> > _______________________________________________
> > dispatch mailing list
> > dispatch@ietf.org
> > https://www.ietf.org/mailman/listinfo/dispatch
> >
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch