SNMP trap configuration

We have a requirement where we want to configure the SNMP trap details, I understand that we can configure the SNMP trap details through the EventDestination schema where we can mention the protocol as SNMP., Here is te example below.

==================================================================

curl -k -H "X-Auth-Token: $token" -X POST
https://${bmc}/redfish/v1/EventService/Subscriptions
-d '{"Destination": "snmp://192.168.31.89:162",
"SubscriptionType": "SNMPTrap",
"DeliveryRetryPolicy": "TerminateAfterRetries",
"Protocol": "SNMPv2c"}'
{
"@message.ExtendedInfo": [
{
"@odata.type": "#Message.v1_0_0.Message",
"Message": "The resource has been created successfully",
"MessageArgs": [],
"MessageId": "Base.1.8.1.Created",
"MessageSeverity": "OK",
"Resolution": "None"
}
]
}

==================================================================

For the SNMP trap details we have defined our own MIB , Does Redfsh mandates the MIB? , that a particular MIB to be implemented by the redfish implementation.?

Or it is up to the implementation that they can define and implement their own MIB and use the redfish to configure the trap configuration(eg: where to send the trap, retry policy etc).

Thanks

Ratan