rfc.dk

Cited in: RFC 10040

12 RFCs mentioned in the text of RFC 10040 (Locator/ID Separation Protocol (LISP) Geo-Coordinates)

RFCTitleStatusDate
2119Key words for use in RFCs to Indicate Requirement LevelsS. BradnerBest Current PracticeMarch 1997
6280An Architecture for Location and Location Privacy in Internet ApplicationsR. Barnes, M. Lepinski, A. Cooper, J. Morris, H. Tschofenig, H. SchulzrinneBest Current PracticeJuly 2011
6973Privacy Considerations for Internet ProtocolsA. Cooper, H. Tschofenig, B. Aboba, J. Peterson, J. Morris, M. Hansen, R. SmithInformationalJuly 2013
7841RFC Streams, Headers, and BoilerplatesJ. Halpern, Ed., L. Daigle, Ed., O. Kolkman, Ed.InformationalMay 2016
8060LISP Canonical Address Format (LCAF)D. Farinacci, D. Meyer, J. SnijdersExperimentalFebruary 2017
8126Guidelines for Writing an IANA Considerations Section in RFCsM. Cotton, B. Leiba, T. NartenBest Current PracticeJune 2017
8174Ambiguity of Uppercase vs Lowercase in RFC 2119 Key WordsB. LeibaBest Current PracticeMay 2017
9179A YANG Grouping for Geographic LocationsC. HoppsProposed StandardFebruary 2022
9300The Locator/ID Separation Protocol (LISP)D. Farinacci, V. Fuller, D. Meyer, D. Lewis, A. Cabellos, Ed.Proposed StandardOctober 2022
9301Locator/ID Separation Protocol (LISP) Control PlaneD. Farinacci, F. Maino, V. Fuller, A. Cabellos, Ed.Proposed StandardOctober 2022
9303Locator/ID Separation Protocol Security (LISP-SEC)F. Maino, V. Ermagan, A. Cabellos, D. SaucezProposed StandardOctober 2022
9735Locator/ID Separation Protocol (LISP) Distinguished Name EncodingD. Farinacci, L. Iannone, Ed.Proposed StandardFebruary 2025