IETF Logo Mail Archive

[sidr] WGLC: draft-ietf-sidr-bgpsec-reqs

Christopher Morrow <christopher.morrow@gmail.com> Fri, 28 October 2011 18:40 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93C0821F86A1; Fri, 28 Oct 2011 11:40:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.486
X-Spam-Level:
X-Spam-Status: No, score=-103.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 kyjHMfhqWBQQ; Fri, 28 Oct 2011 11:40:45 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id E62DC21F8669; Fri, 28 Oct 2011 11:40:41 -0700 (PDT)
Received: by qadc10 with SMTP id c10so4946096qad.31 for <multiple recipients>; Fri, 28 Oct 2011 11:40:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=4+00NwIm2AMv14MFdXSN/L7giYZYabKHNUA/cdIHjFk=; b=Z4ZIuM/kQRzP1qY2fpSU87XkXZoS2iIbJ9KPsZuQ/BD2RMGWRFdvKWO6luSNqr4+DZ 1K8IEY1Qcd4QtCM9Wzvg3bI/FTAOvfFMaTNoUhv3uRCQN89faRd8bT2pyzw23zLNJIZt szBwl/geQGjsdxkB8LLiNXmid2Dv22vLYI5Yo=
MIME-Version: 1.0
Received: by 10.68.42.39 with SMTP id k7mr5515888pbl.71.1319827241045; Fri, 28 Oct 2011 11:40:41 -0700 (PDT)
Received: by 10.68.63.230 with HTTP; Fri, 28 Oct 2011 11:40:41 -0700 (PDT)
Date: Fri, 28 Oct 2011 14:40:41 -0400
Message-ID: <CAL9jLaa+L-C7+Gp54BpM8FjAj+EFMabwQB9SsPW0N4QnFEfVGw@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: sidr@ietf.org, sidr-chairs@ietf.org, draft-ietf-sidr-bgpsec-reqs@tools.ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 28 Oct 2011 18:40:45 -0000

Seems that the authors, at least, expect this doc to be prepared for
WGLC, could we do that concluding 11/11/11 please?

Draft link: <http://tools.ietf.org/wg/sidr/draft-ietf-sidr-bgpsec-reqs/>
   01 link: <http://tools.ietf.org/html/draft-ietf-sidr-bgpsec-reqs>
  diff link: <http://tools.ietf.org/wg/sidr/draft-ietf-sidr-bgpsec-reqs/draft-ietf-sidr-bgpsec-reqs-01-from-00.diff.html>

Abstract:
"This document describes requirements for a future BGP security
   protocol design to provide cryptographic assurance that the origin AS
   had the right to announce the prefix and to provide assurance of the
   AS Path of the announcement."

Thanks!
-Chris
<wg-co-chair-haircut == completed>

v2.27.8 | Report a Bug | By Email | System Status