Re: [Softwires] Softwire agenda for IETF79
Dear Alain, I believe draft-cui-softwire-host-4over6 and draft-boucadair-softwire-dslite-v6only have the same scope: Provide IPv4 connectivity over an IPv6-only network. I would expect these I-Ds to be listed under the same category. Cheers, Med -Message d'origine- De : softwires-boun...@ietf.org [mailto:softwires-boun...@ietf.org] De la part de Alain Durand Envoyé : jeudi 4 novembre 2010 02:03 À : Softwires list Objet : [Softwires] Softwire agenda for IETF79 Dear wg, Here is the tentative agenda for the softwire meeting at IETF79. As you see, there is an abundance of items that are neither on the current charter nor on the logical updates that we chairs have been discussing with our ADs. - Alain. IETF79 Softwire agenda Items in charter Multicast Mesh, Mingwei Xu, Chris Metz draft-dhankins-softwire-tunnel-option, David Hankins items in agreed evolution of the charter: draft-lee-softwire-dslite-deployment-00, Yiu Lee draft-qin-softwire-dslite-multicast-00, Jacni Qin draft-ietf-softwire-dslite-radius-ext-00, roberta Maglione draft-ietf-softwire-gateway-init-ds-lite-02, F. Brockners draft-cui-softwire-host-4over6, Yong Cui Items not in charter draft-guo-softwire-sc-discovery, Sheng Jiang draft-boucadair-softwire-dslite-v6only-00, Mohamed Boucadair draft-boucadair-softwire-cgn-bypass-03, Mohamed Boucadair draft-despres-softwire-6a44-01, Remi Despres draft-cui-softwire-pethttp://datatracker.ietf.org/doc/draft-cui-softwire-pet/, Peng Wu draft-templin-iron-13, Fred Templin draft-templin-intarea-seal-21, Fred Templin draft-tsou-softwire-gwinit-6rd. Tina Tsou draft-guo-softwire-6rd-radius-attrib-00, Sheng Jian draft-despres-softwire-4rd-00http://tools.ietf.org/id/draft-despres-softwire-4rd-00, Remi Despres draft-matsuhira-sa46t-as-00, Naoki Matsuhira ___ Softwires mailing list Softwires@ietf.org https://www.ietf.org/mailman/listinfo/softwires * This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. ___ Softwires mailing list Softwires@ietf.org https://www.ietf.org/mailman/listinfo/softwires
[Softwires] 4 Japanese ISPs intending to adopt 4rd - IETF spec needed
Hi, all, FWI, here are extracts from mails exchanged on the v4tov6transition list. The proposed 4rd specification is tools.ietf.org/id/draft-despres-softwire-4rd-00. As 4rd is likely to have only a very short presentation time on Monday morning (if any at all in view of the posted agenda), these extracts are IMHO worth looking at, to understand the importance of getting an 4rd specification in IETF. Good reading, and best regards, RD 1. From Satoru Matsushima, on September 2, 2010: ... FYI, SPs in Japan, BBIX, Internet Multifeed, JPIX and IIJ-II unveil the intention of adopting SAM/4rd as a solution for their IPv4 service over IPv6 native network. We then support including Remi's helpful comment for section 4.3 in the draft. Please take look at these joint press release. BBIX: http://www.bbix.net/press/file/press_20100831.pdf Internet Multifeed: http://www.mfeed.co.jp/press/2010/pdf/20100831.pdf JPIX: http://www.jpix.ad.jp/jp/pdf/20100831_001.pdf IIJ-II: http://www.iij.ad.jp/news/pressrelease/2010/0831.html Since these documents are written in Japanese originally, English page does not available by now. ... 2. From Satoru Matsushima, on September 20, 2010: ... Here is the summary of press release contents from Japanese ISPs. ... o They had co-worked to find what most efficient solution for IPv4 service over native IPv6 network. o The background is that they are going to provide IPv6 service from 2011, but they also need to provide IPv4 service as well. o Significant requirements for the solution are: 1. Sharing a IPv4 address among many of customers with highest cost efficiency - The analogy of SAM/4rd is as same as 6rd, it could be expected that high cost efficiency with stateless operation. NAT state only exist on the CPE side. 2. As much as simple provisioning and configuration - CPE can automatically configure its IPv4 address from delegated IPv6 prefix. 3. Optimized routing path for IPv4 service on the native IPv6 network (need mesh capability) - SAM/4rd allow CPE to CPE packet flow on optimized routing path in the IPv6 network. Since 4rd (IPv4 residual deployment), which is a part of IPv4 over IPv6 scenario of SAM (draft-despres-softwire-sam) satisfy these requirements, the ISPs intent to adopt SAM/4rd for their IPv4 solution. ___ Softwires mailing list Softwires@ietf.org https://www.ietf.org/mailman/listinfo/softwires
Re: [Softwires] Softwire agenda for IETF79
Remi, -Original Message- From: softwires-boun...@ietf.org [mailto:softwires-boun...@ietf.org] On Behalf Of Rémi Després Sent: Thursday, November 04, 2010 2:54 AM To: Alain Durand Cc: Softwires Subject: Re: [Softwires] Softwire agenda for IETF79 Alain, Dave, The Softwire charter says: The Softwires Working Group is specifying the standardization of discovery, control and encapsulation methods for connecting IPv4 networks across IPv6 networks and IPv6 networks across IPv4 networks in a way that will encourage multiple, inter-operable implementations. - Draft-despres-softwire-6a44-01 describes an encapsulation method for IPv4 over IPv6. - It concerns use cases that aren't covered yet (ISP-provided IPv6 addresses across NAT44's). - In Maastricht, there were 3 presentations for these use cases (not found out of scope then) - This draft is the result of a merger effort of two proposals. I formally solicit to have this draft re-integrated in the list of in-scope items. I have to say that this seems like an unabashed self-promotion. Your 6a44 is not the only proposal that can satisfy a wide variety of use cases (see: draft-russert-rangers), nor IMHO is it the best one. Thanks - Fred fred.l.temp...@boeing.com RD Le 4 nov. 2010 à 02:03, Alain Durand a écrit : Dear wg, Here is the tentative agenda for the softwire meeting at IETF79. As you see, there is an abundance of items that are neither on the current charter nor on the logical updates that we chairs have been discussing with our ADs. - Alain. IETF79 Softwire agenda Items in charter Multicast Mesh, Mingwei Xu, Chris Metz draft-dhankins-softwire-tunnel-option, David Hankins items in agreed evolution of the charter: draft-lee-softwire-dslite-deployment-00, Yiu Lee draft-qin-softwire-dslite-multicast-00, Jacni Qin draft-ietf-softwire-dslite-radius-ext-00, roberta Maglione draft-ietf-softwire-gateway-init-ds-lite-02, F. Brockners draft-cui-softwire-host-4over6, Yong Cui Items not in charter draft-guo-softwire-sc-discovery, Sheng Jiang draft-boucadair-softwire-dslite-v6only-00, Mohamed Boucadair draft-boucadair-softwire-cgn-bypass-03, Mohamed Boucadair draft-despres-softwire-6a44-01, Remi Despres draft-cui-softwire-pethttp://datatracker.ietf.org/doc/draft-c ui-softwire-pet/, Peng Wu draft-templin-iron-13, Fred Templin draft-templin-intarea-seal-21, Fred Templin draft-tsou-softwire-gwinit-6rd. Tina Tsou draft-guo-softwire-6rd-radius-attrib-00, Sheng Jian draft-despres-softwire-4rd-00http://tools.ietf.org/id/draft-d espres-softwire-4rd-00, Remi Despres draft-matsuhira-sa46t-as-00, Naoki Matsuhira ___ Softwires mailing list Softwires@ietf.org https://www.ietf.org/mailman/listinfo/softwires ___ Softwires mailing list Softwires@ietf.org https://www.ietf.org/mailman/listinfo/softwires ___ Softwires mailing list Softwires@ietf.org https://www.ietf.org/mailman/listinfo/softwires
Re: [Softwires] Softwire agenda for IETF79
Le 4 nov. 2010 à 15:32, Templin, Fred L a écrit : ... - Draft-despres-softwire-6a44-01 describes an encapsulation method for IPv4 over IPv6. ... I formally solicit to have this draft re-integrated in the list of in-scope items. I have to say that this seems like an unabashed self-promotion. It is only a defense of a collective work in which I am implied with Brian and Sheng. If we don't do it ourselves, who will do it? Your 6a44 is not the only proposal that can satisfy a wide variety of use cases (see: draft-russert-rangers), nor IMHO is it the best one. I observe a tendency to jump in, with a promotion of YOUR work, each time I defend one in which I am involved. Please feel free to do what you feel appropriate about your work. But, preferably, avoid criticizing colleagues when you do so. Regards, RD ___ Softwires mailing list Softwires@ietf.org https://www.ietf.org/mailman/listinfo/softwires
Re: [Softwires] Softwire agenda for IETF79
If we don't do it ourselves, who will do it? I used to think that way too, but through hard knocks came to realize that my time was more appropriately spent developing the technologies. Widely-applicable and high-quality technologies will speak for themselves if the community is being diligent in tracking them, and I have faith that that is exactly the case here. Thanks - Fred fred.l.temp...@boieng.com ___ Softwires mailing list Softwires@ietf.org https://www.ietf.org/mailman/listinfo/softwires
[Softwires] Please see sa46t and sa46t-as related docs for IETF 79
Hi, All. Follows are current sa46t and sa46t-as related I-D and past presentation slides at IETF meetings. http://tools.ietf.org/html/draft-matsuhira-sa46t-spec-01 http://tools.ietf.org/html/draft-matsuhira-sa46t-gaddr-01 http://tools.ietf.org/html/draft-matsuhira-sa46t-as-00 http://tools.ietf.org/html/draft-matsuhira-sa46t-applicability-00 http://www.ietf.org/proceedings/77/slides/v6ops-6.pdf http://www.ietf.org/proceedings/78/slides/softwire-10.pdf Please see these docs for fruitful discussion. Regards, Naoki Matsuhira ___ Softwires mailing list Softwires@ietf.org https://www.ietf.org/mailman/listinfo/softwires
