Iirc, the attrs set to empty string was an workaround to be sure the AVPs with attrs value do not get shifted (associated) with a wrong destination. The AVP cannot be null, so if among selected destinations some of them were with attrs and some without, then the number of AVPs with attrs was lower than the number of destinations.

Maybe is no longer needed with xavps, as the fields related to a destination are kept in an XAVP sublist. But that has to be reviewed to see if there is any side effect. Might be better to split this chance in its own commit.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.