：CreateTrafficMarkingPolicy

The operation that you want to perform. Set the value to CreateTrafficMarkingPolicy.

The client token that is used to ensure the idempotence of the request.

You can use the client to generate the value, but you must make sure that it is unique among different requests. ClientToken can contain only ASCII characters.

Specifies whether only to precheck the request. Valid values:

• true: checks the request but does not create the traffic marking policy. The system checks the required parameters, the request format, and the service limits. If the request fails to pass the precheck, an error message is returned. If the request passes the precheck, the DryRunOperation error code is returned.
• false (default): sends the request. If the request passes the check, the traffic marking policy is created.

The ID of the transit router.

The name of the traffic marking policy.

The name must be 2 to 128 characters in length, and can contain letters, digits, underscores (_), and hyphens (-). The name must start with a letter.

The description of the traffic marking policy.

The description must be 2 to 128 characters in length, and can contain letters, digits, underscores (_), and hyphens (-). The description must start with a letter.

The priority of the traffic marking policy. Valid values: 1 to 100.

The priority value of each traffic marking policy on a transit router must be unique. A smaller value indicates a higher priority.

The differentiated services code point (DSCP) value to be added to packets that match the traffic classification rule. Valid values: 0 to 63.

The DSCP value of each traffic marking policy on a transit router must be unique.

The DSCP value that is used to match packets. Valid values: 0 to 63.

The traffic classification rule matches the packets that contain the specified DSCP value. If you do not set this parameter, packets are considered a match regardless of the DSCP value.

You can create up to 50 traffic classification rules at a time. You can specify a DSCP value for each traffic classification rule.

The destination CIDR block that is used to match packets.

The traffic classification rule matches the packets whose destination IP addresses fall within the specified destination CIDR block. If you do not set this parameter, packets are considered a match regardless of the DSCP value.

You can create up to 50 traffic classification rules at a time. You can specify a destination CIDR block for each traffic classification rule.

The description of the traffic classification rule.

You can create up to 50 traffic classification rules at a time. You can specify a description for each traffic classification rule.

The description must be 2 to 128 characters in length, and can contain letters, digits, underscores (_), and hyphens (-). The description must start with a letter.

The protocol that is used to match packets.

Valid values: HTTP, HTTPS, TCP, UDP, SSH, and Telnet. For more information, log on to the CEN console.

You can create up to 50 traffic classification rules at a time. You can specify a protocol for each traffic classification rule.

The destination port range that is used to match packets. Valid values: -1 and 1 to 65535.

The traffic classification rule matches the packets whose destination ports fall within the destination port range. If you do not set this parameter, packets are considered a match regardless of the DSCP value.

You can enter up to two port numbers. Take note of the following rules:

• If you enter only one port number such as 1, the system matches the packets whose destination port is 1.
• If you enter two port numbers such as 1 and 200, the system matches the packets whose destination ports fall within 1 to 200.
• If you enter two port numbers and one of them is -1, the other port number must also be -1. In this case, packets with all destination ports are matched.

You can create up to 50 traffic classification rules at a time. You can specify a destination port range for each traffic classification rule.

The source CIDR block that is used to match packets.

The traffic classification rule matches the packets whose source IP addresses fall within the specified source CIDR block. If you do not set this parameter, packets are considered a match regardless of the source IP address.

You can create up to 50 traffic classification rules at a time. You can specify a source CIDR block for each traffic classification rule.

The source port range that is used to match packets. Valid values: -1 and 1 to 65535.

The traffic classification rule matches the packets whose source ports fall within the source port range. If you do not set this parameter, packets are considered a match regardless of the source port.

You can enter up to two port numbers. Take note of the following rules:

• If you enter only one port number such as 1, the system matches the packets whose source port is 1.
• If you enter two port numbers such as 1 and 200, the system matches the packets whose source ports fall within 1 to 200.
• If you enter two port numbers and one of them is -1, the other port number must also be -1. In this case, packets with all source ports are matched.

You can create up to 50 traffic classification rules at a time. You can specify a source port range for each traffic classification rule.

The name of the traffic classification rule.

You can create up to 50 traffic classification rules at a time. You can specify a name for each traffic classification rule.

The name must be 2 to 128 characters in length, and can contain letters, digits, underscores (_), and hyphens (-). The name must start with a letter.

The ID of the traffic marking policy.

The ID of the request.