> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On 
> Behalf Of Dean Willis
> Sent: Tuesday, June 24, 2008 3:38 PM
> To: Elwell, John
> Cc: [email protected]; Keith Drage
> Subject: Re: [Sip] Let's talk about a Dublin agenda
> 
> 
> On Jun 24, 2008, at 3:17 PM, Elwell, John wrote:
> 
> >>
> >>
> >> 2) For the remainder, I'd like to suggest the "REal Time
> >> Identity and
> >> Role Expression" (RETIRE) Working Group, which would take
> >> over the RFC
> >> 4474 revision along with SIP-SAML.
> > [JRE] Will that produce results before we all retire? But 
> seriously, a
> > new WG might be a good idea, but how long to set it up? What needs  
> > to be
> > done at or before Dublin in that direction?
> 
> Well, a new working group starts with a BOF request and a draft  
> charter and somebody who wants the WG badly enough to do the 
> leg work and chair the BOF.

You say that as if nobody tried before.  I requested a BoF for
Philadelphia, called Discussion and Analysis of SIP Identity 
(DASI).  It was turned down by the IESG, and did not have the
support of the RAI ADs.

I have received no indication that additional people in SIP cared 
about the problem (beyond the ~6 or so involved in the thread we
had on the list), nor an indication from the RAI ADs that our email 
threads on SIP after the Philadelphia meeting had swayed their 
opinion.

I could continue to beat my head against the wall, but I can't
see through the blood as it is.

> It's a little late in the cycle to get one of those in for 
> Dublin, but we could certainly start talking about a draft 
> charter, then run a BOF at the next meeting.  That would fit 
> squarely with my goal of ramping down the "eternal SIP group" 
> by fall 2009.

-d

_______________________________________________
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