{"action":"created","issue":{"url":"https://api.github.com/repos/FRRouting/frr/issues/3462","repository_url":"https://api.github.com/repos/FRRouting/frr","labels_url":"https://api.github.com/repos/FRRouting/frr/issues/3462/labels{/name}","comments_url":"https://api.github.com/repos/FRRouting/frr/issues/3462/comments","events_url":"https://api.github.com/repos/FRRouting/frr/issues/3462/events","html_url":"https://github.com/FRRouting/frr/pull/3462","id":389903847,"node_id":"MDExOlB1bGxSZXF1ZXN0MjM3Nzg5MDM1","number":3462,"title":"Allow Class E addresses throughout FRR","user":{"login":"dtaht","id":108682,"node_id":"MDQ6VXNlcjEwODY4Mg==","avatar_url":"https://avatars3.githubusercontent.com/u/108682?v=4","gravatar_id":"","url":"https://api.github.com/users/dtaht","html_url":"https://github.com/dtaht","followers_url":"https://api.github.com/users/dtaht/followers","following_url":"https://api.github.com/users/dtaht/following{/other_user}","gists_url":"https://api.github.com/users/dtaht/gists{/gist_id}","starred_url":"https://api.github.com/users/dtaht/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dtaht/subscriptions","organizations_url":"https://api.github.com/users/dtaht/orgs","repos_url":"https://api.github.com/users/dtaht/repos","events_url":"https://api.github.com/users/dtaht/events{/privacy}","received_events_url":"https://api.github.com/users/dtaht/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":26,"created_at":"2018-12-11T18:50:53Z","updated_at":"2018-12-17T20:48:38Z","closed_at":null,"author_association":"NONE","pull_request":{"url":"https://api.github.com/repos/FRRouting/frr/pulls/3462","html_url":"https://github.com/FRRouting/frr/pull/3462","diff_url":"https://github.com/FRRouting/frr/pull/3462.diff","patch_url":"https://github.com/FRRouting/frr/pull/3462.patch"},"body":"There is no reason to conflate the multicast and class e address\r\nspaces within FRR.\r\n\r\n### Summary\r\nIt turns out that class-e addresses (240.0.0.0/4) are surprisingly usable - fully assignable and statically routable in freebsd, osx, ios, linux, and android. \r\n\r\nWith a very small set of patches all the routing daemons can be made to work also.\r\n\r\nWe are hoping to do a public test of public routability of 255.0.0.0/8 next year after setting up a larger testbed than the 4 testbeds we have so far, and after approaching iana and the ietf. \r\n\r\n### Related Issue\r\n\r\nThere's a document in progress, and all the other (extremely tiny!) patches we've need to make to the linux and other routing daemons is now up at: http://www.taht.net/classe/\r\n\r\n### Components\r\n\r\nThis touches everywhere broadcast, multicast and class e were conflated in frr. Public bogon lists are the only other problem we've seen to date, however the pim related changes should be looked at closely.\r\n"},"comment":{"url":"https://api.github.com/repos/FRRouting/frr/issues/comments/447993524","html_url":"https://github.com/FRRouting/frr/pull/3462#issuecomment-447993524","issue_url":"https://api.github.com/repos/FRRouting/frr/issues/3462","id":447993524,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0Nzk5MzUyNA==","user":{"login":"eqvinox","id":1715611,"node_id":"MDQ6VXNlcjE3MTU2MTE=","avatar_url":"https://avatars2.githubusercontent.com/u/1715611?v=4","gravatar_id":"","url":"https://api.github.com/users/eqvinox","html_url":"https://github.com/eqvinox","followers_url":"https://api.github.com/users/eqvinox/followers","following_url":"https://api.github.com/users/eqvinox/following{/other_user}","gists_url":"https://api.github.com/users/eqvinox/gists{/gist_id}","starred_url":"https://api.github.com/users/eqvinox/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eqvinox/subscriptions","organizations_url":"https://api.github.com/users/eqvinox/orgs","repos_url":"https://api.github.com/users/eqvinox/repos","events_url":"https://api.github.com/users/eqvinox/events{/privacy}","received_events_url":"https://api.github.com/users/eqvinox/received_events","type":"User","site_admin":false},"created_at":"2018-12-17T20:48:38Z","updated_at":"2018-12-17T20:48:38Z","author_association":"CONTRIBUTOR","body":"P.S.: a patch to refactor and centralize all the \"is this IPv4 address valid\" into one common `prefix_ipv4_valid_unicast()` function is obviously welcome and would be a great divide & conquer approach here; it's the majority of the work and a no-brainer to merge.  And as soon as everything is in one place, allowing 240./8 becomes a very short and easy second patch."}}
{"actor":{"display_login":"eqvinox"}}