M2-101-UM_v1-1_MIDI-CI_Specification
MIDI-CI defines an architecture that allows Devices with bidirectional communication to agree to use extended MIDI capabilities beyond those defined in MIDI 1.0, while carefully protecting backward compatibility. MIDI-CI features “fall back” mechanisms so that if a Device does not support new features MIDI continues to work as defined by MIDI 1.0. Goals of MIDI-CI design:
Fully backward compatible: supports continued MIDI 1.0 functionality for any Devices that do not recognize extended MIDI features enabled by MIDI-CI.

1. Allow easy configuration between MIDI-CI Devices.
2. Sender can know the capabilities of a Receiver.
3. Sender and Receiver can negotiate auto-configuration details
4. Define method for negotiating choice of Protocol between Devices.
5. Define method for using Profiles.
6. Define method for Discovering, Getting, and Setting a wide range of Device Properties. 

M2-104-UM_v1-0_UMP_and_MIDI_2-0_Protocol_Specification
This Specification defines two major extensions to the MIDI 1.0 Protocol:

• Universal MIDI Packet (UMP) Format
  UMP can contain all MIDI 1.0 Protocol messages and all MIDI 2.0 Protocol messages in a single, common container definition with a payload format which is intended to be usable in (or easily adaptable for) any standardized or proprietary data transport.
• MIDI 2.0 Protocol
  The MIDI 2.0 Protocol is an extension of the MIDI 1.0 Protocol. Architectural concepts and semantics remain the same as MIDI 1.0. Compatibility for translation to/from the MIDI 1.0 Protocol is given high priority in the design of the MIDI 2.0 Protocol.