Just to make sure I understand this. Deterministic (statefull) NAT is deterministically translating inside IP to outside IP + port range (take NAT44 case).
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. CPE still needs statefull NAT. Is this correct? Thanks, Kris -----Original Message----- From: behave-boun...@ietf.org [mailto:behave-boun...@ietf.org] On Behalf Of Reinaldo Penno Sent: Tuesday, November 01, 2011 4:12 PM To: softwires@ietf.org; beh...@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 beh...@ietf.org https://www.ietf.org/mailman/listinfo/behave _______________________________________________ Softwires mailing list Softwires@ietf.org https://www.ietf.org/mailman/listinfo/softwires
