…-----------------+ | Address Block | 192.0.0.0/29 | | Name | DS-Lite | | RFC | [RFC6333] | | Allocation Date | June 2011 | | Termination Date | N/A | | Source | True | | Destination | True | | Forwardable | True | | Global | False | | Reserved-by-Protocol | False | +-------------…

…----------------+ | Address Block | 192.0.0.0/29 | | Name | DS-Lite | | RFC | [ RFC6333 ] | | Allocation Date | June 2011 | | Termination Date | N/A | | Source | True | | Destination | True | | Forwardable | True | | Global | False | | Reserved-by-Protocol | False | +------------…

… 3.2.2 says: Operators should assign the same IPv4 address (e.g., 192.0.0.2/32 [RFC6333]) to all AFTRs. It should say: Operators should assign the same IPv4 address (e.g., 192.0.0.1/32 [RFC6333]) to all AFTRs. Notes: In RFC6333 6.5: The AFTR SHOULD use the well-known IPv4 address…

… 3.2.2 says: Operators should assign the same IPv4 address (e.g., 192.0.0.2/32 [RFC6333]) to all AFTRs. It should say: Operators should assign the same IPv4 address (e.g., 192.0.0.1/32 [RFC6333]) to all AFTRs. Notes: In RFC6333 6.5: The AFTR SHOULD use the well-known IPv4 address…