"there was a common expectation that IP packets on the Internet were limited to 576 bytes.” no there was a common _requirement_ that all IPv4 hosts had to accept an IP packet up to 576 bytes iun suze RFC791: Every internet destination must be able to receive a datagram of 576 octets either in one piece or in fragments to be reassembled. "Finally, many more resolvers today are capable of falling back to TCP when they receive a truncated response over UDP” really? Where is the study that publishes this finding? thanks, Geoff
On 30 Apr 2020, at 10:44 pm, Andrew McConachie <andrew.mcconachie@icann.org> wrote:
Dear RSSAC Caucus Members,
According to the RSSAC Work Plan the RSSAC should update its FAQ before December every year. <https://www.icann.org/en/system/files/files/rssac-work-plan-05feb20-en.pdf>
Recently the RSSAC recieved a question via the ask-rssac@icann.org mailing address concerning why the limit of 13 root servers had been set in the 1990s. Through researching that question with the help of input from community members we developed a new answer for this question in the RSSAC FAQ. Rather than just update that single question in the FAQ the RSSAC Admin Committee decided to use this as an opportunity to update the entire FAQ for 2020.
The current FAQ: <https://www.icann.org/groups/rssac/faq>
The draft new FAQ: <https://docs.google.com/document/d/13znyayqFMBXxPIRrKbhyQDk1dO7LOy9oFwedy-oj...>
Please review the new Draft FAQ and provide any input by May 14th, 2020.
Thanks, Andrew
_______________________________________________ rssac-caucus mailing list rssac-caucus@icann.org https://mm.icann.org/mailman/listinfo/rssac-caucus
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.