WAP Encoding issue

We have LG certifying their phone against Kannel and they spotted a  
problem which I'm forwarding to the list. Might be a bug.
This is against current CVS.


<---snip---->
Dear Kannel, Jenny and Technical support team

The reason we got failed in the case wml/events/tasks/go/20, using  
Kannel is
the G/W can't handle multipart header in encoding v 1.4. And there is  
also problem with Encoding-Version negotiation
on your gateway.


Please refer those log files which captured by ethereal and
WSP spec, WAP-230-WSP-20010705-a.pdf Section 8.5.2 Multipart Header.

K_CL_go20 is tested with connection mode CL(ConnectionLess mode), and  
K_CO_go20 is
done with CO(Connection Oriented mode)

What's your gateway really support encoding version?
Our device support version 1.4.

In the file K_CO_go20, see the packet NO 3, you can see the Encoding  
version 1.4.
And the packet No 4, your gateway gave us, encoding version 1.4.
Then, please see the Packet No 14 which is used by POST method. You  
can see the content
"Media Type: application /vnd.wap.multipart.form-data(45 bytes)."  
which is encoded by version 1.4
As Spec explained about Multipart Header, "if the peer implementation  
- (your gateway) supports an encoding version
later than 1.3, the sender SHOULD set the nEntries filed to 0.".
That's why multipart data starts with "00". But you can see the next  
packet, I got failed.

Now see the log file, K_CL_go20, after encoding version negotiating,  
we send message as encoded by v 1.3.
In the packet No 5, content "Media Type: application / 
vnd.wap.multipart.form-data(45 bytes)." is encoded by v 1.3.
That is why starts with "02" like spec describes "The nEntries field  
was used to specify the number of entries in the
multipart entity in WAP implementations usingencoding version 1.3 or  
earlier."
This one got passed.

I have no idea why your gateway gave us different encoding version  
depending on connection mode.
Finally, please see the last file,  
"internalKannel_CO_go20_encoding_v_1_3"
We can't access your gateway now, so we use our local G/W which is  
also Kannel.
We changed our broswer's encoding version 1.3. You can see the Packet  
No 1 and No 3.
And see the Packet No 42 as above.
This time we got passed.

So, It's  Kannel can't handle multipart-header in encoding version  
1.4  as spec describes and
there is encoding version negotiation problem which is different  
depending on connection mode.
Please check this problem.

Best regards,

JinSeok Choi

-----------------------------------------------------------------
Choi JinSeok   Research Engineer
LG Electronics Inc.
3G Mobile Handset Development Gr.
Mobile Communication Technology Research Lab.
Mobile : +82-10-9620-0405
Phone  : +31-450-7318
------------------------------------------------------------------


<---END SNIP--->