Agenda time in Dublin..... !!!!  

Sam 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
James M. Polk
Sent: Tuesday, April 01, 2008 4:01 PM
To: Paul Kyzivat; Dan York
Cc: [email protected]; Bob Penfield
Subject: Re: [Sip] Enjoyable read... Re: I-D Action:
draft-kaplan-sip-four-oh-00.txt

At 01:29 PM 4/1/2008, Paul Kyzivat wrote:
>humor?
>
>I'm looking forward to cleaning up the details and getting this 
>approved. Its about time we moved on.

last nit - it needs to explicitly deprecate all currently standardized
headers by name (not just whimically mention "all others present and
future are no good anymore") to reduce the last bits of potential
confusion by readers - and I think this doc is done.

Who's gonna call for consensus on it?


>         Paul
>
>Dan York wrote:
> > Hadriel,
> >
> > Nice piece of work that you and Bob did!   I laughed quite a good
bit
> > throughout.
> >
> > Thanks for injecting some humor here, Dan
> >
> > On Apr 1, 2008, at 3:15 AM, Hadriel Kaplan wrote:
> >> Greetings,
> >> Given today's relative importance in history - being the date Swiss

> >> farmers had their largest spaghetti crop harvest, Sweden introduced

> >> color television, the USSR connected Kremvax to Usenet, the Alabama

> >> state government changed the value of Pi to 3.0, and much more - we

> >> took it upon ourselves to write up and submit a new Internet-Draft 
> >> for an update to RFC 3261 (and a bunch of other RFCs): P2P2PSIP,
a.k.a.
> >> SIP v4.0.
> >>
> >> A URL for this Internet-Draft is:
> >> http://www.ietf.org/internet-drafts/draft-kaplan-sip-four-oh-00.txt
> >>
> >> Abstract:
> >> This document defines a new and improved version of SIP, which 
> >> tastes great and is less filling than the previous SIP.  This draft

> >> updates all previous and future RFCs related to SIP in SIPPING, 
> >> SIMPLE, MMUSIC, BEHAVE, and so on.
> >>
> >> -hadriel
> >> p.s. I apologize for the length of it - it was only 41 pages long 
> >> originally, but my co-author demanded it be expanded to 42 pages 
> >> (for obvious reasons), and thus it's a bit bloated.
> >>
> >> _______________________________________________
> >> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> >> This list is for NEW development of the core SIP Protocol Use 
> >> [EMAIL PROTECTED] 
> >> <mailto:[EMAIL PROTECTED]> for questions on current 
> >> sip Use [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> for new 
> >> developments on the application of sip
> >
> > --
> > Dan York, CISSP, Director of Emerging Communication Technology
> > Office of the CTO    Voxeo Corporation     [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>
> > Phone: +1-407-455-5859  Skype: danyork  http://www.voxeo.com
> > Blogs: http://blogs.voxeo.com  http://www.disruptivetelephony.com
> >
> > Build voice applications based on open standards.
> > Find out how at http://www.voxeo.com/free
> >
> >
> >
> >
> >
> >
> > --------------------------------------------------------------------
> > ----
> >
> > _______________________________________________
> > 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

_______________________________________________
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