RFC 3420 Internet Media Type message/ipfrag November 2002 If the message/sipfrag part contains a body, it MUST also contain the appropriate header fields describing that body (such as Content- Length) as required by Section 7.4 of [1] and the null-line separating the header from the body. 3. Examples 3.1 Valid message/sipfrag parts This section uses a vertical bar and a space to the left of each example to illustrate the example's extent. Each line of the message/sipfrag element begins with the first character after the "|" pair. The first two examples show that a message/sipfrag part can consist of only a start line. | INVITE sip: SIP/2.0 or | SIP/2.0 603 Declined The next two show that Subsets of a full SIP message may be represented. | REGISTER sip:atlanta.com SIP/2.0 | To: sip: | Contact: [email protected]>;q=0.9, | [email protected]>;q=0.1 | SIP/2.0 400 Bad Request | Warning: 399 atlanta.com Your Event header field was malformed A message/sipfrag part does not have to contain a start line. This example shows a part that might be signed to make assertions about a particular message. (See [6].) | From: Alice [email protected]> | To: Bob [email protected]> | Contact: [email protected]> | Date: Thu, 21 Feb 2002 13:02:03 GMT | Call-ID: a84b4c76e66710 | Cseq: 314159 INVITE Sparks Standards Track