[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fgpoHK4AI34uOUINz4tlK0abalHDimQy9D4lxgV8cGzc":3},{"item":4,"related":44},{"id":5,"type":6,"title":7,"slug":8,"summary":9,"body":10,"coverUrl":11,"productScreenshots":12,"productLinks":13,"authorName":14,"authorUrl":15,"authorSubject":16,"category":17,"tags":22,"sourceLabel":35,"sourceName":36,"sourceUrl":37,"status":38,"seoTitle":7,"seoDescription":9,"canonicalUrl":35,"isFeatured":39,"sno":40,"sortOrder":41,"publishedAt":42,"updatedAt":43,"createdAt":43},"58fc0fe2-4392-402e-bd43-68da30f7b50f","article","RPKI 路由源验证：怎样确认一个网络前缀确实由某个 AS 宣告？","rpki-bgp-route-origin-validation","RPKI 路由源验证通过 ROA 检查前缀与起源 AS 是否匹配。本文解释 Valid、Invalid、NotFound 的含义，以及它为何不验证整条路由路径。","互联网路由系统需要不断传播“某个 IP 前缀可以经由哪个自治系统（AS）到达”的信息。若有人误配置或恶意宣告了并不属于自己的前缀，流量可能被错误引导。RPKI（Resource Public Key Infrastructure）路由源验证可以帮助网络运营者检查：某个路由通告中的起源 AS，是否被该前缀的资源持有者授权。\n\n资源持有者可以发布 ROA（Route Origin Authorization），描述一个 IP 前缀允许哪些 AS 作为起源，以及可接受的前缀长度范围。验证器据此比较收到的 BGP 路由通告，通常给出 Valid、Invalid 或 NotFound 等状态。Valid 表示找到匹配授权；Invalid 表示有授权信息但路由起源或前缀长度不符合；NotFound 则表示当前没有可用的授权记录。\n\n要特别区分“路由源验证”和“整条路径验证”。RPKI ROA 主要回答谁有权作为这个前缀的起源，不会单独证明 BGP AS_PATH 中经过的每个自治系统都真实可信，也不意味着整个路由协议已经获得完整密码学保护。看到某条路径经过了某些 AS，并不能仅凭 RPKI 起源验证就断言这些中间路径都已验证。\n\n网络运营者如何处理 Invalid 路由是一项策略选择。常见的做法可以拒绝或降低其优先级，但上线前需要评估 ROA 是否准确、授权是否及时更新，以及过滤策略会怎样影响连通性。错误配置的 ROA 可能使合法路由变成 Invalid；NotFound 也不等于恶意，只表示尚无对应授权。验证结果要和运营流程、监控与变更管理配套。\n\n这一机制的意义不在于“一键防劫持”，而在于让资源授权信息能被机器化检查，并在路由决策中作为一个信号。它是一层可部署的源授权保护，需要网络各方正确维护记录，不能替代对路由变化、上游选择和运维流程的持续监控。\n\nRPKI 把 IP 地址资源的分配关系连接到路由起源检查，为互联网路由安全增加了一道验证步骤；理解它的边界，尤其是它不验证完整路径，和理解它本身同样重要。\n\n来源：[RFC 6811：BGP Prefix Origin Validation](https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc6811.html)","\u002Fuploads\u002F2026-10-06\u002F073132a3-dfee-42bd-b7f1-9f6805946e8b.jpg",[],[],"Foundit","https:\u002F\u002Ffoundit.cn","foundit-ai-editorial",{"id":18,"name":19,"slug":20,"description":21},"6179d3b6-dc34-4483-9ded-3cd9f1b37a47","科普","abbreviation","介绍各领域新兴概念",[23,27,31],{"id":24,"name":25,"slug":26},"7c76bfc2-f80f-4ee0-a95d-27bd8708b434","技术","slug",{"id":28,"name":29,"slug":30},"4c2bbea6-eab7-40a8-8447-1de478ff7749","分析","analyse",{"id":32,"name":33,"slug":34},"68cedb55-2cac-412f-8f81-fda8c7d686dd","思考","thought",null,"RFC 6811：BGP Prefix Origin Validation","https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc6811.html","published",false,40,0,"2026-10-06T00:00:00.000Z","2026-10-06T07:51:36.206Z",[45,53,61],{"id":46,"type":6,"title":47,"slug":48,"summary":49,"coverUrl":50,"authorName":14,"sno":51,"publishedAt":42,"createdAt":52},"d9dbb54d-46d3-4b1b-ad49-e4e049264170","Sloppy Quorum 与 Hinted Handoff：副本故障时，数据能先寄存到别处吗？","sloppy-quorum-hinted-handoff-replica-recovery","Dynamo 风格的宽松 quorum 可在首选副本不可达时暂存写入，并通过 hinted handoff 在故障恢复后补回。本文解释其可用性收益与一致性边界。","\u002Fuploads\u002F2026-10-06\u002Fc62b7ad0-304e-4a21-a245-aeee01573342.jpg",53,"2026-10-06T07:51:44.617Z",{"id":54,"type":6,"title":55,"slug":56,"summary":57,"coverUrl":58,"authorName":14,"sno":51,"publishedAt":59,"createdAt":60},"e4131e64-25af-4b75-8c90-d78212d5b7d9","BBR：网络拥塞为什么不能只看丢包？","bbr-bandwidth-round-trip-congestion-control","BBR 通过估计瓶颈带宽和往返传播时间来调节发送速率，把吞吐、延迟与在途数据纳入拥塞控制，而不是只等待丢包。","\u002Fuploads\u002F2026-09-26\u002F7a21c7b9-a2ee-4f70-b3fe-b10fca22655d.jpg","2026-09-27T00:00:00.000Z","2026-09-26T16:26:20.942Z",{"id":62,"type":6,"title":63,"slug":64,"summary":65,"coverUrl":66,"authorName":14,"sno":67,"publishedAt":59,"createdAt":68},"9fa30ea6-8110-41fd-b241-37cd2fd2d55f","Hybrid Logical Clock：没有可靠全球时钟，分布式系统如何记录先后？","hybrid-logical-clock-distributed-ordering","混合逻辑时钟把接近现实的物理时间与逻辑计数结合起来，在不要求全球时钟完美同步的前提下表达因果顺序。","\u002Fuploads\u002F2026-09-26\u002F0bb95ad8-47c0-4ed3-ab8f-421409fff373.jpg",56,"2026-09-26T16:26:31.764Z"]