Peoples, As I go through the documentation process, and we finalize some of the last open items, we will be sending e-mail requesting approval. It would be appreciated if you could please make it a priority to provide feedback as soon as possible so we can get resolution and move forward. Henrik has requested the removal of "globalReservationId" from the GenericConfirmedType since it is a convenience element only. I have no issue with the proposed change but want to make sure no design teams are using the capabilities. At the bottom of the e-mail is the component that will be modified. In addition, Henrik has proposed the collapse of the GenericConfirmedType and GenericRequestType to remove the separate type wrapper and make the impacted messages of type ConnectionIdType. For example, the provision message set would not be defined as the following: <xsd:element name="provision" type="tns:ConnectionIdType" /> <xsd:element name="provisionConfirmed" type="tns:ConnectionIdType /> So I am asking for approval on the following two items: 1. Removal of globalReservationId from the GenericConfirmedType. 2. Removal of the GenericConfirmedType and GenericRequestType. Thanks, John <xsd:complexType name="GenericConfirmedType"> <xsd:annotation> <xsd:documentation xml:lang="en"> This is a generic type definition for a "Confirmed" messages in response to a successful processing of a previous "Request" message such as provision, release, and terminate. Elements: globalReservationId - An optional global reservation id that was originally provided in the reserve request. connectionId - The Provider NSA assigned connectionId for this reservation request. This value will be unique within the context of the Provider NSA. </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:element name="globalReservationId" type="tns:GlobalReservationIdType" minOccurs="0" /> <xsd:element name="connectionId" type="tns:ConnectionIdType" /> </xsd:sequence> </xsd:complexType>