ReECN Adding Accountability for Causing Congestion to TCPIPReECN造成拥塞TCPIP加入问责.pptVIP

下载本文档

5
0
约1.59万字
约 33页
2017-03-08 发布于上海
举报
版权申诉

ReECN Adding Accountability for Causing Congestion to TCPIPReECN造成拥塞TCPIP加入问责.ppt

1、原创力文档（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。。
2、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
4、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
5、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
6、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
7、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

ReECN Adding Accountability for Causing Congestion to TCPIPReECN造成拥塞TCPIP加入问责

Re-ECN:Adding Accountability for Causing Congestion to TCP/IP Bob Briscoe, BT UCLArnaud Jacquet, BT Alessandro Salvatori, BT IETF-65 tsvwg Mar 2006 problem statement (§1) previous draft-00 focused on how to do policing problem solved is actually how to allow some networks to do policing conservative networks might want to throttle if unresponsive to congestion (VoIP, video, DDoS) middle ground might want to cap congestion caused per user (e.g. 24x7 heavy sources) liberal networks open access, no restrictions evolution of hi-speed/different congestion control,... new worms many believe Internet is broken not IETF role to pre-judge which is right answer to these socio-economic issues Internet needs all these answers – balance to be determined by natural selection ‘do-nothing’ doesn’t maintain liberal status quo, we just get more walls re-ECN goals just enough support for conservative policies without breaking ‘net neutrality’ manage evolution of new congestion control, even for liberal → conservative flows nets that allow their users to cause congestion in other nets, can be held accountable doc roadmap completely updated draft-01 Re-ECN: Adding Accountability for Causing Congestion to TCP/IP IETF-64 Vancouver Nov 05 initial draft, intent then: hold ECN nonce (RFC3540) at experimental get you excited enough to read it, and break it thanks to reviewers (on and off-list); you broke it (co-author noticed flaw too) now updated draft: draft-briscoe-tsvwg-re-ecn-tcp-01.txt ultimate intent: standards track immediate intent: re-ECN worth using last reserved bit in IP v4? changed re-ECN wire protocol in IPv4 (§3) propose Re-ECN Extension (RE) flag for IPv4: propose to use bit 48(was reserved) set by sender, unchanged e2e once flow established sender re-inserts ECN feedback into forward data (“re-ECN”) as follows re-ECN sender always sets ECT(1) on every congestion event from transport (e.g. TCP) sender blanks RE else sets RE conceptually, ‘worth’ of packet