Re: [Softwires] [BEHAVE] Stateless Deterministic NAPT/DS-Lite

Hello Kristian,

comments inline.

On 11/3/11 4:38 PM, "Poscic, Kristian (Kristian)"
<kristian.poscic@alcatel-lucent.com> wrote:

> Just to make sure I understand this.
> 
> Deterministic (statefull) NAT is deterministically translating inside IP to
> outside IP + port range (take NAT44 case).

Yes. 

> 
> Deterministic stateLESS NAT is deterministically translating inside IP +
> inside_src_port to outside IP + outside_src_port.
> No states are required since the incoming traffic in the downstream direction
> (outside IP +port) can be deterministically translated to inside IP+port.
> Any incoming traffic from outside will be mapped to something (predictable) on
> the inside even though there may be no traffic initiated from the inside.

Correct, no need for previous outbound packet. Subscriber gets port
forwarding naturally as a consequence.

> 
> CPE still needs statefull NAT.
> 
> Is this correct?

Yes.

> Thanks,
> Kris
> 
> 
> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf Of
> Reinaldo Penno
> Sent: Tuesday, November 01, 2011 4:12 PM
> To: softwires@ietf.org; behave@ietf.org
> Subject: [BEHAVE] Stateless Deterministic NAPT/DS-Lite
> 
> Hello,
> 
> we submitted a new draft detailing our implementation of
> Stateless-Deterministic NAPT44 and DS-Lite. (SD-NAT)
> 
> http://tools.ietf.org/html/draft-penno-softwire-sdnat-01
> 
> This is a based on our experience with port bucket/chunk allocation and
> deterministic NAPT44. In the draft we provide a comparison with other
> stateless/stateful methods floating around.
> 
> Thanks,
> 
> Reinaldo
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave