Re: [Softwires] draft-murakami-softwire-4v6-translation

2011-08-20 Thread Rémi Després
Le 20 août 2011 à 06:15, Brian E Carpenter a écrit : Ahah, you seem to assume that A+P will solve the ISP's shortage of IPv4 addresses. That may be true for a year or three, but after that they will discover that they have to CGN their A+P customers, and then you have NAT444 after all, IMHO.

Re: [Softwires] 4rd mapping rule separation

2011-08-20 Thread Rémi Després
Le 20 août 2011 à 03:55, Mark Townsley a écrit : On Aug 19, 2011, at 8:04 PM, Nejc Škoberne wrote: Because of what RFC6333 says, suggesting NOW that solutions that don't need NATs are variants of DS-lite is a sure way to confuse people. Then we're already confused:

Re: [Softwires] 4rd mapping rule separation

2011-08-20 Thread Mark Townsley
On Aug 20, 2011, at 3:20 AM, Rémi Després wrote: Le 20 août 2011 à 03:55, Mark Townsley a écrit : On Aug 19, 2011, at 8:04 PM, Nejc Škoberne wrote: Because of what RFC6333 says, suggesting NOW that solutions that don't need NATs are variants of DS-lite is a sure way to confuse

Re: [Softwires] Comments on draft-despres-softwire-4rd-addmapping-00

2011-08-20 Thread Rémi Després
Washam, Thank you for the detailed reaction. More below. Le 20 août 2011 à 10:44, Washam Fan a écrit : Hi, I support the seperation of address mapping from tunneled or translated 4rd mechanisms. Excellent. I have some comments as below. 1. Is there any reason you changed 4rd BR to 4rd

[Softwires] New working group documents

2011-08-20 Thread Yong Cui
Hi folks, Following our rough concensus during Quebec City meeting and according to our charter/milestones, the chairs would like to ask the mailing list for the confirmation to adopt the following drafts: 1. Deployment Considerations for Dual-Stack Lite

Re: [Softwires] New working group documents

2011-08-20 Thread Rémi Després
Le 20 août 2011 à 16:21, Yong Cui a écrit : Hi folks, Following our rough concensus during Quebec City meeting and according to our charter/milestones, the chairs would like to ask the mailing list for the confirmation to adopt the following drafts: ... 5. Motivations for Stateless IPv4

Re: [Softwires] draft-murakami-softwire-4v6-translation

2011-08-20 Thread Cameron Byrne
2011/8/19 Brian E Carpenter brian.e.carpen...@gmail.com: Ahah, you seem to assume that A+P will solve the ISP's shortage of IPv4 addresses. That may be true for a year or three, but after that they will discover that they have to CGN their A+P customers, and then you have NAT444 after all,

Re: [Softwires] draft-murakami-softwire-4v6-translation

2011-08-20 Thread Tina TSOU
Brian, Remi, In line. Best Regards, Tina TSOU http://tinatsou.weebly.com/contact.html -Original Message- From: softwires-boun...@ietf.org [mailto:softwires-boun...@ietf.org] On Behalf Of Brian E Carpenter Sent: Saturday, August 20, 2011 3:54 PM To: Rémi Després Cc:

Re: [Softwires] Can stateless address sharing be sufficient in some use cases

2011-08-20 Thread Rémi Després
Le 21 août 2011 à 00:54, Brian E Carpenter a écrit : On 2011-08-20 19:15, Rémi Després wrote: ... - There is no claim AFAIK that the stateless solution fits all situations. There is only a claim that some will use it alone if they can, because of its simplicity, that some will combine it

Re: [Softwires] 4rd mapping rule separation

2011-08-20 Thread Rémi Després
Mark, Interesting definition of retronym. It remains, though, that an analogue clock, the example given in the given reference) is a clock variant (a device for measuring time). A 4rd-encapsulation solution is in no way a DS-lite variant (built on a tunnel to reach a CGN). It would be nice,