New ID submission, as below.  This is to solve a real world problem.

Comments welcome.

Nick

[email protected] wrote:
> A new version of I-D, draft-hilliard-grow-no-export-via-rs-00.txt
> has been successfully submitted by Nick Hilliard and posted to the
> IETF repository.
> 
> Name:         draft-hilliard-grow-no-export-via-rs
> Revision:     00
> Title:                The BGP NO_EXPORT_VIA_RS Community for Route Servers
> Document date:        2017-10-08
> Group:                Individual Submission
> Pages:                5
> URL:            
> https://www.ietf.org/internet-drafts/draft-hilliard-grow-no-export-via-rs-00.txt
> Status:         
> https://datatracker.ietf.org/doc/draft-hilliard-grow-no-export-via-rs/
> Htmlized:       
> https://tools.ietf.org/html/draft-hilliard-grow-no-export-via-rs-00
> Htmlized:       
> https://datatracker.ietf.org/doc/html/draft-hilliard-grow-no-export-via-rs-00
> 
> 
> Abstract:
>    This document describes a BGP Well-known Community called
>    NO_EXPORT_VIA_RS.  This community allows BGP route server clients to
>    instruct an Internet Exchange BGP Route Server to tag prefixes
>    destined for other route server clients with the NO_EXPORT Well-Known
>    Community.  This mechanism allows route server clients to
>    transitively control distribution of their prefixes in other
>    Autonomous Systems connected to the Internet Exchange Route Server.
> 
> 
>                                                                               
>     
> 
> 
> 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.
> 
> The IETF Secretariat
> 

_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow

Reply via email to