NAT Behavioral Requirements for TCP¶
Guha, S. (2008). NAT Behavioral Requirements for TCP.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Maintenance Rehearsal
- In the network case the decay-prone state is the established connection binding held in NAT tables, firewalls, and load balancers along the path; idle bindings are reaped after a characteristic timeout.
This sourceSpecifies that NATs maintain TCP session state and reap idle bindings after configurable timeouts (established connections not less than 2 h 4 min, transitory not less than 4 min), the decay timer a keep-alive must undercut.
Supported in partVerified against the work's full text
RFC 5382 covers NAT TCP session state and idle-timeout reaping (established not less than 2 h 4 min); firewalls and load balancers are out of its scope.
“NATs may choose to proactively reap idle sessions.”
- In the network case the decay-prone state is the established connection binding held in NAT tables, firewalls, and load balancers along the path; idle bindings are reaped after a characteristic timeout.
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:98f0a67f479a · see in the full table