[homenet] IPv4 source-specific routing in the Linux kernel
« Finally, Martin Kafai Lau asked if work should be done to merge the IPv4 and IPv6 FIB (forwarding information base) trees. The FIB tree is the data structure that represents routing tables in the Linux kernel. Miller explained that the two trees are not semantically equivalent: while IPv6 does source-address lookup and routing, IPv4 does not. We can't remove the source lookups from IPv6, because "people probably use that". According to Alexander Duyck, adding source tables to IPv4 would degrade performance to the level of IPv6 performance, which was jokingly referred to as an incentive to switch to IPv6. « More seriously, Sowa argued that using the same compressed tree IPv4 uses in IPv6 could make sense. People may want to have source routing in IPv4 as well. Miller argued that the kernel is optimized for 32-bit addresses in IPv4, and conceded that it could be scaled to 64-bit subnets, but 128-bit addresses would be much harder. Sowa suggested that they could be limited to 64 bits, as global routes that are announced over BGP usually have such a limit, and more specific routes are usually at discrete prefixes like /65, /127 (for interconnect links) or /128 for (for point-to-point links). He expressed concerns over the reliability of such an implementation so, at this point, it is unlikely that the data structures could be merged. What is more likely is that the code path could be merged and simplified, while keeping the data structures separate. » https://lwn.net/Articles/719297/ ___ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
[homenet] I-D Action: draft-ietf-homenet-dot-05.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Home Networking of the IETF. Title : Special Use Domain '.home.arpa' Authors : Pierre Pfister Ted Lemon Filename: draft-ietf-homenet-dot-05.txt Pages : 7 Date: 2017-04-20 Abstract: This document specifies the behavior that is expected from the Domain Name System with regard to DNS queries for names ending with '.home.arpa.', and designates this domain as a special-use domain name. The '.home.arpa' domain replaces '.home' as the default domain used by the Home Networking Control Protocol (HNCP). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-homenet-dot/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-homenet-dot-05 https://datatracker.ietf.org/doc/html/draft-ietf-homenet-dot-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-dot-05 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
[homenet] homenet - New Meeting Session Request for IETF 99
A new meeting session request has just been submitted by Ray Bellis, a Chair of the homenet working group. - Working Group Name: Home Networking Area Name: Internet Area Session Requester: Ray Bellis Number of Sessions: 1 Length of Session(s): 1.5 Hours Number of Attendees: 120 Conflicts to Avoid: First Priority: v6ops intarea dnsop dnssd 6man babel Second Priority: mptcp People who must be present: Mark Townsley Terry Manderson Ray Bellis Resources Requested: Special Requests: Monday morning or immediately after lunch Monday strongly preferred as Ray has to be in the UK on Tuesday for his 25th wedding anniversary. Mark also has family commitments later in the week. - ___ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
