Re: AD Sponsorship of draft-moonesamy-recall-rev

S Moonesamy <sm+ietf@elandsys.com> Thu, 16 May 2019 19:37 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5C1E120299 for <ietf@ietfa.amsl.com>; Thu, 16 May 2019 12:37:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=TG7f+eGL; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=B7/9+wMs
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tu8-F4lDEk62 for <ietf@ietfa.amsl.com>; Thu, 16 May 2019 12:37:55 -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 7C31512028C for <ietf@ietf.org>; Thu, 16 May 2019 12:37:55 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.226.214.184]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x4GJbXs0025135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 May 2019 12:37:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1558035474; x=1558121874; bh=E5Jc2mFQwbeyLjRkc6aPWlLPatRTPZ02rBQcFd0Q4QA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=TG7f+eGL913xB+qqMp4O0VPbcHBmkUqD306kF7bsnpm9STVaI9c3GxyOgELRs1A8Z WsLeTADolCm+qm25/LrK7y76upd8QfNdS/sR0Pdv2DlHvBfjl02681u5RR9IFB3s8O MsACiokCPaKSZENGsEHgo3qs5FryXH+k6J6hxcXY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1558035474; x=1558121874; i=@elandsys.com; bh=E5Jc2mFQwbeyLjRkc6aPWlLPatRTPZ02rBQcFd0Q4QA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=B7/9+wMsxvsMd30KOzs3XdqT9g8T74d70cGcSTKcPYrrjJiKUs975F1aQoU68AlvX XqhNAxzghwCxPCJZUu6D9F3m0TwvtRpyI0GavSMzlz6EekRKFOlkEwXmRpj3JJ52+B 8OiV3+VOLf+IbeLX0I4+fnAMwL1Vgnr+TIzFlBgA=
Message-Id: <6.2.5.6.2.20190516103829.11f9fb18@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 16 May 2019 12:00:31 -0700
To: Suresh Krishnan <suresh@kaloom.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
Cc: John C Klensin <john-ietf@jck.com>
In-Reply-To: <15BCE05FEA1EEA6AD0E7E5BD@PSB>
References: <6.2.5.6.2.20190509041736.0d6d4548@elandsys.com> <f5834466-8f40-42bd-82d8-4dcb7d418859@www.fastmail.com> <6.2.5.6.2.20190509105617.0c08ef60@elandnews.com> <e854adaf-1ead-41d0-95bf-df56cb5a5914@www.fastmail.com> <6.2.5.6.2.20190514234822.0bc461f0@elandnews.com> <15BCE05FEA1EEA6AD0E7E5BD@PSB>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/D7wWboMSRG9JQQcDOLNgHSo2mcY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2019 19:37:57 -0000

Hi Suresh,

I submitted a new version of the draft: 
https://datatracker.ietf.org/doc/html/draft-moonesamy-recall-rev

The description for "eligibility-discuss" mailing list could be 
interpreted as a place to discuss eligibility to participate in the 
IETF.  Was that mailing list set up to determine the policy for 
eligibility to participate in the IETF?

Regards,
S. Moonesamy