Re: [Softwires] MAP-T DMR and IPv4 address mapping

- From: softwires-boun...@ietf.org [mailto:softwires-boun...@ietf.org] On Behalf Of Ole Troan Sent: Thursday, June 06, 2013 9:28 AM To: Wojciech Dec Cc: Softwires-wg; Congxiao Bao Subject: Re: [Softwires] MAP-T DMR and IPv4 address mapping would like to get your feedback regarding

Re: [Softwires] What are the claimed flaws of 4rd-U?

Hi Remi, 2012/4/2 Rémi Després despres.r...@laposte.net Hi, Congxiao, During the Softwire meeting, you came to the mike to assert that the 4rd-U specification was known to have flaws. Yes, I said that and I insist on saying that again today. Yet, you do know that the 4rd-U

Re: [Softwires] Path to move forward with 4rd… More MAP-T experiment needed

Fully agree with Maoke! This is not just the issue of publishing two documents...To accormodate with 4rd-U, many existing RFCs should be updated, like RFC 4291,RFC6052,etc. There is no evidence to show that we need to do that because 4rd-U havn't been shown that it is workable in today's

Re: [Softwires] Path to move forward with 4rd

Hi Penno, MAP-T was derived from dIVI and dIVI-PD, which has been running at CERNET2 for two years and have been tested at China Telcom both in Beijing and Hunan last year. In addition, the dIVI-PD was demonstrated successfully in Softwire Interim Meeting in Beijing last September. BTW, the

Re: [Softwires] MAP documents - next steps

I support to have this set of drafts adopted as WG documents. Congxiao 2012/2/3 Xing Li x...@cernet.edu.cn 于 2012/2/1 22:33, Ole Trøan 写道: Mark, While I appreciate the functional modularity in understanding the solution space, I do wish that DT had come up with a way to make this one

Re: [Softwires] New Version Notification for draft-mdt-softwire-map-translation-00.txt

Hi Leaf, Thanks for your comments. Please see in lines: 2012/1/13 Leaf yeh leaf.y@huawei.com Comments and Questions: 1. Section 7.3 - Translating IPv6 Address and Port Number into IPv4 Address and Port Number at the BR quote At the BR, the IPv4 source address MUST be derived from the

Re: [Softwires] 4rd Address Mapping - version-01

Hi Remi, Ok, we will draft a document on using existing tools for OM in dIVI/dIVI-PD very soon. Best, Congxiao Rémi Després 写道: Hi Xing, Congxiao, Le 4 oct. 2011 à 15:26, xiaohong deng a écrit : ... It IMHO would be helpful if anybody would clarify some details to 1) first prove

Re: [Softwires] MAP: Mapping of Addressees and Ports design team

Hi Ole, I am Congxiao Bao, I would like to be in the design team of MAP, I think I could contribute my design ideas for stateless double transaltion.Since I have been working on IVI ,dIVI and dIVI-PD for about three years. Thansk! Best, Congxiao 2011/10/7 Alain Durand adur...@juniper.net

Re: [Softwires] Proposed Unified Address Mapping for encapsulation and double-translation

residual deployment across IPv6-only routing domains. It results from an informal meeting among participants having different preferences between double-translation and encapsulation solutions (Xing Li, Congxiao Bao, Wojciech Dec, myself, at the end of the Beijing meeting). The idea

Re: [Softwires] 4rd Address Mapping - version-01

Hi Remi, Ok, we will draft a document on using existing tools for OM in dIVI/dIVI-PD very soon. Best, Congxiao 2011/10/4 Rémi Després despres.r...@laposte.net Hi Xing, Congxiao, Le 4 oct. 2011 à 15:26, xiaohong deng a écrit : ... It IMHO would be helpful if anybody would clarify some

Re: [Softwires] Softwire Interim Meeting in Beijing

2011/8/19 Rajiv Asati (rajiva) raj...@cisco.com It doesn't, IMO. In fact, I beg to say that it is unfair mention 'tunneling vs translating' as a blanket statement, since we have known all along that a sane 4v6 solution would likely involve translating (44), no matter what. Moreover, it is