Re: [apps-discuss] Comments on draft-hryckelynck-writing-rfcs-01
SM <sm@resistor.net> Thu, 17 May 2012 23:41 UTC
Return-Path: <sm@resistor.net>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82F2D21F8757 for <apps-discuss@ietfa.amsl.com>; Thu, 17 May 2012 16:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.488
X-Spam-Level:
X-Spam-Status: No, score=-102.488 tagged_above=-999 required=5 tests=[AWL=0.111, 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 5APt7xyWd1rG for <apps-discuss@ietfa.amsl.com>; Thu, 17 May 2012 16:41:22 -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 88EF321F8744 for <apps-discuss@ietf.org>; Thu, 17 May 2012 16:41:22 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q4HNfFi7017147; Thu, 17 May 2012 16:41:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1337298081; i=@resistor.net; bh=jEwZuX+qMon/ZAejOGeGPiym4geXoyq5L7RtTmruAtU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=b6k4D4bb37BmUXKvA8TZSA+7ZQjdGHYaVB3T2sU3eKm7X2IFwrGy/RypUcNcLyddY iqvjWr3+FNzXutSNdwRbeK3qBtGzFGrPL3i6YKDQ7cfqhm29TnZWzs8UFdMvYNICtQ BMJbCq+oDK6MbuWO9gJ5H1o6cd8LiEAcP3rpz2mU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1337298081; i=@resistor.net; bh=jEwZuX+qMon/ZAejOGeGPiym4geXoyq5L7RtTmruAtU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=gCgBrt2v38OdESuMgVHOSnwbHm+sx0MntDFx9rY0eLEQE8nVMF7aYt7uRahun1xda oonj6fv6GrbGlvJxcMwD4GZFyizUG08wYTp68RylrdXxUBkGUEQ0THl/yNIYS5R2cB 4OVeYQAxYR7+eOpKFmg7fmLqZy4SV/ldwLQuU8HA=
Message-Id: <6.2.5.6.2.20120517155700.0b009770@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 17 May 2012 16:40:56 -0700
To: hub ryck <hub.ryck@gmail.com>
From: SM <sm@resistor.net>
In-Reply-To: <CAAyzDoRZLOoh2aTJJpkQaR-3Z4d33U3wD62P4346=Pqph3iBAw@mail.g mail.com>
References: <6.2.5.6.2.20120421143240.07253358@elandnews.com> <CAAyzDoSNZUiRnfg7tePdaSY1xjmQqqW37TbwMk8mL-uVKHEuTg@mail.gmail.com> <6.2.5.6.2.20120429134847.08f02068@resistor.net> <CAAyzDoRZLOoh2aTJJpkQaR-3Z4d33U3wD62P4346=Pqph3iBAw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] Comments on draft-hryckelynck-writing-rfcs-01
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2012 23:41:23 -0000
Hi Hubert, At 04:12 17-05-2012, hub ryck wrote: >I did a mistake when I posted the first version. I wanted to change >the name but I don't know how. The problem is, when I post a new >version, if I change the name how the site will related it to the >previous version ? Barry Leiba provided an explanation at http://www.ietf.org/mail-archive/web/apps-discuss/current/msg05884.html >"it is easy to say" is ok for me. I modified section 1 in draft >"draft-hryckelynck-writing-rfcs-04" as follows : > >"It is easy to say that mails with, for example, an attempted fraud >content are mails we must intercept." I was trying to explain and you used it as suggested text. :-) >I checked every expired draft containing "mail" or "smtp" or "spam". >I could see that finding a way to get the user advice has been a >concern for others. >But none of the previous approaches I found is close from the one I propose. Ok. I'll suggest that you get reviews from other people as it may help to refine the proposal. >I was not sure of what you meant when you asked "What is my opinion". I meant it "as what would conclude after reading the material". >Also, I realized, as these RFCs are experimental, I may have >referenced them as non normative ? The Style Guide at http://www.rfc-editor.org/rfc-style-guide/rfc-style explains how to determine whether a reference should be normative or informative. >My opinion is that it is too bad "efforts to reconcile the two >approaches have failed". >But I don't think it will help :-) No comment. :-) >I didn't know you were writing a draft on the subject => >"draft-moonesamy-senderid-spf-conclusion-xx" That draft will never be published. I would not even recommend spending the time to read it. >Would you like to be an author ? I would be more than happy if you want to. It's going to be a lot of work to get this draft anywhere near consensus. May I suggest that you contact the APPSAWG Chairs ( https://datatracker.ietf.org/wg/appsawg/charter/ ) to see whether there is any support for your proposal? I'll consider your question if the WG Chairs determine that there is support. >As a matter of fact your first mail arrived in the junk mail directory :-) :-) >If we look now on what happen with IETF mailing list, my mail was >submitted to approbation. That is because you are not subscribed to the mailing list ( https://www.ietf.org/mailman/listinfo/apps-discuss ). >It looks like my mail has to be "accepted" by someone. Also I could >find in RFC3683, >"maintainers of any IETF mailing list may, at their discretion, also >remove posting rights to that IETF mailing list." I'll try and explain this in simple terms. It may not be the correct explanation. If there are several messages about a topic which the moderator of an IETF mailing list considers as unrelated to the topic being discussed on that mailing list, they will send you a message about the matter. If you keep ignoring their kind advice, they can moderate the messages you send to the mailing list. >So I will do an answer similar to the one I made about experimental >status. At this stage, "draft-hryckelynck-writing-rfcs-xx" has to >be viewed as a practice and then if the community gives sympathetic >consideration to this practice we could then design parts of this practice >as a protocol (like for example communication between MTA and Base) >or as protocol extensions (specific header, error code, ...). It is more about whether there is consensus. >In resume : >1- what about this idea ? >2- work >3- if idea is OK => what about a practice ? >4- work >5- if practice is OK => what about designing parts of this practice >as a protocol ? > >Do I have to modify something in this sense in the draft headers to >show this is a Practice and not a protocol ? >Is "Intended status: Experimental" still OK ? I suggest contacting the APPSAWG Chairs before getting into such an effort. >======================== >Also, I received the following comment from Dave Crocker "the >proposal does not seem to require any user choice". As a matter of >fact at this stage I was only proposing to store I saw Dave Crocker's message as it was posted to the apps-discuss@ietf.org mailing list. Please see the suggested I made above. Regards, -sm
- [apps-discuss] Comments on draft-hryckelynck-writ… SM
- Re: [apps-discuss] Comments on draft-hryckelynck-… hub ryck
- Re: [apps-discuss] Comments on draft-hryckelynck-… Dave Crocker
- Re: [apps-discuss] Comments on draft-hryckelynck-… SM
- Re: [apps-discuss] Comments on draft-hryckelynck-… hub ryck
- Re: [apps-discuss] Comments on draft-hryckelynck-… hub ryck
- Re: [apps-discuss] Comments on draft-hryckelynck-… Barry Leiba
- Re: [apps-discuss] Comments on draft-hryckelynck-… SM
- Re: [apps-discuss] Comments on draft-hryckelynck-… hub ryck