Re: [sidr] Master thesis - RPKI

Demian Rosenkranz <drosen2s@smail.inf.h-brs.de> Tue, 14 January 2014 16:27 UTC

Return-Path: <drosen2s@smail.inf.h-brs.de>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 191801AE0FD for <sidr@ietfa.amsl.com>; Tue, 14 Jan 2014 08:27:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.229
X-Spam-Level:
X-Spam-Status: No, score=-1.229 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7] autolearn=no
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 r6vK_uo0_W7H for <sidr@ietfa.amsl.com>; Tue, 14 Jan 2014 08:27:15 -0800 (PST)
Received: from ux-2s11.inf.fh-bonn-rhein-sieg.de (ux-2s11.inf.fh-bonn-rhein-sieg.de [194.95.66.8]) by ietfa.amsl.com (Postfix) with ESMTP id 8487A1AE117 for <sidr@ietf.org>; Tue, 14 Jan 2014 08:27:13 -0800 (PST)
Received: from [192.168.16.1] ([194.25.10.166]) (authenticated bits=0) by ux-2s11.inf.fh-bonn-rhein-sieg.de (8.14.4/8.14.4/Debian-4ska0) with ESMTP id s0EGR0au023419 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <sidr@ietf.org>; Tue, 14 Jan 2014 17:27:01 +0100
Message-ID: <52D56551.7030203@smail.inf.h-brs.de>
Date: Tue, 14 Jan 2014 17:26:57 +0100
From: Demian Rosenkranz <drosen2s@smail.inf.h-brs.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
CC: sidr@ietf.org
References: <52D3FE0B.1080808@smail.inf.h-brs.de> <Pine.WNT.4.64.1401141433160.5660@mw-PC>
In-Reply-To: <Pine.WNT.4.64.1401141433160.5660@mw-PC>
Content-Type: text/plain; charset="ISO-8859-15"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Auth: by SMTP AUTH @ ux-2s11
X-MIMEDefang-Info-ge: Gescannt in Inf@FH-BRS, Regeln s. MiniFAQ E-Mail/Mailscanner
X-Scanned-By: MIMEDefang 2.73
Subject: Re: [sidr] Master thesis - RPKI
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 16:27:17 -0000

Thanks!

Actually I'm not really happy with this subdivision and I think I will 
change it. I tried to make it neatly arranged. Object related problems 
belong to a single object, that causes the "problem" and system related 
problems usually relate to whole datasets or the system at all.
I'm open to suggestions :-)

Kind regards

Demian

Am 14.01.2014 14:51, schrieb Matthias Waehlisch:
> Hi Demian,
>
>    nice work. I'm a little bit wondering about the classification. Can
> you be a bit more specific how do you define "Object related" and
> "Systems related"?
>
>    For example, the "Short Lifetime Attack" is categorized under "Systems
> related". However, it is directly related to the configuration of the
> signed object; on the other hand, it harms the RP system.
>
>    Does the classification reflects (a) which part of the system is
> harmed, (b) which part is used to introduce problems, or (c) a mixture?
> I think a clearer separation would be helpful.
>
>
>
> Thanks
>    matthias
>
>