Re: [marf] [apps-discuss] APPSDIR review of draft-kucherawy-marf-source-ports-01

S Moonesamy <sm+ietf@elandsys.com> Fri, 20 April 2012 00:55 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: marf@ietfa.amsl.com
Delivered-To: marf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F070C11E80A1; Thu, 19 Apr 2012 17:55:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level:
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, 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 wfpGhDhQ4dej; Thu, 19 Apr 2012 17:55:11 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DD14F11E8073; Thu, 19 Apr 2012 17:55:11 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.237.193]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q3K0somD027173 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 Apr 2012 17:55:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1334883305; i=@elandsys.com; bh=MBjGV4DN9h3WYRMPscMfJ/JhI+2AhMLqBJkBra6Ik7Q=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1ua+mcEnwvnWSic1exVQe+x8t+Ay97VsFhAOgpNmpbBDBMnfICSI1lGoCW8J/PjfA D1Bs6pWLdnp36xH3mEnwrvf+zlOrZ9mxVWVpAVMpbpQ5qFrsWfBzYxBU1odkh7zHDI ROraOm8PrYosVWmLmdjlTErArjIkLP8CUWuv6eIg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1334883305; i=@elandsys.com; bh=MBjGV4DN9h3WYRMPscMfJ/JhI+2AhMLqBJkBra6Ik7Q=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qCDBmk5FX+irUDI3kJP+2iXovLNOHEO/xYYnhJtmigA/HWQGtsbUWY34FjyHI1ri5 GS3827Fvp8wur75uHJDxNkKIHZ8PnZbKhDAlEwbj+/IAXVf5r3GqaXBWuhGGIcTkJM Jv1NHsgK7bgNsOuxg7o2Tyn51Bh/C4lf7ryp69dg=
Message-Id: <6.2.5.6.2.20120419171013.09a89ba0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 19 Apr 2012 17:54:03 -0700
To: "Murray S. Kucherawy" <msk@cloudmark.com>, apps-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <9452079D1A51524AA5749AD23E0039280FB707@exch-mbx901.corp.cl oudmark.com>
References: <6.2.5.6.2.20120419130040.0b4ee328@elandnews.com> <9452079D1A51524AA5749AD23E0039280FB707@exch-mbx901.corp.cloudmark.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Mailman-Approved-At: Fri, 20 Apr 2012 09:54:49 -0700
Cc: draft-kucherawy-marf-source-ports.all@tools.ietf.org, marf@ietf.org
Subject: Re: [marf] [apps-discuss] APPSDIR review of draft-kucherawy-marf-source-ports-01
X-BeenThere: marf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Message Abuse Report Format working group discussion list <marf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/marf>, <mailto:marf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/marf>
List-Post: <mailto:marf@ietf.org>
List-Help: <mailto:marf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/marf>, <mailto:marf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 00:55:13 -0000

Hi Murray,

At 16:45 19-04-2012, Murray S. Kucherawy wrote:
>Hi SM, thanks for the review!

It took 74 minutes, including distractions. :-)

>You're right about UDP.  I'd prefer to leave TCP in, however.

Ok.

>I think these are semantically the same.  We're still left with the 
>question, "When would you not?"  The answer is "When you don't have 
>it," I suppose.  I'll reword accordingly.

I used RECOMMENDED to be in line with RFC 6302.  I could not come up 
with suggested text for that "SHOULD" within the deadline.

>There's some in the next version, based on yours and other feedback.  :-)

I'll do a follow-up if the draft goes to Last Call.  BTW, you don't 
need an update in the Abstract ( -02).

>I haven't seen specific section call-outs done in an updating 
>document before, only the "Updates" stuff on the title page.  Is 
>this necessary?

No, as I classified it under nits.  This document may be folded in 
the RFCs it updates at some point.  It's easier if it inherits the 
requirements in those documents.  If I am implementing the 
specifications, it is easier to read and understand.  From an IETF 
perspective, you don't have to worry about all that.

BTW, I didn't get into the RFC 6302 angle altogether.  Section 13.3 
of RFC 6269 discusses about spam in the context of IP address 
sharing.  The issues around IP address sharing are due to the 
deployment of CGNs.

Regards,
S. Moonesamy