IETF Logo Mail Archive

Re: [abfab] Comments on draft-ietf-abfab-eapapplicability-00.txt

Leif Johansson <leifj@sunet.se> Mon, 06 August 2012 22:17 UTC

Return-Path: <leifj@sunet.se>
X-Original-To: abfab@ietfa.amsl.com
Delivered-To: abfab@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76D1521F84F8 for <abfab@ietfa.amsl.com>; Mon, 6 Aug 2012 15:17:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level:
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599]
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 i1NVGRd51E8Q for <abfab@ietfa.amsl.com>; Mon, 6 Aug 2012 15:17:43 -0700 (PDT)
Received: from backup-server.nordu.net (backup-server.nordu.net [IPv6:2001:948:4:1::66]) by ietfa.amsl.com (Postfix) with ESMTP id 837A221F84F5 for <abfab@ietf.org>; Mon, 6 Aug 2012 15:17:43 -0700 (PDT)
Received: from [10.0.0.11] (ua-83-227-179-169.cust.bredbandsbolaget.se [83.227.179.169]) (authenticated bits=0) by backup-server.nordu.net (8.14.3/8.14.3) with ESMTP id q76MHW5P017441 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Aug 2012 00:17:39 +0200 (CEST)
Message-ID: <5020427A.7090804@sunet.se>
Date: Tue, 07 Aug 2012 00:17:30 +0200
From: Leif Johansson <leifj@sunet.se>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Sam Hartman <hartmans@painless-security.com>
References: <00da01cd6ebc$a1768ae0$e463a0a0$@augustcellars.com> <004901cd704c$301bb500$90531f00$@augustcellars.com> <5019DBFD.8000208@sunet.se> <tsl8vdru13n.fsf@mit.edu>
In-Reply-To: <tsl8vdru13n.fsf@mit.edu>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: abfab@ietf.org
Subject: Re: [abfab] Comments on draft-ietf-abfab-eapapplicability-00.txt
X-BeenThere: abfab@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application Bridging, Federated Authentication Beyond \(the web\)" <abfab.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/abfab>, <mailto:abfab-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/abfab>
List-Post: <mailto:abfab@ietf.org>
List-Help: <mailto:abfab-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/abfab>, <mailto:abfab-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 22:17:44 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/07/2012 12:06 AM, Sam Hartman wrote:
> My personal preference is to keep network access discussions out
> of scope here.
> 
> I think the IDP can detect gss-eap based on the RADIUS AVPs such
> as acceptor-hostname and acceptor-realm that are sent by GSS-EAP.
> 
> If another ABFAB application integration layer is used, then it may
> get more complex.
> 

Nothing stops us from updating the applicability stmt at that time.

> My personal belief is that level of detail is not needed for the 
> applicability statement.
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAgQnMACgkQ8Jx8FtbMZnfn9ACbBQCByYRwvfEAeqgEZIpQBDtd
9KAAmwRZc1YfXqAYemvJ3qMwhQhMR1Vm
=yXjt
-----END PGP SIGNATURE-----

v2.23.0 | Report a Bug | By Email