draft-ietf-idr-bgp-extended-messages-11.txt   draft-ietf-idr-bgp-extended-messages-12.txt 
Network Working Group K. Patel Network Working Group R. Bush
Internet-Draft D. Ward Internet-Draft Internet Initiative Japan
Updates: 4271 (if approved) Cisco Systems Updates: 4271 (if approved) K. Patel
Intended status: Standards Track R. Bush Intended status: Standards Track D. Ward
Expires: January 25, 2016 Internet Initiative Japan Expires: November 22, 2016 Cisco Systems
July 24, 2015 May 21, 2016
Extended Message support for BGP Extended Message support for BGP
draft-ietf-idr-bgp-extended-messages-11 draft-ietf-idr-bgp-extended-messages-12
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 the BGP specification in RFC4271 by providing an document updates the BGP specification in RFC4271 by providing an
extension to BGP to extend its current message size from 4096 octets extension to BGP to extend its current message size from 4096 octets
to 65535 octets. to 65535 octets.
skipping to change at page 1, line 45 skipping to change at page 1, line 45
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 January 25, 2016. This Internet-Draft will expire on November 22, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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
skipping to change at page 3, line 41 skipping to change at page 3, line 41
Applications generating messages which might be encapsulated within Applications generating messages which might be encapsulated within
BGP messages MUST limit the size of their payload to take into BGP messages MUST limit the size of their payload to take into
account the maximum message size and all encapsulation overheads on account the maximum message size and all encapsulation overheads on
the path the encapsulated data are expected to traverse. the path the encapsulated data are expected to traverse.
5. Error Handling 5. Error Handling
A BGP speaker that has the ability to use extended messages but has A BGP speaker that has the ability to use extended messages but has
not advertised the BGP Extended Messages capability, presumably due not advertised the BGP Extended Messages capability, presumably due
to configuration, SHOULD NOT accept such a message. to configuration, SHOULD NOT accept an extended message. A speaker
MAY implement a more liberal policy and accept extended messages even
from a peer that has not advertised the capability.
However, a BGP speaker that does not advertise the BGP Extended However, a BGP speaker that does not advertise the BGP Extended
Messages capability might also genuinely not support extended Messages capability might also genuinely not support extended
messages. Such a speaker would be expected to follow the error messages. Such a speaker would be expected to follow the error
handling procedures of [RFC4221], Section 6.1, and reset the session handling procedures of [RFC4221], Section 6.1, and reset the session
with a Bad Message Length NOTIFICATION if it receives an extended with a Bad Message Length NOTIFICATION if it receives an extended
message. A speaker that treats an improper extended message as a message. A speaker that treats an improper extended message as a
fatal error should do likewise. fatal error, as described in the preceding paragraph, MUST do
likewise.
6. Acknowledgements 6. Acknowledgements
The authors thank Enke Chen, Susan Hares, John Scudder, John Levine, The authors thank Enke Chen, Susan Hares, John Scudder, John Levine,
and Job Snijders for their input. and Job Snijders for their input.
7. IANA Considerations 7. IANA Considerations
The IANA is requested to register a new BGP Capability Code to be The IANA is requested to register a new BGP Capability Code to be
named BGP Extended Message Capability and referring to this document. named BGP Extended Message Capability and referring to this document.
skipping to change at page 5, line 7 skipping to change at page 5, line 7
9.2. Informative References 9.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), May draft-ietf-sidr-bgpsec-overview-02 (work in progress), May
2012. 2012.
Authors' Addresses Authors' Addresses
Randy Bush
Internet Initiative Japan
5147 Crystal Springs
Bainbridge Island, Washington 98110
US
Email: randy@psg.com
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
Dave Ward Dave Ward
Cisco Systems Cisco Systems
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: dward@cisco.com Email: dward@cisco.com
Randy Bush
Internet Initiative Japan
5147 Crystal Springs
Bainbridge Island, Washington 98110
US
Email: randy@psg.com
 End of changes. 8 change blocks. 
11 lines changed or deleted 22 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/