Re: SIMPLE and OMA and 3Gpp and RCS and... (new subject)
Mary Barnes <[email protected]> Sun, 4 Nov 2012 07:15:55 -0600
| Newsgroups | gmane.ietf.simple |
|---|---|
| Message-ID | <CAHBDyN7bcN3g0cf8B5ND0GLWiTu8teLtrE=1D-NJaUtZw8mGpw@mail.gmail.com> |
--===============0982701579859908099== Content-Type: multipart/alternative; boundary=e0cb4efe2a0a40295d04cdab2bc7 --e0cb4efe2a0a40295d04cdab2bc7 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Nov 1, 2012 at 6:12 PM, Ben Campbell <[email protected]> wrote: > > On Nov 1, 2012, at 6:09 PM, Ben Campbell <[email protected]> wrote: > > > > > On Nov 1, 2012, at 6:00 PM, "DRAGE, Keith (Keith)" < > [email protected]> wrote: > > > >> So I guess that IETF has therefore abandoned RFC 5727. > > > > I'm trying to figure out how "abandoning 5727" follows from "no liaison > manager for OMA". I'm not getting it; can you elaborate? > > > >> > >> OMA last asked for 6 header fields to be registered. As far as I > understand they were told they needed a standards track RFC to do this. > Identifying no need for cooperation tells me that IETF is quite happy they > have their own version of the SIP specification. > >> > > > > I don't think choosing not to assign a liaison manager implies we expect > no cooperation. You don't need an IETF assigned liaison manager to someone > bring a draft to the IETF, do you? > > Okay, that was a cut-paste disaster. s/ "to someone bring" / "for someone > to bring" > [MB] Correct, you do not need an IETF appointed liaison manager in order to work with another SDO/forum. There is an email address for any liaison statements to be sent and those are generally distributed to the appropriate parties. The drafts run the normal course through the process. Note, that IETF only recently decided they did not need a liaison manager for OMA as the individual that was in that role was no longer able to do it. But, the assessment at that time was that one was not needed. The onus is not on IETF to drive the contributions from another SDO. The onus is on the individuals that are driving the work. [/MB] > > > > >> Keith > >> > >>> -----Original Message----- > >>> From: Hannes Tschofenig [mailto:[email protected]] > >>> Sent: 01 November 2012 20:09 > >>> To: Ben Campbell > >>> Cc: Olle E. Johansson; Bernard Aboba; DRAGE, Keith (Keith); > >>> [email protected] > >>> Subject: Re: [Simple] SIMPLE and OMA and 3Gpp and RCS and... (new > subject) > >>> > >>> Murray was the liaison person to the OMA from the IETF side. Murray > >>> recently discontinued his participation in the OMA (due to a job > change). > >>> We discussed the need to appoint a new liaison person in the IAB and > came > >>> to the conclusion that no new appointment is necessary; the required > need > >>> to interact with the OMA had decreased over time. > >>> > >>> Does anyone on this list believe that there is a need for cooperation > with > >>> the OMA? > >>> > >>> Ciao > >>> Hannes > >>> > >>> Sent from my ASUS Pad > >>> > >>> Ben Campbell <[email protected]> wrote: > >>> > >>>> > >>>> On Nov 1, 2012, at 2:20 PM, "Olle E. Johansson" <[email protected]> > wrote: > >>>> > >>>>> What is the current relationship betwen OMA and the IETF? ANy > >>> cooperation, like between 3Gpp and the IETF? > >>>>> > >>>> > >>>> > >>>> There is a liaison, but I don't think it's been very active for a > while > >>> now. > >>>> _______________________________________________ > >>>> Simple mailing list > >>>> [email protected] > >>>> https://www.ietf.org/mailman/listinfo/simple > > > > _______________________________________________ > Simple mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/simple > --e0cb4efe2a0a40295d04cdab2bc7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <br><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, N= ov 1, 2012 at 6:12 PM, Ben Campbell <span dir=3D"ltr"><<a href=3D"mailto= :[email protected]" target=3D"_blank">[email protected]</a>></span> wrote:<b= r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:= 1px #ccc solid;padding-left:1ex"> <div class=3D"im"><br> On Nov 1, 2012, at 6:09 PM, Ben Campbell <<a href=3D"mailto:ben@nostrum.= com">[email protected]</a>> wrote:<br> <br> ><br> > On Nov 1, 2012, at 6:00 PM, "DRAGE, Keith (Keith)" <<a hr= ef=3D"mailto:[email protected]">[email protected]= </a>> wrote:<br> ><br> >> So I guess that IETF has therefore abandoned RFC 5727.<br> ><br> > I'm trying to figure out how "abandoning 5727" follows f= rom "no liaison manager for OMA". I'm not getting it; can you= elaborate?<br> ><br> >><br> >> OMA last asked for 6 header fields to be registered. As far as I u= nderstand they were told they needed a standards track RFC to do this. Iden= tifying no need for cooperation tells me that IETF is quite happy they have= their own version of the SIP specification.<br> >><br> ><br> > I don't think choosing not to assign a liaison manager implies we = expect no cooperation. You don't need an IETF assigned liaison manager = to someone bring a draft to the IETF, do you?<br> <br> </div>Okay, that was a cut-paste disaster. s/ "to someone bring" = / "for someone to bring"<br></blockquote><div>[MB] Correct, you d= o not need an IETF appointed liaison manager in order to work with another = SDO/forum. There is an email address for any liaison statements to be sent = and those are generally distributed to the appropriate parties. =A0The draf= ts run the normal course through the process. =A0Note, that IETF only recen= tly decided they did not need a liaison manager for OMA as the individual t= hat was in that role was no longer able to do it. =A0But, the assessment at= that time was that one was not needed. The onus is not on IETF to drive th= e contributions from another SDO. =A0The onus is on the individuals that ar= e driving the work. =A0[/MB]=A0</div> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> <div class=3D"HOEnZb"><div class=3D"h5"><br> ><br> >> Keith<br> >><br> >>> -----Original Message-----<br> >>> From: Hannes Tschofenig [mailto:<a href=3D"mailto:hannes.tscho= [email protected]">[email protected]</a>]<br> >>> Sent: 01 November 2012 20:09<br> >>> To: Ben Campbell<br> >>> Cc: Olle E. Johansson; Bernard Aboba; DRAGE, Keith (Keith);<br= > >>> <a href=3D"mailto:[email protected]">[email protected]</a><br> >>> Subject: Re: [Simple] SIMPLE and OMA and 3Gpp and RCS and... (= new subject)<br> >>><br> >>> Murray was the liaison person to the OMA from the IETF side. M= urray<br> >>> recently discontinued his participation in the OMA (due to a j= ob change).<br> >>> We discussed the need to appoint a new liaison person in the I= AB and came<br> >>> to the conclusion that no new appointment is necessary; the re= quired need<br> >>> to interact with the OMA had decreased over time.<br> >>><br> >>> Does anyone on this list believe that there is a need for coop= eration with<br> >>> the OMA?<br> >>><br> >>> Ciao<br> >>> Hannes<br> >>><br> >>> Sent from my ASUS Pad<br> >>><br> >>> Ben Campbell <<a href=3D"mailto:[email protected]">ben@nostru= m.com</a>> wrote:<br> >>><br> >>>><br> >>>> On Nov 1, 2012, at 2:20 PM, "Olle E. Johansson" = <<a href=3D"mailto:[email protected]">[email protected]</a>> wrote:<br> >>>><br> >>>>> What is the current relationship betwen OMA and the IE= TF? ANy<br> >>> cooperation, like between 3Gpp and the IETF?<br> >>>>><br> >>>><br> >>>><br> >>>> There is a liaison, but I don't think it's been ve= ry active for a while<br> >>> now.<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" t= arget=3D"_blank">https://www.ietf.org/mailman/listinfo/simple</a><br> ><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> </div></div></blockquote></div><br></div> --e0cb4efe2a0a40295d04cdab2bc7-- --===============0982701579859908099== 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 --===============0982701579859908099==--