Linda, a key principle for use cases that we want to support is de-coupling the mobile's IP address from a particular user plane anchor and its topological location.
Which anchors serve the mobile's current IP address is to be propagated to the transport network. We discuss two options, based on a transport network controller and based on a decentralized control plane. For both we discuss which semantics to share between the mobile communication system and the transport. NAT should be ok, the question is at which PE router traffic enters/leaves the mobile communication system and where the NAT is located. In case of a few routers that connect multiple ASs, the draft may apply to a limited scope. Hope that clarifies. Thanks, marco From: Linda Dunbar <[email protected]> Sent: Freitag, 2. August 2024 02:05 To: [email protected] Cc: [email protected] Subject: questions about draft-liebsch-dmm-mts-00 Marco, For the basic scenario described in your draft-liebsch-dmm-mts-00, does the IP address for the UE change when the UE moves from one UPA to another? Your draft talks about de-coupling of a mobile node's IP address. If the UE's IP address changes, how does the information propagate to the Transport Control Plane over the N6 Interface? For the Traffic steering of non-routable IP: Today, NAT is used to translate UE's private IP to a routable IP. So, the address on the N6 interface is routable IP. Under what scenario will the "non-routable IP" be an issue? Thank you very much, Linda Dunbar
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ dmm mailing list -- [email protected] To unsubscribe send an email to [email protected]
