Value,Description,Reference,Change Controller
0,None (used by client in Request),[RFC-ietf-ippm-capacity-protocol-25],IETF
1,Acknowledgment,[RFC-ietf-ippm-capacity-protocol-25],IETF
2,Bad Protocol Version,[RFC-ietf-ippm-capacity-protocol-25],IETF
3,Invalid Jumbo datagram option,[RFC-ietf-ippm-capacity-protocol-25],IETF
4,Unexpected Authentication in Setup Request,[RFC-ietf-ippm-capacity-protocol-25],IETF
5,Authentication missing in Setup Request,[RFC-ietf-ippm-capacity-protocol-25],IETF
6,Invalid authentication method,[RFC-ietf-ippm-capacity-protocol-25],IETF
7,Authentication failure,[RFC-ietf-ippm-capacity-protocol-25],IETF
8,Authentication time is invalid in Setup Request,[RFC-ietf-ippm-capacity-protocol-25],IETF
9,No Maximum test Bit rate specified,[RFC-ietf-ippm-capacity-protocol-25],IETF
10,Server Maximum Bit rate exceeded,[RFC-ietf-ippm-capacity-protocol-25],IETF
11,MTU option does not match server,[RFC-ietf-ippm-capacity-protocol-25],IETF
12,Multi-connection parameters rejected by server,[RFC-ietf-ippm-capacity-protocol-25],IETF
13,Connection allocation failure on server,[RFC-ietf-ippm-capacity-protocol-25],IETF
14-239,Unassigned,,
240-249,Reserved for Experimental Use,[RFC-ietf-ippm-capacity-protocol-25],IETF
250-254,Reserved for Private Use,[RFC-ietf-ippm-capacity-protocol-25],IETF
255,Reserved,[RFC-ietf-ippm-capacity-protocol-25],IETF