Alex:

 

The request to get an Community class for a well-known transmit 4 byte ASes 
needs a draft.  

I’ve volunteered to write such a draft for this draft, and I have text started. 
  

I will send you a draft by August 27th.     If you have something you wish to 
put in it, please let me.

 

Just a warning, during the next 2 weeks, I will be offline more than online.  

As a professor, I am taking this time to finish some of my own school work. 

 

Cheerily, Susan Hares 

 

From: GROW [mailto:grow-boun...@ietf.org] On Behalf Of Alexander Azimov
Sent: Friday, July 26, 2019 1:12 PM
To: grow@ietf.org
Cc: i-d-annou...@ietf.org
Subject: Re: [GROW] I-D Action: 
draft-ietf-grow-route-leak-detection-mitigation-01.txt

 

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-dra...@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/
 
<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

_______________________________________________
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow

Reply via email to