Re: I-D Action: draft-ietf-simple-simple-08.txt
Jonathan Rosenberg <[email protected]> Sat, 16 Feb 2013 07:37:19 -0500
| Newsgroups | gmane.ietf.simple |
|---|---|
| Message-ID | <CA+23+fEde+VmvHr-X-Um1ae5_Lj9qwnP+ngHGmC2cTgZ_URCAA@mail.gmail.com> |
--===============0323049995001990100== Content-Type: multipart/alternative; boundary=f46d04428f18ba944a04d5d6c029 --f46d04428f18ba944a04d5d6c029 Content-Type: text/plain; charset=ISO-8859-1 Olle, I agree with Ben's assessment above. When we started this draft, we decided on a fairly hard definition around scope of what is included, and what is not. We purposely are not including the many SIP extensions that apply in general to SIP, including presence. As such, I do not think we should include rfc6072 or 5922. Similarly I dont think a section on xcap (useful as it might be) belongs here. I look forward to seeing your draft ;) Thanks, Jonathan R. On Wed, Jan 30, 2013 at 1:56 PM, Ben Campbell <[email protected]> wrote: > (as chair) > > Robert has asked us to progress this as soon as possible. I plan to go > ahead and do that for the existing version. > > That does _not_ mean we should ignore feedback, nor should we shut down > this discussion. We will just treat any further comments and discussion as > if they were IETF Last Call comments. > > Thanks! > > Ben. > > On Jan 30, 2013, at 1:49 AM, Olle E Johanson <[email protected]> wrote: > > > > > 29 jan 2013 kl. 15:17 skrev Ben Campbell <[email protected]>: > > > >> (as chair) > >> > >> We had a WGLC on version 06 of draft-ietf-simple-simple some time (as > in years) ago. It's been on hold since then to allow the other SIMPLE work > to substantially complete. Since our penultimate milestone (simple-chat) > has recently been approved by the IESG, it's time to progress simple-simple > and complete our final chartered milestone. > >> > >> The only non-trivial change between 06 and 08 was the split of the > entry for the old msrp-acm draft into separate entries for RFC 6135 > (COMEDIA for MSRP) and RFC 6174 (CEMA), to account for the split of that > draft. > >> > >> After conferring with the author and our AD, I think these changes are > pretty obvious and not likely to be controversial. Therefore we plan to > request publication of version 08. If anyone objects to that course of > action, please speak up asap. > > > > Ok, I know I had years to make a comment, but anyway :-) > > > > I would like to see references to the SIP domain certificate > specification, as it plays a role for implementors, as well as the SIP > certificate management service. These should be important for anyone > building SIMPLE implementations and adds some missing pieces in the SIMPLE > specs. > > > > - RFC 6072 Certificate Maangement Service for Session Initiation Protocol > > http://tools.ietf.org/html/rfc6072 > > - RFC 5922 Domain Certificates in the Session Initiation Protocol > > http://tools.ietf.org/html/rfc5922 > > > > Maybe we could add a clarification for newbies that "The SIP > subscribe/notify mechanism is not only used in SIMPLE, but also in other > event packages outside of the scope of this document." > > > > > > I could possibly also add a section about the missing interoperability > in presence/XCAP implementations but that propably won't help this > particular document that I find has a lot of value. > > > > See you all at SIPit 30! Only a few days of registration open - so > please hurry to http://www.sipit.net and register! > > /O > > > >> > >> Thanks! > >> > >> Ben. > >> > >>> From: [email protected] > >>> Subject: [Simple] I-D Action: draft-ietf-simple-simple-08.txt > >>> Date: January 28, 2013 6:44:53 PM CST > >>> To: [email protected] > >>> Cc: [email protected] > >>> > >>> > >>> A New Internet-Draft is available from the on-line Internet-Drafts > directories. > >>> This draft is a work item of the SIP for Instant Messaging and > Presence Leveraging Extensions Working Group of the IETF. > >>> > >>> Title : SIMPLE made Simple: An Overview of the IETF > Specifications for Instant Messaging and Presence using the Session > Initiation Protocol (SIP) > >>> Author(s) : Jonathan Rosenberg > >>> Filename : draft-ietf-simple-simple-08.txt > >>> Pages : 15 > >>> Date : 2013-01-28 > >>> > >>> Abstract: > >>> The IETF has produced many specifications related to Presence and > >>> Instant Messaging with the Session Initiation Protocol (SIP). > >>> Collectively, these specifications are known as SIMPLE - SIP for > >>> Instant Messaging and Presence Leveraging Extensions. This document > >>> serves as a guide to the SIMPLE suite of specifications. It breaks > >>> them up into categories and explains what each is for and how they > >>> relate to each other. > >>> > >>> > >>> The IETF datatracker status page for this draft is: > >>> https://datatracker.ietf.org/doc/draft-ietf-simple-simple > >>> > >>> There's also a htmlized version available at: > >>> http://tools.ietf.org/html/draft-ietf-simple-simple-08 > >>> > >>> A diff from the previous version is available at: > >>> http://www.ietf.org/rfcdiff?url2=draft-ietf-simple-simple-08 > >>> > >>> > >>> Internet-Drafts are also available by anonymous FTP at: > >>> ftp://ftp.ietf.org/internet-drafts/ > >>> > >>> _______________________________________________ > >>> Simple mailing list > >>> [email protected] > >>> https://www.ietf.org/mailman/listinfo/simple > >> > >> _______________________________________________ > >> Simple mailing list > >> [email protected] > >> https://www.ietf.org/mailman/listinfo/simple > > > > -- Jonathan Rosenberg, Ph.D. [email protected] http://www.jdrosen.net --f46d04428f18ba944a04d5d6c029 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Olle,<div><br></div><div style>I agree with Ben's asse= ssment above. When we started this draft, we decided on a fairly hard defin= ition around scope of what is included, and what is not. We purposely are n= ot including the many SIP extensions that apply in general to SIP, includin= g presence. As such, I do not think we should include rfc6072 or 5922. Simi= larly I dont think a section on xcap (useful as it might be) belongs here. = I look forward to seeing your draft ;)</div> <div style><br></div><div style>Thanks,</div><div style>Jonathan R.</div><d= iv style><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"g= mail_quote">On Wed, Jan 30, 2013 at 1:56 PM, Ben Campbell <span dir=3D"ltr"= ><<a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</= a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex">(as chair)<br> <br> Robert has asked us to progress this as soon as possible. I plan to go ahea= d and do that for the existing version.<br> <br> That does _not_ mean we should ignore feedback, nor should we shut down thi= s discussion. We will just treat any further comments and discussion as if = they were IETF Last Call comments.<br> <br> Thanks!<br> <span class=3D"HOEnZb"><font color=3D"#888888"><br> Ben.<br> </font></span><div class=3D"im HOEnZb"><br> On Jan 30, 2013, at 1:49 AM, Olle E Johanson <<a href=3D"mailto:oej@edvi= na.net">[email protected]</a>> wrote:<br> <br> ><br> </div><div class=3D"HOEnZb"><div class=3D"h5">> 29 jan 2013 kl. 15:17 sk= rev Ben Campbell <<a href=3D"mailto:[email protected]">[email protected]</a>= >:<br> ><br> >> (as chair)<br> >><br> >> We had a WGLC on version 06 of draft-ietf-simple-simple some time = (as in years) ago. It's been on hold since then to allow the other SIMP= LE work to substantially complete. Since our penultimate milestone (simple-= chat) has recently been approved by the IESG, it's time to progress sim= ple-simple and complete our final chartered milestone.<br> >><br> >> The only non-trivial change between 06 and 08 was the split of the= entry for the old msrp-acm draft into separate entries for RFC 6135 (COMED= IA for MSRP) and RFC 6174 (CEMA), to account for the split of that draft.<b= r> >><br> >> After conferring with the author and our AD, I think these changes= are pretty obvious and not likely to be controversial. Therefore we plan t= o request publication of version 08. If anyone objects to that course of ac= tion, please speak up asap.<br> ><br> > Ok, I know I had years to make a comment, but anyway :-)<br> ><br> > I would like to see references to the SIP domain certificate specifica= tion, as it plays a role for implementors, as well as the SIP certificate m= anagement service. These should be important for anyone building SIMPLE imp= lementations and adds some missing pieces in the SIMPLE specs.<br> ><br> > - RFC 6072 Certificate Maangement Service for Session Initiation Proto= col<br> > =A0 <a href=3D"http://tools.ietf.org/html/rfc6072" target=3D"_blank">h= ttp://tools.ietf.org/html/rfc6072</a><br> > - RFC 5922 Domain Certificates in the Session Initiation Protocol<br> > =A0<a href=3D"http://tools.ietf.org/html/rfc5922" target=3D"_blank">ht= tp://tools.ietf.org/html/rfc5922</a><br> ><br> > Maybe we could add a clarification for newbies that "The SIP subs= cribe/notify mechanism is not only used in SIMPLE, but also in other event = packages outside of the scope of this document."<br> ><br> ><br> > I could possibly also add a section about the missing interoperability= in presence/XCAP implementations but that propably won't help this par= ticular document that I find has a lot of value.<br> ><br> > See you all at SIPit 30! Only a few days of registration open - so ple= ase hurry to <a href=3D"http://www.sipit.net" target=3D"_blank">http://www.= sipit.net</a> and register!<br> > /O<br> ><br> >><br> >> Thanks!<br> >><br> >> Ben.<br> >><br> >>> From: <a href=3D"mailto:[email protected]">internet-dra= [email protected]</a><br> >>> Subject: [Simple] I-D Action: draft-ietf-simple-simple-08.txt<= br> >>> Date: January 28, 2013 6:44:53 PM CST<br> >>> To: <a href=3D"mailto:[email protected]">i-d-announce@ietf= .org</a><br> >>> Cc: <a href=3D"mailto:[email protected]">[email protected]</a><br> >>><br> >>><br> >>> A New Internet-Draft is available from the on-line Internet-Dr= afts directories.<br> >>> This draft is a work item of the SIP for Instant Messaging and= Presence Leveraging Extensions Working Group of the IETF.<br> >>><br> >>> =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : SIMPLE made Simple: An Ove= rview of the IETF Specifications for Instant Messaging and Presence using t= he Session Initiation Protocol (SIP)<br> >>> =A0 =A0 Author(s) =A0 =A0 =A0 : Jonathan Rosenberg<br> >>> =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-simple-simple-08.= txt<br> >>> =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 15<br> >>> =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2013-01-28<br> >>><br> >>> Abstract:<br> >>> The IETF has produced many specifications related to Presence = and<br> >>> Instant Messaging with the Session Initiation Protocol (SIP).<= br> >>> Collectively, these specifications are known as SIMPLE - SIP f= or<br> >>> Instant Messaging and Presence Leveraging Extensions. =A0This = document<br> >>> serves as a guide to the SIMPLE suite of specifications. =A0It= breaks<br> >>> them up into categories and explains what each is for and how = they<br> >>> relate to each other.<br> >>><br> >>><br> >>> The IETF datatracker status page for this draft is:<br> >>> <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-simple-= simple" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-simpl= e-simple</a><br> >>><br> >>> There's also a htmlized version available at:<br> >>> <a href=3D"http://tools.ietf.org/html/draft-ietf-simple-simple= -08" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-simple-simple-= 08</a><br> >>><br> >>> A diff from the previous version is available at:<br> >>> <a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-simpl= e-simple-08" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-iet= f-simple-simple-08</a><br> >>><br> >>><br> >>> Internet-Drafts are also available by anonymous FTP at:<br> >>> <a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_bla= nk">ftp://ftp.ietf.org/internet-drafts/</a><br> >>><br> >>> _______________________________________________<br> >>> Simple mailing list<br> >>> <a href=3D"mailto:[email protected]">[email protected]</a><br> >>> <a href=3D"https://www.ietf.org/mailman/listinfo/simple" targe= t=3D"_blank">https://www.ietf.org/mailman/listinfo/simple</a><br> >><br> >> _______________________________________________<br> >> Simple mailing list<br> >> <a href=3D"mailto:[email protected]">[email protected]</a><br> >> <a href=3D"https://www.ietf.org/mailman/listinfo/simple" target=3D= "_blank">https://www.ietf.org/mailman/listinfo/simple</a><br> ><br> <br> </div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>= <div dir=3D"ltr">Jonathan Rosenberg, Ph.D.<br><a href=3D"mailto:jdrosen@jdr= osen.net" target=3D"_blank">[email protected]</a><br><a href=3D"http://ww= w.jdrosen.net" target=3D"_blank">http://www.jdrosen.net</a></div> </div> --f46d04428f18ba944a04d5d6c029-- --===============0323049995001990100== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Simple mailing list [email protected] https://www.ietf.org/mailman/listinfo/simple --===============0323049995001990100==--