Re: [sip-clf] [apps-discuss] AppsDir review of draft-ietf-sipclf-format-05

Gonzalo Salgueiro <gsalguei@cisco.com> Thu, 09 February 2012 14:44 UTC

Return-Path: <gsalguei@cisco.com>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 947DB21F857F for <sip-clf@ietfa.amsl.com>; Thu, 9 Feb 2012 06:44:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.368
X-Spam-Level:
X-Spam-Status: No, score=-10.368 tagged_above=-999 required=5 tests=[AWL=0.230, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CjqweTin+T3T for <sip-clf@ietfa.amsl.com>; Thu, 9 Feb 2012 06:44:15 -0800 (PST)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by ietfa.amsl.com (Postfix) with ESMTP id 87F2C21F8567 for <sip-clf@ietf.org>; Thu, 9 Feb 2012 06:44:15 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q19EiDew029016 for <sip-clf@ietf.org>; Thu, 9 Feb 2012 09:44:14 -0500 (EST)
Received: from rtp-gsalguei-8714.cisco.com (rtp-gsalguei-8714.cisco.com [10.116.61.53]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q19EiCec025302; Thu, 9 Feb 2012 09:44:12 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-20-451617382
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <alpine.OSX.2.02.1202090843230.4366@mac-allocchio3.elettra.trieste.it>
Date: Thu, 9 Feb 2012 09:44:11 -0500
Message-Id: <4FB65F28-DC68-4240-99F9-E99C457968A8@cisco.com>
References: <alpine.OSX.2.02.1201161423200.36734@mac-allocchio3.garrtest.units.it> <DB153777-972C-43DC-AF92-0D03052A9226@cisco.com> <alpine.OSX.2.02.1202090843230.4366@mac-allocchio3.elettra.trieste.it>
To: Claudio Allocchio <Claudio.Allocchio@garr.it>
X-Mailer: Apple Mail (2.1084)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>, apps-discuss@ietf.org, draft-ietf-sipclf-format.all@tools.ietf.org
Subject: Re: [sip-clf] [apps-discuss] AppsDir review of draft-ietf-sipclf-format-05
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2012 14:44:16 -0000

Hi Claudio - 

On Feb 9, 2012, at 2:47 AM, Claudio Allocchio wrote:

> Hello all!
> 
>>> * Section "3. Document Conventions"
>>> 
>>> The authors have decided "For the sake of clarity and completeness" to quote a full section of RFC4475 into this document. However there were quite long discussions in the Apps Dir in other reviews if this quoting practice is appropriate or not, because it can lead to discrepacies, when the quoted document is updated or obsoleted, resuing in confusion for the readers who just trust the quoted text without checking the state of the referenced document. I would suggest, as in the other cases, NOT to quote the external text, but to use an explicit external reference only, urging the reader to check that "for the sake of clarity".
>> 
>> I agree with the position but in this particular case I'm of the mind that removing that text and referencing the RFC diminishes the effectiveness of that section. It is my preference to leave the quoted text (which is very short) embedded in this document as it is critical to understanding the notation used throughout the document.
> 
> maybe a possible compromise is to quote the text, as is now, but to add a small note which reminds the reader to check the update/obsoletes status of RFC4475? ;-)

I could add that but bear in mind that I only care about the quoted text dealing with formatting rules from RFC4475 and nothing else. So whether it gets updated or obsoleted is irrelevant in this case. In fact, if it gets updated and it affects the formatting guidelines I quoted then I don't want to reference it at all since it is no longer useful or significant to this draft.
> 
>>> * Section "4. Format"
>>> 
>> This is something that we have discussed and have not found an elegant solution for. While there are maintenance risks it was thought to be very valuable to display the pertinent portion of the complete CLF within the section where that was discussed. I'll do my best to ensure that they are all copied over properly from Figure 1.
> 
> as I said, it is a Nit... thanks for taking some time in thinking about it.

Thanks to you for your careful review.

Warm Regards,

Gonzalo

> 
> have a nice day!
> 
> 
> ------------------------------------------------------------------------------
> Claudio Allocchio             G   A   R   R          Claudio.Allocchio@garr.it
>                        Senior Technical Officer
> tel: +39 040 3758523      Italian Academic and       G=Claudio; S=Allocchio;
> fax: +39 040 3758565        Research Network         P=garr; A=garr; C=it;
> 
>           PGP Key: http://www.cert.garr.it/PGP/keys.php3#ca
>