http://blog.gmane.org/gmane.ietf.multimob hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.ietf.multimob/217 <pre> Dear Juan Zuniga, Luis M. Contreras, Carlos Jésus Bernardos, Seil Jeon, Younghan Kim: An IPR disclosure that pertains to your Internet-Draft entitled "Multicast Mobility Routing Optimizations for Proxy Mobile IPv6" (draft-ietf-multimob- pmipv6-ropt) was submitted to the IETF Secretariat on 2013-05-15 and has been posted on the "IETF Page of Intellectual Property Rights Disclosures" (https://datatracker.ietf.org/ipr/2075/). The title of the IPR disclosure is "InterDigital Patent Holdings, Inc.'s Statement about IPR related to draft-ietf- multimob-pmipv6-ropt-05.""); The IETF Secretariat _______________________________________________ multimob mailing list multimob&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/multimob </pre> IETF Secretariat 2013-05-21T19:34:56 http://comments.gmane.org/gmane.ietf.multimob/216 <pre>Folks, Since there was a late IPR claim on this draft, this message starts a one week Multimob Working Group last call on advancing: Title : Multicast Mobility Routing Optimizations for Proxy Mobile IPv6 Author(s) : Juan Carlos Zuniga Luis M. Contreras Carlos J. Bernardos Seil Jeon Younghan Kim Filename : draft-ietf-multimob-pmipv6-ropt-05.txt Pages : 25 Date : 2013-05-13 as Experimental. Substantive comments and statements of support for advancing this document should be directed to the mailing list. Editorial suggestions can be sent to the authors. This last call will end on May 28, 2013. We also indicate that there are now two IPR claims made on this draft, for details, see https://datatracker.ietf.org/ipr/search/?option=document_search&amp;document_search=draft-ietf-multimob-pmipv6-ropt Regards, Behcet _______________________________________________</pre> Behcet Sarikaya 2013-05-21T14:42:02 http://comments.gmane.org/gmane.ietf.multimob/215 <pre> Dear Juan Zuniga, Luis M. Contreras, Carlos Jésus Bernardos, Seil Jeon, Younghan Kim: An IPR disclosure that pertains to your Internet-Draft entitled "Multicast Mobility Routing Optimizations for Proxy Mobile IPv6" (draft-ietf-multimob- pmipv6-ropt) was submitted to the IETF Secretariat on 2013-05-15 and has been posted on the "IETF Page of Intellectual Property Rights Disclosures" (https://datatracker.ietf.org/ipr/2077/). The title of the IPR disclosure is "Foundation of Soongsil University-Industry Cooperation's Statement about IPR related to draft-ietf-multimob-pmipv6-ropt-05.""); The IETF Secretariat _______________________________________________ multimob mailing list multimob&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/multimob </pre> IETF Secretariat 2013-05-16T20:46:34 http://comments.gmane.org/gmane.ietf.multimob/214 <pre> Dear Juan Zuniga, Luis M. Contreras, Carlos Jésus Bernardos, Seil Jeon, Younghan Kim: An IPR disclosure that pertains to your Internet-Draft entitled "Multicast Mobility Routing Optimizations for Proxy Mobile IPv6" (draft-ietf-multimob- pmipv6-ropt) was submitted to the IETF Secretariat on 2013-05-14 and has been posted on the "IETF Page of Intellectual Property Rights Disclosures" (https://datatracker.ietf.org/ipr/2074/). The title of the IPR disclosure is "Foundation of Soongsil University-Industry Cooperation's Statement about IPR related to draft-ietf-multimob-pmipv6-ropt-05.""); The IETF Secretariat _______________________________________________ multimob mailing list multimob&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/multimob </pre> IETF Secretariat 2013-05-15T14:33:30 http://comments.gmane.org/gmane.ietf.multimob/213 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multicast Mobility Working Group of the IETF. Title : Multicast Mobility Routing Optimizations for Proxy Mobile IPv6 Author(s) : Juan Carlos Zuniga Luis M. Contreras Carlos J. Bernardos Seil Jeon Younghan Kim Filename : draft-ietf-multimob-pmipv6-ropt-05.txt Pages : 25 Date : 2013-05-13 Abstract: The MULTIMOB group has specified a base solution to support IP multicasting in a PMIPv6 domain [RFC6224]. In this document, some enhancements to the base solution are described. These enhancements include the use of a multicast tree mobility anchor as the topological anchor point for multicast traffic, as well as a direct routing option where the MAG can provide access to multicast content in the local network. These enhancemen</pre> internet-drafts< at >ietf.org 2013-05-13T19:28:49 http://comments.gmane.org/gmane.ietf.multimob/207 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multicast Mobility Working Group of the IETF. Title : Multicast Mobility Routing Optimizations for Proxy Mobile IPv6 Author(s) : Juan Carlos Zuniga Luis M. Contreras Carlos J. Bernardos Seil Jeon Younghan Kim Filename : draft-ietf-multimob-pmipv6-ropt-04.txt Pages : 25 Date : 2013-05-03 Abstract: The MULTIMOB group has specified a base solution to support IP multicasting in a PMIPv6 domain [RFC6224]. In this document, some enhancements to the base solution are described. These enhancements include the use of a multicast tree mobility anchor as the topological anchor point for multicast traffic, as well as a direct routing option where the MAG can provide access to multicast content in the local network. These enhancemen</pre> internet-drafts< at >ietf.org 2013-05-03T17:29:50 http://comments.gmane.org/gmane.ietf.multimob/206 <pre>Hi authors, On page 21, The MN1 will send an MLD Report message (containing an State Change Record for the last subscribed multicast group with a filter change record mode indicating INCLUDE mode and an empty source list) to the MAG to request the cease of the multicast traffic delivery. In RFC 3810, on Page 22, A MODE_IS_INCLUDE Record is never sent with an empty source list. The API defined in RFC 3810 does allow the stop listening operation but the above seems not the right way. RFC 3810 defines soft leave which is based on timers. As I raised during Orlando meeting, this stop listening operation seems to be integrated into the source lists, i.e. not applicable to ASM. From the charter point of view, this may not be a problem because the scope specifically mentions MLDv2/IGMPv3. I repeat my suggestion on the A flag from Feb. 25: If a feasible solution emerges and WG believes that there is a need then a separate draft can be written and individual Handover</pre> Behcet Sarikaya 2013-05-01T19:35:05 http://comments.gmane.org/gmane.ietf.multimob/205 <pre>Biggest Fake Conference in Computer Science We are researchers from different parts of the world and conducted a study on the world’s biggest bogus computer science conference WORLDCOMP ( http://sites.google.com/site/worlddump1 ) organized by Prof. Hamid Arabnia from University of Georgia, USA. We submitted a fake paper to WORLDCOMP 2011 and again (the same paper with a modified title) to WORLDCOMP 2012. This paper had numerous fundamental mistakes. Sample statements from that paper include: (1). Binary logic is fuzzy logic and vice versa (2). Pascal developed fuzzy logic (3). Object oriented languages do not exhibit any polymorphism or inheritance (4). TCP and IP are synonyms and are part of OSI model (5). Distributed systems deal with only one computer (6). Laptop is an example for a super computer (7). Operating system is an example for computer hardware Also, our paper did not express any conceptual meaning. However, it was accepted both the times without any modifications (and without</pre> johnsonhammond1< at >hushmail.com 2013-04-27T17:36:07 http://comments.gmane.org/gmane.ietf.multimob/193 <pre>Dear all, After the Orlando meeting discussions on the flag A mechanism described in draft-ietf-multimob-handover-optimization-02 for mitigating the internal signaling within the network in case of reactive handover, we would like to consult WG members about your preference: Option 1.- To include the flag A mechanism as an integral (and mandatory) part of the solution, as described in the draft today. Option 2.- To consider the flag A mechanism as an option to reduce signaling in the core, then removing the reference to this mechanism from the draft. The final document would consider that the LMA always queries the pMAG by default, but mentioning that some mechanism (out-of-scope) could be used to reduce this signaling (by avoiding to query the pMAG). Thanks in advance, Best regards, Luis ________________________________ Luis M. Contreras Technology / Global CTO / Telefónica Efficiency Projects / Telefónica I+D Distrito Telefónica, Edificio Sur 3, Planta 3 28050 Madrid España / Spain</pre> LUIS MIGUEL CONTRERAS MURILLO 2013-04-10T07:49:37 http://comments.gmane.org/gmane.ietf.multimob/189 <pre>Hi Authors, From my previous review on Feb. 11, 2013: How do you avoid tunnel convergence problem if there are more than one MTMA? You have some hints in Appendix A.3, related to Fig. 8 but it is still not clear. Please explain it here in 3.1 We discussed this in Orlando, here are excerpts from the minutes: Behcet - But tunnel convergence is if mobile receives multiple copies of the same data JC - I am not sure I understand? Carlos - A single group will be linked to a single MTMA. So cannot receive multiple copies in the mobile Please add a good explanation of how the tunnel convergence is avoided in the presence of multiple MTMAs in Section 3.1. Regards, Behcet _______________________________________________ multimob mailing list multimob&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/multimob </pre> Behcet Sarikaya 2013-04-04T22:12:29 http://comments.gmane.org/gmane.ietf.multimob/185 <pre>Folks, Since there was consensus in the meeting on Wednesday this week, this message starts a three week Multimob Working Group last call on advancing: Title : Multicast Mobility Routing Optimizations for Proxy Mobile IPv6 Author(s) : Juan Carlos Zuniga Luis M. Contreras Carlos J. Bernardos Seil Jeon Younghan Kim Filename : draft-ietf-multimob-pmipv6-ropt-03.txt Pages : 25 Date : 2013-02-25 as Experimental. Substantive comments and statements of support for advancing this document should be directed to the mailing list. Editorial suggestions can be sent to the authors. This last call will end on April 8, 2013. We also indicate that there was an IPR claim made according to IETF rules on version 00 of this draft, for details, see https://datatracker.ietf.org/ipr/search/?option=document_search&amp;document_search=draft-ietf-multimob-pmipv6-ropt. R</pre> Behcet Sarikaya 2013-03-15T14:51:05 http://comments.gmane.org/gmane.ietf.multimob/184 <pre>Folks, IETF 86 session minutes have been uploaded. If you have corrections, please send a mail. Thanks to Akbar for diligently taking the minutes. Also, multiple upstream interfaces draft presentation has been uploaded. Behcet _______________________________________________ multimob mailing list multimob&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/multimob </pre> Behcet Sarikaya 2013-03-13T17:32:12 http://comments.gmane.org/gmane.ietf.multimob/183 <pre>Presenters, Pls send your presentations by Tuesday morning to the chairs (cc'ed). _______________________________________________ multimob mailing list multimob&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/multimob </pre> Behcet Sarikaya 2013-03-11T17:44:07 http://comments.gmane.org/gmane.ietf.multimob/182 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multicast Mobility Working Group of the IETF. Title : Multicast Listener Extensions for MIPv6 and PMIPv6 Fast Handovers Author(s) : Thomas C. Schmidt Matthias Waehlisch Rajeev Koodli Godred Fairhurst Dapeng Liu Filename : draft-ietf-multimob-fmipv6-pfmipv6-multicast-01.txt Pages : 27 Date : 2013-02-25 Abstract: Fast handover protocols for MIPv6 and PMIPv6 define mobility management procedures that support unicast communication at reduced handover latency. Fast handover base operations do not affect multicast communication, and hence do not accelerate handover management for native multicast listeners. Many multicast applications like IPTV or conferencing, though, are comprised of delay-sensitive real-time traffic and wil</pre> internet-drafts< at >ietf.org 2013-02-25T23:42:30 http://comments.gmane.org/gmane.ietf.multimob/178 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multicast Mobility Working Group of the IETF. Title : PMIPv6 multicast handover optimization by the Subscription Information Acquisition through the LMA (SIAL) Author(s) : Luis M. Contreras Carlos J. Bernardos Ignacio Soto Filename : draft-ietf-multimob-handover-optimization-02.txt Pages : 47 Date : 2013-02-25 Abstract: This document specifies a multicast handover optimization mechanism for Proxy Mobile IPv6 to accelerate the delivery of multicast traffic to mobile nodes after handovers. The mechanism is based on speeding up the acquisition of mobile nodes' multicast context by the mobile access gateways. To do that, extensions to the current Proxy Mobile IPv6 protocol are proposed. These extensions are not only applicable to the base solution for multicast support in Pr</pre> internet-drafts< at >ietf.org 2013-02-25T22:10:50 http://comments.gmane.org/gmane.ietf.multimob/176 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multicast Mobility Working Group of the IETF. Title : Mobile Multicast Sender Support in Proxy Mobile IPv6 (PMIPv6) Domains Author(s) : Thomas C. Schmidt Shuai Gao Hong-Ke Zhang Matthias Waehlisch Filename : draft-ietf-multimob-pmipv6-source-03.txt Pages : 26 Date : 2013-02-25 Abstract: Multicast communication can be enabled in Proxy Mobile IPv6 domains via the Local Mobility Anchors by deploying MLD Proxy functions at Mobile Access Gateways, via a direct traffic distribution within an ISP's access network, or by selective route optimization schemes. This document describes the support of mobile multicast senders in Proxy Mobile IPv6 domains for all three scenarios. Protocol optimizations for synchronizing PMIPv6 with PIM, as well as extended M</pre> internet-drafts< at >ietf.org 2013-02-25T19:35:40 http://comments.gmane.org/gmane.ietf.multimob/173 <pre>Hi all, We have uploaded a new version of draft-ietf-multimob-pmipv6-ropt. We have aimed at addressing the comments received at the meeting, as well as the reviews we got on the list from Akbar, Behcet and Hitoshi. Please take a look and let us know if you have any further comments. Best regards, Juan Carlos et al. enhancements content </pre> Zuniga, Juan Carlos 2013-02-25T15:45:10 http://comments.gmane.org/gmane.ietf.multimob/172 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multicast Mobility Working Group of the IETF. Title : Multicast Mobility Routing Optimizations for Proxy Mobile IPv6 Author(s) : Juan Carlos Zuniga Luis M. Contreras Carlos J. Bernardos Seil Jeon Younghan Kim Filename : draft-ietf-multimob-pmipv6-ropt-03.txt Pages : 25 Date : 2013-02-25 Abstract: The MULTIMOB group has specified a base solution to support IP multicasting in a PMIPv6 domain [RFC6224]. In this document, some enhancements to the base solution are described. These enhancements include the use of a multicast tree mobility anchor as the topological anchor point for multicast traffic, as well as a direct routing option where the MAG can provide access to multicast content in the local network. These enhancemen</pre> internet-drafts< at >ietf.org 2013-02-25T15:31:59 http://comments.gmane.org/gmane.ietf.multimob/170 <pre>Has been posted at http://www.ietf.org/proceedings/86/agenda/agenda-86-multimob _______________________________________________ multimob mailing list multimob&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/multimob </pre> Behcet Sarikaya 2013-02-20T16:48:04 http://comments.gmane.org/gmane.ietf.multimob/168 <pre>A new draft has been submitted to Multimob. Please read and comment: http://tools.ietf.org/id/draft-asaeda-multimob-pmip6-ropt-with-pim-00.txt _______________________________________________ multimob mailing list multimob&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/multimob </pre> Behcet Sarikaya 2013-02-18T23:00:51 http://comments.gmane.org/gmane.ietf.multimob/162 <pre>Hi JC, Authors, This draft is a candidate for WG LC soon, so please consider my comments below and revise accordingly: Section 3.1. Similarly, more than one MTMA could be deployed by the operator (not shown in Figure 1). How do you avoid tunnel convergence problem if there are more than one MTMA? You have some hints in Appendix A.3, related to Fig. 8 but it is still not clear. Please explain it here in 3.1 Section 3.2. each MAG has a direct connection (i.e., not using the tunnel interface) with a multicast router. Does MR need to be next hop? If not what happens? Again this is later on explained on Page 15, but why not here? 3.3. Dynamic Selection Support This section is about MAG as a multicast router. WG has not yet decided if MAG should be a multicast router. So this section is out of scope. Please remove. Section 4.2.1 Is Figure 4 really needed? Maybe remove. 4.2.2. multicast establishment. vvv service 4.3. MAG as multicast router This section is also about MAG </pre> Behcet Sarikaya 2013-02-11T22:51:19 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.ietf.multimob