Re: [dispatch] Prorgessing draft-avasarala-dispatch-comm-div-notification-02

At the moment, I think those of us looking at this from the 3GPP way of doing things do not see a more general application of this.

I do not have a problem with doing it more generally, but I guess the people who see a clear use case for that need to speak up and identify their use cases. 

Otherwise we end up designing a general event package that no one else ever uses. As opposed to the alternative of clearly stating the restricted use to a particular applicability, approving it, and moving on to something else with our restricted amount of resources.

regards

Keith 

> -----Original Message-----
> From: dispatch-bounces@ietf.org 
> [mailto:dispatch-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
> Sent: Tuesday, February 09, 2010 9:16 AM
> To: DISPATCH
> Cc: Mary Barnes
> Subject: [dispatch] Prorgessing 
> draft-avasarala-dispatch-comm-div-notification-02
> 
> Hi,
> 
> there have been a set of messages on the list providing 
> comments on the draft below:
> 
> http://tools.ietf.org/html/draft-avasarala-dispatch-comm-div-n
> otification-02
> 
> As you know, the process for defining SIP event packages is 
> documented here:
> 
> http://tools.ietf.org/html/draft-peterson-rai-rfc3427bis-04#se
> ction-4.1
> 
> Based on the feedback received, the authors need to decide 
> whether they want to generalize their solution so that is is 
> generally applicable to the public Internet or if they want 
> to (further) clarify that this mechanism is intended to work 
> only in IMS networks that provide a CDIV service.
> 
> If the authors choose the latter approach, we (the DISPATCH 
> chairs) will choose a "Designated Expert" who will check the 
> draft against the 7 points described in the document above.
> 
> Cheers,
> 
> Gonzalo
> DISPATCH co-chair
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
> 