Re: [Gen-art] [spfbis] Gen-ART LC review of draft-ietf-spfbis-experiment-09.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 07 June 2012 07:26 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FC6821F85EA; Thu, 7 Jun 2012 00:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.671
X-Spam-Level:
X-Spam-Status: No, score=-101.671 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 gNgrPI2xtTzG; Thu, 7 Jun 2012 00:26:40 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id A1D8A21F8541; Thu, 7 Jun 2012 00:26:39 -0700 (PDT)
Received: by eekd4 with SMTP id d4so109452eek.31 for <multiple recipients>; Thu, 07 Jun 2012 00:26:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=zpbe70X/utG+0dbvqr9dC6TknxtCoG3EDikz6M0giVo=; b=p5+A/c8tBHoCG1nMLC0zOo8g8CeFSjWpGu+qQE4rPrvHWIKdL6c/TZq5n8pWZyTArL fqv9/bZ9IFh0Kn0cXZuw6sY9ZCol7BxVxJsWekYToHVIL54EDPyfovZDSEmYTvQol9kz Mmpv+baPQXkLJqPNEVB2mTMfmoh6vofdWUMCt7irqC0B99+otrJwJWDkjgvea7srIreO 6mq/DzQ9uK7IZ9zhz3+fqHwPY351v/KclFHmRt+EPyzoge+FmvB5xD2dpSxTA8GaUwp9 hfiQbl9wojaskebuhwNoCcdFn6GASLN/NRXkGB3smgpQFtHc4nB7Vbq/jdNp3mgPLBir ghdw==
Received: by 10.14.97.77 with SMTP id s53mr522331eef.104.1339053998746; Thu, 07 Jun 2012 00:26:38 -0700 (PDT)
Received: from [192.168.1.66] (host-2-102-217-102.as13285.net. [2.102.217.102]) by mx.google.com with ESMTPS id c13sm7585924eeb.7.2012.06.07.00.26.36 (version=SSLv3 cipher=OTHER); Thu, 07 Jun 2012 00:26:37 -0700 (PDT)
Message-ID: <4FD057A2.5060909@gmail.com>
Date: Thu, 07 Jun 2012 08:26:26 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
References: <4FCF32B5.7010102@gmail.com> <6.2.5.6.2.20120606081749.0a94ad98@elandnews.com> <CAC4RtVCXvE0htGxpqQfCKiTzgdnofjzLM6SAQz=kwTBu8Ako4g@mail.gmail.com> <6.2.5.6.2.20120606122623.088e6170@elandnews.com>
In-Reply-To: <6.2.5.6.2.20120606122623.088e6170@elandnews.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: spfbis@ietf.org, General Area Review Team <gen-art@ietf.org>, Barry Leiba <barryleiba@computer.org>, draft-ietf-spfbis-experiment.all@tools.ietf.org
Subject: Re: [Gen-art] [spfbis] Gen-ART LC review of draft-ietf-spfbis-experiment-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 07:26:40 -0000

Restoring the Gen-ART CC since we need the discussion in the archive.

See below...

On 2012-06-06 20:43, S Moonesamy wrote:
> Hi Barry,
> At 12:23 06-06-2012, Barry Leiba wrote:
>> Leaving the entire message below, because Brian doesn't appear to have
>> been copied on it.
> 
> I didn't copy Brian as I thought it better to wait for a WG reply.
> 
>> I don't see why it's not right at all, and please don't make the
>> mistake of thinking that an informational document doesn't have
>> normative references.  I think the original Experimental docs are
>> *absolutely* normative references for this document, and i see nothing
>> wrong with that at all.
> 
> The comment posted by Dave is at
> http://www.ietf.org/mail-archive/web/spfbis/current/msg01426.html
> 
> I generally use the following for guidance:
> 
>   "Normative references specify documents that must be read to
>    understand or implement the technology in the new RFC, or
>    whose technology must be present for the technology in the
>    new RFC to work."

Exactly. This draft does not define new technology, is not a
technical specification (cf RFC 2026), and therefore does not
need normative references.

    Brian

> 
> Regards
> S. Moonesamy
> 
> .
>