The RTMv2 API defines several simple data types. The following table lists these data types.
| Data type | Description | Typedef |
|---|---|---|
| RTM_VIEW_ID, *PRTM_VIEW_ID | Identifies a particular view. | INT |
| DWORD RTM_VIEW_SET, *PRTM_VIEW_SET | Identifies a set of views; expressed as a mask. | DWORD |
| RTM_ENTITY_HANDLE, *PRTM_ENTITY_HANDLE, RTM_DEST_HANDLE, *PRTM_DEST_HANDLE, RTM_ROUTE_HANDLE, *PRTM_ROUTE_HANDLE, RTM_NEXTHOP_HANDLE, *PRTM_NEXTHOP_HANDLE, RTM_ENUM_HANDLE, *PRTM_ENUM_HANDLE, RTM_ROUTE_LIST_HANDLE, *PRTM_ROUTE_LIST_HANDLE, RTM_NOTIFY_HANDLE, *PRTM_NOTIFY_HANDLE | Handles pointing to RTMv2 data. | HANDLE |
| RTM_ENTITY_METHOD_TYPE, *PRTM_ENTITY_METHOD_TYPE | Identifies methods exported by a registered client. | DWORD |
| RTM_ENTITY_EXPORT_METHOD, *PRTM_ENTITY_EXPORT_METHOD | Specifies the common prototype for client methods. | _ENTITY_METHOD |
| RTM_ROUTE_CHANGE_FLAGS, *PRTM_ROUTE_CHANGE_FLAGS | Input and output flags used to specify the state when a route is added or updated. | DWORD |
| RTM_NEXTHOP_CHANGE_FLAGS, *PRTM_NEXTHOP_CHANGE_FLAGS | Output flags used to specify the state when a next hop is added. | DWORD |
| RTM_MATCH_FLAGS, *PRTM_MATCH_FLAGS | Input flags used to specify criteria when matching routes in the routing table. | DWORD |
| RTM_ENUM_FLAGS, *PRTM_ENUM_FLAGS | Identifies enumerations. | DWORD |
| RTM_NOTIFY_FLAGS, *PRTM_NOTIFY_FLAGS | Output flags used to specify which type of notification is being issued; composed as follows: (Change Types | Dests) a client is interested in. | DWORD |
| RTM_EVENT_CALLBACK, *PRTM_EVENT_CALLBACK; | Identifies the callback used to notify clients that a change has occurred in route state or clients registered. | RTM_EVENT_CALLBACK |
Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
