libgtpnl/67e1fef97dafa2b140a974b7cbb...

76 lines
4.2 KiB
Plaintext

{
"comments": [
{
"unresolved": true,
"key": {
"uuid": "cd48c380_8cedbf65",
"filename": "/COMMIT_MSG",
"patchSetId": 2
},
"lineNbr": 9,
"author": {
"id": 1000074
},
"writtenOn": "2024-02-15T15:10:21Z",
"side": 1,
"message": "IIUC you mean here that we now use different local TEI pools for IPv4 and IPv6 (which makes sense, since the the IP addresses will be different given the family is different), and hence one now needs to specify from which family (pool) the TEI is identified.\n\nSo in theory one would have to pass a tuple \u003clocal_IPaddr, TEID\u003e to fully identify the tunnel, but since we have 1 local IP address per family then passing the famlily is enough. Am I correct?",
"revId": "67e1fef97dafa2b140a974b7cbbb668eff66aa6c",
"serverId": "035e6965-6537-41bd-912c-053f3cf69326"
},
{
"unresolved": true,
"key": {
"uuid": "c66d4f48_89ff8d1b",
"filename": "/COMMIT_MSG",
"patchSetId": 2
},
"lineNbr": 9,
"author": {
"id": 1000112
},
"writtenOn": "2024-02-15T17:22:34Z",
"side": 1,
"message": "Probably the kernel patch kernels to clarify this:\n\ngtp: identify tunnel via GTP version + TEID + family\n\nThis allows to define a GTP tunnel for dual stack MS/UE with both IPv4\nand IPv6 addresses while using the same TEID via two PDP context\nobjects.\n\nStill not complete description though.\n\nYou have to specify the gtp device too, so this:\n\n[ GTP device, GTP version, TID/I_TEID, family ]\n\nthere is a 1:1 mapping between the local listener address and the GTP device. And a GTP can only listen to one single address at the same time, either IPv4 or IPv6.",
"parentUuid": "cd48c380_8cedbf65",
"revId": "67e1fef97dafa2b140a974b7cbbb668eff66aa6c",
"serverId": "035e6965-6537-41bd-912c-053f3cf69326"
},
{
"unresolved": true,
"key": {
"uuid": "fcee2076_2e91b009",
"filename": "/COMMIT_MSG",
"patchSetId": 2
},
"lineNbr": 9,
"author": {
"id": 1000074
},
"writtenOn": "2024-02-15T17:31:51Z",
"side": 1,
"message": "Ah I think I previously confused IPv4/Ipv6 *outer* support with *inner* support here, sorry.\n\n\u003eAnd a GTP can only listen to one single address at the same time, either IPv4 or IPv6.\n\nSo this means, If one wants to implement a GSN node which can be accessed both through IPv4 and IPv6 in UDP/GTP-U (*outer*, not *inner*), then 2 gtp tun devices need to be created right? One for IPv4 and one for IPv6.\n\nEg. When sending a GTPv2C CreateSessionReq, the GSN node can specify both an IPv4 and an IPv6 address where it can be reached (in FQDN IE). Similar stuff in the CreateSessionResp back.\nSimilar stuff in GTpv1C with \"GSN Address\" IEs.",
"parentUuid": "c66d4f48_89ff8d1b",
"revId": "67e1fef97dafa2b140a974b7cbbb668eff66aa6c",
"serverId": "035e6965-6537-41bd-912c-053f3cf69326"
},
{
"unresolved": true,
"key": {
"uuid": "d76eb6cf_3bdff6f9",
"filename": "/COMMIT_MSG",
"patchSetId": 2
},
"lineNbr": 9,
"author": {
"id": 1000112
},
"writtenOn": "2024-02-17T06:49:08Z",
"side": 1,
"message": "\u003e So this means, If one wants to implement a GSN node which can be accessed both through IPv4 and IPv6 in UDP/GTP-U (*outer*, not *inner*), then 2 gtp tun devices need to be created right? One for IPv4 and one for IPv6.\n\nYes, you need one gtp device for IPv4 and another for IPv6 in case you want to support for GTP over IPv4 and GTP over IPv6 respectively.\n\n\u003e Eg. When sending a GTPv2C CreateSessionReq, the GSN node can specify both an IPv4 and an IPv6 address where it can be reached (in FQDN IE). Similar stuff in the CreateSessionResp back.\n\u003e Similar stuff in GTpv1C with \"GSN Address\" IEs.\n\nOK, that is, GTP control plane also allows for this. Thanks for confirming.",
"parentUuid": "fcee2076_2e91b009",
"revId": "67e1fef97dafa2b140a974b7cbbb668eff66aa6c",
"serverId": "035e6965-6537-41bd-912c-053f3cf69326"
}
],
"submitRequirementResults": []
}