EV seems to not accept the SupportedAppProtocolRes

[TobiSchneider]

Hello,

I am currently testing on an EV, which seems to be closing its TCP-Socket after receiving my SupportedAppProtocolRes. I can see some differences in the response XML compared to the examples in din70121 and iso15118. Like the additional name spaces and the "standalone="yes"". Is there something I am overlooking or has this behavior been seen before?

Here is the receive and response :

Received EXI stream: 8000DBAB9371D3234B71D1B981899189D191818991D26B9B3A232B30020000040040

 <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
 <ns2:supportedAppProtocolReq xmlns:ns6="urn:iso:15118:2:2013:MsgDef"
     xmlns:ns5="http://www.w3.org/2000/09/xmldsig#"
     xmlns:ns7="urn:iso:15118:2:2013:MsgBody"
     xmlns:ns2="urn:iso:15118:2:2010:AppProtocol"
     xmlns:ns4="urn:iso:15118:2:2013:MsgDataTypes"
     xmlns:ns3="urn:iso:15118:2:2013:MsgHeader">
     <AppProtocol>
         <ProtocolNamespace>urn:din:70121:2012:MsgDef</ProtocolNamespace>
         <VersionNumberMajor>2</VersionNumberMajor>
         <VersionNumberMinor>0</VersionNumberMinor>
         <SchemaID>1</SchemaID>
         <Priority>1</Priority>
     </AppProtocol>
 </ns2:supportedAppProtocolReq>

EXI encoded SupportedAppProtocolRes: 80400040 Base64 encoded SupportedAppProtocolRes: gEAAQA==

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:supportedAppProtocolRes xmlns:ns6="urn:din:70121:2012:MsgDef"
    xmlns:ns5="http://www.w3.org/2000/09/xmldsig#"
    xmlns:ns7="urn:din:70121:2012:MsgBody"
    xmlns:ns2="urn:iso:15118:2:2010:AppProtocol"
    xmlns:ns4="urn:din:70121:2012:MsgDataTypes"
    xmlns:ns3="urn:din:70121:2012:MsgHeader">
    <ResponseCode>OK_SuccessfulNegotiation</ResponseCode>
    <SchemaID>1</SchemaID>
</ns2:supportedAppProtocolRes>