Re: FW: [Gen-art] Gen-ART review of draft-saintandre-rfc4622bis-01

"Vijay K. Gurbani" <vkg@alcatel-lucent.com> Tue, 21 August 2007 18:38 UTC

Return-path: <gen-art-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1INYcQ-000494-0U; Tue, 21 Aug 2007 14:38:22 -0400
Received: from gen-art by megatron.ietf.org with local (Exim 4.43) id 1INYcP-00048z-5E for gen-art-confirm+ok@megatron.ietf.org; Tue, 21 Aug 2007 14:38:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1INYcO-00048r-Ru for gen-art@ietf.org; Tue, 21 Aug 2007 14:38:20 -0400
Received: from ihemail1.lucent.com ([135.245.0.33]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INYcN-0003aW-K3 for gen-art@ietf.org; Tue, 21 Aug 2007 14:38:20 -0400
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l7LIcG7c015363; Tue, 21 Aug 2007 13:38:16 -0500 (CDT)
Received: from [135.185.244.90] (il0015vkg1.ih.lucent.com [135.185.244.90]) by ihmail.ih.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id l7LIcGa20434; Tue, 21 Aug 2007 13:38:16 -0500 (CDT)
Message-ID: <46CB3118.5070307@alcatel-lucent.com>
Date: Tue, 21 Aug 2007 13:38:16 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: FW: [Gen-art] Gen-ART review of draft-saintandre-rfc4622bis-01
References: <20070821175539.GB18815@jabber.org> <46CB2E1D.5050807@stpeter.im>
In-Reply-To: <46CB2E1D.5050807@stpeter.im>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: gen-art@ietf.org, lisa@osafoundation.org
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Errors-To: gen-art-bounces@ietf.org

Peter Saint-Andre wrote:
>>3) In S2.7.2 and S2.8.2, XMPP addresses continue to the next line.
>> Do you need LWS at the beginning of the second line to denote
>> continuation?
> 
> It's not clear to me how best to represent the line breaks. I will
> inquire of this with the RFC Editor.

I do not know of other areas, but at least within the SIP set of
documents in the RAI area, we have a convention: SIP header field
values can be folded onto multiple lines if the continuation line
begins with a LWS.  This includes URIs as well; i.e., a SIP URI
may continue on the next line if the continuation line starts
with a LWS.

Now, I am not sure what the general behavior of URIs is with
respect to line folding; at least rfc3986 (URI: Generic Syntax)
appears to be silent on this topic (a quick search of "folding",
"LWS", "continuation" does not yeild anything in that RFC.)  Maybe
someone from the Apps area can help.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs


_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www1.ietf.org/mailman/listinfo/gen-art