Ummm. I don't believe this is part of the RFC, nor should it be. I would be careful with limits that you impose on these fields. The issue is not so much compliance with the standard, but interoperability. In any case, this should probably be moved to the SIP implementers list.
/sean --- Prabhas Sinha <[EMAIL PROTECTED]> wrote: > I think this information is available in the RFC , I > had read it long time > back but I'll put it here for you: > To: (50 bytes for name/address-space) + (8 bytes > for tag) = 58 bytes > From: (50 bytes for name/address-space) + (8 bytes > for tag) = 58 bytes > Content Length: 12 bytes > Call-ID: 50 bytes > Content Encoding: 50 bytes > Content Type: 50 bytes > CSeq: 12 bytes > Via: 75 bytes > > If there is some changes to it then somebody please > correct me. > Moreover, please send your questions to > [EMAIL PROTECTED] from now onwards. > > > Thanks, > Prabhas > > ----- Original Message ----- > From: "Vladica Stanisic" > <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, March 25, 2002 3:39 PM > Subject: [Sip] header fields' sizes in SIP > > > > I am a student working on SIP designing a control > memory. > > Header fields' sizes in SIP are not defined since > SIP is text based > protocol. > > Can anybody give me guidelines about sizes of > mandatory header fields > > > > Allow > > Call-ID > > Contact > > Content-Length > > Content-Type > > From > > Proxy-Authenticate > > Supported > > To > > Unsupported > > Via > > WWW-Authenticate > > > > Thanks > > -- > > Vladica Stanisic > > Research Assistant > > North Carolna State University > > e-mail:[EMAIL PROTECTED] ===== Sean Olson <[EMAIL PROTECTED]> __________________________________________________ Do You Yahoo!? Yahoo! Movies - coverage of the 74th Academy Awards� http://movies.yahoo.com/ _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
