Re: About Flute-revised open points
[email protected] Thu, 7 Apr 2011 11:18:34 -0400
| Newsgroups | gmane.ietf.rmt |
|---|---|
| Message-ID | <[email protected]> |
--===============1135467509== Content-Type: multipart/alternative; boundary=Apple-Mail-55--387716580 --Apple-Mail-55--387716580 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 I agree with Magnus here. I hope that Rod can review Vincent's = historical summary of the issues and provide consensus or comments to = help us resolve this. =20 Additionally, here is a link to the message that summarizes the = backwards incompatibility issues identified by Dave Harrington's AD = review of FLUTE: http://www.ietf.org/mail-archive/web/rmt/current/msg01434.html best regards, Brian Adamson [email protected] On Mar 31, 2011, at 11:01 AM, Magnus Westerlund wrote: > Hi, >=20 > I think this is a good example of what I expect in this discussion. I > think that a number of the changes has good reasons to their changes = and > that we are not likely to reverse the WG documents text. For the = record > I don't really remember the reasons for the designs in this schema and > what the underlying 3GPP reasons are. >=20 > I have no rapid need for an updated flute so I am willing to let this > discussion go on for a while. Especially letting people try to dig up > any more motivations. But the fact is that the WG spent 5+ years in > producing this document. There are reasons why it looks like it does. > Reversing that decision at the last minute seems dangerous and likely = to > cause more issues than actually bumping the version number. >=20 > Cheers >=20 > Magnus Everybody, A follow-up to our long discussion during the meeting: 1- Concerning Flute version, the email that convinced me of the necessity to move to version 2 is the following one, from Mike, sent on Feb 7, 2011: http://www.ietf.org/mail-archive/web/rmt/current/msg01511.html 2- Concerning XML extensibility, after searching a little bit better in my archives, I finally found the initial reasons. See the following 3 emails (from June 2005): * The initial email (from Rod) explaining why 3GPP proposed another schema: http://www.ietf.org/mail-archive/web/rmt/current/msg00404.html * The answer from Magnus, with the 3GPP schema: http://www.ietf.org/mail-archive/web/rmt/current/msg00477.html * Finally Rod's promise (yes!!!) to include this schema: http://www.ietf.org/mail-archive/web/rmt/current/msg00482.html That's for the history. The question now is what do we want to do? Vincent > _______________________________________________ > Rmt mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/rmt >=20 > --=20 >=20 > Magnus Westerlund >=20 > ---------------------------------------------------------------------- > Multimedia Technologies, Ericsson Research EAB/TVM > ---------------------------------------------------------------------- > Ericsson AB | Phone +46 10 7148287 > F=E4r=F6gatan 6 | Mobile +46 73 0949079 > SE-164 80 Stockholm, Sweden| mailto: [email protected] > ---------------------------------------------------------------------- > _______________________________________________ > Rmt mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/rmt >=20 --Apple-Mail-55--387716580 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 <html><head></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I = agree with Magnus here. I hope that Rod can review = Vincent's historical summary of the issues and provide consensus or = comments to help us resolve this. = <div><br></div><div>Additionally, here is a link to the message = that summarizes the backwards incompatibility issues identified by Dave = Harrington's AD review of FLUTE:</div><div><br></div><div><a = href=3D"http://www.ietf.org/mail-archive/web/rmt/current/msg01434.html">ht= tp://www.ietf.org/mail-archive/web/rmt/current/msg01434.html</a></div><div= ><br></div><div><br></div><div><br><div><br></div><div>best = regards,</div><div><br></div><div><br><div> <div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; = -webkit-line-break: after-white-space; font-size: 12px; = "><div><div>Brian Adamson</div><div><a = href=3D"mailto:[email protected]">[email protected]</a><= /div><div><br></div></div><br></div><br = class=3D"Apple-interchange-newline"><br = class=3D"Apple-interchange-newline"> </div> <br><div><div>On Mar 31, 2011, at 11:01 AM, Magnus Westerlund = wrote:</div><br class=3D"Apple-interchange-newline"><blockquote = type=3D"cite"><div>Hi,<br><br>I think this is a good example of what I = expect in this discussion. I<br>think that a number of the changes has = good reasons to their changes and<br>that we are not likely to reverse = the WG documents text. For the record<br>I don't really remember the = reasons for the designs in this schema and<br>what the underlying 3GPP = reasons are.<br><br>I have no rapid need for an updated flute so I am = willing to let this<br>discussion go on for a while. Especially letting = people try to dig up<br>any more motivations. But the fact is that the = WG spent 5+ years in<br>producing this document. There are reasons why = it looks like it does.<br>Reversing that decision at the last minute = seems dangerous and likely to<br>cause more issues than actually bumping = the version = number.<br><br>Cheers<br><br>Magnus<br></div></blockquote><div><br></div><= div><span></span>Everybody,<br><br>A follow-up to our long discussion = during the meeting:<br><br>1- Concerning Flute version, the email that = convinced<br> me of the necessity to move to version 2 = is the<br> following one, from Mike, sent on Feb 7, = 2011:<br><br><a = href=3D"http://www.ietf.org/mail-archive/web/rmt/current/msg01511.html">ht= tp://www.ietf.org/mail-archive/web/rmt/current/msg01511.html</a><br><br>2-= Concerning XML extensibility, after searching a = little<br> bit better in my archives, I finally found = the initial reasons.<br> See the following 3 emails = (from June 2005):<br><br>* The initial email (from Rod) explaining why = 3GPP proposed<br> another schema:<br><a = href=3D"http://www.ietf.org/mail-archive/web/rmt/current/msg00404.html">ht= tp://www.ietf.org/mail-archive/web/rmt/current/msg00404.html</a><br><br>* = The answer from Magnus, with the 3GPP schema:<br><a = href=3D"http://www.ietf.org/mail-archive/web/rmt/current/msg00477.html">ht= tp://www.ietf.org/mail-archive/web/rmt/current/msg00477.html</a><br><br>* = Finally Rod's promise (yes!!!) to include this schema:<br><a = href=3D"http://www.ietf.org/mail-archive/web/rmt/current/msg00482.html">ht= tp://www.ietf.org/mail-archive/web/rmt/current/msg00482.html</a><br><br>Th= at's for the history. The question now is what do we want<br>to = do?<br><br> Vincent</div><br><blockquote = type=3D"cite">_______________________________________________<br></blockqu= ote><blockquote type=3D"cite">Rmt mailing = list<br></blockquote><blockquote type=3D"cite"><a = href=3D"mailto:[email protected]">[email protected]</a><br></blockquote><blockquote = type=3D"cite"><a = href=3D"https://www.ietf.org/mailman/listinfo/rmt">https://www.ietf.org/ma= ilman/listinfo/rmt</a><br></blockquote><blockquote = type=3D"cite"><br></blockquote><br><blockquote type=3D"cite"><div>-- = <br><br>Magnus = Westerlund<br><br>--------------------------------------------------------= --------------<br>Multimedia Technologies, Ericsson Research = EAB/TVM<br>---------------------------------------------------------------= -------<br>Ericsson AB = &n= bsp; | Phone +46 10 7148287<br>F=E4r=F6gatan 6 = &n= bsp; | Mobile +46 73 0949079<br>SE-164 80 Stockholm, Sweden| = mailto: <a = href=3D"mailto:[email protected]">magnus.westerlund@ericsson.= com</a><br>---------------------------------------------------------------= -------<br>_______________________________________________<br>Rmt = mailing list<br><a = href=3D"mailto:[email protected]">[email protected]</a><br>https://www.ietf.org/mail= man/listinfo/rmt<br><br></div></blockquote></div><br></div></div></body></= html>= --Apple-Mail-55--387716580-- --===============1135467509== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Rmt mailing list [email protected] https://www.ietf.org/mailman/listinfo/rmt --===============1135467509==--