Re: [spfbis] WGLC: draft-ietf-spfbis-4408bis-14

"Murray S. Kucherawy" <superuser@gmail.com> Wed, 17 April 2013 03:02 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: spfbis@ietfa.amsl.com
Delivered-To: spfbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6B7E21F8E9A for <spfbis@ietfa.amsl.com>; Tue, 16 Apr 2013 20:02:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.932
X-Spam-Level:
X-Spam-Status: No, score=-2.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 vTB-nGIa7eFG for <spfbis@ietfa.amsl.com>; Tue, 16 Apr 2013 20:02:53 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 3871821F8526 for <spfbis@ietf.org>; Tue, 16 Apr 2013 20:02:53 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id z2so914863wey.1 for <spfbis@ietf.org>; Tue, 16 Apr 2013 20:02:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=hW/2GcS04d6Utw8O0ZMD0Mi0jy8f/hHRxyM2b/zYSB0=; b=iVOJvf0PcYQyrI9NvxO8puQQPQ67Vvg7Ko3ojL72YGwymzFc8U/AMzVVo78NVk0fAq tV2xFs3LaOTD029ReniaHXfAaiFYWFf7dphVQBw8JQSdLf7BuMNuUW5nT4WiRof10nqn WYGdVts2QsAJAc4ynup0CS5pxSpsc2APjTHM6a4S9nuxJvKQDe0xws4t/Zu3TtodhGN7 nlEFqWZMOPRPR5pRz997ppVW1cUSAauM5b/gg8pC+40YCldxk4uMqSReA3EiBcJCmZ2M NRSwvvzx8+rY6WYOZsvv+vFSvpxZuvEeHkhN72pn2cL44tixiU3jryvNa/e3ovhd7wot p0cQ==
MIME-Version: 1.0
X-Received: by 10.180.84.162 with SMTP id a2mr7663694wiz.14.1366167771916; Tue, 16 Apr 2013 20:02:51 -0700 (PDT)
Received: by 10.180.36.176 with HTTP; Tue, 16 Apr 2013 20:02:51 -0700 (PDT)
In-Reply-To: <CAJ4XoYegUT5WRmD_OuimM2Rzx9FBrbhMH2vqkAQx-7o3gnuVeA@mail.gmail.com>
References: <20130409062431.GK24624@mx1.yitter.info> <CAJ4XoYd2r7=Vd3Ge4JZie=Hz6+JupDR-OkuSRzRkyuk+5KHrKA@mail.gmail.com> <7FE87BAF-B202-4CD5-B7BA-EDABE151E142@eudaemon.net> <CAJ4XoYegUT5WRmD_OuimM2Rzx9FBrbhMH2vqkAQx-7o3gnuVeA@mail.gmail.com>
Date: Tue, 16 Apr 2013 20:02:51 -0700
Message-ID: <CAL0qLwasgmtFRf3N-wF5UDdT6dhdqHT7b4fpnj=xXtKUqh0LiA@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Dotzero <dotzero@gmail.com>
Content-Type: multipart/alternative; boundary="f46d04427194bfb47b04da85b83f"
Cc: "spfbis@ietf.org" <spfbis@ietf.org>, Tim Draegen <tim@eudaemon.net>, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [spfbis] WGLC: draft-ietf-spfbis-4408bis-14
X-BeenThere: spfbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SPFbis discussion list <spfbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spfbis>, <mailto:spfbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spfbis>
List-Post: <mailto:spfbis@ietf.org>
List-Help: <mailto:spfbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spfbis>, <mailto:spfbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Apr 2013 03:02:54 -0000

Apologies; I do plan to spend time on it this week.  I've been buried with
$DAYJOB, illness, travel, etc. lately and I'm quite behind on non-trivial
IETF matters.


On Tue, Apr 16, 2013 at 7:42 PM, Dotzero <dotzero@gmail.com> wrote:

> On Tue, Apr 16, 2013 at 10:10 PM, Tim Draegen <tim@eudaemon.net> wrote:
> > On Apr 16, 2013, at 10:08 PM, Dotzero <dotzero@gmail.com> wrote:
> >> I've reviewed the draft and have one "nit" and one question/comment:
> >>
> >> In the Abstract the use of ADMD should be followed with
> >> (ADministrative Management Domains)
> >>
> >>   Email on the Internet can be forged in a number of ways.  In
> >>   particular, existing protocols place no restriction on what a sending
> >>   host can use as the "MAIL FROM" of a message or the domain given on
> >>   the SMTP HELO/EHLO commands.  This document describes version 1 of
> >>   the Sender Policy Framework (SPF) protocol, whereby an ADMD can
> >>   explicitly authorize the hosts that are allowed to use its domain
> >>   names, and a receiving host can check such authorization.
> >
> > Oh dude!   Get out of my head!   I'm reviewing the document (about 5
> minutes in) and this was my first note!
>
> At least what I found is relatively minor in the greater scheme of
> things. Reading the whole thing thoughtfully is so different from
> going back and forth on individual items.
>
> Mike
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis
>