| commit | 867b13025b22bb831f190bcefeb17bfc026a5eb5 | [log] [tgz] |
|---|---|---|
| author | Pau Espin Pedrol <pespin@sysmocom.de> | Wed Jan 24 16:14:28 2024 +0100 |
| committer | Pau Espin Pedrol <pespin@sysmocom.de> | Wed Jan 24 16:14:30 2024 +0100 |
| tree | cf8a5903a004d95088e52deb77a0bf44670ecde0 | |
| parent | a6b0c1c128957f4f9df51c1a07acb65fa8500a20 [diff] |
DIAMETER: Split Gy and Gx messages to their own TS files Those interfaces reuse messages from other Diameter RFCs, but changing the contents of the messages, eg some Mandatory fields like Service-Context-Id which are mandatory in RFC5006, doesn't even appear in Gx CCR in TS 29.212. Keeping them well separated helps in avoiding confusion on users fo the messages. Change-Id: Ibe0d5f263813d5083e020c942283f214983162b4