Dear GROW WG, Job and I incorporated the changes requested during the last WG session. The changes are mainly: - IP networks are also covered besides IXPs - Renaming of the BLACKHOLEIXP community to BLACKHOLE - Overhauled operational recommendations (section 3)
Best regards, Thomas > On 29 Jul 2015, at 19:18, [email protected] wrote: > > > A new version of I-D, draft-ymbk-grow-blackholing-01.txt > has been successfully submitted by Thomas King and posted to the > IETF repository. > > Name: draft-ymbk-grow-blackholing > Revision: 01 > Title: BLACKHOLE BGP Community for Blackholing > Document date: 2015-07-29 > Group: Individual Submission > Pages: 7 > URL: > https://www.ietf.org/internet-drafts/draft-ymbk-grow-blackholing-01.txt > Status: https://datatracker.ietf.org/doc/draft-ymbk-grow-blackholing/ > Htmlized: https://tools.ietf.org/html/draft-ymbk-grow-blackholing-01 > Diff: > https://www.ietf.org/rfcdiff?url2=draft-ymbk-grow-blackholing-01 > > Abstract: > This document describes the use of a well-known Border Gateway > Protocol (BGP) community for blackholing at IP networks and Internet > Exchange Points (IXP). This well-known advisory transitive BGP > community, namely BLACKHOLE, allows an origin AS to specify that a > neighboring IP network or IXP should blackhole a specific IP prefix. > > > > > > 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 >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
