├── rfc ├── 2328 │ ├── rfc2328.pdf │ └── rfc2328_中文版.pdf ├── 3107 │ ├── rfc3107.pdf │ └── rfc3107_中文版.pdf ├── 4271 │ ├── rfc4271.pdf │ └── rfc4271_中文版.pdf ├── 4364 │ ├── rfc4364.pdf │ └── rfc4364_中文版.pdf ├── 4456 │ ├── rfc4456.pdf │ └── rfc4456_中文版.pdf ├── 4577 │ ├── rfc4577.pdf │ └── rfc4577_中文版.pdf ├── 4724 │ ├── rfc4724.pdf │ └── rfc4724_中文版.pdf └── 4760 │ ├── rfc4760.pdf │ └── rfc4760_中文版.pdf ├── README.md └── LICENSE /rfc/2328/rfc2328.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/netwiki/share-doc/HEAD/rfc/2328/rfc2328.pdf -------------------------------------------------------------------------------- /rfc/3107/rfc3107.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/netwiki/share-doc/HEAD/rfc/3107/rfc3107.pdf -------------------------------------------------------------------------------- /rfc/4271/rfc4271.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/netwiki/share-doc/HEAD/rfc/4271/rfc4271.pdf -------------------------------------------------------------------------------- /rfc/4364/rfc4364.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/netwiki/share-doc/HEAD/rfc/4364/rfc4364.pdf -------------------------------------------------------------------------------- /rfc/4456/rfc4456.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/netwiki/share-doc/HEAD/rfc/4456/rfc4456.pdf -------------------------------------------------------------------------------- /rfc/4577/rfc4577.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/netwiki/share-doc/HEAD/rfc/4577/rfc4577.pdf -------------------------------------------------------------------------------- /rfc/4724/rfc4724.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/netwiki/share-doc/HEAD/rfc/4724/rfc4724.pdf -------------------------------------------------------------------------------- /rfc/4760/rfc4760.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/netwiki/share-doc/HEAD/rfc/4760/rfc4760.pdf -------------------------------------------------------------------------------- /rfc/2328/rfc2328_中文版.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/netwiki/share-doc/HEAD/rfc/2328/rfc2328_中文版.pdf -------------------------------------------------------------------------------- /rfc/3107/rfc3107_中文版.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/netwiki/share-doc/HEAD/rfc/3107/rfc3107_中文版.pdf -------------------------------------------------------------------------------- /rfc/4271/rfc4271_中文版.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/netwiki/share-doc/HEAD/rfc/4271/rfc4271_中文版.pdf -------------------------------------------------------------------------------- /rfc/4364/rfc4364_中文版.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/netwiki/share-doc/HEAD/rfc/4364/rfc4364_中文版.pdf -------------------------------------------------------------------------------- /rfc/4456/rfc4456_中文版.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/netwiki/share-doc/HEAD/rfc/4456/rfc4456_中文版.pdf -------------------------------------------------------------------------------- /rfc/4577/rfc4577_中文版.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/netwiki/share-doc/HEAD/rfc/4577/rfc4577_中文版.pdf -------------------------------------------------------------------------------- /rfc/4724/rfc4724_中文版.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/netwiki/share-doc/HEAD/rfc/4724/rfc4724_中文版.pdf -------------------------------------------------------------------------------- /rfc/4760/rfc4760_中文版.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/netwiki/share-doc/HEAD/rfc/4760/rfc4760_中文版.pdf -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | BGP、OSPF、MPLS路由协议RFC分享 2 | 3 | # 1. 概述 4 | ## 1.1 BGP 5 | 全球有无数台路由器，产生的路由更是多到无法想象。这些路由器分属于大大小小上千个ISP，分布在上百个国家和地区。这些国家由于政治、经济、文化背景千差万别，对互联网的理解也大相径庭。 6 | 7 | 边界网关协议（BGP）是运行于 TCP 上的一种自治系统的路由协议。 BGP 是唯一一个用来处理像因特网大小的网络的协议，也是唯一能够妥善处理好不相关路由域间的多路连接的协议。 8 | 9 | ## 1.2 OSPF 10 | OSPF(Open Shortest Path First - 开放式最短路径优先是一个内部网关协议，用于在单一自治系统内决策路由。是对链路状态路由协议的一种实现。著名的Dijkstra算法被用来计算最短路径树。OSPF支持负载均衡和基于服务类型的选路，也支持多种路由形式，如特定主机路由和子网路由等。 11 | 12 | ## 1.3 MPLS 13 | 多协议标签交换（Multi-Protocol Label Switching，MPLS）是新一代的IP高速骨干网络交换标准，由因特网工程任务组（Internet Engineering Task Force，IETF）提出。 14 | 15 | MPLS是利用标记（label）进行数据转发的。当分组进入网络时，要为其分配固定长度的短的标记，并将标记与分组封装在一起，在整个转发过程中，交换节点仅根据标记进行转发。 16 | 17 | # 2. 分享 18 | 看看上面的描述大家是不是对于上面的三种协议非常感兴趣了，这三种协议非常复杂，不是短短一篇文件就可以介绍完毕的。 19 | 20 | 如果想着学习还得通过专门的学习资料才行，比如《TCP/IP路由技术》，思科路由相关的大量书籍，华三《网络大爬虫》及《网络之路》作为入门。 21 | 22 | 但是这些都不是最好的，最好的是`RFC`，其包含了关于Internet的几乎所有重要的文字资料。如果你想成为网络方面的专家，那么RFC无疑是最重要也是最经常需要用到的资料之一，所以RFC享有网络知识**圣经**之美誉。 23 | 24 | 但是RFC都是英文的对于很多小伙伴来说都不太友好，我当年学习时，为了方便就边学习边翻译，然后翻译了几个主要的RFC这里分析给大家了。如果觉得翻译的水平不咋地也可以看原文哦，也会附上。 25 | 26 | ## 2.1 rfc-4271 27 | [中文版](https://github.com/netwiki/share-doc/blob/master/rfc/4271/rfc4271_%E4%B8%AD%E6%96%87%E7%89%88.pdf) 28 | [原版](https://github.com/netwiki/share-doc/blob/master/rfc/4271/rfc4271.pdf) 29 | 30 | 本文讨论了一种自治系统路由协议，即边界网关协议（BGP）。 31 | BGP宣告系统的主要功能是与其他BGP系统交换网络可达性信息。这个网络可达性信息包括历经的一系列自治系统（ASes）可达信息。该信息足以构建AS可达性连通图，对路由环路进行修剪，在AS级别，可能会执行一些策略决定。 32 | BGP-4提供了一套支持无类别域间路由（CIDR）。这些机制包括支持公告一组目的地作为IP前缀，并消除BGP内网络“类别”的概念。BGP-4也介绍路由聚合机制，包括AS路径的聚合。 33 | 34 | ## 2.2 rfc-3107 35 | [中文版](https://github.com/netwiki/share-doc/blob/master/rfc/3107/rfc3107_%E4%B8%AD%E6%96%87%E7%89%88.pdf) 36 | [原版](https://github.com/netwiki/share-doc/blob/master/rfc/3107/rfc3107.pdf) 37 | 38 | 本文档规定了用于特定路由的标签映射信息的方式，他们搭载在同一边界网关协议（BGP）更新消息中，用于分发本身路由。当BGP用于分发特定路由时，也可以用于分发多协议标签交换（MPLS）映射到该路由标签。 39 | 40 | ## 2.3 rfc-4364 41 | [中文版](https://github.com/netwiki/share-doc/blob/master/rfc/4364/rfc4364_%E4%B8%AD%E6%96%87%E7%89%88.pdf) 42 | [原版](https://github.com/netwiki/share-doc/blob/master/rfc/4364/rfc4364.pdf) 43 | 44 | 本文档描述了服务提供商可以使用IP骨干网为其客户提供IP虚拟专用网（VPN）的方法。该方法使用“peer 模型”，其中，客户边缘路由器（CE路由器）将路由发送到服务提供商边缘路由器（PE路由器）；不同站点的CE路由器相互不对等，所以VPN的路由算法看不到“重叠”。数据包通过骨干区隧道，使核心路由器不需要知道VPN路由。 45 | 46 | ## 2.4 rfc-4456 47 | [中文版](https://github.com/netwiki/share-doc/blob/master/rfc/4456/rfc4456_%E4%B8%AD%E6%96%87%E7%89%88.pdf) 48 | [原版](https://github.com/netwiki/share-doc/blob/master/rfc/4456/rfc4456.pdf) 49 | 50 | 边界网关协议（BGP）是一种为TCP/IP互联网设计的自治系统间路由协议。通常，单个AS中的所有BGP speaker必须为全连接的，以便任何外部路由信息必须重新分配给自治系统（AS）内所有其他路由器。这是一个严重的规模问题，已经在几个替代方案很好地记录了。 51 | 本文档描述了一种称为“路由反射”方法的使用和设计来减轻对“全连接”内部BGP（IBGP）的需求。 52 | 53 | ## 2.5 rfc-4577 54 | [中文版](https://github.com/netwiki/share-doc/blob/master/rfc/4577/rfc4577_%E4%B8%AD%E6%96%87%E7%89%88.pdf) 55 | [原版](https://github.com/netwiki/share-doc/blob/master/rfc/4577/rfc4577.pdf) 56 | 57 | 许多服务提供商提供虚拟专用网络（VPN）服务给其客户，使用的技术是客户边缘路由器（CE路由器）作为提供商边缘路由器（PE路由器）的路由peer。边界网关协议（BGP）通过供应商的IP骨干网用于分发客户的路由，以及多协议标签交换（MPLS）通过提供商的骨干网用隧道传输客户数据包。这被称为“BGP/MPLS IP VPN“，BGP/MPLS IP VPN的基本规范假设PE路由器和CE路由器之间接口上的路由协议是BGP。本文档扩展了该规范，通过允许PE/CE接口的路由协议为开放最短路径优先（OSPF）协议。 58 | 59 | ## 2.6 rfc-4724 60 | [中文版](https://github.com/netwiki/share-doc/blob/master/rfc/4724/rfc4724_%E4%B8%AD%E6%96%87%E7%89%88.pdf) 61 | [原版](https://github.com/netwiki/share-doc/blob/master/rfc/4724/rfc4724.pdf) 62 | 63 | 本文档描述了一种BGP机制，其有助于最小化BGP重启导致对路由的负面影响。End-of-RIB标记被详细描述并且可以用来传送路由收敛信息。一种新的BGP能力，称为“GR能力”定义为允许BGP speaker表达其具有BGP重启期间保持转发状态的能力。最后，概述了TCP会话终止/重新建立期间暂时保留路由信息的处理。 64 | 本文档中描述的机制适用于所有路由器，即包括在BGP重启期间能够保持转发状态和那些没有（尽管后者只需要实现此文件描述的机制的一个子集）。 65 | 66 | ## 2.7 rfc-4760 67 | [中文版](https://github.com/netwiki/share-doc/blob/master/rfc/4760/rfc4760_%E4%B8%AD%E6%96%87%E7%89%88.pdf) 68 | [原版](https://github.com/netwiki/share-doc/blob/master/rfc/4760/rfc4760.pdf) 69 | 70 | 本文档定义了BGP-4的扩展，使其能够携带多种网络层协议的路由信息（如IPv6，IPX，L3VPN等）。扩展是向后兼容的 - 支持扩展的路由器可以与不支持扩展的路由器互操作。 71 | 72 | ## 2.8 rfc-2328 73 | [中文版](https://github.com/netwiki/share-doc/blob/master/rfc/2328/rfc2328_%E4%B8%AD%E6%96%87%E7%89%88.pdf) 74 | [原版](https://github.com/netwiki/share-doc/blob/master/rfc/2328/rfc2328.pdf) 75 | 76 | 此文是往上已有的文档，我这就不重新造轮子了。 77 | 78 | 本备忘录说明了OSPF协议版本2。OSPF 是一种连接状态/link-state 路由协议，被设计用于单一的自制系统/Autonomous System 中。每个OSPF路由器都维持着同样的数据库以描述AS的拓扑结构，并以此数据库来创建最短路径树并计算路由表。 79 | OSPF 在发现拓扑改变后，仅利用很少的路由流量就可以快速的重新计算出路径。OSPF 提供等值多路径。通过提供区域/area 路径，来提供额外的路径保护并可以减少协议所需要的流量。此外，所有的OSPF 路由信息交换都经过验证。 80 | 81 | 82 | 83 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | --------------------------------------------------------------------------------