Re: [abfab] Last Call: <draft-ietf-abfab-gss-eap-08.txt> (A GSS-API Mechanism for the Extensible Authentication Protocol) to Proposed Standard

Stephen Farrell <> Thu, 19 July 2012 10:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B2CB121F8683; Thu, 19 Jul 2012 03:56:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4yOYI58lCSBg; Thu, 19 Jul 2012 03:56:27 -0700 (PDT)
Received: from ( [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by (Postfix) with ESMTP id E40B521F85E3; Thu, 19 Jul 2012 03:56:26 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 715B4153663; Thu, 19 Jul 2012 11:57:19 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1342695438; bh=x3Edd7DmQxcE47 grygw+wUXF+aWkYdbPNwlOCDDhPrw=; b=kAktqkvOMcdKna49invQRiBHoN5A2e rh4Op1THOZtDsYXouf3oae0gpKmgr3YuuQYZ8FXy23bdp9I+DRYivewaxNQkWLRK ilzZfHGNP4adzpzBiMZQOGu9tYNOYJosuwKqmzcCANzJfTEEvQ139Mu2tFJ8NvrP NlankxrP3GQbzjkEFdglnRpWxhy2NkFRGDP7ASb5nWkFL6BuejmcZxQ77OKFqyaC QaqhvtPTG9XIf9lzLQbnYok4as5DHtxGxggxiGyqjARY680y/o0tBnw02+ayAzfn /VBR3HYinc5FsENizx7A3MdreDtzwNdqCfEL6HgIAURPjn3nBGrbzoew==
X-Virus-Scanned: Debian amavisd-new at
Received: from ([]) by localhost ( []) (amavisd-new, port 10027) with ESMTP id 3xH0ujybs+ir; Thu, 19 Jul 2012 11:57:18 +0100 (IST)
Received: from [] (unknown []) by (Postfix) with ESMTPSA id 9E851153661; Thu, 19 Jul 2012 11:57:16 +0100 (IST)
Message-ID: <>
Date: Thu, 19 Jul 2012 11:57:16 +0100
From: Stephen Farrell <>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Sam Hartman <>
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: <> <>
In-Reply-To: <>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 19 Jul 2012 10:56:27 -0000

Sorry, I should've asked this before but I'm sometimes dumb:-)

If I put in an RFC editor note adding a normative reference
to the new EAP applicability statement [1] would that sort
this out and not cause any problems for anyone?



On 06/26/2012 08:14 PM, Sam Hartman wrote:
> EAP (RFC 3748) has a applicability statement  scoped very strictly to
> network access.
> This document  provides a mechanism that falls well outside that
> applicability statement and permits the use of EAP for general
> application authentication.
> When ABFAB was chartered, there was a charter item to update the EAP
> applicability statement. I think A number of people in the room at the
> BOF, including myself, would have objected to the work being chartered
> had that charter item not been present.
> I think that work is important because I believe there are a number of
> important concerns that apply to the use of EAP for authentication
> beyond network access that need to be documented.
> Unfortunately, the technical specification has gotten ahead of the
> applicability statement update.
> I'm OK with that provided that we're still firmly committed to an
> applicability statement update. As part of approving this document now,
> I want to confirm that we have consensus at least within the ABFAB
> working group and the IESG to do that update.
> If there is any doubt I'd far prefer that this document be held until
> the applicability statement catches up.
> --Sam