| draft-ietf-idr-bgp-extended-messages-05.txt | draft-ietf-idr-bgp-extended-messages-06.txt | |||
|---|---|---|---|---|
| IDR Working Group K. Patel | IDR Working Group K. Patel | |||
| Internet-Draft D. Ward | Internet-Draft D. Ward | |||
| Intended status: Standards Track Cisco Systems | Intended status: Standards Track Cisco Systems | |||
| Expires: June 27, 2013 R. Bush | Expires: February 04, 2014 R. Bush | |||
| Internet Initiative Japan | Internet Initiative Japan | |||
| December 24, 2012 | August 03, 2013 | |||
| Extended Message support for BGP | Extended Message support for BGP | |||
| draft-ietf-idr-bgp-extended-messages-05 | draft-ietf-idr-bgp-extended-messages-06 | |||
| Abstract | Abstract | |||
| The BGP specification mandates a maximum BGP message size of 4096 | The BGP specification mandates a maximum BGP message size of 4096 | |||
| octets. As BGP is extended to support newer AFI/SAFIs, there is a | octets. As BGP is extended to support newer AFI/SAFIs, there is a | |||
| need to extend the maximum message size beyond 4096 octets. This | need to extend the maximum message size beyond 4096 octets. This | |||
| document updates [RFC4271] by providing an extension to BGP to extend | document updates [RFC4271] by providing an extension to BGP to extend | |||
| its current message size from 4096 octets to 65535 octets. | its current message size from 4096 octets to 65535 octets. | |||
| Requirements Language | Requirements Language | |||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
| "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to | "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to | |||
| be interpreted as described in RFC 2119 [RFC2119] only when they | be interpreted as described in RFC 2119 [RFC2119] only when they | |||
| appear in all upper case. They may also appear in lower or mixed | appear in all upper case. They may also appear in lower or mixed | |||
| case as English words, without normative meaning. | case as English words, without normative meaning. | |||
| Status of this Memo | Status of This Memo | |||
| This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
| provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on June 27, 2013. | This Internet-Draft will expire on February 04, 2014. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2012 IETF Trust and the persons identified as the | Copyright (c) 2013 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
| to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
| include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
| the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
| described in the Simplified BSD License. | described in the Simplified BSD License. | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 2. BGP Extended Message . . . . . . . . . . . . . . . . . . . . . 3 | 2. BGP Extended Message . . . . . . . . . . . . . . . . . . . . 2 | |||
| 3. Extended message Capability for BGP . . . . . . . . . . . . . . 3 | 3. Extended message Capability for BGP . . . . . . . . . . . . . 3 | |||
| 4. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 4. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 | 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 | 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 | 7. Security Considerations . . . . . . . . . . . . . . . . . . . 3 | |||
| 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 | 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 8.1. Normative References . . . . . . . . . . . . . . . . . . . 4 | 8.1. Normative References . . . . . . . . . . . . . . . . . . 4 | |||
| 8.2. Informative References . . . . . . . . . . . . . . . . . . 4 | 8.2. Informative References . . . . . . . . . . . . . . . . . 4 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 1. Introduction | 1. Introduction | |||
| The BGP specification [RFC4271] mandates a maximum BGP message size | The BGP specification [RFC4271] mandates a maximum BGP message size | |||
| of 4096 octets. As BGP is extended to support newer AFI/SAFIs and | of 4096 octets. As BGP is extended to support newer AFI/SAFIs and | |||
| newer capabilities (e.g., [I-D.ietf-sidr-bgpsec-overview]), there is | newer capabilities (e.g., [I-D.ietf-sidr-bgpsec-overview]), there is | |||
| a need to extend the maximum message size beyond 4096 octets. This | a need to extend the maximum message size beyond 4096 octets. This | |||
| draft provides an extension to BGP to extend its current message size | draft provides an extension to BGP to extend its current message size | |||
| limit from 4096 octets to 65535 octets. | limit from 4096 octets to 65535 octets. | |||
| 2. BGP Extended Message | 2. BGP Extended Message | |||
| A BGP message over 4095 octets in length is a Extended Message. | A BGP message over 4096 octets in length is a BGP Extended Message. | |||
| BGP extended messages have maximum message size of 65535 octets. The | BGP Extended Messages have maximum message size of 65535 octets. The | |||
| smallest message that may be sent consists of a BGP header without a | smallest message that may be sent consists of a BGP header without a | |||
| data portion (19 octets). | data portion (19 octets). | |||
| Multi-octet fields MUST be in network byte order. | Multi-octet fields MUST be in network byte order. | |||
| 3. Extended message Capability for BGP | 3. Extended message Capability for BGP | |||
| To advertise the BGP Extended Message Capability to a peer, a BGP | To advertise the BGP Extended Message Capability to a peer, a BGP | |||
| speaker uses BGP Capabilities Advertisement [RFC5492]. By | speaker uses BGP Capabilities Advertisement [RFC5492]. By | |||
| advertising the BGP Extended Message Capability to a peer, a BGP | advertising the BGP Extended Message Capability to a peer, a BGP | |||
| skipping to change at page 4, line 38 | skipping to change at page 4, line 22 | |||
| [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway | [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway | |||
| Protocol 4 (BGP-4)", RFC 4271, January 2006. | Protocol 4 (BGP-4)", RFC 4271, January 2006. | |||
| [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement | [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement | |||
| with BGP-4", RFC 5492, February 2009. | with BGP-4", RFC 5492, February 2009. | |||
| 8.2. Informative References | 8.2. Informative References | |||
| [I-D.ietf-sidr-bgpsec-overview] | [I-D.ietf-sidr-bgpsec-overview] | |||
| Lepinski, M. and S. Turner, "An Overview of BGPSEC", | Lepinski, M. and S. Turner, "An Overview of BGPSEC", | |||
| draft-ietf-sidr-bgpsec-overview-02 (work in progress), | draft-ietf-sidr-bgpsec-overview-02 (work in progress), May | |||
| May 2012. | 2012. | |||
| Authors' Addresses | Authors' Addresses | |||
| Keyur Patel | Keyur Patel | |||
| Cisco Systems | Cisco Systems | |||
| 170 W. Tasman Drive | 170 W. Tasman Drive | |||
| San Jose, CA 95134 | San Jose, CA 95134 | |||
| USA | USA | |||
| Email: keyupate@cisco.com | Email: keyupate@cisco.com | |||
| End of changes. 10 change blocks. | ||||
| 21 lines changed or deleted | 21 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||