Re: [GROW] I-D Action: draft-ietf-grow-route-leak-detection-mitigation-01.txt

Alexander Azimov <a.e.azimov@gmail.com> Sun, 06 October 2019 20:59 UTC

Return-Path: <a.e.azimov@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED47712011D; Sun, 6 Oct 2019 13:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 91RjxFV-kBdE; Sun, 6 Oct 2019 13:59:24 -0700 (PDT)
Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A51A71200CE; Sun, 6 Oct 2019 13:59:24 -0700 (PDT)
Received: by mail-ot1-x32c.google.com with SMTP id 60so9384396otu.0; Sun, 06 Oct 2019 13:59:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kj2wcQNO681SJ24P4gXn9lcPX8d9s12PPzM8dMlYwK4=; b=J4OYF3qu4+XQzBWMNVnSNtffQeHYk7ZQSoQesS05selbPxpPaTxiOronfi7OYWSE3k Flcz8t0JCjMgmGPRUVN1l/srw5JdpI+P1JHkcCdEf3JXNeq8EJgxaZYy7/FcGNWLEfH2 IElf0AHbQBcMU9yBT2YAuw/AuRTR1NZH2brytLLNjjQPOVltiK1G5MuNypvTaHeelCRO o+kC5xXU90xdt6OCFYzoiXBx0dGq3sZ0pyJ4wXPvk5tW2yzXiJq0ybN6Q3MG1oyrdIc/ ba4D4/t67VYDNYcpMIQGjBTifAY+UdzugIBUxFQ9lZihuIfriMTc6kE3fzl+QnFCOkNj /fjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kj2wcQNO681SJ24P4gXn9lcPX8d9s12PPzM8dMlYwK4=; b=ofikCz7nb+SmG24akbEB+xa3h/3I5lfMa74pivxOsPtQaOd1OStQlKfBVMftF8z1Q5 OINNKyH8dUnyMaMpJ5N34KYtMdSLaoGeVGiswLcai+6sK/fQjAy8nrCetacUXUXkJJUZ JBcuXi4sijXj1aHkbsZEsdDCEAaZSHCc1B2cjp3ZQLMFqOaOS5XAXdcrGOxUW06NC9do XCMuvgqyFkB1xWMsM19XxmgzK3sh9eL6EQSsbd3+tPVDwoW6Dl27GAO8Wj3xIgwj9UDR ceD0d6UVWLGEY8D021lGl0A2xuHcniYVeUBis9gWDgD6VA+ZYRY0TY9whIR6PDB5GxbV dKYg==
X-Gm-Message-State: APjAAAWvLLTdizt2MQhyJO/88/OT8saOxusXGLUKpbynueUT2S6friWP kIboxXrB+1BpFJ3OhHWopXx5/XouIpsXaVqWygmZqozwkVU=
X-Google-Smtp-Source: APXvYqymOcjYkXurZ/50O9H/qRGYWRSog3Bdi5DhG90lHrQ25b/VOPO3AN2QOazCDR3zHDbQ9vzxRthmot4I9J2NIz4=
X-Received: by 2002:a9d:58d:: with SMTP id 13mr18972343otd.248.1570395563563; Sun, 06 Oct 2019 13:59:23 -0700 (PDT)
MIME-Version: 1.0
References: <156416048884.7629.15852627985138020754@ietfa.amsl.com> <CAEGSd=CTGZqk22ob0B_pKTA4yen+=2MGsMp94EUrs7uwvqX+ag@mail.gmail.com>
In-Reply-To: <CAEGSd=CTGZqk22ob0B_pKTA4yen+=2MGsMp94EUrs7uwvqX+ag@mail.gmail.com>
From: Alexander Azimov <a.e.azimov@gmail.com>
Date: Sun, 06 Oct 2019 23:59:12 +0300
Message-ID: <CAEGSd=DT2j_FdfT0H6wh0oJN5JhYv7VAscn703FBychyJdbqqQ@mail.gmail.com>
To: grow@ietf.org
Cc: i-d-announce@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b91eda0594443518"
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/KUXEVOaEhV6H9VRWCz8D2Ga99j8>
Subject: Re: [GROW] I-D Action: draft-ietf-grow-route-leak-detection-mitigation-01.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Oct 2019 20:59:28 -0000

Dear WG,

I'd like to highlight, that the WGLC for
the draft-ietf-grow-route-leak-detection is still locked by the absence of
reserved class for well-known transit communities.
If somebody is already working on this specification - please raise your
hand. Otherwise, I will be using my Russian-English to wright this spec.
You are warned.

пт, 26 июл. 2019 г. в 20:11, Alexander Azimov <a.e.azimov@gmail.com>:

> Dear WG,
>
> This document of route leak detection using communities seems to address
> all unresolved issues from the previous versions.
> We believe that the proposed solution can be easily adopted by the ISPs
> thus reducing the number of route leaks that become globally propagated.
>
> There is one unresolved dependency - we need IANA to reserve a class for
> well-known transit communities.
> As far as I remember that there was already some work in this field. I'm
> eager to assist if this can help to speed up the process.
>
> пт, 26 июл. 2019 г. в 20:02, <internet-drafts@ietf.org>:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Global Routing Operations WG of the IETF.
>>
>>         Title           : Methods for Detection and Mitigation of BGP
>> Route Leaks
>>         Authors         : Kotikalapudi Sriram
>>                           Alexander Azimov
>>         Filename        :
>> draft-ietf-grow-route-leak-detection-mitigation-01.txt
>>         Pages           : 9
>>         Date            : 2019-07-26
>>
>> Abstract:
>>    Problem definition for route leaks and enumeration of types of route
>>    leaks are provided in [RFC7908].  This document describes a new well-
>>    known Large Community that provides a way for route leak prevention,
>>    detection, and mitigation.  The configuration process for this
>>    Community can be automated with the methodology for setting BGP roles
>>    that is described in ietf-idr-bgp-open-policy draft.
>>
>>
>> The IETF datatracker status page for this draft is:
>>
>> https://datatracker.ietf.org/doc/draft-ietf-grow-route-leak-detection-mitigation/
>>
>> There are also htmlized versions available at:
>>
>> https://tools.ietf.org/html/draft-ietf-grow-route-leak-detection-mitigation-01
>>
>> https://datatracker.ietf.org/doc/html/draft-ietf-grow-route-leak-detection-mitigation-01
>>
>> A diff from the previous version is available at:
>>
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-grow-route-leak-detection-mitigation-01
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>>
>
>
> --
> Best regards,
> Alexander Azimov
>


-- 
Best regards,
Alexander Azimov