Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 152A43A6877; Mon, 22 Dec 2008 20:40:13 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D97B83A63EC for ; Mon, 22 Dec 2008 20:40:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.596 X-Spam-Level: X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, WEIRD_PORT=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lIQCRnKhWuCW for ; Mon, 22 Dec 2008 20:40:11 -0800 (PST) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by core3.amsl.com (Postfix) with ESMTP id E28003A6877 for ; Mon, 22 Dec 2008 20:40:10 -0800 (PST) Received: by yx-out-2324.google.com with SMTP id 8so1322235yxg.49 for ; Mon, 22 Dec 2008 20:40:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=tm/lLFy5ZDqOOpWXlY32XhKg1KDcqUsp7PYNivl9XD4=; b=lCUvaToF8IGhYnPbxZb1U+QNrMwjBxV2zFTEz6YOOmDqwrZW96b2cgLZ2IlaN7jaOS C1U2IiOS2kW0ynFxxYNUZMwnderrvvZanvA0VQU8GIN9l2hze1bClRusTbf60u3sD4rR 3w4lc4UTagAN7nfVglyT5pWY8GJKntA+PwrIk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=Y2Jf//E47LR1zEj3y4sWGfJF/rKGU0hyNwvVy8PMWIyNYV4UPBQfn2Xgc1rUI17YhL XDORn7e/fP9HZYQgtl2TzUI5PN9xZRp4NO++zipPUE3ig1heuCQSAfD/ozsiDUjwuog9 hfZvQI+dw07Zp89mOT4J0L2ot6hNiHY+LCw04= Received: by 10.151.150.20 with SMTP id c20mr13202748ybo.139.1230007200652; Mon, 22 Dec 2008 20:40:00 -0800 (PST) Received: by 10.151.135.1 with HTTP; Mon, 22 Dec 2008 20:40:00 -0800 (PST) Message-ID: <8cde4ec40812222040v461c79e0y18d4ced0f1a9a57d@mail.gmail.com> Date: Tue, 23 Dec 2008 12:40:00 +0800 From: "Stephen Guo" To: sip@ietf.org MIME-Version: 1.0 Subject: [Sip] Is this a valid request? X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0629557713==" Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org --===============0629557713== Content-Type: multipart/alternative; boundary="----=_Part_95629_19059394.1230007200636" ------=_Part_95629_19059394.1230007200636 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi all, Please have a look, is following request valid? There is a horizontal tab preceding each extra line in To header. INVITE sip:tester@192.168.3.104 SIP/2.0 CSeq: 1 INVITE Via: SIP/2.0/UDP 192.168.3.101:5068 ;branch=z9hG4bK68aj5t30nezhwfkv921lsbuiq7coxrdy From: "Negativa" ;tag=somefromtagval Call-ID: 6tasnymb8du9e2xp045ohz3lwkcr1vfq@TheKlatchianHead To: "Negativa" Contact: Max-Forwards: 70 Content-Type: application/sdp Content-Length: 389 (SDP not shown) *According RFC 3261 section 7.3.1 Header Field Format* description, "Header fields can be extended over multiple lines by preceding each extra line with at least one SP or horizontal tab (HT)", above request is valid, right? -- Best Regards, Stephen ------=_Part_95629_19059394.1230007200636 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi all,
    Please have a look, is following request valid?
There is a horizontal tab preceding each extra line in To header.

INVITE sip:tester@192.168.3.104 SIP/2.0
CSeq: 1 INVITE
Via: SIP/2.0/UDP 192.168.3.101:5068;branch=z9hG4bK68aj5t30nezhwfkv921lsbuiq7coxrdy
From: "Negativa" <sip:tester:password@192.168.3.104:5060>;tag=somefromtagval
Call-ID: 6tasnymb8du9e2xp045ohz3lwkcr1vfq@TheKlatchianHead
To:    
   
   
   
    "Negativa" <sip:tester:password@192.168.3.104:5060>
Contact: <sip:tester:password@192.168.3.104:5060>
Max-Forwards: 70
Content-Type: application/sdp
Content-Length: 389

(SDP not shown)

According RFC 3261 section 7.3.1 Header Field Format description, "Header fields can be extended over multiple lines by preceding each extra line with at least one SP or horizontal tab (HT)", above request is valid, right?

--
Best Regards,
Stephen
------=_Part_95629_19059394.1230007200636-- --===============0629557713== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip --===============0629557713==--