Re: [abfab] Last Call: <draft-ietf-abfab-gss-eap-08.txt> (A GSS-API Mechanism for the Extensible Authentication Protocol) to Proposed Standard
Sam Hartman <hartmans-ietf@mit.edu> Thu, 19 July 2012 11:18 UTC
Return-Path: <hartmans@mit.edu>
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 AA33321F8595; Thu, 19 Jul 2012 04:18:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.887
X-Spam-Level:
X-Spam-Status: No, score=-102.887 tagged_above=-999 required=5 tests=[AWL=-0.622, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 bqmP0YIiZZFb; Thu, 19 Jul 2012 04:18:39 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 2A34E21F8594; Thu, 19 Jul 2012 04:18:39 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 31DB3204BA; Thu, 19 Jul 2012 07:19:50 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id F099441F0; Thu, 19 Jul 2012 07:19:04 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [abfab] Last Call: <draft-ietf-abfab-gss-eap-08.txt> (A GSS-API Mechanism for the Extensible Authentication Protocol) to Proposed Standard
References: <20120626165832.6142.66386.idtracker@ietfa.amsl.com> <tslk3yt6g2s.fsf@mit.edu> <5007E80C.5070404@cs.tcd.ie>
Date: Thu, 19 Jul 2012 07:19:04 -0400
In-Reply-To: <5007E80C.5070404@cs.tcd.ie> (Stephen Farrell's message of "Thu, 19 Jul 2012 11:57:16 +0100")
Message-ID: <tsleho8j8wn.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: abfab@ietf.org, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 19 Jul 2012 11:18:39 -0000
>>>>> "Stephen" == Stephen Farrell <stephen.farrell@cs.tcd.ie> writes: Stephen> Sorry, I should've asked this before but I'm sometimes dumb:-) Stephen> If I put in an RFC editor note adding a normative reference Stephen> to the new EAP applicability statement [1] would that sort Stephen> this out and not cause any problems for anyone? I don't object to that, but it does hold up the doc. I'm happy letting this doc go forward now so long as we're all on the same page on the applicability stament. I realize we run the risk that somehow the applicability effort derails. Personally, I'm willing to take that risk, so long as we believe today we do intend to publish the applicability statement. If someone on the IESG or in the community wants that normative reference, I support adding it. I'm just not asking for it myself.
- Re: [abfab] Last Call: <draft-ietf-abfab-gss-eap-… Sam Hartman
- Re: [abfab] Last Call: <draft-ietf-abfab-gss-eap-… Stephen Farrell
- Re: [abfab] Last Call: <draft-ietf-abfab-gss-eap-… Sam Hartman
- Re: [abfab] Last Call: <draft-ietf-abfab-gss-eap-… Leif Johansson