Re: [v6ops] draft-ietf-v6ops-nat64-experience-02.txt comments

Hi Mikael,

>>
>> 1. "Single stack IPv6 network deployment can simplify the network
>>     provisioning. ". I would remove "the" frmo this sentence.
>>
>> I think it's good that you stress the benefit of having access being
>> single stack instead of dual stack.
>>
>> 3.1
>>
>> I think it might be beneficial to say a little bit more here why 464xlat
>> is important, perhaps just one sentence "464XLAT enables access of IPv4
>> only applications or applications that call IPv4 literal addresses" (or
>> similar).

Will add the texts to describe the benefits of 464xlat

>> About geo-location, perhaps it can be adviced to chop up the outside IPv4
>> address pool so that IPv6 addresses are NAT64:ed depending on their
>> geographical location (we're doing this on a per country basis).

That is an interesting use. How do you implement those IPv4 pool
allocations?  I heard some NAT64 implementations could allocate
different IPv4 pools to each inbound interface. Are you doing in the
similar way?

>> 5.1
>>
>> I would like some text on "port block allocation", where a customer gets
>> 512 or 1024 ports, this is logged, which means as long as the same
>> customer still has this 512 port block, no further logging is needed.

If I understand correctly, that is a static port block allocation. A
port block would be reserved to a particular customer. No logging
information needed. will clarify at the next update.

>>
>> Apart from that the document looks good, and nothing more came to mind
>> when I read it.

Many thanks for the review.

Best Regards

Gang

>>
>> --
>> Mikael Abrahamsson    email: swmike@swm.pp.se
>>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>