default search action
Fernando Gont
Person information
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
2020 – today
- 2023
- [i40]Fernando Gont, Iván Arce:
Unfortunate History of Transient Numeric Identifiers. RFC 9414: 1-27 (2023) - [i39]Fernando Gont, Iván Arce:
On the Generation of Transient Numeric Identifiers. RFC 9415: 1-37 (2023) - [i38]Fernando Gont, Iván Arce:
Security Considerations for Transient Numeric Identifiers Employed in Network Protocols. RFC 9416: 1-10 (2023) - 2022
- [i37]Fernando Gont, Will (Shucheng) Liu:
Recommendations on the Filtering of IPv6 Packets Containing IPv6 Extension Headers at Transit Routers. RFC 9288: 1-33 (2022) - 2021
- [i36]Fernando Gont, Jan Zorz, Richard Patterson:
Reaction of IPv6 Stateless Address Autoconfiguration (SLAAC) to Flash-Renumbering Events. RFC 8978: 1-11 (2021) - [i35]Fernando Gont, Suresh Krishnan, Thomas Narten, Richard Draves:
Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6. RFC 8981: 1-20 (2021) - [i34]Fernando Gont, Jan Zorz, Richard Patterson, Bernie Volz:
Improving the Reaction of Customer Edge Routers to IPv6 Renumbering Events. RFC 9096: 1-11 (2021) - [i33]Fernando Gont, Nick Hilliard, Gert Doering, Warren Kumari, Geoff Huston, Will (Shucheng) Liu:
Operational Implications of IPv6 Packets with Extension Headers. RFC 9098: 1-17 (2021) - [i32]Fernando Gont, Guillermo Gont, Miroslav Lichvar:
Network Time Protocol Version 4: Port Randomization. RFC 9109: 1-9 (2021) - 2020
- [i31]Ron Bonica, Fred Baker, Geoff Huston, Robert M. Hinden, Ole Troan, Fernando Gont:
IP Fragmentation Considered Fragile. RFC 8900: 1-23 (2020)
2010 – 2019
- 2017
- [i30]Fernando Gont, Will (Shucheng) Liu, Tore Anderson:
Generation of IPv6 Atomic Fragments Considered Harmful. RFC 8021: 1-12 (2017) - [i29]Fernando Gont, Alissa Cooper, David Thaler, Will (Shucheng) Liu:
Recommendation on Stable IPv6 Interface Identifiers. RFC 8064: 1-9 (2017) - 2016
- [i28]Fernando Gont, Tim Chown:
Network Reconnaissance in IPv6 Networks. RFC 7707: 1-38 (2016) - [i27]Alissa Cooper, Fernando Gont, David Thaler:
Security and Privacy Considerations for IPv6 Address Generation Mechanisms. RFC 7721: 1-18 (2016) - [i26]Fernando Gont:
Security Implications of Predictable Fragment Identification Values. RFC 7739: 1-20 (2016) - [i25]Fernando Gont, Jen Linkova, Tim Chown, Will (Shucheng) Liu:
Observations on the Dropping of Packets with IPv6 Extension Headers in the Real World. RFC 7872: 1-15 (2016) - [i24]CongXiao Bao, Xing Li, Fred Baker, Tore Anderson, Fernando Gont:
IP/ICMP Translation Algorithm. RFC 7915: 1-34 (2016) - [i23]Fernando Gont, Will (Shucheng) Liu:
A Method for Generating Semantically Opaque Interface Identifiers (IIDs) with the Dynamic Host Configuration Protocol for IPv6 (DHCPv6). RFC 7943: 1-10 (2016) - 2015
- [i22]Brian E. Carpenter, Tim Chown, Fernando Gont, Sheng Jiang, Alexandru Petrescu, Andrew Yourtchenko:
Analysis of the 64-bit Boundary in IPv6 Addressing. RFC 7421: 1-24 (2015) - [i21]Marcelo Bagnulo, Christoph Paasch, Fernando Gont, Olivier Bonaventure, Costin Raiciu:
Analysis of Residual Threats and Possible Fixes for Multipath TCP (MPTCP). RFC 7430: 1-19 (2015) - [i20]Fernando Gont, Will (Shucheng) Liu, Gunter Van de Velde:
DHCPv6-Shield: Protecting against Rogue DHCPv6 Servers. RFC 7610: 1-12 (2015) - 2014
- [i19]Fernando Gont, Vishwas Manral, Ronald P. Bonica:
Implications of Oversized IPv6 Header Chains. RFC 7112: 1-8 (2014) - [i18]Fernando Gont:
Implementation Advice for IPv6 Router Advertisement Guard (RA-Guard). RFC 7113: 1-13 (2014) - [i17]Fernando Gont, Will (Shucheng) Liu:
Security Implications of IPv6 on IPv4 Networks. RFC 7123: 1-19 (2014) - [i16]Fernando Gont, Randall J. Atkinson, Carlos Pignataro:
Recommendations on Filtering of IPv4 Packets Containing IPv4 Options. RFC 7126: 1-36 (2014) - [i15]Fernando Gont:
A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC). RFC 7217: 1-19 (2014) - [i14]Fernando Gont:
Layer 3 Virtual Private Network (VPN) Tunnel Traffic Leakages in Dual-Stack Hosts/Networks. RFC 7359: 1-12 (2014) - 2013
- [i13]Fernando Gont, Carlos Pignataro:
Formally Deprecating Some ICMPv4 Message Types. RFC 6918: 1-8 (2013) - [i12]Fernando Gont:
Processing of IPv6 "Atomic" Fragments. RFC 6946: 1-9 (2013) - [i11]Fernando Gont:
Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery. RFC 6980: 1-10 (2013) - 2012
- [i10]Fernando Gont, Steven M. Bellovin:
Defending against Sequence Number Attacks. RFC 6528: 1-12 (2012) - [i9]Fernando Gont:
Deprecation of ICMP Source Quench Messages. RFC 6633: 1-8 (2012) - [i8]Carlos Pignataro, Fernando Gont:
Formally Deprecating Some IPv4 Options. RFC 6814: 1-6 (2012) - 2011
- [i7]Michael Vittrup Larsen, Fernando Gont:
Recommendations for Transport-Protocol Port Randomization. RFC 6056: 1-29 (2011) - [i6]Fernando Gont, Andrew Yourtchenko:
On the Implementation of the TCP Urgent Mechanism. RFC 6093: 1-12 (2011) - [i5]Fernando Gont:
Reducing the TIME-WAIT State Using TCP Timestamps. RFC 6191: 1-10 (2011) - [i4]Fernando Gont:
Security Assessment of the Internet Protocol Version 4. RFC 6274: 1-75 (2011) - 2010
- [i3]Fernando Gont:
ICMP Attacks against TCP. RFC 5927: 1-36 (2010)
2000 – 2009
- 2009
- [i2]Fernando Gont:
TCP's Reaction to Soft Errors. RFC 5461: 1-13 (2009) - [i1]Lars Eggert, Fernando Gont:
TCP User Timeout Option. RFC 5482: 1-14 (2009)
Coauthor Index
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from , , and to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from .
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-04-25 05:49 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint