IETF Logo Mail Archive

[sidr] SIDR ReCharter - to capture/cover path validation work

Christopher Morrow <christopher.morrow@gmail.com> Wed, 16 February 2011 17:53 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: sidr@core3.amsl.com
Delivered-To: sidr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB87D3A6EDD; Wed, 16 Feb 2011 09:53:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kVAVtWktQwoc; Wed, 16 Feb 2011 09:53:18 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 1F2EE3A6EDA; Wed, 16 Feb 2011 09:53:17 -0800 (PST)
Received: by wyf23 with SMTP id 23so1714267wyf.31 for <multiple recipients>; Wed, 16 Feb 2011 09:53:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=FzJzyt82zl2Vn8GuBRIRn8iwrGcLc8kwZz30wrFmTI0=; b=EUY6NCpUNapwOlBGl8VHeNNWH+h2tmjqsm4dO0jV7dbJvlUca25Z/byJewoCtMAi9X 5rsn5HBI4rUC/ZSGzjlkx0ntzT7fnjkeFDeQJC3jxpYI1rWNT9THICcGdNHaDmmBmbvg 4HaVsDbEF2492CC/xgcEXFDxCAJZS9sbNGYuY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=QzyXWOoC1NerRPS3udtjswqUfnNo0BuTg4ocbReAx8mchdD8TSzK6rBcrNYHWpk8Er VByp6xEj+h+LPnTN7IVAXHtaCjN0WcrjIUyBIULimd0TY0Z/Nym66/4QKrmLGrvUUBpn nDRCr7Cmr8HIr28txoXR63YkwPP6DMDQ05bgU=
MIME-Version: 1.0
Received: by 10.216.14.147 with SMTP id d19mr756020wed.84.1297878826058; Wed, 16 Feb 2011 09:53:46 -0800 (PST)
Received: by 10.216.1.197 with HTTP; Wed, 16 Feb 2011 09:53:45 -0800 (PST)
Date: Wed, 16 Feb 2011 12:53:45 -0500
Message-ID: <AANLkTikqDyhK4O3rTMQtDNJD8KG3pD19FE=Ys2RkTBNP@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: sidr@ietf.org, Stewart Bryant <stbryant@cisco.com>, Adrian Farrel <Adrian.Farrel@huawei.com>, sidr-chairs@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [sidr] SIDR ReCharter - to capture/cover path validation work
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 16 Feb 2011 17:53:19 -0000

Howdy, as mentioned a few weeks back we need to re-charter the WG in
order to move on from simply validating origination of routing
information to possibly validating path information as well, here's a
strawman charter re-work, how about we discuss some on the list and
have some more chat about it at the Prague meeting?

= = = = = = = = =

Description of Working Group:

The purpose of the SIDR working group is to reduce vulnerabilities in
the inter-domain routing system. The two vulnerabilities that will be
addressed are:

   * Is an Autonomous System (AS) authorized to originate an IP prefix
   * Is the AS-Path represented in the route the same as the path
        through which the route update traveled

The SIDR working group will take practical deployability into consideration.

Building upon the already completed and implemented framework:

   * Resource Public Key Infrastructure (RPKI)
   * Distribution of RPKI data to routing devices and its use in
        operational networks
   * Document the use of certification objects within the secure
        routing architecture


This working group will specify security enhancements for inter-domain
routing protocols.

The SIDR working group is charged with the following goals and
milestones:
ID Date      Pub Date
Mar 2011   Jan 2012  An overview of the RPKI and BGP Protocol changes
required for origin and path validation
Mar 2011   Jun 2012  A document describing threats to the routing system
Mar 2011   Jun 2012  A requirements document that  addresses these threats
Mar2011    Jan 2012  Document the BGP protocol enhancements that meet
the security requirements
Nov 2010    Jul 2011   draft-ietf-sidr-origin-ops
Mar 2011   Jul 2012   Operational deployment guidance for network operators
Jun 2011    Dec 2011 System and architecture design choices made in
the protocol and RPKI
Mar 2010    Mar 2012   draft-ietf-sidr-cps-irs
Mar 2010    Mar 2012   draft-ietf-sidr-cps-isp
Nov 2010    Jan 2012   draft-ietf-sidr-pfx-validate
Jan 2010    Jun 2011    draft-ietf-sidr-publication
Nov 2010    Jun 2011   draft-ietf-sidr-repos-struct
Nov 2010    Jun 2011   draft-ietf-sidr-roa-format
Feb 2011    Jun 2011    draft-ietf-sidr-rpki-rtr
Nov 2010    Nov 2011   draft-ietf-sidr-ltamgmt
Dec 2010    Oct 2011   draft-rgaglian-sidr-algorithm-agility
Jan 2011    Oct 2011   draft-ietf-sidr-ghostbusters
Jan 2010    Dec 2011   draft-ietf-sidr-keyroll
Jan 2010    May 2011  draft-ietf-sidr-arch
Jan 2010    May 2011  draft-ietf-sidr-cp
Jan 2010    May 2011  draft-ietf-sidr-res-certs
Jan 2010    Jun 2011  draft-ietf-sidr-roa-validation
Jan 2010    Jun 2011  draft-ietf-sidr-signed-object
Jan 2010    Jun 2011  draft-ietf-sidr-rpki-manifests
Jan 2010    Jul 2011  draft-ietf-sidr-rpki-algs
Jan 2010    Jul 2011  draft-ietf-sidr-rescerts-provisioning
Jan 2010    Aug 2011  draft-ietf-sidr-ta


==================

-Chris
<co-chair-mittens==off>

v2.23.0 | Report a Bug | By Email