Re: Fully functional email address
S Moonesamy <sm+ietf@elandsys.com> Sat, 21 June 2025 20:36 UTC
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 6099837CE493 for <ietf@mail2.ietf.org>; Sat, 21 Jun 2025 13:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jTfuHenUzHpN for <ietf@mail2.ietf.org>; Sat, 21 Jun 2025 13:36:47 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mail2.ietf.org (Postfix) with ESMTP id 1E99337CE48F for <ietf@ietf.org>; Sat, 21 Jun 2025 13:36:46 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.70.50]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 55LKaWjS021379 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 21 Jun 2025 13:36:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1750538203; x=1750624603; i=@elandsys.com; bh=eCvPHS4F0nU1bPfwOZLG3O790PEp6oYGZJaEER5sAhY=; h=Date:To:From:Subject:In-Reply-To:References; b=cLNCfa6HoamuG3Z4ukeJUddMbxrj+SKtCl9/HIA339/DVbv0q+r/5rSIkMhdlYKr0 NkvIUNEE6qPwTr2g4WNB1pIB0qkIkX4nnWb9KozfcjT+fv6baZEXXicINMqFjpO1cy LLKmHl+hJlQeAncgfW+FP6rkQ0qSxwxyw1Agobqk=
Message-Id: <6.2.5.6.2.20250621122853.0c7ee188@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 21 Jun 2025 13:35:53 -0700
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Fully functional email address
In-Reply-To: <D4B7CE7F7D767882F6C5AD10@PSB>
References: <D4B7CE7F7D767882F6C5AD10@PSB>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: RSFFPVZO4ZG5664YTK5LK2I6TDYPONVV
X-Message-ID-Hash: RSFFPVZO4ZG5664YTK5LK2I6TDYPONVV
X-MailFrom: sm@elandsys.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9wgs6fBRnTMwMyejUmszkaojqcM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>
Hi John, At 12:10 PM 21-06-2025, John C Klensin wrote: >But part of the point, IMO, is that, if we view appeals as more of a >process of making sure that all perspectives were considered in >reaching consensus or making a decision, then a requirement to >explain --ideally in the sort of short and clear message that I seem >to have trouble writing because I prefer to explore details and >subtleties -- is obvious and does not require additional rules. I would like someone to think of the details and subtleties so that I am not surprised down the line. I'll say yes to the above. >We might disagree there. Over the years, we've seen an evolution >toward WGs becoming very narrowly focused on a range of topics and, >probably consequently, smaller. Sometimes that has lead to a WG all >of whose participants share the same general assumptions and points >of view, even though there may be others in the community with very >different ones. Even if someone with a different point of view tried >to participate, being the lone voice with a different (and maybe >unpopular) perspective can be difficult and such people sometimes >give up out of frustration even though there is no evil intent within >the WG. Others may have insufficient time or resources to >participate actively in the WG despite having expertise in the topic >and therefore wait until WG LC or IETF LC to intervene, something >that can be deeply frustrating to a WG that thought it was finished. >Those kinds of things can easily lead to a situation in which there >is the appearance of consensus within the WG (e.g., a report that >there were no, or only one, dissent) but where those important issues >have not been noted and discussed. Yes. >Do these things happen? Yes, and I think increasingly so as WGs and >topics get more specialized. There have been several times in recent >years where I've started down the path to appeals of those sorts of >situations. In almost all cases, the issues have been reopened and >resolved after informal conversations with WG Chairs and with the AD >at least copied; a few have ended up in appeals to the IESG. And, >again, unless the IESG is dismissive without either examination of >the issues or requiring the WG to reexamine them, I think that is how >the system is supposed to work. Yes (to more specialized). >And those are places where I don't think the IETF can go if we want >to remain effective and have our consensus documents be consistent >with Doing the Right Thing and, to the extent possible, agreement in >the larger implementer and user communities. If being open, or >questioning decisions made without consideration of significant >issues, is perceived as a problem, then I think we are in big trouble. It's fine to ask questions. Asking the same question again and again is not a good idea if the question was already answered. >But, again, I think all of that needs to occur in a spirit of trying >to work together to get high quality results. If it turns into some >variation on "I need to win (at any cost) and that means you need to >lose" then I think we have, or are at least headed into, problems far >more serious than issues about particular appeals, email >functionality, etc., and may need to move toward discussions about >disruptive and destructive behavior and not, e.g., quibbles about >email functionality. The environment is quite competitive. It's not that easy to get everyone into such a spirit. The "need to win" works if the person joined for a one-off effort. It may not work that well if the person plans to spend a few years in this community. >Yes to the point and no to "fair". Howeer, one or two of my oddities >is that I not only tend to be sensitive to the possibility of even >more than two sides to a story but that I am less concerned about >fairness (or perceptions of it) than I am about careful consideration >of all of the issues that bear on a problem, what tradeoffs (if any) >exist among them, and whether a consensus middle ground is possible >without creating a solution that is worse than any of the other >alternatives. Of course, fairness facilitates all of that and might >turn out to be the same thing, but I think better and quicker >progress is often facilitated by concentrating on the issues >themselves (and trying to be sure that all of them are exposed) than >about debates about whether some one, or some process, is >sufficiently fair or not. It takes a significant amount of time to listen to the two (or more) sides. It can take even more time to get a group to converge on a middle ground. The perception could influence that, i.e. the decision-maker is favouring Person A over Person B, or Company C over Company D. Regards, S. Moonesamy
- Re: Fully functional email address John C Klensin
- Re: Fully functional email address John C Klensin
- Re: Fully functional email address George Michaelson
- Fully functional email address S Moonesamy
- Re: Fully functional email address Paul Wouters
- Re: Fully functional email address S Moonesamy
- Re: Fully functional email address John Levine
- Re: Fully functional email address Michael Richardson
- Re: Fully functional email address Christian Huitema
- Re: Fully functional email address George Michaelson
- Re: Fully functional email address John C Klensin
- Re: Fully functional email address S Moonesamy
- Re: Fully functional email address John R. Levine
- Re: Fully functional email address Salz, Rich
- Re: Fully functional email address Rob Sayre
- Email usage (Was: Fully functional email address) Jay Daley
- Re: Fully functional email address Stephen Farrell
- Re: Fully functional email address Jay Daley
- Re: Fully functional email address S Moonesamy
- Re: Fully functional email address Martin J. Dürst
- Re: Fully functional email address Christian Huitema
- Re: Fully functional email address S Moonesamy
- Re: Fully functional email address Stephen Farrell
- Re: Fully functional email address John Levine
- Re: Fully functional email address Rich Kulawiec
- Re: Fully functional email address Phillip Hallam-Baker
- Re: Fully functional email address Paul Wouters
- Re: Fully functional email address John C Klensin
- Re: Fully functional email address S Moonesamy