[Idr] 2 week adoption call for - draft-sriram-idr-route-leak-detection-mitigation-00 (6/25 to 7/9/2015)
"Susan Hares" <shares@ndzh.com> Thu, 25 June 2015 17:45 UTC
Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E99C1A1B7A for <idr@ietfa.amsl.com>; Thu, 25 Jun 2015 10:45:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.155
X-Spam-Level:
X-Spam-Status: No, score=-97.155 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] 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 PbBY7MKhtNq8 for <idr@ietfa.amsl.com>; Thu, 25 Jun 2015 10:45:37 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF3021A1B64 for <idr@ietf.org>; Thu, 25 Jun 2015 10:45:36 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.187.115;
From: Susan Hares <shares@ndzh.com>
To: 'idr wg' <idr@ietf.org>
Date: Thu, 25 Jun 2015 13:45:20 -0400
Message-ID: <015c01d0af6e$b4fd58f0$1ef80ad0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_015D_01D0AF4D.2DED3F90"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdCvbc6f7dardKlkSZG/+/qgBOVH8A==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/57EgVv4chIN4tPynaL3W16FxjEg>
Cc: dougm@nist.gov, ksriram@nist.gov
Subject: [Idr] 2 week adoption call for - draft-sriram-idr-route-leak-detection-mitigation-00 (6/25 to 7/9/2015)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jun 2015 17:45:38 -0000
IDR Working group: This begins a 2 week adoption call for draft-sriram-idr-route-leak-detection-mitigation-00 which can be retrieved at: http://datatracker.ietf.org/doc/draft-sriram-idr-route-leak-detection-mitiga tion/ This is an informational draft regarding route-leak mitigation. For this WG adoption call please include in your response: a) Who will desire to read this informational draft now and in 1 year from now>? b) Is this informational draft's description of route-leak types and mitigated by the origin validation [RFC 6811] and BGPSEC path validation [draft-ietf-sidr-bgpsec-protocol] are correct? c) It is necessary to solve the route-leak problems not covered by origin validation and BGPSEC path validation? d) Do you think the solution suggested for the extension of BGPSEC will fix these unsolved route-leak problems? Sue Hares and John Scudder
- [Idr] 2 week adoption call for - draft-sriram-idr… Susan Hares
- Re: [Idr] 2 week adoption call for - draft-sriram… Jeffrey Haas
- Re: [Idr] 2 week adoption call for - draft-sriram… Matthias Waehlisch