[BGPCEP-344] Implement draft-ietf-idr-bgp-extended-messages Created: 22/Dec/15 Updated: 03/Mar/19 Due: 17/Mar/16 Resolved: 26/Feb/16 |
|
| Status: | Resolved |
| Project: | bgpcep |
| Component/s: | BGP |
| Affects Version/s: | Bugzilla Migration |
| Fix Version/s: | Bugzilla Migration |
| Type: | Bug | ||
| Reporter: | Robert Varga | Assignee: | Om Prakash |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 4831 |
| Description |
|
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-extended-messages defines a mechanism for extending the maximum size of a BGP message to 64kB. Supporting this capability will allow us to ingest routes more efficiently, as the peers will be free to pack more NLRIs with equal attributes into a single message. While the latest (-11) revision does not list the codepoint for the capability, a temporary IANA allocation has been granted on 9/30/2015 (https://www.iana.org/assignments/capability-codes/capability-codes.xhtml#capability-codes-2), hence we can safely implement this. |
| Comments |
| Comment by Milos Fabian [ 05/Feb/16 ] |
|
*Enhance bgp-message yang model to support "BGP Extended Message Capability". *Create codec for "BGP Extended Message Capability". Register the codec instance in BGP activator. *Make capability configurable for a peer - extend bgp-peer configuration yang model. If the option is enabled in a peer configuration, make sure the capability will be advertised in the Open Message. *If the capability is advertised by both sides, make sure the BGP Message Header Decoder is working with expected maximum message length (65535 bytes). |
| Comment by Milos Fabian [ 25/Feb/16 ] |