name: ABNF
full_form: Augmented Backus-Naur Form
context: In particular, it was needed to have most of the AVPs used by 3GPP Diameter charging applications "optional" per ABNF syntax (i.e. with []), so that corresponding IE category can override the ABNF syntax. The few AVPs which are used as "required" AVP in the ABNF syntax (i.e. with {} and <>), are for most of them, inherited from IETF ACR/ACA, CCR/CCA common structure, (e.g. { Origin-Host }), and it can be only category M for the corresponding IE.
description: Augmented Backus-Naur Form (ABNF) is a meta-language used to describe the syntax of data in various protocols. It provides a standardized way to express the structure and organization of data, making it easier to define and implement protocols.
explanation: The text describes ABNF as a tool for defining protocol syntax, not a specific network function, service, or technology. This places it within the broader category of 'Miscellaneous'.
section_title: 4.2.2.2AVP ABNF syntax
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,B-Message,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,B-Message,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: B-Miscellaneous,I-Miscellaneous,I-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O