[GTER] Fwd: RFC 8092 on BGP Large Communities Attribute

[Rogerio Alves]

O Mikrotik suporta sim communities de 32bits.
Eu ainda não encontrei para juniper!

Att.Rogerio Alves

2017-02-18 17:18 GMT-02:00 Rubens Kuhl <rubensk at gmail.com>:

> Bom, acabaram as desculpas para o RouterOS não implementar "Large
> Communities", agora que é uma RFC. Enquanto isso, o GoBGP já suporta há...
> meses ?
>
> http://largebgpcommunities.net/implementations/
>
>
> Rubens
>
> ---------- Forwarded message ----------
> From: Greg Hankins <ghankins at mindspring.com>
> Date: Sat, Feb 18, 2017 at 4:59 PM
> Subject: RFC 8092 on BGP Large Communities Attribute
> To: nanog at nanog.org
>
>
> Hey NANOG,
>
> As a followup to our NANOG 68 presentation in Dallas on BGP Large
> Communites
> (https://www.nanog.org/meetings/abstract?id=2990), RFC 8092 as just
> published
> on Thursday.  BGP Large Communities solve a big issue for network
> operators,
> by providing a simple way to signal meta-information between networks
> using 16-bit or 32-bit ASNs.
>
> Publication as an RFC was accomplished in a remarkably short time, due to
> the
> close cooperation and strong consensus between the IETF IDR Working Group
> and network operators.  The idea progressed rapidly from its inception in
> March 2016, to the first Internet-Draft in September 2016, to its final
> IESG approval stages in December 2016, and finally to publication as an
> RFC in barely seven months.
>
> In addition the the final standard, a number of implementations and tools
> were developed along the way, so that network operators can test and deploy
> the new technology now.  The latest list of software that support BGP
> Large Communities is here: http://largebgpcommunities.net/implementations/
> .
>
> While the final milestone to RFC publication has been reached, this is by
> no
> means the end of the story!  Work on the "Usage of BGP Large Communities"
> I-D (https://tools.ietf.org/html/draft-ietf-grow-large-communities-usage)
> continues, to provide examples and inspiration for network operators on
> how to use BGP Large Communities.
>
> It’s time to celebrate, as 32-bit ASNs are first class citizens now too!
>
> More information can be found here: http://largebgpcommunities.net/ .
>
> RFC 8092 can be found here: https://tools.ietf.org/html/rfc8092 .
>
> Kind regards,
> Greg
>
> --
> Greg Hankins <ghankins at mindspring.com>
>
> ----- Forwarded message from rfc-editor at rfc-editor.org -----
> Date: Thu, 16 Feb 2017 10:23:49 -0800 (PST)
> From: rfc-editor at rfc-editor.org
> To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
> Cc: drafts-update-ref at iana.org, idr at ietf.org, rfc-editor at rfc-editor.org
> Subject: [Idr] RFC 8092 on BGP Large Communities Attribute
>
> A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 8092
>
>         Title:      BGP Large Communities Attribute
>         Author:     J. Heitz, Ed.,
>                     J. Snijders, Ed.,
>                     K. Patel,
>                     I. Bagdonas,
>                     N. Hilliard
>         Status:     Standards Track
>         Stream:     IETF
>         Date:       February 2017
>         Mailbox:    jheitz at cisco.com,
>                     job at ntt.net,
>                     keyur at arrcus.com,
>                     ibagdona.ietf at gmail.com,
>                     nick at inex.ie
>         Pages:      8
>         Characters: 15979
>         Updates/Obsoletes/SeeAlso:   None
>
>         I-D Tag:    draft-ietf-idr-large-community-12.txt
>
>         URL:        https://www.rfc-editor.org/info/rfc8092
>
>         DOI:        10.17487/RFC8092
>
> This document describes the BGP Large Communities attribute, an
> extension to BGP-4.  This attribute provides a mechanism to signal
> opaque information within separate namespaces to aid in routing
> management.  The attribute is suitable for use with all Autonomous
> System Numbers (ASNs) including four-octet ASNs.
>
> This document is a product of the Inter-Domain Routing Working Group of the
> IETF.
>
> This is now a Proposed Standard.
>
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and
> suggestions
> for improvements.  Please refer to the current edition of the Official
> Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
> standardization state and status of this protocol.  Distribution of this
> memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   https://www.ietf.org/mailman/listinfo/ietf-announce
>   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
> For searching the RFC series, see https://www.rfc-editor.org/search
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
> Association Management Solutions, LLC
>
>
> _______________________________________________
> Idr mailing list
> Idr at ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
> ----- End forwarded message -----
> --
> gter list    https://eng.registro.br/mailman/listinfo/gter