[Trust-router] FW: New Version Notification for draft-schaad-trust-router-problem-01.txt

"Jim Schaad" <ietf@augustcellars.com> Thu, 30 May 2013 21:31 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: trust-router@ietfa.amsl.com
Delivered-To: trust-router@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5275521F86AE; Thu, 30 May 2013 14:31:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.264
X-Spam-Level:
X-Spam-Status: No, score=-3.264 tagged_above=-999 required=5 tests=[AWL=0.335, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 jWWAr8GjTvLh; Thu, 30 May 2013 14:31:47 -0700 (PDT)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by ietfa.amsl.com (Postfix) with ESMTP id 94C7521F8696; Thu, 30 May 2013 14:31:44 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTPSA id 2A66C2CA20; Thu, 30 May 2013 14:31:44 -0700 (PDT)
From: Jim Schaad <ietf@augustcellars.com>
To: trust-router@ietf.org
References: <20130530211857.10340.69519.idtracker@ietfa.amsl.com>
In-Reply-To: <20130530211857.10340.69519.idtracker@ietfa.amsl.com>
Date: Thu, 30 May 2013 14:30:52 -0700
Message-ID: <04ee01ce5d7c$f7c60240$e75206c0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGebNoyW1RF+EXbAdPZfyyPhs4Yspl+HVnw
Content-Language: en-us
Cc: radext@ietf.org, abfab@ietf.org, MOONSHOT-COMMUNITY@JISCMAIL.AC.UK
Subject: [Trust-router] FW: New Version Notification for draft-schaad-trust-router-problem-01.txt
X-BeenThere: trust-router@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "ABFAB Trust Router discussion list." <trust-router.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trust-router>, <mailto:trust-router-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trust-router>
List-Post: <mailto:trust-router@ietf.org>
List-Help: <mailto:trust-router-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trust-router>, <mailto:trust-router-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2013 21:31:52 -0000

I present this document for discussion on the IETF Trust Router mailing list.

It is a new and completely different version of the problem statement from that offered by the Janet people.  I think it is a more complete and more understandable document that the one they have provided.

The document was started under an alcoholic haze and frustration over the fact that the BOF for the group might not occur in Berlin as was originally envisioned.  The primary hope of this document is to try and get more conversation on this mailing list about the problem itself.  Note that I don't currently care what the solution is.  That should be discussed after the BOF has been completed.

Jim


> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Thursday, May 30, 2013 2:19 PM
> To: Jim Schaad
> Subject: New Version Notification for draft-schaad-trust-router-problem-
> 01.txt
> 
> 
> A new version of I-D, draft-schaad-trust-router-problem-01.txt
> has been successfully submitted by Jim Schaad and posted to the IETF
> repository.
> 
> Filename:	 draft-schaad-trust-router-problem
> Revision:	 01
> Title:		 Trust Router Problem Statement
> Creation date:	 2013-05-30
> Group:		 Individual Submission
> Number of pages: 17
> URL:             http://www.ietf.org/internet-drafts/draft-schaad-trust-router-problem-01.txt
> Status:          http://datatracker.ietf.org/doc/draft-schaad-trust-router-problem
> Htmlized:        http://tools.ietf.org/html/draft-schaad-trust-router-problem-01
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-schaad-trust-router-problem-01
> 
> Abstract:
>    There are a number of problems with using the current AAA framework
>    for doing access control, this document looks at a number of these
>    issues and poses some questions about how to create a new trust
>    router system.
> 
> 
> 
> 
> The IETF Secretariat