36. The APN attribute should not become a way of carrying arbitrary metadata. It is not clear at this stage what information needs to be in the APN attribute versus what information could be in the APN attribute.

[APN-Github]

Yes, we agree that the APN attribute should not become a way of carrying arbitrary metadata. The APN Header is specified in this draft https://datatracker.ietf.org/doc/draft-li-apn-header/. The carried APN ID and the APN Parameters are also defined. The APN Attribute Conveying Requirements are also specified in this draft https://datatracker.ietf.org/doc/html/draft-li-apn-framework-04#section-5.1.

[jariarkko]

Can I suggest that the right answer is thinking in terms of bits, not in terms of AVPs. A few bits can't carry user or application IDs, but could carry classes of things.

[APN-Github]

Can I suggest that the right answer is thinking in terms of bits, not in terms of AVPs. A few bits can't carry user or application IDs, but could carry classes of things.

Would you like to further clarify a bit about how APN uses AVP in your mind? Currently APN does not use AVP (Attribute-Value Pair) but bits.