BACnet-Reject-PDU and BACnet-Abort-PDU to be supported

[duffy-ocraven]

BACnet-Reject-PDU ::= SEQUENCE {
 	pdu-type 		Unsigned (0..15), -- high four bits, 0x60 for this PDU type
 	reserved 			Unsigned (0..15), -- low four bits, always 0 for this PDU type
 	original-invokeID 	Unsigned (0..255), -- matching what was in the ConfirmedRequest to which this is response
 	reject-reason 		One octet containing the BACnetRejectReason

and the BACnetRejectReason enumerated is:{
other (0),
buffer-overflow (1),
inconsistent-parameters (2),
invalid-parameter-data-type (3),
invalid-tag (4),
missing-required-parameter (5),
parameter-out-of-range (6),
too-many-arguments (7),
undefined-enumeration (8),
unrecognized-service (9),

BACnet-Abort-PDU ::= SEQUENCE {
	pdu-type		Unsigned (0..15), -- high 4 bits, thus 0x70 or 0x71 for this PDU type
	server			Unsigned (0..15) -- BOOLEAN 0 == FALSE, 1 == TRUE,
	original-invoke-id	Unsigned (0..255), -- matching what was in the ConfirmedRequest to which this is response
	abort-reason		One octet containing the BACnetAbortReason

and the BACnetAbortReason enumerated is: {
other (0),
buffer-overflow (1),
invalid-apdu-in-this-state (2),
preempted-by-higher-priority-task (3),
segmentation-not-supported (4),
security-error (5),
insufficient-security (6),
window-size-out-of-range (7),
application-exceeded-reply-time (8),
out-of-resources (9),
tsm-timeout (10),
apdu-too-long (11),

Note that unlike the BACnet-Error-PDU, in these two the ServiceChoice is not present.

[NothinRandom]

@duffy-corelight, latest update and enumeration addresses this issue. Like the others, I'll let the customer close the issue if deemed as satisfied.