[yam] Working Group Process
S Moonesamy <sm+ietf@elandsys.com> Fri, 18 June 2010 16:06 UTC
Return-Path: <sm@elandsys.com>
X-Original-To: yam@core3.amsl.com
Delivered-To: yam@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A1733A683F for <yam@core3.amsl.com>; Fri, 18 Jun 2010 09:06:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.432
X-Spam-Level:
X-Spam-Status: No, score=-0.432 tagged_above=-999 required=5 tests=[AWL=-0.433, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mshJOdfwVexe for <yam@core3.amsl.com>; Fri, 18 Jun 2010 09:06:31 -0700 (PDT)
Received: from mail.elandsys.com (mail.elandsys.com [208.69.177.125]) by core3.amsl.com (Postfix) with ESMTP id E1DC13A6801 for <yam@ietf.org>; Fri, 18 Jun 2010 09:06:31 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.234.222]) (authenticated bits=0) by mail.elandsys.com (8.13.8/8.13.8) with ESMTP id o5IG6M14020990; Fri, 18 Jun 2010 09:06:31 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=elandsys.com; s=mail; t=1276877195; bh=hGdondvLTuTSDqSJVuUcSUZUldY=; h=Message-Id:Date:To:From:Subject:Cc:Mime-Version:Content-Type; b=hG76rY6PntFVdJH5f5uBMsH35zWP4jhoygSqTituoLyJDjFTAMPIxZgHSv9/Quu3N qgrJZ1WE4hTx34VCe1Mpd46fDDBcwaQbe/FBAPPT42/6uu19iJdNV+tjzMMRoeS3Vs SjQSCfWNYUInOoaCsEk3ovMF1IbcXB8CLn8WE8yo=
Message-Id: <6.2.5.6.2.20100618081336.0a895e98@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 18 Jun 2010 09:05:07 -0700
To: yam@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: Chris Newman <Chris.Newman@sun.com>
Subject: [yam] Working Group Process
X-BeenThere: yam@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Yet Another Mail working group discussion list <yam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yam>
List-Post: <mailto:yam@ietf.org>
List-Help: <mailto:yam-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jun 2010 16:06:33 -0000
Hello,
This is the second time this working group is having a discussion
about the process. I don't think I need to summarize the comments
that have been posted as the outcome is clear.
As I haven't seen any questions about the YAM WG Charter, I gather
that you all fully understand it by now. The working group has been
given some leeway to discuss or raise issues up to now. What
constitutes an issue is defined in the YAM Charter.
- The working group does not intend to revise the actual protocols
in any way.
- Semantic or syntactic changes should be avoided.
- Substantive changes may be considered if they contribute in a substantial
and substantive way to the quality and comprehensibility of the
specification while not forcing a change to the exiting protocol.
Any issue raised must follow these guidelines. Open-ended
discussions are not acceptable unless you can explain why it is relevant.
The working group adopted a process to focus strictly on advancing
email-related specifications which are already at Draft
Standard. Its function is not to reopen or reconsider protocols or
to have noisy debates about the protocols.
If you have any questions about the above, please contact me.
Regards,
S. Moonesamy
YAM WG Secretary
- [yam] Working Group Process S Moonesamy