On Wed, 2002-05-29 at 07:56, Sachin K wrote: > > ok, let me try to put it this way, > > as given in RFC 3204, if i want to carry QSIG information between gateways, > i have support MIME extensions (RFC 2046) in my sip stack, that means i have > to update my parser (ABNF grammar) to understand this SIP message and encode > the message in the same manner. > > my question is, > > 1) which grammar i have to include in my parser ?? (everything which is > mentioned in RFC 2046 ??)
Pieces of 2045, 6 and maybe 7. You need to be able to survive receiving an arbitrary multipart mime body. If transport of QSIG is the only thing you care about, you only need understand (parse) the basic headers and any called out in 3204. Be aware that there are other contexts in which you will encounter multipart. Take a look at the S/MIME section in bis-09 for example. > > 2) if the QSIG (MIME part) is more in size, how should i send it ?? More in size than what? If its too big to go into a single UDP datagram, you must send it over a stream oriented protocol like TCP. > > > TIA, > Sachin K > > > On Wednesday 29 May 2002 06:07 pm, Christer Holmberg wrote: > > Hi, > > > > I am not sure I understood your question correct, but you are not > > allowed to fragment SIP messages on the application level. > > > > Regards, > > > > Christer Holmberg > > Ericsson Finland > > > > Sachin K wrote: > > > Hi, i have a sip stack, which is compliant to RFC 2543 bis 6. now if i > > > have to support MIME types ( like ISUP and QSIG RFC 3204 ) in my > > > stack, do i have to completely implement MIME RFC 2046 ?? in that case > > > can anyone plz give me an example of fragmenting the SIP message > > > containing QSIG information ? andhow fragmented SIP message is > > > assembled at the other end ?? TIA Sachin K > > > > > > > > > -------------------------------------------------------------- > > > Dexcel Electronics Designs (P) Ltd., Bangalore, India > > -------------------------------------------------------------- > Dexcel Electronics Designs (P) Ltd., Bangalore, India > > > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
