Url tokenization information in the mdl files

:::(Error) (For Internal Use)
We did not publish this to the GA RN and Log Shipping docs because it is customer specific. There will be different sets of MDL fields per customer. We inserted a general statement about URL tokenization in the Log Shipping document. I created a new doc for this information. Are there other customers besides iTV that we've already implemented custom URL tokenization for? Is there any value in creating/maintaining this doc for internal use, or is this info already curated somewhere else by dev or ops?
:::

When custom URL tokenization is implemented for a customer, the solution includes custom MDL fields delivered via Log Shipping. The specific MDL fields for each customer are described below.

Detailed information about all the MDL fields.{target=_blank}

iTV

Field	Data Type	Example Value(s)	Description	Status
mip_action	String	log, block	Indicates the match ip setting, log or block. The setting is defined by the `mip` parameter value (block or log) in the request's JWT payload. If the `mip` parameter is not present in the JWT payload, log is applied.	In production.
JWT_IP	String	???	The obfuscated JWT IP address.*	Will not be in production before 8.2 is released. Maybe later.
TokenizationIpPlaintext	String	???	The JWT IP address in plain text, if the PLL rules allow for it to be passed as plain text.*	Will not be in production before 8.2 is released. Maybe later.

The Pll rules determine whether or not the JWT IP address is obfuscated. If it is obfuscated, it is logged in the JWT_IP field. If it is allowed to be passed in plain text, it is logged in the TokenizationIpPlaintext field.