Re: [sunset4] Meeting in BA

[Naoki Matsuhira <[e-mail]>]

Thank you, Wes,

The essence of my proposal is thinking including private network with 
IPv4 private address. There are many many private network such as 
corporate network, so I believe transition technology should support 
IPv4 private address.

We know that IPv6 is beginning to spread, in the near feature, the 
situation with wide IPv6 and small IPv4 and small but many IPv4 private 
will be the reality. Looking that time, IPv6 should wind up IPv4 network 
including private address, then enable IPv6 only operation in 
infrastructure, and provide IPv4 continuous use environment as a service.

The technical essence of my proposal is Plane ID in M46A. And I propose 
my proposal as a general-purpose technology, and may apply many IPv4 
network such as for backbone network, enterprise network, datacenter 
network.

The difference from MAP, DSLite, 464XLat, I understand these are 
combined technology, i.e., NAT with hub and spoke Tunnel. In M46E 
(encapsulation) position, M46E and NAT combination may possible. I 
believe the decision of such combination is focusing to access network 
and main point is address sharing.

As encapsulation technology, M46E support full mesh, and N point full 
mesh normally require N^2 configuration, however M46E-FP require N 
configuration. So I believe these proposal may contribute.

Regards,

Naoki



On 2016/02/16 3:52, George, Wes wrote:
> Let's start the discussion here -
>
> Can you explain how this is different from existing IPv4 over IPv6
> transition technologies e.g. MAP, DSLite, 464XLat?
> IETF doesn't have a lot of appetite for defining yet another transition
> technology, even those that use IPv6 to provide IPv4 as a service, so you
> have an uphill battle to demonstrate why this is something we should work
> on. What problems exist with the already defined and implemented protocols
> listed above that this solves, and how? This is probably something that
> should go in your intro draft, but you can start by writing something up
> on the mailing list for discussion.
>
> Thanks,
>
> Wes
>
>
>
>
> On 2/11/16, 8:51 PM, "Naoki Matsuhira" <[e-mail]> wrote:
>
>> Hi,
>>
>> Recently, I submitted six drafts. I want to ask sunset4 WG there are
>> interests in these drafts.
>>
>> The basic idea is IPv4 mapped IPv6 address which could distinguish
>> several IPv4 network including IPv4 private network with IPv4 private
>> address (M46A).
>>
>> I am proposing encapsulation technologies using this address (M46E-FP,
>> M46E-PR, M46E-PT) , and translation technology using this address(M46T).
>> I am also proposing IPv4 address sharing technology(M4P6E).
>>
>> I thing there are proposal both sunset4 WG have interest and not interest.
>>
>> I especially would like to propose the encapsulation technologies. These
>> technologies are IPv4 over IPv6 encapsulation, so by using these
>> technologies, it is possible sunsetting IPv4 (IPv6 only )in network
>> infrastructure, and provide IPv4 with overlay. I believe with this
>> technology, could provide IPv4 as a service. That may first step to
>> completely sunsetting IPv4, with staring focus to infrastructure.
>>
>> These six drafts are the following.
>>
>> https://www.ietf.org/id/draft-matsuhira-m46a-00.txt
>> https://www.ietf.org/id/draft-matsuhira-m46e-fp-00.txt
>> https://www.ietf.org/id/draft-matsuhira-m46e-pr-00.txt
>> https://www.ietf.org/id/draft-matsuhira-m46e-pt-00.txt
>> https://www.ietf.org/id/draft-matsuhira-m46t-00.txt
>> https://www.ietf.org/id/draft-matsuhira-m4p6e-00.txt
>>
>> In addition, these proposal had been proposed under the name SA46T in
>> the past. Starting proposal, there was only one idea, however I got
>> several ideas. So I organize and changing name, and re-submitted. If you
>> know SA46T, I believe you will understand immediately.
>>
>> Regards
>>
>> Naoki Matsuhira
>>
>>
>>
>>
>> (2016/01/20 0:05), George, Wes wrote:
>>> Hello -
>>>
>>> WG scheduling cutoff is 19 February. That gives us almost exactly a
>>> month. The list has been very quiet, and we need to see some activity to
>>> justify a meeting – what does the WG wish to discuss face to face?
>>>
>>> Thanks,
>>>
>>> Wes
>>>
>>> Anything below this line has been added by my company’s mail server, I
>>> have no control over it.
>>>
>>> -----------
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> This E-mail and any of its attachments may contain Time Warner Cable
>>> proprietary information, which is privileged, confidential, or subject
>>> to copyright belonging to Time Warner Cable. This E-mail is intended
>>> solely for the use of the individual or entity to which it is addressed.
>>> If you are not the intended recipient of this E-mail, you are hereby
>>> notified that any dissemination, distribution, copying, or action taken
>>> in relation to the contents of and attachments to this E-mail is
>>> strictly prohibited and may be unlawful. If you have received this
>>> E-mail in error, please notify the sender immediately and permanently
>>> delete the original and any copy of this E-mail and any printout.
>>>
>>>
>>>
>>> _______________________________________________
>>> sunset4 mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/sunset4
>
>
> ________________________________
>
> This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
>