Dean,

So these milestone items we are late on, how many of them are late
because they are held up waiting for face-to-face discussion?

John 

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On 
> Behalf Of Dean Willis
> Sent: 18 July 2008 01:40
> To: Jonathan Rosenberg
> Cc: SIP IETF; Cullen Jennings
> Subject: Re: [Sip] Draft agenda, SIP at IETF 72
> 
> 
> On Jul 17, 2008, at 3:08 PM, Jonathan Rosenberg wrote:
> 
> > I would also suggest the same list. And in particular, if we don't  
> > make a lot of progress on INFO and rfc4474, we have wasted 
> our time.  
> > Those two IMHO should cover 75% of our meeting time. Having 
> a bunch  
> > of 10 minute presentations, each of which is on a topic that only  
> > three people care about, is not a good use of everyones 
> time. Those  
> > two topics clearly have big impact on SIP as a whole and are of  
> > broad interest.
> 
> I don't disagree. In fact, I think you are absolutely right.
> 
> But while they are within the scope of our charter, neither INFO nor  
> revision of RFC 4474 is a milestone on our charter. The other things  
> we currently have on the agenda (except "keep") ARE milestone items.  
> And we're LATE on most of them!
> 
> So either our charter is wrong, or we're out-of-scope in our 
> interests.
> 
> I've previously tried to charter deliverables on both items and been  
> shot down.
> 
> So what do you think we should do?
> 
> --
> Dean
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use [EMAIL PROTECTED] for questions on current sip
> Use [EMAIL PROTECTED] for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip

Reply via email to