IETF Logo Mail Archive

[yam] Status: draft-ietf-yam-rfc1652bis-pre-evaluation-02 (was: I-D Action:draft-ietf-yam-rfc1652bis-pre-evaluation-02.txt)

S Moonesamy <sm+ietf@elandsys.com> Sat, 12 December 2009 15:23 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 BBB6E3A68A9 for <yam@core3.amsl.com>; Sat, 12 Dec 2009 07:23:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level:
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599]
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 fDFcYtZy1VGJ for <yam@core3.amsl.com>; Sat, 12 Dec 2009 07:23:11 -0800 (PST)
Received: from mail.elandsys.com (mail.elandsys.com [208.69.177.125]) by core3.amsl.com (Postfix) with ESMTP id E8B893A6778 for <yam@ietf.org>; Sat, 12 Dec 2009 07:23:11 -0800 (PST)
Received: from subman.elandsys.com ([41.136.232.170]) (authenticated bits=0) by mail.elandsys.com (8.13.8/8.13.8) with ESMTP id nBCFMi5Q018797; Sat, 12 Dec 2009 07:22:50 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/simple; d=elandsys.com; s=mail; t=1260631372; x=1260717772; bh=psa8mJV8MSXlEt4yUzsg31cgllQ=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=RoVwWBeqJ9krdaTezCNl2+29f9sAPxkVfp4OOebPJTzEcDRiPs6R9DMNvPoR2aWBg TuwPfhOjmFYEDhO9DkOp/vS8pMoObvldKVTQBKtRO2zYlMV+Bo+OwLHlhmW5FsxprK mF9BkETbTgPtqFWlLcTLaLMnZ6+942xiNprqGjBE=
Message-Id: <6.2.5.6.2.20091212065624.02f39b18@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 12 Dec 2009 07:22:24 -0800
To: yam@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <01NH516XKYU0004042@mauve.mrochek.com>
References: <20091211173001.CC22C3A69A0@core3.amsl.com> <4B22C3B8.3070708@dcrocker.net> <01NH516XKYU0004042@mauve.mrochek.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: Ned Freed <ned.freed@mrochek.com>
Subject: [yam] Status: draft-ietf-yam-rfc1652bis-pre-evaluation-02 (was: I-D Action:draft-ietf-yam-rfc1652bis-pre-evaluation-02.txt)
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: Sat, 12 Dec 2009 15:23:12 -0000

At 18:03 11-12-2009, Ned Freed wrote:
>This looks fine now. I think the associated tracker issues can be closed.

I'll close Issue #4 and Issue #15.  If anyone has an objection or 
comments about draft-ietf-yam-rfc1652bis-pre-evaluation-02 [1], 
please post them to this mailing list.

>P.S. Now to get the actual RFC 1652bis document out. Hopefully soon...

There may be some feedback about 
draft-ietf-yam-rfc1652bis-pre-evaluation after December 17th.

Regards,
S. Moonesamy
YAM WG Secretary

1. 
http://www.ietf.org/internet-drafts/draft-ietf-yam-rfc1652bis-pre-evaluation-02.txt

v2.23.0 | Report a Bug | By Email